Church HR, Staffing & Child Safety

Re-Screening Existing Volunteers Without Offending Them

Published 2026-08-16 · Church HR, Staffing & Child Safety

Short answer: announce it to everyone at once, screen the pastor and the board first, and frame it as a standard the church now holds rather than a question about any individual. Give a single deadline, make the process identical for all, and never run it quietly on a few people. Selective screening is what causes offense, not screening itself.

The board adopts a child safety policy. It's a good policy. Then somebody works out what it means in practice: sixty-one people currently serve with children, and thirty-eight of them have never completed an application, because they were already serving when the church started asking.

Several of them have taught the same class for a decade. One of them is the treasurer's mother.

This is the moment most churches stall. The policy sits adopted and unapplied, because nobody wants to be the person who asks Marjorie for a background check.

Here's the thing. Deciding to rescreen church volunteers means applying the volunteer application to people who were already serving when the church adopted one. It's much less awkward than it looks, and the awkwardness is almost entirely a function of *how* you do it.

Why offense happens

Not because people were asked. Because of one of these four:

It was selective. Three people were asked and forty weren't. Now those three know something you haven't said out loud.

It was quiet. A private request feels like an investigation. A congregational announcement feels like a policy.

Leadership exempted itself. Nothing sinks a screening rollout faster than a pastor or board member who didn't complete one.

No reason was given. People fill silence with the worst available explanation.

Fix those four and the objection rate drops to near zero. Churches that run this well are routinely surprised by how little pushback they get.

The sequence that works

1. The board adopts it, and it's minuted. This makes it a church standard rather than one leader's initiative. It also means no volunteer is being asked by a person; they're being asked by the church.

2. Leadership goes first. The pastor, the staff, the board and the ministry leaders complete applications and screening before anyone else is asked. Then say so when you announce it. "The board and I completed ours in January" ends most of the conversation before it starts.

3. Announce it to everyone at once. From the front, in the newsletter, and in a direct email to every person in scope. Same message, same day.

4. Give one deadline for everyone. Six to eight weeks is comfortable. A deadline creates a group event rather than a series of individual requests.

5. Make it easy. An online form, a table staffed after each service for two Sundays, someone available to help with the parts people find fiddly. Friction is the main reason files stay incomplete, well ahead of objection.

6. Track it and follow up individually only at the end. Most people complete it in the first fortnight. Chase the remainder quietly and personally, and assume forgetfulness rather than resistance, because that's nearly always what it is.

7. Put the cycle in the policy so this is the last time you run it as a project.

The announcement, in plain words

Say four things. Don't over-explain.

Our board has adopted a child safety policy, and part of it is that everyone who serves with children or youth completes an application and a background check. It's the same process for everyone, renewed every three years.

The staff and the board completed ours last month. Now we're asking everyone else, including those of you who have served faithfully for many years.

This isn't a question about anyone here. It's the standard we're holding as a church, and part of the point is that it protects the people who serve as much as the children.

Forms are at the table in the foyer and online. Please complete yours by the end of March. If you've got any question about it, come and ask me directly.

That last line matters. Make yourself available and most people never take it up.

A worked rollout

A church with 61 people in scope, running an eight-week rollout:

• Week 0: board adopts the policy; pastor, three staff and seven board members complete theirs. 11 files done.
• Week 1: announced from the front, in the newsletter, and by email to all 61. Table staffed after both services.
• Weeks 1 and 2: 34 completed. The first fortnight always carries most of it.
• Weeks 3 to 5: 12 more come in from reminders. Running total 57.
• Week 6: 4 outstanding. Personal conversations. Two had genuinely forgotten, one needed help with the online form, one wanted to understand what happens to their information.
• Week 8: 60 of 61 complete. One person decided not to continue in a children's role, for reasons unrelated to the screening, and moved to the hospitality team.

That last outcome is normal and it isn't a failure. Some people were serving out of obligation, and the process gives them a natural exit.

The four objections, and honest answers

"Don't you trust me?" "It isn't about trust, and if it were about trust we wouldn't have started with the board. It's a standard we apply to everyone, so nobody has to be judged individually. That's the whole point of it being a rule."

"I've served here for fifteen years." "You have, and that's exactly why it matters that you're included. If the people who've been here longest are the ones we skip, the standard has a hole in it in precisely the place it's hardest to explain."

"What happens to my information?" Answer specifically: who runs the check, what data is collected, who sees the result, where it's stored, how long you keep it. Vagueness here is what makes people uneasy. If you can't answer, work it out before you announce. Some of it isn't optional anyway: where a screening company runs the check, the person has to be told in a standalone written disclosure and has to authorize it before it happens (FTC, Background Checks: What Employers Need to Know).

"Is the church paying for this?" The church pays. Always. Asking volunteers to fund their own screening is a small saving that costs you participation and goodwill, and it turns a church standard into a personal expense.

What to do if someone refuses

First, find out what the refusal actually is. Most are practical: privacy worries, difficulty with the form, a bad experience elsewhere. Nearly all of them resolve in one conversation.

If it's a genuine refusal, the answer is the same for everyone and should be stated calmly. They may serve anywhere that doesn't involve access to minors. Not a punishment, not an accusation, and not negotiable. Offer them a real alternative role and mean it.

If a refusal comes from a long-standing or influential member, expect the board to be asked to make an exception. This is why board adoption at step one matters. The answer is already written down.

What to do if something comes back

Decide the standard before you run the first check, not while you're looking at a result about someone you know.

Have written categories. One tier disqualifies absolutely: anything involving minors, sexual offenses, violence. The other is considered in context, weighed against the role, the recency and the pattern. That second tier is doing the same work federal employment guidance describes when it asks whether a criminal record actually bears on the duties in question (EEOC, Pre-Employment Inquiries). Apply both identically to the long-standing member and the newcomer, and what to do when a check comes back with a hit walks the sequence in full.

Give the person the chance to respond; records contain errors and identity mix-ups happen. There are also legal obligations attached to using consumer report information in a decision, and they vary by jurisdiction: at a federal level that means a written authorization before the check, a notice with a copy of the report before the decision is final, and a chance to dispute an error with the agency (FTC, Background Checks: What Employers Need to Know). Follow your provider's process, and if you're unsure what applies to you, ask a licensed attorney once rather than improvising.

Write the decision and the reason in one line. Keep it confidential.

Then draw the hard line: a *disclosure or allegation about conduct with a child* isn't a screening decision at all. That goes immediately to the authorities your law requires and to counsel. Don't investigate it internally first. Know before the rollout which agency that is and what your state's definition of abuse and neglect covers, because that is set by statute rather than by your policy (Child Welfare Information Gateway, Definitions of Child Abuse and Neglect).

How churches get this wrong

Starting with the awkward cases. Start with leadership; the awkward cases become easy once everyone can see the standard is universal.

Running it as a whisper campaign. Two people asked in private, others not. This is the single biggest cause of hurt feelings.

No deadline, so it runs for fourteen months and never finishes.

Charging volunteers for their own checks.

Doing it once. Without a stated renewal cycle you'll be running this same project again in eight years, with the same discomfort. Put the interval in the policy and run it from a list, not from memory.

Re-screening but never re-collecting the application. Address history changes. So does the answer to the direct conduct question. A renewal is a short form, not just a new database search, and the questions the application must ask are worth re-asking.

Make it a cycle, not an event

Once the backlog is cleared, this becomes routine:

• Applications and checks on a stated interval. Every two or three years is common. Each renewal check is a new report, so confirm your original authorization was written to cover repeat checks rather than assuming it was (FTC, Background Checks: What Employers Need to Know).
• Run from a dated list, in one batch, at the same time each year.
• New volunteers screened at onboarding, with references actually called using a reference-check script.
• A short renewal form rather than the full application, unless something has changed.

Run as an annual batch of a dozen files, this stops being a project and becomes fifteen minutes of admin.

Common questions

How often should we re-screen?

Every two or three years is the common standard. Consistency matters more than the exact interval. A church that re-screens reliably every three years is in a better position than one that intended to do it every two and never did.

Do we re-check people who have moved to a different role?

Yes, if the new role carries greater access: setup crew to teaching, occasional helper to overnight trip leader. Re-check on role change regardless of where they sit in the cycle.

Should we re-screen board members?

Yes, and it's the easiest place to start. A board that has screened itself has already answered the hardest objection it will face.

What if a long-standing volunteer is offended anyway?

Some will be, and a small number will stay offended for a while. Be warm, be consistent, and don't make an exception to resolve it. An exception granted under social pressure is the one that gets asked about later.

The discomfort is short and the gap is long

The awkward stretch is about six weeks. The gap you close lasts as long as the church does.

Announce it to everybody, screen the leadership first, give one deadline, and then put it on a cycle so you never have to run it as a project again.

---

One process, applied to everyone. The Volunteer Application & Screening Packet is the application, the background-check authorization and the reference forms: the same set for the newcomer and the volunteer of twenty years, which is what makes it defensible. $39, instant download. The wider HR and child safety set is on the Run My Church hub.

*Faith Docs provides self-help document templates, not legal advice. We are not a law firm. For representation, consult a licensed attorney.*