If your company was counting on testing an AI system in a regulatory sandbox, this piece is for you. This series has chased claims that stopped being accurate and keep getting repeated: dates that changed value, one that disappeared from the article, a deadline that lost its qualifier and obligations attributed to the wrong party.
AI regulatory sandboxes are the opposite case, which is why they close the block well. There is nothing to correct here: there is a milestone that moved, and it is worth keeping on record.
What they are, and what changed
Art. 57 of Regulation (EU) 2024/1689 requires Member States to ensure that their competent authorities establish at least one AI regulatory sandbox at national level. They are controlled environments that facilitate the development, training, testing and validation of innovative AI systems for a limited time before their being placed on the market or put into service, pursuant to a specific sandbox plan agreed between the providers or prospective providers and the competent authorities, with appropriate safeguards in place.
The original text set that it “shall be operational by 2 August 2026”.
Regulation (EU) 2026/1744 replaced that subparagraph. The wording in force says 2 August 2027.
Exactly one year of delay, in an obligation that keeps the same duty on the States — the amended subparagraph restates it with the new date. The article keeps the option of establishing sandboxes jointly with the competent authorities of other Member States and the Commission's technical support, and the Omnibus adds one at Union level: the AI Office may establish an AI regulatory sandbox for AI systems covered by Article 75(1), with priority access for SMEs, including start-ups, and small mid-caps.
Whose obligation it is
The Member States'. Not the providers', not the deployers', not companies'.
That sets it apart from everything else this series has covered: it is not a task you can do well or badly. It is a condition of the environment — something that will be available, or won't be, when you need it.
And that is why it matters even though it binds you to nothing: a date that moves in a public service you expected to use is planning information, not compliance information.
The other face of the same mechanism
Here is what makes this case interesting as a closer for the block.
An outdated guide fails by repeating: someone wrote something true, the law changed, and the text keeps circulating with nothing in the sentence to warn you. That is the pattern of the five previous articles.
A gap fails by not looking: nobody wrote anything, so whoever searches finds neither the old version nor the new one. There is no error to correct because there is no claim.
They look like opposite problems, and they come from the same place: nobody has checked against the text in force. In one case because what was already written was taken as good; in the other because the amending act was never read. A Regulation amended in many places at once, in a single act, produces both — expired claims where there was attention, and silence where there wasn't.
Sandboxes fell into the second group. Not a controversial topic: exactly the profile of what nobody reviews after a reform.
What it means for a company
Little in the immediate term, and it is worth saying without inflating it: no company has a new obligation because of this change.
What does change is an expectation. If at some point you considered testing a system in a supervised environment — because it borders on high risk, because there are classification doubts, or because it is worth documenting the process with the regulator alongside — that resource is not required of each Member State until 2 August 2027.
A year's difference in the availability of an instrument obliges you to nothing, but it shifts internal timelines that had been set counting on it.
What this case teaches about reviewing
The lesson of this last article in the block is not about sandboxes.
It is that a broad reform of a Regulation is not reviewed by re-reading what you already knew. The five previous articles get corrected by re-reading what was written; this one only shows up if someone walks the entire amending act asking what else was touched — including the parts nobody cared about last year.
Applied to an organisation, it is the same difference as always: reviewing what you remember applies to you finds the known errors. Having on record what was checked, when, and against which text is the only thing that reveals what you weren't even looking at.
Content under Article 57 of Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744 (OJEU of 24 July 2026).
This article is for informational purposes only and does not constitute legal advice.