University Policy Announcement and Multi-Stakeholder Email Cascade Audit
Audit institutional email dispatches to generate an executive email cascade report for major policy updates across faculty, staff, and students.
Use this template when planning or reviewing high-stakes institutional policy change announcements across diverse university audiences. It delivers a comprehensive strategic email cascade report with tailored copy variants, mitigation strategies, and response workflows.
Role: Senior Higher Education Communications Director specializing in institutional policy rollouts and executive messaging.
Context
- Higher education institution: {{institution_name}}
- Core policy or administrative change: {{policy_change_scope}}
- Target stakeholder segments: {{stakeholder_cohorts}}
- Historical support friction and inquiry trends: {{historical_inquiry_data}}
- Hard compliance and implementation dates: {{compliance_timeline}}
- Mandated institutional tone: {{preferred_tone}}
Task
Produce an exhaustive email communication audit and strategic rollout report that translates the policy change into audience-specific email blueprints, scheduling sequences, and inbound response management protocols across the entire institution.
Method
- Deconstruct {{policy_change_scope}} to identify critical compliance triggers, structural impacts, and perceived losses or benefits per cohort in {{stakeholder_cohorts}}.
- Synthesize {{historical_inquiry_data}} to pinpoint recurring misunderstandings, escalation triggers, and support bottlenecks from past broadcasts.
- Design a phased transmission sequence aligned to {{compliance_timeline}}, establishing pre-notification, primary dispatch, and reminder intervals.
- Draft cohort-differentiated email templates (leadership, faculty, administrative staff, researchers, students) incorporating {{preferred_tone}}.
- Formulate precise subject lines, preheaders, clear call-to-action buttons, and hyperlinked policy references for every cohort version.
- Build an inbound escalation rubric routing faculty inquiries, press requests, and student petitions to dedicated help desks.
- Define quantitative success metrics (open rates, click-throughs, ticket volume reductions, acknowledgment completion rates).
Constraints
- MUST produce distinct email body drafts for at least three unique stakeholder groups named in {{stakeholder_cohorts}}.
- MUST NOT use generic corporate terminology; maintain academic governance vernacular appropriate for {{institution_name}}.
- MUST map every communication phase explicitly to milestones in {{compliance_timeline}}.
- All draft emails MUST include explicit sender persona recommendations (e.g., Provost, Dean, Registrar) and unmonitored mailbox alternatives.
Output format
Generate a structured executive report with the following exact sections:
- Executive Summary & Policy Impact Matrix (max 300 words)
- Phased Email Cascade Schedule (tabular format: Phase, Target Cohort, Sender, Trigger Date, Core Message)
- Cohort-Specific Email Blueprints (Full text drafts for 3+ cohorts including Subject Line, Preheader, Body, Primary CTA, and Sign-off)
- Inbound Inquiry Escalation & Triage Protocol (max 250 words)
- Performance Telemetry & Risk Mitigation (KPI targets and FAQ strategy)
Self-review
- Confirm all variables from {{institution_name}} through {{preferred_tone}} are integrated directly into the analysis.
- Verify that email draft text avoids ambiguous instructions and specifies clear action deadlines.
- Ensure the tone reflects academic shared governance standards while maintaining operational clarity.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.