Skip to main content
Out of Scope

is redoing work after a client pivot out of scope?

Yes — when a client pivots their direction and asks you to rebuild work you already delivered correctly, the rework is new scope and warrants a new fee. The exception is a pivot caused by your own misread of an approved brief, which you fix on your own dime.

Why this answer

A pivot and a revision look similar from across the room but they're fundamentally different animals. A revision refines work toward a target everyone already agreed on; a pivot moves the target itself. When a client decides halfway through that the campaign should be playful instead of corporate, or that the app should serve a different audience, the work you built toward the original target wasn't wrong — it was correct work aimed at a goal the client has now abandoned. Asking you to redo it isn't asking you to fix a mistake, it's asking you to do a second project's worth of work for one project's fee. The contract scoped a specific brief; the pivot replaces that brief. This holds even when the client is right to pivot — sometimes changing direction is the smart business call — because being right about the new direction doesn't make the old direction your error. The labor you already spent building toward the original goal was real, and it doesn't disappear just because the destination moved.

When the answer flips

This flips back onto you when the 'pivot' is really a correction of your own misread — if you built toward an interpretation the approved brief didn't actually support, then redoing it is just delivering what you were always hired to deliver. It softens toward absorbable when the pivot lands very early, before you've built much, where adjusting course costs little and the goodwill of flexibility outweighs the marginal work. It can also genuinely be in-scope if your contract was written around iterative discovery, where exploring directions and changing course was the explicit point of the engagement. The verdict stays firmly out-of-scope when the original direction was approved in writing and built against, when the pivot arrives after substantial completed work, or when the client frames a wholesale change of direction as 'just a few tweaks' to avoid paying for what is plainly a rebuild. Late, post-approval pivots are the clearest case for a change order.

What to do next

Name the difference between a revision and a pivot out loud, because the client may genuinely not see it. Say something like: 'The original brief was approved and I built to it — moving to this new direction means rebuilding rather than refining, so it's a change order rather than a revision round.' Then quantify what's salvageable and what's truly new, because pivots are rarely total: some discovery, some assets, some structure usually carries over and you should credit that honestly in the price. Quote the rework as scoped new work with its own brief and timeline, not as open-ended hourly drift that lets the new direction wander too. If the pivot is the client's smart call, you can acknowledge that warmly while still pricing it — being supportive of the decision and charging for the labor are not in tension. And always pause dependent work before rebuilding, so you're not stacking more output on a foundation the client is replacing.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

How do I tell a real pivot from a normal revision?+

Ask whether the target moved or the aim got tighter. A revision keeps the same goal and adjusts execution toward it — different headline, warmer tone, cleaner layout, all still serving the brief everyone signed off on. A pivot abandons the goal itself: the audience changes, the strategy changes, the whole point of the piece changes, and the prior work no longer serves any agreed purpose. The tell is whether your earlier work was wrong or merely aimed elsewhere. If you'd have built the same thing knowing what you know now, it's a pivot; if you'd have built it differently because you misread the brief, it's a correction. That distinction decides who pays, so it's worth getting precise about before you quote.

The client says the new direction is what they 'meant all along' — now what?+

Go back to the approved brief, because intent that was never written down doesn't override what was. If the documentation supports the original direction you built toward, then 'what they meant all along' is a reinterpretation after the fact, and the rework is still new scope regardless of how the client now remembers the conversation. Be gentle about it — people genuinely misremember their own earlier thinking — but anchor to the record rather than to competing memories. If the brief was genuinely ambiguous and your reading was reasonable, you're in shared-fault territory and a partial credit on the rework is fair. The approved brief is the referee; that's exactly why getting direction in writing at the start protects both of you here.

Should I credit the client for any work that carries over after a pivot?+

Yes, and doing so makes your pricing far more persuasive. Almost no pivot is total — the discovery you did, the research, the asset library, the underlying structure, sometimes even whole components survive the change of direction. Itemizing what carries over and pricing only the genuinely new work shows the client you're charging for labor, not punishing them for changing their mind. It also keeps the number fair, which keeps the relationship intact. The version of this that goes badly is quoting a full second project fee when half the foundation still stands; the version that goes well is a clear ledger of 'this survives, this is new, here's the cost of the new.' Honesty about reuse is both the fair move and the persuasive one.

What if the pivot is genuinely the client's smart business decision?+

Then support the decision and still charge for the work — those aren't in conflict. A pivot can be the right call for the client's business and simultaneously be unpaid labor for you, and pretending otherwise just means you subsidize their good strategy out of your own time. You can say, sincerely, 'I think this new direction is stronger, and here's the change order to build it.' Clients respect a freelancer who backs their judgment without quietly eating the cost of acting on it. The instinct to absorb rework because the new idea excites you is a generous one, but excitement isn't a billing model. Be enthusiastic about the direction and clear about the fee in the same breath.

The client pivoted early, before I'd done much — do I still charge?+

Often not, and that restraint is good business. When a pivot lands before you've built real output — during early discovery, before the first concepts — adjusting course costs you little, and absorbing that small change buys disproportionate goodwill. The fee should scale with the sunk work, and early sunk work is minimal. Save the change order for pivots that arrive after substantial completed deliverables, where the rebuild is genuinely a second effort. Charging for a course-correction in week one over a few hours' work tends to read as rigid and can sour a relationship you'll want intact for the rest of the project. Judgment matters here: small early pivots are part of the normal texture of creative work, not scope creep.

How do I price the rework without it spiraling into endless changes?+

Scope it as a fresh mini-project with its own approved brief, not as open-ended hourly work. The risk with rework is that the new direction is less settled than the client thinks, so if you bill it hourly with no fixed brief, you can end up chasing a moving target a second time. Pin down the new direction in writing before you quote, fix the deliverable and the revision rounds just as you would for any project, and make clear that further changes of direction are further change orders. This converts a vague 'can you redo it' into a bounded, priced piece of work. The structure that protects you on the original project — clear brief, fixed rounds, named fee — is exactly the structure that protects you on the redo.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide