What to Look for in a Contractor Programme Audit

A contractor's programme is a commercial instrument. It allocates risk, frames every future delay conversation, and quietly decides who pays for float. Accepting a baseline without a proper programme audit is signing that instrument unread — and by the time the dispute arrives, the programme you accepted is the evidence.

Here is what an experienced auditor reads for, in rough order of how often it pays.

Open logic and the illusion of a critical path

Activities without successors are promises the network never has to keep. A programme with hundreds of open ends can show you any critical path it likes, because large parts of the work simply do not push on the end date. The DCMA 14-point check counts these mechanically — missing logic, dangling activities, redundant links — and a mechanical pass is the floor, not the ceiling. The real question: does the driving path match how the job will actually be built? If the critical path runs through the fit-out while the site team is losing sleep over switchgear delivery, the programme is describing a different project.

Float: sequestered, manufactured, or honest

Float is where commercial games live. Watch for the classics: preferential logic that soaks up float on client-facing paths; calendars that quietly differ between similar activities; constraints — especially "start no earlier than" — parked where they pin work conveniently late; and lags doing the job of activities so duration hides inside arrows. Individually each has an innocent explanation. In combination they are a posture: a programme built to generate entitlement rather than to coordinate work.

An audit should quantify it. Strip the manipulative constraints in a copy of the file, re-run the schedule, and watch what moves. The delta between the submitted programme and the cleaned one is a fair first estimate of how much negotiating position is embedded in the baseline.

Resourcing fiction

A logic network can be immaculate and still impossible. Test durations against crew build-ups: does the programme imply a peak workforce the site can't induct, park, or physically fit? Do parallel fit-out fronts assume the same crane? On hyperscale programmes we cross-check labour histograms and peak-week detection across scope owners — because trade stacking that looks fine bar-by-bar becomes obvious when you sum it.

Procurement reality

Every major-project programme claims its long-lead equipment arrives just in time. An audit traces the chain the other way: purchase order dates against actual market lead times, factory test slots, shipping, and site receipt — then asks what happens to the logic when (not if) one slips. Long-lead and owner-furnished items are the most under-managed schedule risk in major projects; a baseline that treats them as reliable calendar dates has already conceded the first EOT argument.

Progress integrity on live programmes

Auditing is not only for baselines. On live programmes, check whether claimed progress reconciles with earned logic: activities at 90% for three consecutive updates, out-of-sequence work quietly re-logicked each month, or a forecast that never moves while float evaporates. These are the early signatures of a programme being managed for the report, not the site.

The posture that works

Two things make audits land. First, write findings for decision-makers — "these 14 constraints move the contractual completion 6 weeks later than the logic supports" beats a table of DCMA percentages. Second, run it with the delivery team where possible, not on them: most programme defects are inherited habits, not conspiracies, and a team that understands the finding fixes it. We audit for owners accepting baselines and for contractors who would rather find their own weaknesses first — the second engagement is always cheaper.

Nomad SPS provides independent programme audits and delay analysis across Australia — the same scrutiny operator-grade clients apply, pointed wherever you need it. Talk to us.