System & Schedule Audit
A Primavera P6 schedule audit answers a simple question: would this programme survive scrutiny — from management, from the client, from a claims consultant? A system audit asks the same question of the environment around it: are the structures, security and data quality helping your teams, or quietly working against them?
I do both, separately or together, as an independent reviewer with no stake in the answer.
Schedule audit
The schedule review goes beyond a mechanical DCMA 14-point pass: open ends, negative float, constraint abuse, unrealistic durations and lags, calendar inconsistencies, baseline integrity, progress-update discipline — and, more importantly, whether the network actually models how the work will be built. A schedule can pass every metric and still be fiction; the difference shows in the logic.
The output is not a scorecard for its own sake: it is a prioritised fix list your planners can act on immediately, with the reasoning explained so the same issues do not reappear next month.
System audit
On the environment side I review the structures (EPS/OBS, codes, calendars), security and user setup, data quality across projects, and actual usage patterns — who really works in the system and who works around it. Fifteen years of implementations make the common failure patterns quick to recognise.
Findings land in an improvement roadmap ordered by effort-to-impact: what to fix this week, what to schedule, what to leave alone. If the roadmap leads to reconfiguration or a reporting layer, you can take it to anyone — including, if you wish, me.
Confidentiality
Audit work means seeing programmes and data your competitors would love to see. I work under NDA as a matter of course, including for defence-sector clients where the requirements are stricter still — a large part of my track record is in that sector precisely because confidentiality discipline is non-negotiable there.
Frequently asked questions
What do you need from us to start?
For a schedule audit: XER/XML exports and one call for project context. For a system audit: read access to the environment (or a database backup) and short interviews with key users. Both can be done fully remotely.
How long does an audit take?
A single-programme schedule audit is typically days, not weeks. Environment audits scale with the number of projects and users — scoped honestly after the first look.
Can this support a claim or dispute?
The audit gives you an independent, documented assessment of schedule quality, which is often the starting point. Formal delay analysis for disputes is a separate engagement — tell me the context and I will say plainly whether I am the right person for it.