A Rehearsal Report Should Tell You Whether the Track Needs to Change

A rehearsal report should make the next rehearsal easier. For a production using backing tracks, that means recording exactly what happened, deciding whether the company or the audio needs to change, and giving every real track revision an unambiguous owner.

The phrase “music felt late” is not enough. Neither is “need a new track.” A useful note names the file, the moment onstage, the version rehearsed, the requested result, and who will approve it.

The short answer

Turn a rehearsal note into a backing-track revision request only after you can answer six questions:

1. Which exact file and version was used?
2. Where did the problem occur?
3. What was happening onstage at that moment?
4. Is the problem in the performance, staging, playback, or track?
5. What specific change would solve it?
6. Who must review the result before it replaces the current file?

If those answers are not clear, the next step is usually another focused rehearsal test—not an audio edit.

Start with the observed fact

Write what the room could see or hear before writing a solution.

Weak note:

Track is too fast.

Useful observation:

In Q07_Finale_ACCOMP_v3.mp3, the ensemble reached the downstage formation about four seconds after the instrumental transition began. The same delay occurred in two runs.

That note does not yet assume the tempo must change. It gives the director, choreographer, music director, stage manager, and track producer a shared event to discuss.

Useful observations often include:

• the spoken line or stage action before the cue;
• the lyric, rehearsal mark, or time stamp where the issue begins;
• the file and version used;
• whether the issue repeated;
• who was performing or operating playback;
• and what happened immediately afterward.

Separate four kinds of notes

Most rehearsal problems belong in one of four lanes.

This separation matters because an edited track cannot fix an unclear cue call, an unlearned entrance, or an old file in the playlist.

It also protects the production from accumulating unnecessary versions. When every rough rehearsal moment becomes a new export, the company soon has several “final” files and less confidence about which one belongs in the show.

Use one line for every actionable note

A compact track-note table can live inside the rehearsal report.

The table should show the current decision, not every conversation that led to it. Keep detailed discussion elsewhere if the team needs it.

Name the location three ways when possible

The fastest revision requests are easy to find.

Use more than one landmark:

• the time stamp in the exact audio file;
• the lyric or spoken cue;
• the rehearsal mark, bar number, or section name;
• the stage action;
• and the musical event, such as “second chorus pickup” or “final dance-break button.”

For example:

At 1:18 in Q05_Opening_ACCOMP_v5.mp3, on the lyric pickup after rehearsal mark C, the confirmed costume reveal needs two additional bars before the ensemble entrance.

That is much safer than “add time before the chorus.”

Describe the production need before the audio solution

A track producer can often offer a better solution when the request explains what the show needs.

Instead of:

Make the intro longer.

Try:

The actor finishes the downstage dialogue, crosses to the platform, and needs to hear a clear two-bar pickup before the first sung entrance. The current file begins the vocal pickup before the cross is complete.

Possible solutions might include a longer introduction, a vamp, a cleaner cue point, a new count-in, or a staging adjustment. The production need helps the team choose among them.

The same approach works for:

• a key that does not fit the confirmed singer;
• a cut that needs to match approved staging;
• a dance break that needs a restart landmark;
• rubato that must support a live breath or gesture;
• an ending that must land with a blackout;
• or orchestration that masks an important vocal entrance.

Preserve the file that proved the problem

Do not rename, overwrite, or remove the rehearsed file until the note has been resolved.

Keep:

• the exact source filename;
• the version number;
• the rehearsal date in the report;
• the current approved status;
• and a short note about what replaces it.

When a revision arrives, compare it against the original problem before distributing it to the cast. A new export is not approved merely because it is newer.

A practical pattern is:

Q##_SongTitle_FileRole_v##.mp3

Avoid names such as:

• final.mp3;
• final-new.mp3;
• use-this-one.mp3;
• and latest-really-final.mp3.

Version numbers are not glamorous. They are reliable.

Test the smallest useful section

The company does not need to run the entire number every time one detail changes.

For a revised file:

1. Begin before the affected cue.
2. Run the stage action into the musical moment.
3. Continue far enough to confirm the exit from the change.
4. Repeat once under normal rehearsal conditions.
5. Record whether the problem is solved.
6. Update the approved version in the report and playback folder.

Then schedule a full-context run when the change affects tempo, continuity, choreography, dialogue timing, or the next cue.

The (Broadwaytrax sitzprobe planning guide) can help the company test performance files in musical context before tech.

Give approval to one named role

Avoid distributing a revised track because several people said it “sounds better.”

Name:

• who requested the change;
• who confirms it matches staging;
• who confirms it works musically;
• who approves the file for performance;
• and who replaces the file on primary and backup playback systems.

One person may hold more than one role on a small production. The important part is that the final approval is explicit.

Keep rights and revision decisions separate

A practical track request does not automatically establish permission to change protected material.

Confirm the production’s show license, approved script and score materials, and any permissions required for cuts, lyric changes, added repeats, altered orchestration, recording, or streaming. A theater-use license for a sound recording is separate from grand rights or permission to present the musical.

The (Broadwaytrax theater-use guide) explains that distinction for schools and theater teams. When a requested change touches protected material, check with the publisher, licensing house, or rights holder.

Send a complete custom-track brief

When rehearsal has confirmed a real audio need, include:

• show and song;
• exact source file and version;
• requested key, cut, tempo, cue, lead-in, vamp, ending, or orchestration adjustment;
• time stamp plus lyric, bar, rehearsal mark, or stage action;
• the production reason;
• reference audio or score material only when you have permission to share it;
• deadline for the next rehearsal test;
• and the person who will approve the result.

(Broadwaytrax custom-track support) can help with single-track revisions and broader production packages built around confirmed singer, staging, cue, and performance needs.

A practical rehearsal-report checklist

• Record the exact file and version used.
• Write the observed problem before proposing a solution.
• Name the time stamp and at least one musical or staging landmark.
• Classify the note as performance, staging, playback, or track.
• Test the smallest safe non-audio fix first when appropriate.
• Explain what is happening onstage.
• Assign one owner and one due point.
• Keep the source file until the revision is approved.
• Test the new file in context.
• Update both primary and backup playback folders.
• Remove superseded files from the live playlist.
• Confirm protected changes with the appropriate rights holder.

FAQ: rehearsal reports and backing-track revisions

Should every track problem go in the rehearsal report?

Record any issue that affects the next rehearsal, the approved performance file, or another department. Brief learning notes can stay with the music director; shared production decisions belong in the report.

Who should request a custom edit?

The request can come from the director, music director, choreographer, stage manager, or operator, but the team should name one person who consolidates the brief and one person who approves the result.

What if the team is not sure whether the track or staging is wrong?

Run a focused test using the exact current file. Change one variable at a time, record what happens, and request an edit only when the production need is clear.

Can we overwrite the old file after a revision?

Keep the prior approved version until the replacement has passed rehearsal and playback checks. Then archive it outside the live playlist rather than leaving multiple ambiguous versions in the performance folder.

How much context does a track producer need?

Enough to locate the moment and understand the production result. Include the file version, time stamp, musical landmark, stage action, requested outcome, and deadline.

The takeaway

A useful rehearsal report turns a vague frustration into a testable production decision. Name the file, locate the moment, separate human and playback issues from real audio needs, and give the confirmed request one owner. That process creates fewer revisions, clearer approvals, and a performance playlist the whole company can trust.