On July 24, 2026, the EU published Regulation (EU) 2026/1744, the Digital Omnibus on AI, and three days later it was in force. The headline: the AI Act's obligations for stand-alone high-risk systems moved from August 2, 2026 to December 2, 2027. Sixteen more months. For AI compliance, that time is real for half the work. For the other half, it's mostly an illusion.
Plenty of teams read the delay as breathing room. Read the regulation the way a builder reads a spec instead, and every obligation falls into one of two piles. Things you write. Things you build.
Two piles
The writing pile is big, and it's the part everyone pictures. Technical documentation. Instructions for use. A declaration of conformity. Registration. Quality management procedures. It's tedious and it costs real money. But it compresses. Put more people on it, buy a template, hire a firm, and a document that would take a quarter takes a month. The final text even reportedly simplified some self-assessment documentation. Paperwork is expensive. It isn't hard.
The building pile is different in kind. Take record-keeping. Article 12 says a high-risk system has to technically allow the automatic recording of events over its lifetime. Lifetime. Not from the day your compliance program started. A log you didn't write in 2026 doesn't exist in 2027, and no firm can bill its way into creating it.
Or human oversight. Article 14 wants the system built so the person overseeing it can understand its limits, stay alert to automation bias, override an output, and interrupt the system with a stop button or something like it. That's not a paragraph in a manual. It's a property of the architecture. A stop that brings an agent to a safe state halfway through a multi-step action has to be designed, built, and tested. You don't draft it.
Or accuracy. The provider has to declare the system's accuracy levels. Declaring a number is easy. Having a number you can defend means ground truth, a measurement pipeline, and a history of results. That history takes time to pile up, whatever the deadline says.
The AI compliance test: could you produce it after the fact?
Here's the test I'd use, and it's sharper than hard versus easy. Ask of each obligation: could we produce this after the fact? A document describing your system can be written the week before an audit. Logs, accuracy measured over time, an oversight path people have actually used, a stop that's been tested: none of those can be backfilled. If the answer is no, it's a build item, no matter how much the regulation's wording makes it sound like paperwork.
This is where I think the delay will quietly hurt people. Paperwork is visible. A binder is a deliverable you can show a board. Build work is invisible until it's done, and it competes with the product roadmap. Give an organization sixteen months and a choice between the two, and a lot of them will polish the binder.
That's worse than it sounds, because a document is a claim. The FTC's 2023 case against Rite Aid shows how. According to the FTC, Rite Aid required store employees to report bad facial recognition matches, then did nothing to make sure they did, and never put in place a way to track how often the system was wrong. The rule existed. The instrumentation didn't. The settlement banned the company from using facial recognition for surveillance for five years. Different law, different country, same lesson. A policy with nothing measuring it isn't oversight. It's a written promise nobody can check.
So do the sort. Take your obligation list and put every line in one of two columns: can be written later, must be built now. Start the build column this quarter, because its lead time is set by architecture and by how long data takes to accumulate, not by the calendar in Brussels. Let the writing column wait. That's the part the delay actually helps.
One caveat, because it matters. Whether your system counts as high-risk at all is a legal question, and it's worth getting counsel on it. The sort is a builder's question. You can answer it this week.
The delay moved the deadline for the paperwork. It didn't move the deadline for the logs you never wrote.