ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

How should you prepare EU Annex III evidence for automated decisions — before the duties apply?

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. Prepare the file, don't claim the compliance. The EU pack in ReviewDesk projects the same decision trace into an Annex III arrangement and labels it preparatory evidence, because the high-risk duties it anticipates apply on 2 December 2027. The work worth doing now is the work that cannot be backdated: decision traces filed at decision time, scope worksheets kept current, and records that will already be a year deep when the duties land.

What is EU Annex III evidence preparation?

EU Annex III evidence preparation is the advance assembly of decision records for the categories of high-risk AI use that the EU framework lists in its Annex III — areas such as employment, creditworthiness, and access to essential services — ahead of the duties' application on 2 December 2027, the date ReviewDesk uses. In ReviewDesk, the EU pack is the third projection of a decision trace, explicitly labelled preparatory.

Why prepare for a duty that has not landed?

Because evidence has a birth date. When the duties apply, the organisations that cope will be those whose records began before the deadline — traces filed contemporaneously, scope determinations made when the systems were deployed, review histories accumulated through real cases. None of that can be manufactured retrospectively with any credibility. Preparation is therefore not early compliance theatre; it is the decision to start the clock on your own records while starting is cheap.

There is also a portfolio argument. Businesses already running Colorado and California workflows hold most of the raw material: one trace, honestly kept, projects into the EU arrangement with no new instrumentation. The marginal cost of the third pack is attention, not infrastructure — which is precisely how ReviewDesk designed the engine, as the evidence-pack guide explains. The question is never whether you can afford to prepare; it is whether you can afford to arrive in December 2027 with a record that starts that morning.

What does 'preparatory' honestly mean?

It means the pack is framed for the Annex III file as ReviewDesk understands the coming duties, without claiming that those duties are currently in force or that the pack satisfies them. The label travels with the pack — in its title, not a footnote — so that no reader, internal or external, can mistake preparation for certification. That honesty is protective in both directions: it stops your own teams from relaxing into a false 'EU handled' state, and it stops the pack from becoming a misrepresentation if it is ever shown outside the building.

Hold the same line in sales and procurement conversations. If your EU-facing customers ask about readiness, the accurate answer — traces running, scope worksheets current, pack labelled preparatory pending the December 2027 application — is also the most impressive one, because it demonstrates that you understand the difference between evidence and assertion. The wider honesty discipline is the subject of the not-recorded guide.

Which decision types deserve EU preparation first?

The ones where your existing regimes already bite and the Annex III territory plainly overlaps: employment screening and management, creditworthiness assessment, and access decisions for essential services and benefits. If a workflow already generates traces for Colorado or California, its EU pack should be switched on and reviewed — the scope worksheet gains its EU line, and the determination language is recorded per regime rather than assumed to transfer. Do not assume a Colorado scope answer is the EU answer; record each on its own terms.

Lower-priority territory can wait for the framework's own clarifications, but the inventory cannot. List every Annex III-adjacent use now, mark which already produce traces, and let the gap list drive the instrumentation order. The inventory method mirrors the ADMT census in the ADMT definition guide — classify uses, not products, and file the judgements with dates.

What should the file contain when the duties land?

The same skeleton the other packs use, because good evidence converges: the decision trace with factors and outcome, the scope determination, the notice position, the human-review availability and its history. Where the EU frame will ask its own emphases — documentation of the system, logging, human oversight arrangements — the underlying facts are the ones your traces already hold, provided the oversight story is real: named reviewers, recorded outcomes, the decision history the inbox accumulates.

Gaps, again, render as not recorded. A trace history that begins in your preparation year will show a clean start rather than a suspiciously perfect retro-history — which is exactly what a reviewer would hope to see from an organisation that prepared honestly. Perfection assembled at the deadline is the one pattern experienced reviewers discount on sight.

How do the three regimes' timelines interleave?

California's regulations took effect 1 January 2026 with compliance from 1 January 2027; Colorado's SB 26-189 takes effect the same day; the EU duties in this frame apply 2 December 2027; California's first annual risk assessment lands 1 April 2028. Sequenced that way, 2027 is the year of living records: the US workflows go live and begin generating the history that the EU file and the first risk assessment will both consume. The full calendar is drawn in the deadlines calendar.

Staffing follows the same sequence. The team that learns trace discipline on the Colorado workflow in January is the team that reviews the first EU packs in the autumn — competence compounds when the regimes are run as one programme with three projections, which is the architectural bet behind the entire evidence engine.

What should you explicitly not do yet?

Do not label any product, page or pack as EU-compliant. Do not promise customers Annex III certification. Do not let the preparatory pack's existence shorten the US work — the duties in force deserve the first hours. And do not freeze your EU preparation at today's understanding: the pack is a living projection, and when official detail firms up, the arrangement will move. Preparation that cannot be revised is just early error, preserved.

Do, instead, the boring irreversible good: keep filing traces, keep worksheets current, keep review histories real, and read the EU pack quarterly with the same gap-hunting eye you apply to the Colorado pack. When December 2027 arrives, the organisations in trouble will be those starting their records. Yours will be a year old and verifiable — which was the entire point of starting early.

Your five actions for EU Annex III evidence preparation

  1. Switch on the EU pack for every workflow already traced for Colorado or California, and read it quarterly for gaps.
  2. Keep the word 'preparatory' attached to the pack everywhere it appears — no compliance claims before 2 December 2027.
  3. Record scope determinations per regime; never assume a US answer transfers to the EU line automatically.
  4. Inventory all Annex III-adjacent uses now and instrument them in gap order.
  5. Spend first hours on the duties already in force — Illinois now, Colorado and California from 1 January 2027.

Worked example: a lender prepares its EU file a year early

A fictional digital lender — NorthLoop Finance — offers small-business credit in the US and is preparing an EU launch through a partner in 2027. Its US workflows already file traces for every credit banding. In spring 2027 it enables the EU pack on those workflows: the projections render, the scope worksheets gain EU determinations, and the first quarterly read finds the expected gaps — human-oversight descriptions thinner than the US packs', because the review bench was built for US volumes.

By the time the partner's due-diligence team reviews the file in autumn, the pack shows eight months of traces, two refreshed scope determinations and a review history with real outcomes — all labelled preparatory, none of it claiming a duty not yet in force. The partner's reviewers later say the label was what convinced them: a supplier who will not overclaim a future duty is a supplier whose present claims can be trusted.

Frequently asked questions

When do the EU duties in this frame apply?

ReviewDesk labels the EU pack preparatory until the high-risk duties apply on 2 December 2027. Until then the pack is preparation — evidence assembled in the Annex III arrangement, not a compliance claim.

Why prepare evidence before the duties apply?

Because records cannot be backdated credibly. Traces filed at decision time, current scope worksheets and real review histories will already be a year deep when the duties land, if you start when your US workflows start.

What does the EU pack contain?

The same decision trace projected into the Annex III arrangement: factors, outcome, model version, notice and review elements as recorded, with the scope worksheet — and gaps rendered as 'not recorded', never invented.

Can we describe ourselves as EU-compliant using the pack?

No. The pack is explicitly preparatory. Describing it as compliance before the duties apply would misrepresent it — the label is part of the pack precisely to prevent that.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. Dates are as used in ReviewDesk's own pages; consult counsel for your EU position.

Keep reading: How do you let someone correct wrong data after an adverse automated decision? · How do you write principal reasons for an adverse decision that a person can actually use? · What must you tell job applicants when a hiring algorithm screens them? · How do ADMT notice and review duties apply to automated credit decisions? · What must landlords and screening services disclose when screening is automated? · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.