Choosing a network installation contractor is a procurement decision about continuity, documentation and accountability—not a comparison of router brands. A capable supplier should understand the business process, inspect the site, coordinate cabling and active equipment, define acceptance tests and explain who owns the network after handover. This guide helps managers compare proposals before appointing a network installation company.
Zama Engineering Systems (ZES) provides its commercial service through the ICT and network infrastructure team. Use this article as a tender and supplier-evaluation checklist, then request a site-specific design rather than copying a generic equipment list.
1. Check whether the supplier begins with business requirements
The first conversation should cover sites, users, devices, applications, operating hours, critical processes, current faults and expected growth. A supplier that begins by selecting equipment before understanding the requirement may under-design one area and overspend in another.
Ask the bidder to restate the problem and measurable outcome. Examples include reliable scanner roaming in a warehouse, sufficient meeting-room capacity, documented branch links, fewer cable faults or a maintainable network for a new building. “Strong Wi-Fi everywhere” is not a measurable brief until areas, devices and test conditions are defined.
2. Demand a site and existing-infrastructure survey
Floor plans are useful but do not show every route obstruction, cabinet condition, wireless barrier, power dependency or provider handoff. The contractor should identify which parts of the proposal are based on verified measurements and which remain assumptions.
If existing equipment will be retained, models, support status, capacity, configuration access and compatibility need review. A low price based on unverified reuse can become an expensive variation after work begins.
3. Require a coordinated physical and logical design
The proposal should connect outlets, fibre, racks, switches, routers, access points, provider services and critical systems. It should show approximate topology, equipment roles, port and PoE capacity, uplinks, resilience assumptions and customer-controlled security decisions.
Passive and active scopes may be delivered by different teams, but the interfaces must have an owner. ZES coordinates its structured cabling service with switching, wireless and server-room requirements so missing patching or rack capacity is not discovered during commissioning.
4. Compare complete scope, not device price
Normalise each quotation across design, materials, licences, subscriptions, containment, racks, power dependencies, installation, configuration, testing, documentation, training, travel and support. Ask bidders to state:
- Exact equipment or performance specification
- Quantities and route assumptions
- Customer-supplied equipment and services
- Recurring licence, cloud or connectivity fees
- Working-at-height, civil, electrical and building-work inclusions
- Access, shutdown and programme assumptions
- Warranty source, exclusions and support process
A cheap hardware list can omit the engineering and records that make the installation usable.
5. Agree acceptance tests before installation
“The network is working” is not enough. The contract should state which copper links, fibre links, wireless areas, uplinks, failover functions and user scenarios will be tested and how results are recorded. Formal cabling certification is different from wire mapping; a Wi-Fi signal reading is different from capacity and roaming validation.
Use the ZES network audit and cabling certification guide to specify evidence. Any untested device, area or third-party dependency should remain visible at handover.
6. Inspect documentation and access ownership
The customer should receive an asset schedule, topology, cabinet and port records, test results included in scope, approved configurations, backups, licence ownership, provider details, known limitations and support contacts. Administrator accounts should be handed to authorised staff through an approved method.
Do not accept a design that depends indefinitely on one installer remembering undocumented settings. Good records make changes and support safer, even if another qualified engineer is appointed later.
7. Evaluate maintenance and lifecycle responsibility
Ask what happens when an access point fails, a switch reaches end of support, a provider circuit is unstable or a new floor is occupied. Response targets, remote access, monitoring, spare parts, travel and after-hours work should be clear.
A defined network maintenance contract is more useful than “free support” with no scope or duration. Product warranty, workmanship correction and ongoing managed support are different commitments.
A practical network contractor scorecard
| Evaluation area | Evidence to request |
|---|---|
| Requirement understanding | Written problem, users, applications, risks and outcomes |
| Survey quality | Verified routes, rooms, power, wireless conditions and assumptions |
| Technical design | Topology, capacity, interfaces, equipment schedule and dependencies |
| Delivery control | Programme, access, safety, change and shutdown plan |
| Testing | Named acceptance tests, limits and report format |
| Handover | As-builts, assets, configurations, results, training and limitations |
| Support | Service hours, priorities, response, parts, travel and exclusions |
| Proof | Relevant verifiable project references and current credentials required for the scope |
Score the evidence, not marketing language. A contractor should be willing to identify uncertainties and further survey needs instead of claiming every integration will work.
Red flags in a network installation proposal
- A fixed access-point count without floor plans, density or device information
- No outlet, rack, fibre, licence or recurring-cost schedule
- “Certified cabling” without a test method and deliverable
- One shared administrator password retained by the installer
- No distinction between internal network and internet-provider faults
- No plan for live migration, backups or rollback
- Unverified claims of blanket coverage, bandwidth or compatibility
- No labels, drawings, test results or handover allowance
Information to include in your request for quotation
- Site addresses, floors, rooms and drawings
- User, device and outlet estimates
- Critical applications and acceptable downtime
- Existing equipment, providers and known faults
- Wi-Fi coverage areas, device types and density
- CCTV, access control, voice or other networked systems
- Target programme, access rules and working hours
- Testing, records, training, warranty and support expectations
When this information is incomplete, ask for a paid or clearly bounded discovery stage. It is safer than forcing bidders to hide large assumptions inside one lump sum.
Frequently asked questions
Should we buy equipment before choosing the installer?
Only after compatibility, capacity, licences, warranty source and design have been verified. Early purchases can lock the project into the wrong port, power or management model.
Is the lowest quotation usually the best value?
No. Compare complete scope, engineering, testing, documentation, lifecycle and exclusions. A low bid may omit the work that prevents faults and variations.
Can one contractor handle cabling and Wi-Fi?
Yes, where the team has the required capability and defines each scope. The important issue is clear ownership of interfaces and acceptance tests.
Should the contractor provide references?
Ask for relevant, verifiable examples with customer permission. Project type, quantities, tests and result matter more than an unsupported client-logo wall.
Turn your network requirement into a procurement-ready scope
Send ZES the site, drawings, devices, applications, known problems and programme. The ICT team can propose a survey and a clearly bounded implementation plan.