November 1, 2026 • Centoffer Editorial • 17 min read
IT Site Survey Checklist: What to Check Before Any Network or Equipment Installation
An IT site survey is a structured on-site inspection done before an installation to confirm the location can physically accept the equipment: power and circuits, cabling paths and distances, rack space, cooling, Wi-Fi conditions, building access, permits and safety. Doing it first turns a risky install day into a predictable one and stops engineers being sent to sites that are not ready.
IT Site Survey Checklist: What to Check Before Any Network or Equipment Installation
An IT site survey is the cheapest insurance an infrastructure project can buy. Before a switch is racked, an access point is mounted or a point-of-sale lane is cabled, someone has to stand in the room and confirm that the site can actually accept the work. When that step is skipped, the installation day becomes the survey: engineers arrive to find a locked comms room, no free power outlet, a ceiling that cannot be opened without the landlord’s permission, or a cable route that runs longer than the standard allows. The engineer leaves, the visit is billed, and the go-live date slips.
This guide is written for enterprise IT buyers and project managers who run installations across many sites — branch networks, store rollouts, office moves, warehouse upgrades — and want every install day to land first time. It covers what a site readiness survey is, what to check category by category, how to structure the report, how to run surveys at scale across countries, and the mistakes that most often turn a “ready” site into a failed visit.
What is an IT site survey, and why does it matter?
An IT site survey (also called a site readiness survey or pre-installation survey) is a structured, on-site inspection carried out before a network or equipment installation to confirm that the location is physically, electrically and administratively ready. It answers one question for every site: if we send the installation team on the planned date with the planned kit, will they be able to finish the job?
It matters because installation failures are rarely technical. A switch configuration can be prepared and tested in advance; a missing circuit breaker or an unapproved ceiling penetration cannot. The site survey moves those physical and procedural risks to the front of the project, when they are cheap to fix, instead of discovering them on install day, when they cost a wasted dispatch and a missed deadline.
There is also a downstream reason. Infrastructure problems that start with a poorly prepared site tend to resurface as outages later. Uptime Institute’s Annual Outage Analysis 2024 reports that power issues are consistently the most common cause of serious and severe data centre outages, and that 54% of operators surveyed said their most recent significant outage cost more than US$100,000, with 16% putting it above US$1 million. Branch sites and stores are not data centres, but the lesson transfers: power, cooling and physical layout decisions made on install day are hard to undo, so check them properly before the equipment arrives.
What is the difference between a site survey, a Wi-Fi survey and a site audit?
These terms get used interchangeably, which causes scoping mistakes. Buyers sometimes order a “site survey” expecting a full readiness check and receive a wireless heat map, or the reverse. The table below separates them.
| Survey type | Main question it answers | Typical outputs | When to use it |
|---|---|---|---|
| IT site readiness survey | Can this site physically accept the planned installation? | Readiness verdict, photos, measurements, power and rack details, remediation list | Before any network, server, POS or AV installation |
| Wi-Fi (wireless) site survey | Where should access points go, and will coverage meet the requirement? | Coverage and signal maps, AP placement plan, interference notes | New wireless deployments, density upgrades, warehouse scanning |
| Asset or site audit | What is currently installed, and in what condition? | Asset inventory, serials, condition notes, labelling gaps | Before a refresh, takeover from another provider or decommission |
| Post-installation verification | Was the work done to specification? | Test results, as-built photos, labelling check, sign-off | After installation, before acceptance and payment |
For most rollouts, the most efficient approach is to combine the readiness survey with a light asset audit in one visit, and add a measured wireless survey where Wi-Fi is in scope. That saves a dispatch per site, which adds up quickly across a 50- or 200-site programme.
What should an IT site survey checklist include?
A complete IT site survey checklist covers eight areas: scope and drawings, power, cabling and pathways, space and racks, environment and cooling, connectivity, wireless conditions, and access, permits and safety. Each is broken down below with the questions the engineer should be able to answer by the end of the visit.
1. Scope, drawings and site contacts
Before anyone travels, the survey engineer needs the project scope in writing: what equipment will be installed, where, and what it connects to. On site, they confirm it against reality.
- Is the floor plan current, and does it match the actual room layout?
- Where exactly will each device be installed (rack position, wall, ceiling, desk, POS lane)?
- Who is the on-site contact on install day, and who can authorise access to restricted areas?
- Are there other contractors (electricians, fit-out, landlord engineers) working on the same dates?
2. Power
Power is where installation days most often fail, and where the long-term risk is highest.
- Is there a dedicated circuit for network and server equipment, or will it share with general office loads?
- How many free outlets are available at each equipment location, and of what type?
- Is there a UPS, what is its capacity and current load, and is its battery within service life?
- Is the earthing (grounding) adequate for the rack, and is it documented?
- For devices powered by Power over Ethernet (PoE), does the planned switch have enough PoE budget?
The PoE question deserves attention because modern access points, cameras and some POS peripherals draw significant power from the switch. According to the Ethernet Alliance’s overview of the IEEE 802.3bt standard (2018), the four PoE types deliver up to 15.4 W (Type 1, 802.3af), 30 W (Type 2, 802.3at), 60 W (Type 3) and 90 W (Type 4, 802.3bt) at the switch port, with less available at the device after cable losses — 71 W for Type 4. The survey should list each PoE device and its class so the switch’s total power budget can be checked before purchase, not after the access points fail to boot.
3. Cabling and pathways
Cabling is where measurements matter more than impressions.
- Measure the actual route — up the wall, across the ceiling, down to the outlet — not the straight-line distance on a floor plan.
- Note existing cable trays, conduits and ceiling types, and whether new pathways are needed.
- Identify fire-rated walls and floors that will need penetrations and firestopping.
- Record the existing patch panel, labelling scheme and spare ports.
- Check whether existing cabling can be reused, and whether it is certified or merely “working”.
For copper Ethernet, the hard limit comes from the cabling standard. Panduit’s 2024 guide to Ethernet link deployments, summarising TIA-568.2-D, describes a permanent link of up to 90 metres and a full channel of up to 100 metres including patch cords. Any planned run approaching that length needs a different design — an intermediate switch, a fibre uplink or a relocated cabinet — and that decision belongs in the survey report, not in the installer’s van.
4. Space, racks and mounting
- Is there physical space for the rack or wall cabinet, including door swing and rear access?
- What is the current rack elevation, and how many free rack units (U) are available?
- Can the floor or wall carry the weight of the planned equipment?
- For ceiling-mounted access points or cameras, what is the ceiling type and height, and is a lift or ladder needed?
- At retail and hospitality sites, where can equipment go without being visible to or reachable by customers?
A photographed rack elevation, with free U positions marked, is one of the most useful single artefacts a survey can produce. It lets the installation team pre-plan cable management and avoids the common “there is no room in the rack” discovery.
5. Environment and cooling
- What is the temperature in the equipment room or cabinet during business hours, and what happens after hours when building air conditioning switches off?
- Is the cabinet in a cupboard with no ventilation, next to a heat source, or exposed to dust, moisture or direct sunlight?
- Is there water or drainage pipework above the equipment location?
As a reference point, the U.S. Department of Energy’s 2021 data centre thermal guidelines webinar, citing ASHRAE’s Thermal Guidelines for Data Processing Environments (5th edition, 2021), recommends an IT equipment air-intake temperature range of 18–27 °C. A branch comms cupboard does not need data-centre engineering, but a cabinet that regularly runs well above that range will shorten equipment life and should be flagged for ventilation or relocation.
6. Connectivity and carrier handoff
- Where does the carrier circuit enter the building, and where is the demarcation point?
- Is the circuit live, tested and labelled, and who holds the provider’s reference number?
- Is there a backup path (4G/5G router, second carrier), and is there signal at the router’s planned location?
- How will the new equipment physically reach the demarcation point?
Carrier readiness is a classic hidden dependency. The installation team can do everything right and still fail if the circuit has not been delivered, or has been delivered to a different floor.
7. Wireless conditions
If Wi-Fi is in scope, the readiness survey should at least note building materials, ceiling heights, sources of interference and the areas where coverage matters most (checkout lanes, warehouse aisles, meeting rooms). Where reliable voice, scanning or mobile POS is required, commission a measured wireless survey. A long-standing design rule comes from Cisco’s site-survey guidance for voice over Wi-Fi, which recommends a cell-edge signal of −67 dBm with 15–20% overlap between neighbouring access point cells; your vendor or wireless designer will set the exact target for your devices, but the survey should state what threshold was used.
8. Access, permits and safety
This category is administrative, and that is why it gets skipped.
- What are the building’s working hours for contractors, and is after-hours work allowed?
- Does the landlord or building management require method statements, risk assessments, insurance certificates or permits for ceiling or riser work?
- Is there a loading dock, goods lift and somewhere to stage equipment?
- Are there hazards the installation team must plan for — work at height, asbestos registers in older buildings, confined risers, live electrical panels?
- What personal protective equipment and site induction does the location require?
A large share of “failed” install days fail here: the engineer arrives on time with the right kit, and is turned away at reception because no work permit was lodged.
How do you run an IT site survey step by step?
A repeatable process matters more than any single checklist item. The following sequence works for single sites and scales to multi-country rollouts.
- Define the scope and the survey template. Agree in writing what will be installed and which checklist sections apply. Use one template for the whole programme so reports are comparable.
- Collect what already exists. Floor plans, previous audit data, carrier order references, landlord rules and photos from the site contact all reduce time on site.
- Book the visit with the site contact. Confirm access to every room on the list, including comms rooms, ceiling voids and risers. A survey that cannot see the comms room is not a survey.
- Survey on site. The engineer works through the checklist, measures cable routes, photographs every equipment location and pathway, and records power, rack and environmental details.
- Record evidence, not opinions. Every finding should carry a photo, a measurement or a document reference. “Rack looks fine” is not evidence; “Rack 42U, positions 30–38 free, photo 14” is.
- Issue a readiness verdict. Go, conditional go (ready once named items are fixed) or no-go.
- Assign remediation. Each open item gets an owner (landlord, store manager, electrician, carrier, IT team) and a due date.
- Re-confirm before install day. A short check — a call, updated photos or a revisit for no-go sites — confirms that remediation actually happened before engineers are dispatched.
This is the same logic as an SLA-governed field job: a defined scope, a standard procedure and a proof-of-delivery record at the end. On Centoffer, surveys are dispatched and closed like any other field job, with the engineer’s photos and checklist attached as the proof of delivery for that visit.
What does a good site survey report look like?
A good site survey report lets someone who has never visited the site plan the installation with confidence. It should be short enough to read in ten minutes and complete enough that nobody needs to phone the engineer afterwards.
Recommended sections:
- Header: site name and address, survey date, engineer, site contact, project reference.
- Verdict: go / conditional go / no-go, with a one-paragraph reason.
- Equipment locations: a photo and a short description for each planned device position.
- Power: circuits, outlets, UPS, earthing, PoE requirements.
- Cabling: measured routes, pathways, penetrations, patch panel and labelling status.
- Rack and space: rack elevation with free U, mounting surfaces, ceiling details.
- Environment: temperature observations, ventilation, risks such as water pipes.
- Connectivity: carrier demarcation, circuit status, backup connectivity signal.
- Wireless notes or survey results, where in scope.
- Access and safety: working hours, permits required, hazards, PPE and induction.
- Remediation list: item, owner, due date, status.
- Bill of materials impact: anything the survey adds or removes (longer cables, extra PoE budget, a wall cabinet instead of a floor rack).
The bill-of-materials section is often missing, and it is where surveys pay for themselves: they convert a generic kit list into a site-specific one before purchase orders are raised.
How do you run site surveys across many locations and countries?
Surveying one office is easy. Surveying 80 stores across six countries before a network refresh is a programme in its own right, and the problems change.
Standardise the checklist, localise the rules. The technical questions are the same everywhere, but building access, permit and safety requirements differ by country, city and landlord. Keep one core template and add a short local appendix for each market.
Batch by geography. Group surveys so one engineer covers several nearby sites in a day. This is where a dispatch model built on location matters; our article on how geo-dispatch matches engineers to jobs explains the mechanics.
Use local engineers with the right skill profile. A survey engineer who will never install anything tends to miss practical details. Use engineers qualified for the installation itself, ideally from the same pool that will do the install.
Track readiness as a pipeline. Across a large rollout, the useful view is not “surveys done” but “sites ready”. Track every site through surveyed → remediation open → ready → scheduled → installed → accepted.
Make the evidence comparable. If every engineer photographs different things, programme-level review becomes impossible. Specify mandatory photos (comms room wide shot, rack front, demarcation point, each device location, each cable route start and end).
| Programme challenge | What goes wrong | What to do instead |
|---|---|---|
| Different engineers in different countries | Inconsistent reports, missing data | One template, mandatory photo list, report review before closure |
| Landlord and permit rules vary | Install crews turned away on the day | Local access and permit appendix per market; lead times recorded in the survey |
| Long lead time between survey and install | Site changes after the survey | Re-confirmation step 48–72 hours before install day |
| Survey treated as a formality | ”Looks fine” reports, failed install days | Evidence-based findings and a named go/no-go decision |
| Remediation has no owner | Open items never closed | Owner and due date for every item, tracked to closure |
How much does an IT site survey cost compared with a failed install day?
Survey pricing varies by country, site size and whether a measured wireless survey is included, so there is no meaningful single market price to quote. The more useful comparison is internal: a survey visit usually costs roughly the same as one engineer visit, and a failed install day usually costs at least one engineer visit plus the knock-on costs.
A worked example makes the trade-off concrete. Suppose a 40-site rollout is planned without surveys, and one site in five turns out not to be ready on install day. That is eight failed visits, each needing a second dispatch, plus eight rescheduled go-lives and the internal time to re-plan them. With surveys, the same eight sites are identified in advance and fixed before anyone is dispatched to install. Whether surveying is cheaper depends on your own failure rate and visit cost, so use your own numbers: if your historical first-attempt failure rate on installs is above a few percent, surveying every site is almost always the better bet. If you have no data, that itself is a reason to survey the first wave and measure.
There is also a quality argument that does not show up in visit counts. Uptime Institute’s 2024 analysis estimates that human error plays a part in roughly two-thirds to four-fifths of downtime incidents, and that the most commonly cited human-error causes are staff not following procedures and procedures that are themselves wrong. A survey with a standard checklist is, in effect, a procedure written before the installation starts.
What are the most common site survey mistakes?
- Surveying from drawings instead of the building. Floor plans are often years out of date. Walk the route.
- Not seeing the comms room. If the key holder is absent, reschedule — do not guess.
- Measuring straight lines. Cable runs go up walls and around obstacles; measure the real path.
- Ignoring after-hours conditions. Temperature, access and noise restrictions change outside business hours, which is when many installs happen.
- Forgetting the landlord. Ceiling, riser and roof work often needs approval with a lead time of days or weeks.
- No go/no-go decision. A report full of observations without a verdict leaves the project manager to guess.
- No owner for remediation. Findings without owners do not get fixed.
- No re-confirmation. Sites change; check again shortly before install day.
- Surveying with the wrong skill set. A general technician may miss PoE budgets, fibre requirements or wireless implications.
- Leaving the survey out of the contract. If the survey is not a defined deliverable with acceptance criteria, it tends to become a quick walk-through.
How should you contract and measure IT site surveys?
Treat the survey as a deliverable with its own acceptance criteria, not a free add-on to the installation quote. A clear statement of work includes:
- Scope: which checklist sections apply and whether a measured wireless survey is included.
- Deliverable: the report template, mandatory photos and the deadline for submission after the visit (for example, within one or two business days).
- Acceptance: the report is complete when all mandatory fields and photos are present and a verdict is given.
- Service levels: time to schedule after the request, attendance on the booked date, and report turnaround — measured the same way as any field service SLA.
- Liability for misses: if an installation fails because of a condition the survey should have recorded, who pays for the return visit?
That last clause changes behaviour more than any checklist. When the survey provider shares the cost of a failed install day, surveys get done thoroughly.
Useful metrics to track across a programme:
- Percentage of sites with a first-time-right installation after a “go” verdict.
- Average time from survey to “ready” status.
- Number of remediation items per site, by category (power, access, cabling…), which shows where your estate is weakest.
- Report rejection rate at review, which shows survey quality by engineer or provider.
How does a site survey fit into the wider installation workflow?
A site survey is the first link in a chain: survey → remediation → staging → installation → verification → handover. Each step should produce evidence the next one relies on. The survey’s photos and measurements feed the installation plan; the installation’s as-built photos and test results feed acceptance; acceptance feeds the asset register.
Where a remote team directs a local engineer — for example, a central network team configuring equipment while a local technician racks and patches it — the survey also establishes what the on-site engineer will need to know. That model, often called smart hands, works best when the remote team has seen the survey photos before the day.
The same chain applies whether the project is a single office fit-out or a regional rollout. What changes at scale is the need for consistent evidence, local engineers in every market and a single place to track every site’s status.
Plan your next installation on surveyed ground
Every failed install day has a cause that could have been found in advance. An IT site survey — done with a standard checklist, real measurements, photographic evidence and a clear go/no-go verdict — turns installations from hopeful dispatches into planned work.
Centoffer dispatches vetted local field engineers for site surveys, installations and follow-up work, with SLA tracking and proof of delivery on every job. Our IT field services cover network and structured cabling work, including Wi-Fi surveys and infrastructure smart hands. If you are planning a multi-site rollout, talk to our team about running the survey wave first.
Frequently Asked Questions
What is an IT site survey?
An IT site survey is an on-site inspection carried out before a network or equipment installation. A field engineer checks power, cabling routes and distances, rack and wall space, cooling, Wi-Fi conditions, building access and safety, then reports whether the site is ready and what must be fixed first.
How long does an IT site survey take?
A small office or retail store is typically surveyed in a single visit of a few hours, while a multi-floor building or warehouse can take a full day or more. Duration depends on floor area, how many rooms hold equipment, and whether a wireless survey with measurements is included.
Is a Wi-Fi site survey the same as an IT site survey?
No. A Wi-Fi site survey focuses on radio coverage, interference and access point placement. An IT site readiness survey is broader: it also covers power, cabling, racks, cooling, access, permits and safety. Many projects combine both into one visit to save a dispatch.
Who should perform a pre-installation site survey?
Ideally a field engineer with the same skills as the installation team, briefed with the project scope, floor plans and a standard checklist. Survey quality depends on consistency, so use a template, require photos and measurements, and have the report reviewed before install dates are confirmed.
What should a site survey report include?
A readiness verdict (go, conditional or no-go), photos of every equipment location and cable path, measured distances, power and circuit details, rack elevation, access and permit requirements, safety observations, and a remediation list with an owner and due date for each item.