Prevailing wage and public works rules in technology contracts

Reference article · 5 min read

A technology project can be a services contract in one phase and a construction contract in the next, depending on what the vendor does on site. When the scope includes pulling cable through a building, mounting cameras and sensors, trenching or lashing fiber, or wiring and cooling a new equipment room, the work may meet the state's definition of public works. A different body of law then attaches: prevailing wage rates, certified payroll, apprenticeship obligations, contractor licensing and registration, and bonding. These rules do not follow the budget code the money came from, and they do not care whether the agency calls the contract IT or construction.

Definitions, thresholds, covered classifications, and exemptions are set by state statute, and in many places by local ordinance as well. Coverage is broad in some states and narrow in others, and a few states have no prevailing wage law at all. Federal construction funding can bring its own labor standards regardless of state law. Confirm the answer for a specific project with the agency's counsel or labor compliance office before the solicitation is released.

What pulls technology work into public works

The nature of the activity. Construction, alteration, installation, and repair are typically covered. In several states maintenance of public property is covered too, which can reach service agreements that include on-site repair.
Attachment to real property. Work that becomes part of a building, a right of way, or a fixed structure tends to be covered. Equipment delivered, plugged in, and carried away again usually is not.
Where the labor is performed. On-site labor is the usual trigger. Work done at the vendor's own offices, including configuration and remote implementation, generally falls outside.
The source of funds. Public funds trigger state law, and federal awards can trigger Davis-Bacon requirements through the grant terms. Read the assistance agreement rather than assuming.

The situations that actually come up

Structured cabling and low voltage. Running backbone and horizontal cable, terminating at patch panels, and installing pathways is installation work and frequently covered. Classification varies: some states have a distinct sound and communications classification with rates different from inside wireman.
Cameras, sensors, and access control. Mounting hardware, running conduit, pulling power, and setting poles is field construction. Head-end configuration and integration with a records system usually is not.
Outside plant fiber. Trenching, boring, aerial lashing, and vault work is construction by any reading, and brings licensing, encroachment permits, and traffic control.
Data center and equipment room work. Electrical distribution, generators, cooling, fire suppression, grounding, and rack installation are covered trades. Racking a server in an existing cabinet is a closer call.
Software configured remotely. Provisioning, configuration, data migration, interface development, and training are services, and a project limited to these is normally outside public works rules.
Mixed scope integrations. The common real case: one award covering software, hardware, and field installation, where only part is covered.

The obligations that come with coverage

Wage determination and classification. The classification applied to each worker, not just the general determination for the county, drives the rate. Misclassified cabling technicians are a frequent source of back wage claims.
Certified payroll. Weekly records of hours, classifications, rates, and deductions, submitted to the agency or a state portal on schedule and retained for a set period.
Apprenticeship. Where required, notice to apprenticeship committees, ratios of apprentice to journeyman hours, and training fund contributions.
Registration and licensing. Some states require contractors and subcontractors to register with the labor agency before bidding. Field trades require a contractor's license a software firm will not hold.
Bonding and retention. Payment and performance bonds above statutory thresholds, retention withheld from progress payments, and stop payment notices in place of lien rights.
Additional conditions. Project labor agreements, skilled workforce requirements, and local hire preferences apply in some jurisdictions.

Decisions to make before the solicitation is released

Write the field work into the scope explicitly, including who furnishes conduit, pathways, power, and mounts.
Get a coverage determination in writing that addresses each portion of the scope separately.
If any portion is covered, attach the applicable wage determination and compliance language to the solicitation. Adding them after award means a change order and a higher price.
Decide the structure: one prime with a licensed installation subcontractor, or separate awards for construction and software.
Align bonding, insurance, and license requirements with the covered portion rather than applying construction terms to the whole contract.
Budget the compliance administration: someone on the agency side reviews payrolls and responds to complaints.

What to ask vendors, and what to require

Which portions of this scope do you treat as covered work, and on what basis.
Who performs the field labor, your employees or a subcontractor, and what are their license and registration numbers.
Can you produce certified payroll in the portal this agency uses, and who prepares it.
How do you meet apprenticeship requirements on a project of this size.
Price covered field labor separately from software, licensing, and remote services.

In the contract, make compliance an express obligation, require flow-down to every subcontractor, condition payment on current certified payroll, and reserve the right to withhold for noncompliance. Keep software deliverables on their own payment schedule so an installation dispute does not stall the rest of the project.

Where this goes wrong

Coverage is usually discovered late, after a vendor has priced the work without prevailing wage in it. Two other recurring errors: assuming a cooperative or statewide contract purchase waives prevailing wage, and treating a managed service with on-site repair as exempt without checking the state's maintenance definition.

HQT works on integration projects that combine software with field installation, and separates scope and pricing so agencies can see which portion a coverage determination affects.

Frequently asked questions

Does prevailing wage apply to low voltage and structured cabling work?

In many states it does, because pulling and terminating cable in a public building is treated as installation work on public property. The classification used, and therefore the rate, varies: some states have a separate sound and communications classification distinct from electrician. Coverage and classification are set by state law and sometimes by local ordinance, so confirm with the agency's counsel or labor compliance office before the solicitation goes out.

Is software configuration or remote implementation work subject to prevailing wage?

Work performed at the vendor's own offices, such as configuration, data migration, interface development, and training, is normally outside public works rules because it is not on-site labor that alters public property. The distinction turns on where the labor happens and what it does. A project that mixes remote services with field installation should price the on-site labor separately so the covered portion is visible.

What happens if we discover after award that prevailing wage applies?

The vendor priced the work without the higher labor rates, so correcting it usually means a change order, and the agency has to add wage determinations, certified payroll, and possibly bonding after the fact. Back wages may be owed for work already performed, and penalties can apply depending on the state. This is why the coverage determination belongs before the solicitation is released rather than after award.

Does buying through a cooperative or statewide contract avoid prevailing wage requirements?

No. The purchasing route determines how the agency selects a vendor; it does not change whether the work being performed is public works under state law. If a task order includes covered field installation, the wage, payroll, and apprenticeship obligations still apply, and the agency should attach the applicable wage determination to the order.

Do prevailing wage rules apply to on-site maintenance under a managed service agreement?

In several states, maintenance of public property is included in the definition of public works, so recurring on-site repair can be covered even when no new construction is happening. Other states limit coverage to construction and alteration. Because this varies, check the state's definition of maintenance and confirm with counsel before treating a multi-year service agreement as exempt.