Waiting Well: A Disciplined Approach to Client Silence in UK Medical Communications

Every account team knows the shape of it. The deck went across on Tuesday, the covering note was concise and warm, and the client said they would come back shortly. It is now day nine. The status column reads amber, somebody asks in stand-up whether there is any news, and nobody has an answer that helps.

Silence of this kind is not an anomaly in medical communications; it is a structural feature of the work. A submission typically sits with a medical team balancing clinic lists, with regulatory colleagues working to the ABPI Code, with procurement, or with a global function in another time zone. The delay is usually a function of someone else's queue rather than a verdict on the draft. But that does not make the intervening weeks free. Handled carelessly, they compress the back end of a project into a fortnight of avoidable pressure. Handled deliberately, they are the reason final approval eventually lands without drama.

Productive waiting is not the same as looking busy

The instinct when a project goes quiet is to fill the space. A tracker gets recoloured, a status deck acquires an extra slide, an internal meeting is convened to discuss the absence of a meeting. None of this moves the work forward, and most of it creates a second problem: a team that has convinced itself it is behind when in fact it is simply waiting.

The test is straightforward. Ask of any task: if the client's comments arrived tomorrow morning, would this work have made the response faster, better or cheaper? Restructuring the slide library so that amendments can be applied in an hour passes the test. Rewriting a section that nobody has asked about does not. Preparing the response grid, the version-control log and the amended timeline in advance passes; speculative re-editing of copy that may be signed off untouched does not.

There is also a commercial dimension. Time booked against a stalled project is time not spent on a live one, and UK account leads are increasingly answerable for utilisation as well as delivery. Waiting well means holding resource lightly — enough to respond quickly, not so much that the project quietly absorbs a week of unbilled effort.

The first 48 hours: confirm, capture, close the loop

The period immediately after submission is where most quiet weeks are won or lost, because it is the only window in which expectations can be set without sounding impatient.

• Confirm receipt and restate the ask. A short note that lists the specific decisions you need, the date you have in the plan for them, and the person who will act on each one. This is not a chase; it is a service.
• Record the assumptions. Write down what the team has assumed in the absence of guidance — tone, level of clinical detail, whether a particular claim is pending new data — and share that record internally. When comments do arrive, the assumptions become the agenda rather than a surprise.
• Agree the internal holding position. Which tasks continue, which pause, which are contingent. Make sure the person who owns the budget knows the project is in a wait state.
• Diarise the follow-up before you need it. A single agreed checkpoint on day five is calmer than three improvised emails.

Week one: keep the file approval-ready

The most valuable thing an account team can do during a silent week is to ensure that the moment comments land, the project can move within hours rather than days. That means the document is genuinely ready to be amended: version control is clean, source references are assembled, the medical writer who knows the file is available, and the review platform is set up with the right permissions.

It also means thinking about certification. If the eventual approval will require a final sign-off step, check now that the named approvers are in the diary for the week after the expected feedback, and that any supporting material they will want — references, data on file, a summary of changes — is already drafted. Chasing a certifier's availability in the same week as the amendments is how three-day turnarounds become ten.

Where the silence extends beyond a week, a brief written update to the client contact is appropriate and should be framed around their decisions, not your anxiety. Something along the lines of: the team is holding the file at the current version, the timeline has contingency until a stated date, and here is what we will need in order to protect the delivery date. It reads as stewardship rather than pressure.

Week two: escalate with grace

The second week is where professional judgement matters most. Escalation is not the same as complaint, and a well-judged route upward protects the relationship rather than straining it. Before going further, establish whether the delay is local or structural: has the named reviewer changed role, is the organisation in a data cut-off, has a governance step been added? A single question to the day-to-day contact, framed as a check on process rather than a demand for output, usually surfaces the real cause.

If the delay now threatens a deliverable, say so early and in writing, with options rather than ultimatums. A short note offering two or three routes — hold the date and compress review, move the date with a revised plan, or split delivery into stages — gives the client a decision to make rather than a problem to absorb. Account teams that present choices in week two tend to find that week three is considerably quieter.

Protecting the plan without alarmism

Three practical habits make the difference over a full programme of work. First, build an explicit feedback window into every timeline at the outset and name it in the project plan, so that a two-week wait is a planned period rather than a deviation. Second, track the elapsed time in a visible place — a simple column recording date submitted and date returned — so patterns become apparent across clients and can inform future estimates. Third, share the pattern in peer conversation, whether at a MedComms Networking UK event or in a smaller regional group; teams that compare notes on how long particular review routes actually take estimate far more accurately than those working from optimism.

None of this requires new systems. It requires a shared understanding that waiting is a phase of the work with its own tasks, its own risks and its own professional standard.

A short checklist for the quiet weeks

First 48 hours — confirm receipt and restate the specific asks; record assumptions; agree the internal holding position with the budget owner; diarise a day-five checkpoint.

Week one — confirm the file is amendment-ready; check version control and source references; verify approver availability for the week after expected feedback; send a brief, decisions-focused update if the silence persists.

Week two — establish whether the delay is local or structural; put options in writing if a date is at risk; adjust resource and budget forecasts; log the elapsed time for future estimating.

A quiet fortnight is not a failure of the account team, and it should not be treated as one. It is a period in which the quality of preparation becomes visible — usually at the moment the comments finally appear in the inbox, and the team either moves in an afternoon or spends three days finding its bearings.