Most churches get the first background check right. Someone signs up to help in the nursery, the check runs, it comes back clean, and the volunteer starts serving. What trips churches up is the assumption that the job is now done — that a check completed once, at onboarding, covers the whole life of that person's service, whether that turns out to be six months or fifteen years.
It does not, and treating it like it does is the single most common gap in an otherwise careful volunteer screening process. A background check is a report on a moment. People's records change after that moment, in both directions, and a policy that never asks the question again is quietly betting that nothing will.
A check reports on a day, not on a person forever
It helps to be precise about what a background check actually verifies. It is a search of certain records — often county and state criminal records, sometimes a sex-offender registry, depending on the provider and the plan — as of the date it ran. It says nothing about what happens the following Tuesday, or the following year. A volunteer who has served faithfully for a decade is not exempt from time passing any more than a brand-new one is.
This is not a comment on any individual volunteer's character. Most people who serve at a church for years never do anything to warrant concern. But a policy is not built around the volunteer you already trust — it is built to catch the rare case you cannot see coming, and a check that never reruns cannot catch anything that happens after the first one.
Set an interval, and put a number on it
The single most useful thing a small church can do here is stop treating rechecks as a judgment call and turn them into a fixed interval. Many churches land on every two to three years for volunteers with regular contact with kids or students, tightened to annually for the roles with the least supervision — a solo nursery worker, someone who drives a church van, a leader who spends one-on-one time with a student. The exact number matters less than having one. “We'll get to it” is not a policy; it is a gap waiting for someone to notice it.
Your insurance carrier or denomination may already set a floor for you — some require rechecks on a specific cycle as a condition of coverage. If yours does not, borrow a number from a similar-sized congregation rather than inventing one from scratch. What matters is that the interval is written down somewhere a new ministry leader can find it, not something only the person who set it up remembers.
Tie the interval to the role, not the calendar year
A common mistake is rechecking everyone on the same date, all at once, regardless of when they started. That creates a scramble every January and lets a volunteer who joined in February slide by for eleven extra months on an already-stale check. It is simpler, and more accurate, to tie each recheck to the individual volunteer's own start date or last check date — three years from when Dana's check ran, not three years from January 1.
This only works if someone can actually see, for each person, when their last check happened and when the next one is due. That is a record-keeping problem before it is a screening problem, and it belongs in the same place as the rest of a volunteer's serving schedule, not in a spreadsheet nobody opens between January scrambles.
Decide who gets flagged when a recheck is due
The same discipline that governs the original alert should govern the recheck: a small, named set of people sees that a check is due or overdue, not the whole serving team. On SundayBridge, background-check alerts sit on the dashboard next to the rest of a serving team's roles and assignments, so a recheck coming due shows up the same way a scheduling gap would — as a thing to handle, visible to whoever runs that ministry, rather than a fact buried in a folder nobody revisits until something goes wrong.
Whoever owns that alert should also own the follow-through: reaching out to the volunteer, explaining that this is routine and not a sign of suspicion, and getting the new check scheduled before the old one lapses. A due date with no owner behaves exactly like no due date at all.
Do not let a lapsed check quietly become a break in service
When a recheck slips past due, the honest options are limited: pause the volunteer from the specific high-contact role until the new check clears, or accept that the policy exists in name only. Neither option is comfortable, which is exactly why churches without a firm interval tend to let it slide — nobody wants to tell a longtime volunteer they cannot serve this Sunday over paperwork. But the alternative is a policy that only ever applies to new volunteers, which defeats the point of having one.
The way to make this less painful is to build in lead time. If a check is due in ninety days, that is the moment to schedule it, not the day it lapses. A volunteer who gets three months of notice experiences a recheck as routine maintenance. A volunteer who finds out on a Sunday morning that they cannot serve until a new check clears experiences it as a crisis, and so does whoever has to tell them.
Explain the schedule before anyone is due for a recheck
The best time to tell a volunteer their background check will run again in a few years is when they first sign up, not three years later when the notice shows up unannounced. Say it plainly: this check happens on a schedule, it applies to everyone in this role, and it is not a comment on anything in particular about them. Framed that way, most volunteers treat a recheck the way they treat a renewed insurance policy — unremarkable, because they were told to expect it.
This is the same instinct behind a good serving rotation: clear expectations set once, at the start, save you a dozen awkward conversations later. A recheck policy that surprises people feels like suspicion. A recheck policy that was explained on day one feels like due diligence — because that is what it is.
Keep the recheck record with the rest of the person, not off to the side
A volunteer's background-check history is one piece of a fuller record that also includes their groups, their giving, and how long they have served. Keeping the check date buried in a separate system, disconnected from everything else you track about that person, is how rechecks get missed in the first place — nobody sees the due date because nobody is looking at that system on an ordinary week. It belongs alongside the rest of their directory record, where whoever already checks on serving assignments will see it without having to remember to look somewhere else.
None of this needs to be complicated to be effective. A fixed interval, one owner, and a record that surfaces the due date on its own — that is most of what separates a background-check policy that actually protects people from one that only looks like it does on the day it was written.