United Kingdom - AI Playbook

Artificial Intelligence Playbook for the UK Government

United Kingdom

RAI-GB-NA-AIPUGXX-2025
Effective: 10 Feb 2025
Possible change, not yet verified. An automated check on 7 Sep 2026 suggested, without a source we could confirm, that this instrument may now be In Force. No official page confirming it could be found. The status shown is the last verified. If you know this instrument, use “Report an issue” to confirm or correct it.
In Force (Amended)(In Force (Amended))As published at gov.uk · checked 9 Sep 2026

United Kingdom - AI Playbook is In Force (Amended) in United Kingdom as of 9 Sep 2026, according to gov.uk.

GuidelineGovernance and OversightRisk ManagementAccountability and Documentation
Export PDF

The AI Playbook for the UK Government is official cross‑government guidance published by the Government Digital Service on 10 February 2025 that replaces and expands the Generative AI Framework for HMG. It sets 10 principles, practical controls, procurement and assurance guidance to help central government and in‑scope public bodies select, buy, deploy and govern AI systems safely, securely and ethically.

Summary

The Artificial Intelligence Playbook for the UK Government (published 10 February 2025 by the Government Digital Service) is a consolidated, practical guidance document intended to support civil servants and public sector organisations in the safe, secure and responsible adoption of artificial intelligence. Building on the earlier Generative AI Framework for HMG (January 2024) and aligned with the government’s broader AI policy agenda (including the AI Opportunities Action Plan), the Playbook expands coverage beyond generative AI to a broader set of AI technologies and use cases. It defines ten core principles (including understanding AI and its limits, lawful and ethical use, security, meaningful human control, lifecycle management, appropriate tool selection, collaboration, commercial engagement, skills and assurance) and translates those principles into actionable steps for teams across the AI lifecycle: from problem definition and user research through procurement, development, testing, deployment, monitoring and decommissioning.

The document emphasises risk‑based decision making, proportionality and the need for cross‑functional governance and assurance. It instructs teams to: conduct user research and inclusive design to mitigate harms; apply data protection and privacy-by-design practices consistent with the UK GDPR and the Information Commissioner’s Office (ICO) guidance; follow government cyber security standards and Secure by Design principles (including relevant NCSC guidance) to protect models and data; and to use documentation artefacts such as model and data cards, risk registers, and the Algorithmic Transparency Recording Standard (ATRS) when algorithmic systems are used in decisions affecting the public. The Playbook also provides procurement and commercial considerations for working with suppliers, including contractual requirements and testing expectations, and integrates assurance checkpoints and recommended governance structures (project boards, AI review boards, escalation paths).

The Playbook is explicitly practical: it contains primers on AI fields, case studies from public sector projects, templates and links to learning resources and assurance tools. It clarifies that while it is guidance rather than legislation, failure to follow its safeguards can expose departments to legal, regulatory and operational risks (including ICO enforcement for data protection breaches, security incident consequences, contractual liabilities and reputational harm). It also sets expectations for transparency and public communication, directing central government departments and certain arm’s length bodies in scope to use the ATRS to document algorithmic tools used in decision‑making. The Playbook aligns UK public sector practice with international guidance and the government’s pro‑innovation regulatory approach, while calling for proportionality and continuous iteration as AI capabilities evolve. The primary published text and supporting assets (PDF, HTML, posters) are hosted on GOV.UK and remain the authoritative sources for the Playbook’s content.

Full article

Read full text ↗

Overview

The "Artificial Intelligence Playbook for the UK Government" (published 10 February 2025) is a cross‑government practical guidance package produced by the Government Digital Service to help civil servants and public sector organisations use AI systems safely, ethically and securely. The Playbook supersedes and expands the earlier Generative AI Framework for HMG (January 2024), and sits alongside the wider policy work such as the AI Opportunities Action Plan (Jan 2025). It sets out 10 core principles, offers lifecycle‑based operational guidance (including procurement and assurance), and provides templates, case studies and links to further technical and ethical resources. The Playbook is intended as a living resource: departments are encouraged to reuse materials, contribute case studies, and update internal processes in line with the guidance.

Definitions

The Playbook adopts internationally‑recognised definitions of AI (consistent with OECD and UK Government usage): an AI system is a machine‑based system that, for explicit or implicit objectives, infers from inputs how to generate outputs (predictions, content, recommendations or decisions) that can influence physical or virtual environments. The Playbook distinguishes fields such as machine learning, deep learning, generative models, symbolic AI and hybrid approaches; it clarifies terms including "model", "training data", "inference", "hallucination", "prompt injection", "data poisoning" and "meaningful human control." These definitions underpin lifecycle guidance and risk assessments throughout the Playbook.

Governance and Institutional Framework

