Skip to content
SRS Networks
HomeNetwork InstallationSite Survey Checklist
Deployment Guides · Pre-Install Survey

Network Site Survey Checklist

Most published survey checklists cover wireless only. A deployment fails on the other six categories — closets, pathway, power, existing systems, and site access — so this one covers all of them.

1996
Surveying sites since
10,000+
Sites deployed
900+
Multi-site deployments
50
States covered

A network site survey should capture seven categories before any quote is written: building access and jurisdiction, MDF and IDF closet conditions, pathway and structural obstructions, power and cooling capacity, wireless and RF environment, existing network and low-voltage systems, and schedule and labor constraints. A survey covering only wireless — the common case — leaves the pathway, power, and closet discoveries to install day, which is where change orders come from.

SRS Networks is a nationwide IT infrastructure deployment partner headquartered in South San Francisco, California, surveying and deploying network infrastructure for multi-site enterprises and channel partners across the 48 contiguous states, Alaska, and Hawaii since 1996. Use this checklist to record site conditions, responsible owners and unresolved dependencies before approving installation work.

The 46-item survey checklist

Seven sections. Capture all of them and the quote that follows is a price rather than an estimate.

1. Building, access, and jurisdiction

7 items
  • Full site address, suite, and permitting jurisdiction
  • Building type — new construction, tenant improvement, or occupied retrofit
  • Total square footage and floors in scope
  • Ceiling type per area (open deck, hard lid, suspended grid, T-bar)
  • Construction era and any pre-1989 abatement exposure
  • Landlord or GC approval process, vendor onboarding, and escort requirements
  • Loading dock, freight elevator, and parking access for crews and material

2. MDF and IDF closets

7 items
  • MDF location, dimensions, and photo of existing conditions
  • IDF locations and whether each covers its area within 90 meters
  • Existing rack space, rack type, and available RU
  • Ladder rack and cable management in place or required
  • Grounding and bonding present per ANSI/TIA-607
  • Demarcation point location and carrier entrance path
  • Closet security — lockable, badge-controlled, or open access

3. Pathway and structure

7 items
  • Existing pathway type and remaining capacity (J-hooks, tray, conduit, innerduct)
  • Core drill or sleeve requirements between floors
  • Fire-rated wall penetrations identified and counted
  • Seismic bracing requirements per local code
  • Obstructions above ceiling — ductwork, plumbing, structural, existing abandoned cable
  • Outside-plant path for building-to-building runs, including trenching or aerial
  • Asbestos or hazmat survey status where core drilling is planned

4. Power and environmental

6 items
  • Dedicated circuits available at MDF and each IDF
  • UPS present, capacity, and battery age
  • Generator or backup power coverage for network equipment
  • Cooling and BTU load in each closet, measured not assumed
  • PoE budget required for planned APs, cameras, and devices
  • Temperature and humidity extremes in any non-conditioned space

5. Wireless and RF

7 items
  • Coverage areas required, including exterior, yard, and outbuildings
  • Construction materials that attenuate signal (concrete, plaster, foil insulation, racking)
  • Racking or inventory plan for warehouse space — survey at load, not empty
  • Client device types and their real capability (scanners, forklift terminals, robots)
  • Existing AP locations, models, and mounting method
  • Interference sources and neighboring networks captured in a spectrum scan
  • High-density areas requiring capacity design rather than coverage design

6. Existing network and systems

6 items
  • Existing switch inventory, port count, and available capacity
  • Circuit inventory — carrier, bandwidth, contract end dates
  • Existing cabling category, condition, and whether it is reusable
  • Camera, access control, and other low-voltage systems already on site
  • Documentation available from prior installs — as-builts, labeling, test reports
  • Systems that must remain live during the work, and their cutover constraints

7. Schedule, labor, and logistics

6 items
  • Standard-hours vs after-hours or weekend requirements
  • Operational blackout dates — peak season, fiscal close, production runs
  • Wage class (commercial, prevailing wage, Davis-Bacon, union jurisdiction)
  • Background check or clearance requirements for on-site technicians
  • Material staging and secure storage space on site
  • Site contact with authority to unlock doors and approve field changes

What a skipped survey actually costs

A remote survey runs $150–$400 and an on-site survey $450–$1,200 in 2026. A single revisit truck roll runs $450–$950 — so one discovery that sends a crew back has already erased the savings, and discoveries rarely arrive alone. The blocked riser that turns up on install day usually brings a permit question and a rescheduled crew with it.

The categories that get skipped are predictable. Wireless gets surveyed because there are tools for it and vendors who sell them. Closet grounding, pathway capacity, PoE budget, and the identity of the person who can actually unlock a door at 6 AM get skipped because nobody sells a tool for those. They are also the items that stop a crew cold.

On multi-site programs the survey does something the single-site math misses: it converts a portfolio of unknown buildings into a repeatable unit. Once twenty sites are surveyed to the same checklist, per-site pricing becomes real, waves can be planned honestly, and the twenty-first building stops being a surprise. Below roughly five sites in one metro, a good contractor's walk-through is enough — the formal package earns its cost at scale.

