After the Omnibus

When a major deadline slips, the instinct in every compliance team is the same: exhale, deprioritise, move on to the fire that is still burning. The Digital Omnibus discussion around the AI Act’s high-risk timelines has produced exactly that exhale. I want to argue against it — not because the delay is unreal, but because of where it moves the pressure rather than removing it.

A note on what follows. The legislative picture here is moving, and the specifics are worth verifying against the current text rather than taking on my word. What I am confident about is the shape of the consequence, which holds regardless of the exact dates.

A delay changes the order, not the existence

The high-risk provisions were always the loudest part of the Act — the part with the heaviest documentation, the conformity machinery, the registration. Pushing their hard deadlines out buys time on the most expensive obligations. That is genuine relief for the organisations those provisions target.

But the Act is not only its high-risk tier. A set of obligations is already live and does not move with the headline deadline: the requirement for AI literacy within organisations deploying these systems; the rules governing general-purpose AI models; and the Article 50 transparency duties — telling people when they are interacting with a machine, labelling synthetic content, and the rest. When the expensive, distant obligation slips, attention does not vanish. It flows to the obligations that are already here.

The redistribution of pressure

Think of regulatory attention as a fluid with a fixed volume. A delay does not drain the tank; it changes which compartment fills. Three shifts follow from this one.

First, enforcement attention concentrates on what is live. A regulator with a mandate and a delayed flagship provision will look for the obligations it can act on now. Literacy and transparency are unglamorous, but they are present-tense, and present-tense is enforceable.

Second, buyer behaviour does not wait for legislators. Procurement teams asking AI questions are not parsing the precise status of the high-risk timeline. They are managing perceived risk, and perceived risk does not reset when a deadline moves. The questionnaires keep coming.

Third, the delay rewards the prepared and punishes the complacent. The organisations that treat the extra time as runway — getting their documentation honest, their literacy real, their transparency genuine — convert a slip into an advantage. The ones that treat it as permission to stop will meet the same wall later, with less time and a regulator that has spent the interval sharpening its focus on exactly the things they ignored.

What I would do with the time

Not relax. I would use a delay to do the unglamorous things properly: build the internal literacy that the live rules already require, get transparency obligations genuinely met rather than nominally checked, and treat the breathing room as the rarest thing in compliance — a chance to do the work before it is urgent.

A reprieve is when the obligation goes away. This is not that. This is the same obligation, rescheduled, with the live parts pulled forward in everyone’s field of view. The exhale is understandable. It is also a mistake.