Free Word download β’ Edit online β’ Save & share with Drive β’ Export to PDF
A Change Order is a legally binding written amendment to an existing contract that formally documents and authorizes modifications to the original scope of work, contract price, or project schedule. It is executed by both parties β typically the project owner or client and the contractor or service provider β before any modified work begins, and once signed it becomes part of the contract record. Change orders arise in every project-based industry: construction, software development, engineering, architecture, and professional services all rely on them to keep contracts accurate as real-world conditions evolve from what was originally anticipated.
Unlike an informal email approval or a verbal instruction to proceed, a properly drafted and signed change order creates enforceable obligations on both sides β the owner is obligated to pay the adjusted amount, and the contractor is obligated to deliver the modified scope within the revised timeline. It also establishes a contemporaneous record of why the change occurred, which party initiated it, and on what basis the price was calculated, all of which become essential if a payment dispute or delay claim arises later in the project.
Proceeding with work outside the original contract scope without a signed change order is one of the most reliable ways to turn a profitable project into an unpaid dispute. Without a written, signed change order, a contractor's only legal recourse for extra work is typically a quantum meruit claim β a court-determined award of the reasonable market value of the work, which is almost always less than what the contractor would have charged under their own pricing. Clients, meanwhile, lose budget visibility and face surprise invoices they feel no obligation to pay because nothing in writing authorized the extra cost.
The risks compound on multi-change projects: by the tenth undocumented scope addition, neither party agrees on what was authorized, how much was approved, or when the project was supposed to finish. Schedule claims and delay damages become unresolvable because there is no written record of which changes caused which delays. A signed change order for every scope modification β even small ones β eliminates this ambiguity, protects payment rights, preserves lien rights in construction contexts, and keeps the project budget and schedule traceable from start to finish. This template gives you a professionally structured, legally grounded starting point that takes under 20 minutes to complete and can be attached directly to your original contract.
| If your situation is⦠| Use this template |
|---|---|
| Residential or commercial construction scope addition | Construction Change Order |
| Software or IT project feature request outside original spec | IT Project Change Order |
| Professional services engagement scope expansion | Service Agreement Amendment |
| Reducing project scope or issuing a credit to the client | Change Order (Deductive) |
| Formally amending the full original contract terms | Contract Amendment |
| Logging multiple pending changes before owner approval | Change Order Log |
| Requesting a time extension only, with no cost change | Contract Extension Agreement |
Why it matters: Work performed without a fully executed change order typically becomes a disputed quantum meruit claim rather than a contractual entitlement. Courts award the reasonable value of the work β which is almost always less than what the contractor would have charged.
Fix: Establish a firm policy: no changed work begins until the change order carries two signatures and a date. Build this into your subcontract language as well.
Why it matters: Language like 'additional electrical work' or 'revised flooring per client request' tells both parties different things. When the invoice arrives, the client disputes what was included and the contractor has no written evidence of the agreed scope.
Fix: Write descriptions specific enough to exclude everything outside them. Reference drawing revision numbers, square footage, material specs, and exact locations. Attach photos or plans as an exhibit.
Why it matters: Tracking only the incremental change amount makes it impossible to monitor total budget exposure. By change order 12, neither party knows what the project actually costs.
Fix: Show three numbers on every change order: the incremental change amount, the cumulative change order total to date, and the revised contract sum after this change order.
Why it matters: A contractor who accepts additional scope without a written time extension waives the right to a delay claim later β even if the extra work demonstrably extended the project. This exposure can exceed the value of the change itself.
Fix: Assess schedule impact for every change order, even minor ones. If the impact is zero, write it explicitly. If uncertain, reserve the right to claim a time extension by adding a carve-out clause.
Why it matters: An email from a client saying 'go ahead with the extra work' is not a signed change order in most jurisdictions. If the project ends in dispute, courts treat unexecuted email approvals inconsistently β some enforce them, many do not.
Fix: Reply to any email directing additional work by attaching a formal change order for signature before proceeding. Keep email trails as supporting documentation, not as the binding agreement itself.
Why it matters: Attempting to settle all open project claims with every individual change order signature creates a waiver trap β the contractor may unknowingly release claims for unrelated delays, defective owner-furnished materials, or other unresolved issues.
Fix: Limit the waiver clause strictly to claims arising from the specific change described in that change order. Add language excluding unrelated claims: 'except for claims arising from matters unrelated to the scope of this Change Order.'
In plain language: Identifies the original contract being modified by name, date, and parties, ensuring the change order is legally connected to the right agreement.
This Change Order No. [NUMBER] amends the [CONTRACT TYPE] dated [DATE] between [OWNER/CLIENT NAME] ('Owner') and [CONTRACTOR/VENDOR NAME] ('Contractor') for the project known as [PROJECT NAME].
Common mistake: Referencing the project name only instead of the contract date and parties. When multiple contracts exist for the same project, this creates ambiguity about which agreement is being amended.
In plain language: Provides a precise written description of what is being added, removed, or modified β specific enough that both parties agree on exactly what work is covered.
The scope of work is hereby modified to include [DETAILED DESCRIPTION OF ADDED/REMOVED/MODIFIED WORK], as further described in Exhibit A attached hereto.
Common mistake: Using vague language like 'additional work as discussed.' Without a precise written description, both parties often have different understandings of what was agreed, which leads directly to billing disputes.
In plain language: States the exact dollar amount being added to or deducted from the original contract sum, along with the new contract total after the change.
The Contract Sum is hereby increased / decreased by $[AMOUNT]. The revised Contract Sum is $[REVISED TOTAL], representing the Original Contract Sum of $[ORIGINAL AMOUNT] plus/minus all approved Change Orders to date totaling $[CUMULATIVE CHANGE AMOUNT].
Common mistake: Stating only the incremental change amount without restating the revised contract total. Omitting the running total makes it difficult to track overall budget exposure across multiple change orders.
In plain language: Records any change to the project's completion date or milestone dates as a direct result of the modified scope, expressed as a specific number of calendar days added or removed.
The Contract Completion Date is hereby extended by [NUMBER] calendar days. The revised Completion Date is [DATE]. No other contract milestones are affected unless noted in Exhibit A.
Common mistake: Approving a cost change without addressing the schedule impact. Contractors who accept additional work without a written time extension waive their right to a delay claim later β even when the extra work clearly took more time.
In plain language: Documents why the change is occurring β owner request, unforeseen site condition, design revision, code requirement, or material substitution β creating a contemporaneous record.
This change is necessitated by: [CHECK ONE] Owner-directed change / Unforeseen site condition / Design revision / Regulatory requirement / Material substitution. Supporting documentation is attached as Exhibit [B].
Common mistake: Leaving the reason field blank to avoid assigning responsibility. The reason determines who bears the cost and time consequences β omitting it invites later disputes about which party caused the change.
In plain language: Specifies whether the change order price is a fixed lump sum, a not-to-exceed estimate, or time-and-materials billed at agreed labor rates and markups.
The change order price is based on: [CHECK ONE] Lump sum of $[AMOUNT] / Time and materials at rates set out in Schedule 1, not to exceed $[AMOUNT] without prior written approval / Unit pricing at $[RATE] per [UNIT].
Common mistake: Defaulting to time-and-materials with no cap when the scope is reasonably definable. An uncapped T&M change order gives the client no budget certainty and gives the contractor no incentive to work efficiently.
In plain language: Confirms that all other terms of the original contract remain unchanged and that this change order supersedes any prior verbal or written discussions about the same change.
Except as expressly modified herein, all other terms and conditions of the Original Contract remain in full force and effect. This Change Order constitutes the entire agreement between the parties with respect to the change described above.
Common mistake: Omitting this clause when multiple change order discussions happened over email or in meetings. Without it, prior emails or meeting notes may be introduced as evidence of different agreed terms.
In plain language: States that by signing, both parties acknowledge that the change order represents the complete and final adjustment for the described change β no additional cost or time claims may be made for the same change afterward.
Contractor's acceptance of this Change Order constitutes full and final settlement of all claims for additional compensation or time extensions arising from or related to the change described herein.
Common mistake: Including an overbroad waiver that attempts to settle all claims on the entire project with each individual change order. Courts have voided blanket waivers that clearly overreached the scope of the specific change.
In plain language: Provides dated signature lines for both the owner and contractor, confirming mutual agreement and β where required β the authority of the signing party to bind their organization.
OWNER: Signature: _______________ Name: [NAME] Title: [TITLE] Date: ___________ | CONTRACTOR: Signature: _______________ Name: [NAME] Title: [TITLE] Date: ___________
Common mistake: Proceeding with changed work after only one party has signed. A unilateral signature is not a binding change order in most jurisdictions β work done before mutual execution creates a disputed quantum meruit claim rather than a contractual entitlement.
Number each change order sequentially starting at CO-001. Enter the number at the top of the form along with the project name and original contract date.
π‘ Keep a running change order log spreadsheet that tracks every CO number, description, cost, and status β this becomes essential for final accounting and dispute resolution.
Enter the full legal names of both parties, the original contract date, and the project description exactly as they appear in the base contract. This ties the change order to the right agreement.
π‘ If the original contract has a unique identifier or purchase order number, include it here β large owners and government clients use it to route the CO through their approval system.
Describe the modified, added, or deleted work in enough detail that someone unfamiliar with the project understands exactly what is and is not included. Attach drawings, specifications, or photos as an exhibit if the change involves physical work.
π‘ If the change was discussed verbally or by email, quote the client's request language in the description β this eliminates later disagreements about who initiated the change.
Enter the incremental cost change (positive for additions, negative for deductions), the cumulative total of all change orders to date, and the new revised contract sum. All three numbers should appear on the form.
π‘ For T&M changes, attach a labor and material breakdown as Exhibit B even when using a not-to-exceed cap β it protects you if the client disputes line items at invoicing.
State the number of calendar days added to or removed from the completion date, and calculate the new completion date explicitly. If the change has no schedule impact, write 'Zero (0) days' β do not leave it blank.
π‘ Distinguish between calendar days and working days. Most construction contracts use calendar days; IT and professional services contracts often use business days.
Check or write the reason category β owner request, unforeseen condition, design revision, regulatory requirement, or other β and attach any supporting documentation that substantiates the cause.
π‘ For unforeseen site conditions, photograph and date the condition before any remediation work begins. Photos attached to the change order are the most persuasive evidence in a later dispute.
Both parties must sign before any changed work begins. Confirm that the signing individual has actual authority to bind their organization β a project manager may not have authority to execute change orders above a certain dollar threshold.
π‘ Check the original contract for any approval threshold clause: many owner contracts require a VP or CFO signature for change orders above $25,000 or $50,000.
File the signed change order with your project contract binder, update your change order log, and issue a revised schedule or budget summary to all stakeholders if the change is material.
π‘ Send the client a PDF of the fully executed change order as a receipt immediately after both parties sign β this eliminates any 'I never received the final version' dispute months later.
A change order is a written, signed amendment to an existing contract that formally modifies the original scope of work, contract price, or project schedule. It is executed by both parties before any modified work begins and becomes part of the contract record, superseding any prior verbal or email discussions about the same change. Change orders are standard in construction, IT, engineering, and professional services contracts.
A change order should be issued and signed before any work outside the original contract scope begins. Common triggers include owner-directed design changes, unforeseen site conditions that require additional work, regulatory requirements discovered after contract execution, material substitutions, and client requests to add or remove deliverables. Waiting until after the work is done to document the change dramatically increases the risk of non-payment or underpayment.
Yes β a properly executed change order signed by authorized representatives of both parties is generally enforceable as a binding contract amendment in most jurisdictions. It modifies the original contract and creates enforceable obligations for both the additional payment and any revised schedule. An unsigned or unilaterally signed change order is typically not binding and may leave the contractor pursuing a less predictable quantum meruit claim for the value of work performed.
A change order modifies a specific element of a contract β typically scope, price, or schedule β on a project-by-project or task-by-task basis and is most common in construction and services agreements. A contract amendment modifies the underlying contractual terms themselves, such as payment conditions, liability limits, or governing law. Change orders are issued frequently during a project; amendments are reserved for material changes to the core agreement structure.
The contractor may still recover payment, but typically through a quantum meruit claim rather than a contract claim β meaning courts award the reasonable market value of the work rather than the contractor's own pricing. This often results in a lower recovery. Additionally, without a written schedule extension, time-related claims for delay damages are generally waived. The practical risk is months of dispute and legal cost over work that a signed change order would have made straightforward.
A work order authorizes new or routine work within an existing service agreement β it initiates a task rather than modifying a contract. A change order specifically amends a previously agreed scope, price, or schedule. In facility management and maintenance contexts the two documents overlap, but when the new task falls outside what the original contract covers, a change order is the correct instrument because it creates a formal contractual modification rather than just a task authorization.
Most construction and services contracts require written change orders and prohibit verbal authorizations. Even in contracts that do not explicitly require writing, verbal change orders are difficult to enforce and easy to dispute. Courts in common-law jurisdictions typically enforce written contracts as written, meaning an oral agreement to change the scope may be inadmissible if the contract contains an integration clause. Written, signed change orders are the only reliable protection.
Change orders should be numbered sequentially from CO-001 and tracked in a dedicated change order log that records the CO number, date issued, date executed, description, cost impact, schedule impact, and status. The log becomes the definitive project record for final accounting, lien releases, and dispute resolution. Each executed change order should be filed with the original contract and referenced in the project's budget tracker.
A contract amendment modifies the underlying terms of the agreement itself β payment conditions, liability caps, warranty periods, or governing law. A change order modifies the operational elements of a specific project: scope, price, and schedule. Change orders are issued repeatedly during a project; amendments are reserved for structural changes to the governing contract. If you need to change the contract's rules, use an amendment; if you need to change what work is being done, use a change order.
A work order initiates or authorizes a specific task within the existing scope of an agreement β it does not modify the contract. A change order formally amends the contract to cover work that falls outside the original scope. When a client asks for something new that was not contemplated in the original agreement, a change order is required; routine task assignments within the original scope need only a work order.
A contract extension agreement extends the term of an existing contract β typically renewing the engagement period without modifying the scope or price. A change order is used when the schedule must shift because of a specific scope addition or site condition. Use a contract extension when the relationship continues unchanged past its original end date; use a change order when a specific project event drives the schedule revision.
A statement of work (SOW) defines the original scope, deliverables, timeline, and price at the start of an engagement. A change order modifies the SOW once the project is underway. The SOW is the baseline; every signed change order is a formal revision to that baseline. When changes are substantial enough to render the original SOW unrecognizable, it may be more appropriate to issue a revised SOW than a chain of change orders.
Change orders are a standard mechanism on every build β covering unforeseen soil conditions, owner design revisions, code compliance adjustments, and material substitutions; AIA G701 is the widely adopted standard form.
Feature creep is endemic to software projects; change orders document additions to original technical specifications, new integrations, and revised delivery milestones before development resources are committed.
Consulting, legal, and accounting engagements use change orders to authorize work beyond the original statement of work, protecting both the firm's billing rights and the client's budget visibility.
Engineering change orders (ECOs) govern modifications to product designs, bills of materials, or production specifications mid-run, with formal approval required to prevent unauthorized production changes.
Change order requirements vary significantly by state and contract type. AIA Document G701 is the construction industry standard in most states. Many state public works statutes require written change orders above a specified dollar threshold and impose strict notice and claim-submission deadlines β typically 7β21 days after the triggering event. California, New York, and Texas have specific prompt-payment statutes that affect when change order amounts must be paid once approved.
Canadian construction contracts commonly follow CCDC (Canadian Construction Documents Committee) standards, which include formal change order and change directive procedures with defined notice requirements. Provincial construction lien acts β such as Ontario's Construction Act β impose strict deadlines for preserving lien rights on unpaid change order work. Quebec's Civil Code governs contracts differently from common-law provinces, and change order language must be consistent with civil law principles.
UK construction contracts frequently follow JCT (Joint Contracts Tribunal) or NEC (New Engineering Contract) standard forms, both of which include detailed variation and compensation event procedures that function as change order mechanisms. The Housing Grants, Construction and Regeneration Act 1996 grants statutory payment and adjudication rights that apply to change order amounts. Variations instructed without a formal written instruction may still be recoverable under the contract if the contractor can demonstrate the instruction was given.
EU member states apply their own contract and construction law frameworks, but EU public procurement rules impose specific requirements for change orders on public contracts β modifications above 10β15% of the original contract value or above β¬5.35M may require a new tender process under the EU Procurement Directive. GDPR considerations are generally not relevant to change orders unless the modified scope involves processing personal data. Cross-border contracts should specify governing law explicitly to avoid conflict-of-laws disputes.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Contractors, project managers, and service providers handling routine scope additions on standard commercial or residential projects under $100,000 | Free | 10β20 minutes per change order |
| Template + legal review | Change orders on government contracts, public projects, or any change exceeding $50,000 where waiver-of-claims language carries material financial risk | $200β$500 for a construction or contracts attorney review | 1β3 days |
| Custom drafted | Complex multi-party construction or IT projects with contractual claim procedures, bonded work, or international parties where enforceability across jurisdictions is critical | $500β$2,500+ depending on complexity | 3β10 days |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Free Forever PlanΒ Β·Β No credit card required
