"Yeah, that looks great, go ahead" is one of the most common sentences in freelance work — and one of the least useful on its own. Said on a call, in a meeting, or over a voice message, it disappears the moment the call ends. Three weeks later, when a disagreement comes up about what exactly was approved, a spoken "yes" is worth nothing next to an email the client can scroll back to.
This is not about distrust. Most clients who approve something on a call fully mean it. The problem is memory, not honesty — people misremember details, forget exactly what was shown, or simply move on to the next thing without a record to check against. The fix is a habit: after every call where something gets approved, send a short written recap the same day, and ask for a one-line confirmation.
The core rule: recap first, ask second
A good post-call recap does two things in order: it restates what was approved, specifically, and then it asks the client to confirm that restatement is correct. Don't skip the second part — a recap with no response is still just your word against theirs if a dispute comes up later. The templates below follow this structure.
1. The standard call recap
Send this within a few hours of the call, while the details are still fresh for both sides.
Hi [Name],
Quick recap from our call today — to confirm I've got it right: you approved [deliverable/version] as final, including [specific details discussed]. I'll move ahead with [next step] based on that.
Let me know if I've missed anything, otherwise I'll take this as confirmed.
[Your name]
2. The recap for a design or content approval shown on screen
When you shared your screen or walked through something live, be specific about which version was seen — this is the detail that gets disputed most often.
Hi [Name],
Following up on today's call: you approved [design/draft] version [v2], the one with [specific detail — e.g. the updated header and blue color scheme]. I'll proceed to [next phase] on that basis.
If that's not quite right, just reply and I'll hold off.
[Your name]
3. The short version, for a quick verbal yes
For smaller approvals that don't need a long recap — still worth a written line.
Confirming what we discussed: [item] is approved, no changes needed. I'll go ahead and [next step]. Thanks!
4. When the approval came through a voice message or quick call, not a meeting
Voice notes and five-minute calls are easy to forget happened at all. Treat them the same way.
Hi [Name],
Got your voice note/call earlier — just writing it down so we both have it: you approved [item] as-is. Moving ahead with [next step] based on that.
[Your name]
5. Asking for an explicit confirmation when the client doesn't reply to the recap
If a recap goes unanswered for a few days, don't assume silence means agreement — ask directly, once, with a deadline.
Hi [Name],
Just checking on the recap I sent on [date] about [item] — wanted to make sure it matched what we discussed on the call. If I don't hear otherwise by [date], I'll go ahead on that basis so we don't lose time.
[Your name]
6. The recap that also protects the timeline
If the approval unlocks the next phase or a payment milestone, say that explicitly — it turns a casual confirmation into something with a date attached.
Hi [Name],
To confirm from our call: [item] is approved as final. As per our agreement, this starts the [X-day] window for [next phase/final payment], so I'll move ahead from today's date.
[Your name]
Where to send the recap, and why email usually wins
Slack, WhatsApp and project-management comments all work as a channel for a recap, but email has two practical advantages worth keeping in mind. First, it is searchable on your own terms years later, even after a Slack workspace is archived or a WhatsApp thread is deleted by either side. Second, it reads as slightly more formal, which quietly signals to the client that this message is meant as a record, not a casual chat reply. If your main working channel is Slack or a client portal, it is still worth cross-posting the recap to email for anything that affects money, scope or the final deliverable — quick day-to-day back-and-forth can stay wherever is convenient.
What if the client disagrees with your recap?
This is actually the useful outcome, not a failure of the process. If a client replies "actually, I meant X, not Y," you have just avoided weeks of building on the wrong assumption — and you have it in writing before any work was wasted on the misunderstanding. Treat a correction to a recap exactly the way you'd treat a scope clarification: thank them for catching it, note the correct version, and send a fresh short recap confirming the update.
Make the written record the norm, not the exception
Once you build the habit of recapping every verbal approval, the paper trail stops depending on memory — yours or the client's. The Client Approval Log + 50 Client Messages pack gives you an Excel log to record exactly this (date, deliverable, approver, approval date, evidence link) alongside 50 ready-to-paste messages for approvals, revisions, scope creep and payment, including the recap templates above.
Client Approval Log + 50 Client Messages
Keep a written record of every approval, and ask for it politely. $5.
Get it on Gumroad