Is there a law that says how often to re-run a background check?

Almost never, and that is exactly the problem. A handful of states attach a renewal interval to specific licensed roles — a licensed childcare center, for example — but a volunteer greeter or small group leader at a typical congregation is not covered by any statute that names a number. The absence of a legal deadline is not the same as no obligation. It means your church is the one who has to pick a number and write it down.

Do adult-only ministries need a recheck schedule at all?

Most churches still set one, just a longer one, because a background check is really a proxy for a broader question: is this the same trustworthy person we screened three years ago? A five-year cycle for ushers, greeters, and adult small group leaders is common and defensible. What you should avoid is having no schedule at all for any serving role, since “we checked once, a long time ago” is the sentence that reads worst after something goes wrong.

What should we do between renewal dates if we hear something concerning?

Re-run the check immediately, regardless of where the person sits in the cycle. The renewal schedule is a floor, not a ceiling. If a volunteer discloses a new charge, a parent raises a concern, or something surfaces informally, waiting for the next scheduled date because “it isn't due yet” defeats the purpose of having a policy in the first place. Treat any credible concern as its own trigger, separate from the calendar.

Who should own tracking the renewal dates?

One named person, not “the office” in the abstract. Diffuse ownership is how renewal dates quietly slip past their deadline — everyone assumes someone else is watching the calendar. Whoever runs your serving teams, often a volunteer coordinator or an elder over ministries, should own the list, and that ownership should survive a change in who holds the role, which means it needs to live in a record, not in one person's memory.

Does a clean recheck mean we can stop worrying about that volunteer?

No, and it is worth saying plainly. A background check, first run or fifth, only surfaces what made it into a public record. It says nothing about behavior nobody has reported yet. The renewal schedule keeps your paperwork current and closes the gap where a five-year-old check quietly goes stale, but it was never meant to replace the ordinary judgment of leaders who actually watch how someone treats children, money, or people in a vulnerable moment.

How often should you re-run background checks on volunteers

Every church runs the first background check. It is the second one that trips people up. A volunteer coordinator hires a service, screens a new children's ministry helper, files the result, and moves on to the next Sunday's problem. Nobody circles back in three years to ask whether that same helper is still clean, because nothing on the calendar told them to. The policy, if the church has one, usually says who gets checked and rarely says when the check expires.

That gap is not laziness. It is a question small churches genuinely never settle, because there is no single legal answer waiting to be looked up. Below is a cadence you can adopt as written, the reasoning behind each interval, and the one sentence that turns this from a hallway conversation into an actual policy.

Why this question stays unanswered for so long

Most volunteer screening policies are written once, usually after a denomination sends a sample policy or an insurer asks for one at renewal time. Those templates are thorough about who needs a check — anyone working with minors, anyone handling money, anyone alone with a vulnerable adult — and vague about how often the check needs to happen again. The sample language says “checks will be conducted periodically” or “as required,” which is a sentence that satisfies an insurance auditor and helps nobody actually running a serving team three years later.

The result is a policy that is airtight at onboarding and silent after that. A volunteer who has served faithfully for six years, screened once on their first Sunday, is not covered by anything the policy actually says, because the policy never named a number.

A cadence you can copy

There is no single correct interval, but there is a defensible one most small churches land on once they stop avoiding the question. Use role, not tenure, as the variable that changes the number.

Roles alone with children or students — re-check every two years. This is the tightest interval on the list because the stakes are highest and because a two-year window is short enough that a volunteer's status stays genuinely current, not a formality from half a decade ago.
Roles handling money — counters, treasurers, anyone with signing authority — every three years. Financial history changes more slowly than criminal history tends to surface, so a slightly longer window is reasonable here.
Adult-only serving roles — greeters, ushers, adult small group leaders — every five years. This is the longest interval, and it is still an interval, which matters more than the exact number. Five years with a schedule beats no schedule at all.
Any credible concern, at any time — run it immediately, independent of where the person sits in the cycle above. The schedule is a floor. A new charge, a disclosure, or a parent's concern does not wait for the next renewal date.

None of these numbers is arbitrary in the sense of being made up on the spot, but none of them is a legal requirement either. They are a reasonable default. If your denomination, insurer, or state gives you a shorter number for a specific role, use theirs. Where nobody tells you anything, the cadence above is a defensible place to start and, more importantly, a place to actually land instead of circling the question indefinitely.

The sentence that makes it a policy instead of a habit

A cadence only works once it is written into the document your church actually uses, not just understood by whoever happens to be running serving teams this year. Add a line close to this:

“Background checks are re-run on the following schedule: every two years for roles working directly with minors, every three years for roles with financial signing authority, and every five years for all other serving roles. Any credible concern raised outside this schedule triggers an immediate re-check regardless of the volunteer's renewal date.”

That single paragraph does more work than pages of surrounding policy language, because it removes the two failure points that actually cause lapses: a vague word like “periodically,” and no stated exception for something urgent that cannot wait for a calendar date.

Tracking dates is the part that actually breaks

