Build a registration form for a youth lock-in, a kids’ camp, or a mission trip, and there is one field that never makes the first draft: an emergency contact. Name, age, allergy notes, maybe a t-shirt size — all of that goes in without a second thought. The field that matters most if something actually goes wrong gets added later, usually right after it was needed and wasn’t there.
It is not that anyone decides emergency contacts don’t matter. It is that a registration form gets built around the questions someone thinks to ask on a calm afternoon at a desk, and “who do I call if this child gets hurt on a hike two hours from here” is not the question that occurs to you on a calm afternoon. It occurs to you standing at a trailhead.
The field that only matters on the worst day
Most fields on a registration form matter every day — a t-shirt size gets used the week the shirts are ordered, a dietary note gets used every meal of the trip. An emergency contact is different. On a normal event it sits there unused, and it is tempting to treat unused fields as unnecessary ones. But this is the field that, on the one day it is needed, is needed urgently, by someone who does not have time to dig through a filing cabinet or call the church office and wait for someone to pick up.
That mismatch — rarely used, occasionally critical — is exactly the kind of thing that gets skipped when a form is built quickly. Nobody builds a form thinking about the worst day. Everyone should.
Why it matters more for kids’ and youth events specifically
An adult who twists an ankle at a men’s retreat can call his own spouse. A ten-year-old at a day camp cannot. The younger the participant, the more the responsibility for making the call shifts entirely onto whoever is running the event, and that person needs a name and a working phone number in front of them, not a guess about which parent’s number is current.
The same logic applies to any event where the group leaves the building: a hiking trip, a mission trip, an off-site service project, an overnight lock-in. Distance and time both work against you in an emergency — the farther the group is from home and the later it is at night, the more a five-minute delay finding the right number actually costs.
What the field actually needs to capture
A good emergency contact field on a registration form is short, not thorough. Three things earn a place:
- A name. Not necessarily the parent who filled out the form — whoever should be called first if something happens.
- A phone number that actually gets answered. Ask directly: if we needed you in the next five minutes, what number rings loud enough for you to notice? That is a different question than “what is your phone number,” and it gets a more useful answer.
- A relationship. One word — parent, grandparent, neighbor — so whoever is calling knows how to open the conversation and how much explaining they need to do.
Resist the urge to expand this into a longer intake. A registration form is filled out quickly, often on a phone, often by a parent juggling two other kids at the same time. Three fields get filled in accurately. Ten fields get half-skipped or filled in on autopilot.
Why the household record alone isn’t enough
Plenty of churches already keep emergency contact information somewhere — on a child’s intake form, in a Sunday school binder, in a household’s profile. That is good, and it should not be duplicated for no reason. But a general household record answers “who do we call, generally,” while a specific event needs to answer “who do we call this week, for this trip.” A grandmother who is the backup contact on file might be the one traveling with the family on the week of the retreat. A number that was current last September might belong to a phone that got a new number in January.
The cleanest approach is to treat the two as related but distinct: the household record is the baseline, and a registration form is the moment to confirm it is still right for this specific event, the same way you would double-check an address before mailing something important rather than trusting it was correct the last time someone asked. If your church is still working out how household and individual records relate to each other in the first place, that groundwork is covered in households versus individuals, and it makes this kind of cross-checking much easier once it is settled.
Build it into the registration, not a follow-up email
The worst version of this field is the one added after the fact — an email sent out a week before the trip asking parents to “please reply with an emergency contact if you haven’t already.” Some parents reply. Most don’t, because it arrives as one more email in a full inbox rather than a required step in the thing they were already doing.
The field belongs in the registration itself, required, right alongside the child’s name and age, so a parent cannot finish signing up without it. This is the same discipline as planning an event with a clear owner for every task — build the requirement into the process up front, rather than hoping a reminder catches everyone who slipped through.
SundayBridge keeps event registrations attached to the same gathering they belong to, in the same place as the rest of the event’s details, rather than as a separate spreadsheet a coordinator has to reconcile against the sign-up sheet. Adding an emergency contact field to that registration means it travels with the roster instead of living in a different document entirely.
What to do with the list once you have it
Collecting the field is only half the job. It needs to actually be usable on the day of the event, which usually means printed or exported to something that does not depend on cell signal or an office login. A trip leader standing in a parking lot at a trailhead cannot look anything up if the only copy lives on a computer back at the church. The whole point of collecting this information ahead of time is that it is ready before anyone needs it, in the hand of the person who will actually make the call.
A short, exported roster — name, age, emergency contact, phone number, any allergy notes — costs almost nothing to prepare and covers the one scenario where the difference between having it and not having it is not measured in convenience but in minutes.
One field, added once, used rarely, needed absolutely
Most of what goes into planning a church event pays off in smoothness — the day runs better, people feel more cared for, less falls through the cracks. This one field is different. Most events, it never gets opened. The one event it does, it is the only thing that matters. That asymmetry is exactly why it belongs on the form from the start, not the list of things added after someone wished it had been there.