Council Approved Your ERP Project: The 2026 ERP Project Kickoff Plan for the First 90 Days
Council approved your ERP. Here is a 2026 ERP project kickoff plan for the first 90 days: contract execution, charter, team backfill, kickoff and comms plan.
On this page
- Key takeaways
- What happens after council approves an ERP project? (2026 answer)
- First 30 days: ERP contract execution and locking down what you bought
- Write the ERP project charter before the vendor’s kickoff
- Days 31 to 60: build the ERP project team and backfill the people you pull
- Days 61 to 90: run an ERP project kickoff that sets the rules
- Build the ERP communications plan for 2026: council, staff and residents
- Common mistakes in the first 90 days after council approval
- Who should run the project on your side?
- FAQ
- Conclusion: the first 90 days set the terms for the next three years
Council approved your ERP project. Now the real work starts, and the next 90 days decide whether the project runs on your terms or the vendor’s. In the first 30 days you execute the contract and write the project charter. By day 60 you have a named, backfilled team and a working steering committee, and by day 90 you have held your ERP project kickoff and launched a communications plan for council, staff and residents.
Scope can start moving sooner than many finance teams expect. The City of Little Rock, Arkansas offers a clear example. Its Board of Directors authorized the initial Oracle Fusion implementation agreement on March 17, 2026, and by August 18, 2026 had a change order on the agenda adding modules to the project. Five months in, scope was already moving.
Many kickoff guides are written for private companies. They skip council resolutions, insurance certificates, board updates and what backfill looks like in a civil-service environment. Below is a sourced 30/60/90-day ERP implementation plan built for cities, counties, school districts, special districts and utilities.
Key takeaways
ERP council approval authorizes a contract. Contract execution, insurance certificates and a notice to proceed still have to happen.
Write your own project charter before the vendor’s kickoff deck sets the agenda.
GFOA’s governance template expects an agency project manager at 30 to 40 hours a week during implementation, so plan backfill now.
Virginia’s IT procurement guidance recommends a contract kickoff within 30 days of award, and says kickoff is not the place to change contract terms.
Scope moves after approval (Little Rock added modules within five months; Fresno removed modules years in). Stand up change control in month one.
What happens after council approves an ERP project? (2026 answer)
Council approval authorizes staff to sign a contract. It does not start the project. After the vote, you execute the contract, write a project charter, seat governance and a project team, hold the kickoff and launch communications. Only then do discovery and design begin.
The gap between the vote and real work can be months. El Paso County, Colorado selected Oracle Fusion for financials, HR and payroll in an earlier phase, then issued a separate RFP for an implementation provider on January 22, 2026. That RFP lists contract award in “Spring 2026” and an estimated implementation start in “Fall 2026.”
The project itself is long. Little Rock’s council report says the conversion will take 18 to 36 months. What you do in the first 90 days sets the habits for all of it.
The first 90 days at a glance
Swipe to see all columns →
| Window | Goal | Key outputs | Owner |
|---|---|---|---|
| First 30 days | Execute the contract and charter the project | Signed contract with all exhibits, insurance certificates, contract abstract, change-control rules, draft charter | Sponsor, procurement, finance, city or county attorney |
| Days 31 to 60 | Build the team and governance | Named project manager, steering committee, functional leads, RACI, backfill plan per department | Sponsor, HR, department heads |
| Days 61 to 90 | Kick off and communicate | Internal kickoff, joint ERP project kickoff, decision log, status report format, communications calendar | Agency project manager with the vendor PM |
Treat these windows as a sequence, not a law. If your vendor can start sooner, compress them. For the full multi-year picture after kickoff, see our guide to the ERP implementation timeline.
First 30 days: ERP contract execution and locking down what you bought
The first month is paperwork that protects you. You want a fully executed contract with every exhibit attached, insurance certificates on file, key personnel confirmed and a clear rule for how changes get approved. Skip this and the first dispute becomes an argument about which version of the SOW is real.
Get the contract fully executed
A council vote often authorizes the city manager or county administrator to sign. Someone still has to route signatures, attach the SOW, pricing schedule and service terms, and collect insurance certificates. Virginia’s IT procurement manual lists “review and coordination of any required insurance and insurance certificates” as a standard post-award kickoff item, and the checklist travels well beyond Virginia.
Then build a one-page contract abstract and give it to finance, accounts payable and the project manager. Include:
The contract term and payment milestones
Any holdback or retainage
Named key personnel
The change-order approval threshold
Acceptance windows for deliverables
Most people on the project will never read the full contract. They will read one page.
Hold back and pay on acceptance
Payment terms are your strongest lever, and they only work if staff know them. When Superior, Wisconsin approved Oracle NetSuite for Government and UKG on December 16, 2025, the city said it would retain 10% of both contracts until the project is complete. Put holdback amounts and acceptance dates in your abstract so AP never pays a milestone that has not been accepted.
If you negotiated staffing assumptions and a key personnel clause before the vote, now you turn them into checks. Your job is to confirm the named people actually show up.
Know whether you signed one contract or two
Many agencies buy software from one party and implementation from another. El Paso County bought its Oracle modules through Mythics, then ran a separate RFP for the implementer. It required bidders to contractually agree to implement the functionality confirmed against the software reseller’s earlier response.
Two contracts means two sets of obligations and a gap between them. Map who owns each item:
Subscription and environments
Configuration
Data conversion and integrations
Testing and training
Post-go-live support
Any task with no owner will land on your staff by default.
Stand up change control before anyone asks for a change
Scope will move. Little Rock’s August 2026 change order added Sourcing and Inventory Management, Recruiting Booster, and implementation work for the LRCVB and a retiree benefit program. That came about five months after approval.
Scope can shrink too. On October 30, 2025, Fresno, California, approved an amendment that removed HR, payroll and utility billing modules from its 2021 Tyler agreement, with a $150,000 credit toward future SaaS fees or modules over three years.
Both cases show that what council approves is not frozen. Decide now who can approve a change, up to what dollar amount, and when it goes back to council. Our guide on keeping a public sector ERP project on scope walks through the full change process.
Write the ERP project charter before the vendor’s kickoff
An ERP project charter is the short document that authorizes the project and states its goals, scope, governance, decision rights, and resource commitments. Your sponsor signs it, and your team writes it. If you wait for the vendor’s template, you get the vendor’s priorities.
Agencies that take this seriously write their principles down. El Paso County’s implementation RFP lists guiding principles such as standardizing on best practice, implementing with clean data, and using “strong governance to involve the right people at the right time, with effective decision-making and communication.”
The county, which runs two charts of accounts today, also says it has already redesigned its chart of accounts ahead of the project. That is exactly the kind of decision a charter should settle up front.
What to put in the charter
Measurable goals tied to what the council report promised, such as replacing an unsupported system or closing faster.
Scope by module and phase, with an explicit “out of scope” list.
Guiding principles, including how you will treat customizations and legacy reports.
Governance and decision rights.
Who decides what, and how fast.
Staffing commitments, including the backfill plan for every pulled role.
Risks and assumptions, such as fiscal year-end timing or a pending labor agreement.
Communication cadence, including how often council gets an update.
Success measures for go-live and the first months after it.
KCT rule of thumb: keep the charter under about 10 pages and get the sponsor’s signature on it before the joint kickoff. A charter nobody signs is a suggestion.
Days 31 to 60: build the ERP project team and backfill the people you pull
The project will consume your best people, so the real question is what happens to their day jobs. Answer it in this window. HR approvals, civil-service lists and union consultation take time, and design sessions will not wait.
GFOA’s standard ERP governance model (an undated project roles template written for a county) puts real numbers on the commitment:
Swipe to see all columns →
| Role (GFOA template) | Readiness hours per week | Implementation hours per week |
|---|---|---|
| Steering committee member | 2 to 3 | 2 to 3 |
| Project manager | 15 to 20 | 30 to 40 |
| Accounting lead | 15 to 20 | 25 to 40 |
| Payroll lead | 15 to 20 | 20 to 40 |
| HR lead | 15 to 20 | 20 to 40 |
| Procurement and payables lead | 15 to 20 | 20 to 40 |
| Budget lead | 15 to 20 | 15 to 30 |
| Subject matter experts | As needed | 5 to 10 |
Look at the payroll lead row. Up to 40 hours a week on the project means someone else is running payroll. If nobody plans for that, the project loses, the day job loses, or both.
The cost of getting this wrong can be enormous. Auditors Grant Thornton reviewed Birmingham City Council’s Oracle program in the UK and cited “the failure to properly invest in ERP implementation capacity and capability,” along with turnover in key program roles. The Register reported in February 2025 that the estimated total cost had risen from about £19 million to £108 million.
Different country, same lesson.
Name a full-time project manager on your side
GFOA’s template describes the agency project manager as the “primary point of contact with vendor” and the person who “reviews and accepts deliverables.” Those are your protections. If that person is also running the budget office, deliverables get accepted because nobody had time to push back.
Seat a small ERP steering committee with real authority
GFOA suggests a “small group (5-7 people)” that “assures staff and resources for the project” and approves changes to scope, schedule and budget. That is the core of ERP project governance. Pick people who can actually move staff and money. A committee that only receives updates is an audience, not governance.
Choose your backfill options
Temporary or contract staff for routine processing work.
Overtime for short peaks, not as the whole plan.
Shifting non-essential work or deferring lower-priority projects.
Promoting from within on an acting basis, then backfilling the junior role.
Outside help for specialized tasks such as data cleanup.
KCT rule of thumb: have backfill in place before design sessions start, and keep it through the first fiscal close on the new system. Before kickoff, fill out a simple RACI and a one-page backfill plan for each department.
Many agencies hit the same gap here. You have a signed contract and a vendor project manager, but nobody on staff whose only job is to protect your side of the deal.
KCT’s ERP Consulting & Selection Advisory team can act as your owner’s representative from charter through kickoff and beyond. KCT is not a Tyler partner or reseller and takes no referral fees from Tyler.
Days 61 to 90: run an ERP project kickoff that sets the rules
Kickoff confirms how the project will run. It is not a renegotiation and it is not a sales demo. Walk in with your charter signed, your team named and your contract abstract in hand.
Virginia’s procurement manual recommends that “within 30 days of contract award, a contract kickoff meeting be conducted”. On the agency side it lists the procurement lead, contract manager, business owner or project manager and technical leads. On the supplier side it lists the project or account manager, contract manager and key technical staff.
The same chapter says kickoff “should not be used to change the terms of the contract.” If the execution and staffing work above pushes the full kickoff past 30 days, split it. KCT rule of thumb: hold a short contract-review meeting within 30 days of award, then run the full project kickoff once your team is in place.
ERP project kickoff checklist (kickoff meeting agenda)
Review contract terms, payment milestones and the deliverable acceptance process.
Confirm roles and key personnel on both sides, by name.
Confirm the schedule, milestones and blackout dates: budget adoption, fiscal year-end, payroll year-end, W-2 and 1099 season.
Agree on the status reporting cadence and the escalation path.
Walk through the change-control process you set in the first 30 days.
Confirm data conversion owners and the date of the first mock load.
Confirm environment setup and user access for the project team.
Agree on the communications plan and who speaks for the project.
Run two kickoffs, not one
KCT rule of thumb: hold an internal kickoff first. Your sponsor, project manager and functional leads align on the charter, the decision rights and the hard dates. Then hold the joint kickoff with the vendor, so you show up as one team with one set of answers instead of debating priorities in front of the implementer.
Afterward, send minutes and start a decision log within a few days. Virginia’s guidance calls for a memo to the file after kickoff that lists open items, owners and due dates. Whatever you call it, write down what was agreed while everyone still remembers it the same way.
Build the ERP communications plan for 2026: council, staff and residents
An ERP communications plan serves three audiences with different messages on different clocks. Council needs regular, predictable status. Staff need to know what changes for them and when, and residents only need to hear about it when it touches them.
GFOA’s template gives the steering committee the job to “communicate project throughout the organization” and provide periodic updates to the governing board. El Paso County’s RFP asks bidders to describe their organizational change management approach up front.
Elected officials watch these decisions closely. Superior’s council approved the software unanimously but split 9 to 1 on the implementation oversight contract, with the dissenting councilor objecting that it had not gone out to bid.
Council and board
Pick one status format and use it every time. Cover:
Schedule against plan
Spend against the approved amount
Change orders, tied to your approval thresholds
Top risks and decisions needed
Council should see every change that crosses its line. No surprises is the whole goal.
Employees
Tell supervisors first, then everyone else. Set up an internal project page with an FAQ and a plain timeline of what changes for each department.
Be honest about what is not decided yet. Our guide on managing staff resistance to new ERP software covers the people side in more depth.
Residents and vendors
Wait until the change touches them: a new utility billing statement, a vendor self-service portal or a payment method change. KCT rule of thumb: do not announce public go-live dates until design is done. A missed date announced to residents costs more trust than a late announcement.
Your action: build a one-page communications calendar for the first two quarters, with audience, message, channel and owner for each entry.
Common mistakes in the first 90 days after council approval
In KCT’s experience, many early problems in a government ERP implementation are not technical. They are decisions nobody made on time. Here are the ones we see most, with the fix for each.
Disciplined sequencing pays off later. Since 2021, KCT has led Oxnard, California’s previously stalled multi-module ERP replacement, with deliberately split go-lives: Finance, then HCM, then EPL. The Oxnard case study has the details.
Who should run the project on your side?
Someone on staff has to own your side of the contract full time. The vendor’s project manager may be excellent, but they work for the vendor. Your project manager accepts deliverables, enforces the contract and keeps the steering committee honest.
GFOA’s template puts deliverable acceptance with the agency project manager. Superior went a step further and hired an outside firm for oversight and advisory services during implementation. The mayor compared the role to a construction manager on a building project.
You have two realistic models:
KCT does both, through ERP Consulting & Selection Advisory and Full-spectrum ERP Implementation. What that support looks like depends on your modules, departments and stakeholders. The right starting point is a short assessment of where your project stands.
FAQ
What happens after an ERP contract is signed?
After an ERP contract is signed, the agency attaches every exhibit, collects insurance certificates, sets change control, writes a project charter, names a project manager and steering committee, backfills pulled staff and holds a kickoff with the vendor. Discovery and design come next. KCT rule of thumb: in government, expect this to take about 60 to 90 days.
What should be included in an ERP project kickoff meeting?
An ERP project kickoff meeting should review contract terms and acceptance, confirm roles and key personnel, confirm the schedule and blackout dates, agree on status reporting and escalation, walk through change control, confirm data conversion owners and set the communications plan. Virginia’s guidance adds that kickoff should not change contract terms.
What is an ERP project charter?
An ERP project charter is a short document, signed by the executive sponsor, that authorizes the project. It states goals, scope, guiding principles, governance, decision rights, staffing commitments, risks and success measures. The agency should write it, not the vendor, and finish it before the joint kickoff.
How long after contract signing does ERP implementation start?
ERP implementation usually starts weeks to months after contract signing. El Paso County, Colorado planned a spring 2026 award and a fall 2026 start. KCT rule of thumb: budget about 60 to 90 days for execution, staffing and kickoff. Our ERP implementation timeline covers what follows.
Do you need to backfill staff during an ERP implementation?
Backfilling staff during an ERP implementation is necessary in most agencies. GFOA’s governance template expects the project manager at 30 to 40 hours a week and most functional leads at 20 to 40 hours a week during implementation. Few departments can absorb that without temporary staff, overtime or deferred work.
How long does a government ERP implementation take?
A government ERP implementation often takes one to three years, depending on modules and phasing. Little Rock expects 18 to 36 months for its Oracle Fusion conversion. Superior, Wisconsin expected about one year for accounting and nine months for HR and payroll.
Conclusion: the first 90 days set the terms for the next three years
The council vote is permission, not progress. The agency that executes the contract cleanly, writes its own charter, staffs the team and runs a disciplined kickoff ends up owning the project. The agency that waits gets handed someone else’s plan.
So start this week. Name your project manager and sponsor, draft the charter before the vendor’s kickoff deck arrives, and put change control in writing before anyone asks for a change.
If you want an experienced owner’s representative in your corner for those first 90 days, talk to KCT’s ERP Consulting & Selection Advisory team. If you would rather have one partner carry delivery from kickoff through go-live, see Full-spectrum ERP Implementation. Either way, contact KCT and start with a short assessment of where your project stands.