Nothing is approved until it exists in writing, even after a clear verbal yes on a call. A design project sign off from client needs to be requested the same day the approval was given, before either person's memory of the conversation starts to drift. "Looks great, let's go" on a call is a genuine, good-faith reaction, and it is not sign-off. It becomes sign-off once it exists as a written confirmation both people can point back to later. This is not a legal standard; it is a practical one, and it is the cheapest insurance available in a solo design practice.
Why "Looks Great" on a Call Isn't Sign-Off
A verbal approval is real in the moment it's said. The problem is not sincerity, it's durability. A phone or video call leaves no record either person can check later, which means both sides are relying on their own memory of a conversation that, from the client's side, was probably one of several things discussed that day.
This becomes visible weeks later, not at the time. The client who said "looks great" genuinely meant it, and by the time a printer proof or a launch date arrives, their memory of exactly what they approved has quietly narrowed or shifted, without any bad faith involved. What they recall approving and what was actually shown on the call are not always the same thing, and there is no record to settle the difference.
Treating a verbal yes as provisional rather than final is not a sign of distrust. It is simply acknowledging what a conversation is and isn't: a real moment of agreement, and not a document either person can refer back to.
Turning a Call Approval Into a Written One, Same Day
The lightest version of this is a same-day recap message, sent the same afternoon as the call, while the context is still fresh for both people. It does not need dedicated approval software or a formal signature process for a solo practice working with one client contact at a time.
A template: "Great call today. Confirming what we agreed: the homepage direction shown is approved as presented, moving into production. Just reply 'confirmed' or let me know if anything needs a second look before I start."
Same-day matters more than the wording. Sent an hour after the call, this message reads as a normal part of the process. Sent three days later, it can read as the designer trying to lock something in after the fact, even though the intent is identical. Speed is what keeps this feeling like a courtesy rather than a maneuver.
What the Written Note Actually Needs to Say
A solo designer's sign-off note does not need to read like a legal document, and turning it into one usually backfires, since a client is less likely to reply promptly to something that looks like paperwork. It needs four things stated plainly: what was shown, what was approved, what happens next, and a simple way to confirm.
What was shown should be specific enough that there's no ambiguity later, "the homepage layout in the two-tone palette," not just "the design." What was approved should match that specificity, since approving "the direction" is different from approving "the direction, pending the two small edits mentioned on the call." What happens next tells the client what their yes sets in motion, so the approval is understood as a decision with consequences, not just a compliment. And the confirmation ask should be a one-line reply, not a form, because a low-friction ask gets answered faster.
What to Do When They've Changed Their Mind First
Sometimes the written confirmation goes out and the reply that comes back is not "confirmed," it's a new note or a change of direction. This is not a failure of the process; it is exactly why the process exists. Better to learn this before production starts than after.
Respond to the substance rather than to the fact that it contradicts the call: "Thanks for flagging that, glad we caught it before moving forward. Can you say more about what's changed since the call, so I make sure the next version actually addresses it?" Treating the reversal as new information rather than a broken promise keeps the relationship intact and gets a more useful answer.
If this happens repeatedly on the same project, it is often a sign the call itself was not doing enough work, that decisions were being made too quickly in the room to actually stick. Slowing the presentation down so a client has time to react honestly, rather than agreeably, in the moment is covered in how to present design work without losing the room.
What This Protects You From, and What It Doesn't
This article is not legal advice, and nothing here should be read as a legal conclusion about what a written message does or does not establish in any particular dispute. What follows is a description of the practical mechanism, not a claim about the law.
A same-day written confirmation is a record you can point back to later: what was shown, what was said to be approved, and when. That record is useful in exactly the way any dated communication is useful, it settles an honest disagreement about what happened, and it makes a dishonest one much harder to sustain. What it does not do is replace an actual contract. It says nothing on its own about payment terms, ownership of the files, liability, or what happens if a client wants to walk away entirely. Those are contract questions, and a sign-off message was never designed to answer them.
When to Route This to an Actual Contract Instead
A same-day recap is the right tool for confirming that a specific deliverable was approved on a specific day. It is the wrong tool for anything involving money owed, rights transfer, liability, or a dispute that has already become adversarial. Those situations call for an actual contract clause or, once a disagreement is real, a conversation with a lawyer rather than a designer's own reading of what a written message might mean.
If a client relationship reaches the point where enforceability genuinely matters, that is the moment to stop relying on this article's advice and get a professional opinion specific to the jurisdiction and the actual agreement in place. Building solid intake habits reduces how often that point is reached; it does not replace legal counsel when it is. Where that written record starts, back at the beginning of the relationship, is set out in what to include in a design brief, and the same discipline, agree it, then get it in writing before moving forward, is what protects a designer at every stage covered in the solo design project process. It applies just as much to a priced scope addition as it does to a final approval, which is why the same habit shows up in how to say no to an out-of-scope request.
FAQ
What counts as client sign-off on a design project?
A written confirmation of what was approved, sent the same day as the conversation where it was discussed. A verbal "looks great" on a call is a real reaction but not a durable record, and it should be followed by a same-day written recap the client confirms in reply.
How do you get written approval without formal signature software?
A short same-day recap message works for most solo design practices: state what was shown, what was approved, what happens next, and ask for a one-line confirmation reply. No dedicated software is required for a single client contact approving a single deliverable.
What if a client changes their mind after giving verbal approval?
Treat it as new information rather than a broken agreement. Ask what's changed and respond to the substance. This is exactly the situation a same-day written recap is meant to catch, before production time has been spent on the wrong direction.
Is a written sign-off message legally binding?
This is not legal advice, and that question depends on the jurisdiction and the specifics of the relationship. A written recap is a practical record of what was discussed and approved on a given day. For anything involving money, rights, or an actual dispute, talk to a lawyer rather than relying on a sign-off message alone.
Does written sign-off replace the need for a contract?
No. A sign-off note confirms that a specific deliverable was approved on a specific day. It does not cover payment terms, file ownership, or liability, which belong in an actual contract agreed before the project starts.