Most church background check policies are written for the easy case. They describe who needs a check, how often, and which provider to use. Then they stop, right before the paragraph that actually matters: what do you say to the person who does not clear it. That is the sentence nobody wants to draft in advance, so it gets improvised in the moment, usually by whoever is standing closest when the report comes back.
Improvised is where policies go wrong. The volunteer coordinator who recruited a warm, willing grandmother for the nursery does not want to be the one reading her a denial. The elder who has never done this before reaches for language that is either too harsh or too vague to hold up if anyone ever asks what the church actually said. Writing the wording down now, while no specific person's name is attached to it, is what makes the actual conversation survivable for everyone in the room.
Why this paragraph gets skipped
It is easier to write a policy about process than about people. Rules for who needs a check and how often to renew it are administrative and impersonal to draft. The denial paragraph is not. Whoever writes it has to imagine a real face — a longtime member, a visitor eager to finally get plugged in, a friend of a friend — sitting across the table hearing “no.” That is uncomfortable to think about in the abstract, so most committees write around it and hope the moment never comes.
It always comes. A church of any size that runs checks consistently will eventually get a result that does not clear. If the wording was never written down, the person delivering it is left choosing between two bad options in real time: say too much and expose the church to a defamation claim or a broken confidence, or say too little and leave someone confused, hurt, and suspicious that something worse is being hidden from them.
What the check actually tells you
A background check is not a verdict on someone's character. It is a record search against a specific role's risk — usually weighted toward offenses against children or vulnerable adults if the role involves them. Your policy should say, out loud, what the check screens for and what it does not. That single clarifying sentence does more to keep a denial letter calm and defensible than anything else in the document.
It also means your policy needs a named standard for what disqualifies someone from a given role, decided before any specific case, not invented afterward to fit whatever the report happens to show. Without that standard, every denial looks like a judgment call the church made about one particular person — which is exactly the impression a good policy exists to avoid.
The wording that holds up
A denial paragraph that is both kind and legally sound tends to share the same shape:
- State the fact, not the finding. “The background check for this role did not clear” says what happened without repeating what was found.
- Name the standard, not the person. “Our policy requires a clear check for roles serving children” ties the decision to a rule that existed before this case, not to a judgment about someone's worth.
- Leave a door open where one exists. If your policy allows an appeal or a different role, say so in the same conversation, not as an afterthought weeks later.
- Keep it short. A long explanation invites questions you cannot answer without disclosing what should stay private. Three or four sentences, delivered in person or by phone with a brief follow-up note, is enough.
What the wording should never do is speculate, apologize for the policy itself, or promise a reconsideration that isn't actually on the table. Certainty, even in a hard message, is kinder than a conversation that sounds like it might be renegotiated the following week.
Who delivers it, and how
Decide this in the policy, not in the moment. The person who recruited the volunteer is almost never the right messenger — that relationship has to continue after the conversation, at the same Sunday potluck and the same small group. A staff member or a named background-check coordinator, someone whose role is specifically to handle these results, keeps the tone consistent from case to case and keeps the recruiting relationship untouched by an outcome that coordinator did not create.
The delivery should be in person or by phone, never by a mass email or a form letter that could be read by anyone else on staff. Write a template for the coordinator to use as a script, not a document to be handed over. If a written note follows, it restates the same three or four sentences and nothing more.
Building in a real appeal
A policy with no path for reconsideration invites people to go around it, quietly, through a personal favor from someone on the team. A policy with a named appeal step — who reviews it, on what evidence, within what timeframe — gives everyone, including the volunteer, somewhere honest to take a disagreement. It does not have to be elaborate. A single sentence naming who hears an appeal and how long they have to respond is enough to close the loop your improvised version left open.
This is also where the difference between roles matters. A denial from serving in the nursery is not the same conversation as a denial from counting the offering, and your policy should be honest that the standard, and the appeal, can differ by role without pretending every “no” carries the same weight.
What happens to the paper afterward
Decide, in the same policy, who keeps the result, for how long, and who else ever sees it. A background check report is not a document for the ministry leader's binder or the church office filing cabinet where anyone with a key can find it. Name one keeper, a retention period, and a destruction date, the same way you would for any other sensitive personnel record.
This is also the part of the policy most churches never revisit once the check clears, which is exactly backwards. The cleared results sit quietly and rarely cause harm. It is the small number of denials that need the clearest handling, because those are the files someone could later be asked to produce, explain, or defend.
Fitting this into how you actually run serving teams
None of this wording works if nobody notices when a check has not come back, or if the follow-up quietly falls to whoever remembers. SundayBridge surfaces background-check status as an alert on the serving-teams dashboard, so a check that has not cleared, or has not been run at all, shows up next to the role it applies to instead of living in a separate spreadsheet someone has to remember to check. It does not run the check or write the letter for you — the wording above is yours to keep and use — but it keeps the status visible so the conversation happens on time instead of after someone has already served three Sundays.
If your serving teams already feel thin, the temptation in a denial moment is to look the other way because you need the hands. That is exactly the moment the written policy is for: it takes the decision out of a single tired volunteer coordinator's hands and puts it where it belongs, in a standard your church wrote down before anyone's name was attached to it. For the wider question of keeping serving teams staffed without running people into the ground, see serving without burnout, and for the mechanics of getting the right people into the right slot each week, see scheduling volunteers in a small church.
Write it before you need it
The churches that handle a denial well are almost never the ones with the most experience — they are the ones who wrote the wording down on a quiet Tuesday, before a specific face was attached to the decision. Draft the paragraph now. Name the messenger now. Decide the appeal now. When the report comes back and does not clear, the only thing left to do is follow what you already wrote, calmly, to a person who deserves a clear answer instead of an improvised one.
The same discipline applies to every record a serving team touches, not just the hard ones — see building a church directory your team trusts for how the underlying people records should hold up under the same kind of scrutiny.