> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/running-your-event/supporting-participants.md). # Support participants Your job during the investigation is to encourage, point people to the built-in resources, and keep energy positive. KC7 handles the cybersecurity instruction. For the event flow, see [Run event day](/running-your-event/event-day.md). ## What you own and what you don't **You own:** a safe environment to make mistakes, pointing people to hints and tutorials, circulating to check in, celebrating discoveries, and managing time. **You don't own:** teaching cybersecurity (the game does that), solving challenges, answering every technical question, or making sure everyone finishes. The journey matters more than completion. ## Give hints without spoilers Escalate gently, one step at a time: 1. Redirect to resources. "Have you tried the hint button?" 2. Ask a guiding question. "What columns of data do you have?" 3. Give strategic direction. "This challenge is about patterns in the timestamps." Instead of answering, ask a question back: they ask "How do I filter this?", you ask "What are you trying to find?" {% hint style="warning" %} Never give exact answers or syntax. Guide them to the built-in hints or a peer. {% endhint %} ## What to say | Situation | What to say | What to avoid | | -------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------- | | "I'm completely stuck." | "Have you tried the hint button? What have you tried so far?" | Giving the answer | | "Is this answer right?" | "What makes you think that? Try submitting and see." | Confirming from their screen | | "I don't understand this." | "The game explains concepts as you hit them. Try reading the challenge again." | A technical explanation | | "This is too hard." | "These are meant to be challenging. Getting stuck is part of learning. Try a hint." | Agreeing, or comparing them to others | | "I'm finished. What now?" | "Did you try the bonus challenges? Want to help others without giving answers?" | Letting them disengage | For a struggling participant, normalize it ("This one stumps almost everyone"), shift focus to what they've already learned, and offer a fresh start ("Grab water and come back"). "You haven't figured it out *yet*" keeps the door open. For an advanced one, deepen the thinking ("Can you explain why that works?") or invite them to peer-teach. ## Energy check-ins Three group nudges during the event: > **30-45 min:** "Great progress on the scoreboard. Reminder that there are built-in hints if you get stuck." > **60 min:** "About halfway. Feeling stuck is normal. These are designed to make you think. Use those hint buttons." > **Final 30 min:** "Thirty minutes left. If you haven't finished, that's normal. Focus on the challenges you find most interesting." ## When to step in vs let them struggle Healthy struggle is 5 to 10 minutes of active thinking. Step in when frustration turns to disengagement, they've been stuck 15+ minutes with no progress, they're unaware of a resource, or tech is blocking them. ## By format {% tabs %} {% tab title="In-person" %} Circulate constantly, crouch to eye level when helping, and use group announcements for common issues. Check in with struggling participants privately, and mix skill levels at tables. {% endtab %} {% tab title="Virtual" %} Monitor chat and acknowledge every question. Public chat for tips that help everyone, private messages for individual encouragement. Post periodic hint reminders, and use breakout rooms for small-group help. {% endtab %} {% endtabs %} ## Host tools Check the **live scoreboard** every 15 to 20 minutes (not constantly) for group progress, and the **analytics dashboard** for which challenges are hardest. Use both for general guidance, not to single people out. ## Technical issues Specific fixes are in the [Troubleshooting guide](/event-resources/troubleshooting.md). In the moment: stay calm, try a quick fix (refresh, different browser, clear cache), escalate to support if needed, and keep everyone else engaged. {% hint style="info" %} If KC7 is loading and accepting answers, it's working. The difficulty is intentional. {% endhint %} ## Finishers and stallers Celebrate early finishers and invite them to help others or explore bonus challenges. Reassure those still working that not finishing is normal. Their account saves progress, so they can continue anytime. ## Related pages * [Troubleshooting guide](/event-resources/troubleshooting.md) * [Event FAQs](/event-resources/faq.md) * [Get help](/community/getting-help.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kc7cyber.com/running-your-event/supporting-participants.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.