The AI Act's longer runway is an opportunity to build governance that lasts

Transparency duties under Article 50 have begun to apply, even as the EU AI Omnibus implementation for many high-risk systems has moved to December 2027 and, for certain AI-enabled products, to August 2028.

<![CDATA[ <article> <p>Transparency duties under Article 50 have begun to apply, even as the EU AI Omnibus implementation for many high-risk systems has moved to December 2027 and, for certain AI-enabled products, to August 2028. For organizations building and deploying <a href="https://www.techradar.com/best/best-ai-tools">AI</a> in Europe, the message is clear: regulators extended the timeline on complexity, but not on transparency. </p><p>While some organizations may view the extension as welcome breathing room, the time would be far better used preparing for the future of AI. To do that, we need to frame the challenge around creating the conditions for long-term innovation, rather than around compliance deadlines.</p><p>As AI becomes embedded in products, services and decisions that affect people's lives, organizations need confidence in the systems they are deploying, and users need confidence in the organizations deploying them. That work cannot begin in 2027. It needs to start now. </p><p>Compliance is achieved at a point in time; governance is built as a capability. A deadline can be moved, but an institutional capability cannot simply be created at short notice.</p><h2 id="start-with-the-ai-already-in-use">Start with the AI already in use</h2><p>The starting point for every organization should be an honest assessment of whether it has a reliable picture of the tools, outputs and interactions that Article 50 covers. As we have seen in recent years, AI systems can quickly become more deeply embedded in <a href="https://www.techradar.com/best/best-business-plan-software">business</a> over time as employees explore new tools and suppliers innovate and ship new updates.</p><p>This natural expansion is a normal part of adopting a new technology, but it can result in AI becoming a core part of business processes before the proper governance is in place. Governance is most effective when it shapes those decisions from the beginning. </p><p>Attempting to retrofit governance after AI has become embedded is significantly more difficult, more expensive and ultimately less effective, and the resulting loss of trust can be more costly than the upfront work required to prevent it.</p><h2 id="extend-the-controls-already-in-place">Extend the controls already in place</h2><p>The good news is that many of the disciplines required by the legislation should already be familiar. They build on existing practices around privacy, <a href="https://www.techradar.com/news/best-internet-security-suites">security</a>, risk management, accountability and operational governance, and much of the challenge is around applying established governance disciplines to a rapidly evolving technology landscape. </p><p>Organizations that have taken data protection regulation seriously, and already understand impact assessments and effective governance processes, are well positioned to meet many of these requirements – there is considerable overlap.</p><p>The task is to extend them for AI, not replace them. A <a href="https://www.techradar.com/news/best-linux-distro-privacy-security">privacy</a> impact assessment can identify data risks, but it cannot on its own establish whether a model is dependable in a particular context, whether someone can meaningfully question its output or whether an automated process disadvantages a group.</p><p>Those questions should be built into existing workflows, particularly when AI is bought rather than built. Before a capability is embedded in <a href="https://www.techradar.com/best/best-small-business-software">software</a> or a critical process, organizations need clarity on data treatment, service and model changes, incident response, support for transparency duties and the evidence a provider can supply. Even where the underlying model comes from a third party, organizations still need to govern how it is selected, configured and used.</p><h2 id="the-sovereignty-question">The sovereignty question</h2><p>Alongside the AI Act, the other crucial question impacting the way we think about governance in Europe is sovereignty. As the debate gains momentum across Europe, the practical issues raised are becoming clearer. Where is <a href="https://www.techradar.com/pro/best-data-removal-services-of-year">data</a> stored? Which providers do we depend on? How resilient are our technology choices? What happens if commercial, legal or geopolitical circumstances change?</p><p>It is worth being precise about what sovereignty can realistically mean for enterprises. Full compute sovereignty, including control over chips, infrastructure and supply chains, is far beyond the reach of most organizations. The more practical goal is compute resilience: understanding where critical dependencies sit, ensuring no single vendor, <a href="https://www.techradar.com/best/best-cloud-computing-services">cloud provider</a> or model becomes a point of leverage, and retaining control over the layers of the AI stack that remain within the organization's influence.</p><p><a href="https://www.techradar.com/best/best-open-source-software">Open source</a> can support this by providing greater transparency and control over code, but it does not remove infrastructure dependency on its own. An organization may use an open model and still rely on external compute or cloud capacity to operate it.</p><p>Organizations should adopt a sovereign-by-design approach to innovation. Sovereignty should not be considered after technology decisions have been made, it needs to be embedded into decisions on data architecture, vendor selection and risk management from the outset, with resilience, not full independence, as the realistic target.</p><p>It is also important to note that not every dataset, process or workload carries the same level of risk. Organizations should take a tiered approach, applying the strongest sovereignty requirements where data sensitivity, regulatory exposure or operational importance demand it.</p><p>These are not abstract concerns. Viewing AI governance and sovereignty as interconnected challenges creates an opportunity to build a more coherent approach. This is not a case for technological isolation or for stepping back from global technology ecosystems, the aim is narrower than that. It is about ensuring organizations retain meaningful freedom of action in an increasingly complex and uncertain environment.</p><h2 id="the-real-opportunity">The real opportunity</h2><p>The debate about innovation, regulation and sovereignty will continue. Europe will keep refining its approach to AI, and organizations will keep adapting to new technologies, new providers and new risks. The more important question is whether organizations use this window to build the capabilities they will need long term, rather than treating each regulatory milestone as a separate deadline.</p><p>Governance should not be viewed as a compliance exercise that slows innovation. It is an institutional capability that enables organizations to innovate sustainably, adopt new technologies with confidence, and remain resilient as markets, regulations and geopolitical conditions evolve.</p><p>The ultimate goal is innovation built on trust, and we have the ability to deliver that regardless of regulatory deadlines. The real test is not whether an organization built every part of the system it relies on, but whether it understands its dependencies well enough to change course if circumstances demand it.</p><p><a href="https://www.techradar.com/best/best-cloud-storage&amp;quot"><em>Store your data in the cloud with the best cloud storage service</em></a><em>.</em></p><p><em>This article was produced as part of </em><a href="https://www.techradar.com/pro/perspectives" target="_blank"><em>TechRadar Pro Perspectives</em></a><em>, our channel to feature the best and brightest minds in the technology industry today.</em></p><p><em>The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: </em><a href="https://www.techradar.com/news/submit-your-story-to-techradar-pro" target="_blank"><em>https://www.techradar.com/pro/perspectives-how-to-submit</em></a></p> </article> ]]>