Problem · scope creep
Log the scope, then log every change.
“Just one more thing” turns into ten more things. Record the original agreement and every request after it, so the extra work stays visible when you invoice for it.
What is scope creep?
Scope creep is when a project grows beyond what was agreed, with more pages, more revisions or more features, while the budget and deadline stay the same. For freelancers it usually arrives as small requests ("can you also...", "while you're at it...") that each seem too minor to price, but together add days of unpaid work.
It's the norm rather than the exception: PMI's 2018 Pulse of the Profession report found that 52% of completed projects experienced scope creep. The way to stop it is to write down the agreed scope, log each new request against it with a date, and price changes before you start them.
- Worked example: a £3,000 project quoted at 40 hours is £75 an hour.
- Fifteen hours of small extras later, you've earned about £55 an hour: a 27% pay cut nobody agreed to.
How scope creep actually happens
Week 1: the original agreement
The client agrees to a 5-page website with a contact form. You quote £2,000. Everything is clear, and you start work.
Week 2: “just one more thing”
The client emails: “Can we add a blog section? Just 3–4 pages.” You say yes to keep them happy, without writing it down or discussing payment.
Week 3: another quick addition
On Slack: “Actually, we need an e-commerce section too. Shouldn't take long, right?” You're deep in the project, so you add it.
Week 5: the dispute
You send the final invoice. Client: “This should have been included. We discussed all of this at the start.” With no clear record, you've done far more work for the same £2,000.
What scope creep costs you
Each small yes feels harmless. Together they eat into your rate, your schedule and your relationship with the client.
- Unpaid hours, often 20 to 40 extra per project
- A lower effective hourly rate, for example £50 an hour falling to £20
- Time you could have spent on paid work
- Thinner margins on fixed-price projects
- Other project deadlines slipping
- Clients learning to expect unlimited revisions
- Resentment and burnout from unpaid overwork
Why email and Slack don't solve this
Without a record
With ClearTimeline
Original scope buried in email threads
Original scope locked with a timestamp
Change requests scattered across messages
Every change in one timeline
“I think it was in March?”
Exact timestamps for every request
Forwarding messy email chains as evidence
A clean PDF export
How ClearTimeline tracks scope
Document the original agreement, log every change, and have a clear record if a client says “this was always included”.
- 01
Log the original scope
When you start, log exactly what the client agreed to. It's locked with a timestamp and becomes your baseline.
- 02
Log every change request
When the client asks for something new, log it as a scope change, with optional notes on time and cost. No edits, no deletes.
- 03
Share the progress portal
Your client sees the original agreement and every change they've asked for, live. Being open from day one helps prevent disputes.
- 04
Export the record if needed
If a client says extra work was always in scope, export a PDF showing the original agreement and each change request with its timestamp.
“This was all included in the original quote.”
An example scenario: a brand designer whose “small tweaks” turned into major redesigns.
Seeing all eight requests in order, the client said “I didn't realize we changed so much.”
10 Jan 2026, 11:00 UTC
Original scope logged: 3 brand concepts, 2 revision rounds
18 Jan 2026, 15:20 UTC
Change request 1: “Actually we want 5 concepts”
25 Jan 2026, 10:05 UTC
Change request 2: “Add packaging design”
2 Feb 2026, 14:40 UTC
Change request 3: “Need social media templates too”. Five more follow
3 Mar 2026, 09:30 UTC
Client: “This was all included in the original quote”
3 Mar 2026, 12:15 UTC
Timeline shared. Client paid for the extra work
Questions
Should I charge extra for every scope change?
That's your decision. ClearTimeline doesn't enforce pricing — it gives you evidence. Many freelancers absorb small changes but charge for major ones. The key is having documentation so you CAN charge if needed, and clients can't claim 'this was always included.'
Won't this make me look untrusting to clients?
No. Frame it as professional project management: 'I use ClearTimeline to keep us both aligned on scope and progress.' Most clients appreciate transparency. The ones who push back are usually the ones planning to take advantage.
What if the client verbally agrees to changes in a call?
Log it right after the call. Note: 'Client requested X during call on [date].' Even if logged a few hours later, you have a timestamped record. Better than nothing.
Can I use this for hourly projects?
Yes. Even on hourly projects, clients sometimes dispute how many hours certain features should take. A scope tracker shows exactly what was originally agreed vs. what was added, justifying additional hours.
Do clients see the scope changes immediately?
If you share a progress portal with them, yes. This is actually beneficial — they see in real-time what they're requesting. It often makes them more thoughtful about changes.
Keep reading
Dispute risk calculator
Check your project's risk of payment disputes and scope creep in 30 seconds.
Scope change tracker
Document the original scope and every change request with a timestamp.
Scope creep prevention guide
Practical strategies for keeping scope under control.
Client progress portal
Share live project updates so clients see scope changes as they happen.
Stop working for free because of scope creep
Document your next project from day one. Free forever for one project.