How to onboard volunteers with Planning Center Workflows (training included)

To onboard volunteers with Planning Center Workflows, build one workflow in Planning Center People with a step for each stage (interest, conversation, background check, training, shadowing, add to team), feed it from a sign-up form, give every step an owner and a deadline, and let the last step add the person to their Services team. The one stage Workflows can't do by itself is the training: a card only knows a step is done when someone on staff clicks it. Below is the full setup, and how to make the training step run and close on its own.

What you're building

A volunteer pipeline: every person who says "I'd like to serve" becomes a card that moves left to right through the same steps, with someone responsible at each one. Nobody falls through the cracks between the Sunday they filled out a card and the Sunday they're on the schedule.

You need Planning Center People (Workflows and Forms live there) and Planning Center Services (for the team they end up on). Checkr or the Protect My Ministry add-on is optional, for background checks inside Planning Center.

Step 1: Write the path on paper first

Before you open Planning Center, list what has to happen between "interested" and "serving" for one team, in order. For most churches it looks like this:

1. Person says they're interested (form, connection card or conversation)
2. A ministry leader contacts them within a few days
3. Background check (for anyone serving with children, students or vulnerable adults)
4. Training: your church's policies, plus what this role actually does
5. Shadow an experienced volunteer for a Sunday
6. Added to the team and scheduled

Keep it to six or seven steps. Each step should be something one person can finish and mark done. If a step needs three people, it's really three steps, or it needs an owner who chases the other two.

Step 2: Create the workflow in Planning Center People

In People, open Workflows and create a new workflow named for the team or the whole volunteer pipeline (for example, "Volunteer onboarding: Kids"). Add one step per line of your list.

One workflow per team works best when teams have different requirements (kids' ministry needs a background check; parking probably doesn't). One shared workflow works if every volunteer goes through the same path and only the final team differs.

Step 3: Give every step an owner and a deadline

This is what makes a workflow run instead of collect cards.

• Default assignee. Each step needs a person who gets new cards. Planning Center flags steps with no default assignee, and you can set the assignee for one step or all steps at once. Share the workflow with your ministry leaders first so you can assign steps to them.
• Expected response time. In each step's settings, check Expected Response Time and set the number of days. If a card sits past that, Planning Center emails the assignee and marks the card as past due.
• Overdue badge. "Mark overdue after..." puts an overdue badge on stuck cards, and the workflow index shows how many are overdue, so a staff lead can see what needs attention at a glance.

A reasonable start: contact within 3 days, background check within 14, training within 14, shadow within 21.

Step 4: Feed the workflow from a form

Create a volunteer interest form in People (or add questions to an existing connection form). Drag the Workflow fields onto the form and choose which workflow a person joins when they pick a team. Share the form's link or embed it on your website's serve page. Now every sign-up becomes a card in step 1 with an owner and a clock, instead of an email in someone's inbox.

Step 5: Handle background checks inside Planning Center

If your church uses Checkr, you can run background checks from inside Planning Center. The Protect My Ministry add-on (announced by Planning Center in May 2025) lets you track background checks and its safety training from People. If you use another provider, Planning Center lets you record checks manually. Either way, make the background-check step's assignee the person who can see results, and don't move a card on until the check has cleared. Planning Center Check-Ins can also require a cleared background check before someone checks in as a volunteer.

Step 6: Make the training step real

Here is where most volunteer pipelines stall. The workflow step says "Training", but the training itself lives somewhere else: a binder in the kids' wing, a video link in an email, a Sunday-afternoon session that half the new volunteers miss. The step's owner has to find out who finished, then remember to click the card forward. When that person is busy, cards sit in "Training" for weeks and the new volunteer drifts.

Whatever you use, decide three things:

• What the training is. Your policies (child safety, check-in, emergencies), then the role itself (what a Sunday looks like, who to ask). Short beats long: several 5- to 10-minute lessons, not a 90-minute video.
• How you know they understood it. A few quiz questions on the policies that matter most, with a passing score, or at least a signed acknowledgement.
• Who moves the card, and when. If a person has to check completion and click, write their name on the step and give it the expected response time from Step 3.

Doing it with EquipEngine

EquipEngine is a training platform built for Planning Center churches, and this step is what it was built for: link a Workflow step to a course, and the course is assigned the moment someone enters that step, due date reminders go out on their own (7 days before and on the day — see Assigning Courses), and finishing the course moves the card forward and can write the completion back to a custom field on their Planning Center record. See the Planning Center integration docs for how to connect it and set it up on a course. Workflow write-back is on the Equip plan, which comes with a 30-day free trial — see pricing.

Your workflow keeps running exactly as it does now; EquipEngine only listens to the step and closes it.

Step 7: Add them to the team automatically

When a card reaches the end, Planning Center can put the person on their Services team for you. In the workflow, open Perform action, set the application to Services, choose Add to Team, then pick the service type, team and position. From there they can be scheduled like anyone else on the team.

Common mistakes

• Steps with no owner. A step without a default assignee is a place where cards go to wait.
• No expected response time. Without it, a stuck card looks the same as a card that just arrived.
• Training that lives outside the workflow. If finishing training doesn't show up in Planning Center, someone has to check and click, and that's the step that stalls.
• One giant workflow for every team. Kids' ministry and parking have different requirements; one workflow per team (or per requirement level) keeps steps honest.
• Forgetting renewals. Many denominations ask for child-safety training to be renewed every one to five years. Put the renewal on the calendar when you set up the first training, not when it lapses.

Copy this: a volunteer onboarding workflow

Adjust the days to your church, then build it in People this week: one team first, then copy the workflow for the next.

See also: Planning Center integration docs · Assigning courses and due-date reminders · More resources