Loading the draft…
◆ Design · Box 07 · Serve Standard

The Serve Draft

One server, one team. Your rosters look full because the same people are counted on multiple teams. The draft assigns every world-changer one primary home, removes the double-counting, and turns "we always need more help" into a specific, recruitable number — team by team.
0
Roster slots filled today (overlaps counted)
0
Actual unique servers, deduplicated
0
Slots needed to run the weekend at standard
0
The true gap the draft reveals

Step 1Teams & the standard

Each team's weekend need at standard. Sit One, Serve One = 26 serves a year; Kids & Worship carry a raised bar (~39/yr). Sample needs are placeholders — set the real numbers.

Step 2The roster — before the draft

Every server and every team they're currently counted on. Tap a team chip to toggle membership; tap ★ on a chip to set it as their one primary team. Anyone on 3+ teams gets a spread-thin flag — those are the first "land in one home" conversations.
The draft rule: every server gets exactly one primary team — kept if already set, otherwise auto-assigned to their highest-need team (flagged for the Team Leader to confirm). Guest-serving elsewhere is still welcome; the draft governs counting and belonging, not permission.

Step 3The deflation — no one lost, everything counted once

Roster-today vs. primary-after-draft per team. The totals prove the point: the "filled" slots were never that many people.

Step 4The true gap

Primary servers vs. slots needed at standard, ranked by shortfall — the real recruiting picture, team by team.

Step 5Phased rollout

A new standard lands well only when leaders own it first, team leads carry it next, and volunteers hear it last — invited, never conscripted. Dates anchor to the ministry calendar.
Weeks 1–2

Leadership align

Walk the Directors through the draft model and the true gap. Confirm the standard and lock the numbers. Each Director owns their area's gap.

Weeks 3–4

Team talks

Each Team Leader receives their deduplicated primary roster and their team's gap number. Coach the "why": one primary team means real belonging.

Weeks 5–7

Volunteer talks

Confirm each server's primary team warmly — especially the spread-thin. Then launch the church-wide serve invitation.

Weeks 8+

Steady state

Re-draft each season; report the gap monthly until it closes. The standard keeps servers whole and the doors covered.

Step 6Rollout comms, in CWC voice

Three templates — leadership brief, Team Leader talking points, church-wide invitation. Hit ✨ Draft comms to have AI write them from the live numbers, then edit anything.
ChurchOps · Serve-Draft Modeler — its own shared model, saved live
·