How to Run an IT Site Survey Before Onsite IT Support Services Begin

Quick answer: An IT site survey is a planned visit that documents a location’s access, network closet, equipment, cabling, power, connectivity, workspaces and risks before onsite IT support services begin. A small office usually takes one to three hours. Techmate runs surveys across 450+ US cities so every later visit starts from a known site profile.

Most companies learn about their branch offices one emergency at a time. The first time a technician visits is also the first time anyone discovers the closet is in a janitor’s room, the switch is unlabeled and the router is older than some employees. A site survey flips that. Instead of discovering the environment during a crisis, you document it on a calm day, and every future visit from your onsite IT support services provider starts with a map instead of guesswork.

This guide explains when to run an IT site survey, what it covers, how to run one, what the report should include and how to turn findings into action across many locations. A survey is the technician-side counterpart to the onsite IT support site readiness checklist: the checklist prepares the site, and the survey documents it.

Why does an IT site survey matter before onsite work starts?

Unknown conditions are the most common reason an onsite visit runs long or fails outright. A technician who arrives without the closet location, the key holder, the circuit ID or a photo of the rack spends the first hour finding things instead of fixing them. On an urgent dispatch, that hour is the outage.

The risks a survey surfaces are also the ones that cause real downtime. Uptime Institute’s 2025 outage analysis found that power remains the leading cause of impactful outages, IT and networking issues accounted for 23% of impactful outages, and 85% of human-error outages trace back to staff not following procedures or to flawed procedures (Uptime Institute via Business Wire, 2025). A survey checks exactly those things at the branch level: UPS coverage, overheating closets, undocumented changes and missing runbooks.

Unknown devices are a security problem too. ISACA, citing Microsoft’s Digital Defense Report, notes that more than 90% of ransomware incidents involved exploitation of unmanaged devices (ISACA, 2025). The forgotten consumer router in a branch closet or the old NAS under a desk is exactly what a walk-through finds and a remote scan can miss.

When should you run an IT site survey?

When onboarding a new onsite IT support provider
Before opening, relocating or closing a site
Before a multi-site project such as a Wi-Fi upgrade, firewall or SD-WAN rollout
After acquiring a company or its locations
When a site generates repeat tickets and nobody knows why
Periodically, for sites that have not been visited in a year or more
After a lease change, renovation or landlord work that may have moved cabling or equipment

What does an IT site survey cover?

A good survey follows the same sections at every site, so reports are comparable across your footprint.

Access and logistics

Entry procedure, badge or sign-in requirements and after-hours access
Parking and loading dock
Site contact and backup confirmed in person
Photos of the building entrance and the route to the closet

Network closet and rack

Closet location, size, lock and who holds the key
Ventilation and temperature (note if it feels warm, and whether a thermometer or sensor is present)
Rack type and condition
Front and rear photos of every rack
Cable management condition
Labeling present or missing
Non-IT items stored in the closet (boxes, cleaning supplies, holiday decorations)

Network equipment

Device	What to record	Why it matters
Modem or ISP handoff	Carrier, model, circuit ID if labeled, demarc location	Speeds up carrier tickets during an outage
Firewall or router	Make, model, serial, firmware if visible, labeling	Flags end-of-life hardware and support contract gaps
Switches	Make, model, serial, port count, PoE, uplink connections	Needed for remote hands requests and replacements
Access points	Count, locations, models, mounting	Baseline for Wi-Fi coverage planning
Other hardware	Phone system, cameras, door controllers, NAS, unknown devices	Surfaces unmanaged devices and third-party systems

Power

Is critical equipment on a UPS?
UPS model and battery age if visible
Outlets shared with non-IT equipment such as space heaters or appliances
Obvious hazards such as daisy-chained power strips

Cabling

Patch panel present and labeled
Wall jacks labeled to match the patch panel
Visible damaged or loose cabling
Unused cables left in place

Connectivity and performance

Wi-Fi coverage spot checks in key areas, including conference rooms and break rooms
Internet speed test at one or two locations, wired and wireless
Dead zones reported by staff

Workspaces and conference rooms

Number of workstations and their setup (docks, monitors)
Printers and MFPs with models
Conference room AV equipment and condition

Risks and issues

Anything likely to cause an outage or safety issue
Equipment past end of life
Water, heat or physical security concerns (ceiling leaks, unlocked closets, sprinklers over racks)

How do you run an IT site survey step by step?

Schedule with the site contact and explain what the technician will do. Surveys are low disruption but require closet access and brief access to workspaces.
Send the technician a survey template so every site is documented the same way.
Walk the site in a consistent order: entrance, closet, network, power, cabling, workspaces, conference rooms.
Photograph generously. Photos are often more useful than notes, and they let a remote engineer verify what the technician saw.
Label as you go, if authorized. Many surveys include applying labels to unlabeled equipment and patch panel ports.
Debrief with the site contact before leaving to capture local knowledge (“the Wi-Fi drops every afternoon in the back room”).
Submit a structured report within a day or two.

The template matters more than the technician’s experience. An experienced IT field technician with no template will still produce a report that cannot be compared with the next site. If you need a primer on what that role covers, see what is a field technician.

What should the survey report include?

Section	Contents	Who uses it
Site profile	Address, hours, contacts, access instructions, closet location	Dispatchers and every future technician
Equipment inventory	Every device with make, model and serial	Network team, asset management, procurement
Photos	Entrance, closet, racks front and back, workspaces, AV	Remote engineers guiding onsite work
Diagram	Simple sketch of how equipment connects, if possible	Network team and project planners
Findings	Issues ranked by risk: urgent, soon, eventually	IT leadership and budget owners
Recommendations	Suggested fixes, including quick wins	Project and operations teams

