Contractor & Deployment Field Guide

Contractor Selection

Pre-Award Evaluation

■Verify low-voltage licensing in the specific jurisdiction, not just general contractor status
■Confirm prior experience in occupied or restricted environments: data centers, hospitals, government facilities
■Ask for references from projects with split authority, construction manager plus a separate security owner, to confirm they can navigate that structure
■Review background screening program: what is checked, how deep, and whether it meets your facility threshold
■Evaluate foreman and field supervision depth, not just the PM they put in front of you at the bid table
■Confirm subcontractor usage and verify subs go through identical vetting as the prime
■Ask how they handle RFIs and scope creep — that is where low-voltage projects collapse

Security-Specific Gates

■Badge and escort protocol compliance in restricted zones
■Chain of custody procedures for hardware pre-installation
■Tool and material control in secured spaces
■NDA and confidentiality agreements at the individual worker level, not just the company
■Demonstrated ability to work under security escort without degrading project pace

Vendor Management

Selection

■Separate the integrator relationship from the manufacturer relationship and never let one drive the other
■Evaluate whether the recommended product serves your architecture or the integrator's margin
■Confirm manufacturer direct support availability, especially for access control and video platforms
■Assess lock-in risk: licensing model, data portability, API openness, and what happens at contract end
■Require a reference site you can physically visit or speak to directly before award

Ongoing Governance

■Establish a single named point of contact at the vendor and hold them accountable to it
■Set escalation paths in writing before project kickoff
■Require firmware and software update schedules with advance notice built into the contract
■Track warranty coverage by device and location from day one, not at first failure
■Log every RMA and resolution time so you have real performance data at renewal

Deployment & Project Execution

Pre-Deployment

■Confirm conduit and pathway ownership before any pull — know who owns what above the ceiling
■Validate power availability at each device location; do not assume the electrical plan matches field reality
■Sequence low-voltage work around commissioning windows to avoid conflict with live environments
■Align NEA, PFH, and CICO milestones with your security activation requirements in writing before work starts
■Get the cable schedule, device schedule, and as-built expectation agreed and signed before any installation begins

MILESTONE

NEA, PFH, and CICO milestones must be reconciled with your security system activation sequence. A commissioning team that moves faster than your access control cutover creates a gap. Lock that schedule alignment in writing before work starts.

Communication: The Core Discipline

RULE ONE

Even when you are not organizationally under the construction manager, treat that relationship as mandatory, not optional. Touch base every single day. Know their schedule, their open issues, and what trades are active in your work zones before you walk the floor.

Daily CM Interface

■Check in with the construction manager every day, even a two-minute conversation counts
■Know what trades are active in your work zones before you show up to the site
■Get on the daily standup or huddle if one exists — if not, request your own standing slot
■Keep the CM informed of your findings before they hear about them from someone else

Project Manager and Technical PM Alignment

■Confirm who owns scope interpretation: the PM or the TPM. Make sure they agree with each other before you take direction from either
■Push issues up to the TPM early — do not let field-level disputes sit unresolved
■Document every verbal direction change with a written follow-up email the same day
■Never accept a "we'll sort it out later" on scope — that is how change orders become disputes

Repetitive Walk-Downs

RULE TWO

Do not wait for a milestone inspection to find drift. Walk your work zones on a daily cadence during active installation phases and use a consistent checklist every time. Walk with the CM whenever possible so your observations are witnessed and shared.

What to Check on Every Walk

■Device rough-in locations against the approved drawing — verify position, not just presence
■Cable routing against the pathway plan
■Label consistency and accuracy at every termination point
■Penetration sealing status in fire-rated assemblies
■Work area cleanliness and material staging compliance
■Badge and escort compliance for every worker in restricted areas

Documentation on Every Walk

■Photograph rough-in before walls close and before ceilings close — you will need those photos
■Log the walk date, time, areas covered, and who accompanied you
■Log every deficiency with location, a description, and the corrective expectation
■Maintain your own field log separate from the contractor's log
■Keep your own punch list distinct from the one the contractor submits

When the Contractor Is Not Performing

CRITICAL

Build your paper trail from the first missed obligation, not the third. A contractor that ignores a written finding twice is a program risk. Do not wait for a pattern to be obvious before you escalate.

Immediate Actions

■Conduct your own independent walks and document every finding — do not wait for self-reporting
■Photo-document every deficiency with location, date, and time on every image
■Issue a written finding log and require a written response with a resolution date
■Walk with the CM when possible so findings are witnessed and entered into the project record
■Escalate repeat findings immediately — two ignored written findings is a program risk, not a scheduling issue

Formal Escalation

■Issue a written notice of concern tied to a specific SOW provision, not a general complaint
■Set a correction deadline in writing with a specific date, not a vague timeframe
■Escalate to the CM in writing so findings enter the official project record
■If the CM is non-responsive, escalate to the owner's representative or TPM with the same documentation
■Know your contract's cure period and default provisions before you need them

DOCUMENT

Maintain your own field log independent of the contractor's records. Log every walk, every verbal direction, every deviation from the approved plan. Keep a punch list you control. These records are your protection if the project ends in dispute.