Chapter 1 · The resource
Set the scope and handle extra requests
Follow this course in your space: your progress is saved, and the community answers your questions.
Follow for free"While you're at it, could you add a page?" "Just one small thing: can we change the color everywhere?" One at a time, these requests look tiny. Added up, they're often the difference between a profitable project and a losing one, and between delivering on time and delivering late.
The goal isn't to say no. It's for you and your client to both know what was planned and what wasn't.
A one-page scope
A scope doesn't need to be a ten-page contract. One clear page, approved in writing before you start, is enough in most cases.
PROJECT SCOPE: [project name]
Client: [name] Date: [date]
Goal in one sentence:
[E.g.: a 5-page website to present the practice and take appointments]
Included:
- [deliverable 1, with quantity: 5 pages, 3 logo concepts, 40 edited photos]
- [deliverable 2]
- [number of feedback rounds: 2]
Not included (examples):
- [copywriting, translation, printing, maintenance after delivery]
Provided by the client:
- [list, with dates]
Key dates:
- [first version, feedback, delivery]
Approved by: [name], on [date]
The "Not included" line is the most useful one. It heads off half of all misunderstandings before they happen.
Spotting an extra request
Ask yourself three questions:
- Is it written in the scope?
- Will it take more time than planned?
- Does it change a date or another deliverable?
If the answers are no, yes, yes: it's an extra request. Examples:
- Web agency: a sixth page, a booking module, a Spanish version.
- Photographer: an extra session, 30 more edited photos.
- Graphic designer: a fourth logo direction when three were planned.
- Coach: unlimited messaging when one session a week was planned.
- Contractor: moving an outlet, adding a custom shelf.
Three answers to copy
1. Add it with a mini quote
Great idea, [First name]. It wasn't part of the original scope,
so here's how we could add it:
- what it includes: [short description]
- the time it takes: [duration]
- the effect on the schedule: [none / delivery moves to (date)]
I'll send you the add-on quote if you'd like to go ahead.
2. Save it for phase 2
I'm noting the idea, it's a good one. To keep the [date] deadline, I suggest
we finish what's planned first, then do [the request] as a second step.
I'm adding it to the "Phase 2" list so we don't forget it.
3. Swap it for something else
We can do it within the budget and timeline we agreed on if we drop
something else. For example: [planned item] in place of [the request].
What matters most to you?
The change log
Every extra request, accepted or not, goes into a table. When the client says "I thought that was included," you'll have the answer right in front of you.
CHANGE LOG: [project name]
Date | Request | Requested by | Decision | Effect on price | Effect on date
[3/12] | Extra "Pricing" page | [First name] | Added (quote #X) | Quote signed | +3 days
[3/18] | Spanish version | [First name] | Phase 2 | None for now | None
[3/20] | Change the font | [First name] | On the house | None | None
A freebie, announced as one
You're allowed to throw in something small, and it's often a good idea. But say so. A favor you don't name quickly becomes an expectation: next time, the client assumes it's included.
Happy to change the font, and it's on the house since it's quick.
I'm noting it in the project log so we have a record.
Your turn
Pick a recent or current project. Write its one-page scope using the template, focusing on the "Not included" line. Then list from memory the extra requests you accepted without saying anything, and for each one, note which answer you could have used.
Recommended tool
All your projects in one place
Flopilot brings your tasks, documents, notes and conversations together by project, solo or as a team.
Premium
Unlock every course of the group Flopilot
Every lesson, new courses as soon as they come out, and the community. No commitment.