Worship planning
with the depth your worship director needs.
CCLI tracking per song. Default keys and tempos with per-service overrides. Vocalist and instrumentalist assignments by part. A running service-length total against your target. Attention flags for songs that need rehearsal. The worship director's whole job, in one screen.
Built for the worship director's actual job
Picking songs is the easy part.
Everything around the song is the hard part.
A worship director spends maybe twenty minutes picking the songs for a Sunday. The other six hours go into everything around the song — confirming the key the bass player can actually walk in, finding chord charts in the right transposition, assigning who's singing which part, calculating whether the set runs long, flagging the song the band hasn't rehearsed since March, checking whether you're overusing one writer's catalog. CCLI reporting goes in a separate spreadsheet that nobody updates until quarterly reporting is due.
Most planning tools treat worship as “the music block in the order of service.” A song title, a key, a duration, and that's it. That's a tool for an executive admin, not a worship director.
Worship Planning is built for the person who actually leads worship Sunday morning. Every song carries default settings the band already knows. Every service can override any of them for that specific week. The library knows which songs have been done recently, which ones haven't, and which ones are due for a refresh. CCLI usage is logged automatically. And the total run-time updates live as the set comes together, so the worship director knows if Sunday runs four minutes long before rehearsal — not after.
Every song carries its history. Every history shapes the next set.
A song record holds more than a title. Default key, default tempo, the BPM the click track runs at, chord-chart attachments in every transposition you typically need, lyric files, audio reference, CCLI number, copyright holder, last-played date, and a count of how often it's been led in the last twelve months. When the worship director drops the song into a Sunday plan, every one of those defaults travels with it.
And the library learns from itself. Songs you've led six times this quarter surface with an overuse flag. Songs you haven't touched in a year surface with a freshness suggestion. Songs that've never been led yet flag for rehearsal before they hit a Sunday.
- Default key, tempo, BPM, and click settings per song
- Attached chord charts, lyric sheets, and reference audio
- CCLI number, copyright owner, and publishing administrator tracked per song
- Usage analytics: last led, frequency in the last 90 days, overuse and freshness flags
The song is the song. This Sunday, it's different.
A song's default key might be E. This Sunday, the worship director wants it in D because the guest vocalist sits more comfortably there. Set the override on the service plan — the chord chart regenerates in D, the click track adjusts, the in-ear mix notes update. Next week, when someone else opens the song from the library, it's back to E.
Same pattern for tempo, intro length, ending arrangement, lyric variations, and band assignments. The library holds the canonical version. Each service holds the specific decisions for that week. Neither overwrites the other.
- Per-service key, tempo, and arrangement overrides without touching the song library
- Automatic chord-chart transposition to the chosen key
- Per-song notes for the worship team (intro count-in, ending tag, dynamics)
- In-ear mix presets attachable per service
It's not 'who's in the band' — it's 'who sings the soprano line.'
Worship teams don't schedule people generically. They schedule the lead vocal for song one, harmony for song three, the acoustic player who knows the bridge to song four, the drummer who can handle the click for song six. Worship Planning assigns volunteers by part, not by team slot — and the same person can have different parts in different songs of the same service.
Conflict detection is automatic: if the same vocalist is assigned a harmony part on a song they also lead on, you see it before rehearsal. So is availability: if the person you assigned is already serving in another ministry on the same Sunday, the system flags it.
- Per-song part assignment (lead, harmony, electric, acoustic, kit, click runner, etc.)
- Conflict detection across songs and across ministries
- Availability surfaces from the volunteer scheduler — no double-booking
- Rehearsal calendar pulls from the same assignments
The depth that adds up
Every detail a real worship director already tracks somewhere.
We just put them all in one place.
Running service-length total
Each song carries a duration estimate. As songs come into the set, the total updates against your target service length. Catch the four-minutes-over problem on Tuesday, not during rehearsal.
Attention feed
The set page surfaces what needs attention: songs not rehearsed in 90 days, songs with no vocalist assigned yet, songs missing a chord chart in the chosen key. The director's Tuesday checklist writes itself.
CCLI tracking, automatic
Every song with a CCLI number gets logged every time it's in a Sunday set. Quarterly reporting is a single export — no spreadsheet, no scramble.
Rehearsal scheduling
A rehearsal is its own event tied to the Sunday it's prepping for. The same volunteer assignments and song list apply. Rehearsal attendance flags onto the Sunday plan automatically.
Public song catalog
The songs you've led recently can publish to a public catalog on your church profile, so members searching for “that song from two weeks ago” find it.
Worship-flow analytics
Beyond a single service: the system shows you the arc of how worship has flowed across the last twelve weeks. Tempo distribution, key distribution, lyrical themes, songwriter diversity. Catch ruts before they set in.
What the worship director's week looks like.
Tuesday morning, the worship director opens this Sunday's service plan. The attention feed flags two songs needing vocalist assignments and one song the team hasn't rehearsed since March. She makes the assignments, swaps in a fresher song, and sets a per-service tempo override on the closing piece. Running total reads thirty-eight minutes — exactly her target.
Wednesday, rehearsal. The team pulls up the set on their tablets, sees the assignments by part, and runs through the songs in order. The vocalist who's leading the third song asks for the key half a step lower; the override pushes through, chord charts re-render, and the band has the new charts before they leave the room.
Sunday morning, the click track runs at the right tempo, the in-ear mix presets load, and the CCLI log captures every song automatically. Quarterly reporting happens with one export, not three days of spreadsheet reconciliation.
That's the worship director's actual job — and that's the worship director's actual tool.