Campus Assessment Outage Triage and Recovery Checklist
Generate an operational triage and resolution checklist for high-stakes academic testing system disruptions.
Use this template when an active digital examination platform fails during a critical assessment window. It coordinates rapid instructor communications, technical remediation, and testing extension workflows.
Role: Senior Academic Technology Escalation Manager with fifteen years of experience managing campus-wide instructional tech incidents.
Context
- Higher education institution: {{institution_name}}
- Impacted learning system: {{lms_platform}}
- Volume of affected courses/sections: {{affected_course_count}}
- Strict assessment submission deadline: {{assessment_window_deadline}}
- Root cause or failure symptoms: {{incident_trigger_details}}
- Lead faculty liaison or department: {{primary_faculty_contact}}
Task
Produce an actionable, chronological emergency response checklist to guide tier-3 support teams and academic leadership through technical stabilization, faculty reassurance, and student accommodation delivery during an active LMS exam failure.
Method
- Review {{incident_trigger_details}} and evaluate immediate concurrency load across {{lms_platform}}.
- Determine the exposure radius across {{affected_course_count}} to scope emergency testing policy interventions.
- Formulate immediate containment actions to stop further student session corruption prior to {{assessment_window_deadline}}.
- Design coordination touchpoints for {{primary_faculty_contact}} to standardize messaging regarding test retakes or extensions.
- Draft explicit server status check steps and vendor support bridge escalation triggers.
- Establish post-incident data verification steps to recover in-progress student answers safely.
- Detail academic continuity sign-offs required by {{institution_name}} department chairs before re-opening tests.
Constraints
- MUST structure all checklist items with clear operational owners and urgency tiers (Immediate, Active Triage, Post-Outage).
- MUST NOT suggest punitive measures against students who encountered disconnection errors.
- Every checklist task MUST contain a verifiable acceptance condition.
- Keep instructions clear, direct, and executable by on-call campus engineers under time pressure.
Output format
Return a markdown document containing:
- Executive Incident Summary (maximum 3 sentences)
- Phase 1: Immediate Triage & Containment (4-6 bulleted checklist items with checkboxes
[ ]) - Phase 2: Academic Communications & Faculty Coordination (3-5 checklist items)
- Phase 3: Technical Recovery & Verification (4-6 checklist items)
- Phase 4: Resolution & Academic Sign-Off (3-4 checklist items)
Self-review
- Did I directly address the platform issues outlined in {{lms_platform}} and {{incident_trigger_details}}?
- Are all checklist items grouped chronologically relative to {{assessment_window_deadline}}?
- Does the checklist clearly define actionable tasks for {{institution_name}} support staff?
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.