"Only Bob Knows the Router Login": Why Your IT Needs Documentation

Every small business has a Bob. Sometimes Bob is the owner. Sometimes it is the office manager, or the tech-savvy employee who set up the network years ago, or an outside consultant who has not returned a call since spring. Bob knows the router password, which closet the backup drive is in, and why the printer only works if the computer in the corner is turned on. Nobody else does.

Bob is great, right up until Bob is on a cruise, out sick, retired to North Carolina, or no longer on speaking terms with you. That is usually when the server goes down. The fix for this is not glamorous, but it is one of the highest-value things a small business can do for its technology: write it down.

The real cost of undocumented IT

When nobody knows how things are set up, every problem takes longer to fix. A technician who could restore internet service in fifteen minutes with the firewall login might spend half a day resetting equipment and rebuilding configurations without it. Multiply that across every outage and every new hire, and the cost adds up fast.

There are quieter costs too:

  • Lockouts. Your domain name, website hosting, or software license is registered to an email address nobody can access anymore.
  • Missed renewals. A domain or SSL certificate expires and your website and email go dark because the renewal notice went to a former employee.
  • Security gaps. Former staff still know passwords that never got changed, because nobody knew which passwords existed.
  • Vendor dependence. Switching IT providers becomes painful when the old one is the only source of information about your own systems.
Documentation is the difference between "we had a problem and fixed it" and "we had a problem and spent two days figuring out how things were set up."

What to document

You do not need a three-hundred-page manual. A small office can cover the essentials in a few pages and a well-organized password store. Start with these:

Accounts and vendors

  • Internet provider: account number, support contact, what service you have.
  • Domain name registrar and website host: who they are, the login, the renewal date.
  • Email provider, such as Office 365 or your Exchange server.
  • Software vendors and license keys for line-of-business applications.
  • Phone system vendor and the admin login.
  • Warranty and support contract details for servers and key equipment.

Network and equipment

  • Firewall or router: make, model, admin login, and how to reach it.
  • Wireless network names and passwords, including guest Wi-Fi.
  • Switches, access points, and where they physically live.
  • Your internet IP address details and any port forwarding rules, and why they exist.
  • A simple diagram, even hand-drawn, showing how everything connects.

Servers and computers

  • What each server does, its admin account, and its age.
  • A list of workstations and laptops, who uses them, and when they were purchased.
  • Where the backups go, what they cover, and how to restore a file.
  • Printers and copiers, including scan-to-email or scan-to-folder settings.

Procedures

  • How to set up a new employee: accounts, email, access to shared folders.
  • How to remove someone who leaves: accounts to disable, passwords to change, devices to collect.
  • Who to call for what, and in what order, when something breaks.
  • What to do before a hurricane: which equipment to shut down, what to unplug, how to confirm the latest backup went offsite.

Where to keep it (hint: not a sticky note)

Documentation full of passwords is a treasure map, so it needs protecting. A few ground rules:

  • Passwords belong in a password manager, not in a Word document, a spreadsheet on the desktop, or taped under the keyboard. A good password manager encrypts everything, lets you share specific entries with specific people, and makes it easy to change passwords when someone leaves.
  • General documentation can live in a shared folder with access limited to the people who need it, or in a documentation system your IT provider maintains.
  • Keep a copy somewhere else. If your only copy is on the server and the server is what failed, the documentation is not much help. Keep an encrypted copy offsite or in the cloud, and consider a sealed printed copy of the most critical logins in a safe.
  • The business should own it. Whoever maintains your documentation, including an outside IT provider, the business should always have full access to it. Your information is yours.

Keep it current

Outdated documentation can be almost as bad as none, because people trust it. Build updates into normal routines. When a password changes, update the password manager right then. When equipment is replaced, update the list. Once or twice a year, set aside an hour to review everything, perhaps at the start of hurricane season in June, when you are already thinking about business continuity.

Your documentation starter checklist

  1. Sit down with your Bob this month and get the critical logins recorded.
  2. Choose a password manager and move passwords into it.
  3. List every vendor and account that your business depends on.
  4. Make sure domain, hosting, and software accounts use a company-controlled email address.
  5. Sketch a simple network diagram.
  6. Write down onboarding and offboarding steps.
  7. Store a protected copy offsite.
  8. Schedule a review twice a year.

Good documentation is one of those things nobody notices until the day it saves you. Maintaining it is a standard part of our managed IT services, and we are always happy to help a business get its IT information out of one person's head and into a safe, organized place. Drop us a line at info@pinellasit.com.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment