> 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/pre-event-setup.md).

# Set up before the event

Once approved, plan a couple of hours over the week before. The most useful step by far is playing the game yourself. For the three links in your approval email, see [Request your event](/getting-started/request-event.md#read-your-approval-email).

## Play the game yourself

Complete "A Scandal in Valdoria" before your event. You'll know where people get stuck and feel confident guiding them.

1. Go to [kc7cyber.com/go/VALDY](https://kc7cyber.com/go/VALDY).
2. Create a KC7 account if you don't have one.
3. Play through. Plan for about 90 minutes.
4. Note the confusing parts, the "a-ha" moments, and how long each section takes.

## Prepare your team

**Solo hosts.** Complete the module, review [Technical requirements](/planning/technical-requirements.md), and keep support contacts handy.

**Team hosts.** Have all volunteers complete the module. Assign registration, tech support, and roaming roles, brief the team on common issues, and pick a comms channel for the day.

Pull your opening, mid-event, and closing wording from the [host scripts](/event-resources/templates.md#host-scripts).

## Pre-event checklist

**One week before**

* [ ] Complete "A Scandal in Valdoria" yourself
* [ ] Brief volunteers and test your Go Link
* [ ] Send participant invitations
* [ ] Review [Technical requirements](/planning/technical-requirements.md)

**A few days before**

* [ ] Test the tech setup from the actual venue or platform
* [ ] Prepare opening remarks and send a participant reminder

**Day of**

* [ ] Arrive 15 to 30 minutes early
* [ ] Test internet and projection, then open the host dashboard and Go Link

The [full prep timeline](/planning/planning.md#full-prep-timeline) has every milestone.

<details>

<summary>Tips from experienced hosts</summary>

> "I tell participants upfront that getting stuck is part of learning. I got stuck too when I played." — High school teacher

> "I walk around and ask 'What are you discovering?' instead of 'Do you need help?'" — Corporate trainer

> "I keep the troubleshooting guide open on my laptop. It's saved me several times." — University TA

</details>

## Next step

Move on to [Run event day](/running-your-event/event-day.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/pre-event-setup.md?ask=<question>&goal=<endgoal>
```

`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.