Go-live is not a project milestone to be achieved because the date has arrived. It is a client decision to transfer technology and delivery risk into live operations.
Enigma provides independent client-side go-live assurance. We test whether the combined evidence from testing, defects, data migration, interfaces, security, operations, cutover and business readiness is sufficient for accountable leaders to make a defensible decision. We do not replace the programme team, delivery supplier or business owners, and we do not make the executive decision on their behalf.
The go-live assurance problem
Most programmes approach go-live with large amounts of evidence but no single control that proves readiness. Test completion does not by itself establish acceptable residual risk. A migration rehearsal does not prove that production data will reconcile. A detailed cutover plan does not prove that dependencies, decision points and rollback criteria are executable. Supplier confidence is relevant, but it is not independent assurance.
The governance problem is therefore integration. The client must decide whether the combined position is sufficiently understood, evidenced and controlled to accept the operational consequence of proceeding.
What independent go-live assurance examines
- Testing and coverage: whether critical business processes, integrations and non-functional obligations have been exercised under representative conditions.
- Defects and residual quality risk: whether unresolved defects are understood individually and cumulatively, with explicit treatment and accountable acceptance.
- Data migration and reconciliation: whether completeness, correctness, transformation, exceptions and business reconciliation are evidenced.
- Interfaces and dependencies: whether upstream, downstream, supplier and operational dependencies are demonstrably ready.
- Security and access: whether material security, identity, access and control obligations required for operation have been addressed.
- Operational readiness: whether support, monitoring, procedures, ownership, escalation and early-life arrangements can operate from day one.
- Business readiness: whether accountable business owners understand the change, outstanding exposure and conditions attached to acceptance.
- Cutover and rollback: whether sequencing, responsibilities, checkpoints, decision authority, contingency and rollback criteria are executable.
Where the dominant exposure is quality evidence, see Quality and Test Assurance. For migration and transition risk, see Data Migration and Cutover Assurance. Supplier evidence and delivery claims can be examined through Supplier Delivery Assurance.
Evidence before confidence
Enigma follows the evidence-to-decision model described in How We Assure. Evidence is assessed for sufficiency, not merely existence. A document, dashboard or completed action is not treated as proof unless it demonstrates the condition that governance needs to rely upon.
- Define the decision. Establish the proposed production commitment, its consequence and the accountable decision authority.
- Set the readiness baseline. Identify the controls, acceptance criteria, dependencies and evidence required to support that decision.
- Test the reported position. Compare programme and supplier claims with source evidence.
- Integrate exposure. Assess cross-workstream dependencies and cumulative residual risk rather than reviewing each issue in isolation.
- Set decision conditions. Define what must be resolved, evidenced, mitigated or consciously accepted before progression.
- Verify closure. Confirm that material conditions have actually changed rather than simply being marked complete.
What a defensible go-live decision requires
A defensible decision does not require every issue to be closed. It requires every material issue to have an explicit treatment and a decision owner. The board should be able to distinguish:
- Resolved: evidence demonstrates that the underlying condition has been removed.
- Mitigated: exposure remains but an evidenced control reduces its consequence or probability.
- Accepted: the accountable client owner understands and consciously accepts the residual risk.
- Blocking: the evidence is insufficient or the exposure exceeds the client’s stated tolerance for progression.
This prevents schedule pressure from converting unresolved uncertainty into implicit acceptance.
Typical evidence set
- phase exit criteria and evidence of satisfaction;
- end-to-end, regression, UAT and non-functional test results;
- defect position, ageing, severity, business impact and workarounds;
- migration rehearsal outcomes, reconciliation controls and unresolved exceptions;
- interface readiness and dependency evidence;
- security, access and operational control evidence relevant to launch;
- support model, monitoring, incident routes and early-life support arrangements;
- business readiness and acceptance evidence;
- cutover plan, command structure, checkpoints, contingency and rollback criteria;
- open risks, assumptions, decisions and explicit residual-risk owners.
Decision outputs
The output is not another readiness dashboard. It is an independent assurance position tied to the decision.
- an executive conclusion on the sufficiency of the readiness evidence;
- material findings and cross-workstream exposure;
- explicit evidence gaps and unsupported claims;
- decision conditions with owners, evidence standards and closure authority;
- residual risks requiring conscious client acceptance;
- verification of material closure conditions where required.
The independence boundary
The delivery supplier remains responsible for delivery. The programme remains responsible for integration and management. Business and operational owners remain accountable for acceptance within their areas. Enigma remains separate from those responsibilities and does not independently assure work its practitioners directly own. This boundary is defined in the Independence and Conflict Standard.
When to commission go-live assurance
Independent assurance is most valuable early enough for the evidence to change the decision or the delivery response. It should not be treated as a ceremonial review immediately before production. The review can begin while testing, migration and operational readiness are still progressing, with material decision conditions tracked through to the final go-live point.
It is particularly relevant where a date is commercially or operationally difficult to move, supplier and client confidence differ, significant defects or migration exceptions remain, previous milestones have slipped, recovery activity is still open, or the programme board needs an independent basis for accepting residual risk.
Practical decision material is available through Resources. The broader independent assurance model is described under Advisory Services.