Common Stage Management Paperwork Mistakes and How to Avoid Them

Tech week has a way of exposing paperwork. Not the artistic arguments — the small ones. Halfway through a cue-to-cue, the lighting designer calls for cue 47, the board operator is sitting on 45, and the deputy stage manager is reading a page that was reprinted on Tuesday but not Wednesday. Nobody in that room is careless. The system simply was not built to survive contact with a real technical rehearsal. Most of the errors that cause this kind of confusion are ordinary, repeatable, and entirely preventable.

The Prompt Book That Only Its Author Can Read

A prompt book is not a diary. It is an operating document, and it has to work for someone who has never seen the production and is picking it up at short notice. The most common failure is a book that makes perfect sense to the person who built it and very little sense to anyone else.

Look for these habits. Pages added mid-rehearsal but never numbered. Cues written into the margin where the page turn hides them. A blocking note that says “same as before” when the earlier version has since been replaced. Two different abbreviations for the same entrance. No running order at the front, so the only way to find a scene is to flip through ninety pages.

The fix is unglamorous. Number every page, including inserts, and mark inserted pages with a suffix so that “page 42a” is impossible to miss. Keep a contents page that lists scenes, musical numbers, or movement sequences with their page numbers, and update it whenever the book changes. Write in pencil, but keep a dated change log at the back so a decision made on Thursday does not vanish on Friday. And apply one firm rule: when a page is replaced, the old page leaves the building. A prompt book with two versions of the same page is worse than a prompt book with a gap.

Cue Sheets That Assume Too Much

Vague cues are the single most reliable source of friction in a technical rehearsal, because they fail at exactly the wrong moment — when the stage manager is calling and the operator is waiting.

“LXQ 12 — when she crosses” is not a cue. There are at least three moments in that cross where a cue could plausibly land, and each department will choose a different one. A cue needs a number, a department, a trigger written in precise language, and a page reference. If the trigger is a line, quote the line. If it is a physical action, name the action and the person doing it. If it is a point in the music, give the bar or the lyric.

What a working cue line contains

• The cue number and department, written the same way every time
• The page and, where useful, the line or bar number
• The trigger, in specific words rather than a description
• Whether the cue goes on the word or after it — the difference is a beat, and a beat is audible
• Standby timing, especially where a cue follows a short gap
• Any duration, hold, or repeat instruction that affects the operator

Numbering deserves its own paragraph. Collisions between departments are easy to create and miserable to untangle: sound cue 12 and lighting cue 12 both being called “twelve” during a run will eventually produce the wrong cue at the wrong time. Adopt prefixes, agree them before the first tech, and write them on the sheet that goes to the operators, not only in your own book. Where a sequence is dense, use decimal numbering rather than renumbering everything — inserting cue 47.5 costs nothing and spares you a full reprint.

Rehearsal Reports That Record Everything and Tell Nobody Anything

A rehearsal report has one job: to tell the people who were not in the room what they now need to do. Reports that fail usually fail in one of two ways. They bury the single decision that mattered inside four paragraphs about attendance, or they describe the day without ever assigning anything.

The most common omission is the action line. “The sofa felt too far upstage” is an observation. “Move the sofa one metre downstage before Wednesday; props to confirm the new position” is an instruction with an owner and a deadline. Observations are useful, but they should never be mistaken for requests.

Three other habits cause trouble. Writing opinions as facts, so a note reads like a company decision when it was one person's comment. Sending the report the following afternoon, by which time the workshop has already started building the wrong thing. And copying everybody, which reliably produces a group of people who assume somebody else has read it. Keep the distribution list deliberate, and mark clearly who must act and who is merely being kept informed.

Version Control: The Quiet Source of Half Your Confusion

Most paperwork errors are not errors of content. They are errors of edition. Two people are working correctly from two different documents.

Date-based file names solve more of this than any other habit. A file called “rehearsal notes final” tells you nothing; “rehearsal notes 11 March” tells you everything, and it sorts itself in a folder. Keep one master copy in one agreed location, and make it explicit that printed copies are disposable. When something changes in the room, announce it, then update the master the same day — never the other way round. If a change is announced but not recorded, it will be rediscovered during tech by somebody reading an older page.

Timing and Distribution

Paperwork delivered at the wrong moment is nearly as bad as paperwork that is wrong. Cue sheets handed out as the technical rehearsal begins will be read while the operators are also being asked to focus. Aim to have cue sheets distributed with enough time for a read-through before the first cue-to-cue, and keep a spare set at the desk.

For rehearsal reports, decide a deadline and hold it. A short report sent the same evening beats a thorough one sent two days later, because by then the decisions have been made without it. If you cannot finish the full report, send the actions first and the narrative later.

Small Formatting Habits That Save Hours

None of these are dramatic. Together they remove a surprising amount of noise from a technical rehearsal.

• One cue per line, always, even when two cues fall on the same word.
• One agreed vocabulary — if it is a “standby” in the book, it is a “standby” everywhere.
• Date and initial every revised page, so an old sheet can be identified on sight.
• Highlight changes rather than rewriting the whole document.
• Leave a margin wide enough to write in, and use it.
• Read your own cue sheet aloud as if calling it, before you hand it over.

Before You Walk Into Tech

Run a short audit the day before the technical rehearsal. Check that the prompt book has a current contents page and no duplicated sheets. Check that every cue has a number, a trigger, and a page reference, and that the numbering does not clash across departments. Check that the distribution list is current and that everyone on it has the latest version. Then read the last three rehearsal reports and confirm that every action in them has been closed, reassigned, or consciously dropped.

It takes perhaps an hour. It will not make the technical rehearsal easy — technical rehearsals are not supposed to be easy — but it will keep the confusion where it belongs: on stage, in the work, and not in the paperwork.

Photo: Pexels / Pixabay