Free templates

Templates for scope changes, change orders and approvals.

Copy, fill in the brackets and send. Four templates that cover a project from the first scope email to the last change request, free and with no sign-up.

Scope confirmation email

Send this before you start. It turns a conversation into a written list, and the client's reply becomes your baseline for every change after it.

Scope confirmation email

Subject: Confirming the scope for [project name] Hi [client name], Before I start, here's a quick summary of what we agreed, so we're both working from the same list. Included: - [deliverable 1] - [deliverable 2] - [deliverable 3] Not included: - [anything you discussed and left out] Revisions: [2] rounds on each deliverable Price: [amount], paid [schedule] Delivery: [date] Anything outside this list is a change. I'll send the extra time and cost for any change before starting it, so there are no surprises on the invoice. Could you reply to confirm this looks right? Thanks, [your name]

In ClearTimeline, log the agreed scope as your first entry. It's timestamped and can't be edited later, so it stays the baseline even if the email thread gets messy.

Change order email

Send this when a client asks for something that wasn't in the agreed scope, before you start the work. A clear yes now saves an argument at invoice time.

Change order email

Subject: Change request: [what they asked for] Hi [client name], Thanks for sending over [the request]. It's outside the scope we agreed on [date], so I've written it up as a change before starting. What's changing: [one line describing the new work] Extra time: [hours or days] Extra cost: [amount] New delivery date: [date, or "no change"] If that works for you, reply "Approved" and I'll start. If you'd rather keep the original scope, that's fine too, and I'll carry on as planned. Thanks, [your name]

In ClearTimeline, log the request as a scope change and send an approval request. Your client approves from a link, and the time they approved is recorded.

Replies to out-of-scope requests

Short replies for email or chat. Each one says yes to the client and makes the change visible, without a lecture about scope.

  • A small request you're happy to include

    Happy to add that. It's outside what we agreed, so I'll note it as a small extra at no charge this time. Anything bigger I'll quote first.

  • A bigger request that needs a quote

    Good idea. It isn't in the current scope, so I'll send over the extra time and cost before I start. Shall I put that together?

  • More changes after the revision rounds

    I can make those changes. We've used the [2] revision rounds included in the project, so further rounds are [amount] each. Would you like me to go ahead?

  • “I thought this was included”

    Let me check. The scope we agreed on [date] covers [what's included]. [The new item] first came up on [date]. I'm happy to add it as a change. Here's what it would take: [time and cost].

  • A rush request

    I can have that ready by [date]. Turning it around that fast means moving other work, so there's a rush fee of [amount]. Shall I go ahead?

Scope change log

One row for every request after the scope was agreed, including the ones you do for free. Download it as a spreadsheet, or use these columns in your own.

DateRequested byRequest (in their words)In the original scope?Extra timeExtra costDecisionClient approved on
2 Nov 2026Client name“Can we add a blog section? Just 3–4 pages.”No6 hours$480Bill it3 Nov 2026

A spreadsheet works, but anyone can edit it. In ClearTimeline each change is logged with a timestamp that can't be changed, and your client sees the same list in their portal.

Questions

What should a change order email include?

Say what the client asked for, that it's outside the agreed scope, and what it changes: extra time, extra cost and any new delivery date. Then ask for a clear yes before you start, such as a reply saying “Approved”.

How do I say no to out-of-scope work without upsetting the client?

You rarely need to say no. Say yes to the idea, point out that it's a change, and give the time and cost before starting. Clients usually respect a clear process, and it lets them decide whether the change is worth it.

Should I charge for every small change?

That's up to you. Many freelancers include small changes for free but still log them, so the client sees how much extra they've had. Logging them is what lets you charge for bigger ones later.

Why keep a scope change log?

A log shows each request in order, with the date and the decision. If a client says extra work was always included, you can point to when it was first asked for and when they approved it.

Can I use these templates for free?

Yes. Copy them, edit them and use them with your clients. No sign-up needed.

Get Weekly Freelance Protection Tips

Practical advice on preventing scope creep, winning payment disputes, and protecting your freelance income. No spam, unsubscribe anytime.

Want to see the record behind these templates? See an example project

Stop tracking scope changes in your inbox

Log the agreed scope, every change and every approval in one timeline your client can see.

Free forever for 1 project
No credit card required