A church of 140 has a youth group of a dozen, and three of them are eager to help in the toddler room on Sunday mornings. They are good kids — the kind who show up early and actually get down on the floor with a two-year-old. The question that stalls most volunteer coordinators is not whether to let them serve. It is whether a fifteen-year-old needs the same background check as the forty-year-old standing next to her.
The honest answer is: it depends less on age than on what the role actually puts them in position to do. A teen who is always paired with an adult and never alone with a child is a different risk than a teen who runs the room solo for the last ten minutes while the adult signs out stragglers. Getting this right is less about a magic age cutoff and more about being specific about supervision, consent, and what a check on a minor can even tell you.
Age is the wrong first question
It is tempting to set a bright line — sixteen, or eighteen — and apply it evenly. Some denominations and insurers do exactly that, and if yours has a written policy, follow it; it exists for a reason and probably reflects legal advice you have not had to pay for yourself. But absent a firm rule from your insurer or denomination, the sharper question is whether the teen is ever unsupervised with a child who is not their own sibling or close relative. A sixteen-year-old shadowing an adult all morning is a much lower-risk role than a sixteen-year-old covering the nursery solo during the second service while everyone else is upstairs.
Why a check on a minor tells you less
Most background checks search criminal records, sex-offender registries, and sometimes credit or driving history — all of which accumulate with age. A fifteen-year-old has had, at most, a few years in which anything could show up, and juvenile records are often sealed by law regardless. That does not mean skip the check; it means understand that the check on a minor is a much thinner net than the same check on a thirty-year-old, and your supervision structure has to do more of the actual protecting.
Match the screening to the role, not the birthday
Two teens on your team may need two different answers. A sixteen-year-old who greets and checks families in at a table, always beside an adult, is doing a role that carries little private-contact risk. A sixteen-year-old who is the designated helper in the four-year-old room, sometimes alone while the lead teacher steps out to deal with a crying kid down the hall, is doing a role that does carry that risk — regardless of how trustworthy she is. Write down, role by role, whether unsupervised contact with a minor is possible. That list, not a single age line, is what should decide who gets screened.
Consent gets more complicated, not less
Running a check on an adult volunteer is a signature and a wait. Running one on a minor usually means getting a parent or guardian’s consent in addition to the teen’s own, and some screening vendors will not process a check on anyone under a certain age at all — often 18, sometimes lower with parental sign-off. Call your provider and ask directly rather than assuming the intake form works the same way for a fifteen-year-old as it does for his mother. This is also a good moment to loop the parent in on exactly what the role will and will not involve, since they are the one agreeing to it on the teen’s behalf.
What a written policy should actually cover
Most churches that get burned on this issue did not skip screening out of carelessness. They simply never wrote down a rule, so each volunteer coordinator made a different judgment call, and nobody could later explain why one teen was screened and another was not. A workable policy covers four things in plain language: the age at which screening begins by default, the specific roles that require it regardless of age, who signs the consent for a minor, and how often everyone — teen or adult — gets rechecked. None of this needs to be long. A single page that the whole team has actually read beats a thorough policy sitting unread in a binder.
It also helps to separate “can serve at all” from “can serve unsupervised.” A fourteen-year-old can hand out bulletins, help set up chairs, or run the sound board without ever being alone with a child who is not a sibling, and none of that needs the same scrutiny as nursery duty. Treating every volunteer role as identical — either all screened or all exempt — is usually where churches either overspend on checks that tell them nothing or underprotect a role that genuinely needed one.
Talk to your insurer before you write anything down
A church’s liability insurance policy often has its own language about minimum volunteer age, screening frequency, and supervision ratios for anyone working with children, and that language can be stricter than what state law requires. Denominational safe-ministry offices frequently publish their own model policies too, built from decades of incidents most congregations never hear about. Before finalizing your own rule, ask your insurance agent directly what their policy requires for volunteers under eighteen, and check whether your denomination has a standard you are already supposed to be following. It is far cheaper to align with what they already expect than to write your own rule and discover later that it does not meet the bar your coverage assumes.
What changes the moment they turn eighteen
A volunteer who started at fifteen as a supervised helper and is still serving at nineteen has quietly crossed into a different category, and your records need to catch that even if nobody remembers to flag it in person. The check that made sense for a minor — thin record, parental consent, paired-supervision role — is no longer the right one once they are an adult who might reasonably be left alone with children. This is exactly the kind of thing that gets missed when volunteer records live in a binder or a spreadsheet nobody opens between recruiting seasons.
SundayBridge keeps a background-check status on every serving-team profile and surfaces an alert on the dashboard when a check is missing or aging out, whether the volunteer is fifteen or fifty. It will not run the check for you or decide your policy — that is between you, your insurer, and your denomination — but it will stop a teen’s file from quietly drifting past the point where the old answer still applies.
Write the policy down before you need it
The worst time to figure out your stance on teen volunteers is the Sunday a parent asks why her son isn't screened like the adults are, or after an incident makes the question retroactive and urgent. Put it in writing now: the age at which screening starts, the roles that require it regardless of age, the consent process for minors, and the re-check interval as they age up. A short document that your team can point to is worth more than good intentions applied inconsistently case by case.
If you are also rethinking how volunteers get scheduled in the first place, see scheduling volunteers at a small church for how role clarity and screening status fit into the same weekly rhythm. And if the bigger problem is that a small circle of adults is absorbing all the load teens could be sharing, serving without burning out your best people covers how to widen that base safely.
The line between eager and unsupervised
A quick gut check when you are unsure: would you leave this same teen alone in a room with a neighbor’s toddler on a random Tuesday afternoon, with no other adult around and no one checking in? If the answer is yes without hesitation, the role probably does not need the full weight of adult screening. If it takes you a second to answer, that hesitation is the signal that the role belongs in the screened category, whatever the teen’s age happens to be.
None of this is about distrusting a teenager who wants to serve. It is about being honest that “I'm sure she's fine” is not a screening policy, and that the protection a background check offers a thirty-year congregation depends on applying it consistently, not on guessing which of your enthusiastic sixteen-year-olds is trustworthy enough to skip it. Decide the rule on a calm Tuesday, write it down, and let the system remind you when a file needs a second look — not a worried parent, and not a Sunday morning.