AI governance · Current to the Act as amended, June 2026

EU AI Act Readiness Assessment

The Digital Omnibus moved half the deadlines, and everyone heard delayed. The half that did not move lands on 2 August 2026: transparency duties for anyone whose chatbots, synthetic content or deepfakes touch the EU market. In four to six weeks we inventory every AI system you build, buy or embed, classify each against the Act as amended, and hand you a plan showing where each fix sits in your systems, in the order the dates require. From £18,000 + VAT, fixed after a scoping call.

The dates that stand

Transparency (Article 50)2 August 2026
AI content marking2 December 2026
Annex III high-risk2 December 2027
Embedded high-risk2 August 2028
Prohibitions have applied since February 2025 and general-purpose AI duties since August 2025. Penalties reach €35 million or 7% of global turnover for prohibited practices. The assessment runs from £18,000 + VAT, fixed after a scoping call.

Definition

What is an EU AI Act readiness assessment?

An EU AI Act readiness assessment inventories every AI system an organisation builds, buys or embeds, classifies each against the risk tiers of the Act as amended by the June 2026 Digital Omnibus, determines your role for each system, because providers, deployers, importers and distributors carry different obligations, and maps each system to the dates that stand. It ends in a plan showing where each fix sits in your architecture, in the order the deadlines require.

Intelance delivers it in four to six weeks from £18,000 + VAT, fixed by how many AI systems you run after a scoping call, with a board readout included. It is run by architects who place controls in real systems rather than in policy binders, and who reuse what GDPR already built rather than rebuilding it.

The Omnibus, adopted in June 2026, moved Annex III high-risk obligations to 2 December 2027 and embedded high-risk systems to 2 August 2028. It did not move Article 50: transparency duties land on 2 August 2026 and AI content marking follows on 2 December 2026. Our guide to the EU AI Act and ISO 42001 shows how they fit together, and the wider practice is described under AI governance consulting.

In practice, that means
01

The real deadlines and what they mean

What moved to 2027 and 2028, and what still lands on 2 August 2026.

02

Your role for each system

Provider, deployer, importer or distributor: obligations change with the answer.

03

Controls in architecture

Logging, oversight and documentation placed in real systems, GDPR work reused.

04

A dated and priced plan

Each fix located in your systems, in the order the dates require.

The questions

Six questions the assessment answers about every AI system you touch

The Act attaches obligations to systems, roles and dates. These six questions cover all three, and each card shows what you hold at the end.

01

What AI do we run?

Built, bought and embedded in the SaaS you already use: the inventory that includes what nobody registered when it arrived.

You getA register of every AI system you touch, owned and dated.
02

What tier is each system?

Prohibited, high-risk, transparency tier or minimal, against the Act as amended, including the new Article 5 prohibitions.

You getA defensible risk classification per system.
03

What role do we play?

Provider, deployer, importer or distributor, decided per system, because your obligations change with the answer.

You getRole determination that survives a regulator’s first question.
04

Which dates apply to us?

The post-Omnibus map: transparency on 2 August 2026, marking on 2 December 2026, Annex III on 2 December 2027, embedded on 2 August 2028.

You getYour systems against the dates that stand, never the headlines.
05

Where do controls sit?

Logging, human oversight, data governance and technical documentation placed in real systems, reusing what GDPR already built.

You getAn architecture view, so fixes land in systems rather than in binders.
06

What do we do first?

Transparency before marking before Annex III, sequenced against procurement cycles that quietly spend the time you think you have.

You getA priced roadmap in deadline order, ready for the board.

How it works

Four to six weeks to a dated and priced position

The assessment runs to a published rhythm and ends in front of your board.

Week 1

The inventory

Every AI system found: built, bought and embedded, from logs, licences and contracts rather than a survey.

Weeks 2 to 3

Classification and roles

Each system tiered against the Act as amended, and your role determined per system, because obligations follow the role.

Weeks 4 to 5

The obligation map

Every system mapped to the obligations and dates that apply to it, with the 2 August 2026 duties flagged first.

Week 6

Architecture and roadmap

Controls placed in real systems, GDPR work reused, and the fixes priced and sequenced in deadline order, with a board readout.

After

The standing function

The register handed to whoever keeps it alive: your team, the AI Governance Office or Risk-as-a-Service, only if the roadmap says so.

December 2027 sounds distant and is one procurement cycle away for any system needing architecture change. Waiting spends that cycle, which is why the roadmap is sequenced backwards from each date that stands.

The alternatives

This route against the alternatives

Three responses to the Act since the Omnibus. The difference is what happens on 2 August 2026.

Wait for 2027
The policy programme
Assess the systems
What it is
Relax until the Annex III date gets close, because everyone said delayed
Principles, policy and training, with nobody looking at the estate
Every system inventoried, classified and mapped to the dates that stand, from £18,000 + VAT
What it misses
The 2 August 2026 transparency duties that never moved
Which systems the obligations attach to
Built to miss nothing: the Act attaches to systems, and the work starts there
The clock
December 2027 is one procurement cycle away for anything needing architecture change
Runs on workshop time while the dates run on legal time
Sequenced backwards from each date that stands
Best for
Organisations with genuinely no EU exposure
Culture change alongside an assessment, never instead of one
Anyone who builds, buys or embeds AI touching the EU market
Wait for 2027
What it is

Relax until the Annex III date gets close, because everyone said delayed

What it misses

The 2 August 2026 transparency duties that never moved

The clock

