Summary

For small businesses deploying AI, this guide connects the EU AI Act’s roles and transparency duties to the actual workflow. It shows what to record, where a notice belongs and when a specialist decision is needed.

What you'll learn

  • How to identify the business’s provider or deployer role
  • Which Article 50 duty applies to each interaction and content channel
  • How high-risk controls differ from transparency duties
  • Which application dates to record against the workflow
  • What to include in the deployer checklist before launch

The EU AI Act assessment starts with the workflow: who controls the AI system, what it can do, who sees the output, where a human must intervene, and what evidence remains after an action.

Those questions determine whether the business needs to examine Article 50 transparency duties, high-risk deployer controls, provider instructions, or specialist advice. This guide turns that intake into an implementation map. It does not classify a business or provide legal advice.

For the underlying distinction between an AI model, an AI agent, and a business workflow, start with what is an AI agent. This guide focuses on the EU implementation questions that follow once a workflow is real.

How do you start with the workflow and your role?

An EU AI Act assessment starts with the system and the business relationship to it. “We use AI” is too broad to determine what the team should do next.

The European Commission's Article 50 FAQ defines a deployer as a natural or legal person, public authority, agency, or other body using an AI system under its authority, excluding personal non-professional activity. A freelancer using an AI system for regular professional work is a deployer under this definition. A legal person remains the deployer when contractors operate the system on its behalf and under its responsibility and control.[3]

The role map should capture:

Intake questionEvidence to recordWhy it matters
Who operates the system?Legal entity, team, contractor, or provider relationshipSeparates personal experimentation from professional deployment
Under whose authority does the system run?Account owner, contract, environment, and permissionsEstablishes operational responsibility
What workflow does the system support?Trigger, inputs, steps, outputs, and ownerPrevents a generic system label from hiding the real use
Who sees or receives the output?Staff, customers, candidates, suppliers, or the publicDetermines which transparency and risk questions need review
What may the system do?Read, draft, route, write, send, delete, or approveDefines the action boundary and possible harm
What happens when confidence is low?Human review, escalation, pause, or fallbackMakes control operational rather than aspirational

The map should name the existing tools. A workflow that reads Gmail, checks a CRM record, writes to Notion, and drafts a Slack notification has a different risk surface from a tool that answers a private question in a chat window. The model name alone does not describe the system.

A workflow intake moves from business authority through system role, audience, action boundary, and human fallback.
Role and workflow intake comes before a generic AI policy.

Use the role map alongside AI agent governance: the legal role tells you whose duties to examine, while permissions, change control and logs show how the workflow will operate.

Which transparency questions does Article 50 create?

Article 50 transparency depends on the interaction and published content. Its obligations have applied since 2 August 2026; a background tool drafting an internal note has different duties from a customer chatbot or a published deepfake.[2]

Separate the provider's design duties from your duties when using the system. The provider must build the direct-interaction notice and detectable machine-readable marking into the relevant system. The marking duty does not cover an assistive function for standard editing or a use that does not substantially alter the input or its meaning.[5] Deployers have disclosure duties for deepfakes, public-interest text, and emotion recognition or biometric categorisation. Article 50(5) requires clear, distinguishable and accessible information by the first interaction or exposure.[5]

The first compliance artifact is a workflow map.

Which questions does the Article 50 intake have to answer?

An Article 50 intake has eight questions to answer, covering the interaction, the content and which role carries the duty:

  • Does a natural person interact directly with the system?
  • Is the system clearly identified as AI at the first interaction or exposure?
  • Does the system generate or manipulate audio, image, video, or text content?
  • Is the content published to inform the public about a matter of public interest?
  • Is the output a deepfake or another form of artificially generated content?
  • Does a specific exception apply, such as human review and editorial responsibility?
  • Is the obligation placed on the provider, the deployer, or both?
  • What evidence shows how the business met the obligation?

The answer depends on the exact workflow. A private internal draft is not the same as a public article. A customer-facing agent is not the same as a background classification step. A generated image is not the same as a spreadsheet formula. The source text and current guidance must be read against the facts.

Where does the Article 50 notice belong in each channel?

The Article 50 notice belongs where the person meets the system, and the channel decides its form. These are implementation examples; the relevant role and exception still need to fit your use.

