Network refresh as a project: site survey to commissioning

A school administrator gets three vendor quotes for a network refresh. The first is the cheapest. The second has the highest brand names. The third is the most expensive but includes phrases like “site survey” and “commissioning report” that the other two do not mention. The administrator picks the second vendor on the strength of the brand names. Eighteen months later, the school is dealing with a network that meets the spec on paper but does not behave the way the school needs it to in any of the rooms that matter.

The problem was not the brand. It was that nobody measured first. A network refresh that skips the discovery work usually ships hardware that nominally fits the room and operationally does not.

The phases of a refresh project

A network refresh that holds up over time runs through a defined sequence of phases. Each phase has an output that feeds the next one. Skipping any phase shows up later as drift.

Discovery. Documentation of the current network. What is installed, where, how it is configured, who depends on it for what. Discovery includes interviews with the people who actually use the network (teachers in classrooms, staff in the operatory, designers at desks) because the asset list never tells the whole story.

Site survey. Measurement of the radio-frequency environment, the cabling paths, the rack space, the power available, the building materials that affect wireless propagation. The site survey produces a heatmap of the current wireless coverage and a sketch of where new equipment needs to land.

Design. Translation of discovery and survey into a network blueprint. Access-point count and placement, switch count and configuration, firewall sizing, cabling runs, Virtual Local Area Network (VLAN) segmentation. The design also includes a phased budget if the refresh cannot happen in one purchase cycle.

Procurement. Hardware ordered against the design. Lead times built into the project schedule (some Ruckus and Fortinet hardware has multi-week lead times, especially for large orders).

Installation. Physical cable runs, equipment mounting, initial configuration. For schools, this typically happens during the summer window. For dental clinics, evenings and weekends. For offices and agencies, after-hours sessions.

Commissioning. Verification that every piece of the network is doing what the design specified. Coverage tested in every room. Throughput measured under load. Firewall rules verified. Wireless roaming tested. The commissioning step is where bad installations get caught before the client signs off.

Documentation. The output the school or business owns at the end. Configuration backups, design diagrams, Internet Protocol (IP) address plans, vendor contacts, warranty information. Documentation lets future changes be made without re-doing the discovery work.

Handover. Walk-through with the school IT lead or business operations manager. Demonstrates what has changed, where to find documentation, who to call when something needs adjustment.

Why the order matters

Every phase exists because skipping it costs more than running it. Skipping discovery means installing gear in the wrong places. Skipping the site survey means access points where the signal does not reach. Skipping commissioning means the client discovers the install was incomplete months later, when a teacher cannot hear the projector or a clinical iPad will not connect at the back of the operatory.

The cheapest network refresh on paper is usually the one that skips the most phases. The actual cheapest, measured over five years, is the one that runs every phase properly and produces a network the building will not need to refresh again until the hardware ages out.

How long it actually takes

For a small business or independent school, a network refresh runs three to eight weeks from kickoff to handover. Discovery and survey take one to two weeks. Design takes a week. Procurement is the variable that pushes the timeline most often (two to six weeks depending on what is ordered). Install and commissioning are typically one to two weeks combined. Documentation and handover are a week.

The timeline is not how fast someone can swap the switches. It is how long the discipline takes when it is done correctly.

When to think about this

The right time to plan a network refresh is at least six months before the existing infrastructure stops working. After equipment fails, the project is no longer a refresh. It is an emergency, and emergencies skip phases. Schools should align refresh windows with summer. Businesses should align with quieter project periods. Either way, the time to start the conversation is well before the calendar event the refresh needs to be completed by.

A documented network refresh project is the gift the present-day school or business gives to the future IT person who has to maintain it. It is also the difference between a network that runs for ten years and one that needs to be redone in three.