ERP Migration & SelectionFree worksheetPDF, Excel, Word export

ERP Implementation Risk Register Template with Scoring

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.

Download:

ID	Risk description	Category	Probability (1-5)	Impact (1-5)	Score	Owner	Mitigation	Status	Next review
					16
					12
					15
					9
					10

Highest risk score

Average risk score

12.4

Risks logged

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.

Independent risk review

Optional: send your register and we will point out gaps against common ERP failure patterns.

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

How to use it

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

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.

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

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

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.

Frequently Asked Questions

How many risks should an ERP project register hold?

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?

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?

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?

Weekly in the project team meeting, and the top risks in every steering committee. Review frequency should rise as go-live approaches.

If you want an outside view on the top risks in your ERP program, Netray can review your register against common failure patterns.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Back to All Tools