There's a familiar disconnect on a lot of jobs. The scheduler updates the master CPM once a month in the trailer, the project manager runs cost reports off the accounting system, and the field runs its own weekly plan on a whiteboard that nobody upstairs ever sees. Three versions of "how the job is doing," and they rarely agree. When the owner asks in the OAC meeting why the schedule says 62% but the billing says 71%, everybody looks at their shoes.
Project controls — the whole apparatus of tracking cost, schedule, and scope against a plan — only works if it's fed real information about what's actually getting built this week. And the place that information is freshest and most honest is the look-ahead. The three- to six-week plan the foremen build is the closest thing on the job to ground truth. If your controls function isn't drinking from that well, it's forecasting off month-old data and wondering why the numbers keep sliding.
This article is about closing that gap: how near-term field planning actually connects to cost management, earned value, risk, and forecasting, and where it quietly goes wrong.
Why the Look-Ahead Is the Best Data You Have
A master schedule is a promise made at bid time. It's useful for the big shape of the job and for milestone dates in the contract, but by month four it's a historical document that's been re-baselined twice. The look-ahead is different — it's rebuilt every week by the people who are physically going to do the work, and it's constrained by what's real: what material showed up, which inspection cleared, whether the crane is available Thursday.
That makes it the most current, most granular read on the job you'll get. The catch is that this quality of data is perishable. A look-ahead is accurate this week and stale in three. So the integration you're after isn't a one-time data dump — it's a weekly rhythm where field commitments and their outcomes flow into the money side while they're still true.
Earned Value Runs on What the Field Actually Finished
Earned value management lives or dies on one number: how much of the planned work is genuinely done. Budgeted Cost of Work Performed — BCWP, the "earned" in earned value — is just the budget value of completed work. If your percent-complete is a guess made by someone who hasn't walked the deck, your SPI and CPI are decorative.
This is where field-level planning earns its keep. When a foreman closes out "hang drywall, Level 3 north wing" as complete in the weekly plan, that's a real, verified quantity you can tie to a budget line. Aggregate those honest completions and your earned value has a spine. A few things to get right:
- Measure at the right grain. "Frame the building — 40% done" is a fiction someone made up. "Framed grids A–F, levels 1–2" is a fact. Location- and system-based tracking, which is how good look-ahead planning works anyway, gives you completions you can actually defend.
- Beware the 90% syndrome. Activities race to 90% and then camp there for weeks on punch and trim. If your progress input rewards "almost done," your SPI will look great right up until it doesn't. Rules-of-credit (0/50/100, or quantity-based) protect you from optimistic field reporting.
- Reconcile schedule progress against billing monthly. If physical percent-complete and billed percent-complete drift more than a few points apart, one of them is lying. Usually it's the billing, front-loaded to help cash flow — which is fine as a strategy but poison as a data source for forecasting.
Map Activities to Cost Codes, or the Integration Stays Theoretical
Here's the unglamorous work that makes everything above possible: your schedule activities have to connect to your cost codes. If the field plans in "areas and trades" and accounting tracks in "cost codes and pay items," and nothing maps between them, you'll spend every close-out week manually translating, and the translation will be wrong.
You don't need a resource-loaded schedule down to every stick of lumber — that level of loading is a maintenance burden most jobs abandon by month two. What you need is a clean, agreed crosswalk: this activity type rolls up to that cost code. Do that once, enforce it, and variance analysis becomes something you can actually run instead of a quarterly forensic project. When schedule and cost speak the same coding language, a slipping activity immediately shows up as a cost exposure, not a surprise three billing cycles later.
Cash Flow Is Just Your Schedule with Dollar Signs
Every developer and every CFO wants a cash flow curve, and the honest one is nothing more than your schedule projected forward with costs and billings attached. The near-term portion of that curve — the next month or two — is where the look-ahead makes it trustworthy.
The master schedule might say the structural steel package bills in April. The look-ahead knows the erector is two weeks behind on shop drawings and the first billing won't hit until the crane's on site in May. That two-week slip is real money in the S-curve, and it's invisible unless near-term field reality is feeding the forecast. Roughly: costs get incurred as crews perform work (labor and installed material), billings follow completion by a cycle, and retention holds a slice until the end. A look-ahead that's honest about when work will actually progress is what keeps the cash flow projection from being a fairy tale.
Constraints Are Your Risk Register in Disguise
Formal risk management on most jobs is a spreadsheet somebody updates before the owner's meeting. Meanwhile, the real risks are sitting in plain sight in the look-ahead as unresolved constraints — the tasks that can't start because a submittal's still in review, a long-lead item hasn't shipped, an inspection isn't scheduled, or a predecessor trade is behind.
A constraint that's still open two weeks before its activity is supposed to start is a schedule risk with a countdown clock on it. Treat the look-ahead's constraint log as a leading indicator:
- Age your constraints. A constraint opened three weeks ago and still not cleared is far more dangerous than one logged yesterday. Sort by age, not by date needed.
- Watch the make-ready runway. The whole point of a six-week look-ahead is that you have six weeks to clear constraints before work is committed. If constraints are routinely getting resolved in the last few days, your make-ready process is broken and delays are coming whether or not the risk register says so.
- Convergence points are where risk concentrates. An activity waiting on three predecessors, or a location where four trades stack in the same week, carries more schedule risk than the raw duration suggests. Trade-flow sequencing makes these pinch points visible; a linear task list hides them.
PPC: The One Metric That Predicts the Others
If you take one number from the field into your controls package, make it Percent Plan Complete — the share of last week's committed tasks that actually got done. PPC isn't a schedule metric that lives off to the side; it's the single best predictor of whether your forecast is worth anything.
The logic is direct. A crew running 50% PPC is completing half of what it commits to each week. Any forecast built on that crew's promises is off by a factor of two, no matter how polished the Gantt chart looks. A crew holding 85%+ is reliable, and its commitments are forecastable. So PPC and its trend belong right next to SPI and CPI in the controls dashboard — and when you dig into the missed commitments, the reasons why (prerequisite not ready, out of materials, changed priorities) hand you a ready-made list of what's actually throttling the job.
Subcontractor Performance Is a Cost Signal
The field knows which subs show up with the right crew size and which ones promise eight and send three. That knowledge usually stays in the super's head. It shouldn't — it's controls data. A trade that consistently misses its weekly commitments isn't just a schedule annoyance; it's a cost exposure (your GCs and extended overhead) and, if it ever goes to a dispute, the difference between a defensible position and a he-said-she-said. Tracking commitment reliability by sub, week over week, turns a gut feeling into a documented pattern you can act on before it becomes a claim.
Change Orders Ripple Both Ways
When a change hits, everybody focuses on the direct cost — added material, added labor. The schedule impact is where the real money often hides, and it's the part that's hardest to prove after the fact. A change that pushes a critical activity two weeks doesn't just cost the change's own value; it can cascade into extended general conditions, resequenced trades, and lost productivity from stacking.
The discipline that saves you here is documenting the look-ahead as it was before the change and as it became after. That contemporaneous record — this is what we planned, this is how the change forced us to replan — is the backbone of any legitimate time-impact analysis. Trying to reconstruct it from memory six months later is how contractors leave real money on the table.
Making the Connection Actually Work
The integration fails more often on process than on technology. A few things separate the jobs where this clicks from the ones where it stays a nice idea:
- One source of schedule truth. If the field's weekly plan and the controls schedule are two separate documents maintained by two people, they will diverge, and you'll spend your energy reconciling instead of building. The look-ahead the foremen commit to should be the same data the PM forecasts from.
- Align the cycles. The look-ahead runs weekly; controls reporting often runs monthly. Make the monthly report a roll-up of four weeks of real field data, not a separate parallel exercise. Same numbers, different zoom level.
- Nail down who updates what, and when. Progress data is only useful if it's current and complete. Decide who marks work complete, who clears constraints, and by what day each week — then hold the line. Garbage timing produces garbage controls.
- Keep the loading light. Ambition kills these systems. A crosswalk of activities to cost codes and honest weekly completions will carry 90% of the value. Resist the urge to model every resource until you've proven you'll maintain it.
This is exactly where a purpose-built look-ahead tool earns its place. The reason field planning historically didn't feed controls is that whiteboards and paper don't export anything. When crews build their weekly work plans and trade-flow sequences in a shared system — the way LookAheadWall is set up to work — those commitments, completions, and open constraints become structured data the cost and forecasting side can actually consume. The point isn't the software; it's that the field's real read on the job stops dying on a whiteboard at the end of the week.
The Bottom Line
Project controls without live schedule data is educated guessing dressed up in a dashboard. The look-ahead is the freshest, most honest information on the job about what's getting built and what's in the way — and when it feeds earned value, cash flow, and risk instead of sitting in a separate silo, your controls start doing what the name promises. They control something. Get the field's weekly reality talking to the money side, keep it current, and the OAC meeting where the schedule and the billing finally agree stops being a fantasy.