Prevailing Wage Determination

Definition — what it is

A prevailing wage determination is an official schedule, issued by a government labor authority, that sets the minimum hourly wage and fringe benefit rate that must be paid to each labor classification working on a covered public construction project in a specific geographic area. On federal and federally assisted work it is issued by the U.S. Department of Labor under the Davis-Bacon and Related Acts; state and local prevailing-wage laws issue their own determinations for state and municipal projects. The determination is incorporated into the contract and becomes the binding floor for wages and fringes, classification by classification. A prevailing wage determination is not the same as minimum wage and it is not a suggested rate — it is a contractual and statutory obligation, and paying below the determined rate for a classification is a violation that triggers back wages and penalties, which is why identifying and applying the correct, current determination is the foundation of prevailing-wage compliance.

Also known as: Wage Determination, WD, Davis-Bacon Wage Determination, Prevailing Rate Schedule

Why it matters — what it protects

The determination is the yardstick every certified payroll is measured against, so getting it right is upstream of all downstream compliance. If the wrong determination, the wrong locality, or a superseded version is applied, every weekly report is built on the wrong rates, and the error compounds across the entire project. Compliance begins not with payroll but with correctly identifying and locking the determination that governs the contract.

It directly drives labor cost and therefore the bid. Prevailing rates are frequently well above open-market rates, and fringe obligations add materially on top, so mis-estimating the applicable determination during bidding can turn a profitable job into a losing one. Contractors must price to the correct classifications and rates for the project's locality, including any anticipated rate escalation, before they commit to a number.

Classification is where the determination becomes contentious, because the schedule only helps if work is mapped to the right classification. A determination lists rates for specific classifications — laborer, operator, various trades and their subcategories — and the money owed depends entirely on which classification a given hour of work falls under. Disputes over whether a task is, say, laborer or operator work, or which subcategory applies, are common and consequential.

It carries legal weight equal to the contract itself and is enforced accordingly. Because the determination is incorporated into the contract, paying below it breaches both the contract and the governing statute, exposing the contractor to withheld payments, restitution, penalties, and debarment. When a determination lacks a classification for work being performed, the correct path is a formal conformance request to the labor authority, not an informal guess — improvising a rate is itself a compliance failure.

Lifecycle — how it moves

1. Determination identification

   Before bidding, the contractor identifies the correct determination for the project's type (building, heavy, highway, residential) and locality. The schedule type and county are the two inputs that most often get chosen wrong.

2. Incorporation into the contract

   The applicable determination, as of the required lock date (often bid opening or award), is incorporated into the contract. Which version applies and when it locks is set by the governing rules and must be confirmed, not assumed.

3. Bid pricing to the determination

   Labor is estimated using the determined rates and fringes by classification, including anticipated crew mix. Underpricing because the wrong classifications or a stale determination were used bakes a loss into the bid.

4. Classification mapping

   The project's scope of work is mapped to the determination's classifications so every task has a governing rate. Gaps — work with no listed classification — must be identified here, not discovered at payroll.

5. Conformance request (if needed)

   Where the determination lacks a classification for work being performed, the contractor submits a conformance request to the labor authority to establish an additional classification and rate. This is a formal process that takes time and must be initiated early.

6. Application during performance

   Workers are paid at the determined rates and fringes for the classifications of work they actually perform, feeding certified payroll. Rate updates or modifications during a long project must be tracked for applicability.

7. Monitoring for modifications

   Determinations are periodically modified, and whether a modification applies to an ongoing contract depends on timing rules. Missing a modification that does apply, or wrongly applying one that does not, both create exposure.

8. Audit and enforcement reference

   In any wage investigation or audit, the incorporated determination is the reference against which paid rates are judged. It is retained with the contract records for the statutory period.

Anatomy — the data it carries

Determination number and date

The unique identifier and effective/modification date of the schedule. Pins exactly which version governs and is the first thing an auditor checks.

Locality / county

The geographic area the rates apply to. Rates vary by county, and applying an adjacent county's schedule is a common and costly mistake.

Construction type

Building, heavy, highway, or residential. Each type has its own schedule, and the wrong type produces the wrong rates across the board.

Labor classifications

The specific classifications covered — laborers, operators, and trades with their subcategories. The determination is only as useful as the mapping of work to these.

Base hourly rate by classification

The minimum wage that must be paid for each classification. The binding floor the certified payroll rate is checked against.

Fringe benefit rate by classification

The fringe amount owed per hour, payable in cash or as bona fide benefits. Frequently a large fraction of the total and frequently mishandled.

Zone or area modifiers

Some determinations adjust rates by zone, mileage, or specific area conditions. Missing a zone adjustment underpays workers in that zone.

Apprentice provisions

How registered apprentices are paid relative to the journeyman rate and the allowed ratios. Only registered-program apprentices qualify for reduced rates.

Overtime and shift rules

