Free working document
The Six Week Church Rota Build Checklist
The exact sequence a small church coordinator can follow to publish six covered Sundays and stop arranging cover by text message on Saturday night.
This is the checklist behind a rota that holds. It assumes one coordinator, a roster in the dozens, volunteers who serve about once a month, and no staff to delegate to. Work through it once and you have six Sundays published. After that you extend the window by one Sunday each week, which takes about twenty minutes.
Nothing here needs software to be useful. It works on paper or in a spreadsheet, and churches have run it that way for years. What software changes is the chasing: the reminders, the confirmations and the swaps that otherwise land in your evenings. Start with the sequence, then decide what you want to automate.
Six Sundays out: fix the slot list
Five Sundays out: put names in slots
Three Sundays out: publish, confirm, open swaps
Sunday morning and the Monday after
How to use it
Use it first as an audit rather than a build. Take last month's rota and run it against the four stages: was the slot list current, did people get their dates six weeks out, was there a written swap deadline, did anyone log the no shows. Most small churches find they do the first stage well and the last stage not at all, which is exactly why the same gaps keep reappearing.
Then run it forward for one full cycle before you change anything else. Six Sundays is long enough to see whether the swap deadline holds and whether the bench is real, and short enough that you can correct without a season of damage. Keep the completed sheets. When your next coordinator takes over, six months of them is the best handover document you can give.
Send me the editable copy
Send it to your inbox as an editable checklist you can adapt to your own slot list and hand to the next coordinator.
Questions about this document
Our church is smaller than 150. Is six weeks too far ahead?
Six weeks is about right even for a congregation of sixty, because the benefit is planning rather than volume. A volunteer who can see their dates a month and a half out swaps far less often. If your roster is very small, keep the six week window but shorten the slot list.
What if volunteers ignore the swap deadline anyway?
Some will at first, especially if the old habit was texting you directly. Hold the line for one cycle by routing late requests back to the team rather than solving them yourself. The deadline becomes real once people see that it is the route that actually gets their Sunday covered.
Can one person really run this alongside another job?
Yes, once it is built. The initial cycle takes an evening because you are writing the slot list and role descriptions from scratch. After that you are extending by one Sunday each week and chasing a handful of unconfirmed names, which is a twenty minute task.
From the checklist to six published Sundays
The checklist gets you a slot list, a written swap deadline and a printed sheet for the check in desk. PewRoster runs that same sequence every week, so extending the rota by one Sunday takes about twenty minutes instead of an evening of messages. Book a demo and we will publish your first six Sundays alongside you.