Skip to content
ScopeShield

Free editable artifact

Freelance Change Order Form Template

A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.

By ScopeShieldPublished Content reviewed Methodology & product disclosure

Direct answer

What you need to know

A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.

Definition: A change order is a project change record connected to an existing agreement; it is not a substitute for the original agreement.

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].
FieldWhy it mattersExample
Change identifierPrevents approval of an obsolete estimate.CO-03, version 2.
Scope deltaShows additions and removals.Add checkout testing; remove the optional gallery.
Commercial deltaDistinguishes the adjustment from the total.Fee adjustment +[amount]; revised project total [amount].
MilestonesCaptures consequences beyond production.Client supplies assets Monday; review moves to Thursday.

Use it in four steps

  1. Link the original agreement and current scope version
  2. List additions, removals, and unchanged obligations
  3. Re-estimate fee, milestones, and client dependencies
  4. 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

ScopeShield

$39 · instant access