What a project assurance review actually measures

The question a project assurance review answers is not 'is this project on track?' That question has already been answered — by the project team, in the status report, in the steering committee presentation. The answer is always 'broadly on track, with some areas of concern.'

The question a project assurance review answers is: does this project have a credible path to completion? Not a theoretical path. Not a path that depends on everything going right from this point forward. A credible path — one that accounts for the current state of the project, the current capability of the team, the current relationship with the vendor, and the current appetite of the organization to absorb further cost and delay.

To answer that question, a project assurance review examines ten dimensions. Schedule and delivery. Budget and cost control. Leadership and accountability. Communication and reporting. Risk and issue management. Governance and decision-making. Team and capability. Stakeholder and supplier alignment. Data integrity and transparency. Recovery readiness.

Each dimension is assessed independently. Each dimension produces a score. The scores are aggregated into a single Project Score — a number from 0 to 100 that represents the overall health of the project across all ten dimensions.

The Project Score is not a prediction. It is a diagnosis. A Project Score of 35 does not mean the project will fail. It means the project has significant weaknesses across multiple dimensions — and that without intervention, the probability of failure is high.

The value of the Project Score is not the number. It is the conversation the number enables. The executive who receives a Project Score of 35 can have a very different conversation with the project team than the executive who receives a status report that says 'broadly on track, with some areas of concern.'