Two questions.
One defensible boundary.
Your role determines what you are responsible for. Your certification scope determines where your AI management system applies. Neither can be safely inferred from a logo or a certificate headline.
participate
function you perform
! “Provider” appears in both vocabularies, but do not assume the label carries identical consequences.
Classify the activity,
not the company name.
One organisation may hold several roles at once—and a role can change by product, market, or contract. Start with the facts of a specific AI system.
Market control
Do you place the AI system on the market or put it into service under your own name or trademark?
This can include commissioning another party to build it for you.
No examples match that search. Try a role, sector, or activity.
Same organisation. Different analytical lens.
ISO terminology supports management-system context. EU AI Act roles allocate legal obligations. A useful mapping starts with actions, not labels.
Indicative mapping only. The EU AI Act definitions and role-switching provisions should be tested against the specific facts.
A certificate is a boundary.
Make it visible.
Certification can legitimately cover an organisation, a business unit, or a defined product activity. The decisive question is whether the stated boundary matches what you rely on.
Choose the scope described on the certificate
Confirm interfaces with central teams, shared data, suppliers, and out-of-scope AI activities.
Click each test as you verify the certificate and scope statement.
Know your role.
Set the right scope.
Bring one AI use case and one certificate. In a focused review, LeadAI will map the likely roles, identify boundary gaps, and define the evidence to verify next.
Book a scope review ↗