# ERP Selection Risk Register Worksheet > Source: https://netray.co/tools/erp-selection-risk-register-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Track the risks of the ERP selection and decision itself, score them by probability and impact, and assign an owner and mitigation to each. ## Category erp-migration ## Audience - ERP project lead - PMO - CIO ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### ID **Key:** id **Type:** text #### Risk **Key:** risk **Type:** text #### Category **Key:** category **Type:** select **Options:** - Requirements - Vendor - Cost - People - Data - Integration - Schedule - Contract #### Probability (1-5) **Key:** prob **Type:** number #### Impact (1-5) **Key:** impact **Type:** number #### Risk score **Key:** score **Type:** number **Expr:** prob * impact **Format:** integer #### Owner **Key:** owner **Type:** text #### Mitigation **Key:** mitigation **Type:** text #### Status **Key:** status **Type:** select **Options:** - Open - Mitigating - Closed - Accepted #### Next review **Key:** review **Type:** date **Rows:** **Id:** R1 **Risk:** Requirements incomplete because plant teams are busy **Category:** Requirements **Prob:** 4 **Impact:** 4 **Owner:** Project lead **Mitigation:** Time-boxed workshops, sign-off by process owner **Status:** Mitigating **Review:** 2026-11-20 **Id:** R2 **Risk:** Vendor demo shows roadmap items as live features **Category:** Vendor **Prob:** 3 **Impact:** 4 **Owner:** Evaluation team **Mitigation:** Scripted demos, ask for production references **Status:** Open **Review:** 2026-12-01 **Id:** R3 **Risk:** Total cost excludes internal staff and data migration **Category:** Cost **Prob:** 4 **Impact:** 5 **Owner:** CFO delegate **Mitigation:** Five year cost model with contingency **Status:** Open **Review:** 2026-12-01 **Id:** R4 **Risk:** Key process owner leaves during selection **Category:** People **Prob:** 2 **Impact:** 4 **Owner:** Sponsor **Mitigation:** Named deputy for every process **Status:** Open **Review:** 2027-01-10 **Id:** R5 **Risk:** Legacy data quality blocks conversion plan **Category:** Data **Prob:** 4 **Impact:** 4 **Owner:** Supply chain lead **Mitigation:** Profile item master and BOM early **Status:** Open **Review:** 2027-01-10 **Id:** R6 **Risk:** Contract lacks exit and data return clauses **Category:** Contract **Prob:** 3 **Impact:** 5 **Owner:** Legal **Mitigation:** Make exit terms a negotiation condition **Status:** Open **Review:** 2027-02-01 **Totals:** #### Average risk score **Key:** score **Agg:** avg **Format:** decimal **Summary:** #### Highest risk score (max 25) **Key:** top **Expr:** max_score **Format:** integer **Primary:** true #### Risks logged **Key:** n **Expr:** count **Format:** integer **Notes:** Scores of 15 and above usually need executive attention, 8 to 14 need an owner and a plan, and below 8 can be monitored. Review the register at every steering committee meeting and close risks with a reason. ## Content **Intro:** Most ERP risk logs begin at implementation, but many expensive failures start during selection: incomplete requirements, optimistic demos, partial cost models and weak contracts. This register tracks those early risks so they are owned and reduced before you sign. **Sections:** #### How to use the register **Body:** List each risk in a sentence that states cause and effect. Choose a category, then rate probability and impact from 1 to 5. The sheet multiplies them into a score out of 25. Assign one named owner, write the mitigation and set a review date. Sort by score in Excel after export to present the top risks to the steering committee. Close risks with a note instead of deleting them. **Bullets:** - One owner per risk - Write specific mitigations, not 'monitor' - Review at every steering committee - Keep closed risks for lessons learned #### Typical selection risks **Body:** Frequent entries include requirements that describe the current system instead of the needed outcome, vendors demonstrating beta or partner features as standard, cost models that omit internal time and data migration, over reliance on one champion, integration with MES, PLM or CRM scoped late, and contract terms that leave the customer without exit or price protection. For manufacturers in regulated sectors, add traceability, export control and audit requirements. #### Scoring method **Body:** Probability and impact on a five point scale is the common qualitative method. Probability 1 means rare, 5 means almost certain. Impact 1 means negligible, 5 means it could stop the project or add more than 20 percent to cost. Multiply for a score. Use the same definitions across all risks and agree them at the first review so two people do not score the same risk differently. #### Common mistakes **Body:** Registers die when they become a one time exercise, when owners are groups instead of people, or when mitigations are vague. Avoid listing generic risks such as 'budget overrun' without cause. Tie risks to decisions in your selection plan, such as the demo script, the reference calls and the contract checklist, so the mitigations actually happen. **Cta:** For AI, data conversion or integration risks specific to Infor SyteLine, M3, LN or NetSuite estates, Netray can provide a technical risk review as an optional input. **Faq:** #### How is this different from an implementation risk log? **Answer:** It covers the phase before contract: choosing the right system, partner and terms. Implementation logs track delivery risks such as testing and cutover. Many risks carry over, so move the open ones into the project register when you sign. #### What score should trigger escalation? **Answer:** A common rule is 15 or more out of 25 goes to the steering committee, 8 to 14 stays with the project lead, and lower is monitored. Set the thresholds with your sponsor so everyone agrees on what escalation means. #### How many risks should the register hold? **Answer:** Ten to twenty active risks is normal. Fewer may mean you have not looked; many more makes it unreadable. Merge similar entries and archive closed ones. #### Who should own cost and contract risks? **Answer:** Cost risks usually belong to finance or the PMO, and contract risks to legal or procurement. The project lead should not own everything, otherwise the register just reflects one person's view. ## Search terms erp risk register template, erp selection risk register excel, erp project risk log, erp risk assessment template, erp selection risks, erp pmo risk register --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json