Three Audiences, Two Schedules, One Board Meeting

The diagnosis

• Percent complete is cumulative and almost always rises. It can climb steadily while the driving path slides, because earned progress accrues on non-critical work. Reporting it alone with a green status is the classic 'green on the outside' failure.
• Two different views were produced from the same project with no reconciliation between them, so the project had two truths. Once the JV found the gap in a board meeting, every future report inherits the credibility cost.
• 'Green' was assigned to the percent complete rather than to the outcome the committee cares about: will the milestones be met?

What the executive view should carry

• A milestone scorecard: planned vs forecast dates for the 12 critical milestones, with days of variance - not percent complete.
• Trend on the driving path: is critical-path float growing or shrinking over the last 3–6 months?
• Schedule health indicators that do not flatter: negative float, open ends, constraint count, number of activities with large remaining duration.
• Top schedule risks and the specific decisions or interventions the committee is being asked to make.
• A short narrative explaining cause and forecast, signed by the project manager.

Design principle

• One schedule, one data date, many views. Every report must be traceable back to the same update; no report is hand-built in parallel.

Steering committee

• Monthly, issued 3 working days before the meeting: one page of milestones, float trend, top risks, decisions needed, plus the narrative.
• No raw Gantt. No percent complete presented alone.

JV partner

• Controlled access to the native file at a stated version and data date, with a change log and a reconciliation note against the previous issue.
• Agreed review cycle before external use, so the partner is never surprised in a board meeting by a number the project already knew.
• Clear ownership of the file: read-only distribution, single publisher.

Subcontractors

• Weekly 6-week look-ahead, filtered to their scope and derived from the current schedule, showing constraints, permits and predecessor status.
• A defined feedback route: their progress submissions come back through the scheduler, are checked for consistency with the logic, and only then entered into the master.
• Any look-ahead that has drifted from the baseline is reissued, with the reason stated.

Control

• These details belong in the communications management plan, with reporting dates locked and late inputs escalated.

Communicate early, with facts and options

• Get ahead of it: a correction delivered by the project is recoverable; a correction discovered by the partner is a governance finding.
• Lead with the number and the cause: which milestones, how many days, driven by what - then the forecast and the recovery options with cost and risk.
• Bring decisions, not just bad news: option A (recover with added resource, cost X, confidence Y), option B (re-sequence, recovers Z days), option C (accept the slip and shift the affected commissioning window).

What not to do

• Do not re-baseline to make the variance disappear. If a re-baseline is genuinely warranted, take it through change control with sponsor approval, keep the original baseline intact, and report against both for a period.
• Do not soften the language. 'Slightly behind' for 9 of 12 milestones reads as concealment on the second pass.

Repair the credibility

• State what changes in reporting so the committee can rely on the next pack: milestone-based status, published data date, reconciliation between views, and a named owner for the numbers.
• Log the issue with the corrective action, and ask the committee to confirm the reporting standard it expects - that converts a failure into a shared governance decision.