- Start with an inventory. You cannot govern what you have not catalogued. Shadow AI is widespread, and vendor AI is often enabled by default in tools you already pay for.
- Classify tools by the data they process and the decisions they influence. A low-risk AI tool and a high-risk one need different controls.
- An AI acceptable use policy does one job: tell staff what they can use, what data they cannot enter, and what review is required before acting on AI outputs.
- Under UK GDPR, as amended by the Data (Use and Access) Act 2025 (Articles 22A to 22D, in force since 5 February 2026), solely automated decisions with legal or similarly significant effects on individuals need safeguards, and those based on special category data are more tightly restricted. HR screening tools, credit decisions and insurance pricing can fall into this. Having a person somewhere in the process does not on its own make a decision less than solely automated: the human involvement must be meaningful, by someone with the authority and information to change the outcome, and documented.
- Human oversight means a human who genuinely evaluates the AI output before a consequential decision is made. Rubber-stamping is not oversight.
- The EU AI Act can reach UK organisations, but having EU customers or employees does not on its own trigger every obligation. Article 2 looks at concrete tests: placing an AI system on the EU market, using it from an establishment in the EU, or the system's output being used in the EU. High-risk AI obligations apply from December 2027.
- ISO 42001 certification is not necessary for most UK SMEs unless a customer or contract requires it. Even without certification, it can be useful to adopt measures from the standard.
What AI governance actually is
AI governance is the combination of policies, controls, and accountability structures that determine how your organisation uses AI tools, which data those tools can access, how AI-influenced decisions are made and reviewed, and who is responsible when something goes wrong.
It is not an ethics statement, an AI strategy document, or a list of principles. Those are starting points for conversations, not controls. Governance means specific rules that apply to specific tools, specific accountability for specific decisions, and a review process that actually runs.
Many UK organisations at the start of 2026 have none of this. They have staff using ChatGPT, Copilot, Gemini, and a dozen SaaS tools with AI features enabled, with no policy, no training, and no visibility into what data is being processed. The governance gap is not theoretical: it is a UK GDPR exposure, a reputational risk, and, for organisations with EU operations, an EU AI Act compliance question.
Establish ownership first
Before inventorying tools or writing policy, decide who is accountable for AI governance. Without a named owner and clear decision rights, the inventory does not get maintained, the policy does not get enforced, and incidents do not get escalated. In most UK organisations the structure looks like this:
| Role | AI governance responsibility |
|---|---|
| Board / Executive | Set risk appetite for AI use. Receive quarterly reporting on AI risk posture. Approve high-risk AI use cases. |
| AI Governance Owner (IT lead, DPO, or vCISO) | Maintain the AI tool register. Approve or reject new tool requests. Coordinate DPIA completion. Own the acceptable use policy. Report incidents upward. Run the review cadence. |
| DPO / Privacy | Lead DPIA assessments. Advise on the automated decision-making rules (UK GDPR Articles 22A to 22D). Review vendor DPAs. Handle subject access requests involving AI. |
| IT / Security | Assess AI tool security controls. Manage access permissions for enterprise AI tools. Detect shadow AI. Monitor for data exfiltration. Handle AI-related security incidents. |
| Legal / Compliance | Review AI-related vendor contracts. Advise on sector-specific regulatory obligations. Track EU AI Act developments for relevant use cases. |
| Business / Department Owners | Own AI tool use cases within their function. Ensure staff follow the acceptable use policy. Escalate new AI tool requests through the formal approval process. Own human oversight within their workflows. |
| End Users | Follow the acceptable use policy. Use only approved tools. Report incidents and shadow AI use. Complete AI awareness training. |
In a smaller organisation, several of these roles will sit with the same person. That is fine. What matters is that the responsibilities are explicitly assigned, not that each has a dedicated headcount. A 50-person business with a named AI governance owner, a defined escalation path, and a quarterly review meeting has more functional governance than a large organisation with a governance framework document and no one running it.
The ten steps
Once someone owns AI governance, the work comes down to ten steps. We cover them in three companion guides.
AI inventory, risk classification and acceptable use policy covers steps 1 to 3: finding every AI tool in use, including the ones staff signed up for themselves, classifying each tool by the data it handles and the decisions it influences, and writing a policy staff can read in five minutes.
AI data protection, human oversight and security controls covers steps 4 to 6: your UK GDPR obligations, including the automated decision-making rules in Articles 22A to 22D and DPIAs, human review that changes the outcome, and controls for risks such as prompt injection and data leakage.
AI vendors, incidents, the EU AI Act and ISO 42001 covers steps 7 to 10: due diligence before you approve an AI tool, what counts as an AI incident and how to respond, when the EU AI Act reaches a UK organisation, and whether ISO 42001 is worth adopting.
Your first 90 days
Many organisations find that AI governance feels overwhelming in the abstract but manageable when broken into a sequenced 90-day programme. The goal at the end of 90 days is to be able to answer: what AI do we use, who owns it, what data does it process, what risks exist, and what controls are in place?
Governance cadence
AI governance is not a project with an end date. The tools change, vendor terms update, new capabilities emerge, and your organisation's use evolves. Build a review cadence that keeps the programme current without consuming disproportionate time.
Assign a named owner for AI governance, whether that is your DPO, IT lead, or a vCISO carrying the function. Without a named owner, the review cadence does not happen.
Minimum viable AI governance for SMEs
If your organisation does not have a dedicated compliance team, start here. These eight actions give you meaningful governance without requiring a large programme.
This guide covers ongoing governance: the register, the policy, the controls that apply across every AI tool in use. When you are ready to deliberately build AI into a specific process, from business case through pilot, testing, and a measured result, our AI Implementation Guide covers that project end to end. It assumes the governance foundation in this guide is already in place and builds on it.