Key takeaways
- The 2026-27 toolkit (version 9) was released on 2 October 2026, is aligned to the Cyber Assessment Framework version 4.0 and is due by 30 June 2027.
- GP practices complete the category 4 assertions and must reach 'Standards Met'.
- Last year's toolkit asked GPs for 45 evidence items and added two mandatory ones: IT administrator accountability and a digital asset register.
- Spread the work from November to May, use evidence your GP IT provider already supplies and leave June for checking, not writing.
Where the toolkit stands in November 2026
The Data Security and Protection Toolkit is the annual self-assessment that organisations with access to NHS patient data use to show they meet the National Data Guardian's data security standards. For 2026-27, version 9 of the assertions and evidence items was released on 2 October 2026 and is aligned to version 4.0 of the Cyber Assessment Framework[1]. The submission deadline is 30 June 2027[1].
GP practices use the category 4 set of assertions and evidence items, while dentists, pharmacies, opticians and social care providers use category 3[1]. Version 9 includes an updated requirement 10.2.1 for category 3 and 4 organisations[1], so read the change log rather than assuming last year's answers still fit.
30 June 2027
deadline for 2026-27 toolkit submissions[1]
What changed last year, and why it matters now
In 2025-26, one integrated care board's guidance to its GP practices counted 45 evidence requirements in total, mandatory and non-mandatory[2]. Two new mandatory items were added: 4.3.1 on IT administrator accountability and 7.1.1 on a digital asset register. Three existing items were amended and six non-mandatory items were added[2]. The same board highlighted the privacy notice item, 1.1.3, because many practice notices had not been updated since GDPR[2].
Source: NHS North East London (primary care), 2026[2]
Show the data
| Item | Value |
|---|---|
| New mandatory items | 2 evidence items |
| Amended items | 3 evidence items |
| New non-mandatory items | 6 evidence items |
Those additions are now part of the baseline. If your practice met them last year by writing a register or a policy in a hurry in June, this year is the time to make them real: an asset register someone actually maintains, and named accountability for every administrator account.
Know what your GP IT provider covers
Much of the technical evidence for GP practices is supplied centrally. In 2025-26 the North East London GP IT service provided statements and evidence for eleven items, including 4.3.1, 7.1.1 and several in the later sections on continuity and suppliers[2]. Your own board's GP IT team will have its own list. Ask for it in November, because it tells you exactly which items remain the practice's job.
- Request the GP IT evidence pack or statement list for 2026-27 as soon as it is published.
- Note which items it fully covers, which it partly covers and which it leaves to you.
- Do not copy GP IT statements into items they do not address; reviewers look for practice-specific evidence.
- Check that any practice-owned kit, such as a separate phone system or practice-bought laptops, is on your own asset register.
A month-by-month plan
November: set up
Name an owner and a deputy. Download the category 4 assertions and change log. Copy across last year's evidence and mark what needs refreshing.
December: people
Check the training records for all staff, including locums and new starters, and book catch-up sessions for anyone missing. Confirm the Caldicott Guardian and data protection officer details.
January: assets and accounts
Review the digital asset register against reality: every device, system and supplier. Review administrator accounts and who is accountable for each.
February: data flows and suppliers
Update your record of processing and data flow map. Check that every supplier processing patient data has a current contract.
March: policies and privacy notice
Review the data security, records management and acceptable use policies, and rewrite the privacy notice if it still describes old systems.
April: incidents and continuity
Review the breach and near-miss log. Test the business continuity plan, for example a tabletop exercise on losing the clinical system for a day.
May: draft complete
Enter every answer and upload evidence. Ask a colleague or your DPO to review the draft against the guidance.
June: check and publish
Resolve review comments, confirm sign-off by a partner and publish well before 30 June.
The gaps reviewers find most often
- Training records that cover permanent staff but miss locums, registrars and students.
- An asset register that lists computers but not phones, tablets, smartcard readers or cloud services.
- Administrator accounts belonging to people who have left, or shared admin logins.
- A privacy notice that does not mention the phone system, online consultation tool or text messaging.
- Supplier contracts with no data protection terms, often for smaller services such as translation or shredding.
- A business continuity plan that has never been tested.
- A breach log with no entries, which usually means incidents are not being recorded rather than not happening.
An empty breach log is a warning sign, not a success. Practices with good reporting cultures record near misses such as a letter caught before posting. That shows the system works.
Evidence that convinces a reviewer
Toolkit answers are increasingly checked by integrated care boards and, for some organisations, by independent auditors. A statement that says 'policy in place' is weak evidence. A dated document, a screenshot from a system or a minute from a meeting is strong evidence. Aim for proof that something happened, not just that something exists.
- Training: an export from the training system showing names, dates and completion, not a sentence saying staff are trained.
- Asset register: the register itself with a 'last reviewed' date and the reviewer's name.
- Administrator accounts: a list of admin accounts with the accountable person for each and the date it was checked.
- Continuity: the notes of a test or tabletop exercise, including what went wrong and what changed.
- Breaches: the log, with dates, assessments and decisions on reporting.
Store evidence in one shared folder organised by assertion number, and name files consistently. When the reviewer or next year's owner opens it, they should find everything without asking.
Unofficial tools and shadow IT
The asset register should include tools staff use without anyone formally approving them. A 2025 Nuffield Trust and RCGP survey found 11% of GPs used AI tools they had obtained independently, compared with 13% using tools provided by their practice[3]. Transcription apps, writing assistants and personal messaging apps used for work all process patient data and need to be either approved, assessed and listed, or stopped.
Ask staff directly, in a no-blame way, which apps they use to get through the day. The answers often reveal useful tools worth approving properly, as well as risks to close.
People and roles
The toolkit expects named people for key roles. The National Data Guardian's guidance asks organisations in scope to have a Caldicott Guardian, and organisations completing the toolkit provide the Guardian's details in their annual submission[4]. The Guardian applies the eight Caldicott Principles to decisions about using and sharing confidential information[5].
- Senior information risk owner: usually a partner, accountable for information risk.
- Caldicott Guardian: often a GP partner, advising on confidentiality and sharing decisions.
- Data protection officer: independent adviser, often a shared ICB service.
- Information governance lead: usually the practice manager, doing the day-to-day work and the submission.
Example: from June scramble to steady progress
Example (fictional): a 12,000-patient practice had submitted its toolkit in the last week of June for three years running, each time with the manager working evenings. For 2026-27 the manager split the work using the monthly plan above, asked the GP IT team for its evidence list in November and gave the deputy manager ownership of training records and the asset register.
By the end of March most evidence was uploaded. The April continuity exercise exposed one real gap: nobody knew where the paper appointment lists were kept for a system outage. The practice fixed it, recorded the exercise as evidence and submitted in May.
After submission
Publishing the toolkit is a checkpoint, not the end. Keep the action plan for any items you only partly met, review the breach log quarterly and put the next year's start date in the diary. Our guides to the Caldicott Guardian role and the Data (Use and Access) Act 2025 cover two areas that feed into several assertions, and the dental version of this guide explains the category 3 requirements.
Frequently asked questions
When is the 2026-27 Data Security and Protection Toolkit due?
The deadline is 30 June 2027[1].
Which category do GP practices complete?
GP practices use the category 4 assertions and evidence items; dental practices use category 3[1].
Do GP practices have to reach 'Standards Met'?
Yes. Integrated care boards expect all GP practices to complete the toolkit annually and achieve 'Standards Met'[2].
Does our GP IT provider complete parts of the toolkit for us?
It usually supplies statements and evidence for technical items. Ask your board's GP IT team for its list, then complete the items it does not cover.
References
NHS England (Data Security and Protection Toolkit) (2026). Data Security and Protection Toolkit 2026-27: assertions and evidence items (version 9) (opens in a new tab) ↑
NHS North East London (primary care) (2026). Data Security and Protection Toolkit 2025-26 update (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2021). National Data Guardian guidance on the appointment of Caldicott Guardians, their role and responsibilities (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2026). The Caldicott Principles (opens in a new tab) ↑