Think about the last client relationship that went wrong. Not badly wrong, just cooler than it should have been.
There's a good chance the work was fine. What happened was that at some point they expected something they didn't get, and nobody had said anything about it in advance.
Almost every unhappy client is a surprised client. Which is convenient, because surprise is preventable with sentences.
The six moments
Six points in a project where a single line, said before it's needed, prevents a problem.
1 · At quote: what's in, and what isn't
The quote is the first expectation you set, and an itemised one does more than justify a price. It defines the edges.
Say what's not included, explicitly:
"This covers one round of revisions after the first cut, and one 60-second master plus a 15-second cut-down. Additional versions or a second revision round are quoted separately."
That reads as professional, not defensive. Vagueness at quote stage is where scope creep is born (not later, when it shows up).
2 · At booking: the shape of the project
Once the date is agreed, send the timeline. Brief lock, shoot, rough cut, review one, review two, picture lock, delivery.
Two things this does. It tells them when they have work to do: most projects slip on the client's side, and clients rarely realise their approvals are on the critical path. And it makes the round count real, because they can see there are two.
3 · Before the shoot: what you need from them
Access, product, people, permissions, brand assets. With a deadline on each.
Send this as a short list, not buried in a paragraph. The failure mode is a shoot day where the product hasn't arrived, and the entire cost of that lands on you regardless of whose fault it was.
4 · At the rough cut: say what it is
The highest-value sentence in this entire article:
"This is a rough cut: no colour grade, temp music, placeholder graphics. I'm looking for notes on structure and length. Everything else comes next."
Without it, a client who has never seen a rough cut sees an unfinished, ugly video and quietly panics. You then spend a round reassuring them instead of using their notes.
With it, they know what to look at. It costs one sentence and it changes the entire tenor of the first review.
Pair it with what good notes look like: timecodes, consolidated, against the brief. Most clients have never been told, and most want to do it well.
5 · At each handover: what happens next, and by when
Never deliver anything without saying what happens after it.
"Notes by Thursday and I'll have v2 to you Monday. If notes land later than Thursday, delivery moves accordingly."
That last clause is doing quiet, important work. It attaches a consequence to their delay before the delay, so a slipped delivery is a shared fact rather than your failure.
6 · At delivery: what they're getting and what they can do with it
Files, formats, where they live, how long they'll be there. And the usage rights restated in plain words, because the person receiving the files is often not the person who signed the agreement.
The two sentences that prevent the most damage
"That's a change rather than a note. Here's what it would cost."
Said warmly, early, the first time it happens. Not as a challenge. As information. Most clients don't know where the line is, and once told they respect it. Absorb three "small" changes silently and you've taught them the line doesn't exist, and the fourth conversation will be much worse.
"I'll come back to you on that by Thursday."
Instead of an immediate yes to something you haven't thought about. Freelancers say yes reflexively under pressure and then discover the cost afterwards. A deadline for your own answer is a complete, professional response.
When something goes wrong
It will. The differentiator isn't whether things slip. It's the gap between you knowing and them knowing.
Tell them early. A problem flagged on Tuesday is a schedule adjustment. The same problem discovered by them on Friday is a trust event.
Lead with the fix. "The colourist is ill, so delivery moves to Wednesday. I've confirmed the new slot" is a completely different message from "we have a problem".
Don't over-apologise. One clear apology, then the plan. Repeated apology reads as instability and invites them to worry more.
Silence is a message, and it's the wrong one
The single most common complaint about freelancers isn't quality or price. It's not hearing anything.
A client who hasn't heard from you in two weeks assumes the worst. Not because they're unreasonable, but because nothing else is available to assume. Even "still on track, nothing needed from you, next update Friday" resets the clock entirely.
Two minutes. Enormous return.
Where Acumin fits
A Delivery Room gives a project one place where the versions, the notes and the invoice live. That removes the commonest source of confusion, that a client is looking at v2 and talking about v3. Notes anchor to timecodes, so "the bit near the end" stops being a category of feedback.
Version history also settles what round you're on, which is the fact most likely to be disputed at the point it costs money.
None of that replaces the six sentences. A tool can hold the record; only you can set an expectation.
How to use this tomorrow
Take your current project and send the client one message: what happens next, what you need from them, and by when.
If you can't write it in three lines, you don't have a plan. Finding that out today is worth the two minutes.
Related: Delivering files is the last of the six moments, in detail. When a client goes quiet is what to do when the messages stop coming back.