Do You Have to Pay Prevailing Wage on Warranty Work? (w/Examples) + FAQs

Yes, in most cases. If your original contract fell under prevailing wage law, warranty and punch-list repairs under that same contract are almost always covered too, even with no separate pay item. That includes the federal Davis-Bacon rules, which reach construction contracts over $2,000, and most state public-works laws.

This trips up payroll teams because warranty callbacks often land months after the crew was paid. Many default to a standard hourly rate instead of pulling the original rate sheet. General contractors, subs, and the public agency that awarded the job all share risk of a back-pay claim if the old rate is not reapplied. The rule applies the same on a $4,000 home-repair job and a multimillion-dollar highway job, because the trigger is the original contract, not the size of the fix.

This article covers federal rules and general guidance as of July 2026. Wage rules change and vary by state, so check current figures and your state's rules before you act. It covers the federal baseline plus a few sample states, not all fifty.

What Counts as "Warranty Work" Under Prevailing Wage Law

Warranty work is any repair or punch-list task a crew does after the job is done. It usually fixes a defect or meets a promise in the contract. Public agencies often build a one- or two-year warranty term right into the job contract.

That term requires the same crew to return and fix certain defects at no extra charge. Because the warranty duty is part of the original deal, most agencies treat the fix as part of the same job, not a new one. That one fact is why prevailing wage can still apply, even with no new invoice for the labor.

The label used does not change the outcome: calling a fix a "warranty callback," a "punch-list item," or a "service call" does not exempt it. What counts is whether the duty traces back to the original, covered contract. Agencies check what the contract papers require, not what the crew wrote on the ticket. A flaw the crew must fix, even years later, still ties back to that first job.

Two things mark true warranty work apart from a plain repair call. First, the duty must start in the original contract. The agency did not pay for a brand-new bid to get the fix done.

Second, the crew must do build-type tasks, like framing, roofing, paving, or wiring. Plain upkeep, like a filter swap or a breaker reset, is not the same. Upkeep under its own service deal, with its own scope and price, is usually a different class and sits outside prevailing wage.

This split shows up most on roads and public buildings. Warranty terms there often run 12 to 24 months and cover roof leaks, cracked pavement, or a bad HVAC unit. A school board that asks a crew back in month fourteen to fix a leaking roof is using the same clause that ran the first roofing job.

The fix did not need a new bid or a new contract number. That single fact is what keeps the old pay rate in force. Smart crews keep the old rate sheet on file for the whole warranty term, not only while the job runs.

The Federal Rule: Davis-Bacon and 23 USC 113

The federal baseline rests on two rules. The Davis-Bacon and Related Acts (DBRA) set prevailing wages on most federally funded work. 23 USC 113 is the specific law for Federal-aid highway jobs. Both share the same core logic, though the highway rule spells out the warranty case in more depth.

The Federal Highway Administration has posted direct guidance on this point. Under that guidance, warranty or repair work the first contract requires is covered by prevailing wage. This holds even with no separate pay item for it. It also holds even if the fix comes years after the crew left.

FHWA's guidance adds a plain time test. If a worker spends more than 20 percent of a work week on warranty tasks at the old job site, that worker is covered for all hours worked there that week, not only the warranty hours. A crew member who spends one full day out of five caulking a bridge deck crosses that line.

That worker must get the original rate for the whole week. Fall below 20 percent, and only the strict warranty hours need the covered rate under this test. Many agencies still pay the full week at the covered rate to dodge a dispute.

This stance is not new. The Department of Labor's Wage and Hour Division took it up in a 1973 opinion letter. It found that Davis-Bacon rules applied to warranty work on prefab housing.

The reasoning: the work took place at the first job site and was more than a minor task. That view has held for five decades and still guides how agencies read warranty claims today. The rate that applies is the original contract's rate, not a new one set for the warranty term, even if area rates have since shifted.

One more federal wrinkle matters for federal service work. The Service Contract Act (SCA) covers upkeep and service deals. In most cases it uses its own pay rates, apart from the Davis-Bacon build rates. A janitorial deal or an HVAC upkeep deal usually falls under SCA.

A structural fix tied to a build warranty falls under DBRA instead. Mixing up the two is a common and costly slip. The wrong pay chart can shortchange or drastically overpay the crew against what the law asks.

Does Your State Differ?

Most states run their own public-works rules. They stack a state wage law on top of the federal floor. The state rule usually kicks in whenever state or local funds, not federal funds, pay for the job.

California's Department of Industrial Relations requires prevailing wages on any public job over $1,000, per its own FAQ. It also allows narrower exemptions for smaller repair, alteration, or upkeep jobs when the agency runs an approved compliance program. Check DIR's current page for the exact cutoff amounts, since California has shifted these figures over time.

Washington runs a similar statewide system through its Department of Labor and Industries. It covers public jobs and asks crews to file intents and payroll reports for the whole job, including warranty terms tied to the first scope. Nevada has gone further and issued its own advisory opinion on warranty and punch-list work, which shows how often this question comes up in the field.

The real gap between states rarely shows up in whether warranty work is covered. It shows up in how strict the paperwork is, how low the dollar floor sits, and how the state defines the job site for the 20-percent test. A state with a $1,000 floor pulls in far more small punch-list jobs than a state that skips small repairs entirely. Two crews doing nearly the same warranty fix can land on opposite sides of the line, purely because of the state they work in.

Never assume your state copies the federal rule. Some states stretch prevailing wage to warranty work on private jobs that got a public subsidy or tax break. The federal Davis-Bacon rule does not touch those deals at all.

Other states skip small upkeep-style fixes that the federal 20-percent test would still catch. Pull your own state labor office's wage guidance before you set a warranty crew's pay rate. If your job touches more than one funding source, treat the strictest rule as the floor, not a guess.

Which Situation Applies to You?

The right answer rests on three things. Who pays for the job, what kind of contract sets the warranty duty, and how much time your crew spends on-site doing the fix. Match your case to one of the four cases below before you set a pay rate for warranty work.

You're a Contractor on a Federal-Aid Highway Project

If your first contract used federal highway funds, 23 USC 113 and the FHWA guidance above apply directly. Any warranty work the contract requires carries the old pay rate. The 20-percent weekly time test decides whether the whole week, or only the warranty hours, need the covered rate. Keep the old payroll records and rate sheet on file for the full warranty term, which often runs one to two years past job's end.

If a sub does the fix instead of your own crew, the same rate still travels with the work, because the duty ties to the contract, not to whose payroll runs it. Log the visit date, the hours worked, and the exact flaw fixed. That log is what protects you if the agency or DOL checks the warranty term.

You're a Subcontractor on a State or Local Public Works Project

When the job runs on state or local funds, look up your own state's public-works wage law. Do not assume it copies the federal rule. Check the dollar floor that triggers coverage, since it can sit as low as $1,000 in a state like California. Also check whether your state has its own guidance on warranty work, as Nevada has.

As the sub doing the fix, you are usually the one who owes the correct pay rate and must file any required payroll report. The general contractor holds the prime warranty duty to the owner, but you carry the pay-rate duty. Get the old rate sheet from the general contractor in writing before you send a crew, rather than trust memory or an old rate card.

You Do Only Private Commercial or Residential Work

If the first job had no public funds, neither Davis-Bacon nor most state wage laws apply to the warranty work. Both rules turn on public money, not on the mere fact of a warranty clause. A private homeowner's roof-warranty callback is paid at whatever rate the crew's normal payroll sets. That pay still falls under plain wage law, like the Fair Labor Standards Act.

The one case worth a check is a job that got a public subsidy or tax break. Some states stretch prevailing wage to those mixed deals, even though the building itself is privately owned. When in doubt on a subsidized job, ask the awarding agency point-blank whether prevailing wage covers the whole scope, warranty term included.

You're the Public Agency Awarding the Contract

As the agency, you carry the risk if your contract wording is vague on warranty pay. A crew that underpays a warranty visit can create back-pay risk that lands back on the job and stalls close-out. Write the warranty clause so it says plainly that the old rate sheet still applies for the full warranty term.

Ask the crew to file a payroll report for any warranty visit, in the same form it used on the first job. Build a short checklist into your closeout steps, so warranty visits do not slip through once your project lead moves to the next job. Name the specific rate sheet in the clause itself, so a future auditor never has to hunt for which rate applied. A contract that stays silent on this point invites exactly the dispute this article covers.

Worked Example: Calculating Prevailing Wage Pay for a Warranty Callback

Here is a full walkthrough with real numbers. A crew finished a $2.4 million public school job. The first contract set a rate of $38.50 an hour for a carpenter, fringe benefits included.

