EU AI Act Delays Don’t Change Who Must Check AI Value

← Back · ACT I · Chapter 3: Value Drift

What the EU’s deferral, the enforcement that did arrive, and Bain’s reinvestment data say, together, about who actually governs value

August 2, 2026 was supposed to be the day the EU AI Act grew teeth. It was the binding compliance date for high-risk AI systems: the provider obligations in Articles 9 through 17, the deployer obligations in Article 26, the requirements that would have forced organizations to demonstrate risk management, data governance, human oversight, and post-market monitoring for the AI systems that matter most.

The date arrived. The teeth arrived with it, pointed somewhere else. On 29 June the Council of the EU gave final approval to the Digital Omnibus on AI, deferring the high-risk obligations to 2 December 2027 for stand-alone systems and 2 August 2028 for AI embedded in regulated products. The requirements that would force a vendor to prove fitness for the systems that matter most moved sixteen to twenty-four months down the calendar.

What did become enforceable on 2 August is real, and it is larger than the transparency layer alone. The prohibitions on unacceptable practices are live, carrying penalties up to 35 million euros or 7 percent of worldwide annual turnover. The obligations on providers of general-purpose AI models are live, at 15 million euros or 3 percent. The Article 50 duties that tell a user when content or a system is AI are live. The AI Office can now issue requests for information, run its own evaluations, require access to a model, and restrict a model’s availability, and three reporting channels opened alongside those powers: a complaint tool, a whistleblower tool, and a dedicated channel for downstream providers building on general-purpose models. Enforcement did not fail to arrive. It arrived aimed at the properties of the machine, and it left the question of whether the funded result appeared exactly where it already was.

Inside most organizations the response was predictable, and it is already under way. Compliance programs timed to the high-risk obligations are standing down. AI governance roadmaps are re-baselining to 2027. Budget owners are hearing some version of a reasonable-sounding sentence: the regulatory pressure moved, so the governance investment can move with it.

That sentence deserves scrutiny, because a second set of facts arrived this summer, and the two sets belong side by side.

The Value Didn’t Arrive

On 1 June, Bain and Company published its Automation and AI Pathfinder Survey of 951 global companies. The headline finding, in Bain’s own words: the technology worked, the value didn’t arrive. Thirty-seven percent targeted cost reductions of 11 to 20 percent. Nearly forty percent of the companies that measured their outcomes landed in the 0 to 10 percent bucket instead. That base is worth holding on to, because it is the argument in miniature. The shortfall is known only among the firms that went looking for it, and Bain reports nothing about what the rest achieved, because the rest do not know either.

The expectation gap is not the alarming part. Gaps between projection and outcome are the oldest story in enterprise investment. The alarming part is what organizations are doing about it.

Ninety percent of those same companies plan to increase their AI budgets anyway. And asked how they intend to fund the next wave of generative and agentic AI, forty-four percent named savings from prior automation programs, the largest single source named. Savings that, for a large share of them, have not materialized.

Read that mechanism closely, because it has a structure. Wave one is justified by projected savings. The savings are certified at approval and never verified afterward. Wave two is then funded by the projected savings of wave one, which exist in the business case and not in the income statement. Each wave’s foundation is the previous wave’s unaudited claim. This is not investment compounding. It is assumption compounding, and it is the mechanism by which nothing breaks while the outcome moves.

Two Calendars

Now put the two facts together. The regulatory calendar just told organizations that governance of the systems that matter most can wait until December 2027. The capital calendar says the opposite: the reinvestment loop is running now, this budget cycle, in the forty-four percent of companies committing next-wave capital against last-wave claims that no one has verified.

Organizations that anchor their governance to the regulatory calendar have made a quiet and consequential choice. They have decided that the trigger for knowing whether their AI investments produce value is an enforcement date in Brussels. When Brussels moves the date, the knowing moves with it.

But regulation was never the right anchor for value governance, and the deferral only makes the mismatch visible. The AI Act governs harms, transparency, and fundamental rights, and since 2 August it governs them with real penalties behind it. It is important work. It is also silent on the question that determines whether your AI portfolio was worth funding: did the value arrive? No regulator, on any timeline, on either continent, will ever ask whether the savings in your business case showed up in your income statement. That question belongs to exactly one party, and it is the buyer.

Governance on the Buyer’s Calendar

Buyer-side value governance runs on a different clock. It does not activate when an enforcement date arrives, and it does not stand down when one defers. It activates when capital is committed, because that is when the value promise is made, and it verifies on the cadence of delivery, because that is when the promise either becomes real or does not.

In practice, for the reinvestment loop Bain documented, this means something concrete. Before wave two funds, wave one gets verified against the baseline in its own business case. The verification is the projected number set beside the realized number, with the variance named and the cause assigned. If the savings materialized, wave two funds on evidence. If they did not, wave two’s business case gets rebuilt on what is actually true, and the organization learns something it can use for the next decade of AI spending. Either outcome beats funding the future on the unaudited claims of the past.

Bain reaches the first half of this on its own, and it is worth saying so rather than presenting the whole of it as new. Its recommendation to finance leaders is to audit the actual returns from prior automation programs rather than the projected ones, and to size the next investment against what the last one delivered. Where it stops is at the edge of the firm. That audit is an internal discipline, run by the buyer on the buyer’s own numbers, and Bain’s answer to the accountability question is to name a person who owns it. A named owner leaves when the person leaves. A standard published to the seller before the money moves does not, and it puts the burden of proof on the party that made the claim.

The organizations that do this will not notice the difference between August 2 and December 2027, because their governance was never waiting on either date. The organizations that re-baseline their governance to the new regulatory deadline have shown what their governance was for, and it was for the regulator rather than for the value.

The Instrument the Buyer Already Holds

What Bain measured has a name on the buyer’s side. Value drift is the gap between the value a seller promised and the value a buyer can prove it received, and Bain’s survey is that gap measured at scale: capability delivered as advertised, the double-digit efficiency of a decade of data investment still unbooked. The technology performing while the value fails to arrive is the exact signature of drift.

The correction has a name too, and it does not depend on any regulator. It is the Request for Value: the buyer sets the standard the seller must meet, naming the outcome to be proven, the evidence that counts as proof, and the point at which payment attaches to realized value rather than promised value. Where a savings claim was once accepted on assertion, the buyer-governed standard makes it a condition to be demonstrated. The information asymmetry that let sellers price on promise collapses the moment the buyer owns the standard of proof. August 2 does not create that instrument, and no deferral in Brussels disarms it.

Brussels can defer its deadline. Your capital cannot defer its verdict. Every quarter that passes converts the projected savings in the last business case into one of two things: realized value, or the foundation of the next unverified wave. A published buyer-side standard is what determines which one you get. That standard operates on your calendar, which is the one calendar no regulator sets.

This argument has been carried forward. Europe Lets AI Buyers Complain About Suppliers, With Evidence. takes up what the enforcement framework gave the buyer, and what it still does not require anyone to record.

Sources: Bain & Company, “Your AI Budget Is Growing. Your Returns Aren’t. Here’s Why.,” 1 June 2026, reporting the Automation and AI Pathfinder Survey 2026, n=951, bain.com. Council of the European Union, final adoption of the Digital Omnibus on AI, 29 June 2026, consilium.europa.eu.

Keep reading: ACT I · Chapter 3: Value Drift