Your client documents are staff. Are they doing their jobs?

Most designers produce their client-facing documents the same way: under pressure, between other things, when the project demands it. The onboarding pack gets written the night before the kick-off meeting. The fee proposal is assembled from last time's version with the numbers changed. The snagging update goes out because something needs to go out. The documents exist. The project moves forward. Nobody pauses to ask whether the documents are actually working.

That is the wrong question anyway. The right question is: what is each document for?

I have spent the past several months doing something that sounds straightforward but turns out to be surprisingly revealing: mapping every client-facing document in a design practice against what it is genuinely trying to do. Not what it contains, not what it looks like, not how long it is - but what job it is being sent out to perform.

The exercise emerged from work I am doing on a new product launching later this summer: building the full suite of client communication architecture from the ground up. What I did not anticipate was how clearly the mapping would expose the gap between what most practices think their documents are doing and what those documents are actually capable of doing if they are built with intent.

I now think of each client-facing document as a member of staff. It goes out into the world on the practice's behalf. It has a meeting with the client that the designer is not present for. And it either performs well in that meeting, or it does not.

The document cannot be coached in the moment. It cannot read the room. It can only do what it was built to do, which means the decision about what to build it to do has to come first.

Most of the time, it does not come first. It does not come at all.

The four jobs

When you interrogate what client communication is actually trying to accomplish, the answer will always fall into one of four categories.

Persuade. The document is acting on desire and decision. It is moving the client towards a commercial commitment - to enquire, to appoint, to approve, to proceed. This is the selling function, and it is more widely distributed across the client journey than most designers realise. The fee proposal is obviously persuasion. The concept presentation is obviously persuasion. But so, more quietly, is the beautifully produced 'How We Work' document that lands in a prospective client's inbox before they have agreed to anything. Every element of that document (its clarity, its confidence, its design) is making an argument.

Inform. The document is acting on knowledge. It is changing what the client understands about the process, the project, or their own role within it. The distinction between informing and persuading matters more than it might appear, because a document built primarily to inform requires a completely different tone from one built primarily to persuade. Generous, authoritative, and without agenda - that is the register of genuine information-giving. The moment it starts to feel like a pitch, it loses its credibility.

Anchor. The document is acting on the record. It is fixing what has been agreed, decided, or consented to - creating a stable foundation that protects both the project and the practice. Most designers understand anchoring in its legal dimension: the signed contract, the approved brief. What they underestimate is its psychological function. An anchor document does not just protect the practice; it protects the client from their own future indecision or second-guessing. A well-constructed sign-off gives both parties something solid to stand on when the project gets difficult, and projects always get difficult.

Manage. The document is acting on behaviour or emotion. This is the broadest category and, I would argue, the most underserved. Managing a client well across a long and disruptive project requires a specific set of interventions: around their expectations, their emotional response to change, their decision-making, and the underlying trust that makes all the other interventions possible. Each of these is a distinct mode of management, and a document that fails to recognise this will do none of them properly.

The problem with doing several things at once

Every client-facing document serves more than one of these functions. That is not a problem, it is, in fact, the mark of a sophisticated practice, where every communication is earning its keep at multiple levels simultaneously.

The problem arises when a practice has not decided which function is primary.

Take the onboarding pack: the document that a client receives immediately after signing. In most practices, this exists in some form (a welcome letter, some process information, perhaps a checklist of what happens next). The instinct is to load it with information, because there is a lot the client needs to know. So it becomes an information document, dense with process and practicalities.

But the client who has just signed has not primarily signed up for information. They have made a significant financial and personal commitment, almost certainly accompanied by a mixture of excitement and anxiety. What they need, at this particular moment, is to feel that they have arrived somewhere excellent: that the practice they have chosen is as good as it appeared to be, that the project is in capable hands, and that they made the right decision. The primary job of the onboarding pack is relationship management. It is a welcome, not a manual.

That does not mean it cannot also inform. It should. But if the informing function is allowed to govern - if the document reads like a process document rather than a considered welcome - it fails at its primary job, and no amount of useful information compensates for that.

Now consider the fee proposal. Here the primary function is anchoring: fixing the scope, the fee, the terms, and the procurement model in a form that both parties can rely on. But the fee proposal is also doing something more immediate - it is still persuading. The client has not yet committed. How the proposal looks and feels is itself an argument for the practice's rigour and professionalism. A beautifully produced, clearly structured proposal signals that the project will be run with equivalent care. That secondary persuasion function matters - in contributes to conversion - but it must not be allowed to soften or obscure the anchoring function. Clarity and completeness are not negotiable in a document whose primary job is to fix what has been agreed. The persuasion is in the quality of the presentation; the anchoring is in the precision of the content. Both must be present. Neither can be sacrificed for the other.

These are two documents that arrive within weeks of each other, often treated with similar levels of care (or similar levels of haste), but which are doing fundamentally different primary jobs. Designing them as if they were the same kind of thing (because they are both documents, because they both go to the same client, because they are both produced under time pressure) would be a mistake.

What changes when you know the job first

When the primary intent - the distinct purpose of each intervention - is established before the document is built, every subsequent decision becomes easier and more coherent.

The length question answers itself: a document whose primary job is to anchor needs to be complete, regardless of length; a document whose primary job is to manage the client's emotional state at a particular moment needs to be concise, because length itself creates anxiety.

The tone question answers itself: a document whose primary job is to persuade must have conviction; a document whose primary job is to inform must be generous and without agenda; a document whose primary job is to manage behaviour or emotion must be calibrated to the specific thing it is managing - which is not always warmth, and is never bureaucracy.

The timing question answers itself: a document that anchors must arrive before the moment it is meant to fix; a document that manages expectations must arrive before the moment those expectations are tested.

And the design question answers itself: a document is not just its words. Its format, its length, its structure, and its visual quality are all communicating something about the practice before a single sentence is read.

None of this is complicated in principle. It requires only one thing that most designers do not give their document suite: deliberate prior thought.

Nine documents. Nine jobs. One suite.

Across a full design project, from first enquiry to post-completion review, I have identified nine client-facing packs that between them do the heavy lifting of the practice's client communication. Think of them as nine members of staff, each with a specific assignment...and each with the personality best suited to that particular task. 

When those nine documents are built as a suite - with understood primary intents, calibrated tone registers, and deliberate sequencing - they do something no individual document could do alone: they create a consistent, professionally-managed client experience that earns trust progressively, prevents the most common and costly client problems before they arise, and positions the practice as exactly the kind of operation serious clients want to work with.

When they are built on the hoof, one at a time, in response to whatever the project currently demands, they are nine missed opportunities.

I call method of intentional construction The Intent Framework™ - it is the architecture that sits behind the client communication system inside my soon to launch programme: White Label Studio.

White Label Studio organises itself around the workflow of a typical interior design studio, identifying and supplying beautiful client-facing templates structured as directed by The Intent Framework, as well as all the workhorse documents, files and systems your practice needs to run a client project. The larger part of the studio workflow 'iceberg' that sits beneath client view. 

If this way of thinking about your documents resonates - and particularly if you recognise your own practice in the description of how most documents get made - it is worth considering whether your suite is working as hard as it should be.

White Label Studio is my programme for interior designers who want to run a properly structured, commercially serious practice. It will pre-launch in June, sign up to find out more here.