Remote or on-site?

Survey type2026 rangeRight when
Remote$150–$400Prototype sites in a known format, good existing documentation, a competent on-site contact who can photograph closets and pathway on request
On-site$450–$1,200Older buildings, warehouse RF, unknown pathway, occupied space, union or landlord constraints, or any site where the install cost would exceed a five-figure number

Full cost detail on network site survey cost, and the RF-specific method on wireless site survey.

Complete a network site-readiness workbook

Turn survey observations into a release decision. Record what is ready, what remains unknown, who must resolve it and the evidence needed before a crew is dispatched. Use one workbook per site; a checked box without a dated record does not establish readiness.

Free, no registration. Save the fillable PDF locally and confirm your entries are retained before sharing. Duplicate the register pages when you need more rows.

Set the site baseline and receiving authority

Enter the site ID, address, project revision and survey date. Name the customer project lead, facilities contact, network owner and person authorized to release physical work. Record access hours, escort arrangements and the contact who can open each required room. Use role names alongside contact details so ownership survives a staffing change.

Describe the intended physical scope in quantities: drops, access points, closets, rack positions and links between rooms. Reference the floor-plan revision and approved equipment list. Separate confirmed quantities from allowances. An unverified drawing should carry an open status and an owner rather than being copied into a final bill of materials.

Record dependencies with evidence, rather than assumptions

Create one register row for each dependency: pathways, room access, power, cooling, grounding, mounting, equipment delivery or carrier availability. Give it a unique ID, current status, responsible owner, due date and evidence reference. Evidence can be a dated photograph, approved drawing, delivery record or a specialist's written verification. Store sensitive records in your controlled project location; put the reference in the workbook.

For pathways, record origin, destination, route and the person who verified it. For power, reference the qualified facilities or electrical review instead of treating a visible receptacle as sufficient proof. For supplied equipment, reconcile actual received model and quantity against the approved list. Mark unknowns as open; do not use not applicable to conceal an incomplete survey.

Make the release, hold or conditional-release decision

Use ready only when the stated evidence has been accepted by the accountable owner. Use hold where a dependency prevents safe or authorized work. A conditional release must identify the permitted tasks, excluded tasks, approving authority and review point. A delivery promise is not evidence that material has arrived. Record any business deadline separately from technical readiness.

Before dispatch, review open rows with facilities and the customer network owner. Record the decision date, workbook revision and person approving the release. Give the field lead the approved scope and escalation route. If circumstances differ on arrival, stop the affected work and reopen the relevant dependency rather than improvising a route or extending the scope without approval.

Keep an exception trail and hand off the next decision

For every exception, write the observed condition, affected task, proposed action, approver and evidence needed to close it. Keep the original observation when adding the resolution. If an alternate route changes quantities or cost, reference the approved change before updating the baseline. The workbook records the decision; it does not replace a permit, engineering design or building authorization.

At release, list the exact documents sent to the crew and the receiving contact. After work, reconcile outstanding issues with the acceptance checklist and test records. Remove passwords, access codes and personal data from any copy shared outside the project team. A saved fillable PDF is a working record, not an automatically approved project release.

Worked example: a two-floor office

Illustrative scenario, not an SRS project or performance claim.

Fictional site SR-17 has one MDF, two IDFs, 48 data drops and 12 access points. The buyer records those quantities against floor plan revision B. Facilities owns pathway verification; customer IT owns the switch and PoE review. Each dependency has its own evidence reference and review status, so confirming the equipment delivery does not accidentally release the unverified pathway.

Hold example: the planned riser is blocked

The survey photographs show an obstruction on the proposed riser. SR-17 remains on hold for that pathway. Facilities must verify and obtain approval for an alternate route, attach the evidence and identify any scope change. The authorized project lead then records a revised release decision. The planned installation date alone cannot close this blocker.

Planning references

Background planning methods, not a substitute for project-specific engineering, current requirements or authorized change procedures.

Straight answers on site surveys

Seven categories: building access and permitting jurisdiction, MDF and IDF closet conditions, pathway and structural obstructions, power and cooling capacity, the wireless and RF environment, existing network and low-voltage systems, and schedule and labor constraints. Wireless-only surveys are the industry default and the reason pathway, power, and closet problems get discovered on install day instead of during planning.

Resolve the scope before requesting bids

  • Keep site survey photos available

    Define photo ownership, permitted access and export requirements in the closeout package. This is public planning guidance; project records remain access controlled.

Have SRS survey the sites

Send the site list. You get this checklist completed per building, photos, and a per-site install model priced from what we found — not from what a floor plan implied.

partners@srsnetworks.com · (866) 224-3636

Plan the field work behind asset tracking

For an RTLS project, define the approved layout, mounting access, model-specific infrastructure and commissioning handoff before comparing bids. These resources separate physical field work from platform responsibilities.