December 2027 is one procurement cycle away for anything needing architecture change

Best for

Organisations with genuinely no EU exposure

The policy programme
What it is

Principles, policy and training, with nobody looking at the estate

What it misses

Which systems the obligations attach to

The clock

Runs on workshop time while the dates run on legal time

Best for

Culture change alongside an assessment, never instead of one

Assess the systems
What it is

Every system inventoried, classified and mapped to the dates that stand, from £18,000 + VAT

What it misses

Built to miss nothing: the Act attaches to systems, and the work starts there

The clock

Sequenced backwards from each date that stands

Best for

Anyone who builds, buys or embeds AI touching the EU market

Scope

What is covered and what is not

You get

01

The full inventory: every AI system built, bought or embedded, owned and dated.

02

A defensible classification and role per system, against the Act as amended.

03

The post-Omnibus obligation map: your systems against the dates that stand.

04

Controls placed in architecture, reusing what GDPR already built.

05

A priced roadmap in deadline order, with a board readout included.

This is not

×

A legal opinion. We map systems, roles, controls and dates. Where formal legal advice is needed, we say so and work beside your counsel.

×

A policy programme. The Act attaches obligations to systems, and an assessment that never opens the estate cannot find them.

×

A panic purchase. If your exposure is genuinely minimal, the report says so and the spend stops.

×

Frozen in time. The report is current to the Act as amended in June 2026, and re-tiering after future changes is what the standing function is for.

Why Intelance

The standards we hold ourselves to

01

Current to the Act as amended

The June 2026 Omnibus changed half the map. The assessment runs against what stands, and we say plainly which half moved and which did not.

02

Controls placed in architecture

Run by architects who put logging, oversight and documentation into real systems, and reuse what GDPR already built rather than rebuilding it.

03

Fixed after a scoping call

From £18,000 + VAT by how many AI systems you run, agreed in writing before day one.

04

The dates drive the sequence

The roadmap is ordered by deadline, because December 2027 is one procurement cycle away for anything needing architecture change.

05

Honest about exposure

If the Act barely touches you, the report says so. An assessment that can only ever find urgent work is a sales document.

Who delivers this

Every assessment is led by a senior architect and AI governance lead, end to end. Nothing is offshored and nothing is templated.

The leadA UK based senior architect and AI governance lead, accountable to you
The methodInventory, classification and roles, obligation map, architecture, roadmap
The standardsThe EU AI Act as amended, ISO/IEC 42001 practice in house, TOGAF licensed
After the assessmentThe Office and Risk-as-a-Service, only if the roadmap says so
The delivery record The registers behind every claim

Ready to talk?

Tell us what AI you build, buy or embed

Thirty minutes to sort your urgent from your important: what you run, where it touches the EU market and which of the dates that stand apply to you. If chatbots or synthetic content face customers, say so first. That clock reads 2 August 2026.

FAQs

The questions everyone is asking since the Omnibus

Did the EU AI Act get delayed?

Partially. The Digital Omnibus, adopted in June 2026, moved high-risk obligations for stand-alone Annex III systems to 2 December 2027 and for AI embedded in regulated products to 2 August 2028. It did not move the rest: prohibitions and AI literacy have applied since February 2025, general-purpose AI obligations since August 2025, Article 50 transparency duties land on 2 August 2026, and AI content marking follows on 2 December 2026.

What still applies on 2 August 2026?

Article 50 transparency: people must be told when they interact with an AI system, synthetic content must be identifiable, and deepfakes must be disclosed. If you run chatbots that talk to customers, generate content or publish AI media into the EU market, this date is yours regardless of what moved.

What is an EU AI Act readiness assessment?

A structured review that inventories every AI system you build, buy or embed, classifies each against the risk tiers of the Act as amended, determines your role per system, maps each to the obligations and dates that apply, and produces a priced plan showing where each fix sits in your architecture, in deadline order.

How much does an EU AI Act readiness assessment cost?

From £18,000 + VAT with Intelance, fixed by how many AI systems you run after a scoping call, over four to six weeks with a board readout included.

Does the EU AI Act apply to UK companies?

Frequently, yes. The Act applies where AI systems are placed on the EU market or their outputs are used in the EU, so UK organisations serving EU customers are commonly in scope regardless of where they are based. The assessment maps which of your systems that touches.

What is a high-risk AI system?

Broadly, systems in the Act’s Annex III categories, including recruitment and worker management, credit and insurance decisions, biometric identification, critical infrastructure, education and access to essential services, plus AI embedded in regulated products under Annex I. Since the Omnibus, stand-alone Annex III obligations apply from 2 December 2027 and embedded systems from 2 August 2028.

What roles does the Act define, and why do they matter?

Provider, deployer, importer and distributor, and the obligations differ sharply between them. Most organisations are deployers for most systems and providers for a few, sometimes accidentally, by fine-tuning or white-labelling. The assessment determines your role per system, because getting it wrong means preparing for the wrong duties.

What changed in the Act besides the dates?

The Omnibus made targeted amendments rather than a rewrite, including a new Article 5 prohibition covering AI-generated non-consensual intimate imagery and child sexual abuse material. Prohibited practices carry the highest penalties, up to €35 million or 7% of global turnover, and they have applied since February 2025.

What happens after the assessment?

The roadmap is executed in deadline order: your team, any supplier, or ours. The register needs an owner as the Act and its guidance keep moving, and that is the AI Governance Office or AI Risk-as-a-Service, taken only if the roadmap says so.