How do you ensure compliance with the AI Act when using multiple AI tools?

Why work with us:

– We improve your accessibility
– We enhance your customer experience
– We increase your efficiency

Want to know how we’ve been using AI to enhance the customer experience for years?

“With Pegamento, we found not just a supplier, but a true partner in change. Thanks to their expertise and our joint DevOps approach, we have made great strides in a short time. The technology supports our people so they can focus on where they make a difference: personal contact with entrepreneurs.”

If you use multiple AI tools at the same time, you can ensure compliance with the AI Act by maintaining a central AI inventory, determining the risk level for each tool, and clearly documenting who is internally responsible for which system. The EU AI Act imposes obligations on both providers and deployers, and it is precisely the combination of multiple tools that makes it difficult to maintain an overview. In this article, we answer the most frequently asked questions about AI compliance in a diverse AI tool landscape.

Which AI tools are covered by the AI Act?

The AI Act applies to any AI system that you develop, use, import, or distribute within the EU, regardless of whether it is your own tool or a service provided by a third-party provider. This includes chatbots, decision-support systems, image recognition software, automation platforms, and large language models. If the output of an AI system is used within the EU, the regulation applies even if the system itself was created outside the EU.

The law distinguishes between four risk levels. Most AI tools that organizations use on a daily basis fall into the “minimal” or “limited” risk categories and are therefore largely unregulated or subject to only light transparency requirements. High-risk AI, such as systems used in human resources management, credit assessment, or access to essential services, is subject to strict regulations. Systems that are completely prohibited include those that use subliminal manipulation, perform social scoring, or employ emotion recognition in the workplace.

In addition, the law introduces a separate regime for General Purpose AI (GPAI) models, such as large language models. Providers of these models have their own documentation and transparency obligations, regardless of the risk category of the specific application.

How do you know which requirements apply to each AI tool?

The obligations that apply depend on two factors: the tool’s risk category and your role in the chain. If you are a deployer—that is, an organization that uses an AI system from an external provider—different obligations apply than if you are the provider who develops and markets the system yourself.

As a deployer, you are required to:

  • to use the system in accordance with the provider’s user manual
  • assign human supervision to qualified and trained employees
  • to retain logs for at least six months
  • inform employees before a high-risk system is put into service (Article 26(7))
  • to conduct a data protection impact assessment (DPIA) where applicable

For each tool in your portfolio, it is therefore essential to determine whether it constitutes a high-risk system under Annex III of the Regulation. Systems that profile natural persons are always high-risk, regardless of their intended use. Systems that perform only a preparatory or procedural task without posing a significant risk to fundamental rights may fall outside the high-risk category, provided you document this with supporting evidence.

What is the biggest risk when combining multiple AI tools?

The biggest risk when combining multiple AI tools is losing track of who is responsible for what. When different tools from different providers work together in a single process, a responsibility gap can arise: as the deployer, you may assume that the provider covers certain risks, while the provider assumes that you, as the user, will take additional measures.

A second risk is the cumulative impact. An individual tool may pose a low risk, but when multiple systems collectively influence a decision—for example, in a customer contact process where an AI chatbot, a routing system, and a decision model work together—the combined effect may indeed exhibit high-risk characteristics. The AI Act assesses systems based on their actual use and impact, not just their technical design.

In addition, anyone who adds their name to a system, makes a substantial change to it, or alters its intended purpose in such a way that the system becomes high-risk, becomes a provider themselves, with all the associated obligations. This is a point that is often overlooked when combining or modifying tools.

How do you create an AI inventory for compliance purposes?

An AI inventory is a structured overview of all AI systems used by your organization, including their risk category, provider, intended use, and the person responsible for them within the organization. Compiling such an inventory is the practical foundation of any AI compliance approach.

Follow these steps to create a practical inventory:

  1. Identify all AI tools, including those used indirectly through SaaS platforms or built-in features in existing software.
  2. Determine the risk category for each tool based on its intended use and the Annex III criteria of the AI Act.
  3. Define your organization’s role: Are you a deployer, a provider, or both?
  4. Document the provider’s user manual and the internal agreements regarding human oversight.
  5. Record the logging requirements for each tool and ensure that logs are retained for at least six months for high-risk systems.
  6. Assign each tool to a specific person within your organization.

Keep the inventory up to date. AI tools are updated regularly, and an update may change the risk category or the applicable obligations. Therefore, do not treat the inventory as a one-time document, but as a living record.

Who is responsible for AI Act compliance within an organization?

