Building an ERP Change Advisory Group That Actually Meets

Enterprise resource planning (ERP) transformations fail not because of bad software. They fail because governance structures collapse under organizational pressure. The Change Advisory Group (CAG) is the governance body most organizations create with good intentions and abandon within six months. This article explains how to build one that actually convenes, deliberates and delivers decisions.

Why Most CAGs Dissolve

Organizations launch a CAG at the start of an ERP program with enthusiasm. Executives attend the first two sessions. Then competing priorities erode attendance. The group loses quorum. Decisions get deferred. The program team fills the vacuum by making calls it was never authorized to make.

This pattern repeats across industries because CAGs are designed as ceremonial bodies, not decision-making engines. They carry no formal authority, no defined escalation path and no consequence for non-attendance. Without those three elements, the CAG becomes a status update meeting that no senior leader will protect on their calendar.

Define the CAG’s Decision Rights First

Before you recruit members or schedule the first session, define what the CAG owns. Decision rights are the foundation. Without them, the group has no reason to exist and no power to act.

The CAG should own three categories of decisions. First, it approves changes to ERP scope that affect budget, timeline or cross-functional process design. Second, it resolves escalated conflicts between business units over process standardization. Third, it authorizes exceptions to the enterprise design baseline when a business case justifies deviation.

Everything else belongs to the program management office (PMO) or the functional workstream leads. Clarity on boundaries prevents the CAG from becoming a bottleneck and stops the PMO from overreaching. Document these rights in a governance charter that the program sponsor signs before the first CAG session.

Recruit for Authority, Not Representation

The instinct in large organizations is to make the CAG representative. Every business unit wants a seat. Every function lobbies for inclusion. The result is a group of twenty people where half lack the authority to commit resources and the other half attend as observers.

Effective CAGs are small and powerful. Aim for seven to nine members. Each member must hold budget authority over their domain and the organizational standing to enforce decisions within their function. A regional vice president (VP) who cannot realign headcount or redirect discretionary spend is not the right CAG member, regardless of their seniority title.

The chief information officer (CIO) or chief technology officer (CTO) anchors the technology dimension. The chief financial officer (CFO) or a direct delegate anchors the investment dimension. Two or three senior business leaders from the functions most affected by the ERP — supply chain, finance, operations — complete the core group. The program sponsor chairs the group and holds the casting vote when consensus fails.

Structure Sessions Around Decisions, Not Updates

The fastest way to kill a CAG is to fill its agenda with status reports. Executives will tolerate one or two sessions of slide decks before they stop attending. Every CAG session must produce at least one binding decision or it has no value.

Structure each session around a pre-circulated decision brief. The brief states the issue, the options considered, the recommendation and the consequence of inaction. Members receive the brief 48 hours before the session. The session itself focuses on deliberation and resolution, not information transfer.

Limit sessions to 60 minutes. Frequency should match program velocity. During design and build phases, bi-weekly sessions are appropriate. During testing and cutover, weekly sessions may be necessary. Between major milestones, monthly sessions suffice. Adjust cadence deliberately rather than defaulting to a fixed schedule that outlives its usefulness.

Enforce Attendance Without Apology

Attendance is a governance problem, not a scheduling problem. If a CAG member consistently sends a delegate, the group loses the authority it was designed to exercise. Delegates rarely hold the decision rights their principals carry.

The program sponsor must address attendance directly and early. The governance charter should state that three consecutive absences trigger a membership review. This is not punitive — it is structural. A CAG member who cannot attend is signaling that the program does not rank among their priorities. The organization needs to know that and respond accordingly, either by escalating to the member’s superior or by replacing them with someone who can commit.

Some organizations use a formal attendance log that feeds into the program’s steering committee (SteerCo) report. When the SteerCo sees that a business unit’s representative has missed four of six sessions, it creates accountability at a level the CAG itself cannot generate.

Connect the CAG to the Change Impact Process

The CAG does not operate in isolation. It sits above the change impact assessment process and below the SteerCo. Changes to ERP configuration, process design or integration scope flow upward through the PMO’s change control log. The CAG reviews changes that breach defined thresholds — cost, schedule, strategic alignment — and makes the call.

This connection matters because it gives the CAG a steady stream of real work. The group is not convened to discuss abstractions. It reviews specific change requests with quantified impacts and makes decisions that the PMO then executes. That rhythm keeps members engaged because they see their decisions translate into program action within days.

Organizations that implement this model report fewer scope disputes at the workstream level. When functional leads know that unauthorized scope changes will surface at the CAG, they become more disciplined about managing their own boundaries. The CAG’s existence changes behavior even when it is not in session.

Align the CAG With the Broader Governance Stack

The CAG is one layer in a governance stack. Below it sits the PMO and the functional workstream leads. Above it sits the SteerCo and, in some organizations, a program board that includes board-level representation. The CAG must have defined escalation paths in both directions.

Decisions that exceed the CAG’s authority — major budget reallocations, program scope reductions that affect strategic objectives, vendor contract changes — escalate to the SteerCo. Decisions that fall below the CAG’s thresholds return to the PMO. This vertical clarity prevents the CAG from either overreaching or becoming a bottleneck for decisions it was never meant to own.

Internal alignment between the CAG and the organizational change management (OCM) function is equally important. The OCM team tracks stakeholder readiness and resistance. When resistance in a business unit reaches a level that threatens adoption, the CAG needs to know. The CAG can authorize interventions — executive communications, process redesign, additional training investment — that the OCM team cannot authorize on its own.

Measure the CAG’s Effectiveness

Governance bodies rarely measure themselves. That omission allows dysfunction to persist undetected until it is too late to correct. Build three metrics into the CAG’s operating model from the start.

Track decision cycle time — the elapsed time between a change request entering the log and the CAG issuing a resolution. A healthy CAG resolves standard items within two sessions. Track decision reversal rate — the proportion of CAG decisions that get reopened or overridden within 30 days. High reversal rates signal that the group is making decisions without adequate information or authority. Track attendance rate against quorum requirements. Below 80% sustained attendance, the CAG’s legitimacy erodes.

Review these metrics at the SteerCo level quarterly. If any metric trends in the wrong direction, treat it as a governance risk, not an administrative inconvenience.

Summary

An ERP Change Advisory Group (CAG) earns its place in the governance stack by making decisions, not by meeting. Design it around explicit decision rights, recruit members who hold real authority, structure sessions around pre-circulated decision briefs and enforce attendance as a governance requirement. Connect it to the change control process so it has a consistent flow of substantive work. Measure its performance and report those metrics upward. A CAG built on these principles becomes the organizational mechanism that keeps an ERP transformation on course when complexity and competing priorities threaten to pull it apart.