When to ask a client for a review (a timing map for project work)

Wording matters less than timing. A mediocre request sent the afternoon a project lands will beat a beautifully written one sent six weeks later, because it arrives while the client still feels how the work went rather than merely remembering that it went fine.

Goodwill has a half-life. Here’s where the good moments are.

The best moments, ranked

1. Immediately after a compliment

Someone says on a call or in Slack that this was the smoothest launch they’ve had. This is the single best moment there is, and it lasts about a day. They’ve already composed the review — you’re just asking them to write it down. Ask that same afternoon, and quote their words back to them so they don’t have to start from nothing.

2. Handover day

The default trigger for most project work: you deliver, you hand over access and documentation, you ask. Attention is on you, the outcome is agreed, and the relationship is at its warmest. If you only ever establish one habit, make it this one.

3. With the final invoice

The one email that always gets read. Add three lines and a link at the bottom, and state clearly that the review has nothing to do with the payment. Its real advantage is process: the invoice always goes out, so the ask always goes out with it.

4. Two to four weeks after go-live

The best moment for a review with substance in it. By now the client has numbers — the site is faster, the backlog is clearing, support tickets have dropped — and “they delivered on time” becomes “our checkout conversion is up and the team stopped firefighting.” Reviews written here are markedly more useful than reviews written on handover day, which is a good argument for asking at both moments.

5. Quarter boundaries on a retainer

Ongoing work has no natural finish line, which is why long-standing clients so often have never been asked. Manufacture the moment: attach the ask to a quarterly summary or a monthly report, and ask about the relationship rather than a deliverable — responsiveness, reliability, whether they’d recommend you.

6. Renewal or expansion

A client who just re-signed has, in the most concrete way available, told you they’re satisfied. Ask a week after the paperwork is done — not during the negotiation.

7. Right after they refer you

A referral is a stronger endorsement than any review, and someone who has just made one is already in the frame of mind to write one. Thank them for the introduction, then ask.

8. When your champion changes jobs

The one nobody thinks of, and often the last chance you’ll get. Someone leaving a role is unusually willing to speak generously about work they’re proud of, and once they’re gone from the company, their institutional memory of your project goes with them. If you see the announcement, ask that week.

The moments to avoid

• Mid-project. The outcome isn’t known yet, so the review can’t say anything useful, and asking signals that you’re fishing for reassurance.
• While a bug or incident is open. Obvious, and still worth saying: never send an automated-feeling ask into an active problem. Fix it, wait a fortnight, then ask — a client whose incident you handled well often writes the best review you’ll ever get.
• During an invoice dispute or scope disagreement. The request reads as leverage even if you don’t mean it that way.
• During renewal negotiation. Same problem in the other direction: it looks like you’re asking them to commit publicly before they’ve decided privately.
• Their crunch periods. Retail in December, finance teams at year end, education at term start. Wait two weeks. It costs you nothing and roughly doubles your odds.

A cadence that stops at two

Three touches, then done. The discipline is in stopping.

• Day 0 — the ask. With the handover or the final invoice. Specific request, named effort, one link.
• Day 7 — one nudge. Short, capped in writing (“once, then I’ll leave it alone”), with a genuine out.
• Day 21 — close the loop. Tell them you’re closing the request, leave the link live, thank them for the project. This message occasionally produces the review, and always ends the exchange cleanly.

After that, stop. A fourth chase costs more goodwill than the review is worth, and the client who ignored three messages is telling you something. Put the effort into next month’s asks instead — the reliable route to more reviews is more first asks, not more follow-ups per ask.

The scripts for all three touches are in how to ask a client for a review politely.

If you missed every window

Say so. A late ask that acknowledges the delay works far better than one that pretends the project ended last week: “We finished the portal back in March and I never properly asked — if it’s held up on your side, would you leave a few sentences?” The worst outcome is a polite no, which is exactly what you have now.

Make the timing automatic

Timing fails for a mundane reason: at the exact moment you should ask, you’re busy starting the next project. The fix is to have the link already exist.

In Reviewee, you create a review link for a client or project up front and send it whenever the right moment arrives — from Reviewee, or pasted into your own handover email or invoice. Every link shows as pending or completed, so at any point you can see which clients are still sitting in the follow-up window and which have gone quiet long enough to close out.

If reviews are getting lost between account managers rather than between dates, read the review gap in outsourced work.