Algorithmic Transparency: What Public Bodies Must Publish
The UK has mandated algorithmic transparency records across central government since February 2024. Most technology vendors selling into the public sector have not read the standard they will be asked to comply with.
If you sell algorithmic systems into government, there is a document you are more likely to be asked about than any contract clause: a public transparency record describing what your system does, on whom, and why. Most vendors find out about this requirement during procurement, which is later than it should be found out.
What is actually mandated
The UK's Algorithmic Transparency Recording Standard (ATRS) has been mandatory across central government departments since 6 February 2024. It applies to algorithmic tools that significantly influence a decision with public effect, or that interact directly with members of the public, once those tools reach pilot or production use. (GOV.UK)
The standard's own guidance states the expectation for suppliers directly, and it is worth quoting in full because it removes any ambiguity:
"Commercial suppliers that wish to sell algorithmic solutions to public bodies that are then used in processes that impact members of the public should be comfortable with this level of transparency that is expected of the public sector. Public bodies that are procuring solutions from vendors should make this expectation clear in their invitation to tender or other route to market."
There is no carve-out for "the algorithm is proprietary" or "the vendor doesn't disclose that." If a public body cannot get the information needed to complete a transparency record, that is a procurement problem the public body needs to solve before the contract is signed, not after.
What a record actually contains
An ATRS entry is structured, public, and specific. It typically describes what the tool does, what data it uses, how it was tested, what oversight exists, and what a person can do if they believe a decision affecting them was wrong. It is not a marketing description. It is closer to a technical and governance disclosure that a journalist, researcher or affected member of the public can read and act on.
This is a meaningfully higher bar than most commercial software vendors are used to operating under. A private company selling the same underlying technology to another private company faces no equivalent public disclosure requirement. Selling into government changes that.
Why this is not just a UK story
The same direction of travel is visible elsewhere, even where the specific mechanism differs.
The EU's AI Act (Regulation (EU) 2024/1689) reached general application on 2 August 2026. Its Annex III high-risk provisions — which cover many public-sector use cases including law enforcement, migration and access to essential services — were deferred by the AI Omnibus (Regulation (EU) 2026/1744) to 2 December 2027, but the direction is set: high-risk AI systems used by public authorities will carry documentation, logging and human-oversight obligations that are transparency requirements in substance, whatever they are called procedurally. (European Commission)
India's MeitY AI Governance Guidelines, released 5 November 2025, expect anyone developing or deploying AI systems in India — including suppliers to government — to publish transparency reports evaluating risk of harm in the Indian context, with sensitive material shared confidentially with regulators rather than publicly. (PIB backgrounder) The mechanism is different from ATRS. The underlying expectation — that a public-facing algorithmic decision should be explainable to someone outside the organisation that built it — is the same.
In the US, OMB's M-25-22 does not mandate a public record in the way ATRS does, but it requires that agencies retain the ability to evaluate vendor systems independently and disclose testing results internally, which serves a related function: nobody vending into a federal agency should assume their system's internals are permanently opaque to the buyer. (OMB M-25-22)
What this means if you build or buy
If you are a public body: put the ATRS expectation in the invitation to tender, not in a post-award conversation. A vendor who hesitates when the requirement is stated upfront has told you something useful about how the rest of the relationship will go.
If you are a vendor: build for disclosure from the start rather than retrofitting it. A system designed with logging, explainability and audit trails from day one produces a transparency record as a byproduct of good engineering. A system designed without them requires reverse-engineering documentation under deadline pressure, which is a worse experience for everyone and a slower path to being paid.
If you are evaluating a partner for a public sector project, ask directly whether they have supported an ATRS submission, or an equivalent, before. The answer tells you whether transparency is something they are prepared to operate inside or something they will discover mid-contract.
The trust question underneath it
Every regulatory mechanism above is trying to answer the same underlying question: can a person affected by an algorithmic decision find out enough about it to know whether it was fair. That is not a compliance exercise. It is the actual justification for public bodies using these systems at all, and a vendor that treats it as paperwork has misunderstood what it is being asked to provide.
If you are building or procuring an algorithmic system for public sector use and want the transparency requirements built in from the start rather than retrofitted, that is a conversation we are glad to have.
Kaizen Spark Tech designs and delivers software, AI, automation and digital infrastructure for businesses and institutions. Every statistic here is linked to its original published source. Regulatory dates in this article are accurate as of September 2026 and are reviewed quarterly, because several of the frameworks referenced are still moving.