Change order template for freelancers

A change order is a written update to the original project agreement. Any work requested after approval that changes scope, timing, or deliverables should be documented in writing and priced before you do it. That is what a change order is. It is not corporate theater. It is how you stop scope creep from quietly eating your margin.

According to the Project Management Institute (PMI), uncontrolled scope changes are one of the top three reasons projects exceed their budget. The Freelancers Union reports that 71% of freelancers have experienced payment collection problems, and many of those stem from scope disagreements that were never documented. A change order prevents both.

What is a change order

A change order is a written update to the original project agreement.

It usually covers one or more of these:

• new deliverables the original proposal did not include
• revised deadlines (earlier or later)
• additional revision rounds beyond what was agreed
• extra meetings, calls, or implementation work
• removed deliverables (and corresponding price adjustments)
• changes to the creative direction that invalidate completed work

If the request changes the work, it should change the agreement. The change order is the document that makes the change official before you do the work.

The alternative is doing extra work for free, then trying to sort out the money later. That rarely ends well.

When should freelancers use a change order

Use one any time the client says something like:

• “Can we add one more page?”
• “Can you also write the email sequence?”
• “Can we make this mobile version completely different?”
• “We need this delivered two weeks earlier.”
• “Can you just handle the dev side too?”
• “Can we add a few more social graphics?”
• “Can you also set up the analytics?”
• “Can we start over with a different direction?”

If the answer changes scope, price, or timeline, use a change order.

The rule is simple. If you cannot point to the original proposal and say “yes, this was included,” it needs a change order.

Freelance change order template

Copy this and adapt it for your project type.

CHANGE ORDER

Project: {PROJECT_NAME}
Client: {CLIENT_NAME}
Original proposal date: {DATE}
Change order date: {DATE}
Change order number: {NUMBER}

REQUESTED CHANGE
{Describe the new request in one short paragraph. Be specific
about what the client wants added, removed, or changed.}

IMPACT ON SCOPE
- {List what is being added}
- {List what is being removed or modified}
- {Note any deliverables affected}

PRICING ADJUSTMENT
{Additional fixed fee or hourly estimate with total}

TIMELINE ADJUSTMENT
{Updated delivery date or milestone timing. State the original
date and the new date.}

APPROVAL
Work on this change will begin once this change order is approved
in writing and any required payment is received.

Approved by: _______________
Date: _______________

This template works for any project type. Adapt the language to your industry, but keep the structure. The five sections (change, scope impact, price, timeline, approval) cover everything both sides need to agree on.

Change order examples by industry

Different industries face different types of scope changes. Here are realistic examples.

Web design change order

Requested change:
Add one landing page variation and one additional round of
revisions to the original website redesign scope.

Pricing adjustment:
Additional fixed fee of $900.

Timeline adjustment:
Final delivery date moves from May 10 to May 15.

Approval:
This change order becomes active once approved in writing.
Work on the revised scope begins after approval and any
related payment is received.

Copywriting change order

Requested change:
Add a 5-email welcome sequence to the existing website copy
project. The original scope included homepage, about page, and
services page copy only.

Pricing adjustment:
Additional fixed fee of $1,250 for the 5-email sequence.

Timeline adjustment:
Email sequence delivered 7 business days after final website
copy approval. Overall project delivery moves from April 20
to April 30.

Branding change order

Requested change:
Client has decided to pursue a different visual direction after
the first round of logo concepts was presented. This invalidates
the completed work and restarts the concept phase.

Pricing adjustment:
Additional $1,500 for a new round of logo concepts (3 options).
Original round is considered delivered and complete.

Timeline adjustment:
Project timeline extends by 10 business days from the date of
this approval.

Development change order

Requested change:
Add user authentication with social login (Google and Apple)
to the web application. The original scope included email/
password authentication only.

Pricing adjustment:
Additional $2,400 billed at $150/hour, estimated 16 hours.
Final billing based on actual hours.

Timeline adjustment:
Sprint 3 extends by one week. Final delivery moves from
June 1 to June 8.

Photography or video change order

Requested change:
Add one additional shooting location to the brand photography
session. The original scope included two locations.

Pricing adjustment:
Additional $600 for the third location, including travel time
and additional post-production (estimated 15 additional edited
images).

Timeline adjustment:
Shoot day extends by approximately 2 hours. Gallery delivery
date unchanged.

How to price change orders

There are two common approaches. Choose based on what fits your business model.

