Key takeaways
- Use three channels with three jobs: clinical system tasks for anything about a patient, team chat for coordination, and phone or in person for urgent matters.
- No patient-identifiable information in general chat; it belongs in the record and the task list.
- A good task says who, what, why and by when, so the clinician can act without asking.
- Protect clinic time with batching, quiet hours and a duty clinician for anything that cannot wait.
- Count interruptions for a week before and after, so the change is judged on evidence.
The cost of a knock on the door
Every practice has its own interruption culture: the receptionist who pops into a consulting room between patients, the pop-up message during a telephone consultation, the task marked urgent that is really a reminder. Each one is small. Together they break concentration in the part of the day when clinicians most need it.
Clinicians are already stretched. According to the GMC's 2025 workplace experiences research, 22% of GPs say they are unable to cope with their workload at least once a day, compared with 12% of all doctors[1]. Each full-time GP in England now has an average of 2,143 patients[1], and practices delivered 1.55 million appointments per working day in March 2026[2]. A messaging system that adds avoidable interruptions makes all of that harder.
Source: British Medical Association, 2025[1]
Show the data
| Item | Value |
|---|---|
| GPs | 22% |
| All doctors | 12% |
Three channels, three jobs
| Message type | Right channel | Why |
|---|---|---|
| Anything about a named patient that needs action | Task in the clinical system | Recorded, auditable, stays with the patient's record |
| Results, letters and documents needing review | Clinical system workflow | One queue per clinician, nothing lost in chat |
| Rota changes, room swaps, supplies, IT issues | Team chat channel | Quick coordination with no patient data |
| Questions to a colleague with no patient detail | Team chat, direct message | Fast and informal |
| Clinical urgency: a patient deteriorating, an emergency call | Phone, alarm or in person | Immediate; nobody should rely on a message being read |
| Notices for everyone | Team chat announcements, plus huddle | One place to look, repeated face to face |
The point is not the tools but the agreement. If everyone knows which channel is for what, people stop sending the same message three ways to be sure, and clinicians can safely ignore chat during a clinic.
Rules that protect clinicians
- No patient-identifiable information in general team chat. Patient matters go in the clinical system, where data concerning health is protected as the special category data it is[3].
- If it needs an action, it is a task, not a message.
- If it needs an answer within the hour, it goes to the duty clinician, not to whichever clinician is nearest.
- If it is an emergency, phone or go in person. Never message.
- During clinics, chat notifications are off for clinicians. They check messages between sessions.
- Mark tasks urgent only when they meet the practice's written definition of urgent.
- Expect replies to non-urgent chat by the end of the day, not in minutes.
Write the rules on one page, discuss them at a team meeting and display them where staff can see them. They only work if partners and managers follow them too.
Writing a task a clinician can act on
Most of the follow-up messages that interrupt clinicians are caused by unclear tasks. A clinician who has to ask what a task means, or ring the patient to find out, has lost the time the task was meant to save.
Who
The patient, linked to the record, and who raised the request.
What
The request in one sentence: "Patient asking whether to continue amlodipine after hospital stopped it."
Why now
Any background the clinician needs: the discharge letter date, what the patient said, what they have already tried.
Action needed
What you are asking the clinician to do: decide, call back, sign, review.
By when
The deadline the practice process sets, not a guess.
Example (fictional) task: "Mrs A. (linked). Asking if she should restart amlodipine; discharge letter 3 Nov says stopped due to low BP. She feels well, no dizziness. Please advise and reception will call her back. Needed today by 4pm per prescription process."
Setting up team chat properly
Many practices use Microsoft Teams through NHSmail or a similar tool. Set it up deliberately rather than letting it grow.
- A small number of channels with clear names: announcements, rota and cover, IT and facilities, each site.
- Announcements channel restricted to managers, so important notices are not buried.
- Guidance pinned in each channel: what belongs there and what does not.
- Notification settings agreed for clinicians: off during clinics, on between sessions.
- Retention set in line with your records policy, and a reminder that chat can be disclosed in a subject access request or complaint.
- Personal messaging apps on personal phones not used for practice business.
Health and care organisations in England work to the Caldicott Principles, including using the minimum necessary confidential information on a need-to-know basis[4]. A chat channel seen by the whole team is never need-to-know.
The duty clinician as a buffer
A duty clinician absorbs the interruptions that genuinely cannot wait, so other clinicians do not have to. That works only if the route is clear: reception knows which questions go to the duty clinician, how to reach them, and what counts as urgent. Without that, staff will knock on the nearest door.
- Publish the duty rota where reception can see it at a glance.
- Give the duty clinician a direct line or bleep that is not shared with other work.
- Agree a short list of matters that always go to the duty clinician, such as same-day clinical concerns and calls from other services.
- Hold a short catch-up between reception and the duty clinician mid-morning, so routine questions can be batched.
Messages arriving from outside
Internal rules break down when outside messages arrive by the wrong route. Pharmacies, care homes, community teams, hospital departments and patients all contact the practice, and each tends to use whichever channel got a quick answer last time. Decide where each one should land and tell them.
- Give pharmacies and care homes a dedicated professional line or shared mailbox, staffed at set times, rather than the patient line or a clinician's direct number.
- Ask hospital and community teams to send clinical correspondence through the normal document route, so it is filed against the record.
- Send patient emails and online messages into the same queue as online forms, not into individual inboxes.
- Check shared mailboxes at fixed times every day and record who checked them.
- Reply to messages sent by the wrong route with a short note giving the right one, so the habit changes.
Dental practices and private clinics
The same principles apply in smaller teams, with a few differences. In a dental practice the dentist is usually chairside with a nurse, so interruptions cost two people's time and can affect the patient in the chair. Agree that the front desk only interrupts a surgery for an emergency or a patient who has arrived and needs attention, and that everything else waits for a gap between patients. In private clinics where practitioners work sessions on different days, a shared task list in the practice management system matters more than chat, because the person who can act may not be in until next week.
Whatever the setting, the test is the same: could the person receiving the message act on it without asking a single question? If not, the message needs rewriting before it is sent.
Rolling out the change
- Count interruptions to clinicians for one week: a simple tally sheet in each room works.
- Draft the channel rules and task template with a receptionist, a clinician and the manager.
- Launch at a team meeting, with examples of good and poor tasks.
- Review a sample of tasks after two weeks and give friendly feedback.
- Count interruptions again after a month and share the result.
Example: two weeks of tallies
Example (fictional): GPs at a five-partner practice record every interruption during morning surgery for a week.
In this example the largest group of interruptions is reception asking whether a patient can be fitted in, followed by prescription queries and chat messages about room changes. The practice routes all fit-in questions to the duty doctor, introduces the task template for prescription queries and turns off chat notifications during clinics. A second tally a month later shows interruptions roughly halved, and the duty doctor reports that batched questions at mid-morning take less time than the scattered ones did.
Keeping it working
- Repeat the interruption tally twice a year.
- Check a sample of tasks for clarity each quarter.
- Review chat channels and archive the ones nobody uses.
- Include the channel rules and task template in every induction.
- Ask clinicians and reception each quarter what is still getting in the way.
Frequently asked questions
Should patient information go in Microsoft Teams chats?
Not in general team chat. Patient matters belong in clinical system tasks, where they are recorded, auditable and limited to the people who need them.
What is the difference between a task and a message?
A task asks someone to act on something and stays on record in the clinical system. A message is quick coordination with no patient data and no formal action.
How do we stop reception interrupting clinics?
Route anything that cannot wait to a duty clinician, batch routine questions for a set time and agree a written definition of urgent.
How can we tell if the new rules are working?
Tally interruptions for a week before the change and again a month later, and review a sample of tasks for clarity.
References
British Medical Association (2025). Pressures in general practice data analysis (opens in a new tab) ↑
NHS England (via GOV.UK) (2026). NHS England annual report and accounts 2025 to 2026 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2026). The Caldicott Principles (opens in a new tab) ↑