Reception staffing

Cutting clinician admin with better delegation

Which admin tasks practice teams can take from GPs safely, how to write and audit delegation protocols, and where tools fit and where they must not.

Ava research teamPublished 6 min read

On this page
  1. The case for moving admin away from clinicians
  2. Tasks admin teams commonly take on
  3. Setting up document workflow
  4. Getting GPs and staff on board
  5. What every delegation protocol needs
  6. The wider team is already delivering care
  7. Training and measuring the benefit
  8. Where tools fit
  9. What should stay with clinicians
  10. Example: freeing a session a week
  11. Frequently asked questions
  12. References

Key takeaways

  • GPs are under heavy strain: 22% say they cannot cope with their workload at least once a day, against 12% of all doctors[1].
  • Small savings add up: the government estimates that saving 90 seconds per GP appointment would create over 2,000 full-time GPs' worth of capacity[2].
  • Document workflow, recalls, referral admin, results communication and form preparation are the most common tasks moved safely to trained admin staff.
  • Every delegated task needs a written protocol, named clinical oversight, training with sign-off and a regular audit.
  • Tools can help, but many software and AI products used in health care are regulated as medical devices[3], so check before you rely on one.

The case for moving admin away from clinicians

GP time is the scarcest resource in most practices. Each full-time-equivalent GP in England now looks after an average of 2,143 patients[1], and many spend hours each day on letters, results, forms and tasks that do not need a doctor's training. According to the GMC's Workplace Experiences 2025 report, 22% of GPs say they are unable to cope with their workload at least once a day, compared with 12% of all doctors[1].

Doctors unable to cope with their workload at least once a dayGMC Workplace Experiences 2025, as reported by the BMA
Doctors unable to cope with their workload at least once a dayComparison. GPs: 22%; All doctors: 12%.22%GPsGPs: 22%12%All doctorsAll doctors: 12%Doctors unable to cope with their workload at least once a dayComparison. GPs: 22%; All doctors: 12%.22%GPsGPs: 22%12%All doctorsAll doctors: 12%

Source: British Medical Association, 2025[1]

Show the data
ItemValue
GPs22%
All doctors12%

The government's 10 Year Health Plan estimates that saving just 90 seconds per GP appointment would generate over 2,000 full-time-equivalent GPs' worth of capacity[2]. Delegating admin does not save time inside the appointment, but it frees whole sessions that GPs currently spend on paperwork, which can go back to patients or to the clinical work that only a GP can do.

Tasks admin teams commonly take on

Admin tasks commonly delegated from GPs and the safeguard each needs
TaskWhat trained admin staff doClinical safeguard
Incoming letters and documentsRead, code agreed items, action routine requests and file letters that need no GP actionProtocol lists what must always go to a GP; monthly audit
Recalls for long-term conditionsRun searches, invite patients, book the right clinicianClinician-approved recall rules and search definitions
Results communicationTell patients about results the clinician has marked as normal or with a set messageClinician files and annotates every result first
Referral adminType and send referrals, chase acknowledgements, track urgent referralsClinician writes the clinical content; urgent tracking list
Forms and reportsPrepare insurance and other reports with record extracts for the GP to check and signGP reviews and signs everything
Repeat prescription requestsCheck requests against the repeat list and review dates, route to prescriberPrescriber authorises; protocol for overdue reviews
Care navigationDirect requests to the right professional or serviceNavigation protocol agreed by clinicians

Start with document workflow. In many practices it is the largest single block of GP admin, and well-designed protocols let trained staff handle a large share of incoming correspondence, with only letters that need a clinical decision going to a GP.

Setting up document workflow

  1. Measure the current load

    Count the letters and documents each GP receives in two typical weeks, and note how long they spend on them.

  2. Sort a sample together

    A GP and the lead admin sort a sample of a few hundred documents into three groups: file with no action, admin action (code, book, recall, send a standard message), and GP action needed.

  3. Write the protocol

    List the document types and wording that always go to a GP, such as new diagnoses, medication changes, safeguarding concerns, abnormal results and anything the staff member is unsure about. Everything else follows the admin rules.

  4. Train and sign off

    Train staff with real examples, then have a GP check their decisions on a set number of documents before they work alone.

  5. Audit every month

    A GP reviews a random sample of documents processed by admin. Record errors, discuss them and update the protocol.

  6. Review every year

    Update the protocol with new document types and lessons from audits and significant events.

Getting GPs and staff on board

Delegation often stalls not because the protocol is wrong but because people do not trust it. Some GPs worry that a missed letter will become their problem. Some admin staff worry that they are being asked to make clinical decisions without the pay or protection that should come with it. Both concerns are reasonable and deserve a direct answer.

  • Involve at least one sceptical GP in writing the protocol; their questions usually make it safer.
  • Be explicit that staff follow the protocol and the GP owns it; staff are not expected to make clinical judgements.
  • Recognise the extra responsibility with a defined role, such as document workflow lead, and pay to match.
  • Agree how errors will be handled: as learning through audit and significant event review, not blame.
  • Start with one GP's documents or one task, show the audit results, then expand.

