LMS Exam Disruption Escalation Matrix

Role: Principal Academic Technology Support Lead specializing in higher education LMS incident response.

Context

• Academic Institution: {{institution_name}}
• Learning Management Platform: {{affected_lms_platform}}
• Disruption Trigger: {{incident_trigger_details}}
• Impacted Academic Units: {{active_exam_cohorts}}
• Faculty Notification Protocol: {{faculty_communication_sla}}
• Available Engineering Tiers: {{technical_tier_levels}}

Task

Generate an operational incident escalation matrix that categorizes live assessment disruptions, maps immediate technical handoffs across support tiers, and prescribes clear academic continuity workarounds for proctors and department chairs.

Method

1. Evaluate the incoming incident logs from {{affected_lms_platform}} against active exam sessions in {{active_exam_cohorts}}.
2. Classify the disruption into four severity levels based on total student concurrency and exam stakes.
3. Map each severity level to an immediate response owner within {{technical_tier_levels}}.
4. Define explicit time-to-escalate trigger thresholds before routing directly to platform vendor engineers.
5. Establish academic accommodation rules (e.g., auto-pause timer, paper backup, reschedule window) for each tier.
6. Standardize status update messaging cadence to satisfy {{faculty_communication_sla}}.
7. Detail post-incident verification criteria required from proctoring leads before re-opening affected testing sessions.

Constraints

• MUST format the primary output as a structured Markdown matrix containing Severity, Trigger, Owner, Technical SLA, and Academic Action.
• MUST NOT exceed 15 minutes for Tier 1 to Tier 3 escalation handoff triggers.
• Action steps must provide distinct guidance for synchronous proctored exams versus asynchronous take-home submissions.
• Do not include theoretical root cause analysis; focus entirely on active containment and triage.

Output format

1. Incident Severity & Routing Matrix

Markdown table with columns: Severity Tier, Platform Incident Indicator, Primary Resolver, Escalation SLA, Academic Continuity Action.

2. Stakeholder Communication Runbook

Bullet-point notification sequence ordered chronologically from Minute 0 to Minute 60.

3. Session Re-Entry Verification Checklist

4-6 binary verification checks required prior to resuming testing.

Self-review

• Confirm all variables from {{institution_name}} to {{technical_tier_levels}} are explicitly contextualized in the matrix.
• Verify that SLA windows directly reflect emergency testing environments.
• Check that academic continuity actions do not breach standard academic integrity requirements.