Data protection and cyber security

Annual data protection audit checklist for law firms

An annual data protection audit for law firms: records of processing, notices, suppliers, security, rights requests and retention, with the evidence.

Ava research teamPublished 6 min read

On this page
  1. What the annual audit is for
  2. Part 1: records and registration
  3. Part 2: notices and client-facing information
  4. Part 3: suppliers and transfers
  5. Part 4: security and incidents
  6. Part 5: rights requests and retention
  7. Writing the audit report
  8. Running the audit in five working days
  9. Frequently asked questions
  10. References

Key takeaways

  • Run the audit in five parts: records, notices, suppliers, security and incidents, and rights and retention.
  • For each item, collect evidence rather than ticking yes: a document, a log, a screenshot or a test result.
  • Supplier checks are the most neglected area; few businesses review their suppliers' risks at all.
  • Finish with a dated report, named owners and deadlines, and file it where the next audit can find it.

What the annual audit is for

An annual data protection audit is not a legal requirement in its own right. It is the simplest way to show that the firm knows what personal data it holds, why, where it goes and how it is protected, and to catch the drift that happens when people, suppliers and systems change during the year.

Most firms are small enough that one person can run it in a week. 78% of UK legal activities enterprises employ between none and four people[1]. The checklist below scales up for larger practices by giving each part to a different owner.

Choose a fixed month, outside your busiest period and away from practising certificate renewals, and keep the same order every year so results can be compared.

Decide the scope before you start. Include every office, every system that holds client or staff data, home working arrangements and every supplier with access to personal data. A common gap is the firm's own staff records: HR files, payroll and recruitment often sit outside the systems people think of when they hear 'data protection'.

Part 1: records and registration

UK GDPR Article 30 requires each controller to maintain a record of processing activities. The exemption for organisations with fewer than 250 staff does not apply where processing is likely to result in a risk to people's rights and freedoms, is not occasional, or includes special category or criminal offence data[2]. Law firms routinely handle health, family and criminal information, so in practice most need a record.

  • Record of processing reviewed and updated for new practice areas, systems and suppliers.
  • Lawful basis recorded for each purpose, including marketing and recruitment.
  • ICO data protection fee paid and the tier still correct. The fees are £52 for tier 1 (micro organisations), £78 for tier 2 and £3,763 for tier 3; tier 1 covers organisations with turnover up to £632,000 or no more than ten staff[3].
  • Data protection lead named and their contact details current on the website and in notices.

Test the record against one real matter from each department. Follow a conveyancing file, a family file and a private client file from first enquiry to archive, and check that every place the data went appears in the record: the enquiry form, the phone system, the case management system, the email archive, the bank, the search provider, the Land Registry portal and the storage company.

Part 2: notices and client-facing information

  • Website privacy notice matches what the firm actually does, including call recording, web forms, live chat and any AI tools.
  • Client care letter and terms of business refer to the current notice.
  • Engagement letters explain how the firm will communicate, including any use of text messages, portals or AI tools.
  • Recruitment privacy notice exists and is sent to applicants.
  • Cookie banner and settings reflect the cookies the site actually sets.
  • A route for data protection complaints exists. The Data (Use and Access) Act 2025 requires organisations to handle such complaints, for example by providing an electronic complaint form, and to tell people the outcome[4].

Read each notice as a client would. If the notice says calls are not recorded but the new phone system records by default, the notice is wrong. If the website form now feeds a supplier's system, that supplier belongs in the notice.

Part 3: suppliers and transfers

This is the part most often skipped. Only 15% of UK businesses monitor risks from their suppliers or wider supply chain[5]. A law firm's suppliers include case management, cloud storage, email, telephony, dictation and transcription, IT support, payroll, document storage, shredding and any AI tools.

Share of UK businesses taking key cyber governance actions, 2025
Share of UK businesses taking key cyber governance actions, 2025Column chart. Two-factor authentication: 40%; Incident response arrangements: 30%; Cyber risk assessment: 29%; Staff training: 19%; Supplier risk monitoring: 15%.0%10%20%30%40%Two-factor authentication: 40%40%Two-factorauthenticationIncident response arrangements: 30%30%Incident responsearrangementsCyber risk assessment: 29%29%Cyber riskassessmentStaff training: 19%19%Staff trainingSupplier risk monitoring: 15%15%Supplier riskmonitoringShare of UK businesses taking key cyber governance actions, 2025Column chart. Two-factor authentication: 40%; Incident response arrangements: 30%; Cyber risk assessment: 29%; Staff training: 19%; Supplier risk monitoring: 15%.Two-factor authenticationTwo-factor authentication: 40%40%Incident response arrangementsIncident response arrangements: 30%30%Cyber risk assessmentCyber risk assessment: 29%29%Staff trainingStaff training: 19%19%Supplier risk monitoringSupplier risk monitoring: 15%15%

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

