Should You Wait for the Digital Omnibus? A Simple Decision Framework

Your friend at a startup says the AI Act got delayed. Your lawyer says it didn't. They're both sort of right.

Here's what's happening: In November 2025, the European Commission proposed something called the Digital Omnibus — an amendment that could push certain AI Act deadlines back by 16 months. That sounds like great news until you read the fine print.

Some obligations might get delayed. Others won't. And the proposal isn't even law yet.

So what should you actually do? Wait and hope, or prepare now? Let's break it down.

What the Digital Omnibus Actually Is

The Digital Omnibus is a proposed amendment to the AI Act. It's not a repeal, not a rewrite — just a proposed delay for specific types of obligations.

If it passes (and that's still an "if"), it would push the deadline for certain high-risk AI system requirements from August 2026 to December 2027. That's 16 extra months to get ready.

But here's the catch: the proposal was announced in November 2025. It hasn't been adopted yet. There's no firm timeline for when (or if) it'll become law. You're basically betting on regulatory process speed, which is like betting on good airport WiFi.

What Would Actually Get Delayed

If the Digital Omnibus becomes law, here's what gets pushed to December 2027:

Requirements for AI that makes important decisions about people (hiring, credit scoring, healthcare, education)
Readiness checks and conformity assessment deadlines
Heavy documentation requirements for high-risk systems
Third-party assessment obligations

That's a meaningful delay if you're building systems that fall into these categories. You'd get more than a year to shore up documentation, build review processes, and budget for assessments.

What Stays the Same No Matter What

Here's what the Digital Omnibus does NOT affect:

Transparency obligations (Article 50): If you've got a chatbot, a content generator, or anything that creates synthetic images or text, you need to disclose that to users. This deadline is still August 2, 2026. No delay. No exemption. No matter what happens with the Omnibus.

Prohibited practices: These have been in force since February 2025. If you're doing something the Act explicitly bans (like social scoring or manipulative AI), you needed to stop months ago.

The Digital Omnibus doesn't touch these. At all.

The Decision Framework

Alright, here's how to think through your timing:

If your systems are high-risk:

Monitor the Digital Omnibus proposal closely
Start documenting your systems now (that work won't be wasted)
Hold off on expensive third-party assessments until the proposal status is clearer
Budget for both scenarios: August 2026 and December 2027

If you have chatbots or generate synthetic content:

Act now regardless
Transparency obligations aren't affected by the Digital Omnibus
You've got until August 2, 2026 no matter what happens
This is the most common scenario for SMBs — and there's no ambiguity here

If you're unsure about your risk level:

Classify your systems first, then decide
This is the real work anyway
Most SMBs aren't running high-risk systems
But if you've got customer-facing AI, you probably have transparency obligations

Here's the truth: most companies in the 25-75 employee range should prepare for the August 2026 transparency deadline regardless of what happens with the Digital Omnibus. That's where the actual work is.

Why "Wait and See" Is the Worst Strategy

I get the temptation. Regulatory uncertainty is exhausting. Why spend time and money preparing for a deadline that might get pushed back?

Because here's what happens if you wait:

The proposal might not pass. Then you're scrambling in July 2026.
Even if it passes, transparency obligations still hit in August 2026. You've waited for nothing.
You lose the ability to prepare methodically. Rushed compliance work is expensive and brittle.
You signal to customers that you're reactive, not proactive. When they ask about AI Act readiness, "we're waiting to see if it gets delayed" is not a confidence-building answer.

The companies that'll come out ahead aren't the ones gaming the calendar. They're the ones who treat readiness as an operational improvement, not a regulatory checkbox.

What Smart Founders Are Doing Now

Here's the pattern I'm seeing from companies that aren't panicking:

They're classifying their AI systems. Not waiting for perfect clarity — just documenting what they've built and what role it plays. This work is useful regardless of deadlines.

They're tackling transparency obligations first. Chatbot disclosures, synthetic content labels — the stuff that's definitely happening in August 2026.

They're building documentation as they go. Not creating a "compliance project" in Q2 2026, but folding readiness work into their normal product development cycle.

They're making decisions with incomplete information. Because that's what running a company is.

The Bottom Line

Should you wait for the Digital Omnibus? No.

Should you ignore it? Also no.

The right move is to prepare for August 2026 transparency obligations now, monitor the Digital Omnibus proposal for high-risk timeline changes, and treat readiness as a continuous process rather than a one-time project.

If the deadline gets pushed back, great — you'll have more time to refine. If it doesn't, you're ready.

The worst outcome isn't preparing too early. It's being caught flat-footed because you bet on regulatory delay.

Use our decision flowchart to determine your readiness timeline. It'll walk you through your specific situation — what you're building, who's using it, and what obligations actually apply to you. No legal jargon, just a clear path forward.

This document supports readiness preparation. It does not constitute legal advice.