How-to guide · Clients & workflow

How to handle a bad review

By the WorkKitly Team · Last updated: November 2026 · 7 min read

A bad review lands like an attack and reads like a verdict. To the next client who finds it, though, it is mostly evidence of something else: how you behave when the work goes wrong. That is why your reply matters more than the review, and why the response splits into three jobs, done in order. Reply publicly, once: briefly, with thanks and at most one documented fact. Fix privately whatever can honestly be fixed, without conditions attached. Then read the review a third time, for the sentence in it that is true, and change the thing that caused it.

1. Read it like a stranger

Before any reply, untangle it. Three different things arrive knotted in every bad review, and each needs a different response. There is a fact you can check: dates, deliverables, what was promised and what arrived. There is a feeling you cannot argue with: frustration, embarrassment in front of their team, the sense of being let down. And there is a lesson that might be real: the one sentence in the review you would rather not read twice. Facts get checked. Feelings get acknowledged. Lessons get acted on. Almost every bad reply comes from answering one as if it were another — disputing the feeling like a fact, or defending the fact so hard the lesson never gets heard.

So give it a day. The 24-hour rule is not about politeness; it is about authorship. Draft the reply you want to send while it still stings — sarcasm, itemised rebuttal, wounded dignity, all of it — then close it. The draft is therapy. The reply is publishing, and publishing is read by strangers, in a hurry, forever. What you write tomorrow morning — after a night in which nothing about the review changed except your temperature — will be shorter, calmer and harder to argue with: it will only say the things still true when you are no longer angry.

Spend the waiting hours on records instead. Screenshot the review exactly as it stands — date, reviewer, wording — and file it with the project notes. Reviews get edited, occasionally deleted; memory edits itself in your favour and against it by turns. Your records should not rely on memory — the same discipline our guide to taking client call notes builds for live projects: a note made at the time beats a recollection made later, in calm or in anger. Then sort it line by line: this claim is a fact, and it checks out or it doesn’t; this line is a feeling; this one is the lesson. By the time the day is up, the sorting has drafted your reply, chosen your fix and named your change.

2. The public reply: once, briefly, for the next reader

Your reply is not written to the reviewer. It is written to the next client, who will find it while deciding whether trouble with you is handled like an adult. That reader needs to see you specific, brief and unshaken, not victorious. The anatomy is four parts: thank them for the feedback. Name the concrete thing you are sorry for — a specific failure, not a blanket grovel and not the non-apology of “sorry you feel that way”. State one corrective fact, if it is plainly documented. And open the offline door: a real way to reach you, so the conversation can move somewhere private. The whole reply below runs to 72 words:

Thank you for saying this plainly — I’d rather know. You’re right that the final draft reached you four days late, and I’m sorry: that delay was mine, and it put your launch under pressure it didn’t need. The revised version has since been delivered in full. If there’s anything still short of what you expected, I’d welcome the chance to put it right — you can reach me at [your email].

What the reply leaves out is most of the craft. Never the client’s private details — nothing about their business or team that they did not put in the review themselves. Never the fee: money argued in public reads as the whole story, whatever the merits. Never the argument: a point-by-point rebuttal invites a point-by-point war, conducted in front of every future client you will ever have. Never sarcasm, and never the word “actually” doing combat — “Actually, the files were sent Tuesday” is a glove-slap in a correction’s clothing, and strangers can tell. And never a threat: section 4 covers where a lawyer belongs, and it is not in the reply. Then stop: one reply is a professional responding. A thread is a billboard rented for your worst week — every extra round becomes the main story for the next reader, long after the review itself has stopped mattering.

3. The private fix: once, off-platform, without conditions

If the review points at something that can still be put right, reach out once — privately, off the platform, and without conditions. The condition point is not etiquette; it is the line this whole guide stands on. A fix offered in exchange for the review being changed or removed is not a fix: it is a transaction, and exactly the dealing platforms prohibit. Platforms prohibit fake and incentivised reviews, and a benefit offered for an edited review sits on the same side of that line — the exact rules live in each platform’s policy, so check there before you act. Make the fix because the work deserves it; if the client later chooses to update their review, that is theirs to choose — unprompted, unmentioned by you.

A real fix is as concrete as the failure was. The missing deliverable, finished properly and sent without an invoice for the repair. A partial refund where the work genuinely fell short — money settled honestly, on its own track, never traded against the review (the same discipline as our guide to what to do when a client won’t pay). Or the apology with the change named: not a second “sorry” sent into the void, but “the draft was late because I confirmed the date before checking my calendar; I now confirm every deadline in writing, the same day”, which is an apology a stranger could verify. One attempt, made well. If it is refused or unanswered, the reply already on the page is your complete position — and it is enough.

And there are reviews you should not try to fix, because the complaint is not a failure. The review that objects to a price agreed in writing before the work began. The one angry that scope refused in writing — a quote’s exclusions doing exactly their job — was not quietly given away free. The one left by a client you fired for cause (see our guide to firing a client professionally). For those, the calm public reply is the whole remedy. Chasing a fix there reopens arrangements that were right, to please the one reader who was never going to be pleased — and teaches the next reader the wrong lesson about what pressure achieves with you.

4. If it’s false: facts, opinions and the one careful route