Compliance with the AI Act is not the responsibility of a single person or department. In practice, at least three roles are involved: the operational owner of the tool, the IT or digital transformation manager, and the privacy or compliance officer. For high-risk systems, senior management is also responsible, because the regulation requires that human oversight be entrusted to competent and trained individuals.

The Privacy Officer plays a key role in conducting data protection impact assessments (DPIAs), which are required when a high-risk AI system processes personal data. The HR department is involved in the obligation to inform employees before high-risk systems are put into use.

A practical consideration: The AI Act stipulates that individuals who are subject to a decision made by a high-risk system may, pursuant to Article 86, request an explanation of the determining factors. Your organization must be able to provide that explanation. This requires not only technical knowledge of the system, but also clear internal processes and a designated point of contact.

How do you stay compliant when AI tools are updated regularly?

Maintaining compliance amid regular updates requires a fixed review process that is triggered as soon as an AI tool undergoes a significant change. An update can alter a system’s intended use, underlying data, or output, which can have direct implications for the risk category and applicable obligations.

Determine internally what a “substantial modification” means for your tool ecosystem. The AI Act stipulates that anyone who makes a substantial modification to a system becomes a provider themselves. That’s a line you’ll want to monitor carefully, especially if you’re customizing or integrating AI tools into your own processes.

Practical steps to stay up to date:

  • Proactively ask providers for changelogs and release notes with every update.
  • With each significant update, reassess the risk category in your AI inventory.
  • Check whether the supplier’s user manual has been updated and update your internal work instructions accordingly.
  • Ensure that employees who work with high-risk systems are informed of any relevant changes.
  • Schedule a full review of your AI inventory at least once a year, and more frequently if the tool landscape is changing rapidly.

The phased implementation of the AI Act will continue through 2027, with reviews in 2028 and 2029. High-risk Annex III systems will be subject to full compliance requirements as of August 2, 2026. This gives organizations the flexibility to build their compliance process step by step, but makes a structured approach all the more important now.

How Pegamento Helps with AI Compliance

Tracking AI compliance across multiple tools is exactly the kind of challenge where a fragmented vendor landscape can cause problems. We help organizations gain control of their AI environment—from assessment to implementation—all under one roof, without the need for complex coordination among multiple parties.

What we offer in the areas of AI compliance and responsible AI use:

  • Overview and Assessment: We help you identify which AI systems you use and the obligations associated with them.
  • Responsible AI Implementation: Our Agentic AI solutions for customer service are designed with human oversight as a core principle, not as an afterthought. Agentic AI thus represents an evolution from task-oriented bots to self-thinking assistants that take the initiative independently, but always within clear guidelines.
  • No costly custom development, but a smart combination of proven modules: you get a tailored solution that fits your organization and compliance requirements, without the costs and risks of fully custom-built systems.
  • A single point of contact: from consultation to implementation and management, so you always know who is responsible.
  • ISO 27001, ISO 9001, and ISO 26000 certified: information security and quality are embedded in our work processes.

Would you like to know where your organization stands right now in terms of AI compliance? Contact us, and we’d be happy to help you figure it out.

Frequently Asked Questions

What are the fines for non-compliance with the AI Act?

The AI Act establishes a tiered system of fines based on the severity of the violation. Fines for using prohibited AI systems can reach up to 35 million euros or 7% of global annual revenue. Violations of obligations regarding high-risk systems are subject to fines of up to 15 million euros or 3% of revenue, and providing inaccurate information to regulators can result in fines of up to 7.5 million euros or 1% of revenue. Precisely because the fines are substantial, it pays to invest in a solid compliance structure now.

Do I need to actively inform my employees that they are working with an AI system?

Yes, for high-risk AI systems, Article 26(7) of the AI Act requires deployers to inform employees before the system is put into use. This also applies when an existing system is significantly modified. In practice, this means you must establish an internal communication process—preferably linked to your AI inventory—so that every relevant employee is informed in a timely and verifiable manner.

How do I handle AI functionality that is already built into software I use, such as a CRM or HR platform?

Built-in AI features in SaaS platforms are also subject to the AI Act if you actively use them within the EU. Check with your software vendor to find out which AI functionality is active, what its intended use is, and whether the system is classified as high-risk. Include these systems in your AI inventory, even if you did not intentionally purchase them as ‘AI tools,’ because as a deployer, you are responsible for their use.

When is my organization considered a 'provider' rather than a 'deployer'?

