What a blockout is (and what it isn't)
A blockout is a volunteer telling Planning Center "don't schedule me on these dates." While a blockout is active, schedulers see the person crossed out in the scheduling matrix for those dates, and auto-schedule skips them. It's the proactive cousin of the decline: same information, delivered before you built the schedule instead of after.
The one gotcha everyone hits: a blockout does not cancel requests that already exist. If someone was scheduled for June 14 and then adds a blockout covering June 14, the pending request stays — they still need to decline it (or you need to unschedule them). Blockouts prevent future scheduling; they don't rewrite the past.
How volunteers add blockouts
Volunteers manage their own blockouts from Church Center (the app or the web) under their schedule, or from the My Schedule area when they log in to Services. Adding one takes seconds: pick a date or a range, optionally add a reason, save. Volunteers can also set repeating blockouts — "every first weekend of the month," "every Tuesday" — which is the right tool for recurring commitments like a monthly shift elsewhere, a standing class, or a custody schedule.
Schedulers can also add a blockout on behalf of a volunteer from the person's profile in Services. Use that power freely: when someone texts you "we're at the lake July 4th weekend," put the blockout in yourself right then. The thirty seconds it costs you is cheaper than the decline it prevents.
Building a blockout culture
The mechanics are easy; the habit is the hard part. Churches with low decline rates almost always have high blockout usage, and they get there the same few ways:
- Make it part of onboarding. When someone joins a team, the "add your blockouts" walkthrough happens before their first schedule, not after their first conflict.
- Prompt seasonally. Two or three times a year — before summer, before the holidays — ask every team to update blockouts. Christmas schedules built on January's blockout data are how December scrambles happen.
- Praise the behavior. When a blockout saves you from a bad assignment, say so: "saw your blockout, got you covered." People repeat what gets noticed.
Scheduling around blockouts
- In the matrix view, blocked-out volunteers appear crossed out on those dates — auto-schedule and thoughtful manual schedulers both skip them.
- Check before big pushes: before building a month of schedules, skim the team's blockouts so you know your real bench for each week.
- Blockouts beat memory. If you find yourself keeping conflicts in your head or in a notes app, move them into Planning Center where every scheduling tool can see them.
The automation angle: calendars that block themselves out
The deepest blockout problem is that volunteers forget to add them — the conflict lives in their personal calendar, not in Planning Center. Planning Orchestrator closes that gap: volunteers can link a personal calendar feed (Google, Apple, Outlook), and busy events sync into PCO blockouts automatically and stay in sync as plans change. Schedulers can also just tell the assistant "block out the Hendersons for the last two weeks of August" in chat, and every replacement suggestion it makes is blockout-aware from the start — so the shortlist it hands you after a decline never includes someone who already told you they'd be gone.