Writing the cadence down solves the policy problem. It does not solve the tracking problem, which is where most churches actually fail, not in the wording. A three-year renewal schedule spread across forty volunteers means forty different dates to remember, and a spreadsheet column nobody opens unless someone happens to think of it is not a tracking system. It is a document that exists.

On SundayBridge, background-check status shows up as an alert on the dashboard against each volunteer's record, which means the renewal date lives next to the same profile that already tracks their serving assignments — not in a separate file someone has to remember to cross-reference. The point is not the software. The point is that a renewal date detached from the person's actual record is a date that gets missed, and a renewal date attached to it is a date somebody notices.

Do not let the schedule replace ordinary attention

It is worth saying plainly: a clean background check, on day one or on renewal five, only reflects what has made it into a public record. It says nothing about a pattern of behavior nobody has reported. A cadence keeps your paperwork honest and closes the specific gap where a five-year-old check quietly becomes the only thing standing behind a volunteer's status. It was never meant to replace a leader noticing how someone actually behaves with children, with money, or with a person in a hard moment. Treat the schedule as the floor of your diligence, not the whole of it.

What to do about volunteers who are already overdue

If you are reading this because your church has never had a renewal schedule, you almost certainly have volunteers who would already be overdue under any reasonable cadence. The instinct is to quietly grandfather everyone in and start the clock only for new volunteers going forward. Resist it. Run a one-time catch-up pass instead: pull the list of everyone currently serving in a role that touches minors or money, check when each of them was last screened, and re-run anyone past the interval you just adopted. It is an uncomfortable week of paperwork once, not an ongoing problem, and it is far better than discovering the gap after something has already gone wrong.

This is also a natural moment to look at how you schedule volunteers more broadly, since a serving roster that is already organized by role and rotation makes a catch-up pass much faster than trying to reconstruct who serves where from memory or a bulletin insert from two years ago.

Writing this down protects the people who ask, too

A written cadence is not only about catching a problem before it happens. It also protects the volunteers who are doing everything right. When a renewal schedule exists and is applied evenly, a volunteer who gets asked to re-screen after two years understands it as routine, not as suspicion of them specifically. Without a written policy, every re-check request looks like it was triggered by something, which is an uncomfortable position to put a long-serving volunteer in for no reason. The schedule, once it is written down, is doing the coordinator a favor as much as it is doing the church one — it turns an awkward individual conversation into an unremarkable administrative fact.

It also matters for how sustainable the whole serving structure feels. A volunteer coordinator who has to personally remember and justify every re-check on an ad hoc basis is carrying weight that a written, evenly applied schedule removes, which is one small piece of keeping a serving team from burning out the people running it, not just the people on it.

The short version

Pick a cadence by role — two years for anyone alone with minors, three for anyone handling money, five for everyone else serving — write it into your policy in one plain paragraph, name one person who owns the renewal calendar, and treat any credible concern as its own immediate trigger regardless of the schedule. None of that is complicated. It is just the part most churches never get around to writing down, which is exactly why it is worth doing this week instead of after something makes the decision for you.

Frequently asked questions

Is there a law that says how often to re-run a background check?: Almost never, and that is exactly the problem. A handful of states attach a renewal interval to specific licensed roles — a licensed childcare center, for example — but a volunteer greeter or small group leader at a typical congregation is not covered by any statute that names a number. The absence of a legal deadline is not the same as no obligation. It means your church is the one who has to pick a number and write it down.
Do adult-only ministries need a recheck schedule at all?: Most churches still set one, just a longer one, because a background check is really a proxy for a broader question: is this the same trustworthy person we screened three years ago? A five-year cycle for ushers, greeters, and adult small group leaders is common and defensible. What you should avoid is having no schedule at all for any serving role, since “we checked once, a long time ago” is the sentence that reads worst after something goes wrong.
What should we do between renewal dates if we hear something concerning?: Re-run the check immediately, regardless of where the person sits in the cycle. The renewal schedule is a floor, not a ceiling. If a volunteer discloses a new charge, a parent raises a concern, or something surfaces informally, waiting for the next scheduled date because “it isn't due yet” defeats the purpose of having a policy in the first place. Treat any credible concern as its own trigger, separate from the calendar.
Who should own tracking the renewal dates?: One named person, not “the office” in the abstract. Diffuse ownership is how renewal dates quietly slip past their deadline — everyone assumes someone else is watching the calendar. Whoever runs your serving teams, often a volunteer coordinator or an elder over ministries, should own the list, and that ownership should survive a change in who holds the role, which means it needs to live in a record, not in one person's memory.
Does a clean recheck mean we can stop worrying about that volunteer?: No, and it is worth saying plainly. A background check, first run or fifth, only surfaces what made it into a public record. It says nothing about behavior nobody has reported yet. The renewal schedule keeps your paperwork current and closes the gap where a five-year-old check quietly goes stale, but it was never meant to replace the ordinary judgment of leaders who actually watch how someone treats children, money, or people in a vulnerable moment.