# ERP Go/No-Go Decision Record Template (Criteria, Evidence, Sign-Off) > Source: https://netray.co/tools/erp-go-no-go-decision-record-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A formal go/no-go decision document for ERP cutover with criteria status, open defects, conditions and executive sign-off. ## Category erp-migration ## Audience - ERP project manager - Program sponsor - Steering committee ## Tool **Kind:** template **Output:** document **Fields:** #### Project **Key:** project **Type:** text **Default:** Plant 1 ERP Replacement #### Decision meeting date **Key:** meeting **Type:** date **Default:** 2026-11-20 #### Planned go-live date **Key:** golive **Type:** date **Default:** 2026-11-30 #### Decision **Key:** decision **Type:** select **Options:** - Go - Conditional go - No-go - Postpone **Default:** Conditional go #### Open blocker defects **Key:** blockers **Type:** number **Default:** 0 #### Open major defects **Key:** majors **Type:** number **Default:** 3 #### UAT pass rate **Key:** uat **Type:** text **Default:** 94 percent of scripts passed #### Conditions for go **Key:** conditions **Type:** textarea **Default:** All three open major defects closed or covered by signed workarounds by 25 November. Final mock cutover completed within the planned window. #### Rollback trigger and deadline **Key:** rollback **Type:** textarea **Default:** Rollback to legacy if opening inventory reconciliation fails by more than the agreed tolerance and cannot be corrected by Sunday 18:00. **Blocks:** #### Go/No-Go Decision Record **Body:** Project: {{project}} Decision meeting: {{meeting}} Planned go-live: {{golive}} Decision: {{decision}} #### Readiness criteria **Table:** **Columns:** - Criterion - Evidence - Status - Owner **Rows:** **0:** UAT exit criteria met **1:** {{uat}} **0:** Open blocker defects **1:** {{blockers}} **0:** Open major defects **1:** {{majors}} **0:** Data migration reconciled **0:** Interfaces tested end to end **0:** Security roles approved **0:** Users trained **0:** Support model staffed **0:** Rollback plan tested #### Conditions attached to the decision **Body:** {{conditions}} #### Rollback trigger **Body:** {{rollback}} #### Sign-off **Signatures:** - Project manager - Business process owners - IT lead - Executive sponsor **Notes:** Adapt the criteria to your project. A decision record documents accountability; it does not replace a tested cutover plan. ## Content **Intro:** The go/no-go meeting is where evidence replaces optimism. This record lists the criteria, the evidence behind each, any conditions, and who signed. **Sections:** #### How to use the record **Body:** 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. **Bullets:** - Criteria agreed in advance - Evidence, not opinion - Conditions with owners and dates - Rollback trigger written down #### Typical go-live criteria **Body:** 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 **Body:** 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. **Bullets:** - Conditions must be testable - Record who verifies each - Set a new decision date on no-go #### Common mistakes **Body:** 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. **Cta:** If reconciling migrated data before the decision is slow, we can show how read-only queries compare source and target totals quickly. **Faq:** #### What is a go/no-go decision in ERP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms ERP go no go decision template, go no go checklist ERP, go live decision record, ERP go-live approval form, cutover go no go meeting template, go live sign off template, ERP readiness decision document --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json