Almost every office has a network diagram somewhere. It was drawn when the system was installed, saved to a shared drive, and has not been touched since. Then a switch is replaced, a camera system is added, a second internet line is installed, and the diagram quietly becomes fiction. The first time anyone notices is usually during an outage, when someone is trying to follow a map that no longer matches the territory.
Documentation is not glamorous, but it directly affects how fast problems get fixed and how much you depend on any one person's memory. Here is how to keep it accurate with modest effort.
Most small and mid-size organizations do not need elaborate documentation. They need a handful of things that are right.
A network diagram. One page showing the internet connection, firewall, main switches, wireless, servers and key remote locations.
An asset inventory. Computers, servers, printers, phones and network gear, with serial numbers, locations and warranty dates.
An accounts and access list. Which systems exist, who administers them, and where administrative credentials are stored securely.
Vendor and contact sheet. Internet provider, software vendors, phone provider, with account numbers and support lines.
Runbooks. Step-by-step instructions for recurring or high-stress tasks.
A runbook is a short procedure that someone other than the original expert can follow. Good candidates include:
Onboarding and offboarding an employee
Restarting a critical application or server in the right order
Restoring a file or folder from backup
Switching to a backup internet connection
Setting up a new workstation
What to do when the internet is down, including who to call
Write each in plain steps, with screenshots only where they help. Include what "done" looks like, such as how to confirm the service is working. If a step requires a credential, point to where it is stored rather than writing the password in the document.
The most reliable habit is to treat documentation as part of the change itself. If a switch is replaced or a new firewall rule is added, the work is not finished until the diagram or inventory is updated. Add that line to your change checklist or ticket template.
Shared ownership often means no ownership. Name an owner for each document, even if several people contribute. The owner is not the only editor, just the person who makes sure the review happens.
Put a quarterly review on the calendar. Walk the building or use a network scan to compare reality against the diagram and inventory. Fix discrepancies and note the date on the document. A twenty-minute check is far better than a heroic annual rewrite.
The best test of a runbook is having someone unfamiliar follow it. After a new hire is onboarded or a backup is restored, ask whether any step was wrong or missing, and correct it on the spot.
Every document should show when it was last reviewed. Store files where version history is kept, so an accidental edit can be undone and changes can be traced.
Keep documentation somewhere it can be reached during an outage. If everything lives on a server that is down, the guide is not helpful. Store a copy in a cloud location with access controls, and keep a printed copy of the critical items, such as the contact sheet and internet outage steps, with whoever is on call. Because these documents map your environment, they are valuable to an attacker as well, so restrict access to those who need it.
In a clinic or care facility, an outage affects residents and patients. Clear documentation means a backup technician or outside partner can step in without a long discovery period. It also helps during security reviews, insurance applications and HIPAA risk analyses, where you are asked to describe your systems and where protected health information lives.
If you have nothing today, begin with the contact sheet and a rough diagram. Improve from there. UnityCare IT maintains this documentation for the healthcare and senior-living organizations we support, and we can help you build a baseline if you are starting from scratch.
Wi-Fi, switching, firewalls and internet that hold up across a whole facility.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Address: UnityCare Technologies, 2524 N Broadway Ste 554, PMB 947974, Edmond, Oklahoma 73034-4172