Many compliance teams rely on press coverage as an informal early-warning system for the EU AI Act. Someone reads trade newsletters, another forwards leaked drafts, and the legal lead decides if it changes the roadmap. Journalism has become a de facto regulatory intelligence feed. It's time to reconsider this approach.
The Conventional Wisdom
The belief is that the AI Act is complex, enforcement guidance is slow, and reporters in Brussels know where things are heading. Leaked documents can reveal policy directions before formal texts do. By tracking coverage closely, you can anticipate obligations, budget early, and avoid surprises.
There's logic here. EU tech policy often involves leaked material shaping the conversation. Reporters like Maximilian Henning, who covers AI policy, focus on surfacing information not yet public. For compliance officers, a well-sourced scoop can signal the start of a debate.
Why It's Incomplete
The issue is what you do with that signal.
A leak shows what one party wanted at one moment. It's not law, guidance, or an enforcement position. For example, a national government's proposal to embed safety teams inside frontier companies is a negotiating position, not a final decision. It shows the idea exists but doesn't confirm its survival, form, or timeline.
Press coverage also has structural blind spots affecting your exposure. Reporting focuses on news value: novel facts, powerful companies, and political fights. Henning notes that member-state enforcement often escapes scrutiny, and prohibited AI practices are overlooked. These are the areas where a multinational's obligations are decided. If your radar is built on reported news, you're under-informed about where enforcement will actually happen.
There's also an audience problem. Specialized newsletters have replaced broad public coverage, meaning stories reach policy professionals but not a wider audience. Your sense of "what everyone is saying" might just reflect your peer group's reading.
The Evidence
Consider what the EU AI Act actually makes binding. Your obligations come from the regulation's text, annexes, delegated and implementing acts, harmonized standards, and formal Commission guidance. Technical Documentation (Annex IV), risk management for high-risk systems, and Post-Market Monitoring are defined in instruments you can read and cite. None were created by a news story.
Enforcement is structured through national competent authorities in each member state, with Commission oversight of General-Purpose AI Models. This setup means the compliance landscape is uneven by design. A multinational can face different supervisory styles, resourcing levels, and priorities depending on where a system is deployed. Reporting in Brussels trade circles often misses this unevenness because national stories are expensive and often not pursued.
Then there's the reputational channel, where journalism does matter. Leaked documents and Commission inquiries into frontier developers show that scrutiny can start outside formal proceedings. A story can precede an inquiry, and an inquiry can follow a story. That's a risk to manage, but it's about how your organization looks under scrutiny, not a substitute for knowing what the law requires.
What to Do Instead
Separate three things your team currently blends together.
Obligations Intelligence. Source this from primary instruments only: the regulation text, official Commission publications, standards bodies, and national authority notices. Assign an owner and a review schedule. Press coverage can prompt a look, but nothing enters your obligations register until it's traced to a primary source.
Policy-Direction Monitoring. Treat leaks and non-papers as hypotheses. Log each one with its origin, the party it benefits, and what must happen for it to become binding. Tag it "watch" until formal text appears. Don't let it drive spending.
Exposure Testing. Ask the questions journalists would ask. If a reporter obtained your internal documents tomorrow, would your AI Management System records, Validation Evidence, and incident handling hold up? Run this as a tabletop exercise. Aligning to ISO/IEC 42001 gives you a documented system whose gaps are easier to see before someone else does.
Add one more discipline: map your deployment footprint by member state and track the national authority for each. That's the coverage gap the press can't fill for you.
When the Conventional Wisdom Is Right
Don't swing too far. Following the reporting is worthwhile, and ignoring it would be a mistake.
If you're a small team without a dedicated policy function, a good Brussels newsletter is an efficient way to learn that a debate is underway. When leaks and inquiries involve companies in your supply chain, such as a model provider you depend on, the coverage is early notice of downstream risk you'd otherwise miss. And because scrutiny can begin informally, being aware of what's being reported about your sector helps you prepare your communications and escalation paths.
The distinction is between awareness and authority. Press coverage is a good way to find out where to look. It's a poor basis for deciding what you owe. Use journalists as your smoke detector, not your fire code.
