Sunday is a deadline. Plan like it.
The plan, the songs, the files, and the people — one screen, live for everyone. When the drummer declines on Thursday night, the slot reopens with ranked replacement suggestions instead of a panicked group text.
Live
Multi-user plan editing
Ranked
Replacement suggestions
0
Double-booked volunteers
1 click
CCLI usage report
Plans are built from items — songs, announcements, sermon, transitions — each with a length, an owner, notes, and attachments. Lengths sum to a running time with an overrun warning before you're cutting the last song live. Two staff can edit the same plan at once and both see changes as they happen; nobody's edits get clobbered.
Songs carry CCLI numbers, default keys, tempo, and lyrics; arrangements carry their own sequence, key, and BPM. A plan item references a specific arrangement and can transpose per service without touching the original. Every chart is one ChordPro document per arrangement — chords, lyrics-only, and Nashville-number views are renderings of the same source, transposed per service — and every plan use writes a CCLI usage record for your license report.
Teams hold positions; positions get people; every assignment tracks unconfirmed, confirmed, or declined. Volunteers respond from a link or the portal, mark block-out dates in advance, and get automatic reminders. A decline flips the slot to open, notifies the scheduler, and offers ranked replacements — qualified, available, and not over-scheduled.
Volunteers mark unavailable dates once; every scheduler sees the warning before assigning.
Configurable email and push reminders before the service, so nobody discovers their assignment Sunday at 7 AM.
Schedule a team for a month with per-week rotation that respects block-outs and spread.
One ChordPro chart per arrangement, rendered as chords, lyrics, or Nashville numbers and transposed per service — never edited in place.
Every plan use logs the song and CCLI number; the report for your license period is one export.
See what you played and who served across past services — useful for rotation and for January retrospectives.
The position reopens immediately, the scheduler is notified, and SundayHQ suggests ranked replacements — people qualified for the position, not blocked out that date, and not already over-scheduled. One tap sends the invitation.
Yes. Plan editing is live and multi-user: reorder items, change lengths, and edit notes concurrently, and everyone's screen updates without lost edits.
A plan item references an arrangement and can set a per-service key. The chord display transposes for that service without mutating the stored arrangement, so next week starts from the default again.
No. Volunteers respond to assignments from an email link, a push notification, or the member app, where they can also set block-out dates, see their upcoming schedule, and talk to their team in its channel.
Yes — service types template their own positions and default order, and plans are campus-scoped with org-wide rollups, sharing one song library.
Clone a plan, transpose a song, schedule a team, and decline an assignment to watch the replacement flow fire — all in the demo church.