A prompt book can be perfectly clear to its creator and baffling to everyone else. That becomes a problem when someone needs to cover a rehearsal or performance. Build the record with another trained reader in mind from the start. It should show the current script or sequence, the agreed actions and the information required to follow the production. Personal memory can support the book, but it should not be the only place a crucial detail exists.
Agree the structure with the stage-management team and the venue’s working practice. A scripted play, devised piece and movement performance may need different forms. Use clear page or section references and a notation key. Keep changes legible and dated where useful. Do not make an old instruction disappear beneath several layers of unexplained handwriting when the next reader needs to know which action is current.
Record enough context to make a cue meaningful
The University of Alaska Fairbanks stage-manager handbook describes prompt-book development as ongoing through rehearsal and performance processes. That is a useful principle: the book changes as the production becomes more specific. Record the agreed trigger and relevant context using the team’s conventions. A cue number floating beside a page margin is less useful when nobody else can tell what event it belongs to.
Keep department information consistent with the current technical documents. If a cue is renumbered or a sequence changes, update the affected references and communicate the change. Do not let the book, sound list and lighting paperwork describe three different versions of the show. Use the production’s agreed process for technical changes, and leave specialised operation to the trained people responsible for it. Documentation supports competence; it does not replace training.
Include the working information around the script
Keep current contact routes, schedules, presets and emergency arrangements available in the appropriate secure form. Avoid unnecessary personal information in copies distributed widely. The ADC Theatre’s stage-manager guide shows how a real venue connects the prompt-book role with its wider operating procedures. Treat it as an example of a venue-specific system, not a procedure to transplant unchanged into another theatre.
Mark where the approved supporting documents live. If the working system is digital, decide how authorised people access it and what happens when a device or connection is unavailable. If paper is used, keep an agreed backup and a controlled location. A book left in someone’s bag on the far side of the city may be beautifully maintained but unavailable when the company needs it.
Test the handover while there is time
Ask another appropriately trained person to follow a rehearsal with the book. Invite them to flag unclear references, unexplained abbreviations and information that relies on your memory. This is a document test, not a judgement of the person’s skill. Make the confusing parts clearer and repeat the relevant check. A brief planned shadowing session can reveal gaps that a hurried emergency handover would expose at a much worse moment.
When coverage is needed, explain the current production state, recent changes and unresolved issues. Allow time for the covering person to ask questions and observe where necessary. Confirm responsibilities and authority through the production’s arrangements. Do not present a prompt book as sufficient preparation for any person to operate an unfamiliar show safely. The handover must fit the actual role, experience and requirements of the venue.
After the run, archive a useful final version with the agreed restrictions on scripts and production material. Label it as a record of that production rather than an automatically reusable plan for a revival. New people, venues and technical systems will require fresh work. The strongest prompt book preserves what happened clearly enough that the next team can learn from it without mistaking old decisions for current instructions.