Worked example: one more landing page
Original scope: three pages. Change: a fourth page using the existing design system, one review round, and client-supplied copy. Record the extra page, its acceptance criteria, the copy deadline, the fee adjustment, and the revised review milestone together.
What the form cannot resolve
A form cannot settle unclear contract rights by itself. If ownership, liability, termination, or other core legal terms change, obtain legal advice about an amendment rather than assuming a scope form is sufficient.
Copy-and-customize preview
Free editable sample
No purchase or email required.
CHANGE ORDER [CO-number] — version [number] Project / client: [name] Original agreement: [date, version, section] Requested by / date: [contact, date] Reason for change: [business outcome] Add: [deliverables and acceptance criteria] Remove or replace: [items, or none] Unchanged: [remaining obligations] Fee adjustment: [amount and currency] Revised total project fee: [amount and currency] Payment milestone: [trigger and due date] Schedule: [old milestone] → [new milestone] Client dependencies: [inputs, owner, deadline] Approval: [authorized name, date, method] Work begins only after [approval and any agreed payment condition].
| Field | Why it matters | Example |
|---|---|---|
| Change identifier | Prevents approval of an obsolete estimate. | CO-03, version 2. |
| Scope delta | Shows additions and removals. | Add checkout testing; remove the optional gallery. |
| Commercial delta | Distinguishes the adjustment from the total. | Fee adjustment +[amount]; revised project total [amount]. |
| Milestones | Captures consequences beyond production. | Client supplies assets Monday; review moves to Thursday. |
Use it in four steps
- Link the original agreement and current scope version
- List additions, removals, and unchanged obligations
- Re-estimate fee, milestones, and client dependencies
- Collect approval of the exact change-order version
Customization checklist
- Use one currency and identify any tax treatment separately
- Make payment conditions consistent with the agreement
- Retain superseded versions without confusing them with the approved one
Common mistakes to avoid
- Listing only the added fee without the revised total
- Leaving removals implicit in a scope swap
- Starting before the named approver agrees
Frequently asked questions
- Does every small request need this entire form?
- No. A short written approval may suit a low-risk addition where the agreement permits it. Use a structured form when the impact is material or several dependencies change.
- Can a change order reduce scope?
- Yes. Record removed work, any fee adjustment, and the revised acceptance conditions explicitly.
Continue with the next decision
Freelance Change Control Clause: Copy-Ready Contract Wording
A change-control clause requires added or altered work to be described, priced, scheduled, and approved in writing before it begins.
Publisher comparisonChange Order vs Contract Amendment: Which Should Freelancers Use?
Use a change order to document a defined project-level adjustment within the agreement’s change process. Seek advice on a contract amendment when changing underlying terms such as ownership, liability, or termination. The label alone does not determine legal effect.
Free editable artifactOut-of-Scope Email Template for Freelancers
An out-of-scope email identifies the difference between the approved deliverable and a new request, then offers a priced addition, a scope swap, or a later phase. Send it before starting the extra work and retain written approval.
Change Order TemplatesRecord Which Version a Client Approved in a Scope-Change Form
An approval record should identify the exact change version, authorized approver, amount, milestone, and date. A reply approving an obsolete estimate should not silently approve a later revision.
Change Order TemplatesComplete a Web Design Change Order: Extra Page and Integration Example
A web change order should distinguish the page itself from integrations, copy, QA, and launch dependencies. Record the changed acceptance criteria and revised milestones, not just a new page count.