Every church runs background checks a little differently, and most of the variation comes from never having written anything down. The youth pastor requires them for small group leaders. The children’s director requires them for nursery volunteers but not for the parent who fills in during the second service. Nobody requires them for the finance team, because everyone on it has been a member for fifteen years and surely that’s enough.
A background check policy fixes that, not by adding more paperwork but by deciding once, in writing, who gets checked, how often, and what happens when something comes back. The hard part was never running the check itself — it’s the conversation that happens after, when a result lands on someone’s desk and there is no agreed process for what comes next.
Start with roles, not people
A policy built around individual volunteers falls apart the first time someone new walks in the door and nobody remembers whether the rule applies to them. A policy built around roles holds up. List every serving role in the church — nursery, kids’ church, youth, greeter, usher, finance counting team, van driver, small group leader — and sort them into three tiers.
- Unsupervised access to minors or vulnerable adults. Nursery, kids’ church, youth ministry, one-on-one mentoring, home visits. These get a check before the first day of serving, full stop.
- Access to money or financial systems. Counting team, treasurer, anyone with bank or accounting login access. These get a check before access is granted.
- Everyone else in a supervised, public setting. Greeters, ushers, parking team. Many churches choose not to require a check here, or require one only after a set number of months serving. Either choice is defensible as long as it is written down and applied the same way to everyone in the tier.
This sorting exercise usually takes one meeting. It is also the meeting where you find the role nobody thought to classify — the volunteer who drives the church van to pick up kids for Wednesday night, say — and that is exactly the value of doing it.
Pick a vendor and a scope, once
Most background check vendors offer several tiers: a basic identity and sex offender registry search, a county or statewide criminal records search, and a national criminal database search, sometimes with a motor vehicle report added for anyone driving a church vehicle. A church of 120 with a nursery, a youth group, and a van does not need the same scope for every role. Match the scope to the tier you built above, and write the scope into the policy itself so a new pastor or coordinator does not have to guess two years from now.
Cost adds up faster than people expect once a church has thirty or forty volunteers across nursery, kids’ church, and youth, each due for renewal on a different schedule. Deciding the renewal interval up front — three years is common — and running checks in batches rather than one at a time as people happen to sign up keeps the cost and the admin load predictable.
Decide the disqualifying criteria before you see a result
This is the section most policies skip, and it is the one that matters most. If you wait until a result is sitting in front of you to decide whether it disqualifies someone, you are deciding under pressure, with a specific person’s face in mind, which is exactly how inconsistent decisions happen. Decide the categories in advance instead:
- Any offense against a minor, at any age of the record, is an automatic disqualification from any role involving children.
- Violent felonies within a set look-back period — ten years is a common choice — disqualify from any role.
- Financial crimes — theft, fraud, embezzlement — disqualify from finance roles specifically, with a shorter or longer look-back depending on severity.
- Everything else goes to the review committee described below, with guidance to weigh how long ago it happened, whether it relates to the role, and whether there is a pattern.
Writing this down before any name is attached to it is what makes the policy fair. It also protects the volunteer coordinator, who no longer has to be the one person deciding, alone, what a decade-old record means.
Assign a review committee of at least two
One person should never be the sole reader of a background check result. Two people — commonly the pastor and a board member, or the volunteer coordinator and the pastor — review anything that is not a clean pass or an automatic disqualification. Their job is narrow: apply the criteria the church already wrote down, note the reasoning, and record the decision. It is not their job to invent new criteria in the moment.
This is also where confidentiality has to be explicit in the policy. The result itself, and the committee’s discussion of it, stays with the committee. It does not get mentioned at the next staff meeting, and it does not get discussed with the volunteer’s small group leader, even informally. Treat it the way you would treat a pastoral care conversation — discreet by default, shared only with the people who need to know.
What happens between the check and the first Sunday
Turnaround time varies by vendor and by how common someone’s name is, but a few business days to two weeks is typical. Decide, in the policy, what a new volunteer does during that window. For nursery and youth roles, the safest default is that the check clears before the first shift is scheduled — not just requested, cleared. For lower-risk roles, some churches allow scheduling to begin once the check is submitted, as long as the volunteer is never unsupervised.
This is often the moment where a small church’s good intentions collide with its actual staffing gap. The nursery is short two people this Sunday, and a new, eager volunteer is standing right there. The policy exists so that the answer in that moment is already decided, and the person delivering it — usually the volunteer coordinator — isn’t the one who has to invent a reason on the spot.
Track it without pretending software runs the process
A spreadsheet with a name, a role, a check date, a renewal date, and a status column will get most churches through their first year. The failure mode is not the tracking method — it’s that nobody looks at it until someone asks. SundayBridge keeps a background-check alert on the serving team dashboard so a coming-due or missing check surfaces where the person scheduling volunteers already looks, instead of living in a separate file that only gets opened once a year. The actual check still runs through your vendor of choice; the software just makes sure the renewal date doesn’t quietly slide past.
If your team is still tracking this by memory and a shared spreadsheet, the same gaps that show up in every other spreadsheet-run church process show up here too — the tab someone forgot to update, the renewal date that quietly became a rumor instead of a fact.
Write the policy down and put someone’s name on it
A background check policy that lives in one person’s head is not a policy, it is a habit, and habits don’t survive a staff change. Put it in writing: the tiers, the vendor and scope for each tier, the renewal interval, the disqualifying criteria, the review committee, and who owns the tracking. Name an owner — usually whoever handles volunteer scheduling — and have the board or elders formally adopt it, the same way they would adopt a financial policy. When a new pastor or coordinator arrives in three years, the policy should still say exactly what to do, without anyone having to reconstruct it from memory.
Revisit it once a year, not once a decade
A policy adopted once and never reopened tends to drift out of date quietly — a vendor changes its tier names, a state law shifts what shows up on a records search, or the church adds a van ministry that nobody thought to add to the tier list. Put a yearly review on the calendar, ideally paired with whatever regular admin rhythm your church already runs, so the review is a fifteen-minute item on an existing meeting rather than a task that has to be remembered from scratch.