Procurement Maturity Assessment
An evidence-led assessment example
Fictional worked example. All organisations, transactions, scores and comparison figures in this report are illustrative. This is not customer data or a current market benchmark.
Assessment overview
A simple scoring method with the assumed evidence visible.
The current score is the arithmetic mean of six fictional dimension scores. The target is a proposed management objective. This sample does not claim a peer percentile, a database of assessments or a verified client outcome.
Scores and evidence
Each score should be supported by records, interviews and a stated assessment scope.
Capability today and the proposed target
| Dimension | Current score | Proposed target | Assumed evidence and gap |
|---|---|---|---|
| Governance | 2 | 4 | Owners named, but approval rules applied inconsistently |
| Spend visibility | 3 | 4 | Monthly spend view exists; reconciliation needs review |
| Category planning | 2 | 3 | Plans cover only selected priority categories |
| Supplier management | 3 | 4 | Scorecards exist for strategic suppliers |
| Contract management | 2 | 3 | Repository exists; renewal ownership is incomplete |
| Buying controls | 3 | 3 | Guided channels exist; exception review is manual |
Current mean: (2 + 3 + 2 + 3 + 2 + 3) ÷ 6 = 2.5. Target mean: (4 + 4 + 3 + 4 + 3 + 3) ÷ 6 = 3.5. Equal weights are an assumption in this example; a different weighting must be agreed and disclosed.
| Score | Evidence expected |
|---|---|
| 1 | No repeatable process evidenced |
| 2 | Some practices exist, applied inconsistently |
| 3 | A defined process is used across the agreed scope |
| 4 | Process performance is measured and reviewed |
| 5 | Measured improvements are sustained across review cycles |
Missing evidence should be recorded as unassessed rather than automatically given a low score. Agree the rubric before collecting responses.
Prioritised improvements
Start with the three dimensions scoring 2 in this scenario.
| Priority | Action | Owner | Evidence required |
|---|---|---|---|
| Governance | Document approval thresholds and review exceptions | Procurement lead | Approved policy and sampled decisions |
| Category planning | Build plans for agreed priority categories | Category leads | Plans linked to spend, contracts and business needs |
| Contract management | Confirm owners and renewal notice dates | Contract owners | Reviewed register and documented renewal decisions |
A maturity score describes process capability. It does not establish a savings amount. Any financial business case needs its own transaction baseline, costs, assumptions and Finance review.
Review cycle
Separate proposed improvements from demonstrated progress.
Show progress with evidence
- Agree the starting point First 30 days · resolve missing evidence
- Commit to actions Days 31–60 · name owners and resources
- Check adoption Days 61–90 · sample real decisions
- Reassess consistently Months 6–12 · use the same scope and rubric
| When | Activity | Output |
|---|---|---|
| First 30 days | Validate evidence with process owners | Agreed current assessment and missing-data list |
| Days 31–60 | Assign actions, resources and review dates | Approved improvement plan |
| Days 61–90 | Sample whether the revised process is being used | Evidence of adoption and unresolved gaps |
| After 6–12 months | Reassess using the same scope and rubric | Comparable scores with supporting records |
Interview responses, transaction records and policy documents may disagree. Record those differences and resolve them with the owner before finalising an assessment.