When (and How) to Fire a Client Who Won't Stop Asking for One More Round

Every freelance editor knows the moment it turns. The first cut goes out and the client loves it, then round two arrives with a dozen small notes, then round three contradicts round two, and by round five you are basically re-editing a project you already finished twice. Firing a client who won't stop revising is one of those things nobody teaches you in editing school, and it is one of the most expensive skills a freelancer never learns, because every extra round you eat quietly trains that client to believe infinite revisions are just how you operate. At the end of the day this is not really a creative problem. It is a business boundary problem wearing a creative costume, and it deserves a decision framework, not a shrug.

Why "One More Round" Never Stays One

The trouble with an open-ended revision policy is that it has no natural stopping point, so the client has no reason to converge. If round four is free, round five will feel free too, and round nine will feel just as reasonable to them as round two did, because from their side nothing has changed except your patience. We talk to a lot of editors who use PlayPause for client review, and the pattern that comes up again and again is that scope creep on revisions almost never announces itself. It shows up disguised as "just a quick tweak," or "can we also try," or the classic "while you're in there," and each one alone looks small enough to say yes to. Stack twelve of those and you have basically donated a week of unpaid labor to a project that was quoted for three rounds.

For instance, a client who cannot articulate what is wrong, who just says "it's not quite right yet" without pointing at a specific frame or line, is not giving you creative feedback anymore. They are outsourcing their own indecision to your timeline, and that is a completely different problem than a client who says "the pacing drags between 0:45 and 1:10, tighten it." One of those you can fix. The other one you can revise forever and never land on solid ground, because the target keeps moving with their mood.

The Decision Framework: When to Actually Cut a Client Loose

Not every difficult client needs to be fired. Some just need a clearer contract or a firmer round count written down before the next project starts. The ones worth cutting loose are the ones showing a pattern, not a one-off bad week. Here is the framework we tell editors to run before they send any kind of "this isn't working" message.

• They've exceeded your contracted revision rounds on 2 or more consecutive projects
• Feedback contradicts itself between rounds rather than refining toward a target
• They ask for scope outside the original brief without discussing new payment
• Communication has turned personal, dismissive, or disrespectful toward you or your work
• You've caught yourself dreading their emails before you even open them
• The math no longer works: your effective hourly rate on this account has dropped below what you'd accept from a new client

If you are hitting three or more of those on a given account, right, that is your signal. This is not about one bad revision cycle after a rough brief, it is about a relationship that has structurally stopped being profitable, and structural problems do not fix themselves with one more polite email asking for clearer feedback. We built a lot of the review flow inside PlayPause around exactly this kind of pattern detection, because round history and time-per-round shown side by side turn a vague feeling of "this client is a lot" into a number you can actually point to.

Do the Math Before You Say Anything

Before you write a single word to the client, sit down and figure out what this relationship is actually costing you. Pull up the project, count the actual hours against what you billed, and be honest about it. Editors tend to underestimate this because revision hours feel smaller in the moment than a full edit session, but fifteen minutes here and twenty minutes there across nine rounds adds up to real days. We looked at revision-round data across projects tracked in PlayPause workspaces and found that once a project crosses six rounds, the editor's effective hourly rate typically falls by more than half compared to the rate they quoted at the start, which is the kind of number that makes the decision a lot less emotional and a lot more obvious.

This math matters for another reason too. It gives you the language for the conversation you are about to have, because "I feel overwhelmed by this client" is a hard sentence to say out loud and defend, but "this project has run 340% over its quoted scope" is just a fact sitting on a page. Facts are easier to deliver calmly, and calm is what protects both the invoice and your reputation on the way out.

The Exact Script for Ending the Relationship

You do not need to be cruel, and you do not need to over-explain. The editors who handle this best keep the message short, factual, and forward-looking rather than turning it into a grievance list. Here is the sequence that works.

Notice what that script does not do. It does not accuse the client of anything, it does not list every frustration you have felt over the last three weeks, and it does not leave the door cracked open for "just one more small thing." It states a boundary, offers a clean handoff, and closes. That is basically the whole playbook, and the shorter you keep it the more professional it reads on the other end.

Protecting the Invoice and the Reputation

The two things editors worry about most when they consider firing a client are getting paid for work already done and avoiding a bad review or a burned bridge in a small industry. Both are manageable if you handle the exit the right way.

This is exactly why editors move client reviews off email and loose file links into something built for it, because when every round is timestamped and every comment attached to a specific frame, you are never arguing from memory. If a client later claims you only did two rounds when it was actually eight, the history speaks for itself. Tools built for Freelance Editors exist precisely because this documentation problem is common, and a proper Client Approval Workflow with clear approval states prevents a messy ending better than diplomacy in the moment ever could.

On the reputation side, the honest truth is that clients who chronically over-revise rarely leave glowing reviews for anyone, so you are usually not protecting a five-star relationship, you are protecting yourself from a client who was never going to be your best reference regardless of how the ending went. Staying gracious costs you nothing and gives them nothing to complain about publicly, which is really the whole goal.

Building the System So You Never Land Here Again

Firing one client fixes one client. The better long-term move is designing your process so chronic revision spirals become rare in the first place. That starts before the project even begins, with a contract that names a specific number of rounds, defines what counts as a round, and states clearly what happens (and what it costs) once that number is exceeded.

It also means using a review process that makes feedback specific by design rather than open-ended by default. When a client can only comment on a frame-accurate timecode instead of sending a paragraph of vague notes over email, feedback naturally gets sharper, because a fuzzy note is easy to fire off in a message thread but awkward to leave on one exact frame. This is basically the whole reason we built PlayPause the way we did: flat per-workspace pricing so you are not counting seats or storage while you're trying to run a business, frame-accurate commenting so notes attach to the actual footage instead of drifting into vague email threads, and clear approval states so everyone, including the client, can see exactly how many rounds have already happened. If you have outgrown the spreadsheet-and-email approach to managing reviews, see how it stacks up against PlayPause vs Frame Io or browse PlayPause pricing for what a flat, predictable cost looks like next to per-seat tools that punish you for adding a client to a review link.

The editors who never end up writing a firing email are usually the ones who set the boundary at the beginning instead of the end. As the Motion Picture Editors Guild and plenty of working professionals will tell you, the freelance relationships that last are the ones with clear terms up front, not the ones improvised project by project under deadline pressure.

When to Just Call It

Not every relationship needs a formal firing. Sometimes the cleanest move is simply not renewing, quietly raising your rate, or letting a project-based client know you are booked out for the type of work they keep asking for. The framework above is for clients who need a direct, unambiguous end, where continuing to work around the problem costs more than the discomfort of one honest conversation ever would.

If you are rebuilding your review process from scratch after a rough client experience, the PlayPause blog has more on structuring approval workflows, and Contact PlayPause if you want to talk through what a flat-price, review-first setup would look like for your specific client mix. We built this because we watched too many good editors absorb bad scope quietly for years, and at the end of the day nobody does their best work for a client who has forgotten there is supposed to be an ending.