The program had been running for eighteen months.

On paper, green across the board.

Monthly reports showing progress on track.

Milestone dates holding.

No major variations flagged.

Then we were asked to do an independent schedule review.

Not because anyone thought there was a problem.

Because the principal had a policy.

Independent assurance at the halfway point. Routine.

We started with the logic.

Within two days, we found it.

A single interface between the civils package and the mechanical installation sequence had been modelled incorrectly in the baseline.

Not dishonestly. Not carelessly.

Two teams had built their sections of the schedule independently.

Both were technically correct within their own scope.

But the handover assumption between them, the date when civils would hand over the structure for mechanical to begin, had never been formally agreed.

Each team had assumed a different date.

A six-week gap between what civils thought they were handing over

and what mechanical thought they were receiving.

Six weeks.

Invisible in the monthly reports.

Invisible in the milestone tracking.

Sitting quietly in the logic – waiting.

We flagged it.

The teams got in a room.

The interface was renegotiated.

A recovery plan was built.

The project finished three weeks late, instead of the nine weeks late it would have been if the gap had been discovered at the point of handover.

That’s the value of independent schedule assurance.

Not catching people doing the wrong thing.

Catching the gaps that nobody knew existed because everyone was looking at their own section of the schedule and assuming someone else had handled the join.

We don’t guess.

The schedule tells the truth.

If you ask it the right questions.