Data protection

Spotting phishing: training for practice staff

A practical phishing training plan for GP, dental and clinic staff: realistic examples, red flags, fair simulated tests and a simple reporting routine.

Ava research teamPublished 6 min read

On this page
  1. Why phishing deserves most of your training time
  2. What phishing looks like in a practice
  3. Red flags to teach
  4. A year-round training plan
  5. Running fair simulated tests
  6. One routine for reporting
  7. Example: the invoice that nearly got paid
  8. Scripts for the phone and the front desk
  9. What managers and partners should model
  10. Making it stick
  11. Frequently asked questions
  12. References

Key takeaways

  • Phishing is the attack most organisations actually face: 85% of UK businesses that identified a breach or attack in 2025 had experienced it.
  • Training works best as short, practice-specific scenarios repeated through the year, not a once-a-year slideshow.
  • Measure how many people report a suspicious message, not just how many click.
  • A one-step reporting routine, and thanks for every report, matter more than any single test.

Why phishing deserves most of your training time

Among UK businesses that identified a cyber breach or attack in the 2025 government survey, phishing was by far the most common type, experienced by 85%[1]. Impersonation of the organisation or its staff affected 34%[1], and phishing was the most disruptive attack for 65% of businesses that had one[1]. Practices are attractive targets because they hold sensitive data, pay suppliers and handle a constant flow of email from people they do not know.

Attacks among UK businesses that identified a breach or attack, 2025Cyber security breaches survey 2025
Attacks among UK businesses that identified a breach or attack, 2025Bar chart. Experienced phishing: 85%; Phishing was the most disruptive attack: 65%; Experienced impersonation: 34%.Experienced phishingExperienced phishing: 85%85%Phishing was the most disruptive attackPhishing was the most disruptive attack: 65%65%Experienced impersonationExperienced impersonation: 34%34%Attacks among UK businesses that identified a breach or attack, 2025Bar chart. Experienced phishing: 85%; Phishing was the most disruptive attack: 65%; Experienced impersonation: 34%.Experienced phishingExperienced phishing: 85%85%Phishing was the most disruptive attackPhishing was the most disruptive attack: 65%65%Experienced impersonationExperienced impersonation: 34%34%

Source: GOV.UK (Department for Science, Innovation and Technology), 2025[1]

Show the data
ItemValue
Experienced phishing85%
Phishing was the most disruptive attack65%
Experienced impersonation34%

Training is also a requirement. The 2026-27 Data Security and Protection Toolkit asks GP practices whether at least 95% of staff have completed data security and protection and cyber security training in the last twelve months[2]. The Caldicott Principles make the same point in broader terms: everyone with access to confidential information should be aware of their responsibilities[3].

What phishing looks like in a practice

Generic examples about parcel deliveries do not prepare reception and admin staff for what actually arrives. Build your training around messages like these, rewritten for your own systems and suppliers.

  • A password-expiry email that copies your email provider's branding and links to a fake login page.
  • A supplier email saying bank details have changed, with an invoice attached, sent from an address one letter different from the real one.
  • A message from a ‘patient’ with an attachment called test results or referral letter that asks the reader to enable editing.
  • A request for records from a ‘solicitor’ or ‘insurer’ using a free email address and an urgent deadline.
  • A text to a manager's mobile, apparently from a partner, asking them to buy gift cards or approve a payment quickly.
  • A phone call to reception from someone claiming to be IT support who needs a smartcard passcode or a remote session.

The last example is phishing by phone. Training that only covers email misses the channel reception uses most.

Red flags to teach

Red flags staff should recognise, with the safe response for each.
Red flagWhat to checkSafe response
Urgency or threatIs there a real reason this cannot wait an hour?Pause and verify
A change to payment detailsWas this expected? Does the sender's address match exactly?Call the supplier on a number you already hold
A link to log inDoes the address bar show the genuine domain?Go to the service directly, not through the link
An unexpected attachmentWere you expecting it from this sender?Do not open; report it
A request to bypass processWould this person normally ask you this?Follow the usual process anyway
Requests for codes or passwordsDoes any genuine service ever ask for these?Never share; report

A year-round training plan

  1. Induction

    Every new starter, locum and volunteer completes the practice's data security training before getting system access, with a ten-minute session on practice-specific scams and the reporting routine.

  2. Annual core training

    Everyone completes the mandatory course and you record completion so the toolkit return is easy.

  3. Monthly five-minute scenarios

    At a team huddle, show one real or realistic message, ask what people would do, and agree the answer. Rotate who presents.

  4. Quarterly simulated tests

    Send a realistic test email to all staff, then share the results as a team, not by name, with the red flags explained.

  5. Targeted refreshers

    Offer a short one-to-one with anyone who clicks twice, framed as support rather than discipline.

  6. After every real incident

    Share what happened, what the warning signs were and what worked, within a week.

