Internal comms
AuraScore 85/100

Content Security Incident Response Comms Report

Draft a structured internal email report alerting studio personnel to an embargo breach or asset leak with clear containment protocols.

Deploy this template when confidential entertainment IP, unfinished footage, or press embargo materials are leaked externally. It equips communications managers to guide internal cast, crew, and corporate teams on protocol adherence.

Template

Role: Head of Broadcast Corporate Communications and Media Crisis Strategist.

Context

  • Media entity: {{network_name}}
  • Targeted property: {{affected_property}}
  • Incident description: {{incident_nature}}
  • Embargo policy: {{embargo_status}}
  • Approved staff guidance: {{internal_talking_points}}
  • Press inquiry owner: {{spokesperson_lead}}

Task

Generate an internal incident advisory email report informing internal staff of an active IP security incident while establishing immediate communication boundaries and inquiry routing.

Method

  1. Establish the scope and factual context of the security incident concerning {{affected_property}}.
  2. State the nature of {{incident_nature}} without validating speculative rumors or unauthorized material.
  3. Reinforce the standing status of {{embargo_status}} to maintain baseline company discipline.
  4. Translate {{internal_talking_points}} into direct dos and don'ts for employee social media use.
  5. Explicitly route all inbound media, talent, and fan inquiries directly to {{spokesperson_lead}}.
  6. Reiterate asset handling security protocols across creative and corporate teams.
  7. Structure the advisory report for rapid reading by time-pressed production and corporate personnel.

Constraints

  • MUST maintain an objective, calm, and directive tone.
  • MUST NOT link to or quote directly from leaked unauthorized assets.
  • MUST instruct employees not to engage with press or public social media threads.
  • Total output must not exceed 450 words.

Output format

  • Subject line: CONFIDENTIAL: Internal Guidance Regarding {{affected_property}} Media Incident
  • Incident Overview (2-3 concise sentences)
  • Mandatory Employee Guidelines (4-5 bulleted actionable rules)
  • Media & Public Inquiry Routing Protocol (Named contact: {{spokesperson_lead}})
  • Asset Security Reminders (3 brief bullets)

Self-review

  • Are the restrictions on external engagement unmistakably direct?
  • Does the report avoid amplifying the leaked content itself?
  • Is the contact info for {{spokesperson_lead}} clearly displayed for immediate escalation?
AuraScore breakdown
85/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 efficiency9/10 · Strong

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
security
crisis comms
leak response