Background Checks and Volunteer Screening: What to Require Before Someone Serves
A guy shows up at church one Sunday, mentions he used to be in the military, and by the next week he's standing by the back door as part of the safety team. He's probably fine. Most people are. But "probably fine" isn't a policy, and if something ever does go wrong, the first question an insurance adjuster or a lawyer asks is simple: what did you actually check before you handed this person a role of trust?
Why This Isn't Optional Anymore
A background check used to feel like something only "serious" organizations bothered with. That's changed. Most church insurance policies now require documented screening for anyone working with children, and many carriers are starting to ask about it for general security and facilities roles too. This isn't about assuming the worst of your volunteers — it's about being able to show, in writing, that you did the basic diligence any reasonable organization would do. Skipping it doesn't just create risk; it can void coverage exactly when you'd need it most.
What a Background Check Actually Catches
A standard criminal background check searches court records for convictions — it's a real tool, but it's not a magic filter. It won't catch something that was never prosecuted, a pattern of behavior reported informally, or a problem from a jurisdiction the search didn't cover. Treat it as one layer, not the whole system. Pair it with reference checks (actually call the references, don't just collect names) and a simple application that asks directly about any history relevant to the role. None of this is about distrust — it's about building a few independent checks instead of leaning on a single one.
Who Actually Needs One
If your church only requires checks for the people formally labeled "security," you're leaving gaps. Ushers and greeters often have more unsupervised contact with vulnerable people — including children wandering toward a restroom or an older member needing help to their car — than the person standing at the door with a radio. Nursery and kids' ministry volunteers should be non-negotiable. Facilities and maintenance staff who have keys and alone-time in the building belong on the list too. The rule of thumb: if the role involves access, authority, or unsupervised contact, it gets screened.
A One-Time Check Isn't a Policy
The single most common gap safety reviewers find isn't missing checks — it's checks that were done once, years ago, and never repeated. A clean record at onboarding tells you nothing about the five years since. Re-verify annually at minimum, and treat it the same way you'd treat a certification that expires: build a renewal date into whatever system you use to track volunteers, not into someone's memory.
Make the Process Feel Normal, Not Accusatory
How you introduce this matters as much as doing it. Frame it as a standard step every volunteer goes through — not a hurdle aimed at the one person who raised a question. "Everyone on our team completes this, including staff" lands very differently than singling someone out. Most people respect an organization that takes its own standards seriously, especially around children.
Track It Somewhere You'll Actually Look
A background check that gets filed in a drawer and forgotten protects no one. Keep a simple running list — who's current, when their next renewal is due, who's overdue — and check it on a schedule, not just when someone brings it up. The actual check takes a few minutes and a small fee. The habit of keeping it current is what makes the whole thing worth doing.
None of this requires turning your church into a corporate HR department. It requires deciding, once, that trust and verification aren't opposites — and then building a routine simple enough that your team will actually keep up with it.