Change orders and amendments on technology contracts

Reference article · 5 min read

Every implementation of any size produces requests to do something other than what the contract says. Some are genuine additions, some are the agency discovering what it actually meant, and some are the vendor discovering that the work is harder than it bid. Change control exists to sort these apart, price the ones that are real, and record the result so it survives audit and staff turnover.

Scope change, clarification, or defect

Most mid-project arguments are really about which of three categories a request falls into. The three are priced very differently.

• Scope change. Work that adds to, removes from, or materially alters what the contract requires. The vendor is entitled to be paid for it, and the agency to decide whether it is worth the money.
• Clarification. A requirement already in the contract, written loosely enough to leave room for interpretation. Detailing it is not new work, though a written interpretation stops both sides relitigating it.
• Defect correction. Delivered work that does not meet a requirement the contract already imposes. Warranty work, at the vendor's cost.

Settle the question from the contract documents rather than from memory: the statement of work, the requirements matrix, the vendor's proposal as incorporated, and approved design documents. If a requirement appears in the matrix, satisfying it is not a change. If it appears only in a demo or a meeting recollection, the agency's position is weaker. A schedule extension with no price change is still a change.

From change request to signed amendment

1. Written change request. Either party may raise one, stating what is requested, why, and who asked for it.
2. Impact analysis. The vendor states the effect on deliverables, schedule, price, and staffing, including downstream effects on interfaces, testing, and support.
3. Classification and pricing. The agency decides whether this is a change at all, then prices it against the contract's rate schedule.
4. Approval at the correct level, then a written change order or amendment signed before work begins.
5. Baseline update. Schedule, requirements matrix, payment schedule, and acceptance criteria move with it. A change that never reaches those documents returns as a dispute at acceptance testing.

Agencies use the two instruments differently, so read your own policy. A change order commonly operates inside the existing contract, signed by a designated official within preset limits. An amendment modifies the contract itself and usually requires the same formalities as the original.

Approval authority and funding

Authority comes from statute, ordinance, and purchasing policy, and tiers differ by agency. The structure is usually familiar: a project manager or department head approves small changes, a purchasing agent or chief administrative officer a larger tier, and the governing body anything above the formal threshold, anything extending the term, and anything raising the total beyond the appropriation.

Funds must be appropriated and encumbered before an amendment is signed, not after. A grant funded project may also need the funder's prior approval, and those rules change, so confirm them with the grant manager.

When changes add up to a new contract

Watch the cumulative total, not only the change in front of you. A series of individually reasonable changes can reach the point where the work is materially different from what was advertised and competed, which procurement law generally treats as outside the scope of the original award. The warning signs: modules no bidder was asked to price, a value grown by a large multiple, a term extended well past the original period, or new departments never in the solicitation. The remedy is to compete the added work rather than keep amending.

Undocumented work becomes a payment dispute

Someone on the agency side asks for something, the vendor is cooperative, work proceeds on a handshake, and an invoice arrives months later. The agency now holds an invoice with no approved scope, no encumbrance, and often no official who had authority to order the work. Public agencies generally cannot pay outside an approved contract, and staff cannot bind the agency beyond the authority delegated to them. The result is an unpaid vendor, a ratification item on a public agenda, and an audit finding.

When something is genuinely urgent, issue a short written notice to proceed with a not to exceed amount, signed by someone holding the authority, and follow it with the full amendment. The answer is never verbal direction.

The record an auditor will ask for

Keep one central change log for the project, and for each change retain:

• The original written request, dated, with the requester identified
• The impact analysis and the agency's classification decision, with reasoning where it found the work already required
• The price basis: labor categories, hours, and rates tied to the contract rate schedule
• The funding source, appropriation, and encumbrance
• Evidence of approval at the correct level, including agenda item and minutes where the governing body acted
• The executed amendment, the updated baseline documents, and a running total against the original award

What to require in the contract

• A change control clause requiring written requests, setting an impact analysis turnaround, stating the pricing basis, and barring any work without written authorization.
• Labor categories and rates fixed for the term, so changes are priced against competed rates.
• A warranty and defect clause separate from change control, so correcting delivered work cannot be repackaged as a paid change.
• An order of precedence clause incorporating the requirements matrix and approved design documents.

On a project already underway without this discipline, put every open verbal request in writing, classify each one, and reconcile the cumulative total before approving anything new.

HQT works with agencies as an owner's technical representative on implementations, including review of vendor change requests and impact analyses.

Frequently asked questions