How overtime and shift differentials interact with the determined rates, including CWHSSA requirements on covered federal work.

Effective and modification dates

When the determination and any modification take effect, which governs whether a change applies to an ongoing contract.

Conformance/additional classifications

Any classifications added via conformance for work not originally listed. Must be approved by the labor authority, not self-assigned.

Failure modes — how it breaks

Wrong locality or construction type

The contractor applies the schedule for the wrong county or the wrong construction type — building rates on a highway job, or an adjacent county's rates. Every classification is then off, and the entire project is priced and paid on the wrong floor.

Stale or superseded determination

An outdated version is used because the current one, or an applicable modification, was never checked. The rates paid fall below the governing determination, and the shortfall becomes back-wage liability across every affected week.

Improvised rate for unlisted work

Work is performed for which the determination has no classification, and the contractor picks a rate informally instead of filing a conformance request. The labor authority later rejects the self-assigned rate, and restitution is owed at the rate it sets.

Classification disputes ignored

Work that arguably belongs to a higher-paid classification is reported at a lower one without resolving the ambiguity. When the correct classification is later determined, the difference is owed as back wages plus penalties.

Fringe obligation underapplied

The fringe rate is treated as optional or is met with credits that do not cover the determined amount. The effective wage falls below the determination even though the base rate alone looks compliant.

Modification applied wrongly

A mid-contract modification is either ignored when it should apply or applied when the timing rules say it should not. Both directions create exposure — one underpays, the other overpays and misprices the job.

Bidding on the wrong rates

The estimate used the wrong or stale determination, so the bid understates labor cost. The job is won at a price that cannot absorb the actual prevailing-wage obligation, and margin is lost the moment work begins.

Metrics — how it is measured

Correct-determination rate

Share of projects applying the right determination for locality, construction type, and lock date. The upstream metric all compliance depends on.

Classification-mapping completeness

Share of project scope mapped to a listed (or conformed) classification before work begins. Gaps here become payroll violations later.

Conformance turnaround

Time from identifying unlisted work to an approved conformed classification and rate. Long turnarounds stall correct payment on that scope.

Rate-currency compliance

Share of active projects verified against the current determination and applicable modifications. Catches stale-rate exposure.

Bid-to-actual wage variance

Difference between estimated prevailing-wage labor cost and actual. Reveals whether the correct determination was used in pricing.

Classification-dispute incidence

Frequency of disputes over which classification governs a task. High incidence signals unclear scope-to-classification mapping.

Fringe-application accuracy

Share of hours where the full determined fringe obligation was met in cash or bona fide benefits. Measures the most-underapplied component.

The AI shift — what actually changes

Conversational

You can ask direct questions of the governing determination: what the base and fringe rate is for a given classification in this county and construction type, whether a task falls under laborer or operator work, whether a modification issued last month applies to this contract, and where the determination lacks a classification for work being performed — with the specific determination version cited.

Generative

Classification mappings and conformance requests are drafted rather than researched from scratch: given the project scope and the governing determination, a model produces a scope-to-classification map with the base and fringe rate for each, flags scope with no listed classification, and drafts the conformance request for the labor authority for a reviewer to file.

Orchestrated

The determination is tied to the work it governs: incorporated into the estimate at the correct locality and construction type, mapped against the crew mix for pricing, linked to certified payroll so reported rates are validated against it, and monitored for modifications whose timing rules determine applicability to the ongoing contract.

Autonomous

The determination-currency and mapping loop runs within guardrails: the correct determination identified and locked at bid, active projects re-checked against current versions and applicable modifications, scope-to-classification gaps flagged, and rate discrepancies against certified payroll surfaced — while a human resolves classification disputes, decides conformance strategy, and approves the rates applied, because a classification call is a legal judgment, not a lookup.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Confirming you are applying the right rates before you start a covered project.

We are starting a covered public building project in this county. Identify the correct prevailing wage determination for the locality, construction type, and lock date, and give me the base hourly rate and fringe rate for each classification our crew will use: laborers, operators, carpenters, electricians, and ironworkers. Confirm whether any modification issued since award applies to our contract under the timing rules, and tell me if there is any scope in our work for which the determination has no listed classification. Cite the determination number and date for everything, and flag any classification where our intended crew assignment is ambiguous enough to invite a dispute.

What good output looks like: A classification-by-classification rate schedule from the correctly identified determination, with modification applicability resolved, unlisted-scope gaps flagged, and ambiguous classifications called out, all cited to the determination version.

Follow-ups:

• For the unlisted work, draft the conformance request to the labor authority.
• Which of our planned classifications carry the largest fringe obligation?
• Does the current version differ from the one we priced our bid on?

Generative — Mapping your scope of work to classifications and handling gaps.

