Do I need a lawyer to create a change order?

No. A simple change order is just documentation of what you agreed to. It doesn't need legal language. A clear email or one-page document is enough. Only get a lawyer involved if you're working on very large projects.

Should I ask clients to sign change orders?

It depends on the project size. For small changes under $500, email confirmation is usually fine. For bigger changes, a simple signature or written approval is better. Just have them reply confirming they agree.

Can I make a change order retroactive?

Yes, but it's awkward. If you already did the work without documenting a change order, you can write one after the fact. But it's better to create them proactively, before the work.

Change Order Template for Freelancers: Simple Format

You don’t need a fancy legal template or accountant approval. A change order is just a clear record that the client asked for something extra, you quoted a price, and they agreed. Here’s a simple template you can customize and use right now.

Basic Email Change Order Template

This works for most situations. Send it as an email and ask the client to reply confirming they agree.

Subject: Change Order for [Project Name]

Hi [Client Name],

You asked about [describe the change]. This is outside our original agreement, but I can definitely handle it.

Here’s what this change includes:

[What you’re adding/changing]
[Any other details]

Additional cost: $[amount] Timeline impact: [add X days/weeks to delivery]

This will be added to the project on [date]. The revised completion date is now [new date].

Please reply confirming you’d like to move forward with this change. Once you confirm, I’ll get started on it.

Thanks, [Your name]

This is friendly, clear, and professional. The client knows exactly what they’re paying for and when they’ll get it.

Formal Change Order Document

For bigger projects or more formal clients, use this one-page format.

CHANGE ORDER

Project: [Project Name] Client: [Client Name] Date: [Date] Change Order #: [Number]

DESCRIPTION OF CHANGE: [What the client asked for, in detail]

REASON FOR CHANGE: [Brief explanation if relevant. Example: Client requested additional functionality, or Client needs faster timeline]

SCOPE IMPACT: Original scope: [What was agreed in the original contract] New scope: [What’s being added/changed]

COST IMPACT: Original project cost: $[amount] Additional cost for this change: $[amount] New total project cost: $[amount]

TIMELINE IMPACT: Original delivery date: [date] New delivery date: [date] [Specify what’s being delayed, if anything]

APPROVAL:

This change order is contingent on your written approval. Please reply confirming you agree to the additional cost and timeline impact, and I’ll proceed immediately.

Client approval: [Client name/signature] Date: _______________

Freelancer: [Your name/signature] Date: _______________

Print this, have them sign, or just get a written confirmation email. Either way, you have documentation.

Quick Verbal Change Order Confirmation

Sometimes you’ll discuss a change order over the phone or in person. Follow up immediately with an email confirming what you discussed.

Subject: Confirming our conversation about [project]

Hi [Client Name],

Thanks for talking through that change request today. Just to confirm what we discussed:

You’d like to add [describe change] Cost: $[amount] New timeline: [date]

I’ll move forward with this unless you reply saying otherwise. Thanks!

[Your name]

This protects you because it documents the agreement. If the client later says they didn’t agree, you have the email.

When to Use Which Template

Email template: Small changes under $500, ongoing or retainer work, informal clients, or quick turnaround situations. Formal document: Big changes over $1000, new clients, complex projects, or anything you want documented carefully. Verbal confirmation: Changes discussed in real-time that you need to document fast. Most change orders will be email. That’s professional enough.

Key Elements to Always Include

No matter which format you use, include these:

Clear description of what’s being added or changed. The client should read it and know exactly what you’re talking about.

Cost or “no charge.” Never leave the cost ambiguous. If it’s free, say “no charge.” If it costs money, say the amount.

Timeline impact. How does this affect the delivery date? Be specific. “This adds two weeks” not “slight delay.”

Approval requirement. Tell them what you need from them to move forward. “Reply confirming you agree” or “Please sign and return.”

Common Change Order Situations

Client asks for an additional page or section: Adding one additional page to the design: $400. New delivery date: [date].

Client wants more revisions than included: Three additional rounds of revisions beyond the two included: $200 per round. First round due [date].

Client wants the project faster: Expedited timeline, two weeks earlier: +$600 to cover rush fees.

Client wants to add a feature: Integration with [tool/system]: $X. Timeline impact: +[time period].

Scope creep is building: This project has expanded beyond the original scope. I’d recommend either (1) a formal change order for the additions, or (2) simplifying back to the original scope.

Store Your Change Orders

Keep records. Create a folder for each client and save every change order you issue. Include the client’s approval, your timeline, and what you charged.

This is helpful when disputes come up. You have documentation. It’s also helpful for future projects with the same client, so you remember how they work and what tends to shift.