Available Last updated 2026-09-11

Operator Checklists

Concise checklists for every phase of production — suitable for printing or copying into production notes.

These checklists are designed to be copied into production notes or printed for the booth. They reflect the 0.99.1 beta: hardware controller validation is still in progress, so no checklist assumes a physical controller is connected.

Rehearsal

  • Project file is saved and backed up.
  • All media files are present and referenced correctly.
  • Every cue has been previewed in Edit Mode (Space).
  • Audio volume levels are conservative (the gain display is not a peak meter).
  • Cue names are clear and operator-friendly.
  • Group Cues have been tested in Show Mode.
  • Preflight passes with zero blocking errors.

Technical rehearsal

  • Full cue-to-cue pass in Show Mode completed.
  • GO, STOP, PAUSE, RESUME, and PANIC all exercised.
  • STOP re-arm behaviour understood (STOP arms itself before it can fire again).
  • Memo acknowledgement (A) tested where memos require it.
  • OSC/MIDI/HTTP cues verified with their editor test buttons (Test Send / Test Request) against real receiving equipment.
  • Control mappings verified: listeners enabled in Settings → Triggers & Control, mappings exercised from the real sources where possible.
  • Trigger Inbox triaged (no unexpected proposals pending).
  • Output windows on the correct displays; no Missing bindings.
  • Blackout (B) and Test Pattern (T) tested.
  • Backup control method is ready.

Before doors

  • Project saved explicitly (Cmd+S); no unsaved changes anywhere.
  • Preflight re-run and passed; warnings consciously acknowledged.
  • Audio levels verified with ears or external metering.
  • Output windows open, on the correct displays, not blacked out.
  • Operator knows the PANIC key location (Escape).
  • Show Lock state agreed (Cmd/Ctrl+L).

Show start

  • Show Mode active; Engine Ready shown.
  • NOW RUNNING shows “No active cues.”
  • NEXT ARMED shows the correct first cue.
  • Stage manager has confirmed readiness.

During show

  • Watch NOW RUNNING and NEXT ARMED.
  • Listen for clipping or unexpected audio.
  • STOP for normal ends; PANIC only for emergencies.
  • After PANIC, Recover from Panic is a deliberate confirm — take the second to do it properly.
  • Do not switch to Edit Mode during the show.

After show

  • STOP or PANIC to clear all output.
  • Return to Edit Mode.
  • Save the project (Cmd+S).
  • Note any issues for the post-mortem.
  • Back up the project file and media folder.

External triggers

  • Listeners enabled in Settings → Triggers & Control (OSC port, MIDI device, HTTP port).
  • Health strip in Control Mapping shows Listening (not Disabled/Error).
  • Every mapping Tested from the actual source device.
  • note_on / note_off behaviour confirmed for MIDI pads.
  • HTTP endpoints answer (CueForge returns 200 and matches method + path).
  • No feedback-loop or source-conflict warnings in preflight.
  • Trigger Inbox empty or deliberately ignored.
Hardware controllers

Hardware profiles (APC Mini MKII, Allen & Heath SQ, SoundSwitch Control One) are implemented but physical validation on real hardware is still in progress. If you rehearse with a controller, verify every mapping yourself, and always have the keyboard workflow ready as the primary path.

Save / reopen verification

  • Save the project, quit (Cmd+Q), and relaunch.
  • If a recovery banner appears, choose Restore only if it holds work newer than your last save; otherwise Ignore.
  • Open the project and confirm every cue, media reference, and mapping survived the round trip.
  • Run preflight once more after reopening.
Print these checklists

Copy the relevant checklist into your production notes or print it for the booth. A paper backup is invaluable when the screen is occupied by CueForge.