Go-Live Approval / Sign-Off Workflow

ERPWeb Test Client — Test Odoo 16 to 19 Upgrade — Odoo 16 to Odoo 19

Back to Project Readiness Dashboard Go-Live Execution Client Handover / Hypercare Project Close-Out / Archive Upgrade Run Log Odoo.sh Workflow Action Plan Dashboard
APPROVALS PENDING

0/3 Required Approvals Positive

Final human sign-off is not complete yet.

Readiness decision: NOT READY · Readiness score: 33%

Production Go-Live Execution Runbook

EXECUTION NOT COMPLETE

Required blocking execution steps still need to be completed before go-live can be considered complete.

Closed: 0/10 · Blocking open: 7 · Rollback/no-go decisions: 0

Open production go-live execution checklist / runbook

Client Handover / Hypercare Tracker

HANDOVER IN PROGRESS

Required client handover or close-out blocking items are still open.

Closed: 0/7 · Close-out blockers: 6 · Blocked: 0

Open client handover / hypercare tracker

Project Close-Out / Archive Summary

CLOSE-OUT NOT READY

Close-out cannot be completed until the remaining blockers are resolved.

Blockers: 5 · Final report: Not Started · Archive: Active / Not Archived

Open project close-out / archive workflow

Client Approval

Pending

Final Go/No-Go Decision

Pending

Final decision: Not Set

Internal ERPWeb Approval

Pending

Approval History

Type Status Decision Approver Signed Updated
Client Approval Pending Not Set Not captured
Client Decision Maker / UAT Owner 		- May 11, 2026, 7:03 p.m.
Final Go/No-Go Decision Pending Not Set Not captured
ERPWeb Final Go-Live Owner 		- May 11, 2026, 7:03 p.m.
Internal ERPWeb Approval Pending Not Set Not captured
ERPWeb Project Lead / Technical Lead 		- May 11, 2026, 7:03 p.m.

ERPWeb Approval Rule

Go-live should only proceed when the readiness dashboard is acceptable and all three approval records are positive: internal ERPWeb approval, client approval, and final GO or conditional GO decision.

NO-GO / rejected / revoked means the upgrade must not proceed until the approval is corrected and the reason is documented.