Boards typically find out a capital program is in trouble the same way: a status report that was "green" for months turns "yellow," then "red," with no visible transition in between. By the time the color changes, the schedule slip or cost overrun is usually already locked in — the board is being informed of a decision that was effectively made weeks or months earlier on the floor.

This isn't usually a reporting failure in the sense of dishonesty. It's a structural one: the metrics that reach board level are often lagging indicators — cost-to-date, milestone completion, schedule variance — that confirm a problem only after it has already accumulated. By the time a lagging indicator moves, the leading conditions that caused it have usually been visible on the floor for weeks.

What early execution drift actually looks like

Before a capital program shows up as behind schedule or over budget in a board deck, it typically shows earlier, quieter signals:

  • Engineering change requests accumulating faster than they are being resolved
  • Vendor delivery commitments slipping by days at a time, individually small enough that no single slip triggers escalation
  • Field labor hours trending above plan on early work packages, without a corresponding conversation about whether that's a one-time ramp cost or a structural underestimate
  • Milestone definitions quietly loosening — "substantially complete" doing more work in month four than it did in month one

Individually, each of these is often dismissed as noise. Collectively, and early, they're a leading indicator that the program's actual trajectory has diverged from its reported trajectory.

What board-level oversight can reasonably ask for

Fiduciary oversight of a capital program doesn't require board members to become project managers. It does mean asking for the kind of operating telemetry that surfaces drift before it becomes unrecoverable:

  • Leading indicators alongside lagging ones. Change-request backlog, vendor commitment slippage, and early labor variance are available well before cost and schedule variance move.
  • A defined threshold for what triggers escalation to the board, set in advance — not left to the judgment of whoever is preparing the status deck that quarter.
  • Direct visibility into how "on track" is being defined, since the definition itself can drift without anyone deciding to change it.

The cost of finding out late

The gap between when execution drift becomes visible on the floor and when it becomes visible at the board level is often the single largest driver of how expensive a recovery ends up being. Programs caught early are re-sequenced. Programs caught late are re-negotiated, re-funded, or written down. The oversight question isn't whether the board trusts the team running the program — it's whether the reporting structure gives early problems anywhere to surface before they compound.