Cue Sheet Change & Reapproval Register — Excel
After changing an approved cue sheet, retest the affected video, audio, lighting and show cues. Record what is still awaiting approval and who has received the revised sheet.
A record of the request, retest, approval and withdrawal of old cue sheets.
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 24 Oct 2026
- Use this for
- Use when running order, media, speech or entrances change after rehearsal approval. Keep the earlier version.
When to use it
Use when running order, media, speech or entrances change after rehearsal approval. Keep the earlier version.
A department check is not overall use approval. Assign approvers according to actual operating authority, not the fictional role allocation.
Start with the guide: Event Cue Sheet Changes and ReapprovalFill in the template step by step
When to use it
Use when someone requests a change after final cue-sheet approval.
What to have ready
- Approved cue sheet
- Revised media or script
- List of teams that must confirm
- List of file and printout recipients
Record the previous version, requester and proposed change.
Find which adjacent cues, performers, files, staffing or timings are affected and name the responsible teams.
Retest that segment through the actual screens, sound and lighting. Record each team’s reply.
After overall approval, send the new version and withdraw the old files and printouts.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Change ID and previous version | Who requested what change? | Affected teams and files | Change to costs and timings | Segment to retest and test record | Teams confirmed or awaiting reply | Person approving use and time | New version and recipients |
|---|---|---|---|---|---|---|---|
| CH01 / RUN-v4 | Programme lead Choi requests a ten-second cut to the Q22 introduction | MC-v5 and waiting video cue V22 affected | No cost; presentation starts ten seconds earlier | Q21→Q23 retested 2026-11-08 15:10 / RH01 | Presenter, video and audio have confirmed | Stage manager Lee / 2026-11-08 15:20 | RUN-v5 sent at 15:25; four teams confirmed receipt |
| CH02 / RUN-v5 | Content lead Park requests a 51-second award clip in place of the 45-second clip | V020-v4; entrance Q31; music A31 | Entrance moves six seconds later; presenter cue card needs updating | Must retest main/backup files and transition to the next microphone | Video file received; audio and presenter checks still outstanding | Use held / 2026-11-08 16:15 | Keep using RUN-v5; mark the proposed version DRAFT-v6 |
| CH02-R1 / RUN-v5 | 51-second video and later entrance confirmed | V020-v4, MC-v6 and A31 use the same delay | No extra cost; waiting time adjusted to keep the same finish | Transition retested at 16:40; RH02 video and audience check recorded | Video, audio, lighting and presenter confirmed at 16:45 | Stage manager Lee / 2026-11-08 16:50 | RUN-v6 received at 16:55; four printed RUN-v5 copies collected |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Change ID and previous version | Who requested what change? | Affected teams and files | Change to costs and timings | Segment to retest and test record | Teams confirmed or awaiting reply | Person approving use and time | New version and recipients |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- Figure 53 · QLab 5 The Workspace
Adapted checking the cue target and actual video/audio routing during handover and change verification.
- HSE · Managing an event
Adapted coordination, named monitoring responsibilities and communication of changes. UK legal duties and technical limits are not presented as Korean requirements.