Skip to content

EU AI Act comes into force: what small businesses should check now

If you’re a small business owner relying on AI tools, you’ll want to know this change: the EU’s AI Act Digital Omnibus entered into force on 27 July 2026, reshaping how high‑risk AI systems are managed and what vendors must provide. It’s not about scaring customers; it’s about making sure the AI you use behaves as promised and that you’re prepared to document what you rely on.

What happened

The Digital Omnibus is a package that updates the EU AI Act. The big practical change is that high‑risk AI obligations now have a concrete enforcement path and a staged timetable. Some high‑risk obligations were delayed to December 2, 2027, and August 2, 2028, giving companies time to adapt. For many small businesses, that runway helps, but it does not mean “no rules.” It means you should start mapping which of your AI tools fall into the high‑risk category and plan how to stay compliant.

Why it matters

  • What you buy and use matters more than ever. If your AI tools make decisions about people (hiring, lending, credit, or similar areas), expect tighter oversight and required documentation.
  • Vendor accountability increases. Vendors may need to share conformity documentation, risk assessments, and data practices with you or within your contracts.
  • Costs and timelines shift. Some obligations have been postponed, but others come into force—so you’ll want to know where your tools sit on the risk ladder.

What you can do now (practical steps in 15 minutes)

  • Step 1: Quick AI inventory – In 15 minutes, list every AI tool your business currently uses (chatbots, image tools, data analysis, etc.). Note what each tool does, what data it accesses, and whether it makes decisions about people.
  • Step 2: Map to high‑risk categories – For each tool, ask: does it involve personal data, automated decision making, or scoring? If yes, it’s closer to high‑risk territory under the Act’s framework.
  • Step 3: Request conformity info – For every high‑risk tool, ask the vendor for any conformity assessment, data governance docs, or risk analyses they provide. A simple, vendor‑provided minimum‑viable compliance package is a start.
  • Step 4: Document your data handling – Create a one‑page data map for each tool: what data is used, where it’s stored, who can access it, and how long it’s kept. This helps with privacy notices and risk management.
  • Step 5: Create a basic AI risk ledger – Open a spreadsheet and add columns for tool name, risk level (low/medium/high), data touched, and action owner. Update monthly as you learn more or as tools change.
  • Step 6: Build a short questions list for vendors – If you’re purchasing or renewing tools, have a few questions ready: Do you maintain a system‑level risk assessment? Do you provide data processing agreements and model accuracy documentation? How do you handle bias and updates?
  • Step 7: Public and internal notices – If your site or product uses AI in customer interactions, update your privacy policy and terms to reflect AI use and data practices in plain language.

What this means for different readers

  • Regular users – If you encounter AI in consumer apps, you’ll see clearer disclosures and a push for safer, more transparent tools.
  • Small businesses – You’ll want a light, documented process for AI governance. This helps with vendor negotiations and reduces compliance friction later.
  • Creators – If you build tools or offer AI services, prepare transparent risk disclosures and provide customers with accessible information about data and model behavior.
  • IT-minded readers – Use the risk ledger as a baseline to plan audits, vendor reviews, and security reviews tied to AI use.

Final thoughts

The EU AI Act is shaping how businesses use AI—without shutting down innovation. Start small, document what you rely on, and keep the conversation with vendors open. If you’re waiting for a perfect checklist, you won’t find one—start with a simple inventory and a few targeted questions. This month’s decision point: decide which high‑risk tools you will actively monitor and what data you’re willing to map now. The sooner you start, the smoother the path to compliance will be.

Leave a Reply

Your email address will not be published. Required fields are marked *