Your organization becomes a provider as soon as you market an AI system under your own name, substantially modify an existing system, or alter the intended use in such a way that the system falls into a higher risk category. This is a common pitfall when integrating or fine-tuning existing AI models into your own processes. As a provider, you are subject to significantly stricter obligations, including conformity assessments, technical documentation, and registration in the EU database.

How do I combine AI Act compliance with existing GDPR and DPIA obligations?

The AI Act and the GDPR overlap when it comes to data processing: when a high-risk AI system processes personal data, you are required under both regulations to conduct a DPIA. In practice, you can combine these processes by expanding your existing DPIA template to include AI-specific questions about risk category, human oversight, and logging requirements. Involve your Privacy Officer early in the AI inventory process to avoid duplication of effort and achieve an integrated compliance approach.

Are there any tools or templates available to help set up an AI inventory more quickly?

The European Commission and national data protection authorities, including the Dutch Data Protection Authority, publish guidelines and working documents that you can use as a basis. In addition, frameworks such as the NIST AI Risk Management Framework and ISO/IEC 42001 offer structured methods for AI governance that align well with the AI Act requirements. To get started practically, you can also collaborate with a specialized partner that has already developed a working inventory methodology, so you don’t have to start from scratch.

What should I do if an AI provider discontinues a tool or changes its services?

If a provider discontinues or significantly changes its service, this has direct consequences for your compliance status: the user manual you, as the deployer, are permitted to rely on becomes invalid, and you must reassess whether and how you can still use the system responsibly. Always include provisions in contracts with AI providers regarding notification of changes, transfer of documentation, and continuity guarantees. Also, make sure your AI inventory includes a column for contract expiration dates and scheduled review dates, so you don’t run into any surprises.

More blogs

Download the white paper here

Deepen your knowledge with Pegamento’s white papers.

Joost Schaap-Account manager Pegamento

Joost Schaap

Senoir Account Manager

When a customer contacts an organization because they have a complaint, it is crucial that the employee of the organization begin by listening carefully. What does this complaint mean for the customer and also for their own organization? How can this complaint be resolved? After listening carefully the employee needs the right information so that a solution can be offered.

This piece was written by Joost Schaap, working as an Account Manager at Pegamento.

Tim Treurniet-AI developer Pegamento

Tim Treurniet

Designer of Intelligent Systems

Real childhood heroes I never had. But in retrospect, I believe figures like Willie Carrot or Dexter’s lab may have had an influence on me. I get energy from actually making innovative and useful products myself. Nothing like seeing the effect of a project that automates a boring task, or makes a complex process suddenly accessible.

A nice bridge to my photograph is the physical aspect of my work. By working with image recognition, I am often very directly connected to the physical world and my work is more than just programming. For example, our image recognition software ensures safety on bridges, tracks players on a soccer field or uses your own smartphone to accurately measure yourself. This combination between physical and digital provides variety and extra challenge. For me, these are the main reasons for my interest and enthusiasm in what I do!

This piece was written by Tim Treurniet, employed Designer of intelligent systems at Pegamento.

Vera van der Plas-UI-UX designer

Vera van der Plas

UI/UX Designer

As a UX/UI designer, I deal daily with transforming complex data into user-friendly visualizations. All of this topped off with a digital lick of paint which should attract the visitor’s attention to take action.

One of the interesting aspects of this field I find the effects that small tweaks, both textual and visual, can have on conversion. The psychological impact that a simple background color of a CTA button has on our behavior is huge. After all, that color can determine whether or not you are going to buy that product.

What we see and how our brains process and interpret this information fascinates me. The possibilities of subconsciously pointing potential customers in your chosen direction are endless. I hope to apply my expertise more often within our solutions in the future.

This piece was written by Vera van der Plas, working as a UX/UI Designer at Pegamento.

Fouad Rahaoui-Finance Pegamento

Fouad Rahaoui

Financial Controller

A Financial Controller within a company should not only be an expert in Finance. You must also have knowledge of the latest IT developments. Because these are also moving very quickly in the world of Finance.

At Pegamento, I can learn all about the latest IT developments. Like the latest development in the field of Machine learning and deep learning.

Through these application areas, as Financial Controller, I can further automate the financial business processes within Pegamento and implement improvements for the automatic processing of financial data.

This piece was written by Fouad Rahaoui, working as a Financial Controller at Pegamento.

Ernst Vegter-Business consultant Pegamento

Ernst Vegter

Business Consultant

Hospitality is one of my deepest motivations.
Not surprisingly, of course, customer service is a common thread in my career. Aspects of hospitality is being able to connect, to facilitate but mainly to make someone feel genuinely welcome. My intuition is my greatest asset to be able to put myself in the shoes of a guest. A customer is my guest.

