Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Artificial intelligence

AI governance: AI Act compliance, risks and a register of systems

Knowing which AI systems you use, what level of risk they fall under and who is accountable for them: this is the foundation of compliance, and the condition for quickly authorising what can be authorised.

Our principles

  • A register that also covers purchased AI
  • Controls proportionate to risk
  • An arrangement linked to the GDPR and security
In brief

AI governance is the set of roles, rules and controls through which an organisation knows which AI systems it uses, what level of risk they fall under and who is accountable for them. Management Square consultants help your teams put this arrangement in place: a register of systems, classification under the AI Act, a proportionate approval process and coordination with the GDPR.

Scope

How we contribute

  1. Inventory and register of AI systems

    A census of systems developed, purchased or built into off-the-shelf software, including undeclared uses, and the set-up of a register that is kept up to date.

  2. Classification by level of risk

    A question grid based on Regulation (EU) 2024/1689, determination of the organisation's role for each system and written justification of the classification.

  3. Roles and approval process

    A named owner for each system, a decision-making body, a fast track for low-risk uses and an in-depth review for sensitive uses.

  4. Risk management across the lifecycle

    Assessment before going into service, monitoring in operation, incident handling and re-examination when the purpose, the data or the model changes.

  5. Coordination with the GDPR and security

    Coordination with the data protection officer and the head of security: impact assessments, record of processing activities, contractual requirements for suppliers.

  6. Rules of use for employees

    A policy on the use of AI tools written to be applied: authorised tools, data not to be entered, expected checks.

Page contents

Governance that often arrives after the uses

AI governance is rarely the first workstream opened. It arrives when the uses are already there: AI functions activated in off-the-shelf software, assistants built by business teams, employees entering the organisation’s data into consumer tools. No one has the complete list, and no one can say which of these systems create an obligation.

Two classic responses fail. The first is the charter: a text of principles, signed, that nothing links to project decisions. The second is the single committee through which everything must pass: it becomes saturated, lead times lengthen, and teams learn to bypass it. In both cases, undeclared use grows.

Useful governance does something else. It knows which systems exist, classifies each according to its risk, appoints an owner and applies a proportionate level of control. A low-risk use must be able to be authorised quickly. A system that affects a person’s access to a job or to credit must be examined thoroughly.

What the AI Act and the GDPR require

Regulation (EU) 2024/1689 of 13 June 2024, known as the AI Act, entered into force on 1 August 2024. It was amended by Regulation (EU) 2026/1744 of 8 July 2026, which notably revised its timetable. Its application is staggered according to the categories of obligations. The text reasons in terms of levels of risk.

Level What the regulation covers Consequence for your organisation
Prohibited practices (Article 5) Prohibited uses Check that no system, including purchased ones, falls under them
High-risk systems (Article 6, Annexes I and III) Requirements on the system and obligations for providers and deployers Identify these systems, determine your role, organise human oversight and documentation
Transparency obligations (Article 50) Informing people about certain systems, for example those that interact directly with them Identify the interfaces and content concerned
General-purpose AI models (Chapter V) Obligations on the providers of these models Know which models your systems rely on and what documentation their provider makes available

Two notions structure the classification work. The first is role. The regulation distinguishes in particular the provider, who develops a system or has it developed and places it on the market or puts it into service under its own name, and the deployer, who uses it under its own authority in a professional context. The same organisation may hold both roles depending on the system. Article 25 also provides for cases where a deployer is considered the provider of a high-risk system, for example when it makes a substantial modification to it. The second notion is purpose: it is the intended use that determines the classification, not the technology employed. Annex III covers areas such as employment and the management of workers or access to certain essential services.

For high-risk systems, Article 26 sets the obligations of deployers, in particular: using the system in accordance with its instructions for use, assigning human oversight to competent persons, monitoring its operation and keeping the logs under their control. Article 4, as worded following Regulation (EU) 2026/1744, also asks providers and deployers to take measures to support the development of AI literacy among their staff.

The GDPR (Regulation (EU) 2016/679) applies as soon as a system processes personal data, in training as in use. Legal basis, data minimisation, informing individuals, an impact assessment where processing is likely to result in a high risk (Article 35), safeguards around automated individual decisions (Article 22): these requirements apply cumulatively with those of the AI Act. A system that falls under none of the rows in the table is therefore not outside the framework.

Our approach: four workstreams for applicable AI governance

Our consultants work within your teams; decisions remain yours.