What every delegation protocol needs

  • The task, written in one sentence, and the staff roles allowed to do it.
  • The training and sign-off required before someone works alone.
  • Clear rules on what must always go to a clinician, written as a list rather than a judgement call.
  • The default for uncertainty: if in doubt, send it to the clinician.
  • The named GP who owns the protocol and answers questions.
  • How decisions are recorded in the patient record.
  • The audit: sample size, frequency, who does it and where results are kept.
  • The review date.

Keep protocols short enough to use at the desk. A ten-page document nobody reads is less safe than a one-page list that staff check every time.

The wider team is already delivering care

Delegation is not new. In August 2026, only 44.4% of standard GP practice appointments were delivered by a GP; the rest were delivered by other practice staff[1]. Practices have already moved a great deal of clinical work to nurses, pharmacists, physiotherapists and others. The admin equivalent is to give trained non-clinical staff clear authority over defined tasks, with the same principles of competence, protocol and oversight.

Training and measuring the benefit

Train admin staff on real material, not slides. Work through anonymised examples of each document type, discuss the borderline cases and practise the 'if in doubt, send it to the GP' rule until it is automatic. Pair each trainee with an experienced colleague and a named GP for questions in the first weeks.

Measure the benefit from the start so the change can be judged on evidence. Record GP time spent on documents before and after, the number of items handled by admin, audit error rates and any significant events. If GP time does not fall, look for documents still being sent to GPs out of caution and refine the protocol with the owning GP.

  • GP minutes per day on documents and tasks, before and after.
  • Share of documents handled entirely by admin.
  • Audit findings each month, by type of error.
  • Time from document arrival to action for urgent items.

Where tools fit

Technology is changing what admin delegation looks like. The 10 Year Health Plan commits to rolling out ambient voice technology, often called AI scribes, digital triage and a single patient record to cut clinical admin within two years[2]. Among GPs who already use AI, 57% use it for clinical documentation and note-taking and 44% for administrative tasks[4].

Tools that draft, sort or summarise documents can support admin staff, but they need the same governance as a delegated task, and some need more. The MHRA says many software and AI products used in health and social care are regulated in the UK as medical devices[3]. Before using a tool for anything that affects clinical decisions, check its regulatory status, complete a data protection impact assessment, agree what it may and may not do, and keep a human check where the protocol requires one.

What should stay with clinicians

  • Interpreting abnormal or borderline results and deciding on action.
  • Medication changes, new prescriptions and medication reviews.
  • Safeguarding decisions, though admin staff should flag concerns.
  • Clinical content of referrals and reports.
  • Anything the protocol does not clearly cover, or that the staff member is unsure about.

Write these limits into every protocol in plain words, and repeat them in training. Staff who know exactly where their authority ends are more confident inside it, and GPs are more willing to let go of tasks when the boundary is visible. Revisit the limits whenever a new role joins the practice, such as a pharmacist or physician associate, because some tasks may move to them rather than to admin.

Example: freeing a session a week

Example (fictional): A six-GP practice finds each GP spends about an hour a day on incoming documents. After sorting a sample, the GPs agree that roughly two thirds need no GP action. Two experienced receptionists are trained as document workflow leads, signed off after supervised practice and audited monthly. After three months, each GP's document time has fallen by around half, and the monthly audit finds a small number of errors, each discussed and used to tighten the protocol.

The time saved did not come from working faster. It came from deciding, once, which documents genuinely need a GP, and giving trained staff the authority and support to handle the rest.

Frequently asked questions

Is it safe for receptionists to process GP letters?

It can be, with a written protocol that lists what must always go to a GP, training with sign-off, a named GP who owns the process and a regular audit of a sample of decisions.

Can admin staff tell patients their results?

Admin staff can pass on results that a clinician has reviewed and marked with a set message, such as normal and no action needed. Interpreting results and deciding on action must stay with clinicians.

Do we need clinical oversight for every delegated task?

Yes. Each protocol should have a named clinician who owns it, answers questions and reviews the audit results, even when day-to-day decisions are made by admin staff.

References

  1. British Medical Association (2025). Pressures in general practice data analysis (opens in a new tab) ↑

  2. GOV.UK (Department of Health and Social Care) (2025). Fit for the future: 10 Year Health Plan for England (opens in a new tab) ↑

  3. GOV.UK (Medicines and Healthcare products Regulatory Agency) (2025). Software and artificial intelligence (AI) as a medical device (opens in a new tab) ↑

  4. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo