Get the price too high, and you lose the bid to a competitor who read the wage determination correctly. Get it too low, and you're looking at back-wage liability, compliance penalties, or a failed audit months after award. Neither outcome is acceptable, and both happen more often than contracting teams would like to admit.
This article breaks down what makes SCA and Davis-Bacon pricing genuinely hard, where manual processes fail, and how purpose-built pricing software closes the gap.
Key Takeaways
- SCA and Davis-Bacon pricing depends on wage determinations that vary by location, craft, and contract type
- Spreadsheet-based pricing raises audit risk and slows bid turnaround
- Purpose-built software can cut time-to-final-pricing by up to 90% while preserving a full audit trail
- Choose tools with wage data integration, automated conformance flagging, and defensible documentation
Understanding SCA and Davis-Bacon Pricing Requirements
These two federal statutes cover different types of labor, and pricing teams need to know which one applies before they touch a spreadsheet.
- The Service Contract Act (SCA) governs service labor on federal prime contracts exceeding $2,500. Covered employees must receive prevailing local wages or predecessor collective bargaining agreement (CBA) rates, plus fringe benefits.
- Davis-Bacon and Related Acts govern construction, alteration, and repair work on federally funded projects exceeding $2,000. Laborers and mechanics must receive the locally prevailing wage and fringe benefits for similar work in the area.
Both systems require two numbers, not one: a base hourly rate and a fringe benefit rate. A compliant price proposal has to reflect both explicitly, by classification. Skip the fringe calculation, and your price proposal is incomplete even if the base rate is correct.
Rates Are Locked, But Not Forever
Wage determinations attach at the point of contract award or bid, but that's not the end of the tracking obligation.
- Annual appropriations: On multi-year SCA contracts, agencies must obtain a new wage determination at each contract anniversary
- Non-annual contracts: Contracts not subject to annual appropriations need a refreshed determination at least every two years
- Option exercise: Before exercising any SCA option, the agency must pull a current wage determination
- Successor CBAs: Successor contractors inheriting a predecessor's CBA must honor those rates, including scheduled increases
Pricing under SCA and Davis-Bacon is a multi-year tracking obligation, not a one-time bid task. Spreadsheets rarely keep base rates, fringes, and determination dates aligned across anniversaries, options, and successor CBAs.
Getting the Right Determination Into Your Cost Build-Up
Both determination types now live in the same place, which simplifies retrieval but doesn't eliminate the risk of pricing against the wrong one.
SCA and Davis-Bacon general wage determinations are both on SAM.gov's wage determinations database, the official Davis-Bacon site since June 14, 2019. Match all three filters before rates enter the cost model; a miss on any one prices the bid against the wrong rate:
- Location (work-site county and state)
- Contract or construction type
- Labor classification
When a Classification Is Missing
Not every job title in your scope will appear on the applicable wage determination. When that happens, you initiate a conformance action:
- Compare your anticipated labor classifications against the determination's listed classes
- Complete an SF-1444 conformance request identifying the missing classification
- Submit supporting materials through the contracting officer (Davis-Bacon packages go to DOL at DBAConformance@dol.gov)
- Wait for Department of Labor review — the Branch of Construction Wage Determinations typically responds within 30 days
That 30-day window is exactly the kind of delay that catches contractors off guard on a tight bid timeline. If you discover a missing classification the week before submission, you're already behind.
Why Manual Prevailing Wage Pricing Breaks Down
Spreadsheets weren't designed for this. Pricing analysts end up manually cross-referencing wage determinations, fringe benefit schedules, and CBA terms across multiple tabs, hoping nothing falls through the cracks.
A GAO review of federal SCA compliance examined 1,125 procurement contracts and purchase orders worth $90.6 million. At 20 of 22 federal installations reviewed, officials failed to request required determinations or include current ones, affecting 381 contracts and purchase orders worth about $13.1 million.
That failure rate should worry anyone still pricing off a spreadsheet without a systematic check.
Manual pricing also creates two downstream problems:
- No defensible audit trail. Bid protests and post-award audits require proof of each line’s wage determination, fringe schedule, and classification match—spreadsheets rarely store that history in a form auditors can verify quickly.
- Slower turnaround. Hours spent cross-checking rate tables are hours not spent on the technical proposal, and on tight bid deadlines that delay can mean missing the window entirely.
How Prevailing Wage Pricing Software Solves These Problems
Purpose-built pricing software attacks the same three problems from a different angle: it connects wage data directly to cost build-ups instead of relying on someone to look it up and re-type it correctly. What this looks like in practice:
- Base rates and fringe benefits get applied automatically by classification and location, pulled into the cost model rather than manually transcribed
- Missing classifications get flagged during the build phase, so conformance requests go out before submission instead of after a protest
- Every pricing decision (assumption, rate, override) gets logged in a versioned record that holds up under compliance review This is the gap Intellectible's Pricing Engine is built to close. Pricing and proposal teams connect wage determination data, automate cost calculations, and generate compliant outputs—without standing up custom infrastructure for every new contract type.
The Workflow, Start to Finish
The engine follows five stages:
- Intake — bring in the RFP, scope, and related files
- Extract — pull labor and cost details with source evidence and confidence signals
- Review Assumptions — confirm wage rates and pricing factors before lock-in
- Build Cost Model — apply classifications, fringes, and overhead
- Publish Pricing — issue a versioned, review-ready price package AI extraction pulls labor and cost details from RFPs, scope documents, surveys, and CRM notes. Analysts review assumptions (including wage rates and pricing factors) before the cost model locks in. The audit trail captures the full picture:
- Prepared-by, version history, effective date, and approval status
- Labor, overhead, margin, wages, and benefits detail
- Risk flags plus a change log of who modified what and when That is the documentation you want on hand if a contracting officer or auditor asks how a price was built. Intellectible's Pricing Engine reports a 90% reduction in time to final pricing with full audit trail control. That cuts the SCA/Davis-Bacon drag of slow, error-prone manual lookup so pricing and proposal teams can pursue more opportunities without adding headcount.
How State Systems Change the Number You Bid
Federal Davis-Bacon and SCA rules aren't the whole story. Depending on where the work happens, a separate state system may apply on top of, or instead of, federal requirements — and that changes the rate you must price to.
Three patterns drive most pricing decisions:
- No state system: Only the federal determination governs, so the Davis-Bacon or SCA rate is the number you price to.
- State system that exceeds federal: Where a state runs its own schedule through its labor department, rates can sit above Davis-Bacon. Price to the higher of the two, and record which one governed each line.
- State system running on its own cycle: Confirm the live state schedule before pricing locks. Assuming the federal determination covers the full obligation understates the labor line.
State systems change on their own timeline, separate from federal updates. A rate that looked current last quarter may already be stale by bid day. Pull the live schedule for each work site instead of carrying cached numbers forward from a prior pursuit.
What to Look for When Choosing Pricing Software
Not every quoting tool is built for prevailing wage work. Before you commit, check for these three things:
- Direct wage data integration. Does the platform pull from SAM.gov and DOL wage determination sources, or does someone still have to manually enter rates? Manual entry reintroduces the exact risk you're trying to eliminate.
- Conformance workflow support. Can the software flag a missing classification during the build phase and route a conformance request, or does that discovery happen only after submission?
- Cross-contract-type scalability. Can one platform handle SCA, Davis-Bacon, and state-level pricing, or will you need separate tools stitched together for each contract type? Fragmented tooling usually means fragmented audit trails.
A platform that meets these criteria saves time and cuts the number of places a compliance gap can hide.
Frequently Asked Questions
Which wage determination applies to the bid I'm pricing?
Match the solicitation's work-site county, contract type, and labor classifications against the determination on SAM.gov. A miss on any one of those three filters puts the wrong rate into your cost model, so confirm all three before the build phase.
What has to appear in a compliant price proposal?
Two numbers per classification, not one: the base hourly rate and the fringe benefit rate, both traceable to the applicable determination. A proposal that carries the base rate but omits fringe is incomplete even when the base figure is correct.
How do wage rates flow into a bid price?
Each classification's base rate and fringe are applied against estimated hours, then carried through overhead and margin into the cost build-up. Pricing software applies those rates by classification and location automatically, so the figures in the cost model tie back to the determination rather than to a re-typed spreadsheet cell.
How do state prevailing wage laws change the price?
Where a state runs its own system, its rates can exceed the federal determination, and the higher of the two governs what you must price to. Where no state law exists, only the federal determination applies. Both cases have to be resolved before pricing locks, not after.
How should pricing teams handle multi-state work?
Price each work site against its own governing rate rather than applying one blended figure across the contract. States with their own systems update on timelines separate from federal releases, so pull live schedules per site at bid time instead of reusing cached numbers from a prior pursuit.
What happens if a labor classification is missing at bid time?
You file a conformance request, and Department of Labor review typically runs about 30 days. Discovering the gap the week before submission puts the schedule at risk, which is why classification coverage should be checked during the build phase rather than at review.
