Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

EU AI Act for UK Companies: What Applies After Brexit

The EU AI Act reaches UK firms that sell into the EU. This guide covers territorial scope, provider vs deployer positions, representatives and UK-specific steps.

Renomira Team · 6 min read
City of London skyline viewed across the Thames
Photo: User:Colin and Kim Hansen / CC BY-SA 4.0 via Wikimedia Commons

Does the eu ai act apply to uk firms is now a standing agenda item for anyone selling software from London, Manchester or Edinburgh into the single market — and the honest answer is yes, more often than UK boards expect. The Regulation is territorial in effect, not in geography: uk business obligations under eu ai act attach when you place AI on the EU market or when your AI’s output affects people in the Union, regardless of where your office sits. This guide covers the territorial triggers, what post brexit uk ai act compliance actually requires of a UK provider or deployer, how the regime differs from the UK’s own path, and the steps that get a UK firm defensible without a Brussels entity.

When the Regulation bites a UK firm

The territorial scope provisions (Article 2) follow three scenarios:

  1. UK provider placing an AI system or GPAI model on the EU market. Selling to EU customers, offering a service accessible in the Union, or deploying your system’s output for users located in the EU — all count. Full provider obligations follow: classification, documentation, CE marking where high-risk, authorised representative where required.
  2. UK provider whose system’s output is used in the Union. The classic case: a UK-built screening tool licensed to a Dublin recruiter. You are the provider; the recruiter is the deployer. Both regimes apply, to different parties.
  3. UK firm as deployer of EU-provided or any AI affecting people in the EU. If your UK subsidiary uses an AI system to make decisions about persons located in the Union, deployer duties travel with it.

Explicitly out of scope: AI used for personal non-professional activities, and — importantly for some UK firms — systems already placed on the market before the transitional cut-offs. National-security uses fall to member states, not the Regulation. The UK’s geographic separation changes nothing: the trigger is market and effect, not postcode.

Provider or deployer: position a UK firm correctly

Most UK vendors ask “are we in?” when they should ask “which hat are we wearing?”:

  • Selling a tool EU customers configure for their own use: you are the provider of the system as placed on the market; your customer is the deployer. Your contract must say so — provider status determines who signs the declaration, holds the technical file and appoints the representative.
  • White-labelling an EU vendor’s system under your brand: you have re-placed it on the market under your name — provider status transfers to you even though you wrote nothing.
  • Using AI for your own EU-facing operations (a UK consultancy screening EU candidates): deployer duties — instructions followed, oversight assigned, logs kept — and your classification of the underlying tool decides whether they are heavy.

Two documents do most of the proving: the classification rationale with its article reference, and the contract clause allocating provider/deployer status. UK firms that keep both current answer 80% of procurement questionnaires without a meeting.

The authorised representative question

The recurring structural requirement for third-country providers: non-EU providers of high-risk AI systems must appoint an authorised representative in the Union before placing the system on the market (Article 22), and GPAI providers have an analogous duty (Article 54). A UK company with no EU establishment therefore needs an EU-established holder of a written mandate for in-scope systems — a law firm, consultancy or corporate services provider that can retain documentation and answer authorities.

Planning notes: appoint before first placement, not after an enterprise customer’s legal review; price it annually; and keep the mandate’s document list in sync with your versions. Note also that Northern Ireland’s position follows its own arrangements under the Windsor Framework for product legislation — if you trade there, take advice specific to your product family rather than assuming either GB or EU treatment automatically applies.

How the UK’s own path diverges

The UK has chosen not to copy the Regulation — the direction of travel is a principles-based, pro-innovation framework administered through existing regulators rather than a horizontal statute with CE marking. For a london firm eu ai act compliance means planning for both worlds:

  • Compliance burden: EU = obligations attached to specific uses and artefacts (documentation, marking, registration); UK = outcomes delivered through sectoral regulators’ existing powers, with lighter horizontal scaffolding.
  • Individual rights: EU combines AI Act rights (Articles 85–86) with GDPR; UK GDPR divergences are narrower than the statutory regime gap, so EU-facing products still need the EU rights architecture.
  • Enforcement: EU market surveillance authorities with turnover-based fines; UK regulators under their existing remits.
  • Practical consequence: build your programme to the EU standard and satisfy the UK by inheritance — dual-running two frameworks costs more than running the stricter one and mapping it across.
Dimension EU AI Act UK approach
Structure Horizontal regulation with use-based duties and CE marking Principles-based framework delivered by existing regulators
Provider duties Technical documentation, QMS, conformity assessment, declaration Sector guidance and regulator expectations, no CE analogue
Individual rights Articles 85–86 complaint and explanation rights plus GDPR UK GDPR rights; no direct equivalent of Arts. 85–86
Enforcement National market surveillance authorities, turnover-based fines Regulators within existing statutory remits
Compliance strategy for dual traders Build to the stricter standard Satisfied largely by mapping EU artefacts onto UK expectations

