Skip to content

How Much Assurance Is Proportionate?

Proportionate assurance is not the smallest review that can be commissioned. It is the minimum credible scrutiny needed to protect the consequence of a client decision.

Six factors determining assurance depth: decision consequence, irreversibility, supplier dependence, evidence uncertainty, client capacity and delivery complexity.

Key judgement

Too little leaves material claims untested. Too much creates a second delivery structure, increases cost and can weaken accountability.

The operational problem

Review scope is often based on programme budget, available time or a standard checklist. Those factors do not define exposure. A smaller payroll change can threaten critical operations. A large programme may need only a focused review where strong controls and independent client capability already exist.

Proportionality should be determined by decision consequence, evidence uncertainty, supplier reliance, control maturity, complexity, time remaining and the client’s assurance capacity.

Seven proportionality factors

FactorLower intensityHigher intensity
ConsequenceReversible with contained impactCritical operations or irreversible commitment
EvidenceCurrent, traceable and consistentMissing, contradictory or filtered
Supplier relianceStrong client-held source evidenceSupplier controls evidence and interpretation
Control maturityEstablished and demonstrably operatingNew, unstable or repeatedly bypassed
ComplexityFew interfaces and bounded dependenciesMultiple suppliers, integrations or migrations
Time pressureOptions and remediation time remainDecision window or contingency closing
Client capabilityIndependent specialists have capacityNo assurance team or material skills gap
Four proportionate assurance levels: targeted check, focused review, full assurance and continuous oversight.

Four assurance levels

LevelSuitable useOutput
Targeted challengeOne claim or concern with contained consequence.Short confidence note with evidence gaps or conditions.
Decision reviewMaterial gate, investment, acceptance or go-live.Bounded opinion, findings and decision conditions.
Health and viability reviewConnected concerns across workstreams.Integrated viability opinion and prioritised intervention.
Staged assuranceRepeated high-consequence decisions in complex delivery.Evolving confidence, independent escalation and closure verification.

Scoping mechanics

1. Define consequence

2. Assess uncertainty

3. Select domains

4. Set evidence depth

5. Fix review window

Follow the decision across boundaries

A go-live review may need migration and cutover evidence, quality evidence and operational evidence without reassessing every programme control. A recovery review may focus on schedule logic, capacity, supplier commitments and governance, adding technical depth only where those claims depend on it.

Choose evidence depth

Use defensible sampling where the population is controlled. Examine the full set where a small number of critical items determine the outcome, such as unresolved critical defects, decision triggers or material reconciliation exceptions.

Commissioning decision table

QuestionIf noIf yes
Is the decision and consequence clear?Clarify the mandate.Identify claims that must be true.
Do existing controls provide reliable evidence?Increase direct evidence work.Reuse and test the records.
Is client challenge independent and capable?Add specialist coverage.Avoid duplicating competent controls.
Could one domain invalidate the decision?Use risk-based sampling.Examine that domain to sufficient depth.
Will findings remain actionable?Reconsider timing or state limitations.Fix the review and closure window.

Stopping rules

  • Expand when evidence reveals a connected systemic failure.
  • Narrow when reliable controls already answer the decision question.
  • Stop collecting when more volume will not change the judgement.
  • Do not compress below the depth needed to test a material claim.
  • Where time prevents sufficient work, report Insufficient Evidence rather than imply confidence.

Application by client context

ContextAssurance focus
Central GovernmentEvidence for SRO and programme board decisions, multi-supplier dependency, major approvals and public accountability.
Local GovernmentCitizen service continuity, supplier challenge and proportionate scrutiny without creating a permanent council function.
SMEProtection of investment and operations where the technology supplier holds most technical knowledge and evidence.

The consequence for client governance

The supplier remains responsible for delivery and for producing the evidence behind its claims. The client retains accountability for approval, acceptance and residual risk. Enigma’s independent assurance method gives that client a defensible basis for deciding what to rely on, what to condition and when to intervene.

Related Enigma framework pages

Independence boundary

No practitioner independently assures delivery that they directly own. Delivery support, management action and independent verification must be separated and disclosed.