Using the governing wage determination for our project and our scope of work, produce a scope-to-classification map. For each significant work activity, identify the labor classification that governs it and its base and fringe rate, and note where an activity could reasonably fall under more than one classification so we can resolve it deliberately rather than by accident. Identify every activity for which the determination has no listed classification, and for each, draft a conformance request to the labor authority proposing an appropriate additional classification and rate with the supporting rationale. Present the map so our estimators and payroll team can use the same classifications consistently.

What good output looks like: A scope-to-classification map with rates, ambiguous activities flagged for deliberate resolution, and drafted conformance requests for every unlisted activity, usable consistently by estimating and payroll.

Follow-ups:

• Which conformance requests should we file now to avoid delaying payroll?
• Show me the total labor-rate exposure by classification for this scope.
• Where might our classification choices be challenged, and on what basis?

Orchestrated — Keeping the determination, the estimate, and certified payroll aligned across a project.

Reconcile our prevailing-wage application across estimating and payroll for this project. Confirm the determination incorporated into the contract matches the locality, construction type, and lock date, and identify any modification issued since that the timing rules make applicable. Compare the classifications and rates we used in the estimate against the determination to surface any pricing built on wrong rates. Then compare the rates and classifications appearing in our certified payrolls against the same determination and flag any worker paid below the determined base or fringe, and any classification used in payroll that was never mapped or conformed. Return one alignment report tying each discrepancy to the determination, the estimate line, or the payroll record.

What good output looks like: An alignment report tying the incorporated determination to both the estimate and certified payroll, surfacing wrong-rate pricing, below-determination payments, and unmapped classifications, each cited to source.

Follow-ups:

• Quantify the back-wage exposure from the payroll discrepancies.
• Which estimate lines were priced on rates that turned out wrong?
• Does any applicable modification change rates going forward?

Autonomous — Standing policy for keeping determinations current and correctly applied.

Manage prevailing-wage determinations across all covered projects under these rules. At bid, identify and lock the correct determination for the project's locality, construction type, and lock date, and record its number and date. Continuously monitor the labor authority for modifications and, applying the timing rules, flag any modification that affects an active contract; do not change applied rates yourself. Maintain the scope-to-classification map for each project and flag any work performed under a classification that was never mapped or conformed. Validate certified-payroll rates against the governing determination each week and flag any base or fringe shortfall. Never decide a contested classification, never self-assign a rate for unlisted work, never file a conformance request without approval, and never adjust rates applied to workers — route every classification judgment, conformance decision, and rate change to a named human with your analysis.

What good output looks like: A currency-and-mapping monitor with modification and shortfall alerts, where humans make every classification, conformance, and rate decision and the determination version for each project is on the record.

Follow-ups:

• Show me every active project and the determination version it is on.
• Which modifications may apply to ongoing contracts right now?
• List all certified-payroll rate shortfalls flagged this week.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Guessed rates

   Rates are pulled informally, locality and construction type are assumed, and modifications go unchecked, so projects are frequently priced and paid on the wrong floor.

1. Level 1 — Identified

   The correct determination is located and incorporated, but classification mapping and modification monitoring are manual and inconsistent.

2. Level 2 — Linked

   The determination is tied to the estimate and certified payroll, so wrong-rate pricing and below-determination payments become visible and mapping is tracked.

3. Level 3 — Assisted

   Classification maps and conformance requests are drafted, modification applicability is analyzed, and rate discrepancies against payroll are surfaced for review.

4. Level 4 — Operated

   Determination currency, mapping, and payroll-rate validation run unattended within guardrails, while humans decide classifications, conformances, and every rate applied.

Common questions

How is a prevailing wage determination different from minimum wage?

Minimum wage is a single legal floor applying broadly to most work, while a prevailing wage determination is a detailed schedule of much higher minimum rates set specifically for construction classifications in a particular locality and construction type, and it applies only to covered public projects. The determination sets a distinct base rate and fringe obligation for each classification, and those rates are typically well above the general minimum wage. It is a contractual and statutory obligation incorporated into the project's contract, not a general labor-law baseline.

What do we do when the determination has no classification for work we are performing?

You file a conformance request with the labor authority to establish an additional classification and a proposed rate for that work, supported by a rationale, rather than informally assigning a rate yourself. Self-assigning a rate for unlisted work is itself a compliance failure: if the authority later sets a different rate, you owe restitution at that rate, and you may face penalties. Because conformance is a formal process that takes time, unlisted work should be identified during classification mapping at the start of the project and the request initiated early, not discovered at payroll.

Does a wage determination change during a project, and do the changes apply to us?

Determinations are periodically modified, but whether a modification applies to an ongoing contract depends on timing rules tied to when the contract was awarded or the determination locked, so a modification issued after your lock date often does not change your obligations while one issued before might. Applying a modification that does not apply overpays and misprices the job, while missing one that does apply underpays workers and creates back-wage exposure, so both directions carry risk. The safe practice is to lock the governing version at the correct date, then evaluate each subsequent modification against the timing rules rather than assuming it does or does not apply.