Something important has changed quietly over the last two years: being open about the algorithms behind public decisions has gone from good practice to a published, mandatory requirement. If you build or buy AI for a regulated environment, “explainable” is no longer a reassuring word on a slide - it is something you may have to write down and publish. This guide explains, in plain English, what algorithmic transparency is, what the rules now require, and what it means for the AI you are planning to deploy.

Key takeaways

Algorithmic transparency means being open about how, where and why algorithmic tools are used in decisions.

In the UK, recording these tools via the Algorithmic Transparency Recording Standard (ATRS) is mandatory for central government and many public bodies.

Scope is widening, not shrinking - published records passed 125 in 2026, with devolved nations moving to adopt it.

For suppliers, “explainable and recordable” is now effectively a procurement requirement.

What is algorithmic transparency?

Algorithmic transparency means being open about how algorithmic tools support decisions - providing clear, accessible information about what a tool does, why it is used, the data behind it, and how humans oversee it.

The principle is simple: when a tool helps decide something that affects a person - a benefit, a referral, a risk rating - the public has a right to understand that it is being used and on what basis. Transparency is how organisations earn the trust to use AI at all, and how they stay accountable when a decision is later questioned.

What is the Algorithmic Transparency Recording Standard (ATRS)?

The ATRS is the UK government’s standardised way of doing exactly that. It is a template and process for publishing a clear record of each algorithmic tool an organisation uses - what it does, why, how it works, what data it draws on, and how it is governed. First introduced in 2021 and refined through public engagement and piloting, it gives every department a common format, so transparency is consistent and comparable rather than ad hoc. Think of it as a public register of the AI and algorithms shaping public services.

Is ATRS mandatory and who does it apply to?

Yes. Recording in-scope tools via the ATRS became mandatory across UK central government in 2024, and the requirement now extends across departments and many arm’s-length bodies. In practice it applies to:

All central government departments;

Arm’s-length bodies that deliver public or frontline services, or interact directly with the public;

Algorithmic tools that significantly influence a decision with public effect, or interact directly with the public.

The momentum is upward. Published records passed 125 during 2026 with more in progress - up from around 60 a year earlier - and the standard is being extended towards the wider public sector. This is a requirement that is growing in reach, not winding down.

What does an ATRS record actually contain?

Each record is designed to give a clear, non-technical picture of a tool. Typically it covers:

The tool’s purpose and the decision it supports;

How it works, described in plain terms;

The data it uses;

How humans stay involved and retain oversight;

The risks identified and how they are mitigated;

Who owns and governs the tool.

The aim is not to expose proprietary detail, but to make the use of the tool understandable to a non-specialist - a member of the public, a journalist, or an auditor.

Why did algorithmic transparency become mandatory?

The push for mandatory recording did not come from nowhere. High-profile failures of opaque automation - systems that made consequential decisions about people at scale, with too little human review and no public visibility - caused real harm and eroded trust. Transparency is the corrective: if the use of a tool is recorded openly, it can be scrutinised, questioned and challenged before harm spreads. The mandate reflects a simple lesson: in public services, the legitimacy of an algorithm depends not only on whether it works, but on whether people can see how and why it is used. That is why recording is now a default expectation rather than a voluntary gesture.

Algorithmic transparency vs explainable AI: what is the difference?

They are related but not the same. Explainable AI is a technical property - the ability to show how a model reached a specific output. Algorithmic transparency is broader and more organisational: it is about openly communicating that a tool is used, why, and under what governance. You can have an explainable model and still fail at transparency if you never tell anyone you are using it. Recording standards like the ATRS sit at the transparency end - they are about disclosure and accountability, not just technical interpretability.

What it means for your AI roadmap

If you are planning AI in a regulated environment, three implications follow directly:

Transparency must be designed in, not retrofitted. A tool whose decision logic cannot be explained or documented is a tool you cannot record - and, increasingly, cannot deploy.

Suppliers must provide recordable information. If a vendor cannot tell you clearly how their tool works and what it does, you cannot complete a record for it. That is now a practical procurement filter.

Explainability is a deliverable, not a slogan. Immutable audit trails, documented decision logic, bias monitoring and a genuine human-in-the-loop are what make a record possible - and credible.

The organisations that move fastest will be the ones treating these as design requirements from day one, rather than scrambling to reverse-engineer a record after a tool is already live. Building for transparency early is almost always cheaper than retrofitting it under scrutiny.

How to prepare: a short checklist

Five questions to ask before committing to any algorithmic tool:

Can we clearly document what this tool does and why?

Can we explain, in plain terms, how it reaches its outputs?

Is there meaningful human oversight of every consequential decision?

Can our supplier provide the information we need to complete a record?

Who owns the transparency record, and who keeps it current?

If you cannot answer these comfortably, you are not ready to publish a record - and probably not ready to deploy the tool.

Planning AI that has to be transparent, recordable and accountable? Talk to our team about governed, human-in-the-loop AI - or read our guides to sovereign AI and grounded, source-attributed summarisation.

‍