How to Govern Your ERP Vendor During Implementation in 2026: A Public Sector Playbook
ERP project governance for cities and counties in 2026: set up a steering committee, status cadence, RAID log, deliverable acceptance and key personnel rules.
On this page
- Key takeaways
- What is ERP project governance (and how is it different from project management)?
- How to govern your ERP vendor during implementation in 2026: 7 steps
- Step 1: Stand up an ERP steering committee that can actually decide
- Step 2: Set a status report cadence and define what “green” means
- Step 3: Run a RAID log the agency owns
- Step 4: Control deliverable acceptance (and never pay ahead of it)
- Step 5: Treat key personnel changes as governance events
- Step 6: End every phase with a go/no-go gate based on evidence
- Step 7: Report to council on a schedule, not in a crisis
- When ERP implementation governance is not enough
- Common ERP project governance mistakes in 2026
- FAQ
- Final words
Most ERP vendors don’t fail in one dramatic moment. They drift: one accepted deliverable, one unchallenged “green” status and one swapped consultant at a time. ERP project governance is what stops the drift.
In a public sector ERP implementation, governance is the structure your agency uses to make decisions, track risks and accept or reject vendor work during implementation. In practice, that means five things: a small steering committee with real authority, a fixed status cadence, a RAID log the agency owns, written deliverable acceptance, and control over who the vendor puts on your project.
Key takeaways
Keep the steering committee small (GFOA’s governance template suggests 5 to 7 people) and staff it with people who can actually decide.
The agency owns the RAID log, the status criteria and the acceptance decision. The vendor contributes. It doesn’t grade itself.
Define green, yellow and red in writing before the first status report arrives.
No deliverable gets paid until a named agency person accepts it against written criteria.
Any vendor staffing change is a governance event, not an FYI.
Every phase ends with a go/no-go vote based on evidence, not optimism.
KCT plans and leads public-sector implementations as well as advising on them.
Audits keep finding the same gap: the agency lets the vendor run the meetings, track the risks and report the status. In a review of the city’s land management software rollout, Dallas’s City Auditor noted that “Management places reliance on vendors to communicate and track weekly meetings and changes” (Dallas Office of the City Auditor, August 2024).
Below are seven steps to set up in the first month of implementation, with what to put on each agenda and in each report. This is the proactive side of ERP vendor management. If your vendor is already missing dates, start with what to do when your ERP vendor isn’t delivering instead.
What is ERP project governance (and how is it different from project management)?
ERP project governance is the set of decision rights, oversight forums, escalation paths and acceptance rules that an agency uses to control an implementation and hold the vendor accountable. Project management is the day-to-day execution of the plan. In short, governance decides what happens and whether work is accepted, while project management delivers it.
GFOA’s Standard ERP Governance Model template draws the line clearly. During implementation, the steering committee provides general oversight, makes key policy decisions, approves changes to scope, schedule and budget, and resolves escalated issues. The project manager is the “primary point of contact with vendor” and “reviews and accepts deliverables.” Functional project team members work with vendor consultants daily and approve completion of testing for their area.
Notice who’s missing from the decision column: the vendor. Its project manager attends and recommends. The agency decides.
Who does what
Swipe to see all columns →
| Role | Who | Time commitment | Decides |
|---|---|---|---|
| Steering committee | Small senior group (5 to 7 people, per GFOA) | 2 to 3 hours per week, as needed (GFOA) | Scope, schedule and budget changes; policy; escalated issues; stage gates |
| Agency project manager | One dedicated person | 30 to 40 hours per week in implementation (GFOA) | Deliverable acceptance; day-to-day priorities; what goes to steering |
| Functional leads | Finance, HR, payroll, utilities and other module owners | Up to 20 to 40 hours per week, depending on the module (GFOA) | Testing sign-off and data validation for their function |
| Vendor project manager | Vendor’s named lead | Full time on the project (KCT rule of thumb) | Nothing on the agency’s behalf. Attends, reports and recommends (KCT rule of thumb) |
Your action: write a one-page governance charter in week one. Name each role, the person in it, an alternate, and who signs what.
How to govern your ERP vendor during implementation in 2026: 7 steps
To govern your ERP vendor during implementation, set up these seven controls in the first month and run them until the system is stable:
Stand up a steering committee with real decision authority.
Fix a status cadence and define what green means in writing.
Run a RAID log that the agency owns.
Control deliverable acceptance and tie it to payment.
Treat key personnel changes as governance events.
End every phase with an evidence-based go/no-go gate.
Report to council on a schedule, not in a crisis.
Step 1: Stand up an ERP steering committee that can actually decide
Your ERP steering committee should be small, senior and empowered to approve changes to scope, schedule, budget and staffing. When a member leaves, refill the seat right away. An empty seat on a steering committee is a decision nobody can make.
Dallas learned that the hard way. In its August 2024 interim audit of the DallasNow land management software implementation (contracts totaling about $8.25 million), the City Auditor found that leadership changes “have left a void in the DallasNow Governance Committee. The void impacts decision-making, direction, clarity, and expectations of and from the vendor.” The recommendation: reestablish the committee with current personnel who have the authority to make key decisions.
GFOA’s 5 to 7 people fits most cities. Large programs need more seats: Florida’s statewide PALM financial system is governed by an Executive Steering Committee of 17 members representing multiple state agencies, per the Florida Auditor General’s February 2026 report. A city or county can stay much smaller.
Who sits on it
A typical city or county steering committee looks like this (KCT rule of thumb):
Executive sponsor (city or county manager, or a deputy) as chair
Finance director or CFO
HR director
IT director
The department head for the heaviest operational module, such as utilities or public works
Agency project manager, as non-voting secretary
Vendor executive sponsor, invited to present, not to vote
What it decides (and what it doesn’t)
The committee approves change requests above the project manager’s threshold, votes on stage gates, resolves staffing escalations and settles policy questions. It doesn’t debate configuration screens.
If you don’t have a separate change control board for smaller changes, set one up so steering time goes to decisions that matter.
Your action: name an alternate for every seat, and add a two-minute “membership check” as a standing first agenda item.
Step 2: Set a status report cadence and define what “green” means
Hold a weekly working status meeting, a steering meeting every two to four weeks, and require a written vendor report every month. Then write down what green, yellow and red mean before the first report arrives. Otherwise, the vendor will.
Here’s why. In Birmingham, England, an auditor’s review reported by The Register in February 2025 found that cash management was rated “Green” in reports to the council’s Steering Committee, even though some testing was incomplete because the system wasn’t stable. The auditors found “no evidence of suppliers adequately drawing the Steering Committee’s attention to” that uncertainty.
Nevada does it differently.
Plante Moran’s July 2025 monthly IV&V report on the State’s CORE.NV program defines Green, Yellow and Red for scope, schedule, cost and resources in plain sentences. Schedule is green only when “the schedule is progressing as planned, with all critical path milestones and deadlines being met.” Yellow means it isn’t progressing as planned, though critical path milestones are still being met. No room for interpretation.
A governance cadence that works
Swipe to see all columns →
| Forum | Who attends | Cadence (KCT rule of thumb) | Inputs | Outputs |
|---|---|---|---|---|
| Working PM meeting | Agency PM, vendor PM, functional leads as needed | Weekly | Task plan, RAID updates, acceptance log | Action items, items to escalate |
| Steering committee | Voting members, agency PM, vendor sponsor | Every two weeks during build and testing, monthly otherwise | Status report, top RAID items, change requests | Decisions, approvals, gate votes |
| Vendor monthly status report | Written by vendor, reviewed by agency PM | Monthly | Agency-defined template | Steering packet |
| Council or board update | Executive sponsor, finance director | Quarterly and at each stage gate | One-page summary | Public record, budget direction |
What to require in the vendor’s monthly ERP project status report
Nevada publishes its integrator’s reports, which makes them a handy model. CGI’s June 2025 monthly status report for CORE.NV includes:
Overall status with a Green / Yellow / Red legend
Change requests approved during the month
Vendor staff onboarded and offboarded, by role
A risk register and heat map, with the open risk count (11 that month)
A decisions log showing active and recently closed decisions
Deliverables submitted or approved by the State
A 30, 60 and 90-day look-ahead of upcoming deliverables
Add one more line that Saskatchewan’s auditor found missing. The Provincial Auditor’s 2025 report on monitoring IT projects said progress reports “did not calculate differences between planned and revised budgets and schedules.” Require three columns for both dates and dollars: original baseline, current forecast and the variance between them.
The same audit found the province didn’t consistently receive progress reports for two of four projects tested, even though both were late and over budget. The fix it recommended: follow up when a monthly report doesn’t arrive.
Your action: put the green, yellow and red definitions and the report template in your governance charter. Chase any late report that week, and sanity-check the vendor’s phase dates against a realistic ERP implementation timeline.
Step 3: Run a RAID log the agency owns
A RAID log is a single register of Risks, Assumptions, Issues and Dependencies, each with a named owner, a due date and a status. The vendor’s tool can host it. The agency owns it, reviews it and decides when an item is closed.
Nevada’s integrator reports that “Project Risks and Project Issues are logged and maintained in Jira,” with a heat map in each monthly report (CGI, June 2025). That’s fine. What matters is who acts on it.
In Dallas, the auditor found that the City’s program assurance consultant had flagged medium risks “trending toward high risk which are not being addressed by the City,” including integration, user acceptance testing plans and infrastructure (Dallas City Auditor, 2024).
Staleness is the other failure. A 2019 Gainesville City Auditor report noted that the ERP team set up a RAID file in early 2017, but it hadn’t been updated with an assessment of risks during the ongoing procurement.
What each RAID entry needs
ID and short description
Type: risk, assumption, issue or dependency
Owner: a named person, and whether they’re agency or vendor
Impact and probability (Saskatchewan’s auditor expects both for key risks, plus mitigation)
Mitigation or resolution plan
Due date and current status
Escalation level: PM, steering or executive
Assumptions and dependencies hide schedule risk
Vendor plans assume clean data, available experts and ready interfaces. When those break, the schedule slips and the vendor points to the assumption.
Log them as RAID items with agency owners. Plante Moran’s Nevada IV&V report flagged one that’s easy to miss: “Significant staff time off during the period leading up to cutover and go-live is impactful” (Plante Moran, July 2025).
Your action: review the top 10 RAID items at every steering meeting. Anything open past two review cycles escalates one level (KCT rule of thumb).
Step 4: Control deliverable acceptance (and never pay ahead of it)
Every deliverable should be accepted or rejected by a named agency person, against written criteria, within a set review window. Payment follows acceptance. Never the other way around.
GFOA’s template puts acceptance with the agency project manager, who “reviews and accepts deliverables,” while functional teams approve testing completion for their own areas (GFOA). Nevada’s vendor report tracks deliverables “submitted or approved by” the State, including the State’s acceptance of training materials.
Dallas shows what happens when that step gets skipped. The auditor found that “Phase acceptance approvals and evaluation are not completed,” and recommended an analysis of project status (time, scope, cost and resources) “without the intervention of vendors” (Dallas City Auditor, 2024).
The acceptance criteria themselves belong in your contract. If you’re still negotiating, see how to write acceptance criteria and key personnel in your SOW. This step is about operating those clauses once the project starts.
A simple acceptance log
Swipe to see all columns →
| Deliverable | SOW reference | Accepting owner | Submitted | Review due | Accepted or rejected | Payment milestone released |
|---|---|---|---|---|---|---|
| Chart of accounts design | SOW 4.2 | Finance director | Date | Date | Rejected: missing fund crosswalk | No |
| Payroll parallel test results | SOW 6.1 | Payroll lead | Date | Date | Accepted | Yes |
Your action: don’t let anything slide into “deemed accepted” by silence. Log every rejection in writing, with the reason and the criteria it missed.
Most agencies don’t have a full-time project manager who has already walked a vendor through design, build, testing and cutover. KCT’s Full-spectrum ERP Implementation team can run the governance layer alongside your staff: steering prep, status review, the RAID log and the acceptance log. Your people keep the decisions, and we keep the structure running.
Step 5: Treat key personnel changes as governance events
Any change to the vendor’s named project manager, solution architect or functional leads should go to the steering committee with a written transition plan. Govern your own staffing the same way, because agency turnover hurts just as much.
Nevada’s integrator lists staff onboarded and offboarded by role in every monthly report (CGI, June 2025). That’s the standard to require.
The agency side needs equal attention. Dallas’s governance void came from the City’s own leadership changes, not the vendor’s.
Your project manager and functional leads carry up to 30 to 40 hours a week of project work (see the roles table). If they leave, the project loses capacity the vendor can’t replace.
Your action: require a monthly staffing roster in the vendor’s status report and keep one for your own team. Before any vendor swap, ask for overlap time and documented knowledge transfer.
Step 6: End every phase with a go/no-go gate based on evidence
Stage gates are where ERP project governance has teeth. At the end of each phase, the steering committee votes on whether the project is ready to move forward, based on written exit criteria and evidence, not the vendor’s confidence.
Florida PALM is a good model of gates in action. According to the Florida Auditor General (February 2026), the state’s Executive Steering Committee passed Stage Gate 1 (Ready to Start Build) in November 2023 and Stage Gate 2 (Ready to Begin System Testing) in August 2024.
Then schedule delays hit, and the committee vote planned for July 2025 on Stage Gate 3 (Ready to Begin UAT) was postponed. In October 2025, the project moved go-live from July 2026 to January 2027. The committee has since approved full agency user acceptance testing from February 2026 through October 2026.
A delay is uncomfortable. A forced go-live is worse.
Birmingham shows the other path. Per The Register’s 2025 coverage of the auditor’s findings, suppliers backed the April 2022 go-live even though testing was incomplete. Their caveats were “only identified in the supporting detail to Steering Committee reports.”
The council now faces a potential £130 million bill to complete its ERP replacement, against an initial estimate of around £20 million.
Go/no-go exit criteria to require at each gate
Open defects by severity, with zero critical defects for go-live
Test scripts executed and passed, as a percentage of the plan
Data conversion reconciliation results, signed by the functional owner
Results of parallel testing for payroll and other high-risk processes
Training completion for affected users
RAID items tagged as gate blockers, all closed
Cutover rehearsal completed, with timings
Your action: ask the vendor to sign a written readiness statement at each gate. Any caveats go in the main body, on page one, not in an appendix.
Step 7: Report to council on a schedule, not in a crisis
Your council or board should hear budget, schedule and change-order status at fixed intervals and at every stage gate. Scheduled reporting is what turns vendor accountability into a public record instead of a surprise.
GFOA’s template has the steering committee provide periodic updates to the governing board. Grand Rapids shows what that transparency looks like. Its November 2025 ERP update lays out original and amended costs side by side:
Swipe to see all columns →
| Contract | Initial budget | Change orders to date | New projected total | Paid to date |
|---|---|---|---|---|
| Highstreet (implementation partner, 5 years) | $4.8 million | $4.7 million | $9.5 million | $8.3 million |
| Oracle Fusion Cloud (software, 3 years) | $2.0 million | $180,105 | $2.18 million | $1.7 million |
Anyone can see those figures, and that’s the point. Cumulative change orders should be a standing steering item that reaches council on a schedule.
Your action: build a standard one-page council update with four blocks:
Dates: planned versus current forecast for each go-live
Dollars: original budget, change orders to date, projected total, paid to date
Top risks: the three to five biggest RAID items and their owners
Decisions needed: anything that requires council action
When ERP implementation governance is not enough
Good governance prevents a lot of drift and surfaces the rest early. But if a vendor keeps missing dates, rejected deliverables come back unchanged, or key people keep leaving, escalate under the documented path in your contract.
If you’ve followed the seven steps, you already have the paper trail: status reports, RAID history, rejection notes and steering minutes. From there, follow our guide on what to do when your ERP vendor isn’t delivering, which covers the escalation ladder, cure notices and stalled projects.
Common ERP project governance mistakes in 2026
The most common ERP project governance mistakes all hand control back to the vendor. These come up again and again in audits:
FAQ
These are the questions public sector teams ask most often about ERP project governance and vendor oversight.
What is ERP project governance?
ERP project governance is how an organization makes decisions, oversees the vendor, manages risk and accepts work during an ERP implementation. It typically includes a steering committee, a status reporting cadence, a RAID log, a deliverable acceptance process and stage gates.
Who should be on an ERP steering committee?
An ERP steering committee for a city or county should include an executive sponsor, the finance director, HR director, IT director and the department head for the biggest operational module (KCT rule of thumb). The agency project manager and vendor sponsor attend but shouldn’t vote.
How often should an ERP steering committee meet?
An ERP steering committee should meet every two weeks during build and testing, and monthly during quieter phases (KCT rule of thumb). Add extra sessions before each go/no-go gate.
What is a RAID log in an ERP project?
A RAID log is a single register of Risks, Assumptions, Issues and Dependencies on the project. In public-sector ERP projects, the agency should own it and review the top items at every steering meeting, even if the vendor’s tool hosts it.
What should a vendor’s monthly status report include?
A vendor’s monthly status report should include overall status against written green, yellow and red criteria, planned versus forecast dates and dollars, change requests, staffing changes, the risk register, a decisions log, deliverables and a 30, 60 and 90-day look-ahead. Nevada’s published CORE.NV reports are a practical model.
Does a city need independent verification and validation (IV&V)?
Independent verification and validation (IV&V) gives a city an assessment that doesn’t come from the integrator. Nevada uses Plante Moran for IV&V on CORE.NV, and Dallas contracted Gartner Consulting for program assurance. Whether a city needs it depends on project size, risk and internal capacity. Smaller projects may get similar value from a periodic ERP Health Check.
Final words
The vendor brings the software and the method. Your agency brings the decisions. ERP project governance is how you keep those decisions in your hands, from the first design session to the last cutover.
Set up the charter, the cadence, the RAID log and the acceptance log before design starts. They are much harder to build in month twelve, when the vendor’s version of events is the only one on record.
That’s the approach behind our work in Oxnard, where KCT has led the implementation as an embedded member of the city team since 2021, with deliberately split go-lives for Finance, then HCM, then EPL, each cutover rehearsed before the next.
If you want that structure running on your project, talk to us about Full-spectrum ERP Implementation. Already mid-project and not sure your governance is working? Start with an ERP Health Check to see where your oversight has gaps.