Run-of-show for the booth.
Staffing for the building.
A cue list with audio, video, lighting, and slide rows, role assignment per row, and an asset library that knows which mic, which scene, which template. Plus the volunteer side: who's on, who's confirmed, who's a no-show risk for Sunday. The two halves of execution, in one place.
Production and people, planned together
A service doesn't happen because the order is written.
It happens because someone's on the board, and someone's at the door.
There are two distinct hard problems in getting a Sunday on its feet. The first is technical execution: every cue, every transition, every mic level, every slide change, every lighting scene — choreographed so the service runs without a visible seam. The second is human execution: the greeters at the front door, the ushers handing out bulletins, the kids workers in the rooms, the parking team in the lot, the camera operator at the back of the room.
Most churches plan these two problems in separate tools — a Google Sheet for the cue list, a sign-up form for volunteers, a group chat for the last-minute swaps. The result is predictable: the cue sheet is out of date by Saturday, the volunteer board has three holes nobody catches until Sunday morning, and the production team and the hospitality team are working off different versions of what's actually about to happen.
Production & Logistics is one workspace for both halves. The cue list and the volunteer board read from the same service record. When the worship director swaps a song, the production cue list rebuilds. When a volunteer cancels Friday night, the logistics view flags it before Sunday. When the cue requires a second camera operator, the volunteer assignment is already there. Execution becomes one coordinated motion instead of two parallel ones held together by group chat.
One ordered list. Audio, video, lighting, slides — all of it.
The cue list is the executable version of the service plan. Every row is a cue, every cue carries a type (audio, video, lighting, slide, transition), every cue has a role assigned to fire it. Pull up the cue list on a tablet in the booth and run the service top to bottom — or print it as a cue sheet for someone who prefers paper.
Cues link to the asset library. An audio cue points at a specific stem. A lighting cue points at a preset scene. A slide cue points at a slide deck or a song's default slide template. When the worship director adds a new song in the worship tab, its default lighting and slide assets travel into the cue list automatically.
- Cue types: audio, video, lighting, slides, transitions, in-ear mix changes
- Role assignment per cue (FOH engineer, lighting op, slide op, etc.)
- Tablet-ready format for live use, printable as a cue sheet for paper-preferring techs
- Cue notes, hold/standby/go markers, and run-time estimates per cue
The booth's memory, organized.
Every church accumulates a library of slide templates, lighting scenes, intro videos, lower-third graphics, microphone assignments by musician, and walk-in music playlists. Most of it lives in someone's head, or in a folder on someone's laptop. When that person is sick on a Sunday, the service feels different.
The asset library makes the booth's knowledge institutional. Every slide template, lighting scene, audio stem, and standard transition is named, tagged, and reusable. New volunteers ramp up faster because the library is searchable. The veteran tech can take a Sunday off and the service still runs the way it should.
- Tagged, searchable library of slide templates, lighting scenes, audio stems, transitions
- Per-asset usage history — see when each asset was last in a Sunday
- Default assets per song, per service type, per campus
- Asset library survives staff turnover — the booth's memory becomes the church's
Who's on. Who's confirmed. Who's about to flake.
The logistics view is the live state of every team that needs a person on Sunday — greeters, ushers, parking, hospitality, kids workers, production, worship. Each slot shows the assigned person, their confirmation status, and a risk flag if they've no-showed recently or haven't responded to the assignment.
Volunteer coordinators see the holes before Sunday morning. Members get reminder notifications on their own cadence. And when a last-minute cancellation happens, the swap-suggester surfaces candidates who've served the role before and are likely available.
- Live staffing board for every Sunday team — coverage and gaps at a glance
- Confirmation tracking with automated reminders
- No-show risk flagging based on response patterns
- Last-minute swap suggester surfaces qualified, likely-available members
The pieces that make Sunday actually go
Beyond the cue sheet and the board.
Tech rehearsal mode
Run the cue list in rehearsal mode the night before. Walk every cue, fix the timing, save the refined version as Sunday's baseline. The mode tracks rehearsal completion so the morning of, the team sees which cues were actually rehearsed and which weren't.
Volunteer availability + conflicts
Every volunteer has a recurring availability window and a per-week override. Cross-ministry conflicts surface before scheduling — the worship vocalist who's also assigned to greet doesn't make it to either role.
Child labor compliance
For minors serving in any capacity, the system tracks parental consent, age-appropriate role limits, and serving-time caps. Compliance isn't an afterthought — it's in the assignment flow.
Served-recently flagging
Volunteer rotation surfaces the people who've served four weeks in a row, so coordinators can give them a Sunday off before burnout sets in. And the people who haven't served in months, so they can be invited back.
Run-time variance tracking
After each service, the system logs estimated vs. actual run time per cue and per service. Over weeks, the data shows where the service consistently overruns — usually one or two specific segments — so the team can plan smarter.
Multi-campus execution
The cue list and logistics view scope to a campus. The same service plan can drive coordinated execution at the central campus and the satellite, with campus-specific assets and volunteer teams.
Sunday morning, in the booth and at the door.
7:30am. The FOH engineer arrives, opens the cue list on the booth tablet, and sees this morning's run-of-show, including the last-minute song change from Saturday rehearsal. The slide template for the closing song is already linked. The lighting scenes are pre-loaded. The in-ear mix preset for the guest vocalist is ready to load when she takes the stage.
Meanwhile, at the door, the lead usher pulls up the logistics board on her phone. Three of the eight greeter slots are confirmed; two are unconfirmed; one no-showed last week. She fires the swap-suggester for the unconfirmed slots, two members respond within ten minutes, and by 9am the board is full.
The service runs clean. The cue list shows actual times versus estimates as the morning unfolds. By 12:15, the post-service data is already populating the follow-up tab. Nobody is messaging anyone in a group chat. Nobody is reconciling versions of a spreadsheet.