Fourteen months after the job's end, the school reports a leaking window seal. The first contract's one-year warranty clause requires the crew to fix it at no charge. The crew sends one carpenter for one eight-hour day to reseal three windows.

First, check the trigger. The fix falls under the first contract's warranty clause, so the old $38.50 rate applies to the visit. It is not the carpenter's current market rate, and not a new rate set later. Second, run the 20-percent weekly test.

The carpenter worked one eight-hour day out of a 40-hour week, exactly 20 percent. Under a strict read, only that one day needs the covered rate, not the whole week. Third, do the math: eight hours times $38.50 equals $308 owed for the day. The crew must log this in the same payroll form used on the first job.

Now weigh that against a longer visit. Say the same carpenter spends three full days that week on the warranty list instead of one. Three days is 24 of 40 hours, or 60 percent of the week, well past the 20-percent line.

The whole 40-hour week must then be paid at the $38.50 covered rate, for $1,540 that week. Weigh that against the $924 the crew would owe for only the 24 warranty hours at the covered rate, plus 16 hours at a lower rate. The gap between those two sums, about $616 in this case, is the exact kind of shortfall that turns into a Department of Labor back-pay claim.

The lesson in the math is plain. Track hours by task, not only by day, since the 20-percent line decides whether one day or the whole week gets the covered rate. A payroll system that dumps warranty hours into a plain repair code cannot answer that question. It needs a stamp tied to the first contract number, or no one can answer it when an auditor asks for records a year and a half later.

Lessons From the Field

Maria Tracks Hours by Contract Number, Not by Job Site

Maria runs payroll for a mid-size highway crew. She learned this lesson after an audit flagged three warranty visits paid at a flat repair rate instead of the old rate. She now tags every warranty hour to the first contract number in her time system.

That system then pulls the correct old rate on its own, instead of the current one. The single fix caught two more wrong visits the next year, worth $2,900 in back pay the firm paid on its own before DOL asked. Her lesson: what protects a crew is not memory, it is a time code tied to the contract, since rates shift every year and memory does not.

David Underestimates the 20-Percent Threshold

David runs wiring work on state public-building jobs. He assumed a quick two-hour warranty visit never triggered prevailing wage, since the sum felt small. He was right about that one visit but wrong about the test.

Two hours is only 5 percent of a 40-hour week, well under the 20-percent line, yet he had never run the math to know why. His next warranty visit ran a full two days, 40 percent of the week. He paid the plain rate out of habit instead of checking the line again.

That drew a labor-board complaint from the electrician who spotted the pay stub. David's lesson: a rule of thumb that works once is not the same as knowing the test. His fix was a two-minute checklist his crews now run before every warranty job.

The Owens County School District Rewrites Its Warranty Clause

Owens County's facilities lead took over a contract form that never named wages for the warranty term. It left every crew to guess. One crew underpaid a warranty visit, and the district got drawn into the DOL check that followed as the funding agency. The district rewrote its standard clause to say plainly that the old rate still applies for the full warranty term.

It now also asks for a payroll report on every warranty visit. The next three visits under the new form came back clean, with zero disputes, since the crew no longer had to guess what the district expected. This lesson sits on the agency side: a clause silent on pay pushes the risk downstream, and it pulls the agency back in anyway.

Trade-offs and Hidden Costs of Skipping Prevailing Wage on Warranty Work

Underpaying warranty work looks like a quick win, since the crew's hourly cost drops right away. But the risk stacks over the whole warranty term, not only one visit. A back-pay claim usually covers every underpaid warranty hour across the full term, which can run one to two years. A $600 gap on one visit, times a five-person crew, can push the full back-pay bill past the cost of doing the paperwork right from day one.

Extra penalties and a ban from future work sit on top of the back-pay risk. A crew found to have knowingly underpaid Davis-Bacon wages can face a ban from future federal jobs. That penalty often costs far more than the wages, for a firm that leans on public work. Even an honest slip still means paying back wages plus interest, and it draws closer checks on the crew's next bid.

There is a smaller, easy-to-miss cost on the flip side too: paying the covered rate when it is not owed at all. A private crew that assumes every warranty visit needs prevailing wage, even on jobs with no public funds, pays a needless higher labor cost. That slip can also mix up the job's pay setup for tax or insurance purposes down the line. Getting the coverage call right in both directions, not only against underpay, guards the margin on jobs that were never covered to begin with.

