There is a new date on the EU AI Act compliance calendar. There is also a trap.
On 27 July, the EU AI Omnibus entered into force, extending the timetable for some of the Act’s high-risk requirements. The European Commission now puts the main high-risk deadline at 2 December 2027, with certain AI embedded in regulated products moving to 2 August 2028. The Commission’s revised timetable gives AV and IT teams more time to deal with the most demanding requirements.
It does not mean the AI Act has gone away for another year.
Article 50 transparency obligations started applying on 2 August 2026. The Commission published its Article 50 implementation guidelines on 20 July, less than two weeks before the rules took effect.
That is the part many people will miss. The headline says “AI Act deadline delayed.” The room still has a camera, microphones, an AI assistant, and a digital display. Those systems did not receive the memo.
The Date That Moved Was Not the Only Date
The distinction matters because the AI Act was never one giant deadline. It is a collection of obligations arriving at different times, and the Omnibus has altered some of those dates without wiping the others from the calendar.
The European Commission says the changes give industry more time for standards and implementation while retaining the Act’s safeguards. Its current AI Act guidance now puts the main high-risk obligations at December 2027, with certain AI embedded in products following in August 2028.
Article 50 is different. It concerns transparency, including situations in which people interact directly with AI, AI-generated or manipulated content is produced, emotion recognition or biometric categorisation is used, and certain AI-generated material is published.
That does not mean every AI-enabled camera needs a flashing warning on the wall. It does mean an AV professional cannot sensibly treat “AI” as a single product feature and stop there. The function matters, the person affected matters, and who is responsible for the disclosure matters.
The Commission’s Article 50 guidance is therefore worth reading at the system-design level rather than leaving it to the legal department.
Your AI Camera Is Not Automatically the Problem
This is where some early interpretations of the rules have gone too far.
An AI camera that automatically frames whoever is speaking is not automatically a biometric system. A microphone performing noise suppression is not automatically subject to an AI disclosure requirement. Ordinary transcription is not, by itself, the same thing as emotion recognition or biometric categorisation.
The danger comes from bundling.
A meeting-room platform might offer automatic framing, speaker tracking, transcription, meeting summaries, sentiment analysis, and an AI assistant through one interface. To the user, that is one “smart meeting” package. Legally, technically, and operationally, it is several different things.
AVIXA has already covered the more serious end of this problem in its recent examination of AI and workplace meeting systems, looking at emotion recognition and other AI functions operating inside meeting environments.
That distinction should now become standard practice during commissioning. Do not ask a vendor, “Does this camera use AI?” Ask what each AI function actually does. Does it identify a person? Does it classify them? Does it infer something about their emotional state? Does it generate content? Does it interact directly with them? Does the system send information to a cloud service? Does another AI service then process the result?
Those are useful questions. “Is it AI?” is not.
Meeting Assistants Have a Transparency Problem
The most obvious new issue for meeting rooms is the rise of AI assistants.
A participant walks into a room, starts a meeting, and speaks normally. An AI system listens, produces a transcript, summarises the discussion, and perhaps answers questions about what was said. The technology is useful. The compliance question is whether the people using the room understand when they are interacting with AI.
Article 50 requires providers of AI systems intended to interact directly with people to design those systems so that people are informed that they are interacting with AI, unless that is already obvious from the circumstances. The Commission’s Article 50 implementation guidance goes into the scope and practical application of that obligation.
For an AV integrator, this creates a very practical commissioning issue: where does the disclosure appear? Is it visible when the assistant starts listening? Is it part of the user interface? Does the room controller show that an AI service is active? Does the platform handle the disclosure itself, or does the customer need to configure it?
Nobody wants a meeting room that opens with a five-page privacy lecture. Nobody wants one where nobody knows an AI system is listening, either. Good design sits between those extremes.
Digital Signage Has a Different Headache
The signage problem is more visible because AI can become part of the content itself.
The AI Act requires providers of systems generating synthetic audio, image, video, or text content to ensure that outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, subject to the rules and exceptions that apply. That does not mean every digital sign displaying an AI-assisted headline suddenly needs a giant “THIS WAS MADE BY AI” banner.
The rules are more specific than that. They also distinguish between different forms of generated material. The Commission’s Code of Practice on Transparency of AI-generated Content sets out practical measures for meeting the marking and labelling obligations covering AI-generated content, including deepfakes and certain AI-generated text.
For AV teams, the important shift is upstream. The content management system is no longer simply a mechanism for getting pixels onto a display. If generative AI becomes part of the content workflow, someone needs to know how the system handles the required markings.
There is also a useful technical lesson here: do not automatically translate “machine-readable marking” into “C2PA”. C2PA is one technology used for provenance and content credentials. The AI Act does not simply say “use C2PA”. The Commission has been examining several technical approaches, including research into marking and detecting AI-generated audio, image, video, and text.
The specification question is therefore not “Does this platform support C2PA?” It is “Can this content workflow meet the applicable Article 50 requirements?”
That is the question worth putting to the supplier.
The Two-December Date Is the One to Watch
There is one useful piece of breathing room.
The Commission says AI systems placed on the market before 2 August 2026 receive a limited transitional period for the Article 50(2) marking and detection obligation for AI-generated content. For those systems, the relevant compliance date moves to 2 December 2026.
That does not create a general four-month holiday from Article 50. The Commission’s explanation of the limited grace period is quite specific: it applies to the marking and detection obligation for certain existing systems. Other Article 50 obligations still apply from 2 August.
That distinction matters for installed AV estates.
A system installed in July is not automatically exempt from everything because its software predates August. If it falls within another Article 50 obligation, the relevant rule still applies.
This is exactly why “our vendor says we are compliant” is a weak commissioning record. You need to know which obligation the vendor is talking about.
GPAI Enforcement Is Also Live — But Do Not Panic
There is another 2 August development that AV professionals should understand without overreacting to it.
The European Commission’s enforcement powers for general-purpose AI providers entered into application on 2 August 2026. The rules concern providers of general-purpose AI models and obligations that have applied to them since August 2025. The Commission’s GPAI guidance explains that the AI Office can enforce those obligations, including through fines.
This is not a new direct compliance burden on every AV integrator using an AI meeting assistant. If a room assistant calls a large language model in the cloud, the existence of that model does not suddenly turn the integrator into the model provider.
It does, however, make the supply chain more interesting. The AI sitting behind a meeting assistant is no longer an abstract cloud service. Its provider has regulatory obligations, and downstream AI-system providers need enough information about model capabilities and limitations to meet their own obligations.
That gives AV procurement teams a sensible new question: What AI sits behind this feature, and what information does the supplier provide about it?
You do not need to become an AI lawyer. You do need to stop buying AI as if it were a USB cable.
Your Room Inventory Needs an AI Column
The easiest mistake is to audit by product.
“Camera: installed.” “Ceiling microphones: installed.” “Touchpanel: installed.” “Digital signage platform: installed.”
That tells you almost nothing about the AI risk.
The better approach is to audit by function. Record whether each system provides automated framing, speaker tracking, transcription, summarisation, AI assistants, synthetic content generation, biometric categorisation, emotion recognition, or other AI-driven analysis. Record whether each function is enabled, where processing occurs, what information leaves the room, and who controls the setting.
This does not need to become a 40-page compliance document. A good commissioning sheet with an AI section would be more useful.
The same goes for default configurations. If a customer buys a meeting-room platform with 12 AI features, do not assume that “enabled” is the neutral position. Some organisations will want those features. Others will have legal, privacy, security, or corporate-policy reasons for switching them off.
Give the customer a clear choice, and make sure the room still works when the clever bits are disabled.
That last point is becoming a useful test of good AV design. If switching off the AI assistant kills the room, the AI is no longer a feature. It is infrastructure.
The New AV Skill Is Knowing What the AI Is Doing
This is the bigger change hiding behind the August deadline.
For years, AV commissioning has focused on whether the microphone works, whether the camera frames correctly, whether the display receives a signal, and whether the control system behaves itself. Now the question set is expanding: Who is the AI? What does it see or hear? What does it infer? What does it generate? Where does the information go? What does the user see? And what happens when somebody says, “Turn it off”?
That is not a theoretical exercise. It is what happens when the customer’s IT, legal, or privacy team asks questions after installation.
AV professionals do not need to own every answer. They do need to know where the answers live.
AVIXA’s AI-Enhanced Meeting Spaces programme is a useful example of how quickly these capabilities have moved from novelty to standard meeting-room functionality. The programme covers auto-framing cameras, ambient noise suppression, smart sensors, voice activation, and real-time transcription and translation — precisely the sort of functions that are now becoming normal components of the AV specification.
That is why the regulatory conversation has arrived in AV. The AI is already in the room.
My Verdict
Stop auditing AV products for AI. Audit the AI functions inside them.
The 2027 extension is useful. Take the extra time. But do not use it as an excuse to postpone the work that Article 50 has already made relevant.
For every standard room design, create a simple AI inventory. For every AI feature, record what it does, whether it is enabled, what data it handles, where processing occurs, and what user disclosure applies. Get suppliers to document the answers rather than relying on a salesperson’s description of the platform.
And when the client asks whether the room is compliant, do not answer with a product brochure. Show them the configuration. That is the difference between installing AI and commissioning it.