Map what you actually use
A small business can encounter AI through a writing assistant, an image tool, a customer chatbot or a system supplied by another company. These uses do not all carry the same responsibilities. Before responding to a headline about the EU AI Act, make a short inventory of your tools and what you ask them to do.
Record who supplies each system, whether customers interact with it, what information enters it and who checks the output. A team using a tool internally to explore a campaign has a different situation from a company putting an AI service on the market under its own name.
Understand the roles before the dates
The European Commission distinguishes providers, which develop or place systems on the market under their name, from deployers, which use systems professionally under their authority. A business can have more than one role, depending on the activity. Buying a subscription does not by itself answer every question about a later integration or modification.
For an agency, it is useful to describe the arrangement in concrete terms: who selected the tool, who operates it, who receives its output and who is responsible for checking it. Keep that explanation with the project rather than assuming that a supplier’s general marketing page settles your own responsibilities.
Check customer-facing transparency
Article 50 addresses particular transparency situations involving AI interaction and generated or manipulated content. The Commission’s guidance explains different duties for providers and deployers, including distinctions between machine-readable marking and disclosures people can understand. It also describes conditions and exceptions that matter in practice.
A sensible review therefore asks specific questions. Will a customer know they are interacting with an AI system? Could an image or recording be mistaken for an authentic event or a real person’s statement? Is material being published to inform the public on a matter of public interest? Do not assume that every use of AI requires the same label, or that an editorial review removes every possible obligation.
Treat the official timeline as the reference
The implementation timetable has several stages and has been affected by subsequent amendments. A date remembered from an older summary may not describe the current position for your system. Consult the Commission’s implementation timeline and the guidance for the relevant use case before making a release decision.
This matters particularly when a system is used in areas such as recruitment or access to important services. A marketing tool can also be repurposed for a more consequential decision. Review the actual use instead of relying only on the product category on the invoice.
Keep an operational checklist
For everyday creative work, document the material you are entitled to use, the privacy settings chosen for the project, the checks applied to factual claims and the person responsible for publication. Keep supplier documentation and record which version of the guidance informed a significant decision. Update that record when the use changes.
This article is an orientation, rather than a determination of legal compliance for a particular business. When a use has meaningful legal consequences, obtain advice on that specific arrangement. The useful first step is an accurate inventory and a short list of questions, supported by the current official sources below.
