# ERP Project Health Check: Governance and Delivery Assessment > Source: https://netray.co/tools/erp-project-governance-health-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A ten-question self-assessment that scores how healthy your ERP implementation governance and delivery practices are. ## Category erp-migration ## Audience - ERP project manager - Program sponsor - CIO ## Tool **Kind:** assessment **Questions:** #### How active is your executive sponsor? **Options:** ##### Attends steering and removes blockers quickly **Score:** 3 ##### Attends steering but decisions are slow **Score:** 2 ##### Rarely involved **Score:** 1 ##### No named sponsor **Score:** 0 #### How is scope controlled? **Options:** ##### Signed baseline with a formal change process **Score:** 3 ##### Baseline exists but changes are informal **Score:** 2 ##### Scope is loosely documented **Score:** 1 ##### Scope changes freely **Score:** 0 #### What is the state of data migration? **Options:** ##### Object list, owners and at least one mock load done **Score:** 3 ##### Mapping started, no mock load yet **Score:** 2 ##### Data owners not yet agreed **Score:** 1 ##### Data is expected to be handled near the end **Score:** 0 #### How available are business super users? **Options:** ##### Allocated with time backfilled **Score:** 3 ##### Allocated but often pulled away **Score:** 2 ##### Ad hoc availability only **Score:** 1 ##### No named super users **Score:** 0 #### How is testing planned? **Options:** ##### Scripts, cycles and exit criteria agreed **Score:** 3 ##### Scripts in progress, criteria vague **Score:** 2 ##### Testing planned late **Score:** 1 ##### No test plan **Score:** 0 #### How are integrations handled? **Options:** ##### Inventory complete with test windows agreed **Score:** 3 ##### Inventory complete, testing not scheduled **Score:** 2 ##### Partial inventory **Score:** 1 ##### Not yet inventoried **Score:** 0 #### How is the risk register used? **Options:** ##### Reviewed weekly with owners and actions **Score:** 3 ##### Reviewed monthly **Score:** 2 ##### Exists but rarely updated **Score:** 1 ##### No register **Score:** 0 #### How is training planned? **Options:** ##### Role-based plan with dates and sandbox **Score:** 3 ##### Plan drafted, dates not fixed **Score:** 2 ##### Planned to start close to go-live **Score:** 1 ##### No training plan **Score:** 0 #### How mature is cutover planning? **Options:** ##### Runbook timed with a rehearsal done **Score:** 3 ##### Runbook drafted, no rehearsal **Score:** 2 ##### High-level outline only **Score:** 1 ##### No cutover plan **Score:** 0 #### How reliable is status reporting? **Options:** ##### Weekly, factual, with decisions requested **Score:** 3 ##### Regular but optimistic **Score:** 2 ##### Irregular **Score:** 1 ##### No formal reporting **Score:** 0 **Bands:** #### High risk **Min:** 0 **Max:** 39 **Verdict:** Several fundamentals are missing. The project is exposed to schedule and budget overruns. **Recommendations:** - Name an executive sponsor and hold a steering meeting this week - Baseline scope and start a change log - Assign data owners and plan a first mock load - Consider an independent review before committing a go-live date #### Needs attention **Min:** 40 **Max:** 64 **Verdict:** The framework exists, but gaps in data, testing or resourcing could hurt later phases. **Recommendations:** - Fix the weakest two answers before the next phase gate - Ring-fence super user time in the plan - Schedule integration testing and a cutover rehearsal #### Healthy with gaps **Min:** 65 **Max:** 84 **Verdict:** Governance is mostly sound. Focus on the remaining weak areas and keep discipline. **Recommendations:** - Close remaining gaps in training and cutover planning - Keep risk and status reports factual - Rehearse cutover at least twice #### Strong **Min:** 85 **Max:** 100 **Verdict:** Practices look solid. Stay disciplined through testing and cutover. **Recommendations:** - Protect super user time - Hold go/no-go criteria steady as dates approach - Plan hypercare staffing early ## Content **Intro:** Most ERP projects that struggle show warning signs months before go-live. This assessment checks ten areas that predict delivery trouble, so a sponsor or project manager can see where the program is exposed. **Sections:** #### How to use it **Body:** Answer based on what is true today, not on the plan. Ideally have the project manager, business owner and a technical lead answer independently and compare. Differences between their answers are often more revealing than the score. Repeat the assessment at each phase gate to track the trend. #### What the questions measure **Body:** The ten questions cover the areas where ERP programs most often fail: sponsorship, scope, data, people, testing, integration, risk management, training, cutover and reporting. Each answer scores zero to three and the total is shown as a percentage of the maximum. **Bullets:** - Governance: sponsor, scope, risk, reporting - Delivery: data, testing, integration - Readiness: people, training, cutover - Scores are indicators, not guarantees #### Reading the result **Body:** A low score does not mean the project will fail; it means the missing items should be treated as risks with owners. Focus on the lowest-scoring answers first. A project with good scores overall but a zero on cutover planning still carries a serious exposure that the average hides. #### Common mistakes **Body:** Answering optimistically is the main failure: score what is evidenced, such as a signed baseline or a completed mock load, not what is intended. Also avoid using the result to blame teams. Use it to decide what to fix before the next gate. **Cta:** For an outside perspective on a troubled or stalled ERP program, Netray can discuss a structured review of data, integration and cutover readiness. **Faq:** #### Is this a formal ERP audit? **Answer:** No. It is a quick self-assessment that highlights common risk areas. A formal independent review looks at contracts, code, test evidence and data quality in depth. #### When should I run it? **Answer:** At each major phase gate, and any time the team feels the project is drifting. Comparing scores over time is more useful than a single result. #### What score should trigger a pause? **Answer:** A score under 40 percent, or a zero on data migration, testing or cutover, is a good reason to stop and replan before committing more spend or fixing a go-live date. #### Does it apply to cloud ERP projects? **Answer:** Yes. Cloud products reduce infrastructure work, but data, integrations, testing, training and cutover remain the main sources of delay. ## Search terms ERP project health check, ERP implementation assessment, is my ERP project on track, ERP project governance checklist, ERP project audit questions, ERP implementation red flags --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json