Fed by various senses, an image forms around the client. I listen to what is being said, watch facial expressions, taste the underlying tone and get a feel for the challenge to be addressed. An image literally forms on my retina. I have to be able to see it. If I can see it, I can create it.

In this, the trick is to pursue simplicity, give the client a warm feeling that the problem is understood, receive good advice, facilitated and carefully guided to the solution. Trust, connect and unburden.

The feeling when a guest arrives at your hotel after a long tiring journey, can sit in front of the fireplace, be handed a good glass of wine and stare carefree at the fire. My guest knows it will be okay.

This piece was written by Ernst Vegter, working as a Business Consultant at Pegamento.

Gunisch-AI developer Pegamento

Gunish Alag

AI Developer

A picture is worth a thousand words, is an expression most of us have heard. We see a lot of things around us on a daily basis and subconciously have the ability to recognize and understand them. This ability of humans to me seems bizarre.

As a computer vision developer at Pegamento that is what I do, break down complex problems and turn them into solutions using images by meticulously extracting useful data.
With the world moving forward and new technologies emerging, complicated problems which were difficult to solve a decade earlier suddenly seem possible and viable. The future is full of new challenges and I look forward to them.

This story is written by Gunish, working as an AI developer at Pegamento.

Ewold Jansen-Service engineer Pegamento

Ewold Jansen

Service & Support Engineer

Hearing the wishes a customer has or the problems a customer is facing is important in order to then be able to help them properly. In both cases, I help find the right solution.

When the customer comes to us with a desire, they don’t know what all the options are. In this I advise them to make the right choices. When problems arise, listening to them is important. For example, a problem arises from a wrong action. By communicating well in this, many problems can be solved quickly by explaining it well. Through poor communication, a small problem can become very big.

This piece was written by Ewold Jansen, working as a Service & Support Engineer at Pegamento.

Andre Glasbergen-Scrum master Pegamento

Andre Glasbergen

Scrum Master

After completing my studies, I started working as a developer at a young Pegamento with a lot of ambition and enthusiasm. In the first years I learned all about process automation, now better known as RPA. I often had to rack my brains to convert the work instruction into a logical function, with not too many If-statements, so that the robot could perform the work.

I developed further and went to work as a consultant. Listening well to the customer and supporting in the pre-sales phase of projects. Executing projects and listening suited me very well. It was a small, but logical, step to now work as a Scrum Master and Project Manager. I have been supervising projects for a few years now. Such as RPA, Cloud applications and AI, according to the Human lead agile approach, We build this with a large team of specialists.

This piece was written by André Glasbergen, working as a Scrum Master at Pegamento.

Ensar Ari-IT engineer Pegamento

Ensar Ari

IT Engineer

Good communication between customer and organization is very important. As an organization, you naturally want to be easily accessible to your customers. Either via social media channels or via the old familiar telephone. Often organizations do not know exactly how they want their telephone line set up. That is why I like to help them think along and give them ideas. I believe there is a solution to every problem. But sometimes you just need someone who looks at the situation a little differently.

This piece was written by Ensar Ari, working as an IT Engineer at Pegamento.

Nini Heerings-Chief Happiness Officer Pegamento

Nini Heerings

Chief Happiness Officer

“You get to know someone better by playing for an hour than by talking for a year.”

This quote from Plato is totally hitting home for me. That’s why I like to connect people through play. Because while playing, you are totally on, all your senses at work.
In my great role as Chief Happiness Officer, I want to do that by connecting colleagues with each other and with the organization. In a creative and playful way that suits Pegamento.

When I’m not at work, I also enjoy connecting people. I do this by organizing The Playground, where adults play games you used to play in the schoolyard, gymnasium or neighborhood playground. The pure feeling of fun, total relaxation and no thoughts of anything but playing. That feeling is the goal.

This piece was written by Nini, working as Chief Happiness Officer at Pegamento.

Ger Koedam-Communication & Marketing Pegamento

Ger Koedam

Marketing & Communications

How can I help you? That’s pretty much the first question I ask when talking to people who are curious about our services. In such a conversation, the use of senses is very important. Because not everyone is the same. One person thinks in images, while for another words are important or how something feels. For me, sight and hearing are the most beautiful senses, because both eyes and ears absorb information and can convey or process emotions.

Why hearing? Because listening is essential in contact. And it’s the key to unlocking valuable insights.

I developed this skill early on. As a child, I enjoyed radio plays on the radio, bringing the stories to life in my head.

Pim Ritmijer-Software developer Pegamento

