By the second morning of vacation Bible school, the sign-up sheet from registration night and the clipboard at the door have already drifted apart. A kid who signed up for all five days is home sick on Tuesday. A neighbor kid shows up Wednesday who was never on the original list. A grandparent calls to say their grandson is coming Thursday only. None of this is unusual. What is unusual is a church that can answer, at 9:05 on any given morning, exactly who is in the building right now — without someone flipping through three different pieces of paper to find out.
The problem is rarely the volunteers. It is the number of lists. Once registration lives in one place and Tuesday's check-in lives in another, the two start disagreeing within a day, and disagreement is exactly what you cannot afford when a parent asks whether their child made it to craft time.
VBS is also, for many small churches, the single busiest week of the children's ministry calendar. A Sunday morning has one service, one set of teachers, one set of expectations. A VBS week has five mornings in a row, a rotating cast of volunteers who each show up for a shift or two, and a kid count that can shift day to day for reasons that have nothing to do with the program — a soccer game, a cold, a grandparent visiting. That volume is exactly why a loose system that works fine on an ordinary Sunday starts to show cracks by Wednesday of VBS week.
Registration is the list, not a snapshot
Treat VBS registration as one running list that gets updated all week, not a one-time form you fill out and then forget. When the sign-up sheet is treated as a snapshot — printed Sunday night and never touched again — every change that happens during the week (a new walk-up, a canceled day, a corrected phone number) has to live somewhere else. That somewhere else is usually a sticky note, and sticky notes are how kids get missed.
The fix is simple to say and only slightly harder to do: one list, kept current, that both the registration table and the morning check-in station are looking at. If a family adds a day on Tuesday afternoon, that information needs to reach Wednesday morning's list without anyone re-typing it.
What actually needs to be on the list
VBS registration does not need to be elaborate. It needs to be complete enough that a crew leader can act on it without a follow-up phone call. At minimum:
- Child's name and grade or age group
- Which days the child is attending — not assumed to be all five
- A parent or guardian name and a phone number that will actually be answered that week
- Any allergy, medical note, or pickup restriction the crew leader needs to see at a glance
Everything past that — t-shirt size, dietary preference, photo release — is worth collecting if it is easy, but it should never slow down the line at the door. The morning of VBS is not the time to discover your registration form has fourteen required fields.
It helps to think about who actually reads each field, and when. A crew leader assigning a child to a small group needs the grade and the day list in front of them at 8:45am, not buried three screens deep in a form they'd have to search. A parent picking up at noon needs to be able to show up, say a name, and have the volunteer at the door recognize it instantly rather than flip through pages looking for a match. If a field on your registration form does not serve one of those two moments, it is probably nice-to-have rather than need-to-have, and it is fair to cut it or push it to a separate, optional form.
The 9am question, answered without a search
The single test of whether your VBS registration system is working is this: at 9am on any morning of the week, can one person say, within a couple of minutes, who is here today, who was expected and did not show, and who showed up without being on the list? If answering that question means cross-referencing a printed roster against a clipboard sign-in sheet against a group text from a parent, the system has already failed, even if every kid is safe and accounted for.
A church of sixty kids running five-day VBS is really running five separate headcounts off one registration base. The daily number will not match the weekly signup total, and it should not — a sick day, a Friday-only kid, a last-minute add are all normal. What matters is that the gap between “who signed up” and “who is here” is visible in one glance rather than reconstructed by memory.
Run the arithmetic once and it is easy to see why a glance matters more than a total. Say sixty kids registered for the week, but attendance across five days actually looks like fifty-two, fifty-five, forty-eight, fifty-eight, and forty-four — a normal spread for a week that includes a Wednesday illness bug and a lighter Friday. None of those five numbers is wrong, and none of them is the “real” headcount. The real headcount is whichever one matches today, and the only way to know that without guessing is to check the actual list each morning against who walked in the door.
Walk-ups are not an exception to plan around
Every VBS gets a handful of kids who were never in the original registration — a cousin visiting for the week, a neighbor a family brought along on a whim. The temptation is to handle these on a separate sheet because they came in sideways. Resist it. A walk-up is just a late row on the same list, with the same fields filled in: name, days attending, a contact number. Keeping it on a second sheet is how a church ends up with two headcounts that need to be added together by hand every morning, which is exactly the kind of manual reconciling that produces errors on the day it matters most.
The headcount drives more than attendance
A daily VBS headcount is not just a record for the files — it is the number that decides how many volunteers you actually need standing in the room that day. If ten crew leaders showed up Monday to cover fifty-eight kids, and Wednesday's number drops to forty-four because of a stomach bug going around a local school, that is useful to know before you send a text asking for two more volunteer shifts you did not need. The same logic that makes a volunteer schedule work on an ordinary Sunday applies here: staffing decisions are only as good as the headcount they are based on, and a headcount that is a day stale leads to either scrambling for help or over-staffing a slow morning.
The same number also drives food and supply counts — snack quantities, craft materials, name tags. A church that orders snacks off the week-one registration total and never checks the daily number again either runs short on the biggest day or throws away food on the smallest one. Neither is a disaster, but both are avoidable with a number that is five minutes old instead of five days old.
One name owns the morning count
Decide in advance whose job it is to check the daily headcount, and make it the same person every morning if you can. Ambiguity about who is responsible for the count is how a real gap — a child registered for today who never arrived — goes unnoticed until pickup time. This does not need to be complicated. It needs to be someone's named job, done the same way each day, against the same list.
SundayBridge keeps gatherings and their registrations in one place, so a VBS week is one event with one running list rather than a new spreadsheet for every day — and because every attendee can tie back to a household record, a walk-up kid this week is a lead for your guest-to-member follow-up next week, not just a name that disappears when VBS ends.
After the week ends, the list still matters
The value of a clean VBS registration list does not stop on Friday afternoon. It is the record that tells you which families are new to the church, which kids belong to households you already know, and who needs a note or a call in the weeks that follow. Handled well, VBS is one of the better on-ramps a small church has — but only if the names collected during the week make it into your regular records instead of staying trapped on a stack of sign-in sheets in a supply closet. The same rhythm that keeps your weekly admin work manageable — a little, consistently, instead of a lot, rarely — applies just as well to a five-day event as it does to an ordinary Tuesday.