Background check before you schedule a volunteer

This 280-attendance Midwest church blocks kids and student scheduling in Planning Center Services until Planning Center People shows a current background-check date. One owner runs a Tuesday sweep. Hallway exceptions are refused.

By Caleb Brooks · Published September 2026· Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

What are the exact steps?

Name the owner and the cleared-for-kids rule
Write one human owner (often the kids director or administrator) and one backup on the Monday checklist. The rule is plain: nobody is scheduled in kids or student ministry until Planning Center People shows a current background-check date inside your renewal window. Elders approve the rule in writing once so hallway exceptions die.
Add a background-check date field and a cleared list
In Planning Center People (the church's people database), add a field or tag for the background-check completion date and renewal due date. Build a saved list that shows people cleared for kids and students. If a person is not on that list, Services schedulers treat them as not available for those teams.
Start the check before you invite someone onto the plan
When a new volunteer expresses interest, the owner sends the vendor invite the same week. Do not put them on a Planning Center Services plan "just to hold the slot" while the check is pending. Hold the interest on a separate pending list. Schedule only after the result is clear and the date is on the People record.
Record the result and then schedule in Services
When the vendor returns a clear result, the owner enters the completion date and renewal date in People, adds the person to the cleared list, and only then tells the team leader they may schedule in Services. Declined or incomplete results stay off the schedule. Pastoral follow-up for hard news happens by phone, not in a volunteer GroupMe.
Run a ten-minute weekly sweep before plans lock
Every Tuesday, the owner opens the cleared list, checks renewals due in the next 60 days, and compares kids and student Services plans for the next four weeks. Anyone on a plan without a current date gets removed the same day and contacted with a clear next step. The sweep takes about ten minutes at this church's volume.
Refuse Friday night exceptions out loud
If a leader asks to put an uncleared volunteer on the plan because "we're short," point to the elder-approved rule. Offer a cleared substitute from the list. Document the ask so the same pressure does not return every holiday weekend. Safety habits fail in the exception, not in the software.

Which tools does this church use?

Planning Center People Church database (ChMS)
Holds household records, the background-check date field, and the cleared-for-kids list.
$14/mo
Planning Center Services Scheduling
Weekend volunteer scheduling. Team leaders only schedule people who appear on the cleared list.
$0 (included with stack)
Background check vendor Other
Runs the actual check. Results return to the named owner, not a public inbox.
Per-check fees (confirm current rates)

Common questions

Can we schedule someone while the background check is pending?

No for kids and student teams. Hold interest on a pending list. Schedule only after the clear date is on the People record.

Who should own background checks?

One named staffer or director with one backup. If two people own it, nobody owns the Tuesday sweep.

What tools does this church use?

Planning Center People for the date and cleared list, Planning Center Services for scheduling, and a background-check vendor for the actual screening.

Before you start

You need admin access to Planning Center People and Planning Center Services, an account with your background-check vendor, and elder approval of one sentence: kids and student volunteers are not scheduled without a current check on file. Name the owner and backup before you build the list. Tell team leaders the rule in one staff meeting so the first refusal is not a surprise on Saturday night.

Why they built it

Warm leaders were putting new helpers on the kids plan after a hallway yes. Some checks were never started. Others finished weeks after the person had already served. The church decided love of children includes paperwork that finishes before the schedule, not after a scare. Planning Center People holds the date. Services only schedules from the cleared list. The Tuesday sweep catches renewals before Advent and VBS pressure hits.

What they’d do differently

They would refuse “pending on the plan” from week one. Holding a slot for an uncleared volunteer trained everyone to treat the rule as optional. They would also put renewal dates on the record at the same time as the completion date, so the spring scramble is smaller. Hard declines would go to a phone call script written ahead of time, not an awkward text in a volunteer thread.

Before you copy the clicks

Background check before you schedule a volunteer only works when a tired Monday reader can finish it without inventing owners. Read the frontmatter tools (Planning Center People, Planning Center Services, Background check vendor) and confirm those logins already exist in a-suburban-church-in-the-midwest. If a tool is missing, buy or borrow it on purpose. Do not invent a parallel Sheet “just for this week.”

Setup difficulty on this page: one-afternoon. Plan about one afternoon for first setup, plus a quieter second pass after the first real Sunday. Incremental cost range: $0–14/month incremental software + per-check vendor fees. Confirm vendor pricing the week you brief elders.

Who owns each handoff

Name a primary owner and a vacation backup before the first live run. Write those names on a card near the desk that finishes Sunday entry. Greeters, finance helpers, and volunteer coordinators should know who to ping when a step stalls.

Keep exports and pastoral notes on the tightest permissions the job allows. A workflow that moves guest or benevolence data through a shared inbox needs an explicit watch schedule, including holiday weekends.

What the week looks like when it works

Name the owner and the cleared-for-kids rule: keep the owner and timing in the detail as written; do not skip the human handoff.
Add a background-check date field and a cleared list: keep the owner and timing in the detail as written; do not skip the human handoff.
Start the check before you invite someone onto the plan: keep the owner and timing in the detail as written; do not skip the human handoff.
Record the result and then schedule in Services: keep the owner and timing in the detail as written; do not skip the human handoff.
Run a ten-minute weekly sweep before plans lock: keep the owner and timing in the detail as written; do not skip the human handoff.

When the week works, nobody needs a hallway rewrite. Cards or forms land in the right list the same day. Messages leave a church-owned channel when personal phones would hide replies. Exceptions get a note, not a new secret process.

What breaks first

The first break is usually ownership, not software: a card left in a basket, an unwatched reply-to, a schedule published without a backup, or a giving test that never clears into the church account. Automations without watchers create polite silence. Dual systems create double Monday reconcile.

If your staff hours are thinner than the churchRef stack assumes, shrink the promise. Keep the moral core (a person follows through) and cut optional channels until the core is reliable for four Sundays.

Pricing and time honesty

Budget $0–14/month incremental software + per-check vendor fees plus the weekly minutes to keep the path honest. A $0 path that burns three volunteer evenings is not free. Put hours beside fees on the board note. Train the backup on a quiet weekday before vacation season.

Re-verify this workflow when tools change owners or when the churchRef stack updates. lastVerified dates are stewardship tools. Treat an unverified page as a starting draft until someone runs the path again.

Copy-only-if checklist

Tools in frontmatter match logins you actually have.
Primary and backup owners are named in writing.
One full path timed end to end on a phone if foyer work is involved.
No second database or second inbox “for transition.”
Elder or staff note includes cost range $0–14/month incremental software + per-check vendor fees and setup time one afternoon.

Steal the promise and the ownership pattern. Adapt the branding later.

After the first four Sundays

Review what actually happened: missed steps, reply delays, and any hallway workarounds. Keep the parts people used. Cut the parts that required heroics. A workflow that only works when one specific person is healthy is not finished yet. Write the backup path before you call the process done.

One short Monday email with a complete how-to for churches your size: named tools, ordered steps, and real cost. Reply anytime. A person reads it. Unsubscribe in one click.