Church & Worship Service Rundown: A Planning Guide
• John Barker
A worship service has a lot of moving parts — music, teaching, media, transitions, volunteer teams, and often a live stream. A well-built rundown keeps it all flowing smoothly so the congregation can focus on the experience, not the logistics.
Why churches need a rundown
Many churches rely on a printed order of service or a simple list of songs and sermon topics. That works for small, informal gatherings. But as soon as you add production elements — slides, video, lighting, live streaming, or multiple services — you need something more structured.
A rundown gives your team:
- Timing — know exactly how long each service should be and track it in real time
- Coordination — worship team, media team, sound, and pastoral staff all work from the same document
- Consistency — especially important for churches running multiple services or campuses
- Preparation — volunteers can review the flow before they arrive on Sunday morning
Building a worship service rundown
Typical service structure
While every church is different, most services follow a recognizable pattern:
| Time | Segment | Duration | Notes |
|---|---|---|---|
| 9:00 | Pre-service music | 10 min | Ambient music, welcome slides |
| 9:10 | Welcome & announcements | 5 min | Host/pastor, announcement video |
| 9:15 | Worship set 1 | 15 min | 3 songs, lyrics on screen |
| 9:30 | Prayer / transition | 3 min | Lighting change |
| 9:33 | Video / testimony | 5 min | Pre-recorded VT |
| 9:38 | Sermon | 30 min | Pastor, sermon slides |
| 10:08 | Response / worship set 2 | 10 min | 2 songs |
| 10:18 | Offering & closing | 5 min | Giving info on screen |
| 10:23 | Dismissal | 2 min | Next service countdown |
This is a starting point — adjust to fit your church’s style and tradition.
What to include in each segment
Song sets: List each song by title, key, and BPM. Note any arrangement changes (“skip bridge on second song if running long”). Include CCLI numbers if you track licensing.
Sermon: Note the expected duration and any media cues — slides, video clips, or scripture references that need to appear on screen. If the pastor uses a teleprompter or confidence monitor, note what feeds they need.
Transitions: The moments between segments matter. Will the lights dim? Does the band play softly under a prayer? Is there a video bumper between worship and the sermon? Plan these — they’re where services often feel awkward if unplanned.
Media cues: Be specific about when slides change, when videos play, and when lyrics appear on screen. “Play video” isn’t enough — note which video, when it starts, and what happens on screen before and after.
Coordinating your team
Worship team
Share the rundown with the worship leader early in the week so they can plan rehearsal around the service flow. Include song order, keys, and any special arrangements. If there are transitions between songs (medleys, key changes), note them.
Media / tech team
Your media team needs the most detail: every slide change, every video cue, every lyric start and stop. Build a column in your rundown specifically for media cues. Consider including confidence monitor content — what does the speaker see vs. what the congregation sees?
Sound team
Note any microphone changes between segments. If the worship set uses 6 microphones but the sermon only uses 1, the sound team needs to know when to transition. Also note any audio playback cues — walk-in music, video audio, background music under prayer.
Lighting
If your church has programmed lighting, include lighting cues in the rundown. Common changes: house lights up for welcome, dimmed for worship, bright for sermon, dimmed for response.
Volunteers
Greeters, ushers, communion servers, children’s ministry handoffs — they all benefit from knowing the timing. “Ushers prepare for offering at the start of the second worship song” is much clearer than “sometime after worship.”
Multi-service and multi-campus
Running multiple services
If your church runs back-to-back services, timing becomes critical. A 5-minute overrun on the first service cascades into the second — and suddenly your children’s ministry handoff is chaotic and your volunteers are stressed.
Build in a realistic changeover gap between services. 15-20 minutes is common but tight. Track your actual timing each week and adjust the rundown based on real data.
Multi-campus
Churches with multiple campuses often share a sermon (via live stream or pre-recorded video) while running local worship and programming. Your rundown needs to account for:
- Sync points — when does the main campus go live? When does each campus need to be ready?
- Local variations — each campus may have different welcome segments, announcements, or worship sets
- Fallback plan — what happens if the stream drops? Have a plan documented in the rundown.
Common mistakes
- No timing on worship sets — “the Spirit leads” is fine, but your children’s ministry team still needs to know when to expect dismissal. Build in flexibility but set expectations.
- Skipping transitions — the moment between the last song and the sermon is often the most awkward part of a service. Plan it.
- Not sharing the rundown with volunteers — if only the production team sees the rundown, everyone else is guessing.
- Reacting to last-minute changes verbally — if the pastor adds a video Saturday night, update the rundown. A verbal heads-up gets forgotten.
Making it sustainable
The key to a great worship experience isn’t perfection — it’s preparation. A rundown doesn’t make your service rigid. It gives your team the confidence to be flexible because they know the plan. When everyone knows the flow, they can focus on what matters: the people in the room.
Explore our worship service templates to get started.
Stay up to date with our latest guides with our email newsletter.
