Internal comms
AuraScore 81/100

Post-Production Asset Archival and Wrap Comms Specification

Define internal communication specifications for studio crew and post teams during film or television production wrap.

Use this template when a production reaches principal photography wrap or post-production delivery. It creates an internal communication specification governing asset handoffs, storage protocols, and department sign-offs.

Template

Role: Senior Studio Post-Production Operations Manager with fifteen years of experience coordinating media handoffs across major entertainment studios.

Context

  • Studio Name: {{studio_name}}
  • Production Title: {{production_title}}
  • Wrap Date: {{wrap_date}}
  • Target Archival Repository: {{archival_repository}}
  • Security and NDA Tier: {{nda_tier}}
  • Affected Departments: {{affected_departments}}

Task

Generate a comprehensive internal communication specification detailing the precise email directives, asset transfer protocols, and compliance requirements to be broadcasted to all studio departments upon wrap.

Method

  1. Review the operational requirements for {{production_title}} across all {{affected_departments}}.
  2. Define the exact timeline and schedule for physical and digital asset check-in leading up to {{wrap_date}}.
  3. Detail the secure transfer procedures for raw rushes, master files, and metadata into {{archival_repository}}.
  4. Establish the credential revocation and media sanitization rules mapped to {{nda_tier}}.
  5. Draft the primary notification broadcast email template intended for crew leads and department heads.
  6. Formulate an escalation matrix for outstanding equipment, unreturned master drives, and unsigned paperwork.
  7. Establish the post-wrap support and query workflow with specific contact points for production management.

Constraints

  • MUST maintain strict adherence to {{nda_tier}} confidentiality standards throughout all email copy.
  • MUST include explicit instructions for {{archival_repository}} directory conventions.
  • Do not use ambiguous delivery deadlines; all milestones must tie directly to {{wrap_date}}.
  • MUST NOT mention proprietary pricing or external vendor contract values.

Output format

Provide the specification in four structured sections:

  1. Operational Overview (Scope, core milestones, and department checklist).
  2. Broadcast Email Template (Subject line, announcement body, timeline table, and sign-off).
  3. Technical Handoff Specifications (Repository paths, naming standards, access controls).
  4. Escalation and Compliance Matrix (Issue types, resolution owners, turnaround times). Keep the entire output between 400 and 700 words.

Self-review

  • Confirm that all six input variables are accurately reflected in the specifications.
  • Verify that asset handoff protocols match the required {{nda_tier}} security parameters.
  • Ensure all instructions are fully actionable for technical and non-technical production crew.
AuraScore breakdown
81/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 engineering12/12 · Strong

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.

emails
emails-internal
media-entertainment
production
post-production
studio-operations