Required blocking execution steps still need to be completed before go-live can be considered complete.
Readiness: NOT READY · Approval: APPROVALS PENDING
HANDOVER IN PROGRESS
Required client handover or close-out blocking items are still open.
Closed: 0/7 · Required open: 7 · Close-out blockers: 6
Continue to client handover / post-go-live hypercare tracker
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
Pre-Go-Live Check Blocks Go-Live Not Started
Confirm internal ERPWeb approval, client approval, and final go/no-go decision are captured before starting production execution.
Owner: ERPWeb Project Lead
Expected result: Go-live approval workflow is approved or conditionally approved with accepted conditions.
Pre-Go-Live Check Blocks Go-Live Not Started
Confirm the latest production database backup, filestore backup, and restore plan are available before production upgrade starts.
Owner: ERPWeb Technical Lead
Expected result: Backup references are captured and rollback restore path is known.
Trigger: No reliable backup or restore path is available.
Action: Stop go-live and reschedule after backup/restore readiness is confirmed.
Pre-Go-Live Communication Not Started
Notify client stakeholders that the go-live window is starting, including expected downtime and escalation channel.
Owner: Communication Owner
Expected result: Stakeholders are informed before production work starts.
Go-Live Execution Action Blocks Go-Live Not Started
Prevent normal users from continuing work during the production upgrade window according to the agreed client plan.
Owner: ERPWeb Technical Lead
Expected result: Users are safely stopped from creating new production transactions during the upgrade.
Trigger: Users cannot be stopped safely or business refuses downtime.
Action: Stop execution and return production to normal operation.
Go-Live Execution Action Blocks Go-Live Not Started
Execute the approved Odoo upgrade procedure using the agreed production path.
Owner: ERPWeb Upgrade Owner
Expected result: Production upgrade completes without blocking errors.
Trigger: Upgrade fails with unresolved blocking error inside the rollback window.
Action: Start rollback procedure using confirmed backup and rollback owner approval.
Post-Go-Live Validation Validation Blocks Go-Live Not Started
Confirm users can access the upgraded production database and the main Odoo menus load correctly.
Owner: ERPWeb Functional Lead
Expected result: Login and core navigation work in production.
Trigger: Users cannot log in or the main application is unusable.
Action: Escalate to rollback decision point.
Post-Go-Live Validation Validation Blocks Go-Live Not Started
Validate agreed critical flows such as sales, purchasing, inventory, accounting, barcode, website, integrations, and reports as applicable.
Owner: ERPWeb Functional Lead / Client UAT Owner
Expected result: Critical business flows are confirmed working or accepted with documented conditions.
Trigger: A critical flow fails and no acceptable workaround exists.
Action: Escalate to rollback decision point.
Rollback Decision Point Decision Blocks Go-Live Not Started
Make a clear continue-or-rollback decision based on execution result, validation results, remaining window, and client/business impact.
Owner: Rollback Owner
Expected result: Decision is captured as Continue, GO, Rollback, or NO-GO.
Trigger: Blocking validation failure, unacceptable business risk, or rollback window limit reached.
Action: Execute the agreed rollback plan and communicate status.
Post-Go-Live Support Communication Not Started
Notify stakeholders of go-live result, known accepted issues, support process, and next monitoring window.
Owner: Communication Owner
Expected result: Stakeholders know the go-live outcome and support path.
Post-Go-Live Support Validation Not Started
Monitor the system after go-live and confirm support ownership for the hypercare period.
Owner: ERPWeb Support Lead
Expected result: Hypercare monitoring is active and support ownership is clear.
Do not treat go-live as complete until all blocking execution steps are closed and the rollback decision point is captured as GO or Continue.
Rollback / NO-GO / failed / blocked means the production upgrade must be reviewed before continuing.