The Scope Baseline Template: Define Project Deliverables Before You Start

You're two weeks into a "simple" brand project. The client opens the call with "I love the direction — can we explore a few more options?" and attaches a 14-page PDF of references. Three fonts. Two color systems. "And maybe a tagline, you're good at those."

Somewhere in your quote you promised "unlimited revisions." No — you didn't. You just never wrote down how many revisions were included. And now the difference between "a revision" and "a new direction" is decided by whoever sounds more confident in the Zoom call.

This is the exact moment a scope baseline saves your margin.

What a scope baseline is — and isn't

A scope baseline is a written snapshot of everything you agreed to deliver before work starts: the deliverables, the revision rounds, the exclusions, the quote, the hours, and the rate. One page. Written in plain language the client can actually read.

Here's the timing rule that makes it powerful:

Written *before* work starts, a baseline is a plan. Written *after* a dispute, it's a defense. Same words, completely different power.

A baseline isn't a contract — most freelancers don't have the stomach for legalese, and most clients don't need it. It's an agreement that reads like a plan. That's exactly why it works where contracts fail: nobody argues with the plan they already approved.

What a baseline buys you:

• It converts "I thought that was included" into "let's check the baseline." The client isn't lying — they're misremembering. A written list ends the argument before it starts.
• It forces you to price honestly. The hours field is an honesty check: if your estimate × your rate is below your minimum, you find out before you start, not after.
• It makes every add-on a decision, not a favor. When the client asks for something outside the list, the baseline gives you a neutral reason to say "that's new scope" — you're not being difficult, you're following the plan.
• It lets the client opt into extras with eyes open. Clients approve add-ons more easily when they can see exactly what was agreed and what's being added. Visibility beats negotiation every time.

The six fields, explained

1. Deliverables — countable, not vibes

List things a stranger could check off. "5-page marketing site with a contact form" beats "a website." "Logo in PNG + SVG, plus a one-page brand sheet" beats "branding." If you can't verify it, it isn't a deliverable — it's a vibe, and vibes can't be billed against.

2. Revision rounds — and what counts as one

This is the field that stops the 47-email trick, where a client sends feedback one sentence at a time and every reply resets the count. Define a round explicitly: "One round = one consolidated set of feedback → one revised version → your approval." Now "just a small tweak on slide 4" and "one more round" are different things, and only one of them is free.

3. Exclusions — the secret weapon

The list of what you will *not* do. Custom illustrations. Animation. Copywriting. CMS training. Post-launch support. Browser X support. This field does more heavy lifting than all the others combined, because scope creep almost always arrives through the "obviously included, right?" grey zone. Write the grey zone down.

4. Quote & payment

The number, the currency, the deposit, the milestone payments. Fixed price, deposit up front — that's the whole field. It looks boring. It's the one clients actually check.

5. Scoped hours — your honest estimate

Your internal honesty check. Not for the client — for you. If this project is 60 hours of work and your quote is $2,000, that's $33/hour, and you should know that *before* you commit to it. The hours field is where the "this project is actually a good deal" reality check happens.

6. Add-on rate — the price of "sure, no problem"

The rate you'll charge for anything outside the baseline: $50/hour, or $80 per extra revision round. State it even if you never use it. Its real job is signaling — a client who sees a rate next to "extras" pauses before asking for the fourteenth tweak, and that pause is worth more than the rate itself.

The template (copy, paste, fill)

# Project Scope Baseline

**Project**: ______________________
**Client**: ______________________
**Date**: ______________________

## 1. Deliverables
- [ ] ________________________________
- [ ] ________________________________
- [ ] ________________________________

## 2. Revision rounds
Included: ____ rounds
What counts as one round: one consolidated set of feedback →
a revised version → your approval.

## 3. Not included (exclusions)
- [ ] ________________________________
- [ ] ________________________________
- [ ] ________________________________

## 4. Quote & payment
Fixed price: $________
Deposit: ____% up front · Balance: ____ before delivery