Pim Ritmeijer

Software Developer

Programming is more than just “code knocking. For me, listening to what the customer wants and visualizing that is an important part of software development.

Actively listening to a customer to understand the customer’s full story is crucial before building a solution. When you understand a customer’s story, you can think together about a solution that truly helps the customer.

Visualizing solutions is the next step for me. What will be the route we will climb to get to a solution? What challenges are we going to face to get to the top?

Like climbing, good preparation is valuable. Even though you can’t prepare for everything, preparation helps make the application fit the client’s needs as well as possible.

What a beautiful and fascinating profession programming is.

This piece was written by Pim Ritmeijer, working as a Software Developer at Pegamento.

Denise Verhoef-Software developer Pegamento

Denise Verhoef

Software Developer

Hearing is something you do a lot of as a programmer but also thinking, for example, when you are tasked with putting together a customer need. If the customer wants a function for his application, it is important that as a programmer you think carefully about which functions are functional and which functions are not. In this way, you will put together the most functional application possible and the customer will have a good end product. Turning needs into code into functionality is something I find interesting.

I am currently doing an internship at Pegamento and studying Software Developer. I get a lot of information that you have to process and apply. The nice thing about this is that you can learn new things but also that you can experience how it works in real business. I started this training last year and knew nothing about programming beforehand. Now I can find my own way with programming and I enjoy working with it. That you can get from a blank page to a functional application through code is cool!

This piece was written by Denise Verhoef, working as a Software Developer intern at Pegamento.

Remco Pabst-Business consultant Pegamento

Remco Pabst

Computer Vision & AI Lead

Using innovative software technology for people or business to make “things” easier and smarter is really a driving force. That’s why the connection between the senses appeals to me the most. Our brains connect the senses just like a business process connects people, systems (data) and logic. They register and trigger an action, exactly how it should be in an optimal workflow. Very cool what is already possible today when we add a lot of computational power to that as well.

Hearing also means a lot. Not because I like to listen to Jazz, Soul, Deep House or Focus-like music every day AND have to be able to listen well to interpret a wish or pain point, but more because not everyone can have all the senses at their disposal. Think of him or her with a visual impairment. The fact that in close cooperation we were able to apply AI, TTS/STT technology (which is still in development) for this often underserved group of people in today’s digital world and to improve the interaction and experience with it gives me a lot of energy and meaning to what I try to do with technology; create value.

This piece was written by Remco, working as a Business Consultant at Pegamento.

Thomas de Wolf-Vision Engineer Pegamento

Thomas de Wolf

R&D Director

Once when I had to choose which study I was going to do, I had a hard time making that choice. I was interested in engineering, but what I most wanted to do was just work with a team toward a common goal.

To this day, that is still what I love doing most. The technology has become image recognition and the team the computer vision department of Pegamento. So it’s logical that in terms of sense, I end up with “seeing. By using our image recognition solutions to see things in the real world, our entire team solves relevant problems for our customers. And because of the variation in customers, the places where our solutions end up are never the same. For example, one moment I am in the control room of a bridge and the next day I am on a production line for sandwiches or between the fences of a TBS clinic.

This piece was written by Thomas de Wolf, working as a Computer Vision & AI Lead at Pegamento.

Rob Roode-Research Development

Rob Roode

Research & Development

Recognizing and automating patterns. Tasks we are constantly working on when implementing our robots at Pegamento. My 2 Drentsche Patrijshonden are hunting dogs and certainly not robots. The hunting instinct and intuition is basically in their genes. Continuing to offer new forms of training has taught them to recognize and act independently in hunting situations. Even “unsupervised,” even if I’m not around.

But when you try to teach a brain something, it also starts to see things you don’t expect. Dogs pick up on the slightest deviation in your voice or directions. To start recognizing that and correcting it again is perhaps the most complex challenge. But in our work, for the wonderful clients for whom we get to work, it often yields the most beautiful new insights!

This piece was written by Rob, founder of Pegamento and in charge of Marketing and R&D.

Serge Poppes-CEO Pegamento

Serge Poppes

CEO

Feeling. That’s the best thing Pegamento stands for. Feeling for technology in the broadest sense of the word. Not only feeling for the exciting stuff like AI, but also for the basics of communication.

The very best part of my job is selling, listening, translating and thinking about what really matters. We bring the digital transformation with a great team!
The diversity of our team, how sharp we are, but especially the wonderful things we get to make makes me feel extremely good. Hence, I intuitively chose the sense of “feeling.

Feeling gives life and differentiation!