Why freelancers lose money on scope creep (and how a change note helps)

Leon Silcott

Scope creep can reduce a fixed fee's return when the work grows without a price decision. A change note makes the extra work and its cost visible before you start.

The client asks for another export, a second version or a short addition to the brief. You may want to do it. The problem is deciding to do it without checking what it adds to the job. Over several requests, the work you deliver can become larger than the work you priced.

A change note is a short proposal: what changes, what it costs and what happens to the dates. It gives you and the client a chance to choose the addition, replace something else or keep the original scope. It cannot guarantee a profitable project or remove every disagreement.

See the effect in your own arithmetic

Consider a hypothetical designer, Priya, who prices a brand project at £3,200 and plans 80 hours including meetings, administration and handover. Dividing the fee by the planned hours gives £40 per hour. This is a project calculation, not a salary or profit figure; it does not account for every business expense or tax.

Suppose six additions each take 2.5 hours. That adds 15 hours, taking the project to 95 hours. If the fee remains £3,200, the fee divided by time becomes about £33.68 per hour. The client may have paid the accepted fee in full. The gap is between the work originally priced and the work actually undertaken.

This example does not establish how often scope creep happens or how much freelancers lose. Use your own tracked hours to see whether an addition fits your budget. Do not project one awkward job across an entire year unless your records support that calculation.

First distinguish a change from a correction

Not every extra task is scope creep. Fixing your own error, completing an omitted part of an agreed deliverable or responding within an included feedback round can be part of the original work.

Open the accepted scope before pricing. Ask whether the request changes an output, quantity, format, dependency or agreed direction. If it asks for something already promised, deal with it as that work. If the scope is ambiguous, discuss the ambiguity rather than declaring that your private interpretation settles it.

A useful reply while checking is:

“I'll compare that with our agreed scope and confirm the next step. If it is an addition, I'll describe the work and price before starting; if it's already included, I'll explain where it fits.”

Capture the whole request

A client might ask for “a few social sizes”, but you need the platforms, dimensions, content and handover format to price it. Clarify the request before issuing a neat-looking figure that leaves the same questions open.

Write down the reason where it helps the project: a new campaign date, a changed product name or an additional stakeholder. Avoid speculating about motives. The reason explains the proposed work; it should not become a diagnosis of why the client asks for changes.

Keep unanswered questions visible in your internal notes. A proposal should not imply the details are settled if you are still waiting for the source files or specification.

A change note needs five decisions

Describe the work being added, removed or replaced. Show the proposed price basis and revised total. Explain the effect on dates and dependencies. State what remains in place while the proposal is pending. Finally, ask for an explicit response.

If only part of the work is optional, make the options clear enough to accept separately. “£180 extra” is not the full decision if choosing it also moves handover by a week or removes another deliverable.

Keep the note as short as the decision allows. The aim is not to fit every change on a phone screen at any cost. A complex addition may need more detail or a separate brief before either person can sensibly approve it.

A hypothetical proposal with checked numbers

Priya's client requests a second logo route and a set of nine social exports. She prices the route at six hours at £40, or £240. The export set is 4.5 hours at £40, or £180. Together they add £420 to the original £3,200, giving £3,620.

Her proposal says:

“The second logo route is £240 and the nine social exports are £180, making £420 for both. If you accept both, the revised project total is £3,620 and handover moves from 28 November to 4 December. You can choose either addition, both or neither. Please tell me your preference so I can prepare the complete proposed scope and dates. The current accepted terms remain until you explicitly accept a revised version.”

If the client chooses one option, Priya checks the resulting schedule and total before sending that version. She does not assume the partial option has the same date effect as both additions. Each proposal should describe the actual choice being made.

If payment activity already prevents a revision, keep the original job intact and describe only the later extra in a fresh agreement.

Set out a later addition separately

Do not start from a pending proposal

A client may say the idea sounds good while still needing internal approval. Ask for the explicit decision on the actual scope and price. Do not treat “looks interesting” or an opened link as acceptance.

In AsAgreed, a complete proposed revision leaves the accepted version in place until the client explicitly accepts the new one. That distinction should match your project plan. Do not begin the new work and later argue that the client could have objected.

If a decision date affects your availability, explain it factually. “I can offer the 4 December handover if we confirm by Friday; after that I'll need to check the schedule again” is more accurate than promising you can hold the slot indefinitely.

Check whether the original agreement can be revised

AsAgreed scope and price revisions are available only before a new payment report or receipt. Once either exists, later extras need a fresh agreement. Money recorded as already paid at setup is a historical starting position, distinct from new payment activity.

That boundary matters when a client pays early. If Priya already has a new payment report on the original job, she should prepare a separate agreement for the additional route and exports. The original job remains visible with its own scope and payment history.

Explain the relationship in your covering message. Avoid copying the whole original fee into the new proposal and making it appear the client owes it twice. Use your existing project and invoice references to keep the records connected.

Choose a price basis you can explain

A fixed addition gives the client a defined amount for defined work. An hourly estimate needs a clear rate and a way to discuss the final figure. A scope exchange might remove one deliverable and add another without changing the total, but the revised work still needs to be understood.

If you include an addition at no extra charge, state the work and any date effect. That is a deliberate decision you can record, rather than a silent assumption that every future request will also be free.

In AsAgreed, an estimate needs separate acceptance of the final price before it becomes a payable balance. Do not describe a range as already owed or assume reaching its upper end is automatically accepted.

Handle “I thought that was included” as a question

Ask which part of the original brief led to that expectation. Re-read the scope together. You may find an exclusion, a genuinely unclear phrase or something you intended to include and forgot.

A suitable reply is:

“Let's check that before I price it as extra. I described the deliverables as the primary logo and the listed exports. Which part suggested a second route to you? If the wording was unclear, we should address that rather than talk past each other.”

The record supports the conversation. It does not remove the need to listen or decide every interpretation in your favour.

Keep payment history honest

When a client says they will pay for an accepted addition on Friday, that is a plan. It is not a payment report. When they actually send money outside AsAgreed, they can report it, and you confirm receipt after checking it arrived. Only confirmation reduces the confirmed balance.

Keep the original fee, accepted addition and any separate invoice references understandable. A payment made against one job should not be silently allocated to another to make your totals look tidy.

If you later agree a discount or correction, use the appropriate invoicing and accounting record. Do not invent a receipt to represent a price adjustment.

Review your change pattern after the job

Look at the requests you recorded. Were they genuinely unpredictable, or did your original scope omit a recurring need? Perhaps clients regularly need an upload stage or several export formats. That can inform your next proposal without turning it into a claim about all clients.

Keep the data modest: planned hours, actual hours, accepted additions and tasks you deliberately included. Those facts can help you price your own work. They do not prove that a particular note will protect a fixed percentage of revenue.

Choose one improvement for the next brief, such as naming file formats or identifying the client feedback owner. A more specific starting scope can make later changes easier to distinguish.

Before saying yes

Check the request against the accepted work, clarify the output, calculate the price, review the dates and ask for explicit acceptance through the appropriate proposal. If payment activity prevents a revision, use a fresh agreement for later work.

The freelancers overview shows this change process alongside scope and payments. For your next job, start with a scope and price basis that make additions easier to discuss.

Prepare your next freelance project