The stacking risk is worst for crews juggling several public jobs at once. One payroll-code slip often repeats across every warranty visit that uses the same plain repair code. Fixing the root cause, a contract-tied time code, costs almost nothing to set up and stops the repeat slip instead of catching it one audit at a time. Crews that fix the code once often say the change pays for itself within the first audit round, by dodging a repeat citation.

Mistakes to Avoid

• Assuming no pay item means no coverage. Crews often read a missing warranty line item as proof the work is not covered, but FHWA guidance says the pay item does not matter. Skipping this check leads to underpaying the crew and owing back wages once caught.
• Using this year's rate instead of the old one. Rates shift every year, and using this year's rate on a two-year-old contract makes a payroll record that fails the audit test and can draw a compliance finding.
• Ignoring the 20-percent time test. Paying only for the raw warranty hours, when a worker crossed the 20-percent line for the week, shorts every other hour that worker logged on-site, a plain back-pay claim in the making.
• Mixing up SCA upkeep deals with DBRA build work. Using a service-deal pay chart on build-type warranty work, or the flip, sets the wrong rate entirely. The slip is not clear until an auditor pulls the record.
• Letting warranty visits skip payroll reports. Treating a small warranty callback as off-book labor drops the paper trail that proves you followed the rule, leaving no defense if the agency asks for records later.
• Assuming your state copies the federal rule. Some states set a lower dollar floor, a stricter site rule, or extra warranty guidance. Assuming the federal answer carries over unchanged can mean missing a state-only filing step.
• Leaving the warranty clause silent on pay. Agencies that skip pay terms for the warranty period push the guesswork onto the crew. The mixed practices that follow spark disputes that stall closeout and final pay.
• Failing to keep records for the full warranty term. Tossing payroll and time records once the build ends leaves nothing to show an auditor if a warranty-pay question comes up a year or two later.

Do's and Don'ts

Do

• Do pull the old rate sheet before you send a warranty crew, so the rate you pay matches what the contract asks instead of a guess.
• Do tag warranty hours to the first contract number in your time system, since that is what lets you rebuild the correct rate months or years later.
• Do run the 20-percent weekly test every time, since a worker's total hours for the week, not only the warranty hours, set which rate applies.
• Do keep payroll records for the full warranty term, not only while the job runs, since that is the span an auditor will check.
• Do put the pay duty in writing in the warranty clause itself, whether you are the agency writing the contract or the crew signing it, so neither side guesses later.
• Do split DBRA build work from SCA upkeep work before you set a pay chart, since the two rules use different rate sheets entirely.

Don't

• Don't assume a missing pay item means the work is not covered. FHWA guidance rejects that shortcut flat out.
• Don't use this year's rate on a warranty visit tied to an older contract. The old rate sheet rules, not the current one.
• Don't treat a two-hour warranty visit as exempt by default. Check the real weekly hours before you assume you sit under the 20-percent line.
• Don't skip a payroll report on a warranty callback because the job feels small. The paperwork rule does not shrink with the size of the fix.
• Don't assume every state wage law reads exactly like the federal one. Floors, exemptions, and site rules vary by state.
• Don't let a sub set the warranty pay rate without a check with the general contractor first. The prime holds the old rate sheet and the full compliance risk.

Pros and Cons of Building a Dedicated Warranty-Wage Compliance Process

Pros

• Fewer back-pay surprises. A set process catches the 20-percent line and the old-rate rule before payroll runs, instead of after an audit finds the gap.
• Cleaner audits. Payroll tied to a contract-specific code gives an auditor a record to check in minutes, not a manual rebuild months later.
• Stronger bids on future public work. A clean record, free of bans or repeat findings, keeps a crew eligible for the next round of public work.
• Faster job closeout. Agencies close out warranty terms faster when the crew's records already fit the required form, instead of chasing missing files.
• Fewer disputes with crews. Workers who see steady, correctly coded pay for warranty visits file fewer pay complaints than crews paid at random from job to job.

Cons

• Setup time upfront. Building a contract-tied time code, and training payroll staff to use it, takes real hours before the process pays off.
• Ongoing paperwork load. Someone has to pull and file the old rate sheet for every warranty term still open, adding a task to job closeout.
• Coordination across subs. A general contractor has to hand off the old rate to every sub doing warranty work, which does not happen on its own without a set process.
• Software or template costs. Small crews may need to buy or build a time template that fits contract-specific codes, a real cost for a one- or two-person back office.
• Risk of over-applying the rule. A process built with no clear coverage test can flag private, uncovered warranty work as covered by mistake, raising labor cost on jobs where the rule never applied.

