The first federal job I ran, I learned the hard way that "substantially complete" means nothing to a Contracting Officer if your paper doesn't back it up. We hit every milestone, the building was beautiful, and we still sat in a conference room for three months arguing over a delay claim because our subs' documentation was a mess. Government work isn't harder to build than private work. It's harder to prove. And the difference between a profitable public job and one that eats your fee usually comes down to how well you manage your subcontractors' paper, payroll, and participation from day one.
If you're moving from private commercial into public projects — a school district bond job, a GSA renovation, a DOT-funded structure, a municipal water plant — here's what actually changes on the ground, and where the right systems save you.
Certified Payroll Will Bury You If You Let It
On Davis-Bacon and prevailing-wage jobs, every sub touching the work owes you a certified payroll (the WH-347 or a state equivalent) for every week they have workers on site, whether they billed you that week or not. That last part trips up more supers than anything else. A framing sub finishes their scope, walks off, and forgets they had one guy back for a punch item — and now you've got a missing week on a payroll that the agency's compliance officer will absolutely catch.
A few hard rules that keep you out of trouble:
- Payrolls follow labor on site, not invoices. If a sub or a lower-tier sub had a worker on the job Tuesday, there's a payroll for that week. Zero-hour weeks after mobilization need a "no work performed" statement, not silence.
- Classifications have to match the wage determination. A worker running conduit is an electrician at the electrician rate — you can't pay him laborer scale because that's what he did last week. Misclassification is the single most common finding, and back-wage restitution comes out of your retention.
- Apprentices need a registered program number. No registration on file, they get journeyman scale. Every time. I've watched a sub eat $40k because they ran "apprentices" who weren't registered anywhere.
- Fringe benefits must be spelled out — paid as cash on the check or into a bona fide plan, and the math has to reconcile.
Chasing these down by email at month-end is a nightmare. Build the certified-payroll cadence into your weekly rhythm instead: the same Friday you collect the coming week's work plan from a sub, you collect their payroll for the week that just closed. Tie the two together so nobody's on next week's plan until last week's payroll is in. When you know from your look-ahead which subs had crews on site each day, you know exactly which payrolls you're owed — and you catch the missing ones in days, not at closeout.
Small Business Participation Is a Schedule Problem, Not Just a Reporting One
Most public contracts carry participation goals — DBE, MBE/WBE, SBE, SDVOSB, HUBZone, whatever the funding source requires. The mistake I see constantly is treating these as an accounting exercise you reconcile at the end. By then it's too late. If you're at 6% DBE participation on a 12% goal in the final months, there's no scope left to shift, and you're writing a good-faith-effort narrative that may or may not fly.
The fix is to track participation as a live number against committed dollars and against the work still ahead of you. Every month, look at what's left to buy out or self-perform and ask whether a certified firm can realistically take it. A DBE trucking or a certified supplier line item you slot in during procurement counts; one you scramble to find at 90% complete usually doesn't. Your rolling look-ahead is where this lives — the four-to-six weeks of upcoming work is exactly the window where you can still steer a scope toward a certified sub before the buyout closes.
Keep the count honest: only the certified firm's own performed value counts toward the goal. If a DBE just passes material through from a non-certified supplier, most agencies only credit the fee, not the full pass-through. Know the counting rules for your specific program before you bank on a number.
Documentation That Survives an Audit Three Years Later
Private work, you document to protect a change order this month. Public work, you document to protect yourself in an audit or a dispute that lands two or three years after the ribbon-cutting, long after the crews scattered and the daily reports on someone's phone are gone. Assume every record you keep will someday be read by a stranger with a red pen.
What that means in practice:
- Daily reports every single day, including no-work days — weather, crew counts by trade, equipment, deliveries, inspections, and any direction given or received. A blank day is data too.
- Contemporaneous notes on delays. A note written the day the inspector no-showed is evidence. The same note reconstructed from memory during a claim is a liability.
- An audit trail that shows who changed what, when. Editable spreadsheets and overwritten schedules are worth almost nothing in a dispute. You want records that lock — dated, attributed, and unable to be quietly rewritten after the fact.
This is where a real scheduling and field system earns its keep over a pile of spreadsheets. When your weekly work plans and their revisions are captured with dates and authorship, your as-planned-versus-as-built story tells itself. On a delay claim, being able to pull the actual week-by-week look-ahead you published — and show what changed and when a constraint hit — is worth more than any narrative you write after the fact.
Inspections, Testing, and the Long Lead Times Nobody Warns You About
Public jobs carry more inspection and testing than private work, and the inspectors don't work for you. A city building inspector or a state DOT materials inspector serves a dozen projects, and "I need you tomorrow" gets you a slot next week. Treat every required inspection and every special-inspection hold point as a constraint with a real lead time, not a same-day phone call.
Rules of thumb I hold my teams to on public work:
- Request agency and third-party inspections 48–72 hours out, minimum. Concrete pours and anything with a batch-plant ticket, give even more notice.
- Never let a covered inspection slip. If a required inspection didn't happen and you closed the wall or backfilled the trench, you may be opening it back up — on your dime. Megger the runs, pressure-test the lines, and get the sign-off before anything gets covered.
- Track special-inspection reports as their own deliverable. The steel got inspected, but if the report isn't in the file, to an auditor it didn't happen.
Fold these into your short-interval schedule as constraints on the activities they gate. If your look-ahead flags that the inspector needs to be called two days before rough-in cover, that's a hold you clear on Monday for a Wednesday inspection — instead of a crew standing around Wednesday waiting on a call nobody made.
Change Orders and Claims: Slower Approvals, Higher Proof
Government change orders move through more layers and demand more justification than anything on the private side. A Contracting Officer isn't going to sign off on "differing conditions, add $30k" — they need the who, what, when, why, the cost breakdown, and the schedule impact, all documented. And the approval can take weeks, sometimes months, while your subs want to keep moving.
Two habits keep you whole:
- Notice deadlines are real and they're short. Many federal and state contracts require written notice of a claim or changed condition within days of discovery. Miss the notice window and you can forfeit an otherwise valid claim entirely. Know your notice clause cold.
- Document the schedule impact when it happens, not later. When a change hits, capture how it shifted your look-ahead — what got pushed, what crews idled, what the downstream trades lost. A time-stamped weekly plan showing the disruption is far stronger than a retrospective analysis built for the claim.
Buy American, Domestic Sourcing, and Procurement Lead Times
Buy American, Build America Buy America (BABA), and similar domestic-preference rules mean the material your sub wants to order may not qualify. Domestic steel, iron, and manufactured products often carry longer lead times and higher prices than the imported alternative your sub is used to spec'ing. If procurement discovers this at the last minute, you eat the schedule hit.
Get country-of-origin and compliance documentation nailed down during buyout, and build the longer domestic lead times into your procurement log up front. Track the paper — mill certs, manufacturer certifications, origin documentation — the same way you track submittals, because on a compliance audit that paper is the material.
The Common Thread
Notice that almost none of this is about knowing how to build. It's about running a tighter operation — collecting the right paper on a predictable cadence, seeing constraints far enough out to clear them, and keeping a defensible record of what actually happened week by week. That's precisely what disciplined short-interval scheduling gives you: a rolling look-ahead where each sub's work, constraints, inspections, payrolls, and participation are visible together, updated every week, and captured with dates you can stand behind.
Tools like LookAheadWall exist to make that rhythm sustainable across a whole subcontractor roster instead of living in your head and a stack of spreadsheets. But the tool is secondary. The habit is the thing. Get the weekly discipline right — plan the next few weeks with your subs, clear constraints before they bite, and document as you go — and public work stops being a paperwork minefield and starts being just another well-run job. The kind where "substantially complete" actually means you're done.