Approach 1: fixed fee per change

Quote a flat price for the additional work. This is cleaner for the client and easier to approve.

Best for:

• clearly defined additions (one more page, one more email, one more round)
• projects where scope is easy to estimate
• clients who prefer predictable costs

Example: “Adding one landing page variation: $900.”

Approach 2: hourly add-on

Quote an hourly rate and estimated hours. Bill based on actuals.

Best for:

• work that is hard to scope precisely
• ongoing technical changes
• projects where the client wants transparency into time spent

Example: “Additional development work at $150/hour, estimated 16 hours. Final billing based on actual hours.”

Comparison table

Approach	Best for	Client experience	Risk to you
Fixed fee	Clear, defined additions	Predictable cost, easy to approve	You absorb overages
Hourly add-on	Complex or uncertain changes	Transparent but less predictable	Client may question hours
Hybrid (fixed + hourly cap)	Medium complexity changes	Predictable with a ceiling	Balanced risk

The hybrid approach works well for changes that are mostly predictable but could expand: “Additional $1,200 fixed fee, with any work beyond 10 hours billed at $120/hour.” The client gets a baseline price and you have protection if the work grows.

The simplest change order process

Use this every time:

1. Client requests a change
2. You pause and define the change clearly
3. You send the new price and timing in writing
4. Client approves in writing
5. You continue work

Do not:

• Start the extra work first and price it later
• Hope you can “sort it out later”
• Bury the change in a long email thread
• Absorb the work because it “seems small”

The pause between step 1 and step 5 is the entire point. That pause is where you protect your margin.

According to PMI research, projects with a formal change control process are 28% more likely to meet their original budget targets. That applies to freelance projects just as much as corporate ones.

The change order clause to include in your proposal

Put this in the original proposal terms before the project starts:

Any requested work outside the agreed scope requires a written
change order and may affect both project pricing and timeline.

That one sentence prevents a lot of future negotiation. It sets the expectation before any changes happen.

For stronger baseline protection, pair that clause with clear payment terms for freelancers and a defined revision policy in the original proposal.

If you want the full scope protection framework, read the scope creep clause guide. It covers the scope clause, revision policy, and change order process together.

How to talk about change orders without sounding defensive

The language matters. You are not saying no to the client. You are saying yes and routing the request through a process.

Use language like this:

“Happy to do that. Since it changes the original scope, I will send a quick change order with the updated price and timing.”

That works because:

• It is calm and collaborative
• It does not sound combative or defensive
• It makes the process feel normal, not confrontational
• It puts the ball in the client’s court without creating tension

More scripts for common situations

When the client adds deliverables:

“Great idea. That was not part of the original scope, so I will put together a change order with the cost and updated timeline. Should have it to you by end of day.”

When the client wants to accelerate the timeline:

“I can explore moving the deadline up. That would likely require additional hours or adjusting the scope of other deliverables. I will send a change order with the options.”

When the client wants “just one more thing”:

“Sure. I want to keep the scope clean, so I will document this as a change order. If the cost is small, it will be obvious from the change order.”

When the client changes direction mid-project:

“I understand the shift. Since this changes the creative direction we agreed on, I will document the new direction as a change order so we are aligned on the adjusted scope, timeline, and cost.”

When the client says “I thought this was included”:

“Let me check. [Reviews proposal.] The original scope covers [X, Y, Z]. This request is outside that, so I will send a change order. If the cost is reasonable, we can handle it quickly.”

Common freelancer mistakes with change orders

Mistake 1: treating scope changes like favors

If the client asks for something new and you do it for free, you just reduced your effective rate. One free change leads to another. The project gets less profitable with each unpriced addition.

Mistake 2: not defining what changed

“A few updates” is not a scope description. Be specific. List exactly what is being added, what it costs, and how it changes the timeline. Vague change orders create the same problems as vague proposals.

Mistake 3: changing price without changing timeline

More work almost always changes timing too. If you add scope without adjusting the delivery date, you are committing to work more hours in the same window. That means late nights, lower quality, or a missed deadline.

Mistake 4: arguing instead of documenting

You do not need a debate. You need a written update. The change order removes the argument by making the change factual. Price and timeline are math, not opinions.

Mistake 5: not having a change order template ready

If you have to create a change order from scratch every time, you will skip the process when you are busy. Build the template once. Save it. Use it every time.

Mistake 6: waiting too long to send the change order

