The IT Documentation You Only Miss When It Is Too Late

Every company has one person who knows how things fit together. Which server runs the old application, why that firewall rule exists, who to ring at the phone provider, where the licence keys live. It works fine right up until that person is on holiday during an outage, or leaves.

Good IT documentation is simply that knowledge written down somewhere other than one person’s head. It is unglamorous, nobody enjoys maintaining it, and its entire value shows up on the worst day you have all year.

Why the gap stays invisible

Nothing breaks because documentation is missing. That is what makes it so easy to postpone. The cost only appears when something else goes wrong, and then it appears all at once: hours lost working out how the network is put together, or a supplier who will not talk to you because nobody can prove they represent the company.

It is the same category as a fire extinguisher. You do not notice the absence until the day it matters, and by then you cannot fix it.

The IT documentation worth having

You do not need a manual. You need a small number of things recorded accurately.

What you own and where it lives

Devices, servers, and which cloud services you actually use. Include the boring details: serial numbers, warranty dates, and which supplier sold you what.

Accounts and access

Who holds administrator rights on each system, which accounts are shared and where the credentials are kept. Passwords belong in a password manager, never in a spreadsheet, but the record of who has access to what is documentation.

Network layout

A simple diagram beats ten pages of prose. Internet connection, firewall, switches, access points, servers, and how they connect. Add the internet line’s reference number, because you will need it when you call the provider.

Suppliers and contracts

Who supplies what, contract dates, notice periods, support numbers and your customer references. This part of your IT documentation saves money as often as it saves time, because auto-renewing contracts nobody tracked are a familiar expense.

Licences

What you own, how many, renewal dates and in whose name. Software bought on a personal account is a recurring problem when that person leaves.

Recovery steps

How to restore data, how to reach your backup system, who to call in what order. Short enough that someone stressed can follow it.

Where it must live

One rule matters more than the rest. Documentation stored only inside the environment it describes is useless during an outage. If your network diagram sits on the file server that is down, or your recovery steps live in the mailbox you cannot reach, you have written it for nobody.

Keep a copy somewhere separate. That can be a printed folder in a safe, an export on an encrypted drive, or a document in a service unrelated to your main systems. Credentials stay in the password manager with emergency access properly configured. Everything else just needs to be reachable when things are broken.

Keeping it honest

Wrong documentation is worse than none, because people trust it and act on it. The way to prevent that is to attach updating to moments that already happen: onboarding and offboarding, buying new equipment, changing supplier, any significant change to the network.

Then review the whole thing once a year, ideally against reality rather than against memory. Walking the building and comparing what is actually plugged in against what your IT documentation claims takes an afternoon and always turns something up.

The test that tells you where you stand

Ask yourself one question. If the person who knows the most about your IT were unreachable for two weeks, could someone else keep things running, deal with a supplier and restore a file?

If the answer is no, you do not have a documentation problem in the abstract. You have a specific dependency on one individual, and that is worth fixing whether or not anyone ever leaves.

A second question, less comfortable: if you switched IT partners tomorrow, could you hand over everything a new one would need? A partner who cannot produce that on request is telling you something about the relationship.

Let us maintain it for you

Documentation fails for a predictable reason. Writing it is a project, keeping it current is a habit, and habits do not survive a busy quarter unless someone owns them.

At EvolvingDesk we treat IT documentation as part of the service rather than as a deliverable you receive once. We map your environment, record the suppliers, licences and access, keep a copy outside your own systems for the day you cannot reach them, and update it as we make changes rather than months afterwards. It is your documentation, and you can take it with you whenever you want.

The result is that your business no longer depends on one person’s memory, and neither does ours.

Curious what is written down today? Plan a call and we will go through what exists and what is missing.

Read more

• What happens to your data when an employee leaves
• How much does IT management cost per employee, per month
• What is a managed service provider

Further reading: the NCSC material on business continuity and the Ready.gov continuity planning guidance.