# In-Person Events
In-person events trade some logistical overhead for immediacy. You can read body language, hear the side conversations, and announce one fix instead of typing it twenty times. The flip side is that WiFi, power, room layout, and circulation all become your problem.
{% hint style="success" %}
**In-person events shine for** building community, hands-on facilitation, immediate problem-solving, and creating shared memories.
{% endhint %}
***
## 🏢 Choosing Your Venue
A workable venue gives every participant a seat with laptop space, accessible power, reliable WiFi, and a screen visible from anywhere in the room. You also need room to walk between participants without climbing over chairs.
Beyond the room itself, check the basics. Clear signage or directions to find it, accessibility for all participants, parking or transit nearby, restrooms, and ideally a separate area for breaks or food.
### Common Venue Types
{% tabs %}
{% tab title="Classroom/Lab" %}
**Perfect for** school events and training programs. Built-in tech, IT support, and a familiar setting for students. Watch for network restrictions and after-hours access limits.
{% endtab %}
{% tab title="Conference Room" %}
**Perfect for** corporate events and professional training. Reliable infrastructure and good AV, but seating tends to be formal and refreshment space is often tight.
{% endtab %}
{% tab title="Community Space" %}
**Perfect for** public workshops. Flexible layout and low cost, but WiFi and equipment vary, and you may own setup and teardown.
{% endtab %}
{% tab title="Hackathon/Event Space" %}
**Perfect for** large competitions and multi-day events. Designed for tech crowds with strong WiFi, at higher cost and longer booking lead time.
{% endtab %}
{% endtabs %}
***
## 🌐 WiFi Management
WiFi is the single most common failure point. Test it the week before with as many devices as you can muster, verify roughly 3 Mbps per participant, and check that the network doesn't block `*.kc7cyber.com`. Test from several spots in the room, not just near the router.
The day before, confirm credentials still work, run a speed test during the time of day your event will run, and grab the IT contact's number.
### Setup on Event Day
Use a guest network when possible since it usually has fewer restrictions. For larger events, ask about a dedicated network. Always have a mobile hotspot or two on hand as backup.
Display the WiFi name and password somewhere everyone can see from their seat. Whiteboard, large printout, or welcome slide all work. Say it out loud during the intro too.
### Bandwidth Calculator
```
Required Bandwidth = Number of Participants × 3 Mbps × 1.5 (buffer)
```
* 10 participants ≈ 45 Mbps
* 30 participants ≈ 135 Mbps
* 50 participants ≈ 225 Mbps
{% hint style="warning" %}
**School/Corporate Networks**: Test KC7 access well in advance. Some networks block cloud services or require IT approval for whitelisting.
{% endhint %}
***
## 🎬 Room Setup & Projection
### Physical Layout Options
* **Theater style** (30+): Rows facing the screen. Easy to present to, harder for collaboration.
* **Clusters** (team events): Groups of 3-4 per table. Good for teamwork; you circulate between groups.
* **U-shape** (10-20): Everyone faces the center. You see the whole room and discussion flows naturally.
* **Open layout** (flexible): Scattered tables, informal feel, participants choose seats.
### Projection & Display
Test the projector before participants arrive. Keep the screen showing useful information throughout. A welcome slide with WiFi credentials, the Go Link, KC7 intro videos during the opening, and the live scoreboard at key moments. A timer helps if you're working to a hard stop.
Run an audio check too. Confirm video playback volume, test any microphone, and listen for echo or feedback.
***
## 📋 Day-of-Event Checklist
### Arrive Early (60-90 minutes before)
**Physical setup**
* [ ] Unlock venue, lights on, signage posted
* [ ] Tables and chairs arranged for your chosen layout
* [ ] Projection and audio tested
**Technical testing**
* [ ] WiFi connected and speed verified
* [ ] WiFi credentials displayed
* [ ] One participant account walked through end-to-end
* [ ] Host dashboard open on your device
* [ ] Go Link tested in a couple of browsers
**Materials ready**
* [ ] Welcome slides up
* [ ] Go Link visible
* [ ] Name tags, prizes, backup activity (if using)
### Brief Volunteers (30 minutes before)
If you have co-hosts, walk them through their roles, assign each one a section of the room to monitor, and align on when to step in versus when to let participants work through it. Confirm their devices and access work before doors open.
***
## 🎪 Creating In-Person Energy
### Opening
Greet people as they arrive, have music playing, and show genuine excitement about what's coming. The energy you set in the first ten minutes carries through the event.
### During the Investigation
Keep moving. Walk a full perimeter every 10-15 minutes and vary your route so you're not always passing the same people. Pause near anyone who looks stuck, listen to conversations without interrupting, and position yourself where you can see most of the room.
Call out interesting moments out loud without spoiling: "Someone just uncovered something good," or "Several people just made it past Challenge 3." It builds momentum without giving anything away.
### Reading the Room
* **High energy or focused quiet** mean it's working. Stay out of the way.
* **Frustrated energy** calls for encouragement and reminders about hints.
* **Low energy** is a cue to call a break or share a group-level hint.
* **Confusion** usually means something needs to be addressed to the whole room.
***
## 👥 Working with Groups
### Individual vs Team Events
{% tabs %}
{% tab title="Individual Events" %}
Participants work on their own accounts with their own scoreboard entries. Circulate to everyone, give personalized encouragement, and allow informal collaboration. Watch for anyone who looks isolated and pull them into the room.
{% endtab %}
{% tab title="Team Events" %}
Teams of 2-4 share ideas and a single scoreboard entry. Check in with whole teams rather than individuals, and watch for one person dominating while others disengage. Foster competition between teams without losing the cross-team sharing.
{% endtab %}
{% endtabs %}
### Handling Different Participant Types
**Rapid advancers** Celebrate their progress and consider asking them to explain their methods or help a neighbor (only if they're up for it).
**Steady workers** The majority. Positive reinforcement goes a long way. Don't rush them.
**Struggling participants** Check in privately, never publicly. Ask what they've tried, point them to the hint system, and consider pairing them with someone if they'd welcome it.
**Off-task or distracted** A friendly check-in usually re-engages them. If not, they may need a break, or the content may not be matching their level.
***
## 🎯 Effective Facilitation
### What to Say Instead of Giving Answers
* "What patterns do you see in this data?"
* "The hint button might help you here."
* "Tell me what you've discovered so far."
* "What do you think this log entry means?"
### Encouraging Stuck Participants
* "Getting stuck is part of learning cybersecurity."
* "Try breaking this down into smaller pieces."
* "What's one thing you know for certain?"
* "That's exactly the kind of thinking security analysts use."
### Group Announcements
Every 30-45 minutes, share an observation that builds momentum without spoiling. Things like "I'm seeing fantastic detective work happening," or "Remember the hint system is there to help you progress." If you're working to a deadline, give time updates with a reassuring note that everyone's learning regardless of how far they get.
***
## 🛠️ In-Person Troubleshooting
### Common On-Site Issues
**"I can't connect to WiFi"** Verify credentials, forget and rejoin the network, then fall back to a hotspot. If it's widespread, get IT involved.
**"KC7 won't load"** Check the connection, try a different browser, clear cache, try incognito, then try a different device.
**"I lost my progress"** Confirm they're logged into the right account on the right Go Link. Progress auto-saves, so it's almost always a login issue. Note the username for follow-up if not.
**Technical meltdown** Stay calm since participants follow your lead. Acknowledge the issue out loud, switch to your backup plan, and keep the room engaged. Sometimes the best move is to make the troubleshooting itself part of the lesson.
### Power & Hardware
If laptops start dying, point people to outlets and share power strips. For projector failures, share the Go Link verbally, fall back to printouts, and let participants work on their own screens. Bring more power strips and extension cords than you think you need.
***
## 📦 Physical Materials
**Must have**
* [ ] Power strips and extension cords
* [ ] WiFi credentials displayed (poster or whiteboard)
* [ ] Go Link displayed prominently
* [ ] Host device with dashboard access
* [ ] Backup internet (mobile hotspot)
**Nice to have**
* [ ] Name tags or tent cards
* [ ] Printed troubleshooting guide
* [ ] Prizes
* [ ] Snacks and a music speaker
**Emergency kit**
* [ ] Extra power adapters
* [ ] Printed backup activity
* [ ] First aid kit
* [ ] Venue contact information
***
## 🎊 Closing Your Event
### Final 15 Minutes
Give a five-minute warning, then bring the room back together. Display the final scoreboard, recognize top scorers, and highlight a few interesting approaches you saw. Award prizes if you have them. A quick group reflection ("What surprised you about cybersecurity?") works well to close out and leads naturally into discussion of next steps and career paths.
Remind participants they can keep investigating after the event, and share what's coming next from KC7.
### Venue Cleanup
* [ ] Furniture returned to original layout
* [ ] Equipment and materials packed
* [ ] Feedback forms collected
* [ ] Photos of the setup for next time
* [ ] Equipment off, lights off, doors locked
***
## A note on what in-person gives you
The advantage of being in the same room is immediacy. You can walk over and see exactly what someone is seeing, give a thumbs-up across the room, or notice a breakthrough in someone's posture before they even speak. Participants meet each other, form study groups on their own, and build the kind of connections that don't happen over a chat window. The shared experience tends to stick.
***
## 🔗 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/running/in-person.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.