How to Handle Change Orders on a Government ERP Project in 2026
Learn how to evaluate, price, fund and win council approval for ERP implementation change orders in 2026, with real city council examples and a 7-step process.
On this page
- Key takeaways
- What is a change order on a government ERP implementation?
- How to handle ERP implementation change orders in 2026: 7 steps
- How do you avoid ERP scope creep through change orders?
- Common change order mistakes on government ERP projects
- FAQ: ERP implementation change orders
- The bottom line
Handling ERP implementation change orders on a government project comes down to one discipline. Every change gets a written impact estimate, a check against the signed statement of work (SOW), a named funding source, and approval at the level your charter, purchasing ordinance or state law requires, all before any work starts.
Then it gets logged against the original award.
Key takeaways
No work starts before written approval at the right authority level. An email from the project manager is not an approval.
Classify every request first: added scope, time-only, zero-dollar reallocation, de-scope, or agency-driven support. A vendor deficiency is not a change order at all.
Check the vendor’s math and require a signed amendment. Fresno, CA had to bring a change request back to council because an amount on the Tyler summary was incorrect.
Track cumulative change orders against the original award. Allentown, PA’s January 2026 change order would take a $791,980 contract to $1,237,336.
Know your delegated limits. In May 2024, Tumwater, WA’s Finance Director asked council for authority to approve change orders up to 10% of the total contract. Texas law sets its own dollar limits and a 25% cap for many city contracts.
A change order is not an invoice you’re being asked to pay. It’s a decision you’re being asked to make, usually with a price already attached and a deadline someone else picked.
KCT advises on and implements public sector ERP for cities, counties, school districts and special districts. Our team sits on the government’s side of the table when vendor change orders arrive, and the same patterns repeat across projects and platforms.
Most guidance on this topic is about preventing change orders. That matters, but real projects get them anyway, and many start on the agency’s own side.
Tumwater’s first modules went live in April 2023 with the project on time and under budget. The city still needed a time-only amendment in November 2023 and a second amendment of about $35,000, after heavy staff turnover and problems with its HR and payroll module.
Below is a 7-step process to evaluate, price, fund, approve and close out a change order, built on real city council records from 2023 to 2026.
A note on scope. Still writing the contract? Start with our guide to a public sector ERP implementation SOW. Want to stop scope growth before it starts? Read how to keep a public sector ERP project on scope.
This post is for the change order already on your desk.
What is a change order on a government ERP implementation?
ERP implementation change orders are formal, signed amendments to the implementation contract or statement of work that change scope, price, schedule or resources. On a government project, a change order also needs a funding source and approval from whoever holds that authority, which is often the city council, county board or school board.
This post covers changes to the implementation contract. Many ERP products also have a “change order” feature for construction or purchasing, which is a different topic.
Change order vs change request
A change request is the proposal: what the vendor or the agency wants to change, plus an estimate of the impact. A change order is the approved, executed amendment that makes it binding.
Fresno shows both stages. In February 2023, the city council approved a “Project Change Request” to its Tyler agreement that removed a data conversion subcontractor and moved $151,000 to consultant hours and travel.
Two months later, the city came back with Amendment 2. The staff report says it corrected the earlier request, which “had an incorrect amount and was missing an amendment document.”
Treat the request as the start of the conversation, never the end of it.
The five kinds of change order you’ll see
Not every change order is a request for more money. Sorting them by type tells you which questions to ask and who needs to sign.
Swipe to see all columns →
| Type | What changes | Real example | Who usually approves |
|---|---|---|---|
| Added scope | New modules, services or deliverables, usually with new cost | Little Rock, AR (Aug 2026): not to exceed $178,870 for Sourcing, Inventory Management and other added items | Governing body, unless under a delegated limit |
| Time-only extension | Schedule moves, price does not | Tumwater, WA: Amendment 1 approved in November 2023 “for time only” | Depends on local rules; often council if the contract term changes |
| Zero-dollar reallocation | Money moves between line items, total stays the same | Fresno, CA (Apr 2023): $161,400 reallocated from removed conversion scope to hours and travel | Often still the governing body, as in Fresno |
| De-scope with credit | Modules or services removed, fees voided or credited | Fresno, CA (Oct 2025): HR, payroll and utility billing removed, with a $150,000 credit toward future fees | Governing body, since the contract changes |
| Agency-driven support | Extra vendor hours to cover a gap on the agency’s side | Milton, GA (Jul 2025): added remote hours after the former finance director departed | Governing body or delegated official, by amount |
| Vendor deficiency (not a change order) | Delivered work failed acceptance or doesn’t meet the SOW | Fix under warranty or acceptance terms | No approval needed: the vendor already owes it |
Before anyone talks about price, label every incoming request with one of these types. That one label shapes the rest of the process.
How to handle ERP implementation change orders in 2026: 7 steps
The change order process has seven steps: check the SOW, classify the request, test the price, fund it, route it to the right approver, write the staff report and execute the signed amendment. Here it is in one view:
Check the request against the signed SOW and contract baseline.
Classify it, and reject anything that is really a vendor deficiency.
Demand a written impact estimate, then test the price.
Decide the funding source: contingency or new appropriation.
Route it to the right approval level.
Write a staff report council can approve in one read.
Execute the amendment, then log and close it.
Each step below covers what to decide, a real example and what to do next.
Step 1: Check the request against the signed SOW and contract baseline
Before you discuss price, decide whether the work is already owed. Some requested “changes” turn out to be work the vendor agreed to deliver at signing.
GFOA’s ERP Readiness Checklist calls for planning that produces “an accurate and relevant scope” worked out with the vendor and documented in the SOW, and it walks through data conversion, interfaces, modifications, forms and workflow scope.
That document is your measuring stick. If yours is thin, our SOW guide shows what a strong one includes.
Pull three things: the SOW section the request touches, the assumptions list and the exclusions list. Then write one line at the top of the request: in scope, out of scope or ambiguous.
Step 2: Classify it, and reject anything that is really a vendor deficiency
If the change exists because delivered work failed acceptance, it’s a defect, not a change order. You shouldn’t pay twice for the same deliverable.
Use the table above to label the request. “Ambiguous” items deserve a real negotiation, not an automatic yes, because the vendor wrote the estimate and benefits when gray areas get priced as new scope.
Next move: ask the vendor, in writing, to cite the SOW clause or assumption the request relies on. A clear request can answer that in one sentence.
Step 3: Demand a written impact estimate, then test the price
No estimate, no evaluation. A usable estimate names:
The scope and deliverables.
Hours by role.
A fixed or not-to-exceed amount.
Schedule impact and dependencies.
Any effect on SaaS or subscription fees.
Good public examples exist. Little Rock’s August 2026 change order split fixed fees by module group ($130,150 and $48,720) and paired the services change with a companion resolution amending the Oracle subscription.
Milton’s July 2025 memo separated $2,557 in prorated SaaS from $6,300 in services, for a total of $8,857. It also listed extra remote hours separately, with a not-to-exceed amount of $9,800, billed only if used.
Vendor summaries can be wrong, as Fresno’s April 2023 correction shows. Reconcile every number yourself against the contract’s pricing exhibit, and ask one more question: what does this cost if we defer it to Phase 2?
For the line items that tend to hide in ERP pricing, see how to avoid hidden costs in an ERP vendor contract.
Since most of these examples involve Tyler, a quick note: KCT is not a Tyler partner or reseller and takes no referral fees from Tyler.
Step 4: Decide the funding source, ERP project contingency vs new appropriation
Contingency is for the unknowns inside approved scope. Genuinely new scope, such as a new module, should be weighed as new scope even when contingency could technically cover it.
The law can force the issue. For Texas cities, Local Government Code Sec. 252.048(b) bars increasing the contract price through a change order unless money for the added cost is appropriated or provided through time warrants.
Your state’s rules will differ, but the principle holds: no funding line, no change order.
How much contingency is enough? KCT rule of thumb: size it to risk, not to a single percentage. Projects with many interfaces, poor legacy data, lots of departments or heavy customization need more room than a clean financials-only rollout.
Our on-scope guide covers how to track contingency burn over the life of the project.
Write the funding line before you write the approval memo. Include the account, the contingency remaining after this draw and the cumulative change orders to date.
Need a second set of eyes on a change order? KCT’s Full-spectrum ERP Implementation team sits on the government’s side, reviews the estimate against the contract and manages the vendor through the change. In Oxnard, CA, KCT has led a multi-module ERP program since 2021, handling vendor relationship management and escalation through split go-lives for Finance, then HCM, then EPL.
Step 5: Route it to the right approval level and council approval threshold
Approval authority comes from your charter, purchasing ordinance and state law. It does not come from the signature block on the vendor’s form.
Here’s how that plays out in practice:
The GFOA checklist also says your project charter should define “which group makes which decisions (decision matrix)”. Change orders belong in that matrix.
Map your change order approval thresholds once, then stop debating them on every request. The template below is a KCT rule of thumb, not legal advice, so fill in the limits with your purchasing office and attorney:
Swipe to see all columns →
| Approval level | Typical authority (fill in your limits) | What it covers |
|---|---|---|
| Project owner | Zero-dollar changes inside one workstream | Task swaps, minor schedule shifts with no contract change |
| Steering committee | Draws on approved contingency up to a set amount | Unknowns inside approved scope |
| Manager under delegated authority | Up to the limit your ordinance, council action or state law allows | Small priced change orders with funding in place |
| Council or board | Anything above delegated limits, new scope or new funding | New modules, large increases, term changes, de-scopes |
If you already run a three-level change control board, as described in our on-scope guide, this table plugs straight into it.
Then plan around the agenda cycle. Packet deadlines can land weeks before the meeting, and that lag belongs in your project schedule.
Step 6: Write the staff report council can approve in one read
A clear staff report for council gets approved on consent. A vague one gets pulled for discussion, and that delay lands on your project.
Milton’s memo is a solid model. It covers a summary, the reason for the change, funding and financial impact, an alternative (“renegotiate specific terms”), a procurement summary, financial and legal review and the attached change order.
Fresno’s 2025 memo stated its reason plainly: the city faced “significant challenges” configuring HR to its required processes.
Use this checklist for your own report:
What changes, in one or two plain sentences.
Why now, and what happens if the council says no.
The cost and the funding source.
Cumulative change orders to date compared with the original award.
Schedule impact, including any go-live date that moves.
Alternatives considered, including “defer” and “do nothing.”
Who reviewed it: finance, legal, IT and the project sponsor.
Step 7: Execute the ERP contract amendment, then log and close it
The change isn’t real until a signed amendment exists and the change log is updated. A council vote on a summary isn’t the same thing as an executed contract.
Fresno learned this in public. Its February 2023 change request lacked an amendment document and carried an incorrect Tyler amount, so in April 2023 the city brought back Amendments 2 and 3.
The corrected reallocation was $161,400, not $151,000. Amendment 3 moved another $58,400 from data conversion services the city no longer needed.
Make three rules stick:
No work before signature.
Update the change log every time: number, type, amount, cumulative total, percent of original award, schedule effect, approver and date.
Review the log at every steering meeting, and close the order only when the deliverable is accepted.
How do you avoid ERP scope creep through change orders?
You avoid scope creep through change orders by treating them as a portfolio, not a stream of one-off approvals. Each small yes looks reasonable alone. The total is what breaks budgets.
A few habits that are specific to change orders:
For the full prevention method, from scope baselines to contingency burn reporting, see how to keep a public sector ERP project on scope.
Common change order mistakes on government ERP projects
Most change order problems come from skipped steps, not bad intent. These are the ones that show up most often:
The cost of getting this wrong is real. In May 2019, TechTarget reported that the Manatee School District’s ERP project in Florida had climbed from about $10 million to $26 million. The report cited change orders, insufficient project staffing, delayed decisions and customizations, and noted the state auditor general had listed the change orders behind the increase.
FAQ: ERP implementation change orders
What is a change order in an ERP implementation?
A change order in an ERP implementation is a signed amendment to the implementation contract or SOW that changes scope, price, schedule or resources. On a government project, it also needs a funding source and approval from the official or governing body that holds authority under your charter, ordinance or state law.
What is the difference between change orders and change requests?
A change request is the proposal, with a description and an impact estimate. A change order is the approved, executed amendment that binds both parties. Fresno’s 2023 records show why the distinction matters: the city approved a change request, then had to come back with a formal amendment because the request lacked one.
Who approves a change order on a government ERP project?
Approval for a government ERP change order depends on your charter, purchasing ordinance and state law. Small changes may fall under a manager’s delegated authority, such as the 10% Finance Director limit Tumwater staff requested in 2024. Larger changes, new scope and new funding usually go to the council or board.
Confirm your limits with your attorney.
How much contingency should an ERP project carry for change orders?
ERP project contingency should be sized to risk, not set at one flat percentage. KCT rule of thumb: more interfaces, messier legacy data, more departments and more customization all call for more room. Keep contingency for unknowns inside approved scope, and treat new modules as new decisions.
Our on-scope guide covers burn-rate tracking.
Can a change order reduce scope or cost?
Yes, a change order can reduce scope or cost. In October 2025, Fresno removed HR, payroll and utility billing from its Tyler agreement, voided outstanding implementation invoices for HR and payroll, and received a $150,000 credit over three years toward future fees. De-scoping is a legitimate option when a module isn’t working.
Should the vendor start work before a change order is approved?
No, the vendor shouldn’t start work before a change order is approved and signed. Early work weakens your negotiating position, can commit funds that haven’t been appropriated, and may violate your purchasing rules. If timing is tight, plan around the agenda cycle or use delegated authority within its limits.
The bottom line
Change orders are a normal part of public sector ERP. Unexamined change orders are the problem. Every one deserves a classification, a tested price, a funding source and an approver with real authority.
Start this week. Pull your change log and put two numbers side by side: the cumulative change order total and the original award. Then check that total against your delegated limit.
If you can’t produce either number quickly, that’s your first fix.
If change orders are stacking up, start with an ERP Health Check, or talk to KCT about Full-spectrum ERP Implementation support. The right level of help depends on your modules, departments and stakeholders, so we start with an assessment, and KCT can step in at any point in the project.