How to take client call notes that protect you
Every freelancer eventually sits in the call where the client says, warmly and with total confidence, that they definitely approved the extra page — while you remember, with equal confidence, a call where no page was mentioned. Three weeks is all that takes. Memory does not store conversations; it stores the version that suits the person remembering, and it stores theirs the same way. The freelancer who wrote it down does not win because they are more suspicious. They win because they never have to have the argument at all: the note exists, it was sent the same day, and nobody corrected it. That is why call notes are not admin. They are the cheapest insurance in the practice — five fields, ten minutes, and a short confirmation email that turns your private note into a shared record both sides are working from.
1. What a protective note holds
A protective note is short enough to write during the call and exact enough to settle a question months later. It holds five fields, always in the same order, so a note from January reads exactly like a note from October:
Date, and who was on the call. Not just the day — the people. A decision made with the owner in the room is a different object from the same words spoken by an assistant who had to check, and in three weeks nobody will remember which call had whom on it unless the note says.
Decisions. The verbs matter: approved, agreed, chose, dropped. Each decision gets exactly what was decided, in as few words as the truth allows. “Approved the extra page for the services section” protects you. “Discussed pages” protects nobody — discussed is the word disagreements are made of.
Numbers said out loud. Prices, dates and counts, written with their units attached: $2,400, not “the fee”; 12 December, not “mid-December”; three rounds of revisions, not “a few”. A number without its unit is a rumour. A number read back on the call and written with its unit is a fact.
Actions. Who does what, by when — yours and theirs, in the same list. Half of all stalled projects stall on an action the client owed you: the text, the access, the approval. If their actions live only in their memory, your deadline quietly depends on something nobody else is tracking.
Open questions. What was not decided — the field everyone skips and later wishes existed. An open question written down is a parked item with an owner. An open question left unwritten becomes, in the retelling, a decision somebody is sure was made.
One discipline governs all five fields: the note is a record, not a diary. Feelings, readings of tone and private interpretations — “seemed keen”, “probably cannot afford more” — live in a separate line, clearly marked as yours, or nowhere. Apply the read-aloud test to every line: if this note were read out, word for word, in the middle of a disagreement, would each line still help you? A record passes that test. A diary does not, and diaries have a way of being forwarded.
2. During the call: write it in their words
For decisions, write the client’s words, not your translation of them. A paraphrase feels harmless in the moment and becomes the argument later: you wrote “refresh the homepage”, they said “tidy the homepage”, and the distance between those two phrases is a week of work. Their exact words are the cheapest precision available — you were sitting there when they said them. The same habit runs the discovery call script: the budget range and the problem, taken down in the words the client used, because those words are what the quote will be judged against.
Then read the numbers back before the call ends. “So that is delivery on the 12th, at $2,400, with the deposit invoice this week — yes?” Thirty seconds, slightly awkward the first time, and an entire category of later dispute simply never happens. A number the client has said yes to twice — once in conversation, once read back — is as close to undisputable as spoken business gets. If they correct it, better still: the correction happens while the truth is still in the room.
Paper or a typed document makes no difference, and the tool is beneath the point — the same lesson the guide to managing multiple clients draws about dashboards: the medium fails far less often than the habit does. What matters is that the note is written during, in the five fields, every call. One thing does matter about form: mark your guesses as guesses, inside the note itself — a [check] tag beside anything you inferred rather than heard. A note that cannot tell its facts from its guesses protects neither, because the first time a guess is caught masquerading as a fact, the whole document loses its authority.
3. The confirmation email: the same day, in three blocks
A note in your drawer is evidence. A note in the client’s inbox is a shared record — and the difference is one short email, sent the same day, while agreement is still warm. Keep it deliberately plain. The subject line carries the project and the date, so the message can be found in a search months later. The body carries three short blocks, and nothing else: what we decided; what happens next, with dates — your actions and theirs; and what you still need from them, which is the open-questions field wearing its working clothes.
The closing line does the quiet work: “Reply if I have any of this wrong — otherwise I will work to this.” Sent on an ordinary project, to a client in an ordinary relationship, it gives them a fair chance to correct the record and gives you a record nobody corrected. Be honest with yourself about its weight, though: it is good practice, not magic. How much an uncorrected email settles depends on the relationship and on whatever agreement the two of you already have in place — which is why it supports the terms in your freelance contract rather than replacing them. Here is the whole thing, for a fictional rebrand project — 92 words:
Notice what the example does not contain: no summary of the discussion, no reasoning, no warmth beyond the greeting and the thanks. Discussion is what calls are for. The confirmation exists to fix the decisions, the numbers and the next actions in writing, at the moment when fixing them costs a reply instead of a dispute.
4. Filing them: one home per client
A note you cannot find in ten seconds is, for practical purposes, a note you never took. Give every client one home — a single folder or document where their call notes live in date order — inside the same records system that holds the rest of the project: the discipline our guide to documenting your processes sets out for a team of one, and the same folder habit the tax-season guide applies to money records. Notes filed by client, not by month or by app, because every future question about a call arrives wearing a client’s name.
Filed properly, a note has a second life far beyond the call. The brief quotes it: the project brief is, half the time, three call notes with the decisions promoted into scope. A scope disagreement cites it — the note is usually the fastest way to price what a change actually is, which is the whole job of the scope creep calculator. And at the end, the handover document inherits the set: the questions appended to it over the project are your notes, tidied. Keep them for as long as the relationship and its records live. Storage costs nothing; a missing note, on the one occasion it is needed, costs exactly the thing it would have settled.
5. The ways notes fail
Written from memory, three days later. This is the commonest failure and the most understandable: the call ran long, the day moved on, the note happens on Thursday. But memory edits toward the teller — not dishonestly, just humanly — and a note written from Thursday’s memory is a story, not a record. The same-day rule is not fussiness. It is the whole game.
The transcript kept instead of a note. If you record calls, do it openly: in many places, recording needs the other side’s knowledge or consent, so ask — ten seconds, at the start — and keep the written note and the confirmation email as your protection regardless of what any recording captured. The trap is treating the transcript itself as the record. Nine thousand words that nobody will ever read settle nothing; when a question comes, you will still have to find the sentence, interpret it and argue about it. The transcript is evidence storage. The five-field note is the record.
Notes only for the big calls. Small calls make small promises — a date nudged, a file added, a favour agreed — and small promises are precisely the ones that slip, because neither side thought them worth writing down. The five fields scale down happily: a three-line note for a ten-minute call costs two minutes and closes the same hole.
The confirmation never sent, because you get on well. The friendliest clients are exactly the ones whose misunderstandings hurt most, because neither side guarded against them. Sending the email is not a sign of distrust; after the second project it is simply what working with you feels like — and the clients who value being organised will read it as the professionalism it is.
Questions
Related: the record the rest of the project stands on
The call becomes a brief, the brief becomes the work, and the work ends in a handover — with the notes underneath all of it, dated and uncorrected. Keep them in the one home, send the confirmation the same day, and the next time a call is remembered two ways, there will be a third version: the written one, which both of you already have. Between calls, the same record runs the other way: the client status update sends the done lines, the waiting-on items and the dates out to the client on a weekly rhythm — the notes, outbound, before anyone has to ask.