How to Create a Stage Cue Sheet for a Solo Act
- How do you create a stage cue sheet?
- What does the sheet do, and what does it leave out?
- What must you agree with the venue first?
- Which fields belong in the header?
- How do you describe a trigger precisely?
- What would a small cue sheet look like?
- How are standby and execution different?
- What should you check at the paper review?
- What changes when you revise the track?
- How do you hand over the final version?
- Sources
How do you create a stage cue sheet?
Create a stage cue sheet by listing each requested technical change, its exact trigger, the intended action, and the responsible venue role. Identify the matching track version and confirm the sheet with the person calling the act. Rehearse and update it together. This is a communication document: leave equipment operation, overhead work and electrical changes to qualified, venue-authorized personnel and licensed trades where required.
A great entrance can be extravagant. Its paperwork should be easy to read. This guide builds an original example for a fictional solo number called The Last Invitation. No performance, timing trial or venue acceptance is claimed.
What does the sheet do, and what does it leave out?
A cue is the agreed signal for a change in the performance. Your sheet connects that change to something the team can identify. It should help the recipient answer: which moment, which action, and whose responsibility?
StageAgent's sound-cue resource identifies cue numbers, descriptions, timing and notes, including trigger and responsibility. Those are useful starting fields; the expanded worksheet below is our editorial design, not an official industry form.
A sheet is also not a complete prompt book. Theatrecrafts describes a prompt book as the master script or score containing movement and technical cues, alongside broader production information. A short solo-act request may feed into the venue's existing calling documents. Ask what the recipient actually needs rather than sending a second competing system.
Keep costume construction, makeup application and equipment setup outside this sheet. Link or identify the relevant supporting document when a technical decision depends on it.
What must you agree with the venue first?
Ask who receives the document, who approves technical requests, who calls the act, and who operates sound and lighting. One person may cover several roles; do not assume that arrangement. Record the actual agreed names or roles before treating a draft as ready.
Confirm the required delivery format and how the team wants revisions sent. Ask whether their template or numbering replaces yours. A polished spreadsheet is still a draft if nobody responsible for the show has agreed to use it.
Keep requests separate from confirmed capabilities. "I would like a warm opening look" describes an artistic request. "Opening look approved by lighting lead" records a decision only after that decision exists. Do not fill in approval fields because the show date is approaching.
Equipment boundaries belong here, before any technical rehearsal. University of California lighting guidance identifies electrical and overhead-lighting hazards and restricts board and dimmer operation to trained, qualified employees. Ask the venue's authorized technical staff to implement approved changes. Do not climb, reposition fixtures or change electrical connections to obtain the requested look.
Connecticut College's theater safety guidance assigns rigging work to qualified personnel and electrical work to licensed electricians. A written cue does not authorize either task. Keep emergency routes clear and use the venue's emergency procedures if a hazard arises.
Which fields belong in the header?
Our suggested header makes the document identifiable before anyone reads a cue:
- Act title and performer or project identifier.
- Venue and performance date, once confirmed.
- Sheet revision and issue date.
- Exact playback filename and the matching edit/version.
- Recipient and caller, with confirmation status.
- A short key explaining any abbreviations the team has accepted.
For the fictional example, the draft header reads: The Last Invitation; cue sheet revision 2; playback Invitation_Edit_B; venue assignment pending. This is enough to distinguish it from a previous edit, but it is plainly not an approved show document.
Use a filename you can compare letter for letter with the file actually delivered. If several files share a similar name, list the one intended for this act and resolve the others before rehearsal. "Latest track" is not a useful identifier after another edit arrives.
How do you describe a trigger precisely?
Separate the trigger from the result. "When the performer closes the envelope" identifies an observable action. "Change to the agreed closing look" describes the requested result. "Make it dramatic" does neither quite well enough; drama has excellent taste and unreliable administration.
Theatrecrafts recommends clear, visible landmarks for movement-based pieces and concise descriptions of what the caller can see. Use that principle when your act lacks spoken text. Confirm that the assigned caller can actually see the action from their working position.
A timestamp can help identify a location in a particular recording. State where the clock begins. In our example, 00:00 means the start of the delivered playback file, not the performer's entrance or the host's introduction. If the intended trigger is an action, label the timestamp as a reference rather than silently substituting it for that action.
For repeated sounds or movements, distinguish the occurrence. "The envelope closes for the second time" is more specific than "envelope closes." Rehearsal must establish whether the moment remains identifiable; the wording alone does not establish that.
What would a small cue sheet look like?
Here is an original planning example. The labels are provisional, not universal theatre notation. All actions require venue agreement; the lighting looks are descriptions, not console settings.
| Draft label | Trigger or condition | Requested result | Responsible role to confirm |
|---|---|---|---|
| OPEN | Caller confirms the agreed opening readiness conditions | Establish the approved opening look before the entrance | Lighting operator |
| PLAY | Caller gives the agreed playback start signal | Start Invitation_Edit_B from its beginning | Sound operator |
| TURN | Performer closes the envelope for the second time; reference 00:36 in Edit B | Change to the approved contrasting look | Lighting operator |
| FINISH | Final recorded sound ends; reference 03:20 in Edit B | Retain the agreed visible closing look for the planned ending | Lighting operator |
For the example, the performer remains in the closing picture before leaving by the agreed route. There is no automatic blackout instruction. The team must separately establish the exit and transition into the following act; this table does not replace those decisions.
The sheet could include a separate notes column, but do not hide an unresolved dependency there. If TURN depends on a sightline that has not been confirmed, mark that row unresolved. A footnote should not turn uncertainty into apparent approval.
How are standby and execution different?
In the University of Alaska Fairbanks handbook, cue calling distinguishes an optional warning, a standby, and the execution call ending in "go." Its account also includes operator acknowledgments. These are coordinated communications, not decorative words to place beside a timestamp.
Confirm the venue's vocabulary and who gives each call. Do not invent a second signal from the stage or assume that an informal remark authorizes an operator to act. Have the caller transfer the agreed information into their working format.
Do not copy a universal number of seconds for every standby. The preparation needed for a cue differs; the caller and operators should establish the workable placement during rehearsal. The performer-facing sheet records their agreed arrangement rather than prescribing a headset technique.
What should you check at the paper review?
City Tech's cue-calling course separates making a cue list, creating calling material, attending paper tech and rehearsing cues. Its required documents include a calling key, master cue sheet and marked calling pages. That distinction is useful: writing the table is one stage of preparation.
Our suggested review is a conversation with the designated recipient, before testing technical changes. Work through one row at a time. Ask the recipient to describe what they understand, then compare that interpretation with the intended moment.
For TURN, the unresolved questions might be: Is the second envelope closure visible? Is the reference time tied to Edit B? Which approved look should follow? Who issues the execution call? Record the answers rather than treating a general "looks fine" as four separate confirmations.
Remove requests the venue cannot support and revise the act with the responsible team. Keep the rejected option out of the active sheet. An attractive idea does not become executable merely because it survived three rounds of formatting.
What changes when you revise the track?
Treat a changed file as a reason to review the affected cues. UAF's document guidance assigns responsibility for keeping materials current and controlling versions. The following numerical example is invented to demonstrate our revision check.
Suppose Edit A placed the second envelope closure at 00:28. Edit B adds eight seconds before that section, so the new reference is 00:36: 28 + 8 = 36. If the original ending was 03:12, the same addition makes it 03:20: 192 + 8 = 200 seconds. These are example calculations, not measured performance times.
The change record should say what moved and what did not. TURN still uses the second envelope closure as its intended trigger; its reference time changed. PLAY still starts at the beginning of the file, but now names Edit B. FINISH points to the ending of that same edit.
Do not mechanically add eight seconds to every row. OPEN is tied to confirmed readiness rather than the recording clock. A later cut could alter a different part of the track. Inspect the actual edit and reconfirm its relationships with the caller.
How do you hand over the final version?
Use an explicit status such as draft, reviewed with venue or rehearsal changes pending. These are our suggested labels; they record a real step only when that step occurred. Put the revision on every page so a detached page remains identifiable.
Before handoff, check the packet in both directions. Every active cue should point to the correct reference or file. Every file marked as required should have an explained purpose. Remove superseded sheets from the active packet while retaining an archive copy clearly separated from show-use material.
Ask the recipient to confirm the version received. Include a short change note: "Revision 2 replaces revision 1; playback is Edit B; TURN and FINISH reference times changed." That is more useful than "new version attached."
Keep follow-up notes factual. "Caller could not see the second closure from the assigned position" is an observation after a real check. "Use another trigger" is a proposed response awaiting agreement. Do not label either one a completed test before it happens.
The costume and stagecraft collection covers the wider preparation, while performance and makeup supports the artistic plan. If a lighting request depends on the intended face design, reference the matching makeup face chart. Give each document one clear job, and let the act keep the sequins.