It is 4:40 on a Friday and the internet is down. Not slow. Down. Nobody can process a payment, the phones went with it, and the shipping deadline is in twenty minutes. You call the provider, sit through the menu, and a reasonable person finally asks for your circuit ID. You do not know what a circuit ID is. She asks for the account number instead. That is on an invoice, in a mailbox you cannot reach, because the internet is down.
Eventually somebody remembers that the guy who set all this up left fourteen months ago. What he left behind was a network that worked, which is a compliment, and nothing written down, which is the problem. Network documentation produces zero value on 364 days a year and then, on the one day it matters, is worth more than every other IT investment you made that year combined.
Why the Map Matters Most on the Worst Day
Every serious security framework starts in the same place, which should tell you something. The Center for Internet Security puts Inventory and Control of Enterprise Assets first among its Critical Security Controls, for the plain reason that you cannot protect what you do not know exists. The National Institute of Standards and Technology, in Cybersecurity Framework 2.0, defines Asset Management as ensuring that “assets that enable the organization to achieve business purposes are identified and managed consistent with their relative importance.” And in its 2025 asset inventory guidance, the Cybersecurity and Infrastructure Security Agency described that visibility as “a critical first step in reducing risk and ensuring operational resilience.”
Translated into Friday afternoon language: documentation converts a four hour outage into a forty minute one. It also lets you hand your network to a new provider, an underwriter, or a buyer without a three week discovery project.
What a Proper Diagram Actually Includes
Most “network diagrams” in a filing cabinet are boxes with lines between them, drawn once during an office move. That is a picture, not documentation. A useful diagram answers questions under pressure, which means details, not just shapes.
- Every internet connection, with the boring details. Provider, account number, circuit ID, the support number that reaches an actual technician, contracted speed, and contract end date. Note where the line physically enters the building, called the demarcation point, because that is where responsibility changes hands.
- The firewall and router. Make, model, serial number, management address, who holds administrator access, and when the support or security subscription expires. A firewall with a lapsed subscription is a very expensive paperweight.
- Switches and how they connect. A switch is the box everything wired plugs into. Record model, which closet it lives in, which switch it uplinks to, and whether it supplies power over the network cable to phones and cameras, called Power over Ethernet or PoE.
- Wireless access points and what they broadcast. Locations, network names in use, and which internal network each drops users onto. Guest wireless belongs on a separate segment, and the diagram should prove it is.
- Your address scheme. Which ranges of internal addresses are in use, which devices have fixed addresses that must never change, and where automatically assigned addresses start and stop. The most useful section when something new refuses to connect.
- Servers, storage, and where backups land. Location, what each does, and the destination and schedule of every backup job. If a backup writes to a device in the same room as the original, say so plainly, because that is a risk hiding as a safeguard.
- Cloud and outside dependencies. The cloud is just someone else’s computer, and it still belongs on your map. Your Microsoft 365 or Google tenant, accounting and industry software, payment processing, and any remote access path each deserve a box with an owner’s name on it.
- Power. Which equipment sits on battery backup, how long that battery actually runs, and what is plugged straight into the wall and should not be.
The Failover Path Deserves Its Own Section
If you have backup internet, document how it takes over, whether that is automatic, what still breaks when it does, and how you switch back. Untested failover is a rumor.
If you do not have backup internet, consider it. Satellite service like Starlink works well as failover precisely because it skips local infrastructure. When a contractor cuts a fiber line down the road, every business on that line goes out together, and the one with a dish on the roof does not. Pair it with battery backup, because a connection that survives the outage is useless if the equipment it feeds loses power.
The Documents That Travel With the Diagram
- A vendor and account sheet. Every provider, account number, support number, contract end date, and who at your company is authorized to make changes. Providers will not talk to someone not on the account, and learning that mid outage is miserable.
- A restart order of operations. After a power failure, things come back in sequence. Internet equipment, firewall, switches, servers, then everything else. Write it down, because at 5 in the morning nobody reasons well.
- A warranty and license expiration list. Hardware support, firewall subscriptions, software renewals, domain registration. An expired domain takes down email, and it happens more than you would think.
- Photos of the racks and closets. Ten minutes with a phone camera, including labeled cables and the back of each rack, saves hours later.
- A change log. One line per change with the date and who made it. This answers “what changed?”, the first question of every troubleshooting session ever conducted.
Passwords do not belong in the diagram. They belong in a password manager, which is an encrypted vault, with access granted to specific people. The documentation should say where the credentials live, not what they are.
Where It Lives, and Keeping It Current
Documentation stored only on the network it documents is documentation you will not have when you need it. Keep a copy off the network, a printed copy where a manager can reach it, and make sure two people know where both are.
Treat it as sensitive, though. A complete network map is a convenient roadmap for anyone with bad intentions, so access control it rather than sharing it broadly.
Staying current means attaching updates to events, not calendars. When you replace hardware, change providers, or add a location, the documentation gets updated as part of that job rather than a separate project nobody schedules. Then a real review once a quarter, which takes under an hour once the habit exists.
The Bottom Line
A proper network map is not a work of art. It is a diagram with real details on it, a vendor and account sheet, a restart order, and a change log, stored somewhere you can reach when everything else is down. Building the first version takes a few hours. Not having it costs those hours back on the worst possible afternoon, with customers waiting and everyone guessing. It is a one time project with cheap upkeep that makes every future problem smaller.
If nobody at your company can produce a current network diagram right now, reach out to Harrison Ward Technology. We document networks for businesses in Lewisville, Flower Mound, Highland Village, Frisco, and across Denton County, and we would rather build your map on a quiet Tuesday than meet you on a loud Friday.
Comments are closed