Inroads · C3 Toronto · Planning Center data · Jan 1 – Aug 31, pulled Sep 1 2026

People are getting onto teams faster, and more of them

The 2026 campus-and-team workflows, measured against the onboarding flows they replaced. Downtown, Midtown & Hamilton; year-to-date versus the same eight months of 2025.

GRACEDevery recruitment measure is up — with a call backlog to clear (below)
Placed on teams
447 vs 225
≈2× completions recorded Jan–Aug¹
Sign-ups entering
786 vs 545
+44% cards opened YTD
Sign-up → on team
42d vs 58d
16 days faster (median)
Conversion
65% vs 55%
+10 pts of decided cards, joined
Sunday serving slots
+22%
all 3 campuses up · excl. Easter

Recruitment today — who's on a team, from the workflows

Every card in a 2026 Teams workflow, as of this morning. Completed = connection made (they're on the team); removed = connection not made. 304 onboardings have completed through the new flows (283 unique people), 169 are mid-pipeline, and a further 139 joined this year through the handful of old flows still in use¹.

TeamSign-upsJoinedIn progressNot madePipelineOverdue

Pipeline bar: joined · in progress · not made. Creative isn’t listed — its 73 sign-ups this year still run through the 2024-era flow (see watch list).

Speed — how long it takes to start and finish

Median journey from sign-up to joining the team dropped from 58 days to 42. The share of sign-ups fully onboarded within 60 days rose from 27% to 36% — and Downtown, the slowest campus last year, cut its median in half.

Median days: sign-up → on team

Completed cards only · 2025 = Jan–Aug cohort of the old flows (n=288) · 2026 = new flows (n=304)
20252026

Onboarded within 60 days of signing up

Cards old enough to have had 60 days · Hamilton 2025 n=19, treat with care
20252026

Effectiveness — more of the people who decide, join

Of the cards that reached a decision, 65% ended with a person on a team, up from 55% for last year's Jan–Aug cohort. Completions are also accelerating through the year — August was the best month so far.

People placed on teams, by month

Completions recorded each month · 2026 counts the new flows only (old-flow completions in 2026 add ~139 more)
20252026

Are we calling people when we should?

Yes by design, not always in practice. Every 2026 flow opens with an automatic welcome email and then a Team Interest Call as the first human step — a structure the old flows didn't guarantee. Right now, though, there's a backlog:

Waiting on the call
22
open cards sitting at “Team Interest Call”
Of those, overdue
17
past the step's due date
Median wait
26d
since they signed up
All overdue cards
70
11% of YTD sign-ups · biggest cluster: 24 at “Roster / Attend Orientation” (21 overdue)

One focused call blitz clears it. The 22 call-stage people are the warmest leads in the pipeline — a person per campus making calls this week would zero the backlog. (Planning Center doesn't expose per-step timestamps, so overdue flags and step position are the honest proxy for call timeliness.)

Engagement — are more people actually serving?

Scheduled serving slots on a typical Sunday are up at all three campuses — combined +22% year-over-year (Easter excluded). Midtown's teams grew the most, +44%.

Average volunteers scheduled per Sunday

First Sunday of each month, Jan–Aug, from Services plans · Easter 2026 sample excluded from averages
20252026

Attendance quality baseline: in the January 2025 Downtown sample, 81% of scheduled volunteers confirmed and 7% declined. A matching 2026 confirmation pull is the natural next measure to add to the dashboard.

Watch list — the not-yet-graced pockets

Method & caveats

¹ “Placed on teams” counts workflow-card completions recorded Jan–Aug of each year: 2025 = 225 completions on the legacy onboarding flows; 2026 = 308 on the new Teams flows + 139 on legacy flows still in use. By unique people, 333 individuals have completed a team workflow so far in 2026 vs 338 in all of 2025.

Sources: Planning Center People workflow cards (1,835 cards across 55 team workflows, pulled Sep 1 2026) and Planning Center Services plans (first-Sunday samples, Jan–Aug 2025 & 2026, all three Sunday service types). 2025 figures use the Jan–Aug cohort of cards created in the legacy “TEAM ONBOARDING” flows; 2026 figures use the “2026: Teams” flows plus Downtown Security. CDMX flows excluded.

Known gaps: an API pagination quirk left ~130 legacy cards unretrieved (mostly DT Kids and Creative), which slightly understates 2025 — the direction of every comparison is unaffected. Easter fell on a sampled Sunday in 2026 but not 2025, so serving averages exclude that sample. Planning Center does not expose per-step history, so call timeliness is proxied by current step + overdue flags. Completed = “connection made” per the team's convention; removed cards are counted as “not made”, and 169 cards are still undecided.