Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Project management and PMO

Project audit: an independent assessment and a recovery plan

When the indicators and the corridors no longer tell the same story, you need facts. We establish the actual state of the project, what put it there and what you can still decide.

Our principles

  • Cross-checked findings, verified against evidence
  • Decision options, not an inventory of defects
  • A recovery plan the team can carry out
In brief

A project audit is an independent, time-boxed review that establishes the actual state of a project or programme, the causes of its difficulties and the options that remain open. Management Square conducts it on a troubled project or before a commitment milestone, and concludes it with substantiated findings, a recommendation and a recovery plan that can be applied.

Scope

How we contribute

  1. Scoping the audit

    Terms of reference agreed with the sponsor: questions the audit must answer, scope, access to people and documents, confidentiality rules, reporting format.

  2. Document review and verification

    Analysis of the investment case, schedules, budget, contracts, backlog and defect logs, supplemented by direct checks on what is actually delivered.

  3. Cross-interviews

    Individual discussions with the sponsor, project management, the teams, the business and suppliers. Statements are not attributed, so as to obtain candid input.

  4. Root cause analysis

    Distinction between symptoms and causes, based on facts confirmed by at least two sources. A delay is a symptom: the audit looks for the decision, or the lack of a decision, that explains it.

  5. Reporting and recommendation

    Presentation of the findings to the project team, then to the sponsor, with the open options (continue, refocus, suspend, stop) and their consequences.

  6. Recovery plan

    Immediate measures, a reset trajectory, tightened governance and conditions for success, with, if you wish, a follow-up review after implementation.

Page contents

When a project audit becomes necessary

A project audit is rarely requested light-heartedly. It comes when management has lost confidence in the information it receives. Committee meetings follow one another, the indicators have been amber for months, each postponement is presented as the last. In the corridors, people hear a different version from the one in the dashboards.

Internal monitoring is no longer enough, for reasons that have nothing malicious about them. The project manager has an interest in believing in the recovery. The supplier defends its reading of the contract. The teams have said what they knew, sometimes several times, to no effect. The sponsor has staked their credibility. Everyone holds part of the facts, and nobody is in a position to piece them together without being suspected of pleading their own case.

The other moment is less dramatic and just as useful: the eve of a commitment. Before voting a delivery budget, signing with an integrator or authorising a cutover, an outside view checks that the project is ready and that the risks are known to those who decide.

Health check, milestone audit, recovery audit

The word “audit” covers three exercises that do not answer the same question. Confusing them leads to commissioning work that is too heavy, or too light.

Type of review Trigger Question asked Expected result
Health check Programme calendar, with no particular alert Does the project present risks that routine monitoring does not show? Points of attention and preventive actions
Milestone audit Upcoming commitment decision Is the project ready to pass this stage? Reasoned opinion, reservations and prerequisites
Recovery audit Project clearly off track Can the project still achieve its objective, and under what conditions? Decision options and recovery plan

The rest of this page describes the most comprehensive case, that of recovery. The other two use the same method, on a reduced scope.

The scope: seven angles of examination

A project almost never goes off track for a single reason. We examine it from seven angles, scaling the effort to the questions in the terms of reference.

  • The rationale. Is the objective still valid? Do the expected benefits justify the remaining cost, and not the cost already incurred?
  • Governance. Who decides, and are the decisions requested actually made? Many delays are decisions on hold.
  • Scope. Are the requirements stable, and who has the power to refuse a new request?
  • The schedule. Is the remaining work estimated by those who will carry it out? Is the critical path identified?
  • Budget and contracts. What remains to be spent, and what do the suppliers’ commitments actually say?
  • The solution. Can the architecture handle the planned load, and what is the state of the quality delivered? When these points require in-depth examination, we draw on our skills in information system architecture and software quality.
  • The people. Does the team have the necessary skills and availability? Are the future users waiting for the result?

The method: cross-check, verify, confront

The value of an audit lies in the soundness of its findings. Three principles guide our work.

Cross-checking. No finding rests on a single source. A statement heard in an interview is confirmed by a document, a measurement or a second independent account; otherwise it is presented as a perception.

Verifying against evidence. We do not stop at committee minutes. We look at the backlog and the defect log, we ask for a demonstration of what works, we redo the calculation of the remaining work based on the pace actually observed.

Confronting. The findings are presented to the project team before being reported to the sponsor. The team can correct an error of fact or provide a missing element. The conclusions, however, remain ours.

Interviews are individual and statements are not attributed. This rule is announced at the launch, by the sponsor themselves.

Reporting and the recovery plan

