UniFi · Project planning

Planning a Ubiquiti UniFi Network

Build the network around what the business needs to do. The equipment list should follow a clear plan for coverage, capacity, security and recovery.

In plain English

An uplink connects one part of the network to another. PoE is power carried over compatible Ethernet cabling. A UPS is battery backup with a finite runtime. Acceptance means the agreed checks showing that the required work succeeds.

Reviewed September 2026 · 3 minute read

Turn business needs into a short brief

Direct link

Count the people and devices using the network at the same time. Identify the applications that cannot tolerate interruptions, areas with poor service and expected growth. Obtain a floor plan and record building materials, separate structures and available pathways.

From requirement to a testable result
Business needWhat the plan should define
Reliable video callsCoverage and workload checks in the rooms that use them.
Guest internetGuest access plus tested restrictions on business systems.
New workstationsOutlet locations, tested cable runs and available switch ports.
Less disruptionOutage window, rollback and agreed failure/recovery checks.

Also record the provider handoff, internet speed, static addressing, VPN requirements, rack space, power, cooling and budget. A useful brief explains both the desired result and how the customer will accept it.

Choose the gateway, management and physical path

Direct link

Decide between an integrated Cloud Gateway and a separate gateway/application host. Confirm the exact model’s supported applications and scale. Compare routing performance with the intended security and VPN features enabled; port speed alone is not a performance promise.

Check the available management arrangements and current product specifications before ordering. Include optional service costs rather than assuming every related service is free.

  • Cabling: specify endpoints, cable and connector requirements, labels, pathways and the agreed level of testing.
  • Switching: allow for occupied ports, sensible expansion and uplink traffic.
  • PoE: match every device’s required mode and power to its port and the switch’s total budget.
  • Power: estimate actual load and UPS runtime; include the equipment needed to keep the intended service operating.

A switch can have spare PoE ports but insufficient remaining wattage. Review PoE capacity for the selected models. For separate buildings, choose the interconnection after assessing distance, environment and site conditions.

Plan wireless coverage and access together

Direct link

Place APs around occupied areas and real client demand. Account for walls, mounting orientation, interference and the available wired backhaul. More transmit power or more APs does not automatically improve the result.

Coordinate channels and widths, then validate with representative devices and applications. Manufacturer Wi-Fi guidance distinguishes sparse and dense environments; it does not replace testing your building. An internet speed test alone cannot separate Wi-Fi, switching and provider problems.

Document each network’s purpose, addressing, DHCP and allowed connections. Map wired ports and SSIDs to those networks. Test permitted applications as well as blocked access, and protect the administration path throughout changes.

Budget for operation and prove the result

Direct link

Include installation, support, subscriptions where applicable, power, spares, replacement and recovery in the comparison. Assign the customer owner, delegated administrators, update responsibility, alerts and backup storage.

  1. Match the installed cable labels, equipment inventory and port schedule.
  2. Verify wired connectivity, addressing and network access policy.
  3. Check Wi-Fi in the agreed areas with realistic workloads.
  4. Test agreed power or WAN failure scenarios in an approved window.
  5. Hand over backups, recovery access, diagrams and any unresolved exceptions.
Keep scope clear: recording, phone and door systems add their own design and support requirements. Fire and alarm installation is outside FryAVSI’s current scope.

Turn a requirement into a complete plan

Direct link

Your practical challenge

Plan for 12 desks, two APs and a shared printer. Count physical connections, calculate the PoE requirement, describe guest access and record one realistic busy-time test. Leave capacity for the growth you actually expect.

Explain your result, the evidence you used and what remains untested. Use the reference library when you need a chart or worked example.

Put it into practice

Check what you learned

Choose an answer for each question, then check your understanding. Your answers stay in this browser.

1. What should drive the equipment order?
2. A switch has enough PoE ports. What else must be checked?
3. What best verifies Wi-Fi after installation?

Read the answers and explanations
  1. An agreed requirements and acceptance plan

    A requirements-led design connects equipment choices to the business result and the checks that prove it.

  2. Each port's power capability and the total switch power budget

    Port count does not prove power compatibility or sufficient total available wattage.

  3. Tests in required areas using representative clients and workloads

    Real coverage and application checks show whether the design meets the brief in the places people work.

Sources and further reading

Keep your momentum

Ready for the next step?

If you can explain the example and your answer, try the next lesson. Revisit the feedback whenever you need it.

FryAVSI · Updated September 10, 2026

Reference this lesson or use a section’s direct link for a particular chart or example. How to cite an example.

FryAVSI · Northeast Ohio and beyond

A clear next step for your project.

Share the location, the challenge and your target timing. Our team will help define the work.

Talk with our team