Channel or outputArticle 50 distinctionPractical placement
Website chat, messaging conversation or voice assistantProvider direct-interaction duty, unless AI interaction is obvious; Article 50(1).[5]Identify the assistant as AI when the exchange begins, in the same channel
Background sorting or a draft reviewed and sent by a personNo direct human interaction by the AI under this limb.[3]Keep the review point clear; assess published content separately
Synthetic audio, images, video or textProvider machine-readable marking duty, except assistive standard editing or no substantial alteration of the input or its meaning; Article 50(2).[5]Check that the chosen system supplies the required marking; a visible label has a different job
Deepfake image, audio or videoDeployer disclosure duty; creative works have a tailored disclosure rule.[5]Disclose in a way the audience encounters with the content
AI text published to inform the public on public-interest mattersDeployer disclosure, with an exception for human review/editorial control and assigned editorial responsibility.[5]Name the responsible publisher and record the review, or provide the disclosure
Emotion recognition or biometric categorisationDeployer notice to people exposed; assess other restrictions separately.[5]Explain operation before exposure; do not treat notice as permission to use a prohibited system

For example, an AI assistant answering a customer on the phone needs an audible introduction; a website notice the caller never sees is a poor fit. An internal agent drafting a reply for a named employee to review is a different interaction. Record which path your customer actually experiences.

The Commission's Article 50 guidelines and Article 50 FAQ explain the exceptions. Use them when the channel, audience or editorial process changes, rather than assuming that one disclosure covers every output.

What separate control layer applies to high-risk deployers?

High-risk deployer controls cover instructions, human oversight, input data, monitoring and logs. First establish whether your use is high-risk and which application date covers it; these duties are separate from Article 50 transparency.[4]

Article 26 assigns oversight to people with the competence, training, authority and support to intervene. It also requires monitoring against the provider's instructions, risk escalation and appropriate retention of automatically generated logs under the deployer's control. The exact obligations apply to the qualifying high-risk use, rather than every office assistant.[4]

The Article 26 intake should record:

Control questionPractical implementation record
Who has competent human oversight?Named person, authority, training, and review point
What instructions govern use?Provider documentation, approved purpose, and local workflow rules
What input data does the deployer control?Source systems, data owner, relevance check, and access boundary
How is operation monitored?Quality sample, incident signal, review frequency, and owner
What happens when a risk appears?Pause condition, provider notification, authority route, and internal escalation
What gets logged?Input/output context, tool action, approval, change, error, and time
Who is affected at work?Worker notice, representative process, or employment-specific review where relevant
A control map connects human oversight, provider instructions, input data, monitoring, logs, and incident handling.
The legal questions become operational when each one has an owner, a control, and evidence.

Decide how to stay in control of an AI agent before it acts: who can release a held action, what that person sees and how the workflow stops when they are unavailable.

Human oversight does not mean asking a person to glance at every output while the system remains opaque. The person needs the competence, authority, support, and information to intervene. A review button that appears after an irreversible action leaves the reviewer too late to stop it. Design the intervention point before that action.[4]

The same principle applies to monitoring. A green process status cannot prove that the output is correct. The team should define a baseline, sample outputs, record manual corrections, and pause when a serious failure appears. Is your AI agent actually working? describes the distinction between an agent that runs and one that produces an acceptable result.

Legal text becomes operational to an operator when every relevant question has an owner, a control, and a record.

A policy can say “use AI responsibly.” A deployer map identifies who can act, what the system can touch, what a person must review, and what gets logged.

The implementation map should connect the source questions to the actual workflow:

  1. Define the authority. Record the legal entity, provider relationship, account owner, environment, and contractor responsibilities.
  2. Define the workflow. Document the trigger, systems, inputs, steps, outputs, and intended business result.
  3. Define the action ceiling. Separate reading, drafting, routing, writing, sending, deleting, and approving. Give the agent only the access needed for the approved scope.
  4. Define the human point. Name who reviews, what they see, what authority they have, and which actions always wait for approval.
  5. Define the evidence. Record the source documentation, configuration, test cases, approvals, changes, exceptions, and incidents.
  6. Define the stop rule. State when the workflow pauses, who is notified, and how the team investigates before resuming.

This is where implementation work differs from a PDF policy. The system should enforce the important boundary. If the agent cannot send an external message until a person approves it, the integration and action path should block the send. The requirement should not live only in a prompt or an employee's memory.

The control map should cover the tools already in use. Gmail needs an access boundary. A CRM needs a field and write rule. Slack needs a channel and audience rule. Notion needs a workspace boundary. A model provider needs a data and retention review. Each control should answer what the system may do and who can change that scope.