Running fair simulated tests

Simulated phishing helps if staff trust it and harms if they feel trapped. Announce the programme in advance, never use messages that exploit personal fears such as pay cuts or redundancies, and never name individuals in results. Track the report rate, the share of staff who flagged the test, as closely as the click rate. A practice where most people report quickly is safer than one where few click but nobody reports.

Use your toolkit evidence too. The toolkit asks some types of organisation, such as IT suppliers, for the number of phishing emails reported by staff each month[2]. Even where a practice is not asked for that measure, counting reports each month is a simple way to see whether the culture is working.

One routine for reporting

  1. Do not click, reply or forward the message to colleagues.
  2. Report it using the practice's single route, such as a report button or a named mailbox, and tell the practice manager if you clicked or entered details.
  3. If you entered a password, change it straight away and tell IT; if a smartcard or payment is involved, tell the manager immediately.
  4. Forward suspicious emails to [email protected], the National Cyber Security Centre's reporting service, unless your IT provider handles this for you.
  5. Delete the message once reported.

The national reporting service matters beyond your own inbox: the NCSC says it had removed 454.8 thousand scam URLs as of July 2026[4]. Every report helps take down a site that would otherwise reach the next practice.

Example: the invoice that nearly got paid

Example: Lakeside Dental, a fictional practice, receives an email from its laboratory asking for the next payment to go to a new account. The address matches except for one character. The receptionist who opens it remembers the monthly scenario from two weeks earlier, does not reply, and uses the report button. The manager calls the laboratory on the number in the contract; the laboratory's account had been compromised and other customers had received the same message.

Example: the manager thanks the receptionist at the next huddle, shares the email with the red flags marked, and adds a rule that any change to supplier bank details needs a call-back to a known number and a second person's approval.

Scripts for the phone and the front desk

Phone-based phishing works because receptionists are trained to be helpful. Give them words that are helpful and safe at the same time, and practise them in role play so they come out naturally under pressure.

  • Caller says they are IT support and needs a passcode: ‘We never share passcodes, even with IT. If you're from our provider, please log a ticket and I'll call the service desk back on our usual number.’
  • Caller says they are a supplier with new bank details: ‘Thanks, please put that in writing. Our manager will confirm it with you by phone before anything changes.’
  • Caller says they are from the bank and the practice account is at risk: ‘I'll pass this to our manager, who will call the bank on the number on our statements.’
  • Caller asks whether a named person is a patient: ‘I'm not able to confirm who is registered here. If you send a request in writing, it will go to the right person.’

Each script ends the same way: the member of staff hangs up, uses a number the practice already holds, and reports the call. That is the habit that defeats nearly every social engineering attempt.

What managers and partners should model

Attackers often impersonate senior people, because staff hesitate to question them. Partners and managers can remove that leverage by saying openly that they will never ask for urgent payments, gift cards, passwords or records by email or text, and by thanking staff who check with them. When a partner is caught by a test email, saying so at the next meeting does more for the culture than any poster.

  • Use the same reporting route as everyone else, and report your own mistakes.
  • Never send genuine requests that look like phishing: urgent payment requests by text, or links to log in sent from personal accounts.
  • Agree a verification step for any unusual request from a senior person, and follow it yourself.

Making it stick

The single biggest factor is how people are treated when they report. Thank every report, including false alarms, and treat a reported click as a good outcome, because it lets you act. Staff who fear blame stay silent, and silence is how a phishing email becomes a ransomware incident. Pair this work with ransomware preparedness, Cyber Essentials and the rules on smartcards and shared logins, and check that requests for records arriving by email follow the subject access process.

Finally, remember what is at stake for patients: their records are special category data under UK GDPR[5], and a successful phishing attack is often the first step in a breach that exposes them.

Frequently asked questions

How often should practice staff have phishing training?

Complete the mandatory annual course, and add short monthly scenarios and occasional simulated tests. The toolkit expects at least 95% of staff trained in the last twelve months[2].

Should we discipline staff who click a test email?

No. Use it as a learning moment and offer a short refresher to repeat clickers. Blame discourages reporting.

Where do we report a suspicious email?

Use your practice's internal route first, then forward it to [email protected] unless your IT provider does this for you[4].

What if someone entered their password on a fake page?

Change the password immediately, tell IT and the practice manager, check for unusual activity and record it as a security incident.

References

  1. GOV.UK (Department for Science, Innovation and Technology) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  2. NHS England (Data Security and Protection Toolkit) (2026). Outcomes, assertions and evidence items for the Data Security and Protection Toolkit 2026-27 version 9 (opens in a new tab) ↑

  3. GOV.UK (National Data Guardian) (2020). The Caldicott Principles (opens in a new tab) ↑

  4. National Cyber Security Centre (2026). Reporting a scam email (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (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