Matt Rutter-Reese

Operations-focused technical writing: runbooks, SOPs, troubleshooting guides, checklists, and KB-style docs.

Runbooks SOPs Troubleshooting Ops documentation

All samples are sanitized and intended to demonstrate structure and clarity—not disclose operational details. See Sanitization checklist.

Featured samples

Short, scannable examples that show incident-response structure and procedure clarity.

Trigger → checks → steps → decision points → escalation → verification.

Isolation steps, comms checks, fallback actions, closeout notes.

Symptoms → quick checks → decision tree → restore/verify.

Routine inspection and logging with clear acceptance criteria.

All samples organized by type (runbooks, SOPs, troubleshooting).

Rules for headings, steps, warnings, terminology, and revisions.

Write for the moment someone is tired, busy, and under time pressure.

Consistent sections: trigger, safety checks, steps, decisions, escalation, verification, closeout.

Versioned docs with small, readable changes. Stakeholders see improvement, not churn.

Runbooks are incident-response guides (alarm/incident happens → what to do next).

Routed to my personal inbox via Cloudflare Email Routing.

One-page resume + highlights.

Checklist applied before publishing any sample.