Store the report where dispatch can attach it to every future work order for that site. A survey that lives in someone’s inbox does not shorten the next visit.

How do you turn site survey findings into action?

Urgent risks (overheating closet, no UPS on critical equipment, failing hardware) should become tickets right away.
Quick wins (labeling, cable cleanup, moving storage out of the closet) can often be done during the survey or the next visit.
Larger issues (end-of-life equipment, poor Wi-Fi coverage) feed into project planning and budgets. See managing hardware refresh cycles across multiple sites.

Aggregate findings across sites to see patterns. If a third of your sites have no UPS, that is one project, not dozens of tickets. For network remediation such as re-patching, closet cleanup or switch replacement, scope the follow-up as onsite IT network services. For surveying many locations at once, see site audits and IT asset inventory projects across many locations.

How do you survey dozens or hundreds of locations?

Multi-location IT support teams rarely survey one site at a time. A portfolio survey is a project, and it runs best with a clear plan:

Prioritize sites. Start with the highest-revenue, highest-ticket or least-known locations.
Lock the template. Pilot it at two or three sites, fix the gaps, then freeze it for the rollout.
Batch by region. Schedule nearby sites in the same week to keep travel efficient.
Set a quality bar. Define the minimum photo set and required fields, and reject incomplete reports.
Roll up the data. Combine inventories and findings into one view, so leadership sees common risks by region and site type.

Because surveys are planned work, they fit naturally into IT project and rollout field support, using local technicians rather than flying staff between cities. Check onsite IT support locations to confirm coverage for your footprint.

What do site surveys look like for different site types?

Law firm offices: Extra attention to conference room AV, document scanners and printer security, plus confidentiality rules for technicians in client areas.
Bank and credit union branches: Teller and drive-through equipment, check scanners, camera systems and strict escort and access procedures.
Financial services and professional services offices: Trading or client-facing rooms, multi-monitor desks and a careful inventory of anything holding client data.
Real estate brokerages: Shared desks, MFPs and Wi-Fi coverage for agents who move between offices.
Retail stores: POS terminals, back-office closets that double as storage, and ISP handoffs in shared building spaces.

What mistakes make an IT site survey less useful?

No standard template. Every site gets documented differently, and nothing can be compared.
Too few photos. Notes like “rack is messy” do not help a remote engineer. A front and rear photo does.
Skipping the debrief. The office manager knows which room loses Wi-Fi and which outlet trips the breaker.
No owner for findings. If urgent risks are not turned into tickets, the survey only documents the next outage.
Never updating it. A site profile from three years and two renovations ago is not much better than none.

How long does a site survey take and what drives the cost?

A small office usually takes one to three hours. Larger offices with multiple closets or floors take longer. Surveys are typically scoped as standard scheduled onsite work, and the main cost drivers are site size, the number of closets, whether labeling or cleanup is included, and how much documentation is required. They often reduce future costs by shortening every subsequent visit and preventing emergencies. See how IT field support services work for how survey data feeds into dispatch.

How does a site survey improve onsite IT support services?

A survey gives every future technician a map of the site, so onsite IT support services start from knowledge instead of guesswork. Dispatchers can attach the site profile to each work order, remote engineers can reference rack photos during a call, and technicians know where the closet is and who holds the key before they arrive. Many teams make surveys the first step when launching onsite IT support services at a new location. See how Techmate dispatch works for the full request flow.

The bottom line

An IT site survey turns an unknown location into a documented one. Capture access, the closet, equipment, power, cabling, connectivity, workspaces and risks. Produce a consistent report, act on the findings and refresh it when the site changes. Every onsite visit after that starts from knowledge instead of guesswork. Techmate runs site surveys as standalone projects or as part of onboarding across 450+ US cities. Contact us.

Frequently Asked Questions

What is an IT site survey?

An IT site survey is a planned visit to document a location’s IT environment, including access, network closet, equipment, power, cabling, connectivity, workspaces and risks. The output is a site profile, an equipment inventory, a photo set and a ranked list of findings that makes every future onsite visit faster and more predictable.

How long does an IT site survey take?

A small office usually takes one to three hours. Larger or multi-floor sites take longer depending on the number of closets, workspaces and conference rooms, and on whether labeling or cable cleanup is included in the scope. Plan for a report to follow within a day or two.

What should be photographed during a site survey?

Photograph the building entrance, the route to the closet, the closet door and interior, racks from front and rear, network equipment labels, the ISP handoff, the UPS, workspaces, printers and conference room AV. Clear photos let remote engineers guide future work without another site visit.

When should I do an IT site survey?

Run one when onboarding a new provider, before opening, moving or closing a site, before multi-site projects, after acquisitions, for problem sites with repeat tickets, and periodically for sites not visited in a year or more. A renovation or lease change is also a good trigger.

What does an IT site survey report include?

A useful report includes a site profile, an equipment inventory with models and serials, a standard photo set, a simple network diagram, findings ranked by risk (urgent, soon, eventually) and recommendations, including quick wins that can be handled on the next scheduled visit.

Is an IT site survey worth the cost?

Usually. Surveys reduce future visit time, prevent failed visits caused by unknown conditions, surface risks like missing UPS coverage or overheating closets before they cause outages, and give leadership a portfolio-wide view of where to invest. For multi-location companies, the aggregated findings often shape the next year’s IT projects.

Should a site survey be part of onsite IT support services onboarding?

Yes. A survey during onboarding creates the site profile that makes every later onsite visit faster and more reliable. It also gives you and your provider a shared baseline, so both sides agree on what equipment exists and what condition it was in when support began.

Planning to survey your locations or onboard a new onsite provider? Book a free 30-minute IT support audit and we will review your sites, current documentation and coverage gaps, then recommend where to start.