# ERP Project Steering Committee Report Template > Source: https://netray.co/tools/eu-erp-steering-committee-report-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A one-to-two page monthly steering report for ERP implementations with RAG status, milestones, budget burn, risks and decisions required. ## Category erp-operations ## Region Europe ## Industry Discrete Manufacturing ## Audience - ERP project manager - PMO - Executive sponsor ## Tool **Kind:** template **Output:** document **Fields:** #### Project name **Key:** project **Type:** text **Default:** ERP Replacement Programme #### Company **Key:** company **Type:** text **Default:** Nordwerk Maschinenbau GmbH #### Reporting period **Key:** period **Type:** text **Default:** October 2026 #### Project manager **Key:** pm **Type:** text **Default:** J. Weber #### Overall status **Key:** overall **Type:** select **Options:** - Green - Amber - Red **Default:** Amber #### Scope status **Key:** scope_rag **Type:** select **Options:** - Green - Amber - Red **Default:** Green #### Schedule status **Key:** time_rag **Type:** select **Options:** - Green - Amber - Red **Default:** Amber #### Budget status **Key:** budget_rag **Type:** select **Options:** - Green - Amber - Red **Default:** Green #### Approved budget (EUR) **Key:** budget **Type:** number **Default:** 1450000 #### Spent to date (EUR) **Key:** spent **Type:** number **Default:** 820000 #### Forecast at completion (EUR) **Key:** forecast **Type:** number **Default:** 1480000 #### Executive summary **Key:** summary **Type:** textarea **Default:** Fit-gap workshops for production and quality are complete. Data cleansing of the item master is behind plan by two weeks because of duplicate part numbers. #### Decisions required **Key:** decision **Type:** textarea **Default:** Approve two additional days per week of key user time from Production Planning during November. **Blocks:** #### ERP Steering Committee Report **Body:** Project: {{project}} Company: {{company}} Period: {{period}} Project manager: {{pm}} Overall status: {{overall}} #### Executive summary **Body:** {{summary}} #### Status by dimension **Table:** **Columns:** - Dimension - Status - Comment **Rows:** **0:** Scope **1:** {{scope_rag}} **0:** Schedule **1:** {{time_rag}} **0:** Budget **1:** {{budget_rag}} **0:** Resources **0:** Quality / testing #### Budget **Body:** Approved: EUR {{budget}} Spent to date: EUR {{spent}} Forecast at completion: EUR {{forecast}} #### Milestones **Table:** **Columns:** - Milestone - Baseline date - Forecast date - Status **Rows:** **0:** Fit-gap complete **0:** Data migration trial 2 **0:** User acceptance test start **0:** Go-live #### Top risks and issues **Table:** **Columns:** - Ref - Risk or issue - Impact - Owner - Mitigation **Rows:** **0:** R1 **0:** R2 **0:** R3 #### Decisions required from the committee **Body:** {{decision}} #### Approval **Signatures:** - Project manager - Executive sponsor - Finance representative **Notes:** A starting-point format. Adapt thresholds for Amber and Red to your own governance rules and keep the report to two pages. ## Content **Intro:** A steering committee has limited time, so the report must show where the project stands, what is changing and what decision is needed today. This template keeps to that: one status table, one budget block, milestones, risks and the decisions required. **Sections:** #### How to use the template **Body:** Fill in the fields, choose the Red, Amber or Green status for each dimension and write a short executive summary of three or four sentences. The document is generated with your values in place, and you can add detail to the tables after export. Send it two working days before the meeting so members arrive prepared, and bring only the decisions to the table. **Bullets:** - Lead with the overall status and the one thing that changed - State decisions as questions that have a yes or no answer - Keep risks to the top five with named owners - Show budget as approved, spent and forecast #### Defining RAG status honestly **Body:** Agree thresholds before the project starts. For example, Amber when a milestone is forecast more than two weeks late or the forecast exceeds budget by up to ten percent, and Red when the date or budget breach needs the committee to act. Statuses that are always green teach the committee to ignore the report, so be willing to show Amber early. #### What belongs in the risk table **Body:** Typical ERP risks include key user availability, data quality, scope creep through late customisation requests, interface readiness with third-party systems and the vendor's resourcing. Add the date the risk was raised and the next review date so ageing is visible. A risk without an owner and a mitigation is only a worry. #### Common mistakes **Body:** Many reports are too long and bury the decision. Others report activity such as workshops held instead of outcomes such as processes signed off. Another frequent problem is hiding the forecast at completion until the budget is already spent. Report the forecast every month, even if it is uncomfortable. **Cta:** If you would like reports like this populated from your project and ERP data automatically, we can show how it can be set up. Optional. **Faq:** #### How often should the steering committee meet? **Answer:** Monthly is typical during implementation, moving to every two weeks in the last eight weeks before go-live. Between meetings, the project manager should escalate urgent decisions by email rather than waiting for the next scheduled session. #### Who should sit on the steering committee? **Answer:** The executive sponsor, the heads of the main affected functions such as operations, finance and IT, the project manager and the vendor or partner lead. Keep it small, five to eight people, so decisions are actually made. #### What decisions belong at steering level? **Answer:** Budget changes, scope changes with cost or schedule impact, go-live date moves, resource commitments from departments and anything the project manager cannot resolve at working level. Detailed design questions should stay with the project team. #### Can I use this for a rollout to a second plant? **Answer:** Yes. Add a plant or legal entity column to the milestone and risk tables, and report each site's status separately if they are at different stages. The structure holds for multi-site programmes. ## Search terms erp steering committee report template, erp project status report template, erp implementation status report, steering committee template word, erp project dashboard report, project status report template erp rollout --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json