Worship Team Rehearsal Plan: Run One in Under 2 Hours

Most worship rehearsals run in Sunday order. The band plays song one, then song two, then song three, and by the time they reach the difficult song everyone is tired and the clock is running out. Transitions get skipped. The run-through never happens. And on Sunday morning the weakest part of the set is the part nobody had time to fix.

This article lays out a rehearsal that fits in well under two hours, and explains how to prepare so the time is used on the music rather than on explaining the plan. It draws on Don Chapman of WorshipIdeas, Planning Center's own help guides and a church technology writer at techtalk.church.

Practice is personal, rehearsal is relational

Don Chapman's principle is the one that makes everything else possible: volunteers learn their parts at home during the week, and rehearsal is where the team assembles the service. If musicians are hearing the songs for the first time at rehearsal, he writes, that is a leadership problem, not a musician problem.

So the work starts before the rehearsal. Planning Center's help pages list what a leader should have ready:

• Team members scheduled and notified, even before the music is ready.
• Rehearsal times added to the plan, with every team that needs to attend assigned to them.
• Reminder emails for rehearsal and service times, especially when you schedule weeks ahead.
• Songs added to the service order, with song leaders assigned.
• Files attached to each song, in the right arrangement and key.
• An email to the team once the songs are final, and again after any important change.

Planning Center also encourages teams to practise ahead of time using its media player, its Music Stand app or a PDF songbook.

One writer at techtalk.church describes a routine for their Thursday rehearsal: songs chosen several weeks out, then on the Monday before, a note to the team listing each song's key, who leads it and anything different from last time, such as how the transitions will work. The advice is to give the team resources early, so that unpreparedness is never the leader's fault, while accepting that you cannot make people practise. Another tip from the same writer: say which is the authority. On that team, the recording is a reference for feel and style, while the chart decides chord changes and sequence.

How long should it be?

Don Chapman recommends 75 to 90 minutes for a volunteer team. A planning-app vendor, OnStage, suggests 60 to 90 minutes and sending materials 48 hours before. Both are well under two hours, and both assume the setup is done before the clock starts.

That caveat matters. Chapman says musicians should arrive early enough to plug in, tune, set monitors or in-ears, load charts and fix obvious gear problems, and that leaders should arrive first so systems are ready. The rehearsal clock should not begin with everyone still setting up.

The order: risk first, not Sunday order

Chapman's plan rehearses in order of risk. The song most likely to fail goes first, while everyone is fresh. Here is his schedule.

These blocks add up to roughly 90 to 97 minutes, so if you need 75, shorten the sound check, vocals or trouble-spot blocks first and protect the run-through. Here is what each block is for.

• Prayer and overview. Briefly explain the theme, the Scripture or pastoral emphasis, the song order and any unusual cues. It does not need to be a long devotional.
• Sound and monitor check. Use the intro, verse and chorus of the first song to confirm house sound and monitors, and keep it under seven minutes. If you use in-ears, our guide to in-ear monitor mixing covers how to build the mixes.
• Hardest or newest song first. A new song, a tricky groove, a key change, an exposed intro. Do not start with song one just because it is first on Sunday.
• Transitions and service flow. Chapman says this is where most rehearsals fall apart, because most leaders skip it. Rehearse count-offs, pads, who starts the next song, capo changes, prayer-into-song moments, Scripture readings, handoffs and even planned silence.
• Vocals. Lead entrances, harmonies, blend, cutoffs, who sings which verse, and how singers re-enter after a spoken or prayer moment.
• Endings and cues. Endings, repeats, stops and "watch me" cues. A shaky ending is the last impression people take home.
• The run-through. Chapman calls this the most important part. Run the whole set as close to service conditions as possible, including speaking, prayers, Scripture, countdowns and slides, and do not stop unless something truly breaks. Set a hard start time and protect it.
• Final notes. Only essential fixes, the call time, the main cues, a prayer, and release on time.

If you only have 60 minutes

Chapman's shorter version keeps the same order: 6 minutes for prayer and overview, 6 for the sound check, 13 for the hardest song, 13 for transitions, 9 for vocals, endings and cues, 11 for the run-through and 2 for final notes. For 60 minutes he would not try to play every song several times. He would drill the risky sections and protect the run-through, which he calls non-negotiable at any length.

Principles that hold it together

• Send the plan early. Service order, keys, charts, recordings, song maps and transition notes should reach the team early in the week.
• Rehearse by risk. The newest or least-known song first, then transitions, dynamics and response moments.
• Keep the run-through sacred. It is the first thing to get cut when rehearsal runs long, and the one that matters most on Sunday.
• Bring in the technical team. If slides, videos, countdowns or tracks affect the flow, the people running them should be in the run-through. Our article on media team scheduling explains why sound, cameras and slides need their own people.
• Start on time and finish on time. Chapman says honouring volunteers' time builds a culture where people want to come back.

If you are still building the set itself, see our guide to a Sunday worship setlist that flows.

How Planify can help

A rehearsal only works if the right people are in the room.

• Positions for each role. Create vocals, keys, guitar, bass, drums and sound positions in your music department, with a coordinator for each. Each position can have a minimum and a maximum number of people.
• Confirmation by tap. Musicians confirm or decline on WhatsApp, so you know before the rehearsal who is coming.
• Cover from the same position. If someone declines, Planify can ask colleagues who cover that position.
• Unavailable periods. The monthly planner, the open call and cover requests take members' unavailable periods into account.
• Announcements. Send the plan, or a change to it, to a department or position as a short message.

Planify does not hold your charts or recordings. Keep those in your chart app and use Planify for the people.

Which features you get depends on your plan.

Read next: media team scheduling: why sound, cameras and slides can't be swapped.

FAQ

How long should a worship team rehearsal be?

Don Chapman recommends 75 to 90 minutes for a volunteer team, and OnStage suggests 60 to 90. Both assume setup and tuning happen before the official start.

Why start with the hardest song?

Because the team is fresh. Chapman says leaving the hard material for the end means it gets rehearsed when everyone is tired and thinking about dinner.

Should we rehearse the transitions?

Yes. Chapman says most rehearsals skip them, and that awkward gaps on Sunday come from not practising the moments between songs.

How early should the team get the songs?

Early in the week at the latest. OnStage suggests 48 hours before rehearsal, and techtalk.church describes sending keys and notes on the Monday before a Thursday rehearsal.

What if rehearsal runs out of time?

Cut other blocks and protect the run-through. Chapman says it is the one thing that should never go.