Skip to content

G7 · Acceptance

Does the solution do what the business needs?

Source: Stage-Gate®; PRINCE2® stage boundaries; ISO 21502 governance
Level: B · established practice

Evidence

UAT scriptscriticaldepends on context

Acceptance criteriacriticaldepends on context

Test reportcriticaldepends on context

UAT sign-off recordcriticalany context

Defect logcriticaldepends on context

Defect logrequireddepends on context

Process pilot reportcriticaldepends on context

Site inspection record and snag listcriticaldepends on context

Operational readiness report (OAT)criticaldepends on context

Training materialsrequiredwaivabledepends on context

Change logrequireddepends on context

Trial load reportcriticaldepends on context

Reconciliation with the system of recordcriticaldepends on context

Checks

No open critical defects
Acceptance criteria verified by business users
Verified end to end by the owners of consuming systems

How the gate runs

Predictive: Phase gate: held once, at the end of the stage.
Agile (iterative): Rolling gate: held per release; item readiness via Definition of Ready, completion via Definition of Done.
Flow (Kanban): Policy gate: explicit exit policies on the board columns, applied to every item.
Hybrid: Phase gate per phase, with iterations or flow inside the phase.

For agents · MCP

explain_node({ "id": "g.g7" })