## 5. Hours & rate
Estimated hours: ____
Add-on rate: $________ / hour (applies to anything outside this baseline)

## 6. Timeline
Kickoff: ______________ · Delivery: ______________

## 7. Approval
I confirm this baseline describes the work we agreed on.
Name: ______________ · Date: ______________

A filled-in example: the Brewly Coffee landing page

Project: Brewly Coffee — landing page redesign Client: Brewly Coffee (Maya, marketing lead) Date: April 3

Deliverables

• 6-section landing page: hero, story, menu, process, testimonials, footer with contact form
• Responsive at 3 breakpoints (mobile, tablet, desktop)
• Copy pass up to 1,200 words
• Figma file with final styles + a one-page launch checklist

Revision rounds: 2 rounds included. One round = consolidated feedback → revised mockup → approval. Round 3+ billed at $65/hour.

Not included: custom illustrations · motion/animation · CMS setup · email template design · social graphics · any post-launch changes

Quote & payment: $3,500 fixed · 50% deposit ($1,750) · balance before delivery

Hours & rate: estimated 55 hours · add-on rate $65/hour

Timeline: kickoff April 3 · delivery April 24

Approval: "Looks right, let's go." — Maya, April 3, 10:12 AM (email)

Now the client knows exactly what $3,500 buys. And you know that when Maya asks "can you also set up the CMS?" the answer isn't a debate — the CMS is in the exclusions list, in writing, approved.

How to use it at kickoff (this is where the magic happens)

1. Walk through it in the kickoff call. Don't email it cold — read it out loud, section by section. The exclusions list gets the most reaction, which is exactly what you want: surface the disagreements *before* work starts.
2. Send it as the follow-up. "As discussed — the baseline we walked through is attached. One sentence and we're off: reply 'looks right.'"
3. Keep the reply. "Looks right" in writing is your paper trail. It's not a contract, but it's the difference between "we agreed" and "I thought we agreed."
4. Put it where you'll actually see it. Open it next to your project dashboard, not buried in email. Every request gets compared to it — that's the whole job.

After the baseline: compare, don't argue

From the first day of work, every client request gets the same three-second test:

1. Is it in the deliverables? → Included. Do it.
2. Is it in the exclusions? → Add-on. Quote it.
3. It's in neither? → New scope. Log it, price it, bill it.

The response to a request outside the baseline is a script, not a negotiation:

"Happy to — that's outside the original scope, so I'll log it at the add-on rate and we'll settle together."

That one sentence does the work of ten. It's not "no," it's "yes, with a number attached" — and most clients either accept the number or drop the request. Both outcomes are wins. (If you want the full rundown of why this habit matters, What Is Scope Creep? covers the mechanism and the cost.)

One warning: a baseline without a logging habit does nothing. The document only helps if every add-on after it gets recorded — hours, cost, running total — the moment it's requested. That's the tracking loop, and it's exactly what the ScopeGuard docs walk through: baseline → log add-on → Creep Meter → clean add-on invoice. The pattern is the same whether you use the tool or a spreadsheet; the tool just makes the 30-second logging automatic.

The bottom line

The scope baseline is the cheapest insurance you'll ever buy as a freelancer. Ten minutes of writing converts the most common freelancing argument — "I thought that was included" — into a settled question with a written answer.

Deliverables that are countable. Revision rounds that are defined. Exclusions that are written down. A quote, hours, and a rate that are honest. That's the whole template, and it works because it's boring. The freelancers who never lose money to scope creep aren't the ones with iron wills — they're the ones with a one-page plan and the habit of checking every request against it.

Write yours before your next kickoff call. Then send it, get the "looks right," and start the project with the plan on your side instead of hoping the client's memory holds up. Start free with one active project — the first project is where the habit starts.

*Related: What Is Scope Creep? · Retainer vs Fixed Price vs Hourly: How Freelancers Choose a Billing Model · The Creep Meter: The True Cost of Every Client Add-On · How to Invoice for Extra Work: A Freelancer's Guide to Change Orders*