IT runbook documentation turns know-how into procedure
IT runbook documentation writes down how your IT work is actually done: the steps, the order, the checks and the people to call. Runbooks cover specific technical tasks, such as restoring a server or renewing a certificate. Standard operating procedures (SOPs) cover recurring business processes, such as onboarding a new hire. Together they let someone other than the original author do the work correctly.
In many small firms this knowledge lives in one or two people’s heads. That works until one of them is on vacation during an outage, or leaves. A runbook makes the procedure part of the company instead of part of a person.
OC Security Audit writes and reviews runbooks for businesses in Irvine, across Orange County and Southern California, and remotely nationwide.

What every runbook contains
The same fields on every runbook make them faster to write, review and follow.
| Field | What it holds |
|---|---|
| Title, ID and owner | A clear name, a reference number, the person responsible and the last review date |
| Purpose and trigger | What the procedure achieves and the situation in which to use it |
| Systems affected | Links to the servers, applications and network items in the asset inventory |
| Prerequisites | Access needed (as vault references, never passwords), tools, and approvals required |
| Steps | Numbered, one action per step, with the expected result after each |
| Verification | How to confirm the procedure worked, and who confirms it |
| If a step fails | Rollback or the point at which to stop and escalate |
| Contacts | Who to call, in order, with after-hours numbers |
| Test history | When the procedure was last tested, by whom, and how long it took |
Prerequisites link to the credential index and systems link to the IT asset inventory, so a runbook never goes out of date in two places at once.
The runbooks a small firm needs first
Start with the tasks that hurt most when the usual person is not available.
Onboarding
Accounts, groups and licenses, device setup, MFA enrollment, access to line-of-business applications, and the security training a new hire completes.
Offboarding
Disable sign-in, revoke sessions, transfer the mailbox and files, recover devices, and change every shared credential the person could reach.
Backup check and restore
How to confirm last night’s backup, and how to restore a single file, a mailbox and a whole server.
Certificate and domain renewals
What expires, when, who renews it, and what breaks if nobody does.
Internet failover
How to move to the backup circuit and back, using the details in your WAN circuit documentation.
Security incident first steps
Isolate the affected device, preserve logs, call the contact tree, and record who notifies the insurer and legal counsel.
Sample runbook excerpt
- Runbook
- RB-07 · Restore practice-management server SRV-PM-01 from backup
- Owner
- J. Ortega · last reviewed 2026-08-20
- Trigger
- SRV-PM-01 will not start, or its data is damaged or encrypted
- Prerequisites
- Backup console access (vault reference VLT-0012) · NAS-BK-01 reachable · approval from the practice manager
- Steps
- 1. Confirm the failure and open an emergency change.
2. Notify the practice manager and front desk using the contact tree.
3. In the backup console, select the last good restore point for SRV-PM-01 on NAS-BK-01.
4. Restore to the standby host. Leave the original powered off for investigation.
5. Start the practice-management service and open a test patient record.
6. Tell staff the system is back; record start and end times. - Verification
- Front desk confirms today’s schedule loads; the vendor confirms the database version
- If a step fails
- Stop at step 4 and call the practice-management software vendor’s support line
- Last test
- 2026-08-20 restore test · 2 h 10 min end to end
Sample restore order
| Tier | System | Depends on | Agreed target |
|---|---|---|---|
| 1 | Internet circuit and firewall FW-HQ-01 | ISP circuit | First hour |
| 1 | Core switch SW-CORE-01, DHCP and DNS | Power, FW-HQ-01 | First hour |
| 2 | Practice-management server SRV-PM-01 | Tier 1, NAS-BK-01 | Same business day |
| 2 | Microsoft 365 mail and Teams | Internet | Confirm access; service is cloud-hosted |
| 3 | Imaging workstations and Imaging-Sync | SRV-PM-01 | Next business day |
| 4 | File shares and printers | Tier 1 | Within two business days |
The restore order is agreed with the business owner before an outage, not during one. It is the practical result of what the HIPAA Security Rule calls an applications and data criticality analysis, an addressable part of the contingency plan standard at 45 CFR 164.308(a)(7).
How runbooks connect to disaster recovery and business continuity
A disaster-recovery plan says what to recover and in what order. Runbooks say how. A business continuity plan says how the office keeps working while IT recovers.
The HIPAA contingency plan standard at 45 CFR 164.308(a)(7) lists five parts, and each one maps to documentation:
- Data backup plan (required): what is backed up, where, how often, and the backup check runbook
- Disaster recovery plan (required): the restore order and the restore runbooks
- Emergency mode operation plan (required): how critical work continues during the outage, such as paper schedules or call forwarding
- Testing and revision procedures (addressable): the test history on each runbook
- Applications and data criticality analysis (addressable): the tiers in the restore order
For help designing the backup and recovery capability itself, see our business continuity and disaster recovery services.
Contact tree, offline copy and testing
Recovery documentation has to work in exactly the conditions that break everything else.
Incident contact tree
Who declares an incident, then who calls whom: IT lead, MSP, ISP support line, key vendors, the cyber insurance carrier’s claims line and legal counsel. Each entry has a backup person and an after-hours number.
Encrypted offline copy
Runbooks, the contact tree, the restore order and the network diagram exported to encrypted media kept off-site. Refreshed after significant changes. See securing your IT documentation.
Tabletop exercises
Walk through a scenario, such as ransomware on the server or a dead internet circuit, with the people who would be involved. Gaps in the runbooks show up quickly.
Restore tests
Restore a file, a mailbox and a server on a schedule, and record the time each took. We suggest at least one restore test each quarter.
Procedures auditors can review, and your team can use
ISO/IEC 27001:2022 Annex A 5.37 calls for documented operating procedures. The HIPAA Security Rule at 45 CFR 164.316 requires policies, procedures and required records in written form (electronic is acceptable), retained for six years from creation or the date last in effect, whichever is later, and reviewed and updated as needed. Runbooks with owners, review dates and test history are evidence for both. See IT documentation for compliance.
The IT Documentation Build includes runbooks and a restore order for your environment. The IT Documentation Audit reviews the procedures you already have against all 13 domains. Both are $3,500 fixed, one-time. See the IT documentation audit or IT documentation pricing.

Where to go next
IT change management
Every change updates the runbooks it affects, so procedures match the systems.
Securing your IT documentation
Protect your runbooks and keep an encrypted offline copy for the day the platform is down.
Page 13 of 22: Runbooks and disaster-recovery documentation
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation
- 6. WAN and ISP circuit documentation
- 7. Firewall and network settings documentation
- 8. Cloud documentation: Microsoft 365, Azure, AWS
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management
- 13. Runbooks and disaster-recovery documentation (this page)
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali writes runbooks so that someone who has never touched the system can follow them at two in the morning.
Runbook and recovery questions
What is the difference between a runbook, an SOP and a DR plan?
A runbook is the step-by-step procedure for a technical task. An SOP covers a recurring business process. A DR plan sets what is recovered and in what order, and points to the runbooks that do it.
Who should write our runbooks?
The person who does the task, reviewed by someone who does not. During an IT Documentation Build we write the first versions with your team, so they match how your systems really work.
How often should runbooks be tested?
We suggest a quarterly restore test and an annual tabletop exercise, plus a review after any real incident or significant change.
Where should runbooks be kept?
In your documentation platform, linked to the systems they cover, with an encrypted offline copy for outages that take the platform down.
Will OC Security Audit run our recovery?
We document the procedures and the restore order. Running a recovery is hands-on work for your IT team, your MSP or our implementation partner IT Perfection.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

Write it down before you need it
We will look at which procedures live only in someone’s head today and which to document first. Schedule a consultation.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


