T-8 Weeks: Building a Digital Prompt Book That Keeps Every Margin Note

T-minus eight weeks: decide what the prompt book must hold

Eight weeks before opening is a useful point to establish the production's information system. The prompt book is not simply a script displayed on a tablet. It is the stage manager's working record of the production, connecting dialogue, blocking, entrances, technical cues, rehearsal decisions and changes that may affect several departments. A digital version should make those relationships easier to follow. If it takes longer to locate an entrance or confirm a lighting change, the new system is adding work.

Start by listing the documents the production already needs. A typical small-company collection includes the annotated script, contact sheet, rehearsal schedule, blocking notes, cue sheet, scene-change information, rehearsal report template, technical notes and current running order. Separate documents that change frequently from reference documents that should remain stable. This distinction will help determine who needs editing access and which files should be available to the whole company.

• Master script with scene and page references.
• Blocking and entrance notes.
• Lighting, sound, projection and other cue information.
• Rehearsal reports and outstanding action items.
• Production contacts, schedules and emergency procedures.

Choose a document system before choosing a device

A digital prompt book can be built with a document editor, a PDF annotation application, a spreadsheet for cue tracking or a combination of familiar tools. The important questions are practical: Can the stage manager write in the margins? Can an earlier version be recovered? Can the document open without an internet connection? Can another authorized person access it if the stage manager is unavailable? A specialized subscription is not automatically an improvement over software the company already knows.

Check the total cost for the production period. A free application may impose storage, export or collaboration limits. A paid service may charge per user or require a subscription after an introductory period. Confirm supported file formats, device compatibility, account requirements and offline behavior before committing. For a volunteer company, a system that requires every actor to purchase an application creates an unnecessary barrier.

Use a small pilot document before transferring the complete script. Add a handwritten-style annotation, a comment, a cue reference and a revised page. Export the file and open the export on another device. This simple exercise reveals whether the essential information survives when the document leaves the application.

Build a structure that protects the margin notes

The margin is where a prompt book becomes useful. Blocking adjustments, pronunciation reminders, missed entrances and technical clarifications often accumulate beside the printed dialogue. When digitizing a script, preserve page numbers and scene divisions wherever possible. If the source script is a PDF, use an annotation method that keeps comments attached to the relevant page. If the script is a document, use comments or a clearly separated notes column. Avoid placing essential information only in floating text boxes that may move when pages are reformatted.

For example, a note beside a line might read: 'Actor crosses to SR after final word; hold sound cue until door closes.' The note needs a stable connection to the dialogue and an identifiable revision date. A short notation system helps: use a consistent prefix for blocking, sound, lighting and questions requiring director approval. Keep unapproved suggestions visibly separate from confirmed changes.

Create a folder structure that mirrors the production's working relationships. One possible arrangement is a master script folder, a rehearsal folder, a technical folder and a reports folder. Give files descriptive names such as Production_MasterScript_Rev03. Do not rely on labels such as final, final-new or final-revised. A revision number and date make the sequence easier to understand.

Make cue sheets and rehearsal reports part of the same system

A prompt book should connect to the documents that departments actually use. A cue sheet template can include cue number, department, trigger, action, operator, confirmation and notes. For example, LX 12 might be triggered by the actor closing a book, with a note that the transition should begin after the movement rather than on the preceding line. The script reference and cue sheet should use the same cue number. This prevents an update from appearing in one document while remaining absent from another.

A rehearsal report template can record the date, rehearsal hours, attendance, schedule changes, director's notes, production issues and outstanding actions. Keep observations factual and concise. 'The stage-left entrance was blocked by a chair during the second run' gives a department something to address. A general statement that a scene felt disorganized does not identify a practical action.

If text tools help extract dialogue references, entrances or possible cue locations, treat their suggestions as a preliminary index. Script formatting varies, and a character name can appear in dialogue, a stage direction or a cast list. The stage manager must compare each proposed entry with the authoritative script and the director's decisions.

Set permissions, backups and a revision routine

One master copy needs one clear owner. The stage manager can maintain the authoritative prompt book while department heads submit changes through comments or designated documents. Give read-only access to people who need information but should not change the source. This reduces accidental edits and makes it easier to identify which version is current. Establish a cutoff for incorporating changes before rehearsals or technical sessions.

A practical backup routine has at least two parts: a separate copy of important files and an export that can be opened without the original application. For example, save a dated PDF after each rehearsal day and keep a separate backup of the editable source. A cloud account is useful for access and collaboration, but synchronization alone should not be treated as the only backup. Confirm that recovery is possible and that the backup is available to an authorized person.

Production scripts can contain copyrighted material, contact details and sensitive rehearsal information. Limit access to people who need it, avoid public sharing links and establish how long production files will be retained. Check the licensing terms of the script and any software used to store or distribute it. Permission to perform a play does not automatically establish permission to upload its complete text to an external AI service.

• Name one person responsible for the master copy.
• Record revisions with dates and sequential numbers.
• Export a portable copy after significant changes.
• Keep a separate backup and identify who can retrieve it.
• Remove access when production responsibilities end.

The hand-written alternative remains a production tool

A paper prompt book remains sensible when devices are unreliable, the venue has poor connectivity or the stage manager needs to write quickly during movement-heavy rehearsals. A printed master script with numbered pages, removable inserts and a matching digital backup provides a straightforward compromise. The company does not need to digitize every document to gain useful organization.

Before the first rehearsal using the new system, identify a fallback device or printed copy, confirm that essential files open offline and agree on how urgent corrections will be communicated. An elegant digital archive is of little use if the only person who can open it is absent. The immediate next step is to create the production folder, add the current script and cue sheet template, and assign one owner to the master documents.

Questions readers ask