Correspondence as Craft: Reading the Client Email as a Design Material

There is a moment in a commission when the work stops being a response to a brief and becomes a response to a person. The email arrives, often late in the day, and it contains a sentence that quietly redraws the project. In my own practice, the most consequential design decisions are rarely made in the first presentation. They are made in prose: in the reply, the clarification, the list of concerns, the half-apologetic request for one more change.

I have started treating correspondence as a material with its own properties. It has tone, weight, ambiguity and edge. It can be sanded down or left rough. It can be quoted back, annotated and tested. This is not a claim that emails are more important than drawings. It is a claim that they are part of the same craft. Writing and design are both acts of arrangement: deciding what comes first, what is omitted, what needs a heading and what can remain implied.

What follows are seven annotated excerpts from recent UK commissions, anonymised and lightly edited. They are not presented as exemplary exchanges. They are presented as evidence of where the work actually happens.

Revision one: the constraint that names the audience

Client excerpt: 'We need it to feel less corporate, but the board still has to approve it.'

Annotation: this sentence is not a contradiction. It is a map of two audiences. The work had to feel warm to the public and defensible to a committee. That changed the palette, the type scale and the amount of white space. I moved away from a sharp geometric sans and towards a humanist face with more open counters. The email did not ask for that. It created the conditions in which that decision became necessary.

Practical note: when a client gives you two apparently opposing needs, write them down as a hierarchy. Ask which audience is primary at which moment. The answer is usually a design structure.

Revision two: the deadline as a formal pressure

Client excerpt, from a Manchester studio: 'Could we see something by Thursday, even if it is rough?'

Annotation: a deadline is not only a schedule. It is a formal pressure. The request for something rough gave me permission to send a measured sketch rather than a polished mock-up. That sketch exposed the hierarchy more clearly than a finished layout would have done. The rough version showed where the eye went first. The polished version would have hidden the problem beneath surface.

Practical note: name the fidelity in writing. Say what the next document will and will not resolve. It protects the work and it protects the client from mistaking a sketch for a promise.

Revision three: the sentence that removes a feature

Client excerpt, from a Bristol publisher: 'The map is useful, but it cannot be the first thing people see.'

Annotation: this was a deletion disguised as a preference. The map had been doing too much work. It was carrying atmosphere, information and a certain idea of place. Removing it from the cover forced the typography to take responsibility. The project became quieter and more confident. The client had not asked for a redesign. They had asked for a new order of attention.

Practical note: when feedback removes something, ask what that element was doing. Then ask what will now do that work. Deletion is rarely neutral.

Revision four: the ambiguity that requires a counter-brief

Client excerpt, from a Leeds heritage organisation: 'Make it feel more editorial.'

Annotation: editorial is one of those words that can mean almost anything. It can mean grid-led, magazine-like, authorial, restrained, or simply not corporate. Rather than guess, I wrote a short counter-brief: editorial here would mean a clear reading order, a strong typographic voice and room for captions to carry context. The client replied with amendments. That reply became a shared definition. The design then had something to answer to.

Practical note: do not treat vague adjectives as instructions. Turn them into criteria. A counter-brief is often more useful than another round of visuals.

Revision five: the approval that arrives as a list

Client excerpt, from a London gallery: 'Three small things: the caption size, the grey, and whether the second spread can breathe.'

Annotation: a list is a form. It shows that the client has moved from taste to criteria. The caption size is a functional concern. The grey is a tonal concern. The second spread is a spatial concern. Once they were separated, the response was straightforward. The difficulty had been in the blur, not in the requests.

Practical note: separate function, tone and space in your replies. It makes the conversation less emotional and more architectural.

Revision six: the silence

Client excerpt: no reply for eight days.

Annotation: silence is data. It can mean approval, avoidance, internal disagreement or simply a full inbox. I have learned not to fill silence with guesses. I sent a short summary of the decisions awaiting confirmation and named the next date at which the schedule would need a response. The act of summarising changed the scope. It made the project legible as a set of pending choices rather than a cloud of anxiety.

Practical note: write the summary you would want to receive. Keep it short. Name decisions, owners and dates. Do not use silence as an invitation to overwork.

Revision seven: the final note that changes the next project

Client excerpt: 'This feels like us now.'

Annotation: approval is rarely just approval. This sentence was a positioning statement. It told me what the organisation wanted to become, not only what it wanted the document to look like. It became a reference for the next commission. The final email was not the end of the project. It was a piece of research for the next one.

Practical note: keep a decision log. Quote the client back to themselves when the next brief arrives. Memory is a design tool, and correspondence is its archive.

Writing and design as one practice

In the UK, commissioning often runs through committees, trustees, editors and brand guardians. The email is the room where those voices meet. A designer who cannot write clearly will struggle to defend a subtle decision. A writer who cannot see structure will struggle to explain why a sentence belongs on the left and not the right. The two practices are not adjacent. They are continuous.

For freelancers, the practical lesson is not to become more administrative. It is to become more deliberate about language. Write the constraint down. Name the fidelity. Separate the criterion from the adjective. Summarise the silence. Keep the archive. The client email is not the paperwork around the design. It is one of the materials from which the design is made.