The report comes back and it is not empty. Now what. Most volunteer coordinators have run a dozen clean background checks before they hit their first flagged one, and when it happens, the temptation is to either panic — pull the person from every rotation, quietly, without a word — or wave it off because they seem so nice and surely it was nothing. Neither is a policy. Both are just what happens when nobody decided in advance what a flag means.
This is not a legal guide, and it is not a substitute for talking to a lawyer about your state's rules or your insurance carrier's requirements. It is a plain look at how small churches sort background-check results into three piles — nothing to worry about, worth a conversation, and a hard no — so that when your report comes back with something on it, you are not deciding from scratch under pressure.
Start with what a background check actually shows you
A background check is a record of what a court, a registry, or a database has on file. It is not a character reference, and it is not a prediction. It tells you a fact happened — a charge, a conviction, a listing — and gives you dates. It does not tell you why, what changed since, or how the person feels about it now. That gap between the fact and the meaning is exactly where your judgment has to do the work the report cannot.
It helps to remember what the check is for in the first place: it is one layer in protecting the kids, students, and vulnerable adults your church serves, alongside references, interviews, and time spent watching how someone actually behaves around people. A check that comes back clean is not a green light to skip the rest of that work. A check with something on it is not, by itself, a verdict.
The findings that are usually a hard no
Some categories exist for a reason and most churches, regardless of size or denomination, treat them the same way. These are the findings where the honest answer is not “let’s talk about it” but “this person cannot serve with children or vulnerable adults, full stop”:
- Any sex-offense conviction or registry listing. This is close to universal across churches, insurers, and denominational policies. There is no recency window that changes it and no context that softens it for roles involving minors or vulnerable adults.
- Convictions for violent crimes against children. Abuse, endangerment, or similar findings involving a minor victim belong in the same category, regardless of how long ago they occurred.
- An active warrant or open case involving violence or abuse. You do not need a conviction to pause someone from serving with kids while a serious open matter is unresolved.
These are not judgment calls your volunteer coordinator should be making alone in the moment. They are the reason a written policy exists — so the decision was already made, calmly, before a real name was attached to it.
The findings that usually warrant a conversation, not a rejection
Most flags do not land in the category above. They land somewhere messier, and messier is where a good conversation earns its keep. Consider these more carefully, in context:
- A DUI or reckless-driving conviction. Relevant if the role involves driving a church van full of kids. Largely irrelevant if the role is greeting at the door on Sunday morning.
- A single, old, non-violent offense. A theft or drug charge from fifteen years ago, with a clean record since, tells a very different story than the same charge from last year.
- A financial crime for a non-financial role. Fraud or embezzlement history is a serious concern for someone counting the offering. It may be far less relevant for someone leading worship or teaching a class with no money involved.
- A charge with no conviction. An arrest that was dismissed, or a charge that never went anywhere, is not the same as a conviction, and treating it as one can be both unfair and, depending on your state, legally risky.
In every one of these cases, the report gives you a starting point, not an ending point. The conversation — asking the person directly, in private, what happened and what has changed — is where you actually learn something the paperwork cannot tell you.
Match the finding to the role, not just the person
The same result can mean different things depending on what the volunteer would actually be doing. A shoplifting conviction from a decade ago is a real concern for someone handling the offering count and a much smaller one for someone running the sound board. Before you decide what a flag means, decide what the role actually exposes: unsupervised time with children, access to cash, driving others, or none of the above.
This is also where a lot of small churches quietly overreach. If your background-check policy treats a nursery volunteer and a parking-lot greeter identically, you are either screening too little for the higher-risk role or asking too much of the lower-risk one. Building your serving schedule around what each role actually involves — not just who is available — makes this match easier long before a flagged report ever shows up.
Have the conversation before you have the policy debate
When a flag lands on your desk, the instinct is to research the charge, look up the statute, and decide from your chair. Do the conversation first. Tell the volunteer, plainly, what the report showed and ask them to explain. People are often more forthcoming than coordinators expect, especially about something they already know is on their record. What you hear in that conversation — remorse, growth, a story that matches the paperwork or doesn't — usually matters more than the charge itself.
This conversation should happen in person or by phone, never by text or a group email, and it should be had by someone with the standing to make the call, not whoever happened to open the report first. If your church is small enough that the same one or two people run both children's ministry and serving assignments, that overlap is worth naming so the hard conversations do not always fall on the most tired person on the team.
Write the policy down before you need it
The single biggest predictor of a church handling a flagged background check well is whether they had already decided, in a calm month with no name attached, what their hard-no list looks like and what gets a conversation. A one-page policy — agreed on by your elders or board, not improvised by one volunteer coordinator under pressure — does more good than any individual decision you will make in the moment.
That policy does not need to be long. It needs to name the categories above, say who makes the final call, and say how the decision gets recorded — a status, a date, and nothing more. What it should not contain is a running narrative of every volunteer's history. Keep the reasoning in the conversation and the paperwork sparse.
Keep the record simple and the access narrow
Once a decision is made, most churches only need to track a status — cleared, held, or under review — next to a date, alongside whatever roles that status affects. In SundayBridge, that shows up as a background-check alert on the serving dashboard: a flag a coordinator can see when scheduling, without the underlying report living in a shared spreadsheet or a group chat where it can leak.
Who can see that flag matters as much as what it says. Keep it to the one or two people who need it to make scheduling decisions, not the whole team. For more on drawing that line — what belongs in a shared directory and what does not — it is worth reading alongside this one, since the same instinct that overshares a phone number can overshare a background-check result.
What to do when you are genuinely unsure
Some results will not sort cleanly into either pile. When that happens, slow down rather than guess. Ask the volunteer directly. Ask what the role actually requires. If the finding involves anything close to violence, abuse, or minors, involve your board or insurance carrier rather than deciding alone. And if a report seems off — a name that does not quite match, dates that do not line up — treat it as a data problem to verify, not a character problem to judge, before you act on it either way.
A church of 150 people with 20 active volunteers will run a background check on most of those 20 at some point, and statistically most will come back clean. Building your process around the rare flag, instead of treating every volunteer as a suspect until proven otherwise, is what lets you take the genuine flags seriously when they show up.