Supplier challenge is most valuable when the client needs to test whether reported progress, recovery claims or milestone confidence are actually supported by evidence.
Enigma provides independent client-side supplier challenge for technology programmes. The purpose is not to second-guess delivery management or create parallel governance. It is to give the client an evidence-based view of whether supplier claims can be relied upon for the next material decision.
When independent supplier challenge is needed
- Reported status is stronger than the underlying evidence appears to justify.
- Milestones are repeatedly re-baselined without clear evidence that the underlying constraint has changed.
- Recovery plans contain activity but do not demonstrate restored deliverability.
- Supplier testing, migration or readiness claims are being used to support a client acceptance decision.
- Dependencies, defects or exceptions are being managed individually while cumulative exposure remains unclear.
- The programme board needs an independent basis for deciding whether to accept, condition or reject a supplier position.
The buyer problem
The client remains accountable for the consequences of accepting a supplier milestone, recovery plan or readiness statement. Supplier reporting is an important input, but it is not independent assurance. The key question is whether the evidence supports the conclusion being presented.
This distinction is central to Supplier Delivery Assurance and the wider How We Assure model.
What Enigma examines
- Milestone evidence: whether stated completion is backed by objective exit evidence rather than activity or elapsed time.
- Schedule credibility: whether critical dependencies, resource assumptions and remaining work support the forecast date.
- Testing and quality: whether supplier test evidence is representative, traceable and sufficient for client decisions.
- Defects and exceptions: whether unresolved exposure is understood individually and cumulatively.
- Data and migration: whether migration, reconciliation and exception controls support the claimed readiness position.
- Recovery plans: whether proposed actions change the constraints that caused the problem or merely move dates and actions.
- Operational readiness: whether support, access, monitoring, procedures and dependencies are ready for the claimed transition point.
- Governance evidence: whether risks, assumptions, decisions and acceptance conditions are explicit and owned.
Where the dominant concern is quality evidence, see Quality and Test Assurance. For migration and cutover exposure, see Data Migration and Cutover Assurance. For distressed delivery, see Programme Health Checks and Recovery.
Evidence before acceptance
The Evidence Sufficiency Standard is used to distinguish supported claims from assertions. Enigma tests whether the evidence is current, attributable, representative and sufficient for the decision the client is being asked to make.
Typical source evidence includes integrated plans, dependency logs, test evidence, defect records, migration results, reconciliation outputs, acceptance criteria, RAID records, recovery plans, operational readiness evidence and supplier commitments.
Challenge without duplicating governance
Independent supplier challenge should not become another programme-management layer. The programme and supplier remain responsible for delivery. Enigma tests the reliability of the evidence, highlights unsupported assumptions and identifies the consequence for the client decision.
The boundary is defined in the Independence and Conflict Standard. Enigma does not independently assure delivery its practitioners directly own.
Decision conditions and closure
Where evidence is incomplete but the client may still be able to proceed conditionally, the Decision Condition Framework converts uncertainty into explicit conditions with owners, evidence requirements, dates and closure authority.
A condition is not closed because an action is marked complete. The Closure Verification Standard requires evidence that the underlying condition has actually changed.
Typical outputs
- an independent view of whether supplier claims are supported by evidence;
- material gaps, contradictions and unsupported assumptions;
- milestone or recovery-plan credibility findings;
- cross-workstream exposure not visible in individual status reports;
- explicit decision conditions and residual risks;
- closure verification where material conditions must be tracked.
When to commission supplier challenge
The best time is before a supplier claim becomes a client commitment. This can be before milestone acceptance, contract variation, recovery-plan approval, entry to UAT, migration approval or go-live. The earlier the evidence is tested, the more opportunity the client has to act on the result.
For practical evidence requests, use the Resources library. For engagement structure, see Engagement Models. To discuss a defined supplier decision, start an assurance conversation.