AI Act Compliance: The First 90 Days, in Order
An EU AI Act getting-started roadmap for lean teams: days 1-30 scope, 31-60 close mandatory gaps, 61-90 institutionalise — with what to postpone.
Most first steps for eu ai act compliance programmes fail the same way: the team starts with the hardest obligation and stalls in month two. Sequencing matters more than speed. The right 90 day ai act compliance plan front-loads decisions that unblock everything else, closes the cheap mandatory gaps in the middle, and deliberately postpones the expensive machinery until you know it is aimed correctly. This is the plan we run with lean teams — one owner, no big-bang programme, every week producing evidence you would show an auditor.
Days 1–30: scope and decide
The first month buys clarity, not documents:
- Name one accountable owner. Not a committee — a person with a calendar slot and authority to make classification calls. Compliance, risk or legal, depending on who can convene people. Everything else depends on this.
- Build the working inventory. Procurement records, IT SSO logs and a department survey (“what AI assists your team’s decisions?”). Expect the survey to double your list. Separate inventory from in-scope population — you are not yet classifying every plugin.
- Classify the top ten by consequence. Rank the population by what they touch: people decisions (hiring, credit, promotion), money, safety, regulated records. Classify those ten first with written rationales — Annex I? Annex III? neither? Ten reasoned decisions beat a hundred checkboxes.
- Fix the role question. For each: are you provider or deployer? One sentence each. This decides whether your next 60 days are heavy (documentation, conformity) or moderate (oversight, instructions, logs).
- Draft the decision log. A simple table: tool, classification, role, rationale, date, decider. This is the document that answers “why did you think it was out of scope?” — the first question any auditor asks.
What you are not doing yet: buying tooling, drafting 40 procedures, or launching an all-staff course. Postponement is a decision, so write it down — a plan that says “tooling deferred to quarter two, rationale: population not yet stable” is leadership; the same delay with no note is drift.
Days 31–60: close the cheap mandatory gaps
With classification roughed in, attack obligations that are cheap, mandatory for everyone, and visible to auditors:
- Article 4 AI literacy. A 45-minute session per team on what AI is, permitted and prohibited uses, and how to log incidents — attendance recorded. It has applied since February 2025, so this is often the oldest live gap.
- Vendor contract allocation. Add three clauses to the AI procurement template: the vendor declares provider role and supplies their declaration of conformity where applicable; they notify you of changes in intended purpose; they cooperate with authority requests. Retrofit to renewals, not all at once.
- Human oversight, assigned. For every in-scope tool, name the role that monitors outputs and can override — in the operating procedure, not the policy PDF. Article 26 expectations start here for deployers.
- Logging configured. Ensure the systems that make decisions retain input, output and timestamps for at least six months (Article 26(6)) — often a settings change, not a project.
- Register, published internally. Your inventory plus classification and role, maintained somewhere with an owner. The register is the spine; everything else hangs off it.
- Incident path. Define who decides whether an event is a serious incident under Article 73 and who reports. A one-page procedure beats a gap.
By day 60 the posture is defensible: the population is known, roles assigned, the four universal obligations evidenced.
Days 61–90: institutionalise
The last month converts activity into machinery that survives holidays and turnover:
- Backlog from your gap assessment — the heavier items (technical documentation for provider systems, FRIA where Article 27 applies, registration under Article 49, deep-dive on contested classifications) sized with owners and dates.
- Governance rhythm. A 30-minute monthly AI governance check on the register and backlog; a quarterly evidence spot-check on five items; an annual full re-run. Put all three in the calendar before day 90 ends — rhythm is the difference between a programme and a project.
- Change triggers. New tool, purpose change, vendor model swap, incident: each triggers re-classification within a defined window. Write the trigger list into the register’s instructions.
- Escalation route. Who decides when two functions disagree about a classification, and by when. Without it, contested items rot — the most common failure we see after month three.
| Phase | Focus | Evidence produced by the phase gate | Primary owner |
|---|---|---|---|
| Days 1–30 | Scope and decide | Inventory, top-ten classifications with rationales, roles assigned, decision log opened | Named programme owner |
| Days 31–60 | Close mandatory gaps | Literacy attendance, contract clauses, oversight assignments, log settings, internal register, incident route | Compliance + IT |
| Days 61–90 | Institutionalise | Sized backlog with dates, governance calendar, change-trigger list, escalation route | Programme owner + leadership |
Each phase gate is an artefact check, not a status update: if the evidence does not exist at day 30, the phase did not close, regardless of how the work felt.
The quick wins that read bigger than they are
Five moves that take days and change how the programme is perceived: publish the register internally (transparency signals control); attach the classification rationale template to every new-tool intake form (prevention beats review); add the three AI clauses to the procurement template (future contracts close themselves); record literacy attendance for the two teams using generative AI daily (closes the oldest applicable gap); and file one dated decision memo resolving your most contested classification (turns a debate into evidence). None of these requires budget approval, and collectively they cover the obligations every firm owes regardless of classification.
Prioritising: the four-quadrant filter
When the backlog exceeds capacity, filter every item through consequence and reversibility:
- High consequence, irreversible (misclassified high-risk tool already on the market; no declaration for a product customers bought): stop other work, fix now.
- High consequence, reversible (register incomplete; literacy untrained): schedule inside the 90 days — exposure exists but nothing is baked in.
- Low consequence, quick (decision-log format inconsistent): batch into one Friday session.
- Low consequence, slow (rewriting every legacy contract before renewal dates): defer deliberately, with the deferral noted.
The quadrant that kills teams is the low-consequence quick fix — endlessly satisfying to complete, invisible to auditors. Ruthlessness here is the whole point of sequencing.
What a good day-90 position looks like
Not “fully compliant” — that phrase belongs to whoever is selling you something. A credible day-90 position is: one named owner; an inventory with a classified in-scope population; written rationales for the top ten; roles assigned; Article 4 training recorded; contracts with AI allocation; logs at six months; an incident route tested once with a tabletop; a register maintained; a sized backlog with owners and dates; and a governance rhythm in the calendar. When an enterprise customer or authority asks “show me your AI Act position”, that package answers in ten minutes — and every piece of it is traceable to a date and a person.
How to check your own position
Take the five day-30 questions — owner, inventory, classifications, roles, decision log — and answer each with either a document or a date. Anything you cannot answer is your real starting point, regardless of what the policy library says. Then audit your last two weeks of AI activity against day-31 items: did anyone record literacy training, configure log retention, or add the vendor clauses? If the answer is “we discussed it”, convert one discussion into one artefact today — an attendance record, a settings screenshot, a clause in the template. Momentum in this programme is measured in artefacts, not meetings.
Frequently asked questions
What should we do first for EU AI Act compliance?
Name a single accountable owner, build the inventory, and classify the ten systems with the highest consequence — people decisions, money, safety, regulated records — with written rationales. Classification first because every obligation set flows from it; owner first because nothing else survives without one. Tooling, training programmes and full policy suites come after, not before.
How long does it take to become EU AI Act compliant?
Ninety days gets a lean team to a defensible position: known population, assigned roles, evidenced universal obligations (literacy, contracts, oversight, logs, incident route) and a sized backlog for the heavier items. Provider-side high-risk documentation can take significantly longer per system — the 90-day plan front-loads everything that does not depend on it.
What are the quick wins for AI Act compliance?
Article 4 literacy sessions with recorded attendance (a live gap since February 2025), AI clauses added to the procurement template, human-oversight roles named in operating procedures, log retention configured to six months, and one dated decision memo closing your most contested classification. Each takes days; together they cover the obligations every firm owes regardless of classification.
Which AI Act obligations can wait?
Expensive, classification-dependent items can be sequenced: technical documentation for provider systems, EU database registration, FRIA where Article 27 applies, and wholesale contract rewrites before renewal. Defer deliberately — record the item, the date and the rationale — because an undocumented delay is indistinguishable from oversight.
Who should own the 90 day AI Act compliance plan?
One person with authority to convene functions and make classification calls — typically compliance, risk or legal — supported by part-time input from IT and the business. Committees diffuse ownership; a named owner with a monthly governance rhythm and an escalation route for disputes is the structure that survives contact with reality.
Put this guide to work on your own estate.
Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.
- Free forever plan
- No credit card
- EU-hosted · GDPR-native
Build a live AI register in minutes — upgrade only when you need the audit pack.