Do we need a lawyer to write this policy?

Not to draft a first version. Most small churches can write a workable policy from a template like this one, adopt it at a board or elders' meeting, and start using it. Where a lawyer earns their fee is the disqualifying-offenses list and any state-specific consent language, especially if your state has its own rules for volunteers working with minors. A one-time review is worth the cost; writing the whole thing from scratch with an attorney usually is not.

How often should we re-run a background check?

Every two to three years is the common range for volunteers in ongoing children's or youth roles, and most background check vendors will remind you automatically if you set up recurring checks. A person who passed five years ago and hasn't been re-checked since is not actually a covered volunteer under most policies — the point of a renewal date is that the check has to stay current, not just have happened once.

What do we do if someone has an old conviction on their record?

Your policy should say, in advance, that a hit does not mean an automatic no. A committee of two or three people reviews the nature of the offense, how long ago it happened, and its relevance to the role — a decade-old unrelated misdemeanor is different from a recent offense involving a minor. Deciding this in the calm of a policy meeting, rather than in the middle of an awkward conversation with a specific person, is the whole reason to write it down beforehand.

Can someone start serving while their check is still pending?

Only in a role your policy has explicitly marked as not requiring a check, or under a temporary, supervised exception you have written down in advance — for example, a new volunteer who is never alone with a child and is always paired with an approved one. If the policy is silent on this, the safe default is no: the person waits until the check clears, even if that means a gap on the schedule for a week or two.

Do different volunteer roles need different levels of check?

Yes, and the policy should say so by role rather than leaving it to whoever is scheduling that week. A nursery worker, a youth leader, and a counter handling cash offerings present different risks and often call for different checks — a standard criminal background check for most roles, and a more thorough check, sometimes including a sex offender registry search, for anyone with unsupervised access to minors.

A background check policy template for small churches

Most churches run background checks. Far fewer have written down why, on whom, how often, or what happens when a check comes back with something on it. The check itself is the easy part — a form, a fee, a few days' wait. The policy is the part that actually protects people, because it is the document you point to when someone asks “why does the greeter need one but not the usher?” or, worse, when something has already gone wrong and a lawyer asks what your process was.

You do not need a long document. You need a short one that covers every question someone will eventually ask, written down before you are answering it under pressure. What follows is the skeleton: the sections a usable policy needs, in the order a reader expects them, with enough of each to fill in with your own church's specifics.

Start with a one-paragraph purpose statement

Open with why the policy exists, not just what it requires. A short paragraph naming the goal — protecting children, vulnerable adults, and the funds members give in trust — does more work than it looks like it does. It is the sentence a new volunteer reads before the rules, and it is the sentence a court or an insurer reads first if they ever have to. Something like: “This policy exists to protect the children, students, and vulnerable adults in our care, and to protect the volunteers who serve them, by screening everyone in a position of trust before they begin serving.”

Name exactly who the policy covers

Vague scope is where policies fail in practice. List roles, not categories: nursery and toddler room, children's ministry teachers and assistants, youth leaders and youth trip chaperones, any adult who transports minors, small group leaders who meet with minors, counters and anyone with access to bank accounts or online giving logins, and paid staff. If a role involves unsupervised time with a minor, cash, or another person's personal records, it belongs on the list. A short list you actually enforce beats a broad one nobody checks against when the schedule gets built — which is exactly the kind of gap scheduling volunteers in a small church tends to expose, since the same handful of willing people rotate through several roles at once.

It helps to also name who is not covered, so the boundary is not left to guesswork. A visiting speaker who is never alone with a minor, a member helping set up chairs on a single Sunday, or a parent chaperoning their own child's group typically fall outside the policy. Writing that down keeps the requirement focused on real risk instead of becoming a blanket rule people quietly ignore because it feels like overkill for a one-time helper.

Spell out what kind of check each role requires

Not every role needs the same depth of screening, and saying so explicitly keeps the policy from being applied unevenly. A workable structure has two or three tiers:

Standard tier — a criminal background check, covering most volunteer and staff roles with occasional or supervised contact with others.
Enhanced tier — a criminal background check plus a sex offender registry search, for anyone with regular, unsupervised access to minors or vulnerable adults.
Financial tier — a criminal background check with attention to fraud or financial offenses, for counters, treasurers, and anyone with access to accounts.

Naming the vendor you use (many churches use a dedicated faith-based screening service rather than a general consumer site) and the approximate turnaround time sets expectations for new volunteers waiting to serve. It also gives you one number to check when a volunteer asks how much longer their check will take, instead of forwarding the question to whoever set up the account two treasurers ago.

If your budget is a real constraint — and for most churches this size, it is — say so in the policy too. Building the per-check cost into the annual budget as a fixed line item, rather than an occasional surprise expense, is what keeps a treasurer from quietly delaying a check to save money in a tight month. A church of sixty people with ten covered volunteers and a two-year renewal cycle is only budgeting for about five checks in any given year — a predictable number worth planning for rather than absorbing as a surprise.

