Scope creep rarely arrives as a big request. It arrives as "one more thing" on a call, a quick extra banner, a fourth landing page that "should only take an hour." Doing those favors without paperwork feels generous; adding them up at the end of a project usually shows two or three weeks of unpaid work. A change order makes each addition a small, explicit decision for the client: yes, and here is what it costs and how the deadline moves.
This form works with any freelance or agency contract that has a defined scope and a change clause. It is a single page the client can read in two minutes and sign the same day.
TL;DR
The change order form template records the original contract reference, what is being added, removed or changed, the reason, the effect on fee, timeline and deliverables, and written approval from both sides before work starts. Use it for any request outside the signed scope. Price changes with the rates already in your contract, and send the form within one business day of the request so the decision happens while it's fresh.
What's inside
- Reference details — change order number, contract and project, requested by and date.
- Description of change — what's added, removed or modified, in plain language.
- Reason — client request, new information, dependency delay or other cause.
- Impact on deliverables — the revised list of deliverables.
- Impact on fee — line items, rates and the new contract total.
- Impact on timeline — revised milestone and completion dates.
- Payment terms for the change — when the additional fee is invoiced.
- Approval — signatures and the rule that no work begins before approval.
- Change log — a running total of approved changes.
When to use it
Use a change order for any request beyond the signed scope: extra deliverables, new features, more revision rounds, a different technology, a bigger event guest count, a new room in a design project. Also use it when the client removes something, or when a delay on their side (late content, missing access) forces a schedule change.
For a quick informal heads-up before the formal document, send a scope change email the same day, then follow with this form. If the change is so large that it is really a new project, write a new proposal or a new statement of work instead.
How to present a change order without friction
Tie it to the contract. "Section 1.3 of our agreement covers this; here's the change order for the new landing page." The client is following an agreed process, not being upsold.
Offer options. "Add it now for [amount] and move launch by four days, or schedule it as phase two after launch at the same rate." Clients choose more readily between two clear options than they say yes to one.
Keep the price grounded. Use your contract's hourly or unit rates. If you need a different rate, explain why in the reason field.
Never start before approval. If the client is unavailable, wait. Starting work on an unsigned change is how a change order turns into a dispute. The article on asking a client for more budget has scripts for the conversation.
Customize it in your COLO workspace
In COLO, project budgets give you an in-app warning at 80% of a budget; at 100%, billable timers stop and you can choose Request Contract Update, continue as non-billable, or pause. When you request the update, the client approves or declines the budget increase in the client portal. Keep this signed form with the project files as the record of what the change covers, and invoice the additional fee as its own line item through COLO invoicing.
Common mistakes
- Verbal approvals. A "sure, go ahead" on a call is remembered differently three weeks later.
- No timeline impact. Extra work with the same deadline means rushed work, or a missed date blamed on you.
- Batching changes until the end. Ten small changes on one final invoice look like a surprise; ten small change orders look like a process.
- Forgetting removals. If the client drops something, say whether work already done is billed.
FAQ
Q: What is a change order?
A change order is a short written agreement that amends the scope of an existing contract. It describes what is changing, why, and how the change affects the price, the schedule and the deliverables, and both parties sign it before the extra work starts.
Q: When do I need a change order?
Whenever the client asks for something not covered by the signed scope, such as a new page, an extra deliverable, a new feature, or a revision beyond the included rounds. Small favors add up; a change order makes each one visible.
Q: Can a change order reduce the scope?
Yes. Removing work is also a change. Record what is removed, any credit or fee reduction, and whether work already done on the removed item is still billed.
Q: Do I need a signature for a small change?
Get written approval for every change, even if it's an email reply saying approved. For changes that affect the fee or deadline by more than a small amount, a signed change order is worth the extra minute.
Q: How do I price a change order?
Use the rates already in your contract where possible: hourly rate, rate per revision round or unit prices. That keeps the conversation about scope rather than about your pricing.