Check-in looks like a clipboard problem. It is actually three jobs stacked on top of each other: proving who is in the room, getting people into it quickly, and capturing the record you will need later. Solve one and ignore the others and you get the familiar outcomes: a safe process with a twenty minute line, a fast process with no usable data, or a tidy spreadsheet nobody can act on.
The three jobs check-in is doing
Before choosing any tool, be explicit about which of these matters most for the room you are running. The right setup for a children’s program is genuinely different from the right setup for a conference, and the difference comes from this ranking.
| Job | What good looks like | Where it matters most |
|---|---|---|
| Safety and custody | Only an authorized adult can collect a child | Kids programs, youth events, camps |
| Throughput | Under 15 seconds per person at peak | Conferences, large services, classes |
| The record | Accurate attendance you can query later | Grants, membership, follow-up, capacity planning |
A useful exercise: rank those three for your context and write the ranking down. Most disagreements about check-in are really disagreements about the ranking, and they get resolved quickly once it is on paper.
Safety: the parts that are not optional
For any program with minors, check-in is a child protection system first and an attendance tool second. These elements are not preferences.
- Matching claim tags. A unique code printed on both the child’s tag and the guardian’s receipt, regenerated every session. Reusable numbers defeat the purpose.
- An authorized pickup list. Attached to the child’s record, editable only by a staff member, visible to the volunteer at the door.
- Allergy and medical flags on the tag. Printed where a volunteer will see it without opening anything. This is the single most-used field in the system.
- A visible room roster. Whoever is in the room should be able to see who is supposed to be there, and count.
- A written incident path. What happens if a tag is lost, if an unlisted adult arrives, if a child leaves the room. Volunteers should not be improvising these decisions at the door.
One process point worth more than any feature: train volunteers that the tag rule has no exceptions, including for people they recognize. Every serious failure in this area starts with a well-meaning volunteer making a reasonable exception for a familiar face.
Throughput: where the line actually forms
Queues are rarely caused by slow software. They are caused by one station handling both simple and complicated cases, and by printers.
- Split returning from new. Returning attendees need a lookup and a print, about ten seconds. New arrivals need a form and a conversation, one to three minutes. Put them in the same line and the average becomes the worst case. Two clearly labeled stations fixes most queue problems on its own.
- Let people check in before they arrive. Pre-check-in from a phone or an emailed code turns the desk into a pickup point. For conferences, this is the difference between a badge desk and a badge line.
- Test the printers at load, not at setup. Label printers are the most common physical failure point. Print a hundred labels in a row before the event, keep a spare roll and a spare printer within reach, and make sure a volunteer knows how to change one.
- Scale stations to peak, not to attendance. Sixty percent of your people arrive in one fifteen minute window. Size the desk for that window. A rough planning number is one station per sixty people expected in the peak window.
- Have an offline fallback. A printed roster and a pen. Venue wifi fails often enough that this should be part of the standard kit, and it takes thirty seconds to prepare.
The line is almost never the software. It is one desk trying to serve a ten-second task and a three-minute task at the same time.
The record: the part everyone skips
Attendance data has a short half-life. Collected into the same system as your people records, it answers real questions. Collected into a standalone tool, it becomes a stack of session exports nobody opens.
- First-timers who never came back. The single most actionable list any organization can produce, and it only exists if check-in writes to the person record.
- Attendance patterns per person. Someone who came weekly for a year and has not appeared in a month is a follow-up, not a statistic.
- Room and session capacity. Which sessions are consistently over or under, so next term’s schedule is based on evidence.
- Volunteer-to-attendee ratios. Required for ratio compliance in kids programs, and useful everywhere else for staffing.
- Numbers for funders and boards. Unique people served, sessions delivered, growth over time, without reconstructing a year from sign-in sheets.
This is the argument for check-in that is part of your main system rather than a separate app. In Studio Faith and Studio Events, a check-in writes to the same person record that holds registrations, giving, and communication history, so the first-timer list and the follow-up happen in one place instead of being exported and re-imported.
A setup that fits the room
Different rooms need different configurations. These three cover most situations.
| Context | Setup | Watch out for |
|---|---|---|
| Kids program | Staffed stations, matching tags, allergy flags, ratio tracking | Volunteer turnover erasing the training |
| Class or small group | Self-serve tablet or leader marks a roster | Nobody marking it, so records go stale |
| Conference | Pre-check-in plus badge pickup by last name | Peak window under-staffed, printers untested |
Whatever the setup, keep the field count at the door low. Every extra question at check-in slows the line and lowers the accuracy of the answers. Collect the detail at registration, where people have time, and use the door for identification only.
Key takeaways
- Check-in does three jobs at once. Rank safety, throughput, and the record for your context before choosing anything.
- For kids programs, matching tags, an authorized pickup list, and allergy flags on the tag are the non-negotiables.
- Split returning from new arrivals. That one change removes most queues.
- Size stations for the peak fifteen minute window, test printers under load, and keep a printed fallback roster.
- Attendance is only valuable if it writes to the person record. Otherwise it is a pile of exports nobody opens.
Common questions
Do we need a kiosk, or is a phone enough?
A phone or tablet in a volunteer’s hands is enough for most rooms under a couple of hundred people, and it is more flexible because the volunteer can move to the line rather than the line coming to a fixed point. Dedicated kiosks earn their place at high volume or where you want self-service without staffing.
How long should we keep check-in records?
Keep the aggregate attendance indefinitely, since it is your history. For records involving minors, follow your local requirements and your insurer’s guidance, which are often more specific than general data policies. Write the retention rule down and apply it consistently rather than deciding case by case.
What is the fastest way to fix a slow check-in without buying anything?
Add a second station labeled for first-time arrivals and move your most experienced volunteer to it. Most of the queue is caused by long conversations blocking short ones, and separating them costs nothing but a sign and a table.
How do we handle people who refuse to check in?
For adult contexts, accept it and count the room. For anything involving minors, it is not optional, and it helps to explain it as a custody safeguard rather than a data collection step. Framed as safety, resistance almost always disappears.
Should volunteers check in too?
Yes, and it is worth doing properly. You need it for ratios, for knowing who was in a room if a question arises later, and for recognizing service accurately at the end of the year. It also models the behavior for everyone else.