Some reviews are not unfair readings of a real project; they are simply not true. Separate the two kinds of falsehood; they have different remedies. Harsh opinions — disorganised, overpriced, not worth it — are the reviewer’s to hold, however little you recognise them. A platform will not rescue you from an opinion, and arguing with one in public only amplifies it. False statements of fact are different: “he took a deposit and delivered nothing”, “she claims qualifications she doesn’t have” — claims a stranger reads as events, not judgements. Those are what platform report routes exist for: flagging content that violates policy, documentation attached. What qualifies and how it runs is set by each platform’s own policy — read that page, not any guide’s summary, before you file.

The sequence: document first — the screenshots and records from section 1 are the case. Report once, through the platform’s route. Reply publicly with the single documented fact, calmly: “For the record, this project was delivered in full on the date in our shared thread, and the final files are with the client.” Then let the reply do the work while the platform does whatever it does. Report once: a claim filed five times is not five times as strong. Keep the reply free of the word defamation, of legal threats and of speculation about who the reviewer “really” is: all three read as bullying to a stranger, whatever their merits.

As for lawyers: a review earns a lawyer’s opinion when it states provably false facts and the harm is real and demonstrable — work you can point to losing, not a bruised week. Whether a given review crosses that line is a judgement for a lawyer where you live, and this guide is general guidance on professional practice, not legal advice. If a lawyer is ever involved, the work happens through letters and processes, never inside the review thread. The moment a legal threat appears in your reply, the threat becomes the story — and you its villain to every reader who was not there.

5. The change: the only part fully in your control

The reply is for strangers and the fix is for the client, but the third job is for you — and it is the only one entirely in your control. If any sentence in the review is true, it stops being an insult and becomes a process item. Run it through the same discipline as a project postmortem — our guide to running a project retrospective turns findings into one changed template, clause or checklist line — and let the review’s truest sentence write one of yours: deadlines confirmed in writing the same day; the check-in that would have caught the drift in week two; the scope line whose absence cost the argument. A change you can name, in the next reply you ever have to write, is worth more than the review cost you.

Then watch for the pattern, because single reviews mislead and repetition does not. One complaint about lateness is weather. Three reviews naming the same thing — the silence between milestones, the invoice that arrives as a surprise, the draft that lands on the last possible day — are climate: a feature of how the practice runs, priced into your reputation whether you read them or not. It is the same pattern-spotting the review in our guide to auditing your client list applies to money — honestly read numbers saying what one impression cannot.

And the long game, played quietly: the only real counterweight to a bad review is a body of good ones that are specific, recent and plainly earned — collected the honest way our guide to getting testimonials and case studies sets out: asked for after a result, in the client’s own words, published with permission. Never manufactured. No friends posting praise for work they never bought. No discounts traded for stars. No steering only the delighted toward public platforms while the unhappy are routed somewhere private — gating, manipulation even when every published word is true. A wall of earned reviews can absorb one bad day in public, because readers can tell the good ones cost somebody something real. A manufactured wall falls at the first close reading — and takes the honest reviews down with it.

Questions

Asking is fine and normal — most satisfied clients simply never think of it, and a prompt after a good result is honest practice. The line sits at everything after the asking. Never incentivise: no discount, gift or favour offered for a review, whatever its content. Never gate: sending the happy clients to the public platforms while the unhappy are routed to a private form is manipulation even when every published word is true. And never script the words. Ask everyone the same open question and publish what comes back, good and bad, in their own phrasing — a profile built that way can absorb one bad review, because a reader can tell the praise cost somebody something real.
Only if it breaks the platform’s policies — and platforms remove reviews for policy violations, not for hurting. The report route exists for the violations: a review that is fake, that states provable falsehoods as fact, that comes from a conflict of interest, or that reviews an engagement that never happened. A genuine client’s harsh opinion, however unfair its tone feels, is not a violation, and no platform will lift it for being bad for business. So report the ones that qualify, with your documentation attached, and answer the rest with the reply and the fix. What qualifies is defined in each platform’s own policy — check that page before you file.
Within a day or two — after the cooling draft, never instead of it. Run the 24-hour rule first: draft the reply hot, sleep, then send the version you wrote calm. That lands fast enough that your profile looks alive and minded, and slow enough that the reply is the professional one. Two things belong in the gap: checking every date, figure and fact in your draft against your saved records, because a reply containing an error of your own is the one outcome worse than silence — and reading the review a second time for the sentence that is true, which is where the fix and the change come from.
Say so plainly, in one documented sentence: “I have no record of working with this reviewer, and I have reported the review to the platform.” Then report it through the platform’s route — a review of an engagement that never happened is exactly what that route exists for — with whatever records show your actual client list for the period. And move on. Do not argue in the thread, do not speculate publicly about who the reviewer might be, and do not recruit real clients to answer it on your behalf; a calm single sentence plus a filed report reads, to every future client who finds it, as the whole story.

Related: the proof you earn, the exit you keep clean, the debrief

The good reviews that outweigh a bad one are built the slow way — getting testimonials and case studies covers asking after a result, in the client’s own words, with permission. When the relationship itself is the problem, firing a client professionally ends it with a clean handover and a settled account — the exit that gives a bad review nothing to stand on. And every lesson a review teaches belongs in the record: running a project retrospective is where a complaint becomes a changed clause, template or checklist line, so the next review has less to say.