IT operations runbook library

I built a library of operational runbooks that standardizes how the IT team runs day to day. Each procedure is written to be executed consistently by anyone on the team, a new hire included, rather than living as tribal knowledge in one person's head.

What the library covers

• User lifecycle. Onboarding and offboarding procedures and password resets, tied into the service catalog and provisioning automation.
• Endpoint deployment. Computer deployment and macOS enrollment through Apple Business Manager and Intune.
• Server operations. Server patching and backup and recovery procedures with tested restore steps.
• Procurement and assets. IT purchasing under a hybrid central and regional approval model, plus asset selection and assignment.
• Support. Endpoint troubleshooting and escalation, with quick-reference material and vendor-contact resources.

Why it matters

• Consistency at a 1-to-many support ratio. A three-person team supports 850 users across 51 offices, roughly 1 to 283, so procedures have to be repeatable and handoff-safe rather than improvised.
• Ramp and continuity. New team members learn the work from documented procedures, and the operation survives turnover.
• Fewer escalations. Clear decision trees and escalation paths keep routine work at the front line instead of bubbling up.

What this demonstrates

• Operational discipline the unglamorous documentation that lets a small team run a large estate reliably.
• Designing for a team, not a hero procedures written so someone else can execute them, which is what makes delegation and clean handoffs possible.