The Playbook prescribes a layered governance approach: project‑level governance (clear project leads, multi‑disciplinary teams, security and legal owners), programme‑level assurance (AI review boards or programme boards with escalation routes), and departmental oversight (senior responsible owner and alignment with existing departmental governance). It references existing central standards and assurance functions (for example, the Government Digital Service, the Department for Science, Innovation and Technology (DSIT), the Cabinet Office, and assurance teams across departments). For transparency it instructs central departments and certain arm's length bodies in scope to record algorithmic tools in the Algorithmic Transparency Recording Standard (ATRS) and to publish appropriate public‑facing information. The Playbook also recommends establishing documented review gates (design, security testing, privacy impact assessment, pre‑deployment review) and re‑assessment schedules during operation to manage model drift, performance regression and emergent harms.

Key Focus Areas

The Playbook concentrates on these operational domains: risk management (systematic risk registers and harm matrices across safety, privacy, fairness, security, environmental impact and societal wellbeing); procurement and supplier management (assuring model provenance, rights to data and IP, supply chain security and contractual warranties); data governance (data minimisation, retention, anonymisation, bias analysis and logging for auditability); security (adversarial threats, prompt injection, data exfiltration and model theft; aligns with Secure by Design and the Government Cyber Security Strategy); human factors and meaningful human control (clear role definitions, escalation, human‑in‑the‑loop procedures and fail‑safe designs); testing and evaluation (dataset holdouts, red‑teaming, penetration and adversarial tests, user acceptance and accessibility testing); transparency and public engagement (public notices, ATRS entries, explanation approaches and user research); and workforce capability (training, cross‑functional staffing and centres of excellence). The Playbook also stresses environmental sustainability considerations for compute and model selection, recommending proportionality in compute‑intensive choices where alternatives exist.

Implementation Framework

The Playbook provides a staged implementation pathway: stage 0 (problem definition and user research), stage 1 (feasibility and ethics review), stage 2 (procurement and supplier due diligence), stage 3 (development, testing and security validation), stage 4 (deployment with monitoring and incident plans), and stage 5 (decommissioning and knowledge capture). For each stage the Playbook presents recommended artefacts (business case, AI risk assessment, privacy impact assessment, model card, test reports, ATRS entry) and assurance gates. It offers procurement‑specific advice including recommended contract clauses, model provenance requirements, data handling and audit rights, and guidance on when to favour in‑house development versus vetted suppliers. The Playbook also encourages departments to reuse multi‑government components and share infrastructure through cross‑government arrangements to reduce duplicated risk and increase consistency.

Monitoring and Evaluation

The Playbook instructs continuous monitoring for performance, fairness, safety and security: maintain monitoring dashboards, drift detection, logging for reproducibility, periodic re‑validation and triggered re‑assessment for incidents. It encourages teams to implement automated and manual monitoring streams, to collect user feedback, and to report significant adverse incidents via internal incident processes and to relevant external regulators when required (for example ICO for data breaches). The Playbook also urges central collation of lessons learned and regular updates to the Playbook based on operational experiences, evolving threat landscapes and new legal or technical guidance.

Penalties, Liability, and Appeals

As guidance, the Playbook does not itself create statutory penalties, but it clarifies regulatory and legal exposures for non‑compliance with statutory duties (notably data protection obligations under the UK GDPR and the Data Protection Act 2018). Departments are warned that failures can lead to ICO enforcement actions (including fines and corrective orders), contractual remedies and supplier liabilities, internal disciplinary and governance consequences, operational shutdowns, and reputational damage. The Playbook advises establishing clear internal escalation and appeals processes where decisions are contested, and documenting rationale to support legal defensibility of algorithmic decisions.

Relationship to Other Instruments

The Playbook situates itself alongside and references multiple instruments: it expands the earlier Generative AI Framework for HMG (now superseded), maps to the AI Opportunities Action Plan, aligns with the Government Cyber Security Strategy and Secure by Design principles, and points to ICO materials (including AI auditing guidance) and co‑produced explainability guidance from The Alan Turing Institute and the ICO. The Playbook recommends that departmental policies (security, procurement, ethics and privacy) be updated to incorporate its practice recommendations.

International Alignment

The Playbook references international definitions and good practice (OECD AI Principles, co‑operation forums) and encourages alignment with cross‑jurisdictional standards to maintain interoperability with allies and suppliers. It recognises the evolving international regulatory landscape and instructs teams to consider export controls, data transfer rules and global supply chain risks. The Playbook is framed to be compatible with proposed domestic regulatory approaches (the UK’s pro‑innovation regulatory white paper) while aiming to keep public sector practice interoperable with international norms.

Implementation Timeline

MilestoneDateNotes
Publication of Playbook2025-02-10Official GOV.UK publication by Government Digital Service
Departments adopt internal processes2025 Q2-Q4Suggested period for departmental policy alignment and initial training
First annual review / update2026-02-10Playbook published as living document; review based on operational lessons

Sources and References

SourceType
AI Playbook for the UK Government (GOV.UK)Primary Source
Generative AI Framework for HMG (Jan 2024)Primary Source
AI Opportunities Action Plan (Jan 2025)Primary Source

Requirements for a company

