Most small churches don’t skip a child safety policy because they don’t care. They skip it because nobody has an hour to sit down and write one, and because the volunteers running the kids program on a given Sunday are the same three people who set up chairs and count the offering. The policy gets treated like the thing you’ll write once things slow down. Things never slow down.
But a written child safety policy isn’t a legal formality you produce after something happens. It’s the document that keeps something from happening in the first place, and the one thing every volunteer, every parent, and every insurance company will ask to see. Here is what actually needs to be in it before you put a single volunteer in a classroom with kids.
Start with screening, not paperwork
The policy’s first job is deciding who is allowed near children at all, and that decision has to happen before someone signs up, not after they’ve already taught three Sundays. At minimum, write down:
- A minimum time in the church. Many churches require six months of regular attendance before someone can volunteer with kids — long enough for other members to have formed an opinion about the person.
- A background check, run before the first shift. Decide who pays for it, who orders it, and what disqualifies someone — write the disqualifying offenses down rather than deciding case by case under pressure.
- A reference check. A phone call to one person who has seen the volunteer around kids before, not just a character reference from a friend.
- A signed application that asks directly about any history with children and any prior findings, however uncomfortable that feels to hand someone.
None of this needs a database or a vendor contract to start. A church of 80 people with 6 kids-ministry volunteers can run this on a shared spreadsheet and a folder of signed forms — the discipline matters more than the tooling at this stage.
Write the two-adult rule down, don’t just assume it
Almost every church leader will tell you they already do this. Fewer have it in writing, which means fewer actually enforce it consistently — especially on the Sunday the second volunteer calls in sick and someone decides one adult is fine for twenty minutes. It isn’t.
The written version should say, plainly: no adult who is not the child’s parent or guardian is ever alone with a child, in a closed room, without a second adult present or visible through a window or open door. It should also say what happens when staffing falls short — combine classes, pull a volunteer from another room, or cancel that class for the week. Write the fallback plan into the policy itself, so nobody has to invent one under pressure with parents already dropping kids off.
Check-in and check-out have to be a hard rule, not a habit
A child should only be released to the adult who checked them in, or to someone that adult named in advance. This sounds obvious until you picture a Sunday with visiting grandparents, a custody situation nobody mentioned, or a twelve-year-old who wants to walk to the car alone. The policy should spell out who is allowed to pick up a child, what happens when someone unfamiliar shows up asking for one, and who has the authority to say no.
This is also where a policy and a process meet. If you’re thinking through how check-in actually runs on a Sunday morning — who staffs the table, what the handoff looks like — that’s covered separately in the Sunday check-in process guide. The policy sets the rule; the process is how you follow it every week without having to think about it.
Decide, in writing, how an incident gets reported
Every kids program eventually has an incident — a scraped knee, a bite mark, a child who says something that worries a teacher. What separates a well-run church from a vulnerable one isn’t whether incidents happen. It’s whether there’s a clear, written path for reporting them the same day.
- Every incident gets written down, even minor ones, the day it happens — not recalled from memory a week later.
- Parents are told before they leave the building, or as soon as reasonably possible if the parent has already left.
- Anything involving suspected abuse gets reported to the named child safety coordinator immediately, and from there follows your state’s mandatory reporting requirements — most clergy and many volunteers qualify as mandatory reporters, and the policy should say so plainly rather than leaving it to whoever happens to know the law that day.
Keeping a record of who reported what, and when, is exactly the kind of history a pastoral care log is built for — not for gossip, but so the information doesn’t live only in one person’s memory.
Name one owner, not a committee
A policy with no owner rots. Somebody — the kids ministry director, an elder, whoever it is — needs to be the named person responsible for running training once a year, tracking which volunteers are due for a background check renewal, and updating the document itself when something changes. Put their name and role in the policy, not just “the leadership team.” A church of 150 with 15 kids-ministry volunteers cannot track re-check dates from memory across a whole year; someone has to own the calendar.
This is one of the two places SundayBridge fits into this article, and it fits narrowly: the background-check alerts that show up on the serving-teams dashboard exist to catch the renewal date nobody remembers, not to write or enforce the policy itself. The policy is still a document your team writes and agrees to; software just keeps the dates from slipping.
Train on the policy, don’t just file it
A policy that lives in a binder in the office filing cabinet has done nothing. Every volunteer needs to read it, sign that they’ve read it, and go through a short annual refresher — twenty minutes is enough for most small congregations — that walks through the two-adult rule, check-in and check-out, and how to report a concern. New volunteers should get this before their first shift, not sometime in their first month.
If your church is also in the middle of tightening up how volunteer records and schedules are tracked more broadly, that’s worth reading alongside this: scheduling volunteers without burning out the same three people covers the staffing side that a safety policy depends on — a policy that requires two adults per room only works if you actually have two adults scheduled.
Put it in writing, then put it somewhere people will actually look
The single biggest failure mode isn’t a bad policy. It’s a good policy that exists as a Word document on one person’s laptop, unopened since the year it was written. Put it somewhere every volunteer can find it, review it once a year on a set date — not “whenever we get around to it” — and treat updating it with the same seriousness as updating your church’s bylaws.
If your church is still working out of scattered spreadsheets for volunteer records generally, not just kids ministry, it’s worth reading why churches move off spreadsheets before you build a child safety tracking system on top of the same shaky foundation. A safety policy is only as reliable as the records underneath it.
What a one-page policy actually needs
If you’re starting from nothing this week, here is the minimum. Not a finished document — a skeleton you can fill in with your own church’s names, numbers, and state requirements:
- Who is eligible to volunteer, and the minimum screening steps before their first shift.
- The two-adult rule, stated plainly, with a written fallback for when staffing falls short.
- Exactly who may check a child in and out, and what happens when that’s unclear.
- How an incident gets reported, to whom, and by when.
- Your state’s mandatory reporting language, spelled out rather than assumed.
- One named person who owns the policy, the training, and the renewal calendar.
- A review date, once a year, on the calendar — not left to memory.
None of this requires new software or a legal budget. It requires an afternoon, a named owner, and the discipline to actually run the annual review instead of letting the document sit. The churches that get hurt by this aren’t the ones with imperfect policies — they’re the ones with no policy at all, discovered only after something already went wrong.