The Close Call Log: Making Near Misses Useful in UK Medical Communications
Photo: Unknown authorUnknown author, Public domain, via Wikimedia Commons
In UK medical communications, the most instructive events are often the ones that do not quite happen. A file reaches the client with minutes to spare. A missing reference is caught at final proof. An approval route is clarified after a chase rather than before it. The immediate reaction is relief, followed by a return to the schedule. Yet a close call is free evidence. It shows where a process was fragile without the cost of a full failure. The question for teams is whether they have a routine for using that evidence.
Why close calls vanish from view
Near misses are easily lost because they sit between success and failure. The project was delivered, so the incident can look like noise. Team members may also be reluctant to raise it. They may fear that reporting a close call will invite scrutiny of their judgement, even when the underlying issue was a confusing approval route, an unrealistic timetable or a version-control gap.
In a busy agency or in-house team, relief is a powerful incentive to move on. The person who caught the problem may mention it informally, but the lesson stays with them. When the same conditions recur, another person may not catch it so quickly. A blameless post-mortem habit exists to interrupt that cycle. It does not remove accountability for conduct or for regulatory duties. It separates the person from the system so that the system can be examined.
Define what is worth reviewing
Not every minor correction needs a meeting. A practical threshold helps. A close call should be logged when it could have led to a late submission, a missing or incorrect reference, an approval taken through the wrong route, a version error in review, an incomplete disclosure detail or a last-minute change that placed pressure on sign-off. The test is not whether harm occurred, but whether the event reveals a condition that could recur with greater impact.
A simple triage works well. Record the close call within 48 hours while the timeline is still clear. Note the potential impact, the likelihood of recurrence and the learning value. If the answer to any of those is high, schedule a short review. If not, keep a light log entry so that patterns can still be seen across a quarter. The log itself should be accessible to the team and owned by a named person, not left in a private inbox.
A one-page format that keeps the focus on conditions
The most useful reviews are short and structured. A one-page record can capture what almost happened, when and where it was caught, what immediate action was taken and which conditions made the event possible. Useful prompts include: where did the process rely on memory? Which system allowed an old version to remain available? Was the approval route clear to everyone? Did the timetable include enough review capacity? Was a handover completed in writing?
The record should also state the proposed process change, the owner and the date by which it will be checked. A final line should ask how the team will know the change has worked. That might be a reduction in version queries, a cleaner review log or a shorter approval chase. The point is to avoid vague actions such as be more careful. Care is not a control. A naming convention, a checklist item, a permission setting or a scheduled review slot is.
Who should be in the room
Keep the group small. Include the person closest to the work, the relevant team lead, a review or quality colleague and, where appropriate, the account handler or medical writer. If the close call involved a compliance or editorial review step, include the reviewer who knows that step. The person who caught the issue should be invited, not to be praised or blamed, but because their account of the sequence is valuable.
Client participation should be considered carefully. Some close calls are best reviewed internally first, especially where the client relationship is sensitive or where the event touches a shared approval system. If a client-facing conversation is needed, it should focus on the process fix rather than on individual performance. For cross-company teams, separate internal and joint reviews can prevent the discussion from becoming guarded.
Running the conversation without a tribunal
Start with the timeline. Ask what happened, in sequence, and where the work was caught. Then ask what made the event possible. This shift in language matters. Who missed the reference invites defensiveness. What allowed the reference to remain unchecked invites observation. The lead should listen for dependencies on memory, unclear ownership, late information, unrealistic deadlines and tools that permit old versions to circulate.
A 30-minute review is usually enough. Record actions in a shared tracker and close the loop at the next team meeting. If the fix cannot be made immediately, say so and set a review date. The worst outcome is a thoughtful discussion that produces no change and no follow-up. The second worst is a change that nobody communicates to the people who do the work.
Share the lesson, protect the people
Anonymised learning is valuable beyond the immediate team. A short case note can describe the close call, the conditions and the fix without naming individuals or clients. It can be used in induction, in monthly quality updates and in peer discussions. For UK MedComms professionals, external peer networks can be useful for testing whether a process weakness is common, provided that client confidentiality and commercial sensitivity are respected.
MedComms Networking UK readers will recognise the tension between openness and exposure. The habit works when leaders thank people for reporting a close call and when the resulting actions are visible. A team that reports more near misses is not necessarily becoming more error-prone. It may simply be learning earlier.
Know when the routine is not enough
A blameless review does not replace formal incident reporting. If a close call touches patient safety, a suspected regulatory breach, data protection or a serious compliance concern, escalate it immediately through the proper channel. The learning review can follow, but it should not delay the required process. Keep a record of the escalation and the advice received.
As UK teams plan the final weeks of 2026, the close call log is a modest addition to the calendar. Its value lies in repetition. A weekly triage, a monthly review and a visible action tracker can turn relief into improvement. The aim is not to dwell on what almost went wrong. It is to make sure the same conditions do not get a second chance.
