# ERP Implementation Risk Register Template with Scoring > Source: https://netray.co/tools/erp-implementation-risk-register-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable risk register for ERP projects that scores each risk as probability times impact and exports to Excel. ## Category erp-migration ## Audience - ERP project manager - PMO lead - Program sponsor ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### ID **Key:** id **Type:** text #### Risk description **Key:** risk **Type:** text #### Category **Key:** category **Type:** select **Options:** - Scope - Data - Integration - People - Schedule - Budget - Vendor - Technical #### Probability (1-5) **Key:** prob **Type:** number #### Impact (1-5) **Key:** impact **Type:** number #### Score **Key:** score **Type:** number **Expr:** prob * impact #### Owner **Key:** owner **Type:** text #### Mitigation **Key:** mitigation **Type:** text #### Status **Key:** status **Type:** select **Options:** - Open - Mitigating - Closed - Occurred #### Next review **Key:** review **Type:** date **Rows:** **Id:** R-01 **Risk:** Legacy item master has duplicate parts that will inflate the migrated catalog **Category:** Data **Prob:** 4 **Impact:** 4 **Owner:** Data lead **Mitigation:** Run duplicate analysis and agree merge rules before mock load 1 **Status:** Mitigating **Review:** 2026-11-05 **Id:** R-02 **Risk:** Key super users pulled back to daily operations during UAT **Category:** People **Prob:** 4 **Impact:** 3 **Owner:** Plant manager **Mitigation:** Backfill roles and ring-fence UAT hours in the plan **Status:** Open **Review:** 2026-11-05 **Id:** R-03 **Risk:** EDI partner testing not scheduled before cutover **Category:** Integration **Prob:** 3 **Impact:** 5 **Owner:** Integration lead **Mitigation:** Book partner test windows now and add EDI to the go/no-go list **Status:** Open **Review:** 2026-11-12 **Id:** R-04 **Risk:** Custom reports not specified, scope grows during build **Category:** Scope **Prob:** 3 **Impact:** 3 **Owner:** Project manager **Mitigation:** Freeze report list and route additions through change control **Status:** Open **Review:** 2026-11-12 **Id:** R-05 **Risk:** Cutover window shorter than measured data load time **Category:** Schedule **Prob:** 2 **Impact:** 5 **Owner:** Cutover lead **Mitigation:** Time mock loads and pre-load static master data in the weeks before **Status:** Mitigating **Review:** 2026-11-19 **Totals:** #### Highest risk score **Key:** score **Agg:** max **Format:** integer #### Average risk score **Key:** score **Agg:** avg **Format:** decimal #### Risks logged **Key:** id **Agg:** count **Format:** integer **Notes:** Score above 14 is commonly treated as high and needs sponsor attention; 8 to 14 is medium; below 8 is low. Set your own thresholds with your PMO. ## Content **Intro:** A risk register is the one project document that sponsors read closely when something goes wrong. This worksheet gives an ERP project manager a clean starting register with scoring, owners and review dates, and exports directly to Excel for the steering pack. **Sections:** #### How to use it **Body:** Delete the example rows and add your own. Describe each risk as an event and its consequence, assign probability and impact on a one to five scale, and name a single owner. The score column multiplies the two. Sort by score before each steering meeting, update status and next review date, and export to Excel so the sponsor sees the same register you maintain. #### Scoring method **Body:** Probability times impact on a five by five grid gives scores from 1 to 25. It is a ranking device, not a measurement, so use consistent definitions: for example, impact 5 means a go-live slip of more than a month or a budget overrun above ten percent. Agree definitions at kickoff so scores are comparable. **Bullets:** - Probability: 1 rare to 5 almost certain - Impact: 1 negligible to 5 severe on schedule, cost or operations - Review high scores weekly and medium scores every two weeks - A closed risk stays in the log with the reason #### Typical ERP risks **Body:** Experience across ERP programs shows recurring themes: dirty master data, thin super user availability, late integration testing, uncontrolled scope growth, underestimated training, and a cutover window that does not match measured load times. Seed your register with these, then add risks specific to your plants, countries and customizations. #### Common mistakes **Body:** Registers often list issues, which have already happened, instead of risks. Another mistake is no owner or a team name as owner, which means nobody acts. A third is never closing items, so the sponsor stops reading. Keep the register short enough to discuss in ten minutes. **Cta:** If you want an outside view on the top risks in your ERP program, Netray can review your register against common failure patterns. **Faq:** #### How many risks should an ERP project register hold? **Answer:** Most active registers hold 15 to 40 risks. Fewer suggests the team is not looking hard, and many more than that usually means issues and tasks are mixed in. Keep the top ten visible to the sponsor. #### What is the difference between a risk and an issue? **Answer:** A risk is something that might happen; an issue has already happened and needs action now. When a risk occurs, change its status to Occurred and move the response to the issue log. #### Who should own a risk? **Answer:** One named person with the authority to act on it, usually a workstream lead. The project manager facilitates the register but should not own every risk. #### How often should the register be reviewed? **Answer:** Weekly in the project team meeting, and the top risks in every steering committee. Review frequency should rise as go-live approaches. ## Search terms ERP implementation risk register, ERP project risk register template excel, ERP risk log template, probability impact matrix ERP project, ERP project risk management, ERP risk register example --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json