The register of systems. We take stock of systems developed in-house, purchased solutions and AI functions built into software already in place. The sources are cross-checked: project portfolio, procurement, application inventory, interviews with the business. Each record describes the purpose, the owner, the supplier, the data processed and the persons concerned. The register of AI systems is linked to the record of processing activities required by Article 30 of the GDPR.

Classification. A question grid allows a project manager to place their system: purpose, persons concerned, degree of automation of the decision, role of the organisation. Each classification is justified in writing. Doubtful cases are examined with your lawyers and your data protection officer. The final legal qualification rests with your organisation and its legal advisers.

Roles and the approval process. Each system has a named business owner. The process has several tracks: rapid authorisation for low-risk uses, an in-depth review for sensitive systems. Procurement is involved, because part of the obligations is handled in contracts: documentation provided by the supplier, conditions for the use of data, incident notification.

Risk management over time. Assessment before going into service, monitoring in operation, incident handling, re-examination when the purpose, the data or the model changes. Frameworks such as the ISO/IEC 42001 standard (AI management system) or the AI risk management framework published by NIST can serve as a structure, without being an end in themselves.

This arrangement builds on what already exists. The rules on data classification, quality and access fall under data governance: AI governance built alongside it creates duplication and contradictions.

The mistakes we help you avoid

  • Limiting the inventory to IT department projects. AI functions activated by a vendor in software already deployed and tools adopted directly by the business often represent the least visible part of the estate.
  • Classifying once and for all. A system can change level of risk when its purpose evolves. An assistant used to summarise meeting minutes does not call for the same review as the same tool used to sort job applications.
  • Reducing compliance to a file. Documentation that is accurate on the day it is written and never updated offers no protection. Controls must be built into the everyday running of projects.
  • Prohibiting everything by default. A general ban shifts use towards personal tools, out of all visibility. Offering an authorised solution is a risk-control measure.

How to know whether governance is working

The indicators concern coverage, speed and durability over time:

  • the share of systems in service that appear in the register, checked by cross-referencing with procurement and the application inventory;
  • the share of systems classified with a written justification and a named owner;
  • the decision time of the approval process, for each track;
  • the share of high-risk systems with assigned human oversight and complete supplier documentation;
  • the number of incidents reported and the time taken to deal with them;
  • the number of systems discovered outside the register during periodic reviews.

The last indicator is the most telling. As long as systems appear outside the register, the approval process is perceived as an obstacle. A fall in this number shows that teams are declaring their uses because they see a benefit in doing so: a rapid answer and a clear framework.

Typical work

What our consultants contribute to

Register of AI systems

A structured inventory, giving for each system its purpose, owner, supplier, data and classification.

Classification grid

A qualification questionnaire and decision rules, usable by project managers without prior legal expertise.

Governance framework

Roles, governance bodies, a multi-track approval process and a file template for sensitive systems.

Compliance plan

Gaps identified for each system, actions to be taken, owners and order of treatment.

Insights

Further reading

All insights

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is AI governance?

AI governance is the set of roles, rules and controls through which an organisation keeps control of its artificial intelligence systems. It answers three questions: which systems are used, what level of risk each presents, and who is responsible for it. It takes the concrete form of a register, a classification method and an approval process.

Does the AI Act apply to a company that uses AI tools without developing them?

Yes. Regulation (EU) 2024/1689 distinguishes several roles, including that of deployer, which refers to the organisation using an AI system under its own authority in a professional context. For high-risk systems, Article 26 sets obligations specific to deployers. Article 4, on AI literacy, also covers providers and deployers alike.

What does a register of AI systems contain?

For each system, the register states its purpose, its business owner, its supplier and the underlying model, the data processed, the persons concerned, the organisation's role, the classification adopted with its justification, the human oversight measures and the date of the last review. It includes AI functions built into purchased software, which often escape the census.

How does the AI Act fit with the GDPR?

The two texts apply cumulatively. The GDPR (Regulation (EU) 2016/679) applies as soon as an AI system processes personal data, whatever its level of risk within the meaning of the AI Act. In practice, the register of AI systems and the record of processing activities must correspond, and the data protection impact assessment is carried out at the same time as the classification of the system.

Should you create a committee dedicated to AI?

A decision-making body is needed, but it should not examine every use case. A multi-track process works better: low-risk uses are authorised quickly on the basis of a grid, and only sensitive systems go before the body. It generally brings together the business, the IT department, legal, data protection and security.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.