The first time I ran a federal job, I thought the hard part would be the concrete. It wasn't. The concrete went fine. What nearly ate us alive was the paperwork wrapped around it: certified payroll due every week whether or not the crew worked, wage determinations that didn't match the classifications my subs actually used, a DBE goal we were quietly falling short of, and an inspector who would only sign off if he'd been notified 48 hours ahead in writing. Government work is regular construction with a compliance shadow that follows every task around the site. If your field tools only track the concrete, you're managing half the job.
This article is about the half most schedulers ignore — how the field side of a public project actually works, where it goes sideways, and what your look-ahead and reporting need to capture so compliance stops being a fire drill. None of it is exotic. It's just relentless, and it rewards the crews that build the tracking into the daily routine instead of reconstructing it at the end of the month.
What makes a government job different from the field up
On private work, the schedule is the deliverable and documentation is a nice-to-have. On public work, the documentation is a deliverable — sometimes a payment condition. Miss a certified payroll and your progress payment can be held. Blow a DBE commitment and you may owe liquidated damages. Fail to notify an inspector on the agency's terms and you'll re-do work you already covered up.
That changes how you plan. Every activity on a public job carries invisible attachments: a labor classification, a documentation requirement, an inspection hold point, sometimes a material-origin certificate. The superintendents who thrive on this work treat those attachments as part of the task, not a separate back-office problem. When you build a weekly work plan, you're not just deciding who frames wall 3 on Tuesday — you're implicitly deciding what payroll classification that carpenter falls under, whether that wall needs a framing inspection before drywall, and who has to be told, when.
Certified payroll: the weekly deadline that never moves
The federal form is the WH-347, and its sibling requirements show up on state and local prevailing-wage work under different names. The rule that trips up first-timers: you file every week you're on site, including weeks with no work performed — a "no work" payroll is still a payroll. Subs file theirs up through you, and you're on the hook if theirs are late or wrong.
The failure mode is almost never the math. It's the source data. Certified payroll is only as clean as the time records feeding it, and those are captured in the field by people who'd rather be swinging a hammer. Three things go wrong constantly:
- Misclassification. A worker doing laborer tasks in the morning and operating a machine in the afternoon has to be split across two classifications at two wage rates. Crews that log "8 hours, John" instead of the split create a discrepancy that surfaces during an audit, months later, when nobody remembers the day.
- Fringe accounting. Prevailing wage is base rate plus fringe. If you pay fringe as cash instead of into a plan, it has to show correctly on the form. This is where a lot of small subs get letters.
- Apprentice ratios. You can pay apprentice rates only if the apprentice is in a registered program and you're inside the allowed ratio of apprentices to journeymen on site that day. Put too many apprentices on the wall and some of them owe journeyman wages retroactively.
The fix is upstream, in the field, on the day. Capture the classification with the hours, not after. If your daily reporting ties each worker's logged time to a classification as the foreman fills it out, your weekly certified payroll becomes an export instead of an archaeology project. This is the single highest-leverage habit on a public job — get it right and half your compliance headache disappears.
Prevailing wage and the classification trap
Wage determinations are published per county and per trade, and they do not always line up with how your subs actually staff the work. A "cement mason" on the determination might be doing what your sub calls a "finisher." The gap between the official classifications and the real crew is where money leaks. Before mobilizing, walk the wage determination against your actual scope and map every task to a classification. Do it once, in the office, with the sub in the room. Doing it task-by-task in the field, under pressure, is how errors get baked in.
One rule of thumb from hard experience: when a worker's classification is ambiguous, the more expensive classification usually wins in an audit. If you're not sure whether someone's operating or laboring, assume the higher rate until you've confirmed otherwise. Underpaying is a finding; overpaying is just margin.
DBE, MBE, and WBE goals: track the trajectory, not the total
Disadvantaged, minority, and women-owned business participation goals are set as a percentage of contract value, and the mistake almost everyone makes is treating them as an end-of-job number. They're not. They're a trajectory. If you're at 4% participation at the halfway mark on a 10% goal, you can't magically make it up pouring the last slab — the DBE-eligible scopes may already be behind you.
Tie participation to the schedule. When you're doing a look-ahead, you should be able to see which upcoming scopes are being performed by which businesses, and whether the running DBE percentage is tracking toward the goal or falling behind. Catch the shortfall at week six, not month six, and you still have scopes left to reallocate. Catch it at closeout and your only options are an uncomfortable good-faith-effort narrative or a check to the agency. The schedule is where participation is either protected or lost, because the schedule is where scope gets assigned.
Inspections and hold points: notify on their terms, in writing
Agency inspectors don't work like the private-side third party who swings by when you call. They have notification windows — often 24 or 48 hours — required in writing, and they have hold points you cannot cover until they've signed. Bury a framing inspection or a rebar inspection in a wall or a slab and you'll be opening it back up.
Build hold points into the look-ahead as hard constraints, the same way you'd treat a concrete cure time. A framing-to-drywall transition on a public job isn't "frame Thursday, rock Friday." It's "frame Thursday, notify inspector Thursday morning, inspection Friday, rock Monday" — the notice lead time is part of the sequence, and if it isn't drawn into the plan, someone will forget it under pressure and you'll lose the weekend. The general habit that saves you: for every inspection in the next two to three weeks, the notification should already be sitting in the plan with a date attached, visible to whoever is running the wall.
Documentation and audit readiness: the daily report is your defense
Public contracts get audited — sometimes years after substantial completion, sometimes because a disgruntled sub filed a complaint. The daily report is your evidence file. Weather, crew counts by classification, equipment on site, deliveries, delays, inspector visits, verbal directions from the agency — if it isn't written the day it happened, it effectively didn't happen when the auditor comes looking.
A few habits that hold up under scrutiny:
- Photograph everything you're about to cover. Rebar before the pour, framing before the rock, waterproofing before backfill. Date-stamped, and tied to the day's report.
- Log agency verbal direction immediately, in writing. "Inspector told us to add two more anchors on grid C" is a change if it wasn't in the contract. Capture it the same day and it protects both your schedule and your claim; capture it three weeks later and it's your word against theirs.
- Keep records for the full retention period. Federal certified payroll records generally must be retained for three years after the job — often longer under state rules. Don't purge at closeout.
The point of centralizing field reporting in one place isn't tidiness. It's that when the audit letter arrives, you can produce the record in an afternoon instead of a panicked week of digging through binders and phones.
Buy America and material origin
Federally funded work increasingly carries domestic-content requirements — steel, iron, and manufactured products may need to be produced in the U.S., with certification to prove it. This is a procurement and submittal issue that lands squarely in the field, because it's the field that receives and installs the material. If a sub shows up with imported rebar on a Buy America job, catching it at the gate is a problem; catching it after it's in the deck is a disaster. Flag material-origin requirements against the specific deliveries in your procurement look-ahead so the certification is confirmed before the truck is unloaded, not after the concrete's around it.
Progress payments and schedule format compliance
Agencies frequently dictate how you report — a specific schedule format, a required update cadence, sometimes a CPM baseline you have to maintain and show variance against for every pay application. Your field-level look-ahead and the contractual CPM schedule are two different animals serving two different masters, and part of the job is keeping them honest with each other. The CPM satisfies the contract; the weekly work plan runs the actual crews. When those two drift apart, your progress payments get questioned and your as-built story falls apart at closeout.
How the right field tools carry the load
None of this requires heroics. It requires that compliance data get captured at the moment work is planned and performed, by the people doing it, rather than reconstructed later by someone in the trailer. That's the real argument for good field and look-ahead scheduling software on public work: a tool like LookAheadWall lets you build the weekly work plan and trade-flow sequence where the crews already are, so the classification, the inspection hold point, and the DBE-scope assignment travel with the task instead of living in a separate spreadsheet nobody updates. Short-interval scheduling was built to keep the near-term plan honest; on a government job, an honest near-term plan is also your compliance early-warning system.
The superintendents who make government work look easy aren't smarter about concrete. They've just stopped treating compliance as a separate job. They build it into the same weekly rhythm they use to run the crews — plan the work, plan the paperwork the work triggers, and capture the record as it happens. Do that, and the compliance shadow stops chasing you. It walks in step.