The decree is in the Official Gazette; the 441 pages that bind you are not
7 min read
Today, 11 August 2026, Official Gazette General Series No. 185 publishes, on page 46, the decree of 28 July 2026 by the Minister of Enterprises and Made in Italy jointly with the Minister for Public Administration, “Approvazione di modifiche alle specifiche tecniche degli sportelli unici delle attività produttive (vers. 1.02)” — ours: approval of amendments to the SUAP technical specifications, version 1.02 — drafting code 26A04030, signed by Urso and Zangrillo. If you work on a SUAP procedure touching a productive site, it concerns you from today. But the decree itself is two pages; what actually binds you is a 441-page document not in the Gazette.
What it says, and from when
Article 1(1) approves amendments to the “Specifiche tecniche per l’adeguamento delle Piattaforme”, already approved by MIMIT decree of 26 September 2023, now “riportate nell’allegato al presente decreto, di cui costituisce parte integrante” — ours: set out in the annex, forming an integral part of it. Article 1(2), the operative part, is unambiguous: “Le modifiche di cui al comma 1 acquistano efficacia a decorrere dalla data di pubblicazione del presente decreto e sono attuate entro sei mesi dalla medesima data.” Ours: the amendments take effect from publication and must be implemented within six months. Effective today. Deadline: 11 February 2027 — our calculation from the text, not a date in the decree.
The annex that is missing from where it should be
Yet at the foot of the page the Gazette prints a notice: “Il provvedimento in parola e il suo allegato sono pubblicati sul sito istituzionale del Ministero”: ours, that the measure and its annex are published on the Ministry’s own website. We downloaded it: a 441-page PDF, 10.6 MB, its Italian title citing Article 5 of the Annex to Presidential Decree 160/2010, plus a subtitle reading “Changelog – branch ‘Approved02’”. Two pages of decree in the Gazette, 441 pages of requirements outside it, and the vocabulary of a software release — branch, changelog — inside a ministerial instrument.
Three dates for the same instrument
Worth stating precisely: we verified all three today. The Gazette dates the decree 28 July 2026, printing “Roma, 28 luglio 2026”, while its own web address, and the Ministry page it leads to, read “Decreto interministeriale 27 luglio 2026” — in our rendering, Rome, 28 July, against the interministerial decree of 27 July. The decree PDF on that page carries “Roma,” with no date at all, closed by a digital signature. That same page still states, decree now published, “Il provvedimento è in corso di pubblicazione sulla Gazzetta Ufficiale” — ours: still being published in the Gazette. Nothing sinister here: the documents stand as they are. But whoever cites this decree in a specification or an application should cite the Gazette date: it is the authoritative publication, and from there — not the 27th or the 28th on the signature — run the effective date and the six-month deadline.
What actually changes
We read chapter “3. Principi generali” of the changelog — ours: ‘3. General principles’ — and these five points come from there.
First, conformance. Alongside “richieste di integrazione” (ours: requests for supplementation) there now appear, in three places — the SUAP front office, the SUAP back office, the third-party-bodies component — “richieste di conformazione” — ours: requests for conformance. The term recurs 42 times. Before, a body could ask for a filing to be supplemented; now it can formally ask for it to be brought into conformance.
Second, generic communications. Between applicant and SUAP, and between back office and third-party bodies, the specifications add “l’invio e la ricezione di eventuali comunicazioni generiche”, ours: the sending and receipt of any such communications, “volte a garantire uno scambio di informazioni utili per la gestione istruttoria dei procedimenti” — ours: meant to ensure an exchange of information useful for case-handling.
Third: bodies can now join mid-procedure — the change that weighs most on the schedule of anyone already filed. The third-party-bodies component gains “il coinvolgimento di nuovi enti interessati non censiti inizialmente sul procedimento. Tali enti ereditano le stesse funzionalità dell’ente che li ha coinvolti, pertanto, potranno: esprimere un loro parere sulla fattispecie che li vede coinvolti, inviare richieste di conformazione o integrazione, richiedere la convocazione della conferenza dei servizi sincrona e coinvolgere altri enti a supporto per le loro istruttorie.” Ours: new bodies not originally registered may join, inheriting the same functions as the one that brought them in — free to give their own opinion, request conformance or supplementation, call the synchronous conference of services, and bring in bodies of their own. A body outside the original list can join, ask, and convene.
See the service · Talk to an engineer
Fourth, ZES areas and ports enter the perimeter: two new sections, 3.9 on the ZES digital one-stop shop and 3.10 on the Port System Authority, for systems under Article 15(7) of Decree-Law 124/2023. Section 3.9 requires that the system linking the SUAP and ZES desks “DEVE assicurare” — ours: must ensure; the capitals are the document’s own, the RFC convention for obligations — interoperability with the SUAP front-office, AdSP back-office and third-party-bodies components.
Fifth, the Companies Register can now forward a filing directly to the SUAP back office for simplified handling of business-cessation procedures, where a regional rule allows it.
The process starts from Article 12(5) of Presidential Decree 160/2010, and runs through an AgID note of 25 March 2026, a favourable opinion from the Department for Digital Transformation on 9 April, and an agreement in the Unified Conference on 21 May.
The perimeter: not the network as such
Worth making precisely, since it is exactly where a knowledgeable reader takes apart a badly written piece: telecommunications works do not go through the SUAP simply for being telecommunications works. Electronic communications networks have their own, separate authorisation regime — covered in our note on the four-month deemed-consent permit. The SUAP is the one-stop shop for productive activities; these specifications matter to network work serving a production facility, a data centre, a ZES or port area, or part of a settlement procedure where laying cable — including by micro-trenching — is one of the ancillary works. Outside that perimeter, today’s decree does not apply.
What we do not know
We have not read all 441 pages: only the decree in full and chapter “3. Principi generali” of the changelog, which is where the five changes above come from. We do not know how each regional or municipal platform will implement the changes within the six months allowed, nor whether all will do so on time. We make no claim about the reasons for the three dates: we record the documents as they stand. This is a reading of primary legal sources, not legal advice.
The two threads, applied to this instrument
First thread: the specification for a productive settlement with a network in service — a facility, a data centre, a ZES or port area — now states, line by line, who files, with which documents, who answers a request for conformance and within how many days, what happens to the schedule if a body outside the original list joins mid-procedure, and that every SUAP and third-party exchange stays traced and dated: supplementation, conformance and generic communication are now typed platform categories, not notes in the margin. Acceptance testing checks that the trace exists — as with excavation coordination — not that someone remembers it.
Second thread: filed applications, documents, and conformance requests with their answers — as in our note on written requests for access to existing infrastructure — become, with CSIDIA, the group’s other company, a single map of the network and its authorisation file, on which an AI runs the diagnosis and the team answers: a body joining mid-procedure to ask for conformance gets an answer drawn from a file already indexed, not rebuilt from scratch. Within the client’s perimeter: on-premise, on standalone machines with no deep integration, or a dedicated cloud with a data centre in Italy, always with shared management.
From the first session, or the site visit, always free of charge, comes the list of your open SUAP filings with, for each one, which bodies are registered, who answers a conformance request and within how many days, and where the trace of the exchanges sits — including the boxes that stay blank. It stays yours whatever you decide next.