> 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/after-the-event/after.md).
# Wrap up your event
Wrapping up has two parts: the closing ceremony in the last 15 minutes of the event, and the post-event work afterward. The ceremony and the same-day basics are required. Everything beyond that is optional.
## The closing ceremony (final 15 minutes)
Spend the final 15 minutes on three things: celebrate the group, recognize top performers without diminishing everyone else, and point people to what's next. Roughly 5 minutes each.
{% hint style="info" %}
Everyone who participated tackled real cybersecurity challenges. Celebrate that, regardless of how far they got.
{% endhint %}
### Give a time warning
About 10 to 15 minutes before the end:
```
About 10 minutes left. Finish what you're working on and submit any final answers. If you didn't finish everything, that's normal. Your progress is saved, and most people keep investigating after the event.
```
### Celebrate the group, then the winners
Recognize the whole group before announcing standings. Specific observations land harder than generic praise ("Someone found a clever approach to Challenge 7").
{% tabs %}
{% tab title="Individual events" %}
Announce the top 3 to 5 with scores. Add context like "these scores represent completing X out of Y challenges."
{% endtab %}
{% tab title="Team events" %}
Announce top teams. Call out collaboration and how teams used different strengths.
{% endtab %}
{% endtabs %}
Frame winning as "went the furthest today," not "were the best." For the full closing script, see [Templates and materials](/event-resources/templates.md#host-scripts).
### Point everyone forward
Their account saves progress, so they can keep playing "A Scandal in Valdoria," try other modules, or sign up at [kc7cyber.com](https://kc7cyber.com). Point students to clubs and competitions, professionals to certifications.
### Gather feedback before they leave
```
Take 2 minutes for our participant survey. Your feedback shapes what we do next.
```
Share it by link, QR code, or chat. In person, close out logistics: stick around 10 to 15 minutes for questions and offer group photos.
## After the event
### The required minimum
**Within 24 to 48 hours:**
1. Email participants the final scoreboard and a thank-you. Use the [follow-up template](/event-resources/templates.md#follow-up-email-post-event).
2. Thank volunteers, co-hosts, and anyone who helped.
3. Confirm participants can still access the game.
**Within one week:**
4. Fill out the [KC7 post-event survey](https://forms.gle/uvW9wd7AyEN1Hzce6) so KC7 can issue digital badges.
5. Open your tenant dashboard and review results.
That's a complete close. Everything below is optional.
### Optional follow-up
Worth doing if you plan to host again or want to build a community.
Collect feedback and testimonials
Send a 3 to 5 minute survey ([template](/event-resources/templates.md#participant-feedback-survey)) and reach out to engaged participants for testimonials while enthusiasm is high. Ask permission before quoting anyone.
Review your analytics
Pull completion rates, hardest questions, and drop-off points from your tenant dashboard. See [Track performance](/manage-your-tenant/analytics.md). Use it to tune difficulty and timing next time.
Build a community and plan the next event
Set up a space (Discord, Slack, email list) and share updates. Only add people who opt in. Create your next game anytime from the tenant, no approval needed. See [Manage games](/manage-your-tenant/managing-games.md).
Report to stakeholders
For sponsors and leadership, share attendance, feedback highlights, learning outcomes, and photos. For the KC7 Foundation, the post-event survey triggers participant badges and unlocks support.
## Your tenant stays active
Your KC7 tenant doesn't expire. Event data and analytics stay accessible, you can create new games anytime, and participants can keep playing. Some hosts run dozens of events, others run one. Both are fine. See [Use your tenant](/your-tenant/overview.md).
## Common questions
* **Did my event go well?** If participants stayed engaged and left positive, yes. Engagement matters more than completion rate.
* **What if people didn't finish?** Expected. The learning happens during the investigation, not at completion.
* **Should I run another event?** Only if you want to. Your tenant stays active, so you can return whenever.
## Next 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/after-the-event/after.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.