Somebody has to run the background check, and somebody has to explain to a new volunteer why they are being asked to hand over a driver's license number to serve coffee. Both jobs are easier when you actually know what the check covers, what it does not, and why a nursery volunteer and a Sunday greeter are not the same decision.
None of this is complicated once it is laid out plainly. The confusion usually comes from churches treating “background check” as one uniform thing, when in practice it is a records search you can scope up or down depending on what a role actually touches — a child, a car, an offering plate, or none of the above.
What a background check is, in plain terms
A background check is a search of public and semi-public records tied to a person's name, date of birth, and past addresses. A screening company runs the name against county courthouse records, state repositories, a national criminal database, and usually a sex-offender registry, then sends back a report: clear, or a record found that needs a look. That is the whole mechanism. It is not an interview, not a psychological evaluation, and not a judgment call — the judgment call is yours, after you see what the search turned up.
The accuracy of the search depends entirely on the names and addresses you give it. A common name with an incomplete address history can produce a report that misses something, or one that flags a different person with the same name. This is why the intake form matters as much as the check itself — full legal name, every address for the last seven to ten years, and an accurate date of birth are what make the search worth running at all.
Why the risk of the role decides the depth of the check
A church of 150 does not need to run the same screening on every volunteer. What changes the calculus is access: unsupervised time with a child, driving a student somewhere alone, or handling cash and checks before anyone else counts them. A greeter, a bulletin folder, or someone who sets up chairs on Saturday carries none of that exposure, and a full criminal background check on that role is more theater than safeguard.
Where it earns its cost is anywhere a volunteer is alone with a child, a student, or money that has not yet been reconciled. That is nursery and kids' ministry, students' ministry, anyone driving a church vehicle or a personal car with kids in it, and anyone who counts, deposits, or has access to the offering before a second person verifies it. Most denominational insurance policies already require checks for the first category and strongly recommend them for the second — worth confirming with your carrier rather than guessing.
A quick way to sort roles
- Unsupervised access to a minor — nursery, kids' church, student ministry, driving kids anywhere. Check, and recheck on a schedule.
- Handles money before it is reconciled — counting the offering, making the bank deposit, holding a church debit card. Check, and pair it with a two-person counting rule regardless.
- Neither — greeting, ushering, tech booth, hospitality. A check is not wrong here, but it is not where your screening budget and volunteer patience are best spent.
What the report actually contains
Expect three layers in a typical church screening package: a county criminal records search for every county the person has lived in, a statewide search, and a national criminal database search that acts as a wider net. Most packages built for churches add a national sex-offender registry check by default, since that is the specific risk kids' ministry is trying to guard against. Some churches add a motor-vehicle records check for anyone who will ever drive a student or a child, since a suspended license or a pattern of moving violations is relevant there even with a clean criminal record.
What it does not contain is worth saying out loud, because volunteers sometimes assume otherwise and get anxious about the wrong thing. It is not a credit check. It does not pull social media history. It is not a reference check or a character assessment — a background check tells you what is on the public record, not whether someone is a good Sunday-school teacher. Those are separate questions, and a church that skips the informal reference conversation because “the background check came back clean” has skipped a real step, not a redundant one.
What a clean report does not tell you
A background check only surfaces what already resulted in a record. It says nothing about someone who has never been caught, never been charged, or whose concerning behavior has not yet crossed a legal line. This is not a flaw in the tool; it is the nature of a records search, and every reputable screening company will tell you the same thing if you ask. Treat the check as one layer of a safety plan, not the whole plan.
The layers that catch what a background check cannot are procedural: never one adult alone with a child in a closed room, visible windows or open doors in every classroom, a consistent check-in and check-out process so a parent always knows who has their kid, and a simple way for anyone — staff, volunteer, or parent — to raise a concern that gets taken seriously even when nothing shows up on paper. A clean background check plus none of those habits is a weaker safeguard than a held check plus all of them.
How often to run it again
A background check is a snapshot, not a subscription. Something on someone's record two years after their last check will not show up until you run it again. Many churches settle on every two to three years for volunteers in sensitive roles, sometimes tied to whatever their liability insurer requires. Write the interval down somewhere it will survive a change in who runs children's ministry, because the most common failure is not a bad decision — it is nobody remembering the last check was three years ago.
On SundayBridge, a background-check alert sits on the serving-team dashboard alongside each volunteer's roles and assignments, so a check coming due or a hold pending review does not get lost in a spreadsheet nobody opens between recruiting seasons. It is a flag that something needs a look, not a place to store the report itself — the actual document stays with your screening provider, where consumer-reporting rules say it belongs.
What to do when something comes back
A record on the report is a reason to slow down, not a reason to automatically say no. A twenty-year-old misdemeanor and an unresolved charge from last year are not the same conversation. Loop in the ministry leader whose role is affected, and for anything ambiguous, your screening provider's guidance or, in a genuinely hard case, a lawyer familiar with your state's rules. Whatever you decide, tell the volunteer the truth: what was flagged in general terms, what happens next, and who is making the call. A volunteer who is quietly never scheduled again, with no explanation, tends to assume the worst and tell other people about it.
Keep the decision itself — held, cleared, cleared with conditions — separate from a paraphrase of the record. “Held from nursery pending review, checked March 2025” is a fact your future self needs. A summary of what the record said is a liability with no ministry value, and it belongs nowhere a scheduling volunteer might stumble across it. This is worth its own conversation with your leadership team; see keeping background-check results private while still useful for how to draw that line.
Building it into how volunteers get scheduled
The check works best when it is not a separate errand bolted onto recruiting. If a role requiring a check is the same role that shows up in your volunteer scheduling process, the two can move together: nobody gets slotted into nursery until the check clears, and the person doing the scheduling can see that status without asking around. That single habit — check status visible right where the scheduling decision gets made — closes most of the gap between having a policy and actually following it every time.
It also helps to fold the check into the same conversation as everything else you track about a volunteer — their directory record , their serving history, whether they are showing early signs of burnout. A background check is one fact among many about a person who is giving you their Sunday mornings. Treating it as a single isolated gate, disconnected from everything else you know about them, is how churches end up with a binder of old reports nobody has looked at since the day they were filed.
Setting the policy once, in writing
The churches that do this well are not the ones with the most expensive screening package. They are the ones who wrote the policy down once: which roles require a check, which provider runs it, how often it repeats, who reviews a flagged result, and what gets recorded versus what stays with the provider. A church of 80 with two kids' ministry volunteers and a church of 250 with thirty need the same policy in kind, just scaled in volume. Decide it in a calm meeting, not while staring at a flagged report an hour before Sunday, and put it somewhere the next person running children's ministry can actually find.