Change Order

TL;DR

A change order is the lightweight contractual instrument used to record agreed adjustments to scope, schedule, or fees within the existing structure of a Statement of Work. It operates under the SOW’s change-control clause and is typically signed by project sponsors or program managers rather than the original SOW signatories. Change orders are used for tactical changes (scope clarifications, milestone shifts, small fee adjustments) that fit within the SOW’s existing intent. Material changes (term extensions, scope expansions outside the change-control envelope, fee-structure changes) require a formal SOW amendment instead. Both are legally binding when properly executed, including electronically under the federal E-SIGN Act (15 USC 7001, https://www.law.cornell.edu/uscode/text/15/7001).

What Is a Change Order?

A change order is a written, signed instrument used to record agreed adjustments to an existing Statement of Work. It operates under the change-control clause of the parent SOW, which sets the procedural framework: who can sign, what changes are permitted, how fees and schedule are recalculated, and what documentation is required.

Change orders are the operational tool that prevents scope creep from collapsing fixed-price engagements. A well-functioning SOW has a clear scope, and inevitable real-world adjustments (the customer wants two extra wireframes, a milestone slips by ten days, a deliverable is clarified after discovery) get documented as change orders. Without change orders, those adjustments either get absorbed silently by the contractor (eroding margin and goodwill) or get fought about after the fact (damaging the relationship and creating disputes).

Change Order vs SOW Amendment

The two terms are sometimes used interchangeably in casual conversation, but in well-drafted contracts they are distinct.

Change order. Project-level instrument. Operates under the SOW’s change-control clause. Typically signed by project sponsors or program managers. Used for tactical changes within the SOW’s existing intent.

SOW amendment. Contract-level instrument. Formally modifies the SOW document. Signed by signatories with equivalent authority to the original SOW (usually executives or department heads). Used for material changes outside the change-control clause’s permitted scope.

The line between the two is set by the SOW’s change-control clause itself. Most clauses permit change orders within the existing scope envelope (clarifications, refinements, modest expansions, schedule slips, small fee adjustments) and require an amendment for material changes (term extensions, scope expansions outside the original intent, fee-structure changes, alterations to legal protections incorporated from the parent MSA).

Structure of a Market-Standard Change Order

A market-standard change order is concise (usually one to two pages) and contains five elements.

Identification. The original SOW number, execution date, parties, and parent MSA reference. A short reference line such as “Change Order No. 3 to Statement of Work dated 15 January 2026 between Customer Inc. and Contractor LLC under the Master Service Agreement dated 10 December 2025.”

Description of the change. A narrative paragraph or numbered list describing what is being changed. Common patterns: “Add the following deliverable: customer onboarding email sequence, comprising five emails delivered as HTML and plain-text drafts.” Or: “Move the Milestone 3 due date from 28 February 2026 to 14 March 2026.”

Fee impact. A stated number (positive, negative, or zero) and the calculation method. Three common approaches:

• Time and materials. “Additional 32 hours at the SOW hourly rate of $150 per hour, total fee impact +$4,800.”
• Fixed-fee increment. “Flat additional fee of $4,500 for the added deliverable.”
• Percentage of original. “10 percent of the original SOW fee of $50,000, total fee impact +$5,000.”

The change order should record both the new total fee and the calculation method, so both parties can audit the change post-execution.

Schedule impact. Revised milestone dates or deliverable due dates, including any downstream effects on subsequent milestones.

Signature blocks. Signed by the project-level signatories authorised under the SOW’s change-control clause. Electronic signature is the operational default and is legally valid under the federal E-SIGN Act (15 USC 7001, https://www.law.cornell.edu/uscode/text/15/7001) and corresponding state-law UETA frameworks.

Common Scope-Clarification Examples

Change orders most often handle three patterns:

Scope clarification. The SOW says “build a customer onboarding flow.” After discovery, the contractor and customer agree on six specific screens. The change order memorialises the six screens as the operative deliverable list, with no fee or schedule impact. This is a zero-fee change order, and it is one of the most valuable types because it prevents later disputes about what was actually agreed.

Modest scope expansion. The customer requests two additional wireframes mid-project. The change order adds the two wireframes to the deliverable list and records a fee impact (for example, +$2,400 calculated as 16 hours at $150/hour).

Schedule adjustment. The customer is late providing source data, pushing Milestone 2 back by ten business days. The change order revises the Milestone 2 due date and any downstream milestone dates. The change order may also revise the SOW’s final completion date and any client-side payment trigger dates.

Descope. The customer no longer needs Deliverable 4. The change order deletes Deliverable 4 from the SOW and records a fee reduction. Descope change orders are valuable because they prevent the contractor from doing work that will not be paid for and the customer from being billed for work they no longer want.

When a Change Order Is Not Enough

If the change touches terms outside the SOW’s change-control clause’s permitted scope (extending the SOW term, adding a new work-stream materially outside the original intent, altering fee structure beyond what the change-control clause permits, or modifying legal protections from the parent MSA), a change order is the wrong instrument. The right instrument is a formal SOW amendment signed by the same signatories who executed the original SOW.

A change order that purports to do amendment-level work can be challenged later as exceeding the authority granted by the change-control clause. The cost of executing an amendment is modest. The cost of an unenforceable scope change discovered in dispute is large.

How Omnivoo Helps

Omnivoo’s Contract Management workflow includes built-in change order templates linked to their parent SOW, with structured fields for description, fee impact, schedule impact, and calculation method. The platform tracks change orders sequentially under each SOW, flags when a proposed change exceeds the SOW’s change-control clause and should be an amendment instead, and integrates electronic signature for E-SIGN-compliant execution. The audit trail captures every change order against the SOW’s running scope, fee, and schedule baseline so finance teams see the actual project state at a glance.