# ERP Go/No-Go Decision Memo Template (PDF and Word) > Source: https://netray.co/tools/erp-go-no-go-decision-memo-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A one-to-two page memo that records the go-live recommendation, evidence by criterion, conditions and approvals. ## Category erp-migration ## Audience - ERP project manager - Program sponsor - Steering committee ## Tool **Kind:** template **Output:** document **Fields:** #### Company name **Key:** company **Type:** text **Default:** Acme Precision Ltd #### Project name **Key:** project **Type:** text **Default:** ERP Replacement Program #### System going live **Key:** system **Type:** text **Default:** New ERP, Phase 1 (Finance, Supply Chain, Production) #### Decision meeting date **Key:** meeting_date **Type:** date **Default:** 2026-11-12 #### Planned go-live date **Key:** golive_date **Type:** date **Default:** 2026-11-23 #### Prepared by **Key:** prepared_by **Type:** text **Default:** Project Manager #### Recommendation **Key:** recommendation **Type:** select **Options:** - Go - Conditional go - No-go - Defer to new date **Default:** Conditional go #### Cutover window **Key:** cutover_window **Type:** text **Default:** Friday 18:00 to Sunday 18:00 #### Last point of rollback **Key:** rollback_point **Type:** text **Default:** Sunday 06:00, before first transactions are posted #### Open severity 1 defects **Key:** sev1 **Type:** number **Default:** 0 #### Open severity 2 defects **Key:** sev2 **Type:** number **Default:** 3 #### Readiness summary **Key:** summary **Type:** textarea **Default:** UAT scenarios are 96 percent passed. The last mock load reconciled to the ledger within tolerance. End user training reached 92 percent of planned attendees. #### Conditions for go **Key:** conditions **Type:** textarea **Default:** 1. The three open severity 2 defects have an approved workaround. 2. Customer EDI test with the top two partners passes by Wednesday. 3. Hypercare roster is confirmed for the first four weeks. **Blocks:** #### ERP Go/No-Go Decision Memo **Body:** Company: {{company}} Project: {{project}} System: {{system}} Decision meeting: {{meeting_date}} Planned go-live: {{golive_date}} Prepared by: {{prepared_by}} #### Recommendation **Body:** Recommendation to the steering committee: {{recommendation}} Cutover window: {{cutover_window}} Last point of rollback: {{rollback_point}} #### Readiness summary **Body:** {{summary}} Open severity 1 defects: {{sev1}} Open severity 2 defects: {{sev2}} #### Criteria status **Table:** **Columns:** - Criterion - Status (Met / Partly / Not met) - Evidence - Owner **Rows:** **0:** UAT scenarios passed against exit criteria **0:** Open defects within agreed limits **0:** Final mock load reconciled to source **0:** Integrations tested end to end **0:** Users trained and access roles assigned **0:** Cutover plan rehearsed with timings **0:** Support and hypercare roster confirmed **0:** Business owners signed off processes #### Conditions for go **Body:** {{conditions}} #### Rollback and contingency **Body:** If a condition is not met by the review point, or a rollback trigger is reached, the cutover manager will inform the sponsor and execute the rollback plan to {{rollback_point}}. The decision to roll back rests with the sponsor. #### Approvals **Signatures:** - Project sponsor - Business owner (operations) - Finance controller - IT / technical lead - Project manager **Notes:** Starting point for your own governance, not legal advice. Add your organisation's formal criteria, regulatory sign-offs and any customer commitments before use. ## Content **Intro:** The go/no-go meeting is where a long program meets reality, and the record of that decision matters later. This template produces a concise memo that states the recommendation, the evidence by criterion, the conditions attached and the rollback point, ready for signature. **Sections:** #### How to use it **Body:** Fill in the fields before the meeting, then print or export the memo as the meeting document. State the recommendation clearly at the top; do not bury it. Complete the criteria table with a status and a link or reference to evidence, such as a test report or reconciliation sign-off. Add conditions only if they are specific, testable and have an owner and a due date. Capture the sign-offs in the meeting itself. **Bullets:** - Put the recommendation first - Link evidence for each criterion - Make conditions specific and testable - Record who decided and when #### What good criteria look like **Body:** Good criteria are measurable and agreed before testing starts: for example, no open severity 1 defects, a reconciled final mock load, integrations passing end-to-end tests, a defined percentage of users trained, a rehearsed cutover with timings inside the window and a staffed hypercare roster. Business owner sign-off on processes is as important as the technical measures, since the system is only ready if people can operate the business on it. #### Handling a conditional go **Body:** A conditional go is common and legitimate when the remaining items are small, but it needs discipline. Each condition should have a check time before the point of no return, a named owner and a clear consequence if missed. If more than a few conditions are open, or any affects financial postings, shipping or compliance, the honest recommendation may be to defer. Price a deferral using a delay cost estimate. #### Common mistakes **Body:** Decisions made on verbal assurances leave no evidence if something goes wrong. Another mistake is setting criteria after seeing the results, which turns the meeting into negotiation. Teams also forget to define the last point of rollback, so nobody can say when going back stops being possible. **Bullets:** - No written evidence - Criteria changed at the meeting - No defined rollback point - Sponsor not present to decide **Cta:** If you want readiness evidence gathered automatically from test, data and ERP systems into one view, Netray can build it on your infrastructure. **Faq:** #### Who should sign a go/no-go memo? **Answer:** Typically the project sponsor, the business owners of affected processes, the finance controller, the IT lead and the project manager. Add quality or compliance sign-off if regulated processes are in scope. #### When is the go/no-go meeting held? **Answer:** Often there are two: a provisional one one to two weeks before cutover and a final one shortly before the cutover starts. The final meeting confirms that conditions from the first were met. #### What is a point of no return? **Answer:** It is the last moment when you can still revert to the old system without losing transactions or causing inconsistent data. Define it in the cutover plan and write it into this memo. #### Can the memo be used for phased rollouts? **Answer:** Yes. Create one memo per wave or site, and reuse the criteria so decisions are consistent. Note lessons from the previous wave in the readiness summary. ## Search terms erp go no go decision template, go live decision memo, go no go meeting template, erp go live sign off form, go live recommendation document, cutover decision checklist, erp go live approval, go no go criteria erp --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json