Planning a Business Network Deployment
The most expensive networking mistake is surveying an empty building. Coverage measured across a bare warehouse floor bears no resemblance to coverage once racking is up and loaded, and by the time anyone discovers that, the cabling is in the ceiling and the access points are mounted.
Who this is for
- Fitting out a new site, or moving into one
- Replacing consumer or ageing equipment with something supportable
- Adding a warehouse, mezzanine, or outdoor area to an existing network
- Rolling out scanners or IP phones onto a network that was not designed for them
Establish what the network has to carry
- Inventory the client devices, including which bands they support. Warehouse scanners are frequently 2.4 GHz only, and that single fact can invalidate an otherwise sensible design.
- Count peak concurrent devices per area, not total headcount. A conference room is the densest place in most buildings for one hour at a time.
- Identify what must be segmented. Guest Wi-Fi, payment devices, cameras, and building systems generally should not share a network with staff machines.
- List everything needing PoE and its real power draw.
- Note anything that cannot tolerate interruption — payment terminals, voice, and any process that fails badly mid-transaction.
- Establish the internet link speed, which is usually the real ceiling for internet-bound traffic regardless of how good the LAN is.
Metal racking, stock, liquid inventory, cold rooms, and concrete all attenuate signal heavily. A survey in an empty warehouse produces coverage predictions that are simply wrong once it is full. If the site is not yet fitted out, survey again after it is and budget for adjusting access point placement — that contingency is much cheaper than discovering dead aisles during go-live.
Sizing access points on density, not area
The instinct is to place access points so their coverage circles overlap and stop there. That produces adequate coverage and inadequate capacity, because every device in range shares the same airtime.
Worked example. A distribution centre with a 30,000 square foot warehouse, a 40-person office, and a small conference suite.
- Warehouse: coverage-driven, but aisles create signal shadows. Access points positioned along aisles rather than in a grid, with a survey once racking is loaded.
- Office: capacity-driven at roughly 40 laptops plus phones and printers, so device count sets the number rather than square footage.
- Conference suite: highest density in short bursts. Designed for a full room, not an average one.
- Loading bay: outdoor-rated units, and a survey with the doors both open and closed.
Loaded racking blocks signal effectively. Access points placed on a uniform ceiling grid end up covering the tops of racks while the aisles where people work have dead spots. Positioning along aisles, sometimes with directional antennas down the aisle, is what actually works — and it is very hard to retrofit once cabling is in.
Roaming
Roaming is what lets a scanner or a phone move across a site without dropping its connection. It matters far more in warehouses and hospitals than in offices, and it is easy to design out accidentally.
- Plan overlap between cells, enough that a device can find the next access point before losing the current one.
- Keep transmit power consistent across access points. A single unit running much hotter creates a cell devices cling to long after they should have moved on.
- Use the same SSID and security settings everywhere, or roaming cannot be seamless.
- Test by walking the real route with the actual device — a full pick path, or a ward round — not by standing still and reading signal strength.
- Check voice and scanning applications specifically, since these fail visibly during a bad roam while a web page simply pauses.
VLAN design, decided before cabling
| VLAN | Why it is separate |
|---|---|
| Staff / corporate | The main working network. |
| Guest | Internet only, no reachability into anything internal. Non-negotiable if you offer guest Wi-Fi. |
| Voice | Separated for quality of service and simpler troubleshooting. |
| Payment / POS | Segmentation here is frequently a compliance requirement, not a preference. |
| Cameras and building systems | Chatty, rarely patched, and should not reach anything else. |
| Management | Switches, access points, UPS management cards, and out-of-band interfaces. Restricted to administrators. |
A guest network that can see internal systems is an open door, and "we gave them a separate password" is not separation. Guest traffic needs its own VLAN with client isolation and internet-only access. This is the most common serious misconfiguration in small business networks, and it is usually the result of adding guest access to a flat network after the fact.
Cabling and power
- Run cable to more locations than you plan to use. The cable is cheap during a fit-out and expensive afterwards. Spare drops at likely access point positions cost very little now.
- Use a cable category appropriate for the speeds you intend, including multi-gigabit access points.
- Respect maximum run lengths. Long runs cause intermittent faults that look like device problems.
- Plan the PoE budget across switches, not per port — see choosing switches and access points.
- Put network equipment on a UPS. A running server with no network is not much use — see sizing a UPS.
- Ventilate the comms room. Heat shortens the life of everything in it, batteries first.
- Label both ends of every cable during installation. Nobody ever does this afterwards.
Rolling it out
| Phase | What happens |
|---|---|
| 1. Inventory and requirements | Client devices and their bands, peak density per area, PoE list, segmentation needs. |
| 2. Survey | With the space as it will be used. Predictive design first if the building is empty, validated later. |
| 3. Design | Access point placement, VLANs, addressing, PoE and uplink sizing. |
| 4. Cable and power | Drops, comms room, UPS. The part that is expensive to change later. |
| 5. Configure and pilot one area | One floor or one zone, with real users and real devices. |
| 6. Validate by walking it | Roaming, dead spots, and the applications that actually matter. |
| 7. Roll out the rest | Applying what the pilot taught you. |
| 8. Document | Addressing, VLANs, credentials location, cable labels, and a floor plan with access point positions. |
A new laptop will connect almost anywhere. An eight-year-old 2.4 GHz scanner will not. Test coverage and roaming with the least capable device in the fleet, because that device defines where your network genuinely works — and it is the one whose failure stops the warehouse.
Official manufacturer resources
Design guidance, coverage planning tools, and validated reference designs are vendor-specific. Confirm against documentation for the models you are deploying.
Fitting out a site?
Send us a floor plan, the device inventory, and what each area is used for. We will help you size access points on density rather than area, and flag the cabling decisions that are expensive to reverse.
Still stuck? Talk to someone who works on this hardware daily.
Tell us the model, what you have already tried, and what you are seeing. We will tell you whether it is a setting, a consumable, or a part — and we will say so if you do not need to buy anything.
