ERP Migration & SelectionFree templatePDF, Excel, Word export

ERP Go/No-Go Decision Record Template (Criteria, Evidence, Sign-Off)

The go/no-go meeting is where evidence replaces optimism. This record lists the criteria, the evidence behind each, any conditions, and who signed.

Fill in

Project

Decision meeting date

Planned go-live date

Decision

Open blocker defects

Open major defects

UAT pass rate

Conditions for go

Rollback trigger and deadline

Live preview

Download:

ERP Go/No-Go Decision Record Template

Go/No-Go Decision Record

Project: Plant 1 ERP Replacement Decision meeting: 2026-11-20 Planned go-live: 2026-11-30 Decision: Conditional go

Readiness criteria

Criterion	Evidence	Status	Owner
UAT exit criteria met	94 percent of scripts passed
Open blocker defects	0
Open major defects	3
Data migration reconciled
Interfaces tested end to end
Security roles approved
Users trained
Support model staffed
Rollback plan tested

Conditions attached to the decision

All three open major defects closed or covered by signed workarounds by 25 November. Final mock cutover completed within the planned window.

Rollback trigger

Rollback to legacy if opening inventory reconciliation fails by more than the agreed tolerance and cannot be corrected by Sunday 18:00.

Sign-off

Project manager / Date

Business process owners / Date

IT lead / Date

Executive sponsor / Date

Adapt the criteria to your project. A decision record documents accountability; it does not replace a tested cutover plan.

Pre go-live readiness review

Walk your criteria with a delivery practitioner before the decision meeting.

Optional. The tool and every export work without this. No spam.

How to use the record

Agree the criteria weeks before the meeting, not on the day. Fill in the evidence fields from the defect log, test results, migration reconciliation and training records. At the meeting, walk the criteria one by one, set each status and record the decision. If the answer is a conditional go, write the conditions with owners and deadlines. Capture the rollback trigger and point of no return too. Export to PDF for the project file.

Criteria agreed in advance
Evidence, not opinion
Conditions with owners and dates
Rollback trigger written down

Typical go-live criteria

Most programs use a similar set: UAT exit criteria met with no open blockers, an agreed ceiling for majors with signed workarounds, migrated data reconciled to source totals, interfaces proven end to end, security roles approved by process owners, end users trained, support and hypercare staffed, and a rollback plan that has been rehearsed. Add compliance items relevant to your site such as tax, e-invoicing or export control configuration.

Conditional go and no-go

A conditional go is a go only if specific, verifiable conditions are met by a stated time. Avoid vague conditions like improve data quality. A no-go is not a failure; it is the decision working as designed. Record the reasons, the new target date and the work required to reach it. Remember that the cost of delay is usually smaller than the cost of a failed cutover to production inventory, orders and invoicing.

Conditions must be testable
Record who verifies each
Set a new decision date on no-go

Common mistakes

Sponsors sometimes treat the meeting as a formality because the date has been announced. Teams also report only the overall percent of tests passed, hiding failures in critical processes such as shipping or month end. Another gap is deciding go without a rollback trigger, so nobody knows when to stop. Keep the record short, factual and signed. Store it with the cutover plan.

Frequently Asked Questions

What is a go/no-go decision in ERP?

A formal checkpoint before cutover where the steering committee reviews readiness criteria and decides whether to proceed, proceed with conditions, or postpone go-live.

Who attends the go/no-go meeting?

The executive sponsor, project manager, IT lead, business process owners, test lead, data migration lead, the vendor or integrator lead and the support lead.

When should the go/no-go meeting happen?

Usually one to two weeks before cutover, with a short final confirmation just before the cutover window starts, after the last mock cutover results are known.

What is a rollback trigger?

A predefined condition and deadline after which the team reverts to the legacy system. It is written in advance so the decision in the middle of a cutover weekend is not improvised.

If reconciling migrated data before the decision is slow, we can show how read-only queries compare source and target totals quickly.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Back to All Tools