The territorial traps: trials, demos and free tiers

Three placements catch UK firms out. Free-tier availability: if EU customers can register and use your AI features from the EU without restriction, regulators read that as availability on the Union market — a self-service trial is a placement, not a courtesy. EU-hosted pilots: running a pilot with an EU customer, even unpaid, puts the system into service for a user in the Union; document the classification and roles before the pilot starts, not after it succeeds. Marketing claims: describing your tool as suitable for EU hiring, credit or education use declares an intended purpose in exactly the language Annex III keys on — your website can classify you inadvertently. Sweep the EU-facing surface — pricing pages, docs, trial flows — for purpose statements you never intended as regulatory commitments, and reconcile them with your register. The cheapest fix in this section is a sentence deleted from a landing page; the expensive one is discovering the sentence during a customer’s conformity review.

Procurement questions UK firms will get asked

EU customers and their assessors have converged on a short questionnaire for third-country vendors: who is your authorised representative and under what mandate? Which Annex or article is your classification based on — provide the rationale? Where is your EU declaration of conformity (if in scope)? Where is your technical documentation held and how quickly can it be produced? Which AI Act obligations have you already discharged, and what is your register entry for this system? Answer each with a document reference rather than prose. Two further questions are becoming standard in renewal cycles: how do you handle Article 50 disclosures for generated content in your product, and what is your incident-reporting route under Article 73 (if you are a provider of a system where it applies)? Assemble the answers as a standing response pack — ten pages, versioned — and the UK-selling-into-EU position stops being a per-deal scramble and becomes a one-email answer.

How to check your own position

Take your product list and mark every system that EU customers can buy or EU-based users can access. For each marked system: provider or deployer (one line), classification (Annex reference or “none, with rationale”), representative required yes/no, and contract clause confirming role allocation. If any marked system lacks all four answers, that is the work — starting with the classification, because everything else depends on it. Then check the mirror side: if you use AI to make decisions about people in the EU, confirm deployer instructions, oversight assignment and log retention exist for those tools. Finally, compare your UK obligations map against the EU one on a single page; wherever they diverge, decide now which standard you run to. Firms that decided once, deliberately, spend the next year executing; firms that decide case by case spend it negotiating with themselves.

Frequently asked questions

Does the EU AI Act apply to UK companies?

Yes, where the company places an AI system or GPAI model on the EU market, or where its system’s output is used in the Union. Territorial scope under Article 2 attaches to market presence and effect, not establishment — a UK SaaS firm selling an AI screening tool to an Irish customer is fully in scope as a provider, with classification, documentation and representative duties as applicable.

What must a UK business do to comply with the EU AI Act?

Classify each system you place on the market (Annex I product link or Annex III use, with written rationale), discharge the obligations that classification triggers — technical documentation and CE marking for high-risk providers, transparency duties across the board — appoint an EU authorised representative for in-scope high-risk and GPAI provision, and keep contracts clear on who is provider and who is deployer. Deployer-side duties apply separately where your own operations make decisions about people in the EU.

Do UK companies need an authorised representative in the EU?

Non-EU providers of high-risk AI systems do — Article 22 requires an EU-established authorised representative under a written mandate before placement on the market, and GPAI providers have an analogous duty under Article 54. A UK provider without EU establishment must therefore appoint one for in-scope systems: the representative retains documentation and answers authorities, while the provider keeps full responsibility for conformity.

Is the UK AI Act different from the EU AI Act?

There is no single UK statute equivalent. The UK path is principles-based and delivered through existing sectoral regulators rather than a horizontal regulation with CE marking and an EU-wide conformity regime. The practical approach for UK firms selling into the EU: build to the EU standard — it is the stricter regime — and map its artefacts onto UK regulatory expectations rather than running two programmes.

Will EU customers require proof of AI Act compliance from UK vendors?

Increasingly yes, particularly for tools touching people decisions, finance or regulated records. Expect questions on classification rationale, authorised representative details, declaration of conformity where applicable, and your incident-reporting route. Firms that keep a standing response pack — one versioned document answering the standard questionnaire with references — close these reviews in days instead of quarters.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

eu ai act for uk companiesuk business obligations under eu ai actpost brexit uk ai act compliancedoes the eu ai act apply to uk firmsuk company selling into eu ai actai act territorial scope uk providerslondon firm eu ai act complianceuk us ai regulation differences eu ai act

Keep reading