People

What emergency contact info a kid's record actually needs

Not every field on a children's intake form earns its place — here is the short list that does.

7 min read

Ask AI · in the $19/mo plan

Ask your own records a question. Who visited in the last month, and did anyone follow up?” — answered from the records you already keep. It reads your church and no other, and it can't invent a number.

10 questions a month included · no AI add-on to buy

A children’s intake form tends to grow the way a junk drawer grows — a field gets added after one bad Sunday, then another after a different bad Sunday, until the form is three pages long and nobody fills it out completely anymore. Emergency contact information is the part of a kid’s record that matters most in the moment it is needed and is most likely to be stale when that moment arrives.

The good news is that the actual list of fields worth keeping is short. Most of what ends up on a long intake form is either duplicated somewhere else, rarely used, or a nice-to-have dressed up as a necessity. Here is what earns a place on a child’s record, and what does not.

The single most important field is not a phone number — it is a name, or a short list of names, of adults authorized to pick the child up. This is the question a volunteer actually faces at the end of the hour: a man they do not recognize is standing at the classroom door saying he is here for Micah. A phone number does not answer that. A name on a list does.

For most families this is simple: mom and dad, maybe a grandparent. For a smaller number of families it is genuinely complicated — joint custody, a restraining order, a grandparent raising the child instead of a parent. Those are exactly the situations where a clear, current authorized-pickup list protects both the child and the volunteer who would otherwise have to make a judgment call under pressure.

Then the phone number that actually gets answered

Every record has a parent’s phone number somewhere. The mistake is assuming that number is the right one to call in an emergency. Plenty of parents silence their phone during the service, or hand it to a spouse to hold during the sermon, or simply do not hear it over the sound system. Worth asking directly: “if we needed you in the next five minutes, what number rings loud enough for you to notice?” That is the number that belongs on the emergency contact field — it may or may not be the same number listed as the household’s primary contact.

If your church uses a check-in process at the classroom door, this is the moment to ask the question, not buried in a form filled out once a year. A parent standing in front of you will tell you the truth about which number they actually answer. A form filled out at home in a hurry usually just repeats whatever number is already on file.

A second contact for the Sunday the first one doesn’t answer

This is the field that gets skipped most often and matters most when it is needed. Parents get pulled into things — a meeting, a drive with bad signal, a phone left in the car. A second name, ideally someone who lives close enough to actually come get the child if needed, closes the gap. It does not need to be a relative. A neighbor, a family friend, another church member who knows the family — anyone reliably reachable and willing to be called.

The temptation is to list every aunt, uncle, and family friend a parent can think of. Resist it. A list of six names with no clear order is worse than a list of two names in the order to call them. Ask the parent to rank them, and keep the field short enough that a volunteer under stress can actually read it.

Allergies and medical conditions, written plainly

This is not strictly an emergency contact field, but it belongs beside one, because the two are used together in the same moment. A volunteer who is about to call a parent about a reaction needs to already know what they are dealing with. “Peanut allergy, carries an EpiPen in his backpack” is useful. A field that just says “allergies: yes” with no detail is not.

Keep this field in plain language, not medical shorthand a volunteer might misread. And keep it current — a child’s allergies and medications change more than most families think to mention, so it is worth a direct question at re-registration rather than assuming last year’s answer still holds.

What to leave off

A few fields show up on intake forms because they seem thorough, not because they get used:

  • Employer information for each parent. Nobody has ever called a parent’s workplace switchboard to reach them in an emergency. A cell number does that job.
  • A full extended-family contact tree. Grandparents, godparents, and family friends are useful as a ranked second or third contact — not as an open-ended list nobody will read in order.
  • Insurance details. These belong with the family’s own paperwork, not a church record. If a child needs medical attention, the parent or guardian handles insurance directly; the church’s job is getting them there fast, not filing a claim.
  • A physical description of the child. Rarely needed and easy to make uncomfortable. A photo on the profile, kept for identification purposes at pickup, does that job better than a written description ever will.

A shorter, well-maintained record beats a longer, stale one every time. The point of this information is not completeness — it is that a volunteer who has never met a family before can read three or four lines and know exactly what to do.

Where this lives inside a family’s record

Emergency contact fields work best when they sit on the child’s own profile, tied to the household, rather than scattered across a separate binder or a spreadsheet tab nobody remembers to open on a Sunday morning. If your church still keeps kids’ information separate from the rest of the family record, that is often the same gap covered in how households and individuals relate to each other — a child’s emergency contacts are really just another fact about the household, not a different system entirely.

SundayBridge keeps a child’s emergency contact and allergy information on their own profile inside the household, visible to whoever is checking them into a class, alongside the same engagement timeline used for the rest of the family. It is one profile, not a separate kids’ database to keep in sync.

Cleaning up what you already have

If your current records grew the junk-drawer way described above, the fix is not to redesign the form from scratch — it is to go through what already exists and trim it down to the fields above, updating phone numbers as you go. This is slow, unglamorous work, and it is exactly the kind of thing described in cleaning up a messy church database: a little bit each week, starting with the families most likely to have classroom-age kids, rather than one exhausting weekend trying to fix everything at once.

A directory the whole team actually trusts, as covered in building a church directory your team trusts, depends on exactly this kind of discipline — short, current, and reliably filled in, rather than long, thorough, and six months out of date.

A short form is a form that gets filled out

The real risk with emergency contact information is not that a field is missing. It is that the form is so long a busy parent skips half of it, or fills it in once and never updates it again. A short list — authorized pickup names, the phone number that actually gets answered, a second contact, and any allergy or medical notes in plain language — is a list parents will actually keep current, because updating four things once a year is a real task and updating fourteen is not.

Frequently asked questions

Do we need a signed release form as part of a child’s record, or is it a separate paper?
Keep the signed release as a physical or scanned document, not as a data field. A record can note that a release is on file and where, but the signature itself belongs in your paper files or a document folder, not typed into a profile. The record’s job is to tell a volunteer who to call, not to store the legal paperwork.
Should every child have two emergency contacts, or is one enough?
One is enough if that person is reliably reachable, but two is safer. The second contact matters most on the Sunday the parent’s phone is dead, in a meeting, or simply out of range. A grandparent, aunt, or family friend who lives nearby and picks up their phone is worth the extra field.
What if a family doesn’t want to list a stepparent or ex-spouse as a contact?
That is common and worth respecting. The record should reflect who the family actually wants called, not a legal roster of every adult connected to the child. If custody is complicated, a short note from the parent about who has authority to pick up the child is more useful than trying to track the whole family situation.
How often should we update emergency contact information?
Once a year at minimum, ideally at the start of a new Sunday school year or whenever a family re-registers a child for a class or event. Phone numbers change more than people expect, and a five-minute check-in with a parent once a year catches most of the drift before it becomes a problem.
Can volunteers see this information, or is it restricted to staff?
In most small churches, the people running the classroom on Sunday need to see it, because they are the ones who will use it in the moment something goes wrong. The tradeoff is that anyone who can see a child’s profile can see this information too, so it is worth being deliberate about who has access to the system at all.