What They Meant Was: Decoding Client Feedback Before the Rewrite Begins

The 4:47pm email

It arrives just before the end of the day, three comments long. The client would like the copy to be ‘warmer’, the science ‘simplified’ and the whole thing ‘just tightened’. There is no indication of which paragraph, which audience or which constraint prompted any of it.

In UK medical communications, this is not an unusual event. It is the ordinary friction of a client responding to a draft as a reader rather than as the author of a brief. The cost, however, is real: writer hours absorbed into speculative rewrites, account time spent chasing meaning, version numbers climbing, and a medical and regulatory review slot that may be lost if the pack is not stable.

The answer is not to complain about vagueness. It is to build a translation layer between the comment and the redraft.

Vague is not the same as careless

Clients are usually clinicians, brand leads or compliance partners. They read for accuracy, tone and risk, and they compress their reactions because they assume a shared context that the agency does not necessarily hold. A comment such as ‘less promotional’ may encode a specific concern about a claim that sits close to the edge of the ABPI Code. ‘Simpler’ may mean the client has already imagined showing the material to a busy specialist who will give it ninety seconds.

There is also an organisational dimension. Feedback often travels from a global team through an affiliate, or from a medical reviewer via a brand manager, and arrives stripped of its original reasoning. Treating the comment as a puzzle to be solved, rather than an error to be corrected, sets the right tone for the conversation.

Sort before you solve: a three-bucket triage

Before replying, place each comment into one of three buckets. The bucket determines the response.

1. Direction. The client wants a change of emphasis, register or structure. Direction requires a proposed interpretation and a quick confirmation, not a debate.
2. Constraint. Something cannot change because of an approved claim, data on file, a Code requirement or a global template. Constraints require documentation and a named source, and they should be separated from matters of taste.
3. Preference. Aesthetic or habitual choices — house style, a favourite adjective, a dislike of subheadings. Preferences deserve a fast option and a note in the project file, not a lengthy justification.

Some comments straddle two buckets. ‘Make it less promotional’ may be a preference about tone or a constraint about a claim. When that happens, ask which one dominates before rewriting a single line. The distinction matters because constraints need evidence, while direction and preference need a decision.

Decoding the familiar phrases

A short working glossary can help, provided it is treated as a starting hypothesis rather than a fixed dictionary.

• ‘Make it warmer.’ Usually a comment about register and reader proximity. Consider second person, shorter sentences, an opening that acknowledges the reader’s situation before the data, and fewer passive constructions. Ask whether the warmth is intended for the patient, the prescriber or the internal team, and which section currently feels cold.
• ‘Simplify the science.’ Rarely a request to remove accuracy. Often a request to reduce density. Ask which single mechanism or endpoint must survive, and offer a one-message summary with supporting detail moved into a short box.
• ‘Just tighten it.’ Ask for a target: a word count, a percentage reduction or a page limit. Distinguish trimming repetition from removing content, because the two produce very different documents.
• ‘More impactful.’ Ask what the reader should think, feel or do differently after reading. Impact is an outcome, not a typographic treatment.
• ‘Can we make it less promotional?’ Treat this as a compliance signal first. Route it to the medical or regulatory lead and record the specific passage that prompted it.

Used carefully, this decoding reduces the number of cycles. Used lazily, it becomes a set of assumptions imposed on every client. Therapy area, organisation and individual reviewer all change the meaning.

Ask better questions, not more of them

A long list of questions signals indecision. Three well-formed ones signal competence. The principles are simple: ask few questions, make them closed where possible, and always include your proposed reading so that silence can function as consent.

A workable reply might read:

Thank you for these comments. Before we restart, here is my reading of the three main points. First, on ‘warmer’, I will rewrite the opening for the patient reader in the second person and move the efficacy data to the second paragraph. If you meant warmer for the prescriber, tell me and I will adjust. Second, on ‘simpler’, I propose keeping the primary endpoint in the main text and moving the mechanism into a short ‘How it works’ box; the claim wording stays as approved. Third, on ‘tighten’, I will cut from 620 to 450 words by removing repetition rather than content. If you need 350, I can remove the box entirely. If this is right, no reply is needed and we will restart tomorrow morning.

That message does four things: it demonstrates listening, exposes the interpretation to challenge, protects approved wording and sets a deadline for objection.

The feedback translation note

For internal handover between account and editorial teams, a one-page note prevents the comment from mutating as it travels. It should contain:

• the comment as received, verbatim;
• the working interpretation agreed by the team;
• the proposed change, with section and line references;
• the source of any constraint, such as an approved claim or data on file;
• what will not change, and why;
• the decision owner and the date by which a decision is needed;
• the version number and cycle count.

The same note can be sent to the client as a short summary. It creates an audit trail that is useful during medical and regulatory review, and it reduces the risk of a comment being reinterpreted by a third party who was not on the call.

Make the loop shorter next time

Translation is easier when expectations are set at kick-off. Agree a single point of consolidated feedback, a defined approver, a realistic review window and the format in which comments will be returned. Keep a living glossary per client, recording phrases and the meanings the team has agreed for them. After each project, review how many cycles were required and which comments caused the most churn; that evidence is more persuasive than a general request for clearer feedback.

Translation is a service, not a delay

Asking what a client meant is not pedantry. It is a professional courtesy to the writer, the reviewer and the client’s own timetable. A brief pause to translate a comment into an actionable instruction is almost always shorter than a week of rewriting in the wrong direction. The skill lies in making that pause feel like momentum.