What to Do Next

Getting this right is mostly a records habit, not a legal riddle, once you know which files to keep and which line to check. The eight steps below cover the order most crews and agencies follow in practice, from checking the old rate through calling in outside help.

1. Pull the first contract file and check the rate sheet and contract number tied to the job.
2. Check the funding source, federal, state, local, or purely private, since that sets which wage law, if any, applies.
3. Check your state's own public-works law and dollar floor, rather than assume it matches the federal rule.
4. Log the planned warranty visit's expected hours and run the 20-percent weekly test before you send the crew.
5. Tag the time entry to the first contract number so payroll pulls the correct old rate on its own.
6. File a payroll report for the visit using the same form required on the first job.
7. Keep all warranty-term records for at least the length of the warranty term, plus your state's own record rules.
8. Bring in an employment lawyer or a compliance advisor if the job spans several funding sources or states, since that is where the coverage call gets genuinely tricky.

None of these steps needs special software. A shared sheet that tracks the contract number, the old pay rate, and the warranty end date covers most small and mid-size crews. Larger firms often fold this into their existing payroll system instead. Whichever tool you use, the goal stays the same: keep the old rate and the warranty deadline in view for whoever books the crew, so no one has to recall it a year and a half later.

This article covers how prevailing wage usually applies to warranty work, but it is not a stand-in for advice from a compliance lawyer or your state labor office on your own contract. Bring in that kind of review when a job spans several funding sources, several states, or a warranty spat that is already heating up. An hour of legal or compliance advice almost always costs less than an unresolved back-pay claim found months later.

Frequently Asked Questions

Does the warranty term need to be written into the first contract for the rule to apply?

Yes. The duty has to trace back to the first contract's warranty clause. A brand-new repair deal, set up on its own with its own scope and price, counts as a new job with its own pay rules, not a stretch of the old one.

What happens if the old rate sheet has expired by the time the warranty work happens?

The old rate sheet still usually rules. Federal guidance ties warranty pay to the rate that applied when the contract was set, not to whatever rate is current when the fix happens, so keep the old sheet on file for the full warranty term.

Does prevailing wage apply to warranty work on a privately funded commercial building?

No, usually not. Both the federal Davis-Bacon rule and most state laws turn on public funds, so a purely private job's warranty fixes get paid under plain wage law, unless the job got a public subsidy or tax break.

Who owes the correct warranty wage rate, the general contractor or the subcontractor?

The firm that employs the worker doing the fix. That is usually the sub sending the crew, but the general contractor still holds the prime warranty duty to the owner and often stays on the hook for checking the correct rate was used.

Does a two-hour warranty visit ever need a payroll report?

Yes, if the job is otherwise covered. Payroll-report rules carry no minimum-hours pass, so a short visit on a covered job still needs the same paper trail as a full-day warranty callback.

How long does a crew need to keep warranty-term wage records?

Usually for the length of the warranty term plus your state's own record-keeping window, which varies by state and by funding source, so check your own state and contract rules before you toss files.

Does the 20-percent time test reset every week, or does it track the whole warranty term?

It resets weekly. Federal guidance checks the 20-percent line against each single work week, so a worker could cross it one week and sit under it the next, based on how many warranty hours they log that week.

Can a crew agree to a lower rate for warranty work than the first contract set?

No, not on a covered job. The whole point of tying warranty pay to the old rate sheet is to block that kind of side deal, and doing it anyway still creates back-pay risk no matter what both sides agreed to on the side.

Does Davis-Bacon cover warranty work on gear set up during the build, like HVAC units?

Mostly yes, if fixing the gear counts as build-type labor. Swapping or fixing a broken HVAC unit set up under the first contract usually counts as covered build work, while plain filter swaps under a separate service deal usually do not.

What should a small crew do if unsure whether a specific warranty job is covered?

Call the awarding agency or your state labor office directly before you send the crew. A quick coverage check costs nothing and beats finding out during a back-pay audit months after the work is done.

Does the prevailing wage duty travel with a sub that did not exist when the first contract was signed?

Yes, usually. If a sub takes over warranty duties from the first crew, whether through a buyout or a new subcontract, the pay duty still ties to the work itself, not to which firm happens to be doing it.