# Closing Your Event
The final 15 minutes shape what participants remember. A good closing celebrates the group, recognizes top performers without diminishing everyone else, and points people toward what to do next. Plan for roughly 5 minutes gathering and celebrating, 5 minutes on results, and 5 minutes on next steps and feedback.
{% hint style="success" %}
Everyone who participated tackled real cybersecurity challenges. Celebrate that, regardless of how far they got.
{% endhint %}
## The Emotional Mix in the Room
Different participants need different things from your closing. Competitors want recognition for their effort without it stinging the rest of the room. Steady learners want their experience validated as worthwhile even if they didn't "win." People who struggled need to hear that completion isn't the point. The curious want to know what comes next. Address all four by celebrating the group first, then announcing top performers, then giving everyone a clear path forward.
The tone should feel like a coach after a hard game, not a teacher reading scores. "Let's recognize our top performers" lands very differently than "Let's see who won."
***
## Timing Your Close
### Give Adequate Warning
About 10-15 minutes before the end, announce something like:
> "We have about 10 minutes left. Good time to finish what you're working on, submit any final answers, and reflect on what you found. If you didn't finish everything, that's normal. Most people keep investigating after the event, and your progress is saved."
{% hint style="info" %}
Many participants will be deep in focus. Give them time to reach a natural stopping point rather than ending mid-challenge.
{% endhint %}
### Prepare Your Closing Materials
While participants finish up, open your host dashboard for final standings, pull up your closing remarks, prep any prizes or certificates, and queue the participant survey.
***
## Celebrate Everyone First
Before announcing winners, recognize the whole group. Something like:
> "Take a moment to appreciate what you all did today. You used the same investigation techniques professional analysts use. You worked through hard problems and didn't quit. You found patterns in real data. Whether you completed 3 challenges or 13, you grew today."
If you noticed great moments during the event, call them out. Specific observations land harder than generic praise:
* "I loved seeing people help each other through tricky queries."
* "Someone found a really clever approach to Challenge 7."
* "The energy when those 'a-ha' moments hit was great to watch."
{% hint style="info" %}
Participants often feel discouraged if they didn't "win." Celebrating the learning first makes everyone feel valued.
{% endhint %}
***
## Share Final Standings
### Announce Winners with Context
After celebrating the group, share the scoreboard:
> "Now let's recognize today's top performers."
{% tabs %}
{% tab title="Individual Events" %}
Announce the top 3-5 with scores. Add context like "these scores represent completing X out of Y challenges" or "the furthest anyone got was Challenge X, which is impressive." Mention if it was a close race.
{% endtab %}
{% tab title="Team Events" %}
Announce top teams with scores. Call out collaboration you saw on the winning teams and how they used different strengths. Reinforce that real cybersecurity work is collaborative.
{% endtab %}
{% endtabs %}
### Distribute Prizes or Recognition
If you're giving out prizes, certificates, or recognition, call winners up individually or by team, take photos with permission, and have everyone applaud each one. In-person events make for great photo moments, useful for follow-up and future promotion.
{% hint style="warning" %}
Frame winning as "went the furthest today," not "were the best." Avoid language that makes non-winners feel like they failed.
{% endhint %}
***
## Share Key Learning Moments
### Highlight Real-World Connections
Tie the game back to actual security work:
> "What you did today mirrors what professional cybersecurity analysts do every day. You investigated logs, queried databases for patterns, followed evidence trails, and thought creatively about complex problems. Those skills are exactly what the field needs."
### Call Out Interesting Findings
Share notable moments without spoiling for those who'll continue later. "Several of you found clever ways to query the data," or "those who keep investigating will uncover more of the Valdoria story."
### Reinforce That Struggle Is Learning
> "If you felt challenged today, that's good. Nobody becomes a cybersecurity expert in 90 minutes. You took a real first step, and you know more than you did two hours ago."
***
## Provide Clear Next Steps
### Continue with KC7
Their account saves their progress, so they can keep going on "A Scandal in Valdoria" from where they stopped, try other modules, or create a free account at kc7cyber.com for more content.
### Connect to Broader Resources
**For students:** talk to teachers about KC7 in the classroom, look into cybersecurity clubs and competitions, explore degree programs and certifications.
**For professionals:** check on internal training programs, look at industry certifications, and remember that many security careers don't require coding.
**For everyone:** follow KC7 on social media, join cybersecurity communities, and share the experience with others who'd be interested.
***
## Gather Feedback
Ask people to fill out a short survey before they leave:
> "We want to make these events better. Please take 2 minutes for our participant survey. Your feedback shapes what we do next."
Share the survey by displayed link or QR code, chat message for virtual events, immediate email, or printed handout in person.
For informal feedback, ask "What was your favorite part?", "What was most challenging?", and "Would you recommend this to a friend?". Listen for patterns to inform your next event.
***
## Smooth Transitions
### In-Person Events
Cover the logistics. People are welcome to stay or head out, take materials they want, return any borrowed equipment, and check for belongings. Stick around for 10-15 minutes for one-on-one questions, have your contact info ready, and offer group photos.
### Virtual Events
Wrap up clearly with thanks, an offer to stay on for questions, a pointer to the survey link in email, and an invitation for final thoughts before closing. Send a follow-up email within 24 hours with the survey, resources, and any photos or highlights.
***
## Sample Closing Script
> "Alright everyone, let's bring our KC7 investigation to a close.
>
> First, recognize all of you. What you did today is impressive. You learned real cybersecurity skills, tackled hard problems, and showed great persistence. Whether you finished 3 challenges or 13, you grew as a digital detective today.
>
> I loved watching you help each other, ask thoughtful questions, and have those exciting moments when something clicked. That's exactly the kind of curiosity the field needs.
>
> Let's celebrate our top performers: \[announce winners with scores]. Everyone should be proud of what they did.
>
> What you practiced today is what professional analysts do every day: investigating logs, following evidence, and solving complex puzzles to protect organizations. The skills matter in the real world.
>
> Your progress is saved, so you can continue anytime at kc7cyber.com. Keep going - the story gets more interesting.
>
> Before you leave, please take 2 minutes for our feedback survey \[share link]. Your input helps us make these events better.
>
> Thank you all for being here and bringing such great energy. Stay curious, keep learning. Any final questions?"
***
## Post-Closing Actions
### Same Day
* [ ] Send a thank you email
* [ ] Include the survey link if not yet completed
* [ ] Share any promised resources
* [ ] Post photos with permission
### Within 48 Hours
* [ ] Review survey responses
* [ ] Send congratulations to winners
* [ ] Follow up on any technical issues reported
* [ ] Document lessons learned
### Ongoing
* [ ] Stay connected with interested participants
* [ ] Share future event updates
* [ ] Connect participants to relevant opportunities
See [Post-Event Follow-Up](/hosting-an-event/after/followup.md) for full next steps.
***
## Tips from Experienced Hosts
{% hint style="info" %}
"I always end by saying 'cybersecurity needs people who think like you.' It helps everyone feel they belong in this field." — University Professor
{% endhint %}
{% hint style="info" %}
"A group photo at the end creates a sense of accomplishment and gives me promotional material for future events." — Corporate Event Organizer
{% endhint %}
{% hint style="info" %}
"I ask participants to share one word describing their experience. You get responses like 'challenging,' 'eye-opening,' 'fun.' Great energizing close." — High School Teacher
{% endhint %}
***
## Common Mistakes to Avoid
{% hint style="warning" %}
**Rushing.** Take the full 15 minutes. The closing matters as much as the opening.
{% endhint %}
{% hint style="warning" %}
**Only celebrating winners.** Recognize the whole group first.
{% endhint %}
{% hint style="warning" %}
**Forgetting next steps.** Everyone wants to know "what now?". Give them paths.
{% endhint %}
{% hint style="warning" %}
**Skipping feedback.** Survey responses are how you improve.
{% endhint %}
***
## Related Resources
---
# Agent Instructions: 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:
```
GET https://docs.kc7cyber.com/hosting-an-event/after/closing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.