How to Build a Realistic ERP Implementation Plan in 2026 (Public Sector Guide)
Build a realistic ERP implementation plan for your city, county or district in 2026: workstreams, backfill, governance, phasing, milestone gates and go/no-go.
On this page
- Key takeaways
- What is an ERP implementation plan?
- How to build an ERP implementation plan in 2026: 7 steps
- Step 1: Map the ERP implementation workstreams
- Step 2: Build the staffing and backfill plan
- Step 3: Write an ERP project charter with a decision matrix
- Step 4: Choose your phasing strategy (phased vs big bang)
- Step 5: Set ERP implementation milestones as gates, not dates
- Step 6: Write the ERP contingency plan and go/no-go criteria
- Step 7: Plan the first 30 days post go-live and the support model
- Red flags that your ERP implementation plan is not realistic
- FAQ
- Bottom line
A realistic ERP implementation plan is not the Gantt chart your software vendor hands you at kickoff. For a city, county or school district, a working government ERP implementation plan is a set of seven artifacts: a workstream map, a staffing and backfill plan, a governance charter, a phasing decision, milestone gates, a contingency plan and a post go-live plan. If one of them is missing, your schedule is a guess.
Key takeaways
Your plan is seven artifacts, not one schedule. Dates come last.
Backfill key staff before kickoff, not after they burn out. Ellensburg, WA funded a temporary Finance position by council resolution for exactly this reason.
Write a decision matrix that says who decides what, and how fast.
Build go/no-go gates and a rollback or fix-forward plan into the schedule. Washington State University accepted a six-month delay at a go/no-go point and still landed a successful go-live.
Durations belong in a timeline, not here. For how long each phase usually takes, use the KCT ERP implementation timeline guide.
Consider Washington State. Its new core financial system was originally planned to launch by June 30, 2022, according to the State Auditor. In September 2026 the program baselined Phase 1A with a go-live range of April to October 2028.
The auditor tied the early delays to scoping and the complexity of getting agency legacy systems to talk to Workday. Those are planning problems, not effort problems.
Many “ERP implementation plan” guides are written for private companies and stop at a phase list. They skip fiscal year-end, council cycles and the fact that payroll touches every employee.
Below, you will see what each artifact contains, who should own it and the public sector traps to plan around. KCT plans and runs public sector implementations as an embedded team, and each step draws on that work and recent public audits.
What is an ERP implementation plan?
An ERP implementation plan is the government’s own operating plan for delivering a new ERP: who does the work, who decides, what goes live together, how readiness is proven and what happens if it isn’t. The vendor’s project schedule is one input to that plan. It is not a substitute for it.
The GFOA ERP Readiness Checklist frames readiness the same way. It covers written governance roles, staff availability, the implementation approach, quality assurance and payment tied to milestones. Little of that lives in a vendor workbook.
Swipe to see all columns →
| Vendor project schedule | Agency ERP implementation plan |
|---|---|
| Tasks for vendor consultants | Staffing, backfill and who covers each day job |
| Configuration and build sequence | Governance charter and decision matrix |
| Vendor workshop dates | Blackout dates: year-end, audit, budget season |
| Vendor deliverables | Readiness gates with evidence and sign-off owners |
| Go-live date | Go/no-go criteria, rollback or fix-forward, post go-live support |
If your only plan today is the vendor’s workbook, start the agency plan now.
How to build an ERP implementation plan in 2026: 7 steps
Map the workstreams and name an owner for each.
Build a staffing and backfill plan before kickoff.
Write a governance charter with a decision matrix.
Decide your phasing strategy.
Set milestone gates tied to deliverables and the fiscal calendar.
Write the contingency plan, including go/no-go criteria.
Plan the first 30 days post go-live and the long-term support model.
Step 1: Map the ERP implementation workstreams
Break the project into parallel workstreams, each with a named government owner and vendor counterpart. Then plan the connections between them, because integration is where plans quietly fail.
Washington’s program is a clear warning. An October 2024 Gartner quality assurance report found that the state finance office and agencies operated in “parallel” without sufficient interaction, The Spokesman-Review reported.
Ownership also has to be real. GFOA advises confirming each project role with the individual and with their department, not just writing a name on an org chart.
Swipe to see all columns →
| Workstream | Typical government owner | What it produces |
|---|---|---|
| Finance, general ledger and chart of accounts | Controller or accounting manager | Approved chart of accounts, GL design, close process |
| Procurement and accounts payable | Purchasing manager | Approval workflows, vendor master, PO rules |
| HCM and payroll | HR director and payroll lead | Pay rules, benefits setup, position control |
| Utility billing (if in scope) | Utility billing manager | Rate tables, billing cycles, customer accounts |
| Data conversion | Finance or IT data lead | Conversion specs, mock loads, reconciliations |
| Integrations and interfaces | IT applications lead | Interface inventory, tested connections |
| Testing | Test lead (often a business analyst) | Test scripts, defect log, exit reports |
| Training and change management | HR or training coordinator | Training plan, user materials, communications |
| Technical and security | IT director or security lead | Roles, access, environments, security review |
| Project management office | Internal project manager | Schedule, risk log, status reporting |
The workstream nobody owns: end-to-end testing
Every workstream tests its own piece, but few plans name someone to test a whole process, like a requisition flowing through purchasing, AP and the GL. Name one owner for end-to-end tests, with authority to pull in any workstream lead.
Your action: write the workstream list, put a single name on each row and hold a weekly 30-minute cross-workstream stand-up (KCT rule of thumb).
Step 2: Build the staffing and backfill plan
One of the most common unrealistic assumptions in an ERP implementation project plan is that staff can run the project on top of their day jobs. Plan backfill before kickoff.
Guidehouse ranks under-committing resources as the first of five common ERP missteps. Its warning: when the new system lands on top of existing work, staff find “nothing has come off their plate.” Plante Moran makes the same point: staffing subject matter experts may require backfilling roles or cross-training staff.
The City of Ellensburg, WA planned for this. Through Resolution No. 2025-17, adopted in August 2025, the council created a long-term temporary Finance position for its ERP transition, using funds already set aside in its 2024 and 2025-2026 biennial budgets. Both of the city’s advisors recommended hiring before implementation begins, so the new hire is trained and ready to backfill key staff.
GFOA’s checklist suggests possible job changes for project team members, such as flex scheduling, leave policies, titles and supervisors. It also tells governments to expect roughly 5 to 20 consultants on the team for two-plus years, depending on project size.
Who to backfill first
KCT rule of thumb: backfill the people whose day jobs can’t pause and whose knowledge the project needs most:
Finance and accounting leads who own the GL and month-end close
The payroll lead
The utility billing lead, if billing is in scope
The internal project manager, who should be close to full time on the project
Blackout dates and a capacity calendar
Mark the hard walls before scheduling any workshop: fiscal year-end, audit fieldwork, budget season, open enrollment and W-2 season.
GFOA’s checklist includes a step to identify blackout dates for key staff. Washington’s auditor flagged what happens otherwise: end-user training was scheduled when staff are busy with year-end activities such as reconciling accounts. Fiscal staff might not have the capacity to be trained.
Fund backfill in the budget request, not later
Adding positions mid-project means a new council item and a hiring cycle, so put backfill in the original ask.
Your action: build a person-by-person capacity sheet showing time on the project, who covers each day job and when backfill starts.
Step 3: Write an ERP project charter with a decision matrix
ERP project governance works in three layers: an executive sponsor and steering committee, a project management office and workstream leads. Tie them together with a written ERP project charter and a decision matrix that says who decides what, and how fast.
GFOA calls for a formal written description of roles, responsibilities and expectations for each level of governance. Per GFOA, the charter should cover:
Meeting frequency and required communications
Issue resolution, with separate paths for internal issues and contract issues with the vendor
Resource commitment
Which group makes which decisions (the decision matrix)
Decision speed matters. Washington’s auditor pointed to the University of Washington’s Workday rollout, where an inadequately defined cutover plan and delaying critical decisions contributed to significant disruptions. After a yearlong delay and a $71 million budget increase, the university’s costs reached $340 million.
A simple decision matrix might look like this. The deadlines are a KCT rule of thumb, so set your own and write them down.
Swipe to see all columns →
| Decision | Who decides | Escalation deadline (KCT rule of thumb) |
|---|---|---|
| Chart of accounts design | Finance director, with steering committee approval | 10 business days |
| Customization request | Steering committee | Next scheduled meeting |
| Go-live date change | Executive sponsor, on steering committee recommendation | Before the next go/no-go gate |
| Scope moved to a later phase | Steering committee | 5 business days |
| Vendor deliverable acceptance | Workstream lead plus project manager | Per the contract acceptance window |
Where council fits
Your council or board approves the contract and budget, and usually sets the change order threshold. Put that threshold and a reporting cadence (quarterly, as a KCT rule of thumb) in the charter. Change control board mechanics are in the KCT scope guide.
Independent quality assurance
Plante Moran calls a project structure with executive sponsorship, department leads and a PMO “paramount for project success”. It also advises larger organizations to strongly consider professional project oversight. GFOA’s checklist lists a quality assurance process and sign-off as readiness items.
QA can come from internal audit, an advisor or a third party (Washington used Gartner). What matters is that QA reports to the steering committee.
Your action: draft the charter and decision matrix before vendor kickoff, and have the steering committee sign it at its first meeting.
Most agencies write this plan while also running payroll and closing the books. KCT’s Full-spectrum ERP Implementation team builds and runs these plans alongside your staff, from workstream setup through the first 30 days post go-live and beyond.
Step 4: Choose your phasing strategy (phased vs big bang)
Decide what goes live together and in what order based on dependencies, the fiscal calendar and team capacity. Don’t simply accept the vendor’s default sequence.
KCT’s work with the City of Oxnard, CA is a good example. KCT took over a stalled multi-module replacement for a city of about 200,000 and planned deliberately split go-lives: Finance, then HCM, then EPL. Each cutover was proofed and rehearsed before the next, and all three are now live.
As KCT program manager Erwin Limon puts it, a combined go-live makes every module’s risk every other module’s problem.
Swipe to see all columns →
| Approach | Best when | Main risk | Planning implications |
|---|---|---|---|
| Big bang | Small scope, tightly linked modules, strong team capacity | One failure affects every department at once | Heavier rehearsal, larger hypercare team, firm rollback plan |
| Phased by module | Multiple modules with clear dependencies (finance first) | Temporary interfaces between old and new systems | Plan and test bridge interfaces; repeat cutover per phase |
| Phased by department or agency | Large counties or states with many departments | Two systems of record for a period | Reporting and reconciliation across both systems |
Anchor go-lives to the fiscal calendar
KCT rule of thumb: put finance go-lives at the start of a fiscal year or period, and payroll at a calendar year or quarter boundary. Clean boundaries simplify conversion and tax reporting.
Your action: write a one-page phasing decision memo for the steering committee. Cover options, dependencies and the recommended sequence.
Step 5: Set ERP implementation milestones as gates, not dates
ERP implementation milestones should be evidence-based gates. Design signed off, mock conversion reconciled, user acceptance testing exit criteria met, payroll parallel passed. Tie each gate to a SOW deliverable and, where possible, a payment.
GFOA recommends a payment schedule based on completion of milestones, backed by a sign-off process. In Guidehouse’s view, most organizations need at least three full cycles of data migration testing before go-live.
Write exit criteria before testing starts. In Washington, agencies and testers disagreed on what counted as a pass or fail. Some readiness tests only showed that legacy systems could share data with Workday, not that they would work after launch.
Swipe to see all columns →
| Milestone gate | Evidence required | Who signs off |
|---|---|---|
| Design and fit-gap complete | Signed design documents, open gaps logged with decisions | Workstream leads, steering committee |
| Chart of accounts approved | Final COA, crosswalk from legacy accounts | Finance director |
| Mock conversions 1, 2 and 3 reconciled | Balances and record counts tie to legacy, variances explained | Data conversion lead, controller |
| Integrations tested end to end | Every interface run with real-format data | IT applications lead |
| UAT exit | Scripts passed, no open critical defects | Test lead, business owners |
| Payroll parallel passed | Gross-to-net matches legacy within agreed tolerance | Payroll lead, HR director |
| Go/no-go | All criteria in Step 6 met or formally waived | Executive sponsor, steering committee |
For how to run the payroll gate, see the guide to ERP parallel testing before go-live. Match these gates to your contract deliverables; the public sector ERP implementation SOW guide shows what to check.
Your action: replace every date-only milestone in your plan with a gate that names its evidence and its approver.
Step 6: Write the ERP contingency plan and go/no-go criteria
A realistic plan assumes something will slip, and it says in advance what happens next. That means schedule float, people contingency, written go/no-go criteria and a rollback or fix-forward plan.
Washington’s auditor found that as of July 2024, One Washington and the state finance office had not yet finalized contingency plans or go/no-go criteria. The audit’s recommendation was direct: finalize contingency plans and set clear go/no-go decision points in the project schedule.
The same audit offers a better example. Washington State University implemented a Workday financial system in 2020 with go/no-go decision points built into its design timeline. No-go decisions delayed the project six months, but waiting to resolve issues led to a successful implementation overall.
Plante Moran advises identifying a source of contingency funds during the initial planning process, for overruns such as extra training, staff backfill or new interfaces. Grand Rapids, MI reported $4.7 million in change orders on a $4.8 million initial implementer budget (November 2025 steering committee update), which is why the reserve belongs in the original plan. How to hold and report that reserve is covered in the KCT scope guide.
Rollback vs fix-forward
Washington’s deployment strategy describes two contingency types. Rollback stops cutover and restores legacy systems. Fix-forward resolves issues without reverting. The strategy itself notes that rolling back is “complicated, time consuming, and error prone.” Write both paths, and the point of no return between them, into your ERP cutover plan.
Swipe to see all columns →
| Contingency type | When to use it | What you must prepare in advance |
|---|---|---|
| Rollback | A critical failure during cutover, before the new system becomes the system of record | Legacy kept intact, a defined point of no return, a tested restore procedure |
| Fix-forward | Issues appear after go-live but core processes still run | Workarounds for payroll and payments, a staffed issue triage team, vendor escalation contacts |
What go/no-go criteria should cover
Agree on these before UAT starts. Treat any thresholds as a KCT rule of thumb, not a standard.
Final mock conversion reconciled, with variances explained and accepted
No open critical defects, and high defects have documented workarounds
Payroll parallel within the agreed tolerance
Users trained and access provisioned for their roles
Support desk staffed and the triage process tested
Legacy system available in read-only mode for lookups
Communications ready for staff, vendors and, where needed, residents
People contingency
Washington’s auditor listed turnover of program staff as a risk to agency readiness. Cross-train a second person on every critical role and document design decisions.
Your action: put go/no-go dates into the schedule now.
Step 7: Plan the first 30 days post go-live and the support model
Go-live is a milestone in your plan, not the end of it. Staff the first 30 days post go-live, the first close, the first payroll cycles and long-term support.
GFOA advises sketching the long-term support model before the project starts, so the project can produce documentation and train support staff. Its warning: “Waiting until go-live is too late.”
Grand Rapids frames its project in three phases: Initiation, Adoption and Routinization. For the post go-live phases, it lists implementation KPIs such as support ticket volume and user adoption rate.
In Oxnard, KCT stood up a tiered L0 to L2 support desk within weeks.
Your post go-live plan should name:
Hypercare staffing and duration
Issue triage and vendor escalation
The owner of the first close
Who reviews each payroll run before it posts
KPIs: ticket volume, open critical issues, close time and adoption
Your action: name the support owner and the KPIs in the plan today, not the week before cutover.
Red flags that your ERP implementation plan is not realistic
Three or more of these signs means the plan needs work before the next steering committee. Fixes are a KCT rule of thumb unless sourced.
Swipe to see all columns →
| Red flag | What it usually means | Fix |
|---|---|---|
| No backfill line in the budget | Staff will run the project on top of full day jobs | Fund backfill in the original request (Step 2) |
| The vendor schedule is the only plan | Agency work, decisions and readiness are untracked | Build the agency plan around the seven artifacts |
| Go-live or training lands in year-end or audit fieldwork | Key staff won’t have capacity (as Washington’s auditor found) | Mark blackout dates and move the work |
| No decision matrix | Decisions stall and the schedule absorbs it | Charter with owners and deadlines (Step 3) |
| Milestones without exit criteria | Pass and fail will be argued later | Gates with evidence and approvers (Step 5) |
| No go/no-go or rollback plan | The go-live date can’t move safely | Contingency plan and criteria (Step 6) |
| Post go-live isn’t staffed | Users hit problems with nowhere to go | Hypercare and support owner (Step 7) |
| All modules go live at once with no rehearsal | Every module’s risk is tied to every other module | Rehearse cutover or split go-lives (Step 4) |
FAQ
What should an ERP implementation plan include?
It should include seven artifacts: workstreams, staffing and backfill, a governance charter, phasing, milestone gates, contingency with go/no-go criteria and post go-live support. Dates come after those are settled.
Who should be on an ERP implementation team?
An ERP implementation team needs an executive sponsor, a steering committee, an internal project manager and a lead for each workstream, from finance and payroll to data conversion, testing and training. Each lead should have a vendor counterpart and confirmed time on the project.
What is the role of a steering committee in an ERP implementation?
The ERP steering committee makes cross-department decisions: scope, customizations, phasing, go-live dates and escalations. It approves the charter, receives independent QA reports and makes the final go/no-go call with the executive sponsor.
Should you do a phased or big bang ERP implementation?
A phased ERP rollout suits most governments with several modules, because each cutover can be proofed and rehearsed before the next. Big bang can work for small, tightly linked scopes, but one failure then hits every department at once, so it needs heavier rehearsal and a firm rollback plan.
What are go/no-go criteria for ERP go-live?
Go/no-go criteria are the written conditions for cutover: reconciled conversion, no open critical defects, payroll parallel within tolerance, trained users and a staffed support desk. Each needs a named owner and evidence, and the steering committee should approve them before user acceptance testing begins.
How do you backfill staff during an ERP implementation?
Fund temporary positions to cover key project members’ day jobs, and hire before implementation begins so they are trained in time. Start with finance, payroll, utility billing and the internal project manager.
How long does an ERP implementation take?
ERP implementation duration depends on agency size, module count, phasing and staff capacity, so a realistic plan sets gates first and dates second. The KCT ERP implementation timeline guide breaks down typical ranges by agency size and phase.
Do you need outside help to build an ERP implementation plan?
Outside help isn’t required, but many agencies use it because staff are stretched running payroll, close and budget alongside the project. The right level of support depends on your modules, departments and stakeholders, so start with an assessment; KCT can support at any point.
Bottom line
A realistic public sector ERP implementation plan names people, decisions and fallback paths before it names dates. Washington’s slip and WSU’s six-month pause make the same point: the plan that admits uncertainty early is the one that holds.
Before your next steering committee meeting, check whether you can produce all seven artifacts. The ones you can’t are your real risks.
If you want a second set of eyes on your plan before the steering committee signs it, start with an ERP health check, or talk to our Full-spectrum ERP Implementation team about building and running the plan with your staff.