Key takeaways
- Annual slide decks satisfy a checklist but rarely change what reception and secretaries do at 4.55pm on a Friday.
- Train on the real moments: callers claiming to be clients, bank detail changes, misdirected emails and requests for information by phone.
- Ten-minute monthly scenario huddles beat one long session; keep a simple record of who attended.
- Measure behaviour, not attendance: test emails, near-miss reports and spot checks of call handling.
Why most data protection training does not stick
The usual pattern is a yearly online module, a quiz and a certificate. It ticks a box, and within a month nobody remembers which slide covered what to do when a caller asks for a client's new address.
Small organisations are the least likely to train at all. Only 19% of UK businesses carried out cyber security training or awareness raising in the past year, compared with 54% of medium and 76% of large businesses[1]. Most law firms sit in the smaller group.
Source: Department for Science, Innovation and Technology (GOV.UK), 2025[1]
Show the data
| Item | Value |
|---|---|
| All businesses | 19% |
| Medium businesses | 54% |
| Large businesses | 76% |
The SRA's cyber security review found the same gap inside the profession: eight of the 40 firms visited (20%) had never provided specific cyber security training to staff, and more than half did not keep records of who had been trained[2]. Training on newer tools is thinner still: only 11% of UK businesses with ten or more staff say more than half their workforce has had AI-related training[3].
Adults learn from stories and from their own near-misses far more than from definitions. A receptionist who has once role-played a caller pressing for a client's new address will hesitate in the right place next time. Someone who has only read that 'personal data must be processed lawfully' will not.
Train on the moments that actually happen
Front-office staff do not need a lecture on the principles of UK GDPR. They need to recognise six or seven situations and know the firm's answer to each. Build the programme around these.
- A caller says they are the client and asks for an update, but the number is new and they cannot give the matter reference.
- An email, apparently from a client, asks to change the bank account for completion monies.
- A relative or new partner asks what stage a divorce or probate matter has reached.
- An email with attachments goes to the wrong recipient because the address auto-filled.
- A former client asks on the phone for "everything you hold about me".
- A file is left in a meeting room after a client leaves, or papers go missing from a bag.
- A colleague pastes a client letter into a free AI tool to improve the wording.
Ask the team which of these happened in the last three months. The answers tell you where to start, and they turn the training from something done to staff into something built with them.
Phishing deserves the most time: among businesses that identified a breach or attack, 85% experienced phishing[1]. After a breach, additional staff training or communication was the most common preventative step businesses took (32%)[1]. It is cheaper to do it first.
Scripts for the three hardest moments
Three situations cause most of the anxiety on a front desk. Give staff words they can use without thinking.
Bank details: 'Thank you for letting us know. We never act on new bank details sent by email. I will call you on the number we already hold to confirm before anything changes, and nothing will be sent until then.'
A relative asking for an update: 'I understand you want to help. I cannot share anything about anyone's matter without their permission. If they would like you involved, they can tell us directly, and we will note it on the file.'
A request for 'everything you hold about me': 'I will pass this to our data protection lead today. So we can send it securely, could you confirm the best address to reach you and the dates you were a client? We will be in touch to confirm your identity.'
Print the scripts on one card for each desk. Update them when the firm's process changes, and say so at the next huddle.
A 12-month plan that fits a busy firm
| Month | Scenario | Format | Time |
|---|---|---|---|
| January | Verifying a caller before discussing a matter | Role play at the team meeting | 10 min |
| February | Bank detail change requests | Real (anonymised) fraud email, spot the signs | 10 min |
| March | Misdirected email: what to do in the first hour | Walk through the reporting steps | 10 min |
| April | Subject access requests by phone or email | Script practice | 10 min |
| May | Clear desk and visitors | Five-minute walk round of the office | 10 min |
| June | Personal phones and messaging apps | Policy refresher with examples | 10 min |
| July | AI tools and client data | Which data class is this? | 10 min |
| August | Holiday cover and shared inboxes | Who can see what | 10 min |
| September | Third parties calling about a client | Role play | 10 min |
| October | Phishing test results | Review what people clicked and why | 15 min |
| November | Breach reporting and the 72-hour clock | Timeline exercise | 10 min |
| December | Year review and quiz | Short quiz, refresh the policy pack | 15 min |
Keep the annual online module if your insurer or accreditation asks for it, but treat it as a baseline rather than the training itself.
Rotate who leads each huddle. A secretary who has handled a tricky caller often teaches the point better than a partner reading from a policy, and leading a session is the fastest way to learn it.
How to run a ten-minute scenario huddle
Set the scene (1 minute)
Read out the situation in two sentences, using real wording from a call or email with identifying details removed.
Ask before you tell (3 minutes)
Ask each person what they would do next. Write the answers on a board without judging them.
Give the firm's answer (2 minutes)
Show the script or rule, and say why it exists, including the duty to keep client affairs confidential under the SRA Code of Conduct[4].
Practise once (3 minutes)
Two people act it out with the script. Swap roles if time allows.
Record it (1 minute)
Note the date, topic and who attended in a shared log. That record is your evidence.
Script for an unverified caller: "I am sorry, I cannot discuss any matter until I have confirmed who I am speaking to. I will call you back on the number we hold on file, or you can email us from the address you gave us at the start."
Induction for new starters and temps
New people are most at risk in their first fortnight, when they want to be helpful and do not yet know the firm's rules. Before anyone answers the phone or opens the post, give them a 20-minute induction covering four things: how to verify a caller, what to do with a bank detail change, how to report a mistake, and where the scripts live. Pair them with an experienced colleague for their first few days on reception, and add them to the training log on day one so the next huddle includes them.
Measuring whether it worked
Attendance shows that training happened. It does not show that behaviour changed. Track a few measures every quarter and discuss them at the huddle.
- Phishing test click rate and, more important, the share of staff who report the test email.
- Near-miss reports: a rising number early on is a good sign, because people are noticing.
- Spot checks: once a quarter, a manager listens to three new-enquiry calls and checks identity steps were followed.
- Time from discovering an incident to reporting it internally, compared with the 72 hours the firm has to notify the ICO where required[5].
None of these measures works if people fear blame. Thank staff publicly for reporting a near-miss, never name the person who clicked a test email, and make it clear that the only serious mistake is hiding one.
Making it part of the working week
- Fix the slot: the first ten minutes of an existing team meeting, so nobody has to book extra time.
- Partners attend at least quarterly. Staff notice who turns up.
- Use the firm's own near-misses, anonymised, as the next month's scenario.
- Keep each scenario to one decision. If it needs a flowchart, split it into two sessions.
- File the attendance log where the annual audit will look for it.
Example: a front office after six months
Example: a fictional four-person front office at a conveyancing and family practice starts monthly huddles in January. By June, staff report two suspicious bank detail emails, one misdirected attachment and one caller who could not be verified. None led to a loss. Each was logged, and the misdirected email was assessed and recorded as not notifiable within a day.
The partner responsible notes one gap: new temps miss the huddles. The firm adds a 20-minute induction covering the first four scenarios before any temp answers the phone. Pair this with your BYOD rules and a yearly audit that checks the training log.
Frequently asked questions
How often should law firm staff have data protection training?
Short, frequent sessions work better than one long annual course. Many firms run a ten-minute scenario every month and a fuller refresher once a year.
Do we need to keep training records?
Yes. Records show the firm took reasonable steps and help you spot who missed key topics. A simple log of date, topic and attendees is enough.
Should temps and locums be trained?
Yes, before they handle calls or files. A short induction covering verification, bank detail changes and incident reporting covers the highest risks.
References
Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Solicitors Regulation Authority (2020). Cyber Security - A thematic review (opens in a new tab) ↑
Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑
Solicitors Regulation Authority (2025). SRA Code of Conduct for Solicitors, RELs, RFLs and RSLs (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