> 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/event-day.md). # Run event day This guide takes you through event day in order. Pre-arrival setup, welcome and intro, the investigation, then closing. Pull this page up on your phone and follow along. {% hint style="info" %} Three things hosts wish they'd known: the first 15 minutes (logins and orientation) are the hardest, then it gets easier. You don't need to understand the cybersecurity, since the game teaches it. And most participants won't finish, which is fine. Five questions of progress is a successful event. {% endhint %} ## Before you begin You need a tested setup and your approval email open. If you haven't done final prep, see [Set up before the event](/running-your-event/pre-event-setup.md). ## The five phases {% stepper %} {% step %} ### Before participants arrive (15 to 30 minutes) Arrive early to test your setup. 1. Confirm your internet connection is stable. 2. Open your host dashboard on your device. 3. Open the Go Link in a separate window so you can show participants what they'll see. 4. Test projection or screen sharing if you're using it. 5. Have any backup tech ready (mobile hotspot, second laptop). {% endstep %} {% step %} ### Welcome and introduction (10 to 15 minutes) #### Play the KC7 intro videos Start by playing the two videos on your KC7 intro page. They cover what KC7 is, the Valdoria scenario, and what participants will experience. #### Set the stage After the videos, add your own welcome. Keep it short. Sample wording: ``` Welcome to our KC7 cybersecurity investigation. You're about to become digital detectives solving a mystery in the Kingdom of Valdoria. No cybersecurity experience needed. The game teaches you as you go. You'll have about 90 minutes. Don't worry about finishing. The learning happens throughout, and everyone works at their own pace. There's a live scoreboard if you enjoy friendly competition. ``` #### Cover four key points * This is meant to be challenging. Getting stuck is part of learning. * Each person creates their own account so progress is tracked individually. * Working with a neighbor or teammate is encouraged. * Ask for help anytime. You're not expected to solve it alone. {% endstep %} {% step %} ### Get participants started (5 to 10 minutes) #### Share the Go Link Display your Go Link where everyone can see it. Write it on the board, project it, drop it in chat for virtual events, or text the link to the group. #### Account creation Have everyone visit the Go Link and create an account. Two options: * **Full account (recommended).** Saves progress so participants can return later. * **Guest play.** Works for the event, but progress isn't saved. Encourage full accounts so people can finish later if they want. #### Quick check Once everyone has accessed the game, ask: "Can everyone see the Kingdom of Valdoria welcome screen?" If yes, they can start. {% endstep %} {% step %} ### Facilitate the investigation (60 to 90 minutes) Your job during the investigation is encouragement and light guidance. The game handles the cybersecurity teaching. #### Do this * Circulate and check energy levels. * Offer encouragement when someone gets stuck. * Remind participants to use the built-in hint system. * Monitor the live scoreboard for overall progress. * Be visibly enthusiastic about discoveries. #### Avoid this * Giving away answers. * Teaching cybersecurity concepts. The game does that. * Rushing participants who are working methodically. * Focusing only on the highest scorers. For detailed coaching strategies, see [Support participants](/running-your-event/supporting-participants.md). #### Use your host tools The **live scoreboard** shows progress. Check it every 15 to 20 minutes. If most people are stuck on the same challenge, give a gentle group reminder about hints. The **analytics page** shows which challenges are hardest and overall success rates. Useful for spotting common sticking points. For what to say to stuck participants, see [Support participants](/running-your-event/supporting-participants.md). #### Time check at 30 to 45 minutes ``` How's everyone doing? Great progress on the scoreboard. Reminder that there are built-in hints if you get stuck, and you're welcome to discuss approaches with each other. ``` #### Time check at 60 minutes (if applicable) ``` About 30 minutes left. If you haven't finished, that's normal. Focus on the challenges you find most interesting rather than trying to finish everything. ``` {% endstep %} {% step %} ### Wrap up (10 to 15 minutes) Celebrate the group, then the top performers, then point everyone forward. Sample wording: ``` Congratulations everyone. You've just completed your first cybersecurity investigation. Whether you solved the whole mystery or worked through a few challenges, you've learned real digital investigation skills. ``` For the full closing flow with sample script, see [Wrap up your event](/after-the-event/after.md). {% endstep %} {% endstepper %} ## Quick reference * **Welcome and intro.** 10 to 15 minutes * **Get started.** 5 to 10 minutes * **Investigation.** 60 to 90 minutes * **Wrap-up.** 10 to 15 minutes ## Next step Continue to [Wrap up your event](/after-the-event/after.md) for the closing ceremony and post-event steps. --- # 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/event-day.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.