ERP Steering Committee Status Report Template
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.
Fill in
ERP Steering Committee Status Report Template
ERP Steering Committee Status Report
Project: ERP Replacement Wave 1 Company: Example Maschinenbau GmbH Period: October 2026 Project manager: A. Becker Planned go-live: 2027-03-01
Status Summary
| Dimension | Status |
|---|---|
| Overall | Amber |
| Scope | Green |
| Schedule | Amber |
| Budget | Green |
Budget
Approved budget: EUR 650000 Spent to date: EUR 412000 Add forecast to complete and committed orders before the meeting.
Achievements this period
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
Production planning workshops. Third mock load with open orders. Cutover plan draft for review.
Top risks
| Risk | Owner | Mitigation | Rating |
|---|---|---|---|
| Key user availability in production planning during peak season. BOM data quality in the legacy system. | |||
Decisions needed from the committee
Approve move of go-live testing window by two weeks. Release two additional key users for November.
Approval
Starting point only. Adapt the rating definitions to your own project governance. Keep status colours consistent between meetings so trends are visible.
Optional project health check
We can review your project plan and status reporting and suggest measurable milestones and risk indicators. No obligation.
Optional. The tool and every export work without this. No spam.
How to use it
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.
- 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
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
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
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.
Frequently Asked Questions
How long should the report be?
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?
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?
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?
No. It is a project governance template. Contractual changes should follow your change control process and be reviewed by your legal team.
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.
Related Tools
ERP Go-Live Delay Cost Calculator
What-if tool showing the true cost of postponing an ERP go-live: extended project team, legacy licences still running and benefits you do not yet earn.
ERP Migration & SelectionERP Fit-Gap Scoring Worksheet
Editable worksheet to weigh requirements, score how each candidate ERP meets them and calculate a weighted fit percentage you can export to Excel.
ERP Migration & SelectionERP Data Migration Effort Calculator
Estimate cleansing, open document validation and mock load hours for an ERP migration from record counts, defect rate and the number of trial loads.
ERP Migration & SelectionERP Implementation Effort Estimator (Consulting Days)
Estimate consulting days, cost and calendar duration for a mid-market ERP rollout from modules, sites, integrations and the share of requirements needing customisation.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment