Every team knows who’s on, and when.
Rotations that account for who’s actually available, swaps volunteers sort out themselves, and sign-ups anyone can claim. Plus a worship side with a song library, service plans, and a rehearsal view, so the team is on the same page by Thursday.
Nobody quits over the schedule.
They quit over being scheduled the one weekend they told you they’d be away, and then feeling guilty about it.
The schedule is a spreadsheet
One person owns it, it’s out of date the moment it’s sent, and version four is the one in the group text.
Swaps happen in DMs
Two people agree to trade and nobody updates the sheet. Sunday morning, both of them stay home.
The set list arrives Saturday
Which means nobody practiced, which means rehearsal is where you learn the songs instead of where you play them.
Serving & Worship, in detail.
Teams and rotations that respect real life
Build your teams, set a rotation, and let volunteers mark when they’re unavailable before the schedule is built rather than after. Everyone sees their own upcoming slots on the home screen of the app, with reminders that arrive in time to matter.
- Serving teams with their own rosters
- Rotation schedules across weeks and services
- Personal availability, entered by the volunteer
- “My serving schedule” front and centre in the app
Swaps volunteers settle between themselves
Can’t make it? Request a swap and the people who can cover it get asked. When someone accepts, the schedule updates itself: no coordinator in the middle, no spreadsheet to remember, no Sunday morning surprise.
- Swap requests that go to the people who can actually cover
- The schedule updates when the swap is accepted
- Your team lead sees the change without being asked
Sign-ups anyone can claim
Not every serving need is a rotation. Serving opportunities are claimable slots you can open to the whole church, to one team, or to parents only, and when someone claims one, it writes straight back into the schedule instead of living in a separate list.
- Audience-gated: everyone, a specific team, or parents
- Claimed slots write back to the real schedule
- Good for one-off needs: a work day, a funeral reception, a VBS week
Worship, planned properly
A song library your church builds over time, service plans with the order of the whole morning, and a rehearsal view for the room. The team gets it early enough to be ready, which is the entire point.
- Song library the whole team can search
- Per-service plans with ordered items: songs, readings, transitions
- A rehearsal view built for the practice room
- Team sign-up sheets for who’s playing which week
The rest of what Sunday does.
Where this connects
Sunday works on its own, on free Core. Add any of these when you need them (every product shares one directory and one permission system), or get them all with Churchory One.
Churchory Sunday is volunteer scheduling, worship planning and Sunday check-in in one product: rotations built from volunteers' own availability, swap requests, a song library with ChordPro charts, service plans and attendance that shows who's new. It's $99 a year (or $25 a month) on its own, or part of Churchory One.
What problem does Sunday solve?
Volunteers rarely quit over the work; they quit over being scheduled the one weekend they said they'd be away. The schedule is a spreadsheet one person owns, swaps happen in private messages nobody sees, and the set list arrives Saturday night, so rehearsal is where the team learns the songs.
How does it work?
Build your teams
Create teams (worship, tech, greeters, kids, hospitality) with positions and rosters, and choose the services they serve.
Collect availability
Volunteers enter their own blockout dates in the app before the schedule is built.
Fill the rotation
The auto-scheduler fills slots within per-person limits and blockout dates, and can prefer couples together or on different Sundays; adjust anything by hand before you publish.
Plan the service
Build the service plan with songs, readings and transitions in order; the band gets ChordPro charts with live transpose and a rehearsal view days ahead.
Run Sunday
Volunteers get reminders, swaps go to people who can cover, and your welcome team records check-ins and headcounts: who came, how many and who's new.
Common situations
A volunteer cancels Saturday night
They request a swap in the app; the teammates who are free are asked, and when one accepts, the schedule updates and the team lead sees it. No phone tree.
You're short a sound tech next week
Churchory prepares a drafted ask to the people who are free and haven't served lately; you read it, edit it and send it.
The worship leader changes a key on Thursday
Transpose the ChordPro chart once and every musician sees the new key in the rehearsal view.
A family visits for the first time
Sunday check-in records them as new; with Care added, they land on the follow-up list with a named person to welcome them.
What should you expect during setup?
Start with one team. Import or add your volunteers, collect blockout dates for the next two months, and let the scheduler draft a rotation you review. Bring songs in from SongSelect, OnSong or OpenLP files, or Planning Center Services; new churches start with 24 public-domain hymns. Most churches run their first scheduled Sunday within two weeks.
Who uses it?
More questions
Does Sunday include worship planning?
Yes. Service plans, a searchable song library, ChordPro charts with live transpose and a rehearsal view are all part of Sunday.
Can we import our song library?
Yes, from SongSelect, OnSong and OpenLP files and from Planning Center Services.
Can Sunday build our church duty roster?
Yes. A duty roster, serving rota and volunteer rotation are the same thing: who serves where on which Sunday. Sunday builds it from your teams and positions, volunteers' own blockout dates and per-person limits, and everyone sees their dates in the app.
Can volunteers sign up without an account?
Yes. Sign-up links let people claim a slot without creating an account.
How do swaps work?
A volunteer requests a swap, teammates who can cover are asked, and the schedule updates itself when one accepts.
Is Sunday check-in the same as kids check-in?
No. Sunday records adult check-ins, headcounts and new guests; Kids is a separate product for children's check-in with labels and pickup codes. They work together if you own both.
Does each product work on its own?
Yes. Every product runs on Core by itself except Retreat Builder, which needs Events because every retreat is an event. Products light up extra features when you own them together: Groups plus Chat gives each group its own channel, Sunday plus Care puts first-time guests on the follow-up list, and Events plus Newsletters pulls upcoming events into a newsletter.
Can we import our old attendance records?
Yes. The free migration brings up to two years of attendance history, and the history import in Settings → Data & Import has presets for Planning Center, Breeze and a generic spreadsheet if you'd rather do it yourself.
How does Churchory track attendance?
Attendance is captured in the room, not reconstructed on Monday: Sunday check-in and headcounts come with Sunday, group attendance with Groups, and kids check-ins with Kids. Staff see week-over-week history and a list of the groups that forgot to take attendance.
Can we run sign-up sheets for potlucks and work days?
Yes. Events have sign-up sheets with slots people claim (dishes, set-up crew, drivers) with a live count, and slots can be open to everyone, one team, or parents only.