# ERP Steering Committee Status Report Template > Source: https://netray.co/tools/erp-steering-committee-status-report-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Fill-in status report for ERP projects covering RAG status, budget, milestones, top risks and decisions needed, ready to export as a one-page PDF or Word file. ## Category erp-migration ## Audience - ERP project manager - Steering committee - PMO ## Tool **Kind:** template **Output:** document **Fields:** #### Project name **Key:** project **Type:** text **Default:** ERP Replacement Wave 1 #### Company **Key:** company **Type:** text **Default:** Example Maschinenbau GmbH #### Reporting period **Key:** period **Type:** text **Default:** October 2026 #### Project manager **Key:** pm **Type:** text **Default:** A. Becker #### Overall status **Key:** overall **Type:** select **Options:** - Green - Amber - Red **Default:** Amber #### Scope status **Key:** scope **Type:** select **Options:** - Green - Amber - Red **Default:** Green #### Schedule status **Key:** schedule **Type:** select **Options:** - Green - Amber - Red **Default:** Amber #### Budget status **Key:** budget_status **Type:** select **Options:** - Green - Amber - Red **Default:** Green #### Approved budget (EUR) **Key:** budget_total **Type:** number **Default:** 650000 #### Spent to date (EUR) **Key:** budget_spent **Type:** number **Default:** 412000 #### Planned go-live date **Key:** golive **Type:** date **Default:** 2027-03-01 #### Achievements this period **Key:** achieved **Type:** textarea **Default:** Finance and purchasing user acceptance tests completed. Second mock data load reconciled for items and suppliers. Bank interface tested in the sandbox. #### Plan for next period **Key:** next **Type:** textarea **Default:** Production planning workshops. Third mock load with open orders. Cutover plan draft for review. #### Top risks **Key:** risks **Type:** textarea **Default:** Key user availability in production planning during peak season. BOM data quality in the legacy system. #### Decisions needed **Key:** decisions **Type:** textarea **Default:** Approve move of go-live testing window by two weeks. Release two additional key users for November. **Blocks:** #### ERP Steering Committee Status Report **Body:** Project: {{project}} Company: {{company}} Period: {{period}} Project manager: {{pm}} Planned go-live: {{golive}} #### Status Summary **Table:** **Columns:** - Dimension - Status **Rows:** **0:** Overall **1:** {{overall}} **0:** Scope **1:** {{scope}} **0:** Schedule **1:** {{schedule}} **0:** Budget **1:** {{budget_status}} #### Budget **Body:** Approved budget: EUR {{budget_total}} Spent to date: EUR {{budget_spent}} Add forecast to complete and committed orders before the meeting. #### Achievements this period **Body:** {{achieved}} #### Plan for next period **Body:** {{next}} #### Top risks **Table:** **Columns:** - Risk - Owner - Mitigation - Rating **Rows:** **0:** {{risks}} #### Decisions needed from the committee **Body:** {{decisions}} #### Approval **Signatures:** - Project manager - Project sponsor - Steering committee chair **Notes:** Starting point only. Adapt the rating definitions to your own project governance. Keep status colours consistent between meetings so trends are visible. ## Content **Intro:** A steering committee wants three things: where the project stands, what could hurt it and what it must decide. This template puts them on one page so executives can read it in minutes and still see the numbers. **Sections:** #### How to use it **Body:** Fill in the project header, set the RAG status for scope, schedule and budget, and enter the budget figures. Keep achievements and next steps to a few outcome statements, not task lists. Put the decisions you need first in your meeting agenda, because executives remember what they are asked to decide. Export the document as PDF a day before the meeting. **Bullets:** - Use the same format every period - Write decisions as yes or no questions - Name an owner for every risk - Show budget as spent, committed and forecast #### Setting RAG status **Body:** Define the colours before the project starts. A typical rule is green when the variance is inside tolerance, amber when it threatens a milestone but a recovery plan exists, and red when the committee must act. Overall status should never be greener than the worst dimension without an explanation. Honest amber early is more useful than red at the last moment. #### What good reports include **Body:** The strongest ERP reports show progress against milestones such as design sign-off, completed test cycles, mock loads reconciled and training completion, rather than percent complete. They list risks with a probability and impact rating, and they show what changed since the last report. Link the report to the delay cost and effort calculators when a decision involves moving a date. #### Common mistakes **Body:** Reports often hide bad news in long text, mix status with discussion and bring no decisions. Others report activity such as workshops held, not outcomes. If the committee meets monthly, add a line for changes in scope or budget approved since the last meeting so the record is complete for auditors. **Cta:** Netray can add a read-only dashboard of test results, data migration reconciliation and open defects, so the status report is fed by real data. **Faq:** #### How long should the report be? **Answer:** One to two pages. Executives read the summary and the decisions section. Put detail in an appendix or in the project tool. #### How often should the committee meet? **Answer:** Monthly is common for mid-market ERP projects, with extra sessions at design sign-off, before cutover and at go or no-go. Weekly is rarely needed. #### Who should sit on the committee? **Answer:** A sponsor from the business, finance, IT and the heads of the main process areas. The vendor or partner attends for specific items, not for the decision itself. #### Is this a legal document? **Answer:** No. It is a project governance template. Contractual changes should follow your change control process and be reviewed by your legal team. ## Search terms erp steering committee report template, erp project status report template, erp project dashboard template, project status report word, erp rag status report, erp steering committee agenda --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json