Launch package 4

Troubleshooting Runbook Template

A copy-and-use template for documenting symptoms, checks, ownership, escalation, and resolution steps without adding busywork.

Incident intake Verification Escalation Postmortem

Runbook template

Use the checklist below as the first page of a living runbook. Fill in the blanks, keep it concise, and update it after each incident.

Problem statement: what is broken, who is affected, and what changed. Impact: users, devices, sites, apps, or business workflows impacted. Repro steps: the shortest way to reproduce the issue. Baseline checks: account, network, policy, version, and permissions. Log sources: Event Viewer, Intune reports, app logs, or script output. Decision points: when to continue, rollback, escalate, or stop. Resolution notes: root cause, fix applied, verification result, and prevention step.

Section	What to capture	Why it matters
Scope	Device, user, app, policy, or environment	Stops random troubleshooting
Symptoms	Exact error text, timestamps, screenshots	Makes matching logs much easier
Checks	Simple yes/no validation steps	Prevents skipped basics
Escalation	Owner, threshold, and next team	Avoids stalled incidents
Verification	What proves the fix worked	Confirms resolution before close

Best use

Recurring tickets, escalations, and every issue that deserves a repeatable fix path.

Common mistake

Writing a long narrative instead of a step-by-step decision record.

Trust signal

Short, versioned, and practical enough to use during an active incident.