What an organisation has to do under United Kingdom - AI Playbook, at a glance. Not legal advice — the table below gives the provision and deadline for each item.

Must do

11
  • Report significant adverse incidents to internal processes and external regulators when required.Civil servants and public sector organisations using AI systems.
  • Implement data minimisation, retention, anonymisation, and bias analysis for AI data.Civil servants and public sector organisations using AI systems.
  • Record algorithmic tools in the Algorithmic Transparency Recording Standard (ATRS).Central departments and certain arm's length bodies in scope.
  • Publish appropriate public-facing information about algorithmic tools.Central departments and certain arm's length bodies in scope.
  • Maintain systematic risk registers and harm matrices for AI systems.Civil servants and public sector organisations using AI systems.
  • Implement continuous monitoring for AI system performance, fairness, safety, and security.Civil servants and public sector organisations using AI systems.
  • +5 more in the table below

Must not do

0

Nothing in this category.

Should do

2
  • Establish documented review gates for AI system design, testing, and deployment.Civil servants and public sector organisations using AI systems.
  • Update departmental policies (security, procurement, ethics, privacy) to incorporate Playbook recommendations.Civil servants and public sector organisations using AI systems.

Should not do

0

Nothing in this category.

Who must do what

The obligations under United Kingdom - AI Playbook, most serious first. Not legal advice — verify against the official text before relying on it.

#WhoRequirementBy whenWhereSeverity
1Civil servants and public sector organisations using AI systems.Report significant adverse incidents to internal processes and external regulators when required.
“...and to report significant adverse incidents via internal incident processes and to relevant external regulators when required (for example ICO for data breaches).”
—Monitoring and EvaluationCritical
2Civil servants and public sector organisations using AI systems.Implement data minimisation, retention, anonymisation, and bias analysis for AI data.
“data governance (data minimisation, retention, anonymisation, bias analysis and logging for auditability)”
—Key Focus AreasCritical
3Central departments and certain arm's length bodies in scope.Record algorithmic tools in the Algorithmic Transparency Recording Standard (ATRS).
“For transparency it instructs central departments and certain arm's length bodies in scope to record algorithmic tools in the Algorithmic Transparency Recording Standard (ATRS)...”
—Governance and Institutional FrameworkImportant
4Central departments and certain arm's length bodies in scope.Publish appropriate public-facing information about algorithmic tools.
“...and to publish appropriate public‑facing information.”
—Governance and Institutional FrameworkImportant
5Civil servants and public sector organisations using AI systems.Maintain systematic risk registers and harm matrices for AI systems.
“risk management (systematic risk registers and harm matrices across safety, privacy, fairness, security, environmental impact and societal wellbeing)”
—Key Focus AreasImportant
6Civil servants and public sector organisations using AI systems.Implement continuous monitoring for AI system performance, fairness, safety, and security.
“The Playbook instructs continuous monitoring for performance, fairness, safety and security: maintain monitoring dashboards, drift detection, logging for reproducibility...”
—Monitoring and EvaluationImportant
7Civil servants and public sector organisations using AI systems.Conduct comprehensive testing, including red-teaming and adversarial tests, for AI systems.
“testing and evaluation (dataset holdouts, red‑teaming, penetration and adversarial tests, user acceptance and accessibility testing)”
Before deploymentKey Focus AreasImportant
8Civil servants and public sector organisations procuring AI systems.Assure model provenance, data rights, IP, and supply chain security in procurement.
“procurement and supplier management (assuring model provenance, rights to data and IP, supply chain security and contractual warranties)”
Before placing on marketKey Focus AreasImportant
9Civil servants and public sector organisations using AI systems.Align AI system security with Secure by Design and Cyber Security Strategy principles.
“security (adversarial threats, prompt injection, data exfiltration and model theft; aligns with Secure by Design and the Government Cyber Security Strategy)”
—Key Focus AreasImportant
10Civil servants and public sector organisations using AI systems.Consider export controls, data transfer rules, and global supply chain risks for AI systems.
“...and instructs teams to consider export controls, data transfer rules and global supply chain risks.”
—International AlignmentImportant
11Civil servants and public sector organisations using AI systems.Document rationale to support legal defensibility of algorithmic decisions.
“...and documenting rationale to support legal defensibility of algorithmic decisions.”
—Penalties, Liability, and AppealsImportant
12Civil servants and public sector organisations using AI systems.Establish documented review gates for AI system design, testing, and deployment.
“The Playbook also recommends establishing documented review gates (design, security testing, privacy impact assessment, pre‑deployment review)...”
—Governance and Institutional FrameworkRecommended
13Civil servants and public sector organisations using AI systems.Update departmental policies (security, procurement, ethics, privacy) to incorporate Playbook recommendations.
“The Playbook recommends that departmental policies (security, procurement, ethics and privacy) be updated to incorporate its practice recommendations.”
Dec 31, 2025Relationship to Other InstrumentsRecommended

© Regulations.AI · updated on 20 Sep 2026 · reviewed against official sources on 9 Sep 2026