The map should also capture the failure path. An ambiguous customer request, a missing CRM record, a duplicate write, or an unsafe instruction should not become a silent success. The system should flag the exception, preserve enough context for review, and stop the affected action when the blast radius is unclear.

When does the intake stop?

Pause an AI implementation when the team cannot resolve its role, intended use or action boundary. A checklist can expose the question; qualified advice is needed to settle the legal classification.

Escalate for current legal or specialist review when:

  • the workflow may fall into a high-risk use area;
  • the system affects employment, access to essential services, or a person's rights;
  • the business is unsure whether it is a provider, deployer, or another actor;
  • an AI output is published to inform the public;
  • biometric categorisation or emotion recognition is involved;
  • the provider's instructions conflict with the planned use;
  • the data contains sensitive personal information or unclear provenance;
  • the business cannot assign a competent human overseer;
  • a serious incident or material risk has occurred;
  • the current official text or guidance has changed.

Keep unresolved decisions beside the workflow they affect. For example, do not connect a candidate-ranking tool to recruitment records while its high-risk classification and oversight arrangements remain open.

Use approval workflows to hold an action for a human decision. The action log should show the reviewer, what they saw and when they released it, so the team can investigate a disputed result.

How do you keep the map current?

The EU AI Act map is a maintained project record, not a one-time checklist.

Keep these fields visible:

  • publication date;
  • last source review date;
  • official sources consulted;
  • the workflow scope covered;
  • a visible legal-advice boundary;
  • an owner for source review;
  • the events that trigger a refresh.
A maintenance timeline marks source review, workflow changes, provider changes, and incident review as refresh triggers.
A deployer map is maintained when the sources, tools, data, or workflow change.

Refresh the map when the Commission publishes new guidance, the AI Office changes an interpretation, the Regulation is amended, the provider changes its instructions, or the business changes the workflow. A change to the model is not the only reason to review. A new integration, output audience, data source, or approval path can change the operational question.

Keep the application dates beside the obligation, rather than using one launch deadline for everything. As of October 2026, the Commission's timeline is:[1]

Obligation groupApplication date
Original prohibited practices and AI literacy2 February 2025
General-purpose AI governance and model obligations2 August 2025
General application, including Article 50 transparency2 August 2026
High-risk uses in sensitive areas under Annex III2 December 2027
High-risk systems embedded in regulated products under Annex I2 August 2028

A later high-risk deadline does not postpone an already-applicable transparency duty. Record the category, date and responsible person for your use. Revisit that record when the workflow or law changes.[1]

Download the deployer checklist (English PDF) for the role map, channel notices and launch controls.

An implementation partner maps systems, permissions, approvals, logging, and testing. A partner cannot turn a generic checklist into legal certainty. The responsible sequence is source review, workflow mapping, control design, specialist escalation where needed, and a measured launch.

Frequently asked questions

What is a deployer under the EU AI Act?

A deployer is a natural or legal person, public authority, agency, or other body using an AI system under its authority for professional activity. The applicable obligations depend on the system, use, role, and relevant part of the Act.

Does using an AI agent make a small business a provider?

Using an AI system under a business's authority raises deployer questions, but use does not automatically make every business a provider. The provider or deployer role depends on the system, the facts, and how the business operates or places it into service.

Does Article 50 apply to every internal AI-generated document?

No. Article 50 covers specific situations involving direct interaction, certain generated or manipulated content, and particular deployer uses. The current official text and guidance must be checked against the workflow and audience.

Is an EU AI Act checklist legal advice?

No. A checklist organizes implementation questions and evidence. It cannot determine legal classification, replace current official sources, or replace qualified legal advice.

Notes

  1. European Commission, AI Act regulatory framework, accessed October 14, 2026; page last updated August 3, 2026. Used for the current application timeline, risk framework, transition dates, and implementation context.
  2. European Commission, Guidelines on transparency obligations, published July 20, 2026. Used for the Article 50 scope and application date.
  3. European Commission, Article 50 FAQ, accessed October 14, 2026. Used for provider and deployer definitions and practical questions.
  4. AI Act Service Desk, Article 26, accessed October 14, 2026. Used for the deployer-duty summary and the official-text cross-check.
  5. AI Act Service Desk, Article 50, accessed October 14, 2026. Used for the article structure, transparency situations, exceptions, and consolidated text as at 27 July 2026.
  6. The decision map, examples, implementation controls, and escalation boundaries in this guide are Yardwork work-product. They are educational and must not be presented as legal advice or certification.