AI Act: how should a company communicate when the regulatory timetable changes?

A targeted delay is not a general pause

The Council’s AI Act timeline records the application of most rules from 2 August 2026. It distinguishes revised dates for high-risk systems: 2 December 2027 for the stand-alone systems concerned and 2 August 2028 for those embedded in products. Businesses still need to establish which requirements already apply to each situation.

The Council’s final approval on 29 June 2026 concerns a defined package of amendments and simplifications. As of this analysis on 7 October 2026, an undated slide based on an earlier timetable can mislead employees, customers and partners. Sales material, procurement answers and internal policies should refer to the same checked version.

Statements such as “the AI Act has been delayed” or “we are AI Act compliant” are too broad to be useful without qualification. One can suggest that protections have been abandoned; the other can imply assurance across systems and obligations that have not been assessed together. Start with the use case and the company’s role.

Map uses before drafting the corporate position

A drafting assistant, a recruitment product and an AI function incorporated into equipment do not necessarily raise the same questions. The inventory should identify the system, its intended use, affected users and the consequences of an error. Legal and technical specialists establish the relevant classification and requirements; communications teams translate that analysis without extending its conclusions.

For an international group, identify which entity is speaking, which product version is covered and in which market. A statement approved at headquarters may need revision before a French subsidiary uses it. Differences can arise from the actual deployment, contractual responsibilities or local operating arrangements, not merely from the language of the statement.

Assign an operational owner, a legal reviewer and a communications lead to each priority use. This makes it possible to revise a public claim when a supplier changes a model, a pilot expands or a new use emerges. It also prevents communications staff from becoming the sole validators of technical assurances.

Keep three categories of commitment separate

An effective message distinguishes current requirements, preparation for future deadlines and voluntary commitments. These can form part of one programme, but they require different evidence and wording.

Meeting one requirement for one system does not establish group-wide compliance. Equally, a voluntary safeguard can be valuable without amounting to a legal certification. Keep the review date and supporting technical, legal or organisational material alongside each approved formulation.

Match evidence to the audience’s decision

A customer needs to understand the product and its own responsibilities. Employees need to know how work will change and where to raise concerns. Journalists may examine incidents and consistency with earlier promises. Authorities may require specific information within their remit. The factual base must remain shared even when the format and level of detail differ.

A useful communications dossier includes a use-case description, completed controls, known limitations, an incident escalation route and the next implementation steps. A test result should not be presented as valid in every operating context. Human oversight should be explained operationally: who receives the information, who can intervene and what authority that person has.

Published indicators need a method, a sample and a date. A training commitment should distinguish people enrolled, people trained and any assessment actually completed. These details let stakeholders evaluate the programme rather than rely on the name of an internal governance initiative.

Illustrative scenario: a recruitment tool after a timetable revision

Consider a fictional company preparing to deploy an AI-assisted recruitment tool. Following a regulatory timetable change, executives consider postponing bias testing and user training. The communications question is inseparable from the decision: which risks would remain, and which safeguards does the company consider necessary regardless of the deadline?

A defensible statement explains that the regulatory timetable has been reviewed for this use, then sets out the work being maintained and the conditions for deployment approval. It describes the pilot’s limitations and the route for reporting a problem. It does not infer that a later deadline makes the system safe, or that a successful test establishes compliance with the entire regulation.

This scenario is illustrative. Classification and obligations for a real system must be assessed by the appropriate specialists. The communication principle is that a public assurance should never be broader than the assessment supporting it.

Keep the message accurate after publication

Create a register of approved claims: wording, covered use, evidence, approver and review date. Use it across the website, sales responses, executive briefings and employee materials. A material change should trigger a review of affected communications, rather than remain buried in a legal update.

For an initial discussion, gather the priority use inventory, existing statements, available assessments and recurring customer or employee questions. LLM advisory helps connect practical uses, governance and explanation. Public affairs support places the position in its institutional context. Neither replaces the legal or technical assessment. Together, they help the company communicate a programme that stakeholders can understand and examine.