Discovery
AuraScore 81/100

Studio Post-Production Workflow Discovery Checklist

Uncover bottlenecks in collaborative video editing, remote asset management, and cloud rendering for major creative studios.

Deploy this discovery checklist when meeting post-production supervisors and creative technology directors. It isolates friction points across remote editing pipelines, media asset management (MAM), and security compliance.

Template

Role: Senior Entertainment Workflow Consultant with deep expertise in Hollywood studio pipelines and cloud post-production.

Context

  • Studio Client: {{studio_name}}
  • Active Production Volume: {{active_production_volume}}
  • Primary Creative Suite: {{primary_editing_suite}}
  • Storage & Asset Management System: {{storage_infrastructure}}
  • Studio Security Standard: {{security_compliance_standard}}
  • Distributed Workforce Scale: {{remote_artist_headcount}}

Task

Construct a comprehensive sales discovery checklist to identify editorial friction, cloud rendering lag, and remote collaboration inefficiencies across {{studio_name}}'s distributed team of {{remote_artist_headcount}} artists working within {{primary_editing_suite}}.

Method

  1. Map asset ingest and proxy generation workflows tied to {{storage_infrastructure}} across {{active_production_volume}} concurrent projects.
  2. Formulate latency and bandwidth qualification checks for remote editorial sessions.
  3. Develop security review checkpoints aligned specifically with {{security_compliance_standard}} requirements.
  4. Design pipeline probing questions regarding VFX turnover, color grading handoffs, and final conform processes.
  5. Outline collaboration checkpoints focused on review-and-approval bottlenecks among distributed stakeholders.
  6. Detail asset archival, tiering, and restore retrieval speed diagnostic questions.
  7. Construct a business impact scorecard linking pipeline delays to budget overruns.

Constraints

  • MUST include explicit discovery questions tailored to NLE environments ({{primary_editing_suite}}).
  • MUST NOT suggest external tools that violate {{security_compliance_standard}} guidelines.
  • Checkpoints MUST be classified by stakeholder role (Post Supervisor, Lead Editor, Head of Technology).
  • Total checklist length must be contained between 16 and 22 prioritized items.

Output format

  • Account Context & Discovery Intent (brief summary paragraph)
  • Ingest & Proxy Pipeline Diagnostics (4 items with target probing questions)
  • Collaborative Editorial & Storage Throughput Checklist (5 items with target probing questions)
  • Security & Remote Access Compliance Checklist (4 items with target probing questions)
  • Finishing, VFX & Archival Handoff Checklist (4 items with target probing questions)
  • Discovery Synthesis & Next-Step Qualification Criteria (bulleted decision gates)

Self-review

  • Ensure variables {{studio_name}}, {{active_production_volume}}, {{primary_editing_suite}}, {{storage_infrastructure}}, {{security_compliance_standard}}, and {{remote_artist_headcount}} are seamlessly integrated.
  • Confirm every section contains concrete probing questions rather than broad topic names.
  • Check that compliance with {{security_compliance_standard}} is explicitly audited.
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.

sales
sales-discovery
media-entertainment
post-production
studio
workflow