Cloud Transformation

How to Build an Effective ERP Steering Committee

Learn how to structure, staff, and run an ERP steering committee that provides governance, decision-making, and executive oversight.

Why ERP Projects Need a Steering Committee

ERP implementations touch nearly every part of an organization, creating decisions that extend beyond what a project manager or IT team can resolve alone. A steering committee provides the governance structure needed to make timely, cross-functional decisions, resolve conflicts between departments, and ensure the project stays aligned with business strategy rather than drifting into scope creep or stalled decision-making.

Step 1: Define the Committee Charter

Start by documenting the steering committee’s purpose, authority, and decision rights in a formal charter. Clarify what decisions the committee can make independently, such as approving scope changes within a defined budget threshold, versus what must be escalated to the executive sponsor or board. This prevents ambiguity later when difficult decisions arise under time pressure.

Step 2: Select the Right Members

Membership should include senior leaders from each major business function affected by the ERP, typically finance, operations, IT, and HR, along with the executive sponsor who holds ultimate accountability for project success. Members need enough authority to make binding decisions for their department without having to constantly check back with their own leadership, since this slows the project considerably.

Step 3: Establish Meeting Cadence and Structure

Most ERP steering committees meet biweekly during active implementation phases, shifting to monthly during stabilization periods. Each meeting should follow a consistent structure covering project status, budget and timeline tracking, risk and issue review, and any decisions requiring committee approval. Avoid turning meetings into detailed status updates better suited for working-level project teams.

Step 4: Define Clear Decision-Making Processes

Establish how decisions will be made when committee members disagree, whether through executive sponsor tiebreaker authority, majority vote, or escalation to a higher governance body. Document every significant decision made, including the rationale, so the project team has clear direction and the organization maintains an audit trail of why key choices were made throughout the implementation.

Step 5: Monitor Risk and Budget Rigorously

The steering committee should review a standardized risk register and budget tracker at every meeting, with clear ownership assigned to each open risk. Budget variance beyond a predefined threshold should trigger mandatory committee review rather than being absorbed quietly by the project team, since cost overruns often compound if not addressed early.

Step 6: Keep the Committee Engaged Through Go-Live

Steering committee involvement should not taper off as go-live approaches, this is often when critical decisions about cutover readiness, contingency plans, and post-go-live support are most needed. Maintain active committee oversight through hypercare and initial stabilization before formally transitioning governance to standard operational management.

An effective ERP steering committee is one of the strongest predictors of implementation success. Symhas helps organizations establish governance structures, including steering committees, that keep ERP projects on track and aligned with business goals. Contact Symhas to strengthen your project governance.

Schedule a Briefing →

Frequently Asked Questions

How many members should an ERP steering committee have

Typically six to ten members, large enough to represent all major functions but small enough to make timely decisions.

Who should chair the steering committee

Usually the executive sponsor or a senior business leader, rather than the project manager, to maintain appropriate authority and accountability.

How often should the steering committee meet

Biweekly during active implementation is common, shifting to monthly during stabilization and post-go-live support phases.