A background check requires the person's written consent — this is a legal requirement, not a courtesy — so the policy needs a section describing the consent form, who signs it, and who sees the result. State plainly that results are reviewed by a small, named committee (often two or three board members or elders, not the whole staff), stored securely, and not shared beyond that committee. A volunteer deciding whether to trust you with this information wants to know, in writing, that the answer is not “whoever happens to be in the office.”

Storage matters as much as access. A results printout in a folder in an unlocked filing cabinet is not confidential no matter what the policy says. Whether you keep results on paper in a locked drawer or in a restricted digital folder, the policy should say exactly where, for how long, and who has the key or the login — and should require that results be destroyed once they are no longer needed rather than accumulating indefinitely.

Define what counts as disqualifying — and who decides

This is the section churches most often skip, and the one they miss most when they need it. Decide in advance: which offenses are an automatic no (typically anything involving a minor, sexual offenses, and violent felonies), which trigger a case-by-case review (older, unrelated, or minor offenses), and who makes that judgment call. A committee of two or three, working from a short written standard, is far steadier than one person making the decision alone in the moment — and far fairer to the person being reviewed.

It also helps to write down what the committee is weighing, not just that it weighs things: how long ago the offense occurred, how directly it relates to the role in question, whether there is a pattern or a single incident, and what the person has done since. None of this needs to be legalistic. A short paragraph naming these four questions gives a committee something concrete to work from instead of an uncomfortable, unstructured conversation about a person they may know personally.

Set a renewal schedule and an appeals path

A check that happened once, years ago, is not the same as an active policy. Pick a re-screening interval — two years is common, three at the outside for lower-risk roles — and write down what happens if someone's check lapses: they step back from the role until it is current, not quietly kept on the schedule anyway. Add a short appeals section too: if someone disagrees with a decision, who do they ask to reconsider it, and by when. A policy without an appeals path tends to get worked around instead of followed.

Require sign-off before anyone serves, not after

The last section should be the simplest and the most enforced: no one in a covered role serves until their check has cleared and the committee has signed off. This sounds obvious in writing and is routinely skipped in practice, usually because a nursery is short two weeks in a row and someone eager fills in. Building the check into your onboarding step — before a new volunteer is added to any rotation — is what keeps the policy from becoming a formality you only remember after the fact. It is also part of the same discipline as protecting a serving team from burnout: a role people can trust is one with clear boundaries on both ends, who is approved and who isn't.

SundayBridge puts a background-check status on each volunteer's profile and surfaces an alert on the dashboard when one is missing or coming due, so the gap shows up before someone is scheduled rather than after. It will not write your disqualifying- offenses list or decide a borderline case for you — that judgment belongs to your committee, not a dashboard. Getting that oversight in place is one more piece of the weekly rhythm that keeps a small church's admin from sliding, along with keeping an eye on which small group leaders also need a check on file because they meet regularly with minors.

Adopt it, date it, and revisit it once a year

A policy is only real once your board or elders formally adopt it — a line in the meeting minutes, a signature, a date. Put a review date on the calendar a year out. Screening vendors change their offerings, states occasionally update consent requirements, and your own list of covered roles will shift as ministries grow or shrink. A policy that was written once and never revisited tends to quietly stop matching what the church actually does.

Frequently asked questions

Do we need a lawyer to write this policy?: Not to draft a first version. Most small churches can write a workable policy from a template like this one, adopt it at a board or elders' meeting, and start using it. Where a lawyer earns their fee is the disqualifying-offenses list and any state-specific consent language, especially if your state has its own rules for volunteers working with minors. A one-time review is worth the cost; writing the whole thing from scratch with an attorney usually is not.
How often should we re-run a background check?: Every two to three years is the common range for volunteers in ongoing children's or youth roles, and most background check vendors will remind you automatically if you set up recurring checks. A person who passed five years ago and hasn't been re-checked since is not actually a covered volunteer under most policies — the point of a renewal date is that the check has to stay current, not just have happened once.
What do we do if someone has an old conviction on their record?: Your policy should say, in advance, that a hit does not mean an automatic no. A committee of two or three people reviews the nature of the offense, how long ago it happened, and its relevance to the role — a decade-old unrelated misdemeanor is different from a recent offense involving a minor. Deciding this in the calm of a policy meeting, rather than in the middle of an awkward conversation with a specific person, is the whole reason to write it down beforehand.
Can someone start serving while their check is still pending?: Only in a role your policy has explicitly marked as not requiring a check, or under a temporary, supervised exception you have written down in advance — for example, a new volunteer who is never alone with a child and is always paired with an approved one. If the policy is silent on this, the safe default is no: the person waits until the check clears, even if that means a gap on the schedule for a week or two.
Do different volunteer roles need different levels of check?: Yes, and the policy should say so by role rather than leaving it to whoever is scheduling that week. A nursery worker, a youth leader, and a counter handling cash offerings present different risks and often call for different checks — a standard criminal background check for most roles, and a more thorough check, sometimes including a sex offender registry search, for anyone with unsupervised access to minors.