One Long Rehearsal Day or Several Short Blocks: Which Works Better

Every rehearsal plan I review ends up as one of two shapes. The first is a single long day: everyone arrives, the room is set, and the programme is run from the top with tech checks folded in. The second is a set of shorter blocks, perhaps a technical check on one afternoon, a speaker walkthrough on another, and a final run close to the show. Both can work. The question is which one fits the people and the venue you actually have. Learners in the rehearsal scheduling module are asked to draft both versions for the same sample programme, because the differences only show up once you put real start times and names against each block.

In the sample rundown we use in class, a ninety-minute streamed discussion with four speakers, the single day looks tidy on paper. One call time, one lunch, one finish. The split version looks messier, with three separate calls and more emails. That first impression is exactly why people choose the long day, and it is worth examining before you commit to it.

A full day keeps the whole team in one room with the set already built. Nobody has to re-rig microphones or relight a stage between sessions, and problems found in the morning can be fixed before the afternoon run. For venues that charge by the day or only release the space once, this is often the only realistic choice. It also suits programmes with many moving parts that depend on each other, such as a conference with video playback, live speakers and a remote guest. Seeing the whole chain operate in one sitting shows where a handover stalls. A single day gives the stage manager one continuous picture instead of three partial ones.

The cost is stamina. By the third run-through, presenters stop listening to their cues and start reciting them, and technicians who have been standing since early morning make small errors. Speakers with limited availability may only be able to give you two hours of a long day, which leaves the later runs with stand-ins reading their lines.

• One call time and one set-up for the whole team
• Easy to fix a problem and test the fix the same day
• Works when the venue is only available once

Splitting rehearsal into blocks lets each one have a single job. A technical check can run with only the crew present, cameras, sound and playback, without keeping presenters waiting in a corridor. A speaker walkthrough can then focus on timing, stage positions and handovers, with the crew already comfortable with the equipment. This shape also respects availability. A guest who can give ninety minutes on Tuesday and thirty on Thursday can be fitted in without wasting a day of their calendar. Gaps between blocks give you time to revise the cue sheet based on what the first block revealed, so the second block tests the corrected version rather than repeating the same mistakes.

The weaknesses are real, though. Venue access may be restricted, so the set might need to be struck and rebuilt between blocks, which eats time and budget. More calls also mean more chances for someone to miss a message or arrive late. Each block needs a clear purpose written in the schedule, or it drifts into a vague second attempt at everything.

• Each block has one clear purpose
• Presenters rehearse fresh, not tired
• Time between blocks to revise cue sheets

The long day fails most often when too much is packed into the final hours. A schedule that leaves the full run-through until late afternoon means any serious fault found there cannot be corrected, and the team goes home knowing the show has a known weakness. If you choose this option, place the first full run no later than midday. The split plan fails when blocks are vague. A call labelled walkthrough with no stated goal tends to become a loose chat on stage. I have seen three short blocks add up to more total hours than one long day, without any gain, simply because nobody decided what each one was meant to settle.

A shared failure is ignoring travel and setup. Learners often write start times that assume the team is ready the moment the doors open. Build in access time, a short briefing and a clear finish, and state who holds the keys. Those small lines in the schedule are what keep either option from slipping an hour in the first morning.

For most live programmes and streamed discussions, I recommend a split plan with two blocks: a crew-led technical check first, then a combined speaker and crew run close to the show. This keeps the people with the least free time to a single shorter session and gives the crew a head start on the equipment. Choose the single long day when the venue is only available once, when the programme depends heavily on a chain of technical handovers, or when speakers travel in and cannot return. In that case, protect the schedule by placing the full run before lunch and leaving the afternoon for corrections and one final pass.

Whichever you choose, write down why. A one-line reason beside the plan, such as venue access limited to one day, helps the next coordinator understand the decision and adjust it if circumstances change. In class we ask learners to defend their choice in a short note, and that habit alone improves their schedules.

• Two blocks: technical check, then speaker and crew run
• Single day only when access or travel forces it
• Put the first full run before midday

Before committing, answer four things in writing. How many hours does the venue really give you, and when does access begin? Which speakers have a hard limit on their time? Which parts of the programme carry the most technical risk? And who will need the corrected cue sheet between sessions? If the answers point to tight access and uneven availability, lean towards the long day with a strong morning. If they point to flexible access and busy speakers, split it. Write the blocks, name their purposes, and check each against the sample rundown before sending anything to the team.

One last check helps both options. Read the schedule as a presenter would, arriving at the door for the first time. Do they know where to go, when to be ready and what they will be asked to do? If any line leaves them guessing, rewrite it before it reaches their inbox.