Governance & closure
Phase 5 happens after go-live. It closes the loop between what was designed and what was actually built, then seals the record.
Post-go-live validation
Section titled “Post-go-live validation”A three-panel checklist:
- Problem outcomes — were the Phase 1 framing objectives and success criteria met?
- Implementation plan — were the committed recommendations actually delivered? (Each is toggled in or out of scope.)
- Residual gaps — anything still open, recorded for a follow-on engagement.
Saving the validation is one of the closure-readiness checks.
Closure-readiness checks
Section titled “Closure-readiness checks”Phase 5 shows eight checks: deliverables approved, gap register approved, recommendation set approved, implementation plan committed, all conflicts resolved, post-go-live validation saved, and the two sign-offs. Only the dual sign-off is a hard gate — the other six are informational, there to tell you whether the engagement is genuinely finished. Don’t close on the strength of the gate alone if the informational checks are red.
The dual sign-off
Section titled “The dual sign-off”Closing requires two sign-offs from the client side:
- the client’s EA lead, and
- the client’s executive sponsor.
eavantage checks each signer’s actual role on the engagement before recording their sign-off — a person can’t sign off in a role they don’t hold.
Closing the engagement
Section titled “Closing the engagement”- A consultant or engagement lead submits a closure request; a platform administrator approves it.
- A platform administrator can close the engagement directly.
Either way, you type the engagement ID into a confirmation modal to proceed.
On closure
Section titled “On closure”- Deliverables and templates are locked.
- The audit trail is sealed — it was append-only throughout; now it’s read-only.
- Standards, patterns, and playbook entries proven out during the engagement can be promoted into the standards library for the next engagement (as nominations a platform administrator approves).
An on-demand graph integrity check (orphaned, duplicated, or mis-nested elements) is available at any point during the engagement — run it before sign-off if you want the model confirmed internally consistent.