In 1085 a king sent his officials to every county to ask awkward questions: who holds this land, what is it worth, who works it? On November 9, 2026 the Agency for Digital Italy (AgID) did something similar for artificial intelligence in public administration. If your company sells software, consulting or services to a public body, those questions will reach you too.
What AgID published
With determination no. 169 of November 9, 2026, AgID's director general adopted the Guidelines for the adoption of artificial intelligence in public administration. The official announcement places them within the 2024-2026 three-year IT plan for public administration and Article 71 of the Digital Administration Code.
One point first: the document is addressed to public bodies, not suppliers. Its scope refers to the entities in Article 2(2) of the Code. It does not, on its own, create obligations for companies. But public bodies will have to apply it, and they will do so toward those who work with them.
The guidelines revolve around four areas:
| Area | What it asks of the public body |
|---|---|
| Risk and compliance | Classify systems under the AI Act and recognize its own role (provider or deployer) |
| Adoption model | A Plan-Do-Check-Act cycle inspired by the ISO/IEC 42001 standard |
| Data and security | Data quality and defenses against attacks such as evasion and poisoning |
| Ethics and skills | A people-centered approach and staff training |
Where suppliers find themselves in the text
Two passages touch a small company directly. First: public bodies must clearly identify the suppliers and any subcontractors involved in the service chain. Second: they must ensure adequate safeguards so that suppliers do not use the data processed for their own purposes or purposes incompatible with the body's.
The text also recalls the AI Act obligations along the value chain (Articles 22-26) and notes that a deployer can be treated as the provider of a high-risk system in certain circumstances, as provided by Article 25.
The guidelines contain no list of documents to attach to bids, and they should not be read as if they did. What emerges is a direction: more traceability, clear roles, data under control.
The Domesday Book: whoever holds the inventory rules
And you will ask: what does a Norman king have to do with a small Italian company? According to the Anglo-Saxon Chronicle, in 1085 William the Conqueror sent agents to survey every shire of England. The resulting book, completed in 1086 according to its colophon, recorded for each property its annual value, land, labor force and livestock, plus the king's fiscal rights. Information came from public inquiries: each hundred answered through local jurors, twelve of them, half English and half Norman. The Wikipedia entry on the Domesday Book notes this and also the name: a writer of 1179 says that, as at the Last Judgment, there was no appeal.
The point for us is simple: those who govern want to know what exists, who holds it and what it is worth, and they want it in writing. Well, your company today stands before an official with a register: the public body that must classify systems and map suppliers. If you already have the inventory, you answer in ten minutes. If not, you write it in a hurry, and badly.
What to do on Monday morning
- Inventory the AI you use: list tools, vendors, the type of data loaded and who in the company answers for each. A table is enough.
- Check contracts with your AI vendors: see whether customer data can be used to train their models, which is what the AgID text asks public bodies to prevent.
- Write down who decides and who checks: for each use of AI, name the person who verifies the result. In public administration the administrative decision stays human, and your public client will want to see that.
For the big picture, read AI Act: what changes for SMEs and the rules for employees using ChatGPT. See the SMEs page and our services. Then book a free discovery call: half an hour to understand what your next public client will ask.
The Professor of Penzai

