Campus Examination Outage De-escalation Memo
Author a structured executive escalation email to university deans following a major online examination outage.
Deploy this template when a campus-wide learning management system failure interrupts high-stakes assessments. It equips academic leadership with factual timelines, student impact figures, and standardized policy accommodations.
Role: Director of Academic Technology Escalations specializing in higher education LMS operations and campus crisis communications.
Context
- Academic Leader / Dean: {{dean_name}}
- Campus / Institution: {{institution_name}}
- Impacted Courses & Student Count: {{affected_courses}}
- Technical Root Cause: {{lms_root_cause}}
- Policy Accommodation Framework: {{academic_policy_adjustment}}
- Follow-Up Briefing Schedule: {{next_update_time}}
Task
Draft a high-level incident notification email to {{dean_name}} detailing the midterm/finals system outage across {{affected_courses}}, communicating technical remediation status, and providing recommended faculty guidance for {{institution_name}}.
Method
- Analyze the disruption data to summarize aggregate student and course counts affected across {{institution_name}}.
- Frame a professional subject line balancing operational urgency with institutional composure.
- Acknowledge the administrative and emotional friction caused to students and proctors during active assessment windows.
- Summarize the failure mechanism using {{lms_root_cause}} in plain language suitable for non-technical deans.
- Outline the recommended handling of incomplete submissions based on {{academic_policy_adjustment}}.
- Detail backend logging evidence available to faculty for verifying authentic student connection drops.
- Specify the exact schedule for the next leadership sitrep using {{next_update_time}}.
Constraints
- MUST NOT shift blame to third-party vendors or individual course instructors.
- MUST explicitly articulate protections for student grading equity.
- MUST present clear academic continuity guidelines in under 400 words.
- Use formal university executive correspondence conventions.
Output format
- Subject line: [ACADEMIC CONTINUITY ESCALATION] - Incident Briefing
- Executive Overview
- Incident Diagnostics & Scope (table or structured bullets)
- Faculty & Student Accommodation Protocols
- Next Briefing Milestone
Self-review
- Does the email provide deans with defensible policy recommendations for grading?
- Is {{lms_root_cause}} explained clearly without excessive jargon?
- Are all placeholders populated with relevant academic terms?
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.