On federal construction work above a low dollar threshold, the solicitation carries a wage determination: a schedule of minimum hourly rates and fringe amounts by labor classification for that county and that type of construction. It arrives as one attachment among thirty, and it is usually filed with the other attachments.
It is not really an attachment. It is a price list you are contractually bound to pay, published by someone else, and it will not match the labor rates in your estimating system unless you make it match.
The determination is locked to a date
The rates that apply are the ones incorporated at a specific point in the procurement, not whatever is current when you eventually do the work. Modifications published close to bid opening may or may not take effect depending on how much time remains, and revisions issued after the cutoff generally do not reach a contract already awarded.
The practical consequence is that you cannot price from "the current determination for this county." You price from the determination in the solicitation, at the modification level the solicitation names, and you re-check it when an amendment lands — because amendments update wage determinations quietly and often.
Classifications are not job titles
The classification governs the rate, and what decides the classification is the work actually performed, not what the position is called on your payroll.
A worker who spends the day operating equipment is paid at the operator classification for those hours regardless of internal title, and a worker who moves between classifications during a day is paid at each applicable rate for the hours worked in it. Estimating labor as a blended crew rate is fine for your own planning and useless as a compliance position; the payroll has to survive being read line by line.
Fringe is cash unless you can show otherwise
Each classification carries a fringe benefit amount alongside the base rate. That amount has to be delivered — either as bona fide benefits or paid out in cash — and the burden of demonstrating that a plan qualifies sits with the contractor.
This is where estimates quietly go wrong. A firm with a real benefits package assumes the fringe column is already covered by what it spends, then discovers that only part of that spend counts, and the remainder has to be paid as wages. On a labor-heavy scope the difference is not a rounding error.
The missing classification is priced blind
Sometimes the work requires a classification the determination does not list. The mechanism for that is a conformance request, where the contracting officer forwards a proposed classification and rate to the Department of Labor for approval.
Note when this happens: after award. You bid the job, you win the job, and then the rate for that scope is set by a process you do not control. Any scope that depends on an unlisted classification is scope you have priced without knowing its labor cost, and the honest response is to identify it during the estimate rather than discover it during execution.
Certified payroll is a recurring cost, not a form
Weekly certified payroll submissions are a standing obligation for the life of the job, covering your own workforce and flowing down to every subcontractor on site.
That is administrative labor with a real hourly cost, repeated every week, plus the effort of chasing subcontractors who treat it as optional. It belongs in general conditions as a line with a number, and it usually is not there — which is one reason firms new to federal work find their overhead recovery thinner than the estimate promised.
Why it lands in the estimate late
The wage determination is not hidden. It is attached, named, and often summarized in the instructions to bidders. It still gets to the estimator last, for a structural reason: estimating starts from the drawings, and the drawings say nothing about labor rates.
So the takeoff is built with the firm's own historical crew costs — which are accurate, hard-won, and drawn from private or state work where the determination did not apply. The rates are then correct in every sense except the one that governs this contract, and the gap only becomes visible when someone deliberately compares two documents that nothing in the workflow brings together.
That is the kind of requirement Offra is built to surface: pulled out of the attachment it was buried in, tied back to the page it came from, and put in front of the estimator while the number is still changeable.
