How to Create an ERP Implementation Update Deck

ERP implementation steering committee presentations are one of the more high-stakes recurring decks any operations or IT leader manages. These projects are expensive, long, politically complex, and consequential if they go wrong. The steering committee is counting on you to give them an accurate picture of where the project stands — not a rosy version designed to avoid difficult conversations. Leadership that learns the truth six months late has far fewer options than leadership that learns it in real time.

Open with a Project Health Summary

Lead with a one-page project health scorecard: overall status (green/yellow/red), status of each major workstream (finance, supply chain, HR, manufacturing, etc.), budget status (spend to date versus plan, forecast to complete), and schedule status (milestones completed versus planned, projected go-live date versus original date). Include a brief narrative explaining any changes from the prior period update.

If the project has moved from green to yellow or yellow to red, say so explicitly, explain why, and tell the committee what you are doing about it. Committees that discover problems through channels other than the project update lose confidence in the project leadership immediately.

Summarize Phase Completion and Milestone Status

Show a roadmap or Gantt view with completed milestones marked, current phase highlighted, and upcoming major milestones over the next sixty to ninety days. For any milestone that is delayed relative to the original plan, note the delay duration and whether it has been absorbed into schedule buffer or has affected the critical path.

Key completed deliverables — design sign-offs, data migration tests, integrations completed, user acceptance testing phases closed — should be listed here. Progress is hard to feel on a long ERP project; making completed milestones visible helps the steering committee recognize momentum even when the go-live is still months away.

Present Budget and Forecast

Show the budget waterfall: approved budget, spend to date by category, committed future spend, estimated cost to complete, and projected total cost compared to budget. If the project is tracking over budget, show why — scope additions, integrations that were more complex than estimated, or resource cost overruns — and present the options for managing to budget or the formal budget change request if a budget increase is required.

Never present a budget that will require a revision next month. If the overrun is coming, show it now while the committee has time to respond.

Escalate Issues and Risks Requiring Steering Committee Input

This is the most valuable section of the update for the steering committee. Identify the issues that have been escalated from the project team because they require a steering committee decision, executive sponsor action, or cross-functional escalation. For each issue, describe the situation, the options, the recommendation, and the decision required.

Risks that have not yet materialized should also be presented: the likelihood, the potential impact on schedule, budget, or go-live quality, and the mitigation plan in place or under development.

Preview the Next Period

Close with a forward-looking view: the key milestones and deliverables targeted for the next four to six weeks, any decisions or inputs the project team needs from the committee before those milestones can be achieved, and any external dependencies (vendor deliveries, IT infrastructure readiness, or data availability) that the project is waiting on.

Slide Deck's ERP implementation update template includes pre-built layouts for project health scorecards, milestone Gantt views, budget waterfall charts, and issue escalation tables.