How the teams take turns. Each block is a run of Sundays one team serves; the teams follow each other in order.
In the app: Settings → Rotation
First Sunday of the rotation
The Sunday the first team's first block starts. Every block after it follows from this date and the block length.
- Default
- config.yaml's date
- Values
- a Sunday (YYYY-MM-DD)
- Example
- Grace Church started its rotation on 2026-09-06, so Red serves 6 and 13 September, Blue 20 and 27, and so on.
Sundays per block
How many Sundays in a row one team serves before the next team takes over.
- Default
- 2
- Values
- 1 to 8
- Example
- With 4 teams and 2 Sundays each, every team serves about 2 Sundays in 8.
Team order
The teams, in the order they take their turns; drag a team to move it. With one team, it serves every Sunday and its people take turns (see Rules).
- Default
- config.yaml's teams
- Values
- up to 12 team names
- Example
- Red, Blue, Green, Tan.
Sundays a different team serves
Sundays given to another team than the rotation says, without changing the rest of it. Made by dragging one block onto another on the schedule page, which swaps the two teams; listed here, each with "Back to the usual team".
- Default
- none
- Values
- Sunday → team
- Example
- Red is away at camp in November, so an admin drags Red's November block onto Blue's December one, and the two swap.
Sundays with a service cancelled
Sundays when some services are cancelled (one combined service at Christmas). Nobody is scheduled in them, and reminders, My schedule, the calendar feed and publishing leave them out. They can also come from Planning Center Calendar (Calendar changes, below); the ones listed here win.
- Default
- none
- Values
- Sunday → the services cancelled and a note shown to volunteers
- Example
- 2026-12-27: First Service cancelled, "Christmas: one combined service at 10am".