Send the change order the same day the client requests the change. The longer you wait, the more the client assumes you are doing the work for free. Speed protects your position.

How change orders connect to your proposal

A change order only works if the original proposal is clear about what was included.

If your proposal says “website redesign” with no deliverable list, the client can argue that anything related to the website was included. If your proposal lists “homepage, about page, services page, and contact page,” adding a blog page is clearly outside scope.

The proposal is the foundation. The change order is the update.

For the full structure of a proposal that makes change orders easy, read the freelance proposal guide.

For the contract language that supports the change order process, read freelance contract essentials.

Tracking change orders across a project

For longer projects, you may have multiple change orders. Keep them organized.

• Number each change order sequentially (CO-001, CO-002, etc.)
• Reference the original proposal date in each one
• Keep a running total of the original price plus all approved changes
• Update the timeline with each change order
• Store all approved change orders in the same place as the original proposal

At the end of the project, you should be able to point to the original proposal plus change orders and account for every dollar and every deliverable. That is the paper trail that prevents disputes.

When not to use a change order

Not every client request needs a change order. Reserve them for out-of-scope changes.

Does not need a change order:

• A revision within the agreed revision rounds
• A clarifying question about a deliverable
• A small preference change that takes minutes (swap this color, move this element)
• Feedback that refines the existing scope without expanding it

Needs a change order:

• A new deliverable not in the original proposal
• An additional revision round beyond what was included
• A change in creative direction that invalidates completed work
• An accelerated timeline that requires additional hours
• Any change that affects the price or delivery date

Use judgment. If it takes 5 minutes and does not change the scope, skip the paperwork. If it adds hours, cost, or timeline impact, document it.

For the full framework on distinguishing revisions from scope changes, read the scope creep clause guide.

FAQ

Is a change order too formal for freelance projects?

No. The wording can stay simple. A change order can be a short email with the five key elements: what changed, what it costs, how the timeline shifts, and a request for written approval. The point is clarity, not legal drama.

Should I charge for every change request?

Charge for out-of-scope changes that add work, time, or deliverables. Small in-scope clarifications and minor preference changes are different. Use the original proposal as your reference. If the request is listed in the deliverables, handle it. If it is not, send a change order.

What if the client refuses the change order?

Then the extra work does not happen. The original approved scope still stands. This is not a confrontation. It is the process working as designed. If the client wants the work done, they approve the change order. If they do not, you continue with the original scope.

Can I use email as a change order?

Yes, if the terms are clear and the client explicitly approves them in writing. An email that says “the additional landing page is $900 with delivery moving to May 15” followed by the client replying “approved” is a valid change order. A formal template is better for documentation, but a clear email works.

How do I handle multiple change orders on one project?

Number them sequentially. Reference the original proposal in each one. Keep a running total of the adjusted project price and timeline. At the end of the project, you should be able to account for every dollar with the original proposal plus all approved change orders.

What if the client says the change is small and should be free?

Size is not the issue. Scope is. A small change that is outside the original agreement is still outside the agreement. Say: “I hear you that it is small. I still want to document it so we are both clear on the scope. The change order will reflect that the cost is minimal.”

Should I require payment before starting the change order work?

For significant additions, yes. Require payment (or at minimum written approval) before beginning the extra work. For smaller changes, written approval is usually enough, with the additional cost added to the next milestone or final invoice. Match the payment requirement to the size of the change, similar to how you structure your deposit strategy.

How do change orders affect the final invoice?

Each approved change order adjusts the project total. Your final invoice should reflect the original price plus all approved change order amounts, minus any deposit or milestone payments already received. Reference each change order by number so the client can reconcile the total.

The practical takeaway

Freelancers do not lose margin because clients are unreasonable. They lose margin because scope changes happen informally and never get priced.

A change order template gives you a clean way to protect the project without turning every request into a fight. Build the template once. Save it somewhere you can access in 30 seconds. Use it every time a request falls outside the original scope.

GetPaidFirst helps by putting the original scope, pricing, and payment terms in one place, so when something changes you have a clear starting point instead of a vague memory of the sales call.

Further reading:

• PMI guide to change control (Project Management Institute)
• Freelancers Union contract creator (Freelancers Union)
• Scope creep clause (GetPaidFirst)
• Freelance proposal guide (GetPaidFirst)
• Freelance contract essentials (GetPaidFirst)
• Payment terms for freelancers (GetPaidFirst)
• Freelance deposit strategy (GetPaidFirst)