IT support plan: what to document before an emergency

An IT support plan for SMBs starts with business priorities

Not everything is equally urgent. A printer that’s down in an administrative office doesn’t have the same effect as an order-taking system nobody can reach. Name the essential services, the hours they need to be running and the person who can confirm their priority. This short list helps the technician deal with the real impact rather than the loudest ticket.

Also define who can authorize an expense, a planned interruption or a call to the vendor. If management is away, a backup person must be able to decide up to a known limit. Write down the backup communication channels: a mobile number, an accessible Teams group or a call list. If Microsoft 365 is the very thing that’s down, the plan shouldn’t be stored only in SharePoint.

Add a simple escalation rule. For example: after a first check, who do you call and what information do you need to pass on? The goal isn’t to predict every incident, but to avoid fifteen minutes of scattered messages before someone takes charge.

Inventory the equipment without writing a novel

A useful inventory ties each piece of equipment to its role. Note the model, serial number, location, warranty and person responsible for the firewall, switches, access points, servers and specialized devices. For cloud services, note the service name, the tenant or business account and the internal owner.

Keep diagrams simple. A drawing that shows the Internet provider, the firewall, the main networks, guest Wi-Fi and critical systems is better than a complex diagram that never gets updated. Photographing the front and back of the rack after tidy cabling can also help during a remote call, as long as the images are kept in a controlled location.

The date of the last check matters as much as the content. Add it to each sheet and assign updates to a specific person. The page on IT support from Infotech Canada explains how structured support can complement this documentation when the internal team is short on time.

Document access without exposing passwords

The plan should say where the credentials are, not necessarily contain them. Use a business password manager or an approved vault, then document the vault’s name, the people authorized to use it and the emergency access procedure. Avoid a spreadsheet attached to the plan or a password taped under the router.

For each important service, confirm that at least two authorized people can recover access. Check the domain, DNS, Internet provider, Microsoft 365, web hosting, backups and warranty portals. An account created with a former employee’s personal address can block an intervention even when all the technology works.

Also note the MFA requirements and recovery methods. Where are the backup codes kept? Which device receives the notifications? Who can reset a lost factor? Run a controlled test before an emergency rather than finding out the answer during an outage.

Connect vendors, contracts and backups

A contact list should spell out what each vendor handles, its contract number, its service hours and how to open a ticket. Add the response times or limits set out in the contract without treating them as a guarantee. That way, the technician will know whether to call the Internet provider, the software publisher or the company that manages the network.

For backups, document what’s copied, how often, where the copy is kept and who receives the alerts. Above all, write down the date of the last restore test and its result. “Backup enabled” doesn’t answer the most important question: can you bring a file or a system back into service under current conditions?

Also keep track of renewal dates and known exclusions. An out-of-warranty device or an expired subscription changes the options available. This information lets you quickly authorize a temporary replacement or a purchase, rather than waiting for someone to dig through the accounting records.

Keep the document alive with small exercises

An IT support plan for SMBs goes stale as soon as a vendor, a key employee or a piece of equipment changes. Build its review into employee onboarding and departures, network changes and major renewals. A twenty-minute quarterly review can stick to contacts, access, priority systems and backups.

Twice a year, pick a short scenario: the Internet goes down, an administrator account is locked or a folder needs to be restored. Without interrupting operations, ask the team where to find the plan, who makes the decision and which vendor to contact. The hesitations show you exactly what to fix.

Finally, keep a copy that’s accessible during an outage but protected from unauthorized eyes. A redacted printed version can hold the contacts and priorities, while the sensitive details stay in the digital vault. The right plan isn’t the longest one: it’s the one the team can find, understand and use.

Check what would be missing during an outage

If you want to check your documentation before the next emergency, Infotech Canada can review priorities, access, vendors, inventory and backups with your team. The result can stay short: the information that matters, the responsibilities and the next fixes.

Book a meeting

Have a specific question about your situation? Write to us.