Complex programmes are finally being treated as a profession. Assurance should be too.

Why a job title does not fix a complex programme

Every organisation that has run a large ERP or HRIS implementation knows the gap the APS has just named.

You appoint a programme director. Capable, experienced, well regarded. Six months later the programme is drifting anyway. Scope has crept. The integrator's slippage has been rebadged as rebaselining. The status report says amber and everyone in the room quietly believes it is red.

The appointment was necessary. It was never going to be sufficient.

A title assigns accountability. It does not create the structures that make accountability workable. Decision rights that hold under pressure. A steering committee that governs rather than receives. Reporting that describes the programme as it is, not as the people inside it need it to appear. An evidence base the sponsor can actually read.

That is the distinction the APS strategy draws for the public service. Complex delivery is not a role you fill. It is a set of practised, recognised disciplines. The government has looked at its hardest programmes and concluded that titles, seniority and goodwill do not survive contact with genuine complexity.

Private-sector programmes are not different. They are simply less examined.

What a profession actually implies

The word profession carries three commitments, and each one has a consequence for how programmes should be governed.

Recognised competence. A profession distinguishes between people who hold a role and people who can do the work. The Defence strategy makes this national policy. Programme capability is treated as a workforce asset to be built and measured, not assumed.

Structured standards. A profession writes down what good looks like and holds practitioners to it. Methodologies, credentials, defined practice. The scaffolding that makes competence transferable from one programme to the next.

Evidence over assertion. This is the commitment that gets forgotten. A profession does not take its own word for its performance. Medicine has peer review. Law has appeal. Finance has audit. Every mature profession builds in a mechanism through which the work is examined by someone who did not do the work.

Delivery is acquiring the first two commitments at national level. The third is still missing from most programmes we see.

The corollary nobody has stated

Here is the uncomfortable question for any sponsor reading the government's direction of travel.

If programme delivery is a profession, who audits yours?

Not who reports on it. Every programme has reporting, and most of it is produced by the parties being reported on. The vendor reports on the vendor's progress. The system integrator reports on the integrator's milestones. The programme team assembles both into a pack, under time pressure, for a steering committee that has little independent means of testing any of it.

That is not assurance. That is the work marking its own homework, professionally formatted.

Consider how the true position actually travels on a large programme. A workstream lead knows the build is behind, and reports it with context. The programme office consolidates twelve of those reports into one, and the context becomes a footnote. The delivery partner reviews the pack before it goes up, and the footnote becomes a watch item. By the time the position reaches the steering committee it has passed through four sets of hands, every one of them with a reason to soften it.

Nobody lied at any step. The structure did the softening on everyone's behalf.

Assurance is structurally different. It is an examination of programme health by a party with no stake in the answer. Independent of the vendor. Independent of the integrator. Independent, crucially, of the delivery team whose performance is part of what is being examined. Its product is evidence a board can rely on. Where the programme actually stands, which risks are real, whether the business case still holds, and what has to change.

Boards already understand this everywhere else. Nobody accepts unaudited accounts because the finance team is experienced. Nobody skips the building certifier because the builder seems confident. Yet organisations routinely run nine-figure transformation programmes on self-reported status, and discover the true position only when the go-live date stops absorbing it.

The establishment has now conceded that complex delivery is a profession. The corollary is that assurance is its audit function. One does not work without the other.

What this looks like on a private programme

On an ERP or HRIS programme, independent assurance is concrete and unglamorous.

It looks like a structured health check at the moments that decide the programme. Before mobilisation, when the business case and the delivery structure can still be corrected cheaply. At phase gates, when the decision to proceed deserves better evidence than momentum. Before go-live, when someone has to walk the executive through the readiness position and be free to say not yet.

It looks like governance examined against a standard, not against habit. Whether decision rights are real. Whether the steering committee sees the programme or a curated version of it. Whether the contract's accountability mechanisms are being used or politely avoided.

It looks like an examination that covers the ground where programmes actually fail. Plan integrity and the honesty of the critical path. Vendor and integrator accountability. Data readiness, which surprises more go-lives than any other single factor. The health of the business case the programme was funded against. And the condition of the client-side organisation itself, because the weakest voice in most steering rooms is the one paying for everything.

And it looks like findings a sponsor can act on. Not a sixty-page deck. A written position, evidenced, with the material findings ranked and a clear line between what must change and what can wait. The test of good assurance is not the thoroughness of the examination. It is whether the sponsor knew something on Friday that they did not know on Monday, and knew it in time to act.

It looks like continuity. A single health check tells you where the programme stands on the day it was examined. Complex programmes drift between examinations, which is why assurance on the hardest programmes is moving from a point-in-time exercise to a continuous discipline, examining evidence as the programme produces it.

We have built our practice around exactly this discipline. Our Project Health Check applies a structured, evidence-based examination across the dimensions where programmes actually fail, and Continuous Programme Assurance extends the same discipline across the life of a programme rather than a moment in it. The mechanics matter less here than the principle. Assurance is examination by a party with nothing at stake in the answer, against a standard, on evidence.

What it is not also matters. Assurance is not a second delivery team. It does not slow the programme, because it does not sit in the delivery path. It is not a verdict on the people. The most common finding of an independent health check is not incompetence. It is capable people working inside structures that hide the true position from everyone, including themselves.

Three tests that separate assurance from reporting

Plenty of things get called assurance that are not. If you are a sponsor weighing what your programme actually has, three tests settle it.

Independence. Does the party doing the examining have any stake in the examination's answer? A review run by the delivery partner is a progress report. A review run by the firm hoping to sell the recovery is a sales call. Assurance requires a party whose commercial position does not move whichever way the findings fall.

Standard. Is the programme being examined against defined criteria, or against the reviewer's impressions? Professional audit works because the standard exists before the engagement does. An assurance review should be able to show you, in advance, what it examines and what good looks like.

Evidence. Do the findings trace to artefacts, or to interviews alone? Conversations matter, but a position built only on what people said is a position built on the same filtered information the steering committee already receives. Real assurance reads the plan, the registers, the contracts and the data, and tests what it was told against what it found.

A review that passes all three is assurance, whatever it is called. A review that fails any one of them is reporting with better stationery.

Why this is landing now

The timing of the government's conclusion is not accidental, and the forces behind it apply with equal weight to the private sector.

Programmes have become genuinely harder. An ERP or HRIS implementation today is a web of platform vendors, integrators, data migrations, integrations and compliance obligations that did not exist a decade ago. Complexity has outgrown the informal governance that used to be just enough.

The capability market has tightened. Experienced programme leadership is scarce, and organisations increasingly cannot assume the competence they need exists in-house. The Defence strategy treats that scarcity as a national risk. A CFO staring at a once-a-decade implementation should treat it as a programme risk.

And the tolerance for surprise has collapsed. Boards that have watched a public programme fail in the press, or lived through a private one that landed late and over budget, are no longer satisfied with being told the programme is fine. They want to know how anyone would know.

That last question is the whole argument. On a programme without independent assurance, there is no good answer to it.

The question to ask

The Australian government has now said it twice. Complex delivery is a profession, with recognised competence and structured standards. We agree, and we would push the logic one step further than the strategies do.

Every profession earns trust through independent examination. Delivery should not be the exception, least of all on the programmes where the money is largest and the surprises are most expensive.

So ask the question of your own programme. Is it being assured, or merely reported on? And if the answer is reported on, ask who in the structure is positioned to tell you the true position, and what it would cost you to hear it late.