Selling AI to the EU public sector: procurement requirements under the AI Act
Two audiences, one regulation: bidders need the evidence pack tender teams now score, public authorities carry deployer duties on their own systems. What each side must produce, and how contract dates collide with the 2027 duty dates.
Public procurement was one of the first places the EU AI Act turned from theory into scorecards. A municipality buying an AI-assisted permit-triage tool, a health service deploying risk-prediction software, a ministry evaluating CV-screening bids — each of these now sits on both sides of the Act at once: the authority carries deployer duties for the systems it operates, while its suppliers must evidence provider compliance for the systems it sells. For mid-market vendors, that double exposure is the single biggest structural change to government AI selling since framework contracts went digital.
What public authorities actually owe as deployers
When a public body puts a high-risk AI system into service, Article 26 deploys the full deployer duty set onto the authority itself — and none of it can be contracted away:
- Use it as instructed, within the documented intended purpose and performance limits.
- Assign human oversight to named, competent individuals — not an anonymous “case team”.
- Ensure input data is relevant and representative for the context of use, checked before go-live.
- Inform affected persons that a high-risk system is in the decision path — for a public authority this is an express, non-negotiable transparency duty, not a privacy-notice nicety.
- Keep the logs the system generates, retrievable for inspection.
- Consult workers’ representatives before workplace deployment where national law or Article 26(7) requires it.
- Register the use in the EU database where the applicable entries apply — with additional entries for systems used by public authorities under Article 49.
Two further layers attach to public bodies: a fundamental rights impact assessment where the conditions apply (organisations governed by public law are squarely in scope), and, for the authority itself, procurement law that increasingly treats AI compliance as an award criterion rather than a post-award deliverable.
The practical consequence for bidders: the authority’s own compliance team will ask you for the artefacts that let them discharge these duties. Your bid is scored less on AI novelty than on whether their Article 26 file can be assembled from what you hand over.
How tenders encode AI Act compliance
Across EU contracting authorities, the same five evidence requests recur — learn to answer them proactively:
| Tender question | What they are really asking | Where the answer lives |
|---|---|---|
| “Confirm the provider and deployer roles for this solution” | Who carries which duties — and whether our authority accidentally becomes a provider (Art. 25) | Role declaration naming the regulation and your Article 3 position |
| “Provide the conformity assessment status / declaration” | Is the system lawfully placeable on the market? | EU declaration of conformity, internal-control record, or notified-body certificate |
| “Supply the EU database registration reference” | Can we verify registration before go-live? | Registration confirmation with timestamp |
| “Describe human oversight, logging and incident handling” | Can we run Art. 26 duties with what you give us? | Instructions for use, oversight design, logging spec, Art. 73 cooperation SLA |
| “Provide your data governance and bias evidence” | Input-data duties and fundamental-rights risk | Data-governance summary, evaluation results, FRIA inputs where required |
Award criteria have shifted accordingly: technical suitability now routinely includes “demonstrated compliance with Regulation (EU) 2024/1689”, and quality scores reward evidence maturity — documentation indexes, evaluation reports, post-market monitoring plans — over feature checklists. The vendors winning 2026 framework lots are the ones whose compliance file fits inside the bid pack without a follow-up clarification round.
What belongs in the bid pack
For a mid-market AI vendor, the standing evidence pack is worth assembling once and reusing across every ITT:
- Role declaration — one page per product: provider position, intended purpose, Annex III classification (or documented minimal-risk rationale).
- Conformity evidence — declaration of conformity for the applicable route, or, for systems not yet in the high-risk obligation window, a dated roadmap against the commencement dates.
- Registration status — EU database entry where required; otherwise an honest statement of what triggers it.
- Instructions for use — the document your customer’s oversight staff will actually operate from; treat tender-scoring value and legal duty as the same thing.
- Logging and incident specification — what is recorded, retention, export formats, and your Article 73 cooperation commitment with a specific response window (five business days is a market-standard ask).
- Data-governance summary — training/evaluation data categories, bias evaluation approach, subprocessors.
- Roadmap against the calendar — how product updates land before or after the applicable duty dates.
Bidding with a roadmap instead of a certificate is legitimate — hiding the gap is not. Contracting authorities can accept phased compliance where the law’s own timetable allows it; what they cannot accept is discovering at contract signature that a 2027 obligation has no owner on either side.
The timing trap: contracts signed in 2026, duties landing in 2027
The general applicability regime — transparency duties, authorities’ powers, penalties — runs from 2 August 2026, while the full Annex III high-risk obligation set follows the adjusted timetable around 2 August 2027 (confirm the current commencement date against the published regulation before fixing contractual dates — the Digital Omnibus process moved them once already). Public contracts signed in 2026 typically run three to five years, which means:
- Every agreement you sign now outlives the pre-AI-Act world. Embed a compliance-change clause: who re-assesses, who re-registers, who pays for conformity work when the duties bite mid-contract.
- Delivery milestones should align to duty dates. A system going live in mid-2027 needs its conformity and registration evidence at go-live, not at contract award — write the milestone accordingly.
- Warranty periods should survive commencement. Vendor warranties on provider status and documentation access are worth little if they expire before the obligations they warrant take effect.
Authorities that have already run one AI procurement will ask for these clauses unprompted. Offering them first signals that you have done this before — which, in a scored tender, is its own advantage.
Working with the authority: the operating rhythm
Winning is not the finish line; the deployer duties make your post-award support model part of the compliance answer:
- Onboarding artefacts, not slideware. Deliver the instructions of use, oversight configuration and logging setup as acceptance deliverables with dates — the authority’s fundamental rights impact assessment depends on them.
- Named incident contacts on both sides. Serious-incident clocks run in days; an escalation card (who, when, through which channel) belongs in the implementation plan.
- Change notification as a service commitment. Model updates that shift behaviour trigger the authority’s re-assessment — a thirty-day advance notice with a stated re-classification position is the clause counterpart to a runbook.
- Joint register upkeep. Their AI register row and your product record should cross-reference; when an inspector writes to the authority, matching identifiers are what makes the response fast.
How to check your own position in three minutes
The free exposure scan asks twelve questions about your AI usage and governance and returns an exposure score, your ranked exposures with the exact article that fired, and your first three moves mapped to the dates that apply. Confirm your email and the full report unlocks.
Frequently asked questions
Do public authorities get special treatment under the AI Act?
No — they get extra duties. Deployers that are public-law bodies carry the standard Article 26 set plus express notification duties towards affected persons and, where conditions apply, a fundamental rights impact assessment. Registration in the EU database also has additional entries for public-authority use. Nothing about buying from a compliant vendor transfers those duties away.
Can we win a government AI contract before our conformity work is finished?
Yes, where the legal timetable itself allows phased compliance — tendering authorities can accept a documented roadmap with dates tied to the commencement schedule. What fails evaluation is an unexplained gap: no role declaration, no registration plan, no answer for what happens at the 2027 duty dates. Show the path and the dates, not just the ambition.
What is the fastest way to lose a public-sector AI tender?
Missing clarifications. Contracting authorities that score AI compliance run a clarification round when a bid lacks the conformity status, registration reference or oversight description — vendors that answer with a complete artefact list in round one effectively move their score up, while vendors needing two rounds look unprepared regardless of technical merit.
Is an EU database registration number required to bid?
Where the system is high-risk and registration applies, yes — the authority needs the reference before putting it into service, and tender teams increasingly request it at bid stage. For systems outside the high-risk window, state which article governs your registration trigger and when you will hold the reference; honesty with dates outranks a blank field.
How do contract clauses handle duties that start after go-live?
Through a compliance-change clause: an obligation to re-assess on commencement of applicable duties, allocation of who performs and who funds the work, and notice periods for both sides. Pair it with a warranty period that survives commencement — otherwise the vendor’s provider-status warranty lapses exactly when it starts to matter.
What should a public authority’s tender do differently from a private buyer’s?
Ask for the same artefacts plus two: the deployer-side package the authority itself will need (instructions of use, oversight design, logging export, incident card — its Article 26 evidence), and the inputs for its fundamental rights impact assessment. Private buyers rarely need the second; public buyers cannot complete theirs without it.
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.