The Thing That Protects Studio Work Is Not the Contract. It Is the Correspondence.

Studios obsess over contracts and then handle the actual studio work through voice notes, direct messages and a shared chat where decisions evaporate. Six months later, a client claims the scope always included the packaging, or that approval was never given, or that the mark was theirs to register however they liked. The contract is fine. The contract just has nothing to say about Tuesday, because nobody wrote down what happened on Tuesday.

Here is the practitioner position after enough disputes to learn it. The correspondence is the protective layer. Not as defensive theatre, but because a project is a sequence of decisions, and a decision nobody recorded did not happen. Written communication, done lightly and consistently, is cheaper than an hour of a solicitor and one lost relationship.

Confirm Scope After the Call in the Same Hour

Every good call generates decisions, and also a version of those decisions that differs slightly in each participant’s memory. The remedy is a two paragraph note sent before you leave the room. Those notes include what we agreed, what we did not, what happens next, and who owes what by when. Four sentences, no ceremony. “Confirming what we landed on: logo route B approved, tone of voice deferred to phase two, you send the product specs Friday, we deliver concepts Wednesday the 19th.”

Get Approvals in Words That Mean Something

“Love it” is not an approval. Approval needs a verb that survives: approved for production, approved as final, happy to proceed on this basis. Ask for it plainly, and put the request in the delivery message so the reply lands attached to the artefact being approved rather than floating in a separate thread.

Designers hesitate here because it feels like distrust. It is not. It is the mechanism that lets you decline changes later without being the difficult one, because you are holding a line the client drew themselves. Ambiguity in approval is a debt, and it is always collected at the worst possible point in the schedule.

State Usage Rights at Delivery, Not at Dispute

Licensing language buried in a contract clause nobody rereads is not a licence, it is a hope. At handover, in the actual message with the file links, restate the terms in plain language: what the client may do with these assets, what they may not, what remains yours, where the source files sit, what happens if the balance is unpaid. Three bullet points, friendly tone, precise content. Where third party components carry open licences, link the terms published by Creative Commons rather than paraphrasing them.

This is also the moment to say what the deliverables are. “Final logo package: vector master, reversed variant, monochrome, web exports” leaves no room for a later request for everything to be treated as obviously included. Delivery correspondence is a manifest, and manifests prevent arguments.

Raise Trademark Questions Early in Writing

Clients routinely intend to register whatever you just designed, and frequently intend to do it badly. A name phonetically identical to an incumbent in their class, a mark too close to a well known one, a wordmark that describes the service directly. These become your problem the momnt they cost real money on signage and packaging, even when the paperwork says risk transfers to the client.

So raise it once, formally, and let it sit on record. Run a preliminary look yourself, since the WIPO Global Brand Database is free and covers a lot of ground, then say what you found and recommend proper clearance and counsel before filing. You are not giving legal advice and you should say so. You are demonstrating that the studio noticed, which protects the client from a rebrand at launch and protects you from being the person who stayed quiet.

Client Data as a Processing Relationship

Studio work often involves briefs containing unreleased products, customer lists, staff structures, and sometimes personal data. A studio handling that data is a processor, with obligations whether or not anyone framed it that way. The requirements set out in Article 28 of the GDPR shape what you can promise a client and what you must ask of any freelancer you bring in. 

Invoices are Correspondence

An invoice reading “Design services, phase 2” invites a query. One reading “Phase 2: identity system, approved 14 May, per scope confirmed 2 May” answers the query before it is asked. Attach the approval reference, state payment terms without apology, and chase late payment in the same calm register as everything else. Studios lose more margin to awkwardness about money than to client malice. Additionally, the written trail removes the awkwardness, because the numbers stopped being a negotiation the moment scope was confirmed.

The Infrastructure Has To Be Boring and Shared

All of the above collapses if correspondence lives in five people’s personal inboxes and a group chat. Project mail needs to arrive somewhere the studio owns and can still read after someone leaves: role addresses, shared visibility, one thread per project, a naming convention that makes old work retrievable. A professional email setup on your own domain, with shared access and retention you control, is what turns individual good practice into an institutional one.

Clients will change suppliers, merge, and lose the person who commissioned you. Your correspondence is the only complete account of the reasoning. Those are the abandoned routes and why they were abandoned, the constraints that shaped the grid, and the objection raised in month two that explains the mark today. Archive it as an asset rather than exhaust. Protecting the work is not one heroic act at contract stage. It is a hundred small written confirmations, done kindly and promptly. That’s because the studio work intends to be here in ten years with its reputation and its margins intact.

Discover more insights, ideas, and inspiration in our latest blog posts 

Related Post