Scripts
AuraScore 79/100

Multi-Camera Sitcom Production Draft Polish Checklist

Verify laugh rhythm, blocking feasibility, and joke track integrity across episodic multi-camera teleplays before studio tapings.

Deploy this template following table reads to evaluate multi-cam sitcom scripts across physical camera lines and laugh density. It delivers an operational checkpoint system for showrunners and script supervisors.

Template

Role: Supervising Producer & Multi-Camera Sitcom Head Writer

Context

  • Episode Working Title: {{episode_working_title}}
  • Scene Order and Cold Open Roster: {{writers_room_cut_scene_list}}
  • Soundstage Configuration: {{stage_set_limitations}}
  • Target Punch-Up Tracks: {{punch_up_priority_tracks}}
  • Broadcast Standards and Practices: {{network_standards_guidelines}}
  • Commercial & Sponsor Commitments: {{sponsor_integration_points}}

Task

Generate a multi-camera teleplay production audit checklist to evaluate {{episode_working_title}} post-table-read, verifying laugh cadence, four-camera blocking viability, act-out cliffhangers, and network compliance prior to camera blocking night.

Method

  1. Deconstruct {{writers_room_cut_scene_list}} to establish scene-by-scene beats, counting target laughs-per-minute metrics.
  2. Map physical movements against {{stage_set_limitations}}, generating specific checks for quad-camera sightlines, cross-overs, and stage swings.
  3. Create targeted joke-health audit items addressing specific priority tracks from {{punch_up_priority_tracks}} (e.g., toppers, alternative buttons, setup trims).
  4. Formulate Act I, Act II, and Act III act-out boundary verification checks ensuring emotional and comedic stakes remain unresolved.
  5. Design legal and regulatory clearance checkpoints aligned with {{network_standards_guidelines}} to flag potential language, brand, or safety infractions.
  6. Build placement verification checks ensuring natural integration of {{sponsor_integration_points}} without derailing comedic momentum.
  7. Develop page-budget and pacing validation criteria ensuring scenes stay strictly within standard tape-night multi-cam production constraints.

Constraints

  • Every checklist checkpoint MUST specify verification criteria, stage impact, and remedy protocols.
  • MUST NOT include single-camera cinematic shot conventions; all physical staging checks must adhere exclusively to multi-camera proscenium rules.
  • Must explicitly verify comedic buttons on every scene exit without exception.
  • Must separate tape-night logistical checks from creative comedic punch-up checks.

Output format

Provide a comprehensive markdown audit checklist structured across five sequential operational categories:

  1. Camera Staging & Stage Geometry Verification (6-8 items mapped to {{stage_set_limitations}})
  2. Laugh Cadence & Joke Architecture Audit (8-10 checks targeting 3-4 laughs per script page)
  3. Act-Break & Narrative Propulsion Verification (4-6 checks evaluating commercial outs)
  4. Standards, Clearances, & Sponsor Integration Checklist (5-7 compliance items)
  5. Tape Night Emergency Backup & Alternate Joke Matrix (4-6 structural checks for wild lines and B-roll alts)

Self-review

  • Ensure every section provides concrete thresholds (e.g., line-lengths, joke counts) rather than subjective guidelines.
  • Check that multi-cam stage boundaries and proscenium constraints are fully respected.
  • Verify all six variables are woven into specific operational checkpoints.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

writing-content
writing-scripts
media-entertainment
sitcom
television-production
multi-cam