Reporting comes in three stages: what we observed, what explains it, what you can decide. The options are always presented with their consequences in terms of time, cost and risk.

  • Continue with limited adjustments, when the difficulties are contained.
  • Refocus the scope, the trajectory or the team, when the objective remains valid but the plan no longer is.
  • Suspend for the time needed to remove a prerequisite: an architecture decision, a renegotiation, a business decision.
  • Stop, when the remaining cost exceeds the expected value. This is a legitimate option, which the audit must make it possible to put forward.

If the project continues, the recovery plan sets the measures for the first weeks, a trajectory reset on verifiable milestones and tightened governance for the duration of the recovery. On a programme, its implementation falls within programme management.

The pitfalls we help you avoid

  • The audit without a sponsor. If nobody has the power to act on the conclusions, the report joins the previous ones. We check this point before accepting the scoping.
  • The trial. Looking for a culprit guarantees defensive answers and deprives the audit of its best sources.
  • The paper audit. Checking that documents exist says nothing about the state of the project. A test plan can be complete and the tests can still fail.
  • The encyclopaedic report. A long list of findings of equal weight allows no decision. A few major causes, ranked, are more useful.
  • Reasoning on sunk costs. What has been spent does not justify continuing. Only the remaining cost and the value still achievable count.

What shows that an audit has been useful

The first sign is immediate: an explicit decision is taken at the end of the reporting, and it is dated. An audit followed by a request for further analysis has often missed its target.

The other signs can be observed in the months that follow. The milestones of the recovery plan are met, or any deviation is reported without delay. Decisions that were on hold have been made. The project’s forecasts stop slipping from one committee to the next. Finally, the team considers that the report describes its situation accurately, which conditions everything else. When the audit reveals a lasting weakness in monitoring, the natural next step is strengthening the project management office.

Typical work

What our consultants contribute to

Terms of reference

Questions asked, scope, timetable, contacts and ground rules of the audit, signed by the sponsor.

Audit report

Findings ranked by severity, facts supporting them, root cause analysis and a reasoned recommendation.

Decision note

Short summary for the executive committee: actual state, options, consequences of each, decision requested.

Recovery plan

Actions, owners, control milestones and indicators that will make it possible to check that the project is recovering.

Insights

Further reading

All insights
Before an acquisition, the questions an IT due diligence asks of the target's information system

An IT due diligence, or acquisition audit of the information system, examines before an acquisition or an equity investment the state of the applications, dependencies, security, contracts and the system's capacity to be integrated or separated. Management Square presents here an investment committee's questions on these subjects, the evidence to request and what each answer changes in the transaction.

Read the analysis
When to hold a project lessons-learned review, and when to forgo it

A project lessons-learned review is the examination, by those who took part in it, of what a project or a phase teaches for the future: end-of-project review, retrospective in an agile approach, post-incident review. Management Square offers a decision guide here: when to hold it, what to focus it on, whom to bring together, which conclusions to keep and to whom to entrust the follow-up, and when to forgo it.

Read the analysis
Why do IT projects fail? A reading through the signs of drift

An IT project fails, under the convention adopted here, when it misses its deadline, its cost, its scope or the expected benefit beyond the variance its sponsor had accepted. Rather than a list of causes, Management Square offers a reading method here: the observable signs of drift at each stage of the project, what each one can reveal and the response it calls for.

Read the analysis

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is a project audit?

A project audit is an independent, time-limited examination of the situation of a project or programme. It answers questions set in advance by a sponsor: where the project actually stands, why, and what can be decided. It differs from routine monitoring through the independence of the person conducting it and the verification of information at its source.

When should a project audit be triggered?

In two situations. The first is the troubled project: repeated postponements, budget consumed without visible delivery, tensions with a supplier, departures from the team. The second is the approach of a commitment milestone, such as an investment decision, a phase change or a go-live, when management wants an outside opinion before committing.

How long does a project audit take?

The duration depends on the scope, the number of people to be met and the availability of documents. An audit remains short by design, because its value decreases as the project continues to move forward without a decision. The timetable is set in the terms of reference, with a firm reporting date.

How does the project team experience an audit?

It all depends on how the audit is announced and conducted. Presented as a search for those responsible, it closes doors and distorts answers. Presented as a way of obtaining decisions that the team has sometimes been waiting for for a long time, it is usually well received. We always present our findings to the team before presenting them to the sponsor.

Can the auditor then lead the recovery?

The decision belongs to the sponsor. The recovery plan is written to be carried out by the team in place or by any other party, without depending on us. If a follow-on engagement is entrusted to us, this possibility is raised openly at the scoping stage, so that it does not weigh on the conclusions.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.