The first time you run a Last Planner job on a federal contract, you learn fast that the planning board on the wall and the paperwork in the trailer are two different animals — and both have to agree. Private work forgives a lot. A government job does not. The contracting officer has a copy of your baseline, the QC firm has a three-phase checklist for every definable feature of work, and the payroll clerk needs certified records by Thursday. None of that changes the physics of building. What it changes is the discipline around your weekly work plan, and where the plan can quietly get you in trouble if you treat public work like it's just private work with more forms.
Last Planner and look-ahead scheduling still work here — arguably they work better, because public jobs punish poor coordination harder. But you have to bolt the collaborative planning process onto a rigid contractual skeleton. This is a field guide to doing that without getting buried.
Where the CPM baseline and your weekly plan actually meet
Almost every federal and most state contracts require a CPM baseline schedule, monthly updates, and often a written narrative explaining variances. That's the contract schedule. It lives in Primavera or MS Project, it has thousands of activities, and the contracting officer's rep judges your progress and your payment applications against it.
Your look-ahead is a different tool with a different job. The CPM tells you the contractual sequence and the money; the look-ahead — the three-to-six-week window your foremen actually plan against — tells you what's buildable next Tuesday. The mistake I see supers make is treating them as one document. They aren't. The right relationship is a hierarchy:
- The CPM baseline sets the contractual milestones and the network logic you'll be measured against.
- The six-week look-ahead pulls the next slice of that network into a realistic, constraint-free plan.
- The weekly work plan commits crews to specific, make-ready work — the promises your last planners make in the Monday meeting.
Here's the rule that keeps you out of a claim: your look-ahead can be more detailed than the CPM, but it should never contradict it. If your crews are consistently sequencing work in an order the CPM doesn't reflect, that's a signal to formally revise the CPM through the update process — not to quietly run two conflicting schedules. When a delay claim gets analyzed, a forensic scheduler will pull your daily logs and your look-aheads and lay them against the baseline. If the field record shows you were building in a sequence your own approved schedule never contemplated, you've handed the other side an argument. Keep them reconciled. A look-ahead tool like LookAheadWall earns its keep here precisely because it lets the field plan stay visual and location-based while still mapping cleanly back to the CPM activities the contract cares about.
Building the three-phase QC into your make-ready
On USACE and NAVFAC work, the three-phase control system — Preparatory, Initial, and Follow-up inspection for every definable feature of work — is not optional and it is not a formality. This is the single biggest scheduling difference between public and private work, and the one that wrecks the most weekly plans when a super forgets to account for it.
The trap is simple: a crew is ready to start, materials are on site, and the foreman commits the activity in the weekly plan — but the Preparatory Phase meeting for that feature of work hasn't happened yet. Now you can't legitimately start, your PPC (percent plan complete) takes a hit, and if the crew starts anyway you've got non-conforming work and a QC deficiency.
Treat the three-phase inspections as constraints in your look-ahead, the same way you'd treat a permit or a submittal:
- The Preparatory Phase meeting must be scheduled and closed before the activity can enter the weekly plan. Put it in the look-ahead one to two weeks ahead of the work, because it requires the right people — QC manager, foreman, the government QA rep — in a room together, and their calendars are the real constraint.
- The Initial Phase happens at the start of the actual work, on the first section put in place. Build a small buffer here; the initial inspection can catch a workmanship or layout issue that pauses the crew for a day.
- Follow-up is continuous, but the documentation of it is what keeps your pay application clean.
A foreman who understands that "make-ready" on a federal job includes "Prep meeting held and signed" will protect your PPC far better than one who only checks for materials and manpower.
Submittals and long-lead items: the constraint that sinks public jobs
Government submittal review runs on its own clock, and it is rarely a fast one. A government reviewer may take the full contractual review period — often 20 or 30 days — and can return a submittal "Revise and Resubmit," which resets the clock. On a private job you can sometimes lean on the architect for a quick turnaround. On a federal job, leaning doesn't work, and pretending the review will come back early is how you build a look-ahead full of activities you can't actually start.
Run your submittal register as a live constraint log feeding the look-ahead. For every activity in your six-week window, the honest question is: is the governing submittal approved, not just submitted? A "Furnish and Install" activity with an unapproved submittal is a phantom — it looks buildable on the board and isn't. Backing each look-ahead activity up to its submittal and procurement status is exactly the kind of constraint screening Last Planner is built for, and it's where a lot of public-project schedule slippage actually originates.
The stakeholder layer changes who's in the room
On private work your weekly plan meeting is you, your foremen, and the key subs. On government work there's a layer above that — the Contracting Officer (KO), the Contracting Officer's Representative (COR), the QA representative, and sometimes the end-user agency who will occupy the building. You don't run the Last Planner meeting with all of them; that would be unworkable. But your plan has to survive contact with them.
Practical rule: keep the collaborative planning session lean — your last planners are still the foremen and sub leads who make and keep commitments. But maintain a clean, documented output from that meeting that you can hand up the chain. The government side wants to see a controlled process, formal correspondence through the KO or COR, and a schedule that reconciles to the baseline. When your weekly work plan produces a tidy record — commitments made, constraints logged, reasons-for-variance captured — you're feeding the formal machine without turning your field meeting into a bureaucratic circus. That separation, field planning below and formal reporting above, is what keeps both running.
Compliance work that has to live on the schedule
Several government-specific requirements aren't "activities" in the traditional sense but will absolutely stop your crews if they slip off the plan. Put them where you can see them.
- Davis-Bacon / prevailing wage: Certified payrolls are due weekly, and a persistent gap in certifieds can hold up your progress payment. It won't stop a crew from working, but it will stop your money — which eventually stops everything. Track the certified-payroll status alongside the schedule so it never becomes a surprise.
- Small business / subcontracting goals: Federal contracts carry participation goals with real reporting behind them (eSRS on federal work). When you're sequencing which subs work which scopes, the ones carrying your DBE/SDVOSB/small-business commitments need to actually get the work, in the amounts you committed. A look-ahead that quietly reroutes scope to a bigger self-perform crew can put you out of compliance months before anyone notices.
- Environmental and preservation constraints: If your job carries NEPA mitigation, a stormwater permit with inspection cadence, or Section 106 archaeological monitoring, those are hard gates. Archaeological monitoring in particular is a classic weekly-plan killer — you cannot excavate in a monitored area without the monitor present, and the monitor's availability is a scheduling constraint you don't control. Put the monitor's presence in the make-ready check for any ground-disturbing activity in a sensitive zone.
Documentation: your daily log is your schedule's memory
On public work the daily record isn't housekeeping — it's evidence. If there's ever a delay dispute, an REA (Request for Equitable Adjustment), or a differing-site-conditions claim, the contemporaneous record wins. The look-ahead and weekly plan are part of that record when you keep them.
The practice that pays off: every week, capture why commitments weren't met. Last Planner already asks you to log reasons for variance — on a government job, that variance log does double duty as claims documentation. "Activity slipped because the Prep meeting couldn't be scheduled until the government QA rep returned from leave" is a fact you want written down the week it happened, not reconstructed a year later from memory. A rolling, dated record of what you planned, what you built, and what blocked you is worth more in a dispute than any after-the-fact narrative.
Closeout starts on day one, not the last month
Government closeout is heavier than private closeout and it back-loads schedule risk if you ignore it. Beneficial occupancy, final inspection, punch resolution, as-builts, O&M manuals, warranty documentation, and — if it's a LEED or enhanced-commissioning job — a full commissioning sequence that has to run before acceptance, not after.
Commissioning is where supers get caught. Enhanced commissioning requires functional performance testing of systems, and those tests need the systems energized, balanced, and stable — which means mechanical, electrical, and controls all have to converge with real slack before the Cx agent shows up. Pull commissioning into your look-ahead as its own multi-week sequence with the trade-flow dependencies made explicit, and start protecting float for it months out. A commissioning failure in the final weeks doesn't just delay a report; it delays beneficial occupancy and the money that comes with it.
The takeaway
Last Planner and look-ahead scheduling aren't a poor fit for government work — they're a better fit than most supers expect. The collaborative, constraint-screening discipline is exactly what a compliance-heavy contract needs. What you have to add is rigor at the seams: keep the look-ahead reconciled to the CPM, treat inspections and submittals as first-class constraints, protect the compliance requirements that stop your money before they stop your crews, and keep a clean, dated record that doubles as claims defense. Read your specific contract's Section 01 requirements before you build your first weekly plan, because the three-phase QC clause, the schedule submission clause, and the payroll clause will each reshape how your plan has to work. Do that, and the same visual weekly planning you'd run on any job carries you cleanly through the paperwork instead of drowning in it.