VBS registration is only the beginning. Plan the whole day.

Start with one family, then give every child a separate record.

Picture a parent arriving with three children. One is in preschool, one is finishing second grade and one is old enough to help. A single “family registered” row tells the welcome desk very little. Three unrelated forms make the parent repeat everything. Neither is a good starting point.

We would connect a household record to individual children. Shared contact information belongs with the family; each child keeps their own program enrollment, group assignment and attendance history. An emergency contact and an adult authorized for pickup may be different people. The system should preserve that distinction.

Keep the form focused: the child’s name, the age or grade information used for placement, the responsible adult’s contact details, pickup permissions and the information your team actually needs to care for that child. Handle medical and accommodation details through an appropriately restricted process. A public roster is no place for them.

This is not an invented category of software. Planning Center’s children’s ministry documentation describes connecting event signups with assigned VBS crews and recording drop-off and pickup. The practical question is whether an existing tool fits your program and whether someone has configured it around your procedures.

“Sort by age” sounds simple. Decide what it means first.

Are groups based on age on the first day of camp, grade just completed or grade being entered? Those rules can place the same child in different groups. Choose one, explain it on the form and keep the rule consistent.

A useful assignment connects the child to a program session, a named group, its room or meeting point and a responsible leader. Capacity should be an explicit setting. A placement rule can suggest a group, but a coordinator needs a way to review exceptions without quietly changing the underlying family information.

Separate the leader’s view from the coordinator’s view. A leader needs a usable roster and the approved care information relevant to their responsibilities. They do not automatically need every family’s full record, donor history or unrestricted exports.

For a week-long VBS, enrollment and attendance must also remain separate. Registering for all five days does not mean a child arrived on Tuesday. Moving to another activity group should not erase where the child was assigned earlier.

Use QR codes for lookup. Define the handoff separately.

There are at least three different QR codes people may mean: a public link to the registration page, a family check-in credential and a pickup credential. They should not be treated as interchangeable. A flyer code can be public. A family credential must not expose a child’s record to anyone who happens to scan it.

For a custom system, our starting design would use a random code that only the authorized system can look up and that staff can cancel if needed. We would avoid putting names, birthdays, phone numbers or medical details directly into the QR payload. A lost phone or shared screenshot needs a documented response.

Then define the actual attendance steps:

1. Registered: the enrollment is accepted; the child has not necessarily arrived.
2. Checked in: staff records the arrival for this session.
3. Received by the group: the leader confirms the child reached the assigned group, if your procedure requires this checkpoint.
4. Checked out: staff follows the authorized-pickup procedure and records the handoff.

A scan does not establish identity or custody by itself. Planning Center describes matching child and parent security labels before pickup. Your organization still needs its own approved rules for verifying adults, missing credentials, disputed pickup and escalation to the responsible coordinator.

Likewise, a roster shows recorded events, not a child’s live physical location. Software supports supervision; people still supervise. If a leader needs a current headcount during a room change, decide who confirms it and when.

Test the awkward moments before opening day.

A smooth demonstration with one pretend child is not enough. Rehearse siblings arriving together, a walk-in family, a full group, a late pickup, a duplicate scan and a child whose placement needs correction. Test what happens when Wi-Fi, a device or a label printer stops working. A controlled paper fallback needs an owner, limited personal information and a reconciliation step when service returns.

The FTC’s data-security guide recommends understanding what personal information is held, limiting it to what is needed and restricting access. For a camp project, we translate that into a data inventory, role decisions and an agreed retention plan. Those are design decisions to settle before importing last year’s spreadsheet.

For a small, straightforward VBS, a dedicated service may be enough. MyVBS describes free registration and group-management tools, including age or grade sorting and volunteer assignments. Custom work becomes useful when your household relationships, sessions, permissions or existing systems do not fit the standard workflow.

NONPROFIT.SYSTEMS can scope registration pages, family records, placement rules, leader views, QR workflows and reporting as one connected project. We work from Boca Raton with churches and program teams across South Florida. The same planning applies to community camps, after-school programs and enrichment providers. We agree on the features and operating procedures before building; a custom system is not an off-the-shelf safety certification.

Bring your registration form, a sample group list with personal information removed and the three situations your team finds hardest. That is enough to start a useful review. If staffing is the bigger issue, read our guide to volunteer registration and scheduling.