Show the data
ItemValue
Two-factor authentication40%
Incident response arrangements30%
Cyber risk assessment29%
Staff training19%
Supplier risk monitoring15%
  • List every supplier that touches personal data, with what data and why.
  • Check a signed data processing agreement is on file for each.
  • Confirm where data is stored and what safeguards apply to transfers outside the UK.
  • Ask for current security evidence from the critical few.
  • Remove access for suppliers you no longer use.

Rank suppliers by what they can reach. The critical few are usually case management, email, cloud storage, telephony and IT support, because each can see large volumes of client data. Spend most of the supplier time on them and a few minutes on the rest.

Part 4: security and incidents

Security checks and the evidence that proves each one
CheckEvidence to collectTypical owner
Multi-factor sign-in on email, case management and remote accessScreenshot of settings; list of exceptionsIT provider
Leavers removed from all systemsLeavers list compared with active accountsOffice manager
Backups run and a restore testedDate and result of last restore testIT provider
Personal device policy signed by all staffAcknowledgement logCOLP or data protection lead
Physical walk rounds carried outMonthly walk-round entriesOffice manager
Training delivered and recordedTraining log with dates and attendeesData protection lead
Incident log completeLog entries, including incidents not notified, with reasonsData protection lead

Test the breach process as well as reading it. A personal data breach must be notified to the ICO without undue delay and, where feasible, within 72 hours of awareness[6]. Pick last year's most serious incident and check how long each step actually took.

Look at the phone system as closely as the computers. Call recordings, voicemail transcripts and enquiry notes often hold more sensitive detail than emails, and they are easy to forget. Check who can access recordings, how long they are kept and whether callers are told about recording at the start of the call.

Part 5: rights requests and retention

  • Subject access request log: dates received, identity checks and dates answered.
  • Templates for responses, exemptions for privileged material and redaction steps up to date.
  • Retention schedule by matter type, applied to closed files, archive boxes and email.
  • Evidence of deletion or destruction: shredding certificates and system deletion reports.
  • Marketing lists checked for consent and opt-outs.

Retention is where partners disagree. Agree periods by matter type once, write down the reasoning, and apply them. A schedule that exists on paper while thirty years of closed files sit in storage is worse than no schedule, because it shows the firm knew what it should be doing.

Writing the audit report

  • A one-paragraph summary for the partners: overall status and the three most important actions.
  • A table of every amber and red item, with owner and deadline.
  • Items carried over from last year, marked clearly so repeat failures stand out.
  • Changes since last year: new systems, suppliers, offices or practice areas.
  • Incidents and requests during the year, with numbers and any lessons.
  • Sign-off by the managing partner and the date of the next audit.

Running the audit in five working days

  1. Day 1: gather

    Pull last year's report, the record of processing, supplier list, incident log, training log and request log.

  2. Day 2: interview

    Spend 20 minutes each with the COLP, the office manager, the IT provider and one fee earner per department. Ask what changed this year.

  3. Day 3: test

    Check accounts against the leavers list, try the website complaint route, and walk the office after hours.

  4. Day 4: score

    Mark each item green, amber or red, with the evidence or the gap.

  5. Day 5: report

    Write a two-page report with owners and deadlines for every amber and red item, signed off by the managing partner.

Example: a fictional eight-person firm finds three red items in its first audit: no processing agreement with its dictation supplier, two former trainees still able to sign in, and no record of the last restore test. All three are fixed within a month and checked again at the half-year point.

Feed the findings into your training plan, your device policy and your rules on AI tools, then diarise next year's audit before you close this one.

The first audit is always the slowest. Expect it to take twice as long as the five days above, mostly because the record of processing and the supplier list need building rather than checking. From the second year, most of the work is comparing this year's answers with last year's and chasing the changes.

Frequently asked questions

Is a data protection audit a legal requirement?

Not as a standalone duty, but UK GDPR expects controllers to be able to demonstrate compliance. A dated annual audit with evidence is one of the clearest ways to do that.

Who should carry out the audit?

The data protection lead or COLP can run it in most small firms. An outside reviewer every few years adds a fresh view, especially after a merger or a new system.

How long should we keep audit reports?

Keep them for several years so you can show progress over time, and store them with the record of processing and the incident log.

References

  1. Office for National Statistics (2026). UK business: activity, size and location, 2026 (Tables 2, 4, 9 and 17) (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 30: Records of processing activities (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2018). The Data Protection (Charges and Information) Regulations 2018, regulation 3 (opens in a new tab) ↑

  4. GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑

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

  6. 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) ↑

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