Small business network audit checklist

Use this checklist to review the network your business depends on: internet access, WiFi, equipment, accounts, documentation, and recovery.

Record what you know, what needs checking, and who owns each next step. Avoid disruptive tests during business hours.

1. Internet and core connectivity

• Do you know who the ISP is, what the account number is, and who can open a support case?
• Is the internet circuit actually sized for how the business uses cloud apps, voice, cameras, streaming, and guest traffic?
• Do outages come from the provider, or do people just assume that because the WiFi feels bad?
• Is the modem, gateway, or firewall documented well enough that someone else could support it?

If the answer to most of those is "not really," the business probably has an ownership problem before it even has a hardware problem.

2. WiFi coverage and client experience

• Are access points placed where people actually work and gather, not just where installation was easiest?
• Do dead zones, slow spots, or disconnects line up with certain rooms or busy periods?
• Are you using business-grade wireless gear, or home equipment that is being asked to act like business infrastructure?
• Would a new access point improve coverage, or is the bigger issue cabling, uplinks, or interference?

Bad WiFi is one of the most visible symptoms of a weak environment, but it is often only the symptom.

3. Guest traffic and network separation

• Is guest WiFi separated from business systems?
• Are payment systems, printers, staff devices, cameras, and management interfaces kept in sensible boundaries?
• Could one noisy or badly behaved device affect too much of the business?
• Would a new person looking at the network understand which traffic belongs where?

If everything is flat, troubleshooting gets harder and risk spreads farther than it should.

4. Hardware age and lifecycle

• Is any core network gear unsupported or years behind current firmware support?
• Do you know which devices are old enough to become a liability soon?
• Are failures being handled with repeat reboots instead of a plan?
• Would the business know what to replace first if a key switch or firewall died?

Replacing everything is not always the answer, but not tracking lifecycle at all is its own kind of risk.

5. Documentation and handoff quality

• Do you have a current list of core devices, where they are, and what they do?
• Are SSIDs, VLANs, and major network boundaries documented anywhere usable?
• Can someone besides one specific person explain the environment?
• Do vendor changes or staff turnover create confusion every time?

Documentation is not busywork. It is what keeps a small problem from becoming a multi-day mess.

6. Access and account ownership

• Are admin accounts shared casually, or does the business know who has access to what?
• Can the business reach the firewall, WiFi controller, domain registrar, DNS provider, and ISP account without digging through old email threads?
• Have old vendors or former staff kept access they no longer need?
• Is MFA enabled anywhere important?

A lot of support pain comes from access sprawl rather than purely technical failure.

7. Physical environment and supportability

• Is the rack, cabinet, or utility area clean enough that someone can work in it without guessing?
• Are cables labeled or at least organized well enough to avoid accidental disruption?
• Is gear mounted, powered, and ventilated in a way that makes sense?
• Would a technician walking in understand the layout in a reasonable amount of time?

Physical mess almost always becomes technical mess eventually.

8. Business continuity reality check

• What actually happens to the business if the internet drops for half a day?
• What happens if WiFi fails during the busiest hour?
• Is there a fallback for payments, communications, or critical tools?
• Do people know who to call and what to check first?

Small businesses usually do not need a giant formal program, but they do need a realistic sense of how much fragility is hiding in normal operations.

How to use this checklist

If several sections feel fuzzy, that usually means the environment needs cleanup, documentation, or redesign before it needs another piece of hardware. If the answers are clear but the gear is obviously old or undersized, then replacement planning may be the right next step. The point is to make decisions based on what is actually weak, not just what is easiest to blame.

See case studies →