Documentation is the difference between an engineer resolving a ticket in ten minutes and spending an hour rediscovering an estate. The standard matters less than the requirement that it is complete and verifiably current.
Define completeness instead of a topic list. 'Network documented' is not auditable. 'Topology diagram, device register with management addresses, circuit IDs with support numbers, firewall rules with justifications' is.
Update at the point of change. Make the documentation update a step in the change and onboarding process. Documentation maintained on a review cycle is wrong for most of the cycle.
Audit documentation like any other deliverable. Sample accounts quarterly against the standard. Documentation quality degrades invisibly and is only discovered during an incident or when an engineer leaves.
Here's a preview. Unlock the free download to get all 3 sections (2 more below).
| Document | Completeness criteria | Update trigger | Max age | Owner |
|---|---|---|---|---|
| Client profile | Contacts, sites, tier, SLA, escalation path, VIPs | Contract or contact change | 6 months | Account manager |
| Asset register | All endpoints, servers, network devices with serial and warranty | Any asset change | Live | Onboarding / service desk |
More free templates IT teams use alongside this one.
MSP onboarding determines the margin on an account for its entire life. Estates documented properly in the first thirty days generate predictable ticket volumes; estates taken on blind generate surprises that get absorbed into a fixed fee.
Network documentation fails because it is written once, as a project deliverable, and then diverges from reality within a quarter. This template is scoped to the things that change slowly and are expensive to rediscover at 02:00.
A runbook is read by a tired person at 03:00 who did not write it and does not know this service. That single constraint rules out most of what people put in runbooks: architecture background, rationale, and anything written in prose when it could have been a command.
Client profile with escalation paths, asset register, network documentation including circuits and firewall justifications, identity and access configuration, backup scope and last restore test, application inventory, runbooks, and credentials in a proper platform.
Make updating it a step in the change and onboarding processes rather than a periodic review task. Documentation maintained on a quarterly cycle is wrong for most of each quarter, which is precisely when an incident will use it.
Whether an engineer who has never worked on that account can resolve a routine ticket from the documentation alone, without calling a colleague. That is also the test of whether the account is dependent on one person.
