01
A new facility or area
Coverage, capacity, installation, backhaul, power supply, and acceptance criteria need to be coordinated before access points are positioned.
A coordinated design for deployment and acceptance
Design and RF planning of Wi‑Fi networks
We turn site, client device, and application requirements into a Wi‑Fi network design. The design coordinates the RF model, access point placement, channel plan, backhaul, power supply, management, specification, and acceptance program.
Requirements and plans → radio model → access points and channels → transport and power supply → acceptance program
What is included in the design of a Wi‑Fi network
Wi‑Fi network design defines the target architecture and the coordinated decisions needed to estimate, deploy, and accept the network. Inputs include plans, site restrictions, applications, client devices, density, and operating requirements. Agreed deliverables include an RF model, access point placement, channel plan, connectivity diagrams, specification, and acceptance program. A site survey supplies field data; deployment implements the approved design.
When you need a project
02
Expansion of the existing network
New areas and client devices affect interference, capacity, channels, and power settings. The design accounts for existing infrastructure and the scope of changes.
03
Modernization of the platform
It is necessary to define the elements that are retained, dependencies, stepwise replacement, compatibility and the method of checking before and after transition.
04
Tendering or coordination between several contractors
A single set captures boundaries, requirements, specifications, versions and acceptance criteria for comparable offerings and managed implementation.
Required project inputs
| Required | Useful to have | We will clarify this together |
|---|---|---|
| Plans, areas and purpose of premises | Materials, heights, and existing cable routes | Required accuracy of the calculation model |
| Client devices and critical applications | Current WLAN, LAN, PoE and fiber-optic communication lines | Mobility scenarios and acceptance program |
| Restrictions on installation, access and operation | Information security, authentication and management requirements | Need for a survey or on-site validation |
| Design density and mode of use | Customer standards and acceptable models of equipment | Basic and extended documentation |
What parts of the network we design
01
RF model and access point placement
Calculation of coverage and capacity with documented initial assumptions, zones and required scenarios.
02
Channels and Power
We plan how access points will operate together. Settings are refined after deployment and field measurements where this is included in the next stage.
03
Backhaul, power supply, and installation
We document connections, port requirements, PoE, backbone links, mounting locations, and installation methods within the project scope.
04
Management, Access and Security
Document the segments, authentication, system roles and integration points that are compatible with the selected and confirmed platform.
05
Acceptance and operation
We define testable workflows and the documents and data needed to hand the network over to operations.
How the design works
- 01
We document the requirements
Define areas, client devices, applications, criticality, density, mobility, and site restrictions.
- 02
We verify the project inputs
Note the gaps, assumptions and the need for additional measurements or inspection.
- 03
Build a predictive RF model
Model access point placement and interaction using verified project inputs.
- 04
Design the architecture
Coordinate the RF layer with backhaul, power supply, management, access control, and installation.
- 05
We prepare the specification and acceptance criteria
We issue an agreed set, a program of checks and a register of open questions.
What the customer receives
- 01A statement of initial requirements and assumptions;
- 02A predictive RF model and access point placement plans;
- 03Channel plan and initial settings of the radio layer;
- 04Connection, power supply and segmentation scheme within the project boundaries;
- 05Specification of equipment and works in the agreed detail;
- 06Installation and labeling requirements;
- 07Program of acceptance tests;
- 08Register of versions, approvals and open questions.
What is included and what requires a separate agreement
| Included in the base scope | Agree separately | Not included automatically |
|---|---|---|
| Gathering requirements, verifying inputs, predictive modeling, architecture, and design documentation within the agreed scope | Site visits, Wi‑Fi site surveys, field checks, and additional architecture options | Supply, installation and commissioning |
| Specification and Acceptance Program | Detailed documentation for related disciplines, where required | A guarantee of actual performance if the project inputs change |
| Accounting for existing infrastructure based on the information provided | Design supervision and post-installation adjustments | Operational support after network handover |
How the project is checked
| Criterion | How to check | Where we document |
|---|---|---|
| Completeness of initial requirements | Checking areas, clients, applications, density and limitations | Requirements register |
| Traceability of solutions | Inputs and assumptions are stated for placement and architecture | Explanatory note and plans |
| Feasibility | Check mounting locations, backhaul, power supply, and contractor responsibilities | Plans, diagrams and specification |
| Testability of the result | A future test method is specified for the requirement | Acceptance test program |
| Change management | The source data version is associated with the project version | Version and Change Registry |
What determines timeframes and cost
The estimate depends on the size and number of areas, plan quality, materials and heights, density, client platforms and applications, existing infrastructure, security and integration requirements, site visits, design options, and documentation stage. An initial estimate requires plans, requirements, client device information, and a defined design scope.
Questions and answers
Frequently Asked Questions About Wi‑Fi Design
01Is a Wi‑Fi site survey always needed before design?
Not necessarily. For a new facility with accurate plans, known materials, and complete requirements, work can begin with a predictive model. An inspection or measurements may be needed if inputs are insufficient, the environment is complex, the network is already operating, or the consequences of error are significant. We assess the need for a site visit after reviewing plans, restrictions, client device workflows, and future acceptance criteria.
02What exactly is included in the finished project?
The task specification and contract define the design deliverables. These may include requirements and assumptions, a predictive RF model, access point placement, a channel plan, connectivity and power diagrams, a specification, installation requirements, and an acceptance program. Detailed documentation for related disciplines, site visits, design supervision, additional options, and editable source files require a separate agreement.
03Is it possible to use the project for tendering and installation by another company?
Use in a tender or by another installer depends on the agreed design stage, level of detail, file formats, and contractual rights of use. Before work starts, we document contractor responsibilities, the files to be handed over, and the change control process. The recipient must separately verify that the design is current, complete, and applicable to the actual site and selected equipment.
04Does the design model guarantee coverage after installation?
The predictive model shows expected performance for documented inputs and assumptions; it does not replace verification of the installed network. Actual materials, installation, equipment, settings, and the RF environment may differ from the model. Acceptance criteria are therefore agreed before deployment. Field measurements, adjustments, and repeat checks depend on the design scope and separately agreed contractual responsibilities.
05How is the extension of the existing network designed?
We first document the current architecture, equipment, channels, power settings, capacity, problem areas, and planned client devices. We then assess the interaction between existing and new access points, backhaul, power supply, management, and constraints on phased work. If inputs are insufficient, additional configuration data, an inspection, or a Wi‑Fi site survey within the agreed scope may be needed before the design is issued.
06Is it possible to change the initial data after the start of the work?
Yes, but changes to the area, layout, materials, density, client devices, equipment, or integrations may require recalculation and a new document issue. Each change is recorded before its impact on design decisions, scope, schedule, and results is assessed. The current input data version must be clearly linked to the current design version and the list of agreed deviations.
The next step
Define the Wi‑Fi design scope
Send plans, the areas to be covered, client devices and applications, density, mobility, and integration requirements. We will check whether the inputs are complete and define the design deliverables.
Material prepared by Connectum technical team · updated: August 2026