When a client changes the brief mid-project

Three weeks into a website redesign, the client sends a message: “We’ve been thinking — we want to position this differently.”

Maybe the product pivoted. Maybe they showed the wireframes to their board. Maybe a competitor launched something that changed their thinking. The reason doesn’t change what’s in front of you: work done, hours spent, and a new direction that doesn’t match either.

Most freelancers say “OK” and keep going. That’s the mistake.

A brief change is not a revision

Revisions refine the direction. A brief change reverses it.

“Make the headline punchier” is a revision. “We want to target a different audience now” is a brief change. “This section needs more impact” is a revision. “We’ve decided to launch a different product” is a brief change.

The distinction determines what your original agreement covers. Your contract specified a scope. Revisions work within that scope. A brief change exits it — and continuing without new terms is how you accumulate 15 unpaid hours that never make the invoice.

Stop before you go further

The moment you realize the brief has fundamentally shifted: don’t start working on the new direction yet.

This sounds obvious. It isn’t, because clients are usually excited about the pivot, and the momentum of the conversation carries you forward. They explain the new direction, it makes sense, and you’re already thinking about execution before you’ve said anything about terms.

Pause. Send one message — that day, before you touch anything:

“Before I start on the new direction, I want to align on scope and what happens to the work done so far. Can we set up a 15-minute call this week?”

That message resets the conversation to commercial terms before creative ones. It also creates a timestamp — evidence that you treated the change as a decision point, not a continuation.

What the call needs to establish

Three things to agree on before you move forward:

What has changed, specifically. Not a vague summary — which deliverables are affected, what’s being kept, what’s being replaced. That precision prevents a second round of scope drift two weeks later.

What happens to the work done so far. Hours already worked are billable. You agreed to deliver X, you did the work toward X, the client changed their mind. That doesn’t retroactively make those hours free. The invoice for work completed under the original brief is separate from the question of what comes next.

What the new scope looks like. Timeline, deliverables, cost. The new direction may require more time, different expertise, or both. This is where you present a revised estimate — not an apology.

Three real options

You have real options when a client changes direction. None involve absorbing it silently.

Reset and reprice. Invoice for what was built under the original scope. Then agree on new terms for the new direction. Present the split cleanly: “Here’s the invoice for work completed through [date]. Here’s my estimate for the new direction.” Most clients who have worked with freelancers before understand this. A direction change mid-project has a cost — and they made the decision that triggered it.

Reduce scope to stay in budget. “I can accommodate the new direction if we remove [specific deliverable] from the original scope.” The client gets the pivot without an unexpected bill. You trade one deliverable for another at similar cost. This only works if the time involved is genuinely equivalent.

Stop and restart as a new project. If the new direction requires redoing most of what was done — new research, different structure, different deliverables — that’s not a brief change. That’s a new project. Say so clearly: “What you’re describing is substantially different from the original scope. I’d need to treat this as a new engagement, starting from a revised brief. Do you want to discuss what that looks like?” Most clients either agree or realize they’ve asked for more than a pivot.

What you shouldn’t do: absorb it as a revision and continue without updating the terms. That path ends with an invoice that doesn’t reflect reality — and a client surprised by it.

Your calendar as the audit trail

When a brief changes mid-project, timestamps matter.

Scope creep often arrives gradually — extra calls, small additions, shifting requirements — before a full direction change lands. If your calendar events are named consistently — [Acme][Website] Initial research, [Acme][Website] Positioning workshop, [Acme][Website] Brief change call — you have a dated record of what work belonged to which version of the brief.

That record matters if the client later disputes the hours billed before the change. Not as ammunition — as documentation. The before/after is factual when your calendar shows it.

Timescanner reads those events and shows totals by client and project. What was spent on the original direction, what the pivot will require. If you’re on project-based billing and need to justify the hours accumulated before the change, that data is already there — without reconstruction.

Timescanner generates billing reports directly from your calendar. Any iCal-compatible calendar works — Google Calendar, Outlook, iCloud, Proton Calendar, Notion Calendar, Fastmail.