EU AI Act Vendor Contract Clauses to Demand: A Buyer's Redline Guide

A "yes" on a vendor questionnaire has no remedy attached. A clause does. When a high-risk AI buy goes wrong, the question an auditor or market surveillance authority asks is not what the supplier promised in a sales call — it is what the signed contract obliges it to hand over. This guide is the contract layer: clause-by-clause, redline-style drafting guidance with fallback positions and a clause table that turn your diligence findings into binding obligations. It sits below the AI procurement policy and the AI vendor questionnaire template, and covers contracts under Regulation (EU) 2024/1689.

---

Why the Contract — Not the Questionnaire — Carries Your EU AI Act Exposure

Three layers do three different jobs, and confusing them is how exposure slips through. The procurement policy decides which buys get scrutinised and who signs off; the questionnaire collects the vendor's answers; the contract converts those findings into enforceable obligations.

A deployer's own obligations under Article 26 — intended-purpose use, human oversight, monitoring, and log retention — cannot be met on inputs the vendor controls: the Annex IV technical documentation, the Article 13 instructions for use, the logs, and the incident facts all originate with the supplier. The contract secures those as a legal right.

The penalty exposure the clauses protect

The fines behind these clauses are real. Breach of provider or deployer obligations draws fines up to €15 million or 3% of total worldwide annual turnover, whichever is higher (Article 99(4)). Prohibited-practice breaches reach up to €35 million or 7% (Article 99(3)). Supplying incorrect, incomplete or misleading information to authorities draws up to €7.5 million or 1% (Article 99(5)). For SMEs and start-ups, Article 99(6) caps each fine at the lower of the two.

"Vendor" is not a legal category

The Act attaches obligations to named roles, not to "vendors". A provider carries the obligations in Article 16; a deployer carries those in Article 26; an importer (Article 23) and a distributor (Article 24) each hold separate duties. The clauses below make the supplier warrant which role it holds and that it discharges that role's obligations. Scope the clause depth to the risk tier: high-risk Annex III buys take the full set; limited- and minimal-risk buys take a trimmed set, because over-papering a low-risk purchase gets the process routed around.

---

Clause 1 — Documentation, Instructions-for-Use and Conformity Evidence Access

Demand a right to obtain and retain the Annex IV technical documentation (or an adequate summary), the Article 13 instructions for use, and the EU Declaration of Conformity (Article 47), plus evidence of CE marking (Article 48) and EU-database registration (Article 49). The provider draws up the Annex IV file under Article 11; your clause secures access to it.

You cannot follow instructions you were never given, nor demonstrate deployer conformity on documentation the supplier withholds. Tie delivery to a fixed timeline — within a set number of days of signature and on each material update — not "on request".

Fallback position when the vendor will only share a summary

Work a ladder: a full Annex IV file is best; a summary sufficient for Article 13 use is acceptable; a binding attestation plus an escrow or audit right is the floor. Reject "attestation only" for high-risk buys — a bare attestation carries no evidential weight without the documentation behind it.

Redline language to avoid

Strike vague phrasing such as "commercially reasonable efforts to provide documentation" or "available on request". Replace it with a hard delivery obligation and a deemed-breach trigger if documentation is not produced within the window — removing the supplier's discretion over whether you ever see the file.

---

Clause 2 — Article 25 Role Allocation and the Provider-Flip Trap

Have the contract state the supplier's role expressly — typically provider under Article 16 — and warrant that it discharges that role's obligations for the system as supplied, so liability for provider duties does not land on you.

The flip triggers to allocate

Under Article 25, a deployer, distributor or importer becomes a provider — inheriting the full Article 16 stack — if it puts its name or trademark on a high-risk system, makes a substantial modification (Article 3(23)), or changes the intended purpose so the system becomes high-risk. The flip usually fires after signing, when a team repurposes a tool, so the contract should require the vendor to flag any use it knows would trigger it.

Indemnity and re-papering on a triggered flip

Pair the role warranty with an indemnity for losses arising from the supplier mis-stating its role or failing its Article 16 duties, plus a re-papering obligation if a planned change reallocates roles. The deeper mechanics live in the provider vs deployer roles and Article 25 value-chain explainers.

---

Clause 3 — Change and Substantial-Modification Notification

Require advance written notice of substantial modifications (Article 3(23)), model swaps, retraining, and any intended-purpose change. Each can push a system into high-risk, trigger a fresh conformity assessment (Article 43(4)), or fire the Article 25 flip on your side.

Advance-notice window and a right to re-assess or exit

Without notification you discover reclassification during an audit, not before. Set a concrete notice window before the change takes effect, and attach a right to re-run your due diligence and to suspend or exit if it materially alters your risk tier. The clause must bind the vendor to notify you even when it considers the change non-substantial — the Article 3(23) call is yours, the deployer's.

---

Clause 4 — Incident Cooperation and the Article 73 Reporting Chain

Require the supplier to notify you of any serious incident (Article 3(49)) without undue delay, and to supply the information you need to feed the Article 73 reporting chain to the authority.

The Article 73 timelines the clause has to feed

Anchor the clause to the statutory windows. Serious incidents are reported no later than 15 days after the operator becomes aware (Article 73(2)); within 2 days for widespread infringement or serious-and-irreversible critical-infrastructure disruption (Article 73(3)); and within up to 10 days where the incident involved a person's death (Article 73(4)). The supplier's notice must land early enough that you can still meet the shortest applicable window, so set its clock to run from its own awareness and require cooperation with the authority's follow-up.

---

Clause 5 — Audit, Logging and Information Rights

Secure an audit and information right that mirrors the Act's cooperation-with-authorities posture. Article 21 obliges providers, on a reasoned request, to give authorities the information needed to demonstrate conformity; your clause buys an analogous private right to verify compliance.

Logs and post-market monitoring information

Require access to the logs the system generates automatically (Article 12), confirmation that the provider retains the logs under its control for the statutory minimum period (Article 19), and the post-market-monitoring information you need under Article 72. Specify cadence, notice, scope and cost: an unbounded "audit any time" clause gets negotiated out, while a scoped annual-plus-for-cause right survives redlining.

---

Clause 6 — Data Governance, Confidentiality and a Compliance Warranty

For high-risk systems, require evidence that training, validation and testing data meet the Article 10 data-governance practices, and align the AI clauses with the GDPR layer — a Data Processing Agreement and a transfer mechanism where data leaves the EEA.

Confidentiality over disclosed documentation

Add a confidentiality clause covering the Annex IV documentation and logs the vendor discloses. The access right in Clause 1 should not force the supplier to hand sensitive technical material into an uncontrolled environment — a balanced wrapper is what makes that clause survive negotiation.

A standing compliance warranty plus remedy

Close with a standing EU AI Act compliance warranty: the system as supplied complies with applicable obligations, and the vendor maintains compliance through the lifecycle. Back it with a remedy — cure period, suspension, indemnity, exit. A warranty without one is decoration.

---

The Clause Table: What to Demand, the Article It Maps To, and the Fallback

Each row pairs a demand with its EU AI Act anchor, the deployer duty it secures, the fallback you can accept, and the tier it applies to.

Limited- and minimal-risk buys take only the trimmed rows: transparency under Article 50 where output reaches third parties, change notification, and a basic warranty.

---

Worked Example: Redlining a High-Risk Recruitment-AI Contract at a 600-Person Employer

Northgate Talent, a 600-employee EU staffing firm, is contracting for an AI CV-screening tool. Screening sits in Annex III point 4(a) (recruitment), so it is high-risk and the full clause set applies.

The redline. Legal strikes "documentation available on commercially reasonable efforts" for a hard Annex IV-summary delivery obligation (Clause 1), adds the Article 25 role warranty plus indemnity (Clause 2), sets a 30-day advance change-notice window (Clause 3), and binds the vendor to notify serious incidents within 24 hours so Northgate can meet the Article 73(2) 15-day window (Clause 4).

The fallback accepted. The vendor will not hand over the full Annex IV file, so the parties settle on a summary sufficient for Article 13, a scoped annual audit right, and a confidentiality wrapper.

The flip anticipated. A clause requires notice before Northgate can brand or substantially modify the tool — doing so would flip it into a provider under Article 25, a risk the redline surfaces in the contract, not in an audit.

---

Timing: Which Deadlines These Clauses Have to Plan Around

Some obligations already constrain contracts today: Article 5 prohibitions and Article 4 AI literacy since 2 February 2025, and GPAI obligations (Articles 51–55) since 2 August 2025. Landing 2 December 2026 are a new CSAM/"nudifier" prohibition and Article 50 content-marking duties for synthetic output — relevant to any generative-AI contract whose output reaches third parties (these sit under the Digital Omnibus, now adopted and pending Official Journal publication). For high-risk classification, stand-alone Annex III systems (Article 6(2)) read 2 August 2026 in the statute; product-embedded Annex I systems (Article 6(1)) read 2 August 2027.

The note the contract should carry: the Digital Omnibus, adopted in June 2026 — the European Parliament voted on 16 June 2026 and the Council adopted it on 29 June 2026 — defers high-risk to 2 December 2027, with entry into force pending Official Journal publication — and the "stop the clock" variant was rejected. Draft the warranty and change-notification clauses against the adopted 2 December 2027 high-risk deadline.

---

How Confir helps

Confir maps each contract clause to the EU AI Act obligation it secures — Annex IV and Article 13 documentation access, Article 25 role allocation, Article 73 incident cooperation, and the Articles 12, 19 and 72 logging and monitoring rights — so a redline is traceable to the Article that justifies it. The synthesis engine is deterministic and rule-based — no model inference, no hallucination — so the same vendor and clause inputs always produce the same finding. Clause status feeds the same AI register the procurement policy and questionnaire feed, so a missing clause surfaces as a tracked gap rather than buried in a signed PDF.

---

Frequently asked questions

Which clauses should I demand in an AI vendor contract under the EU AI Act?

Six, scaled to risk tier. For high-risk buys: documentation and instructions-for-use access (Annex IV, Article 13); an Article 25 role-allocation clause handling the provider flip; advance change-and-modification notification; incident cooperation feeding the Article 73 reporting chain; audit, logging and information rights (Articles 12, 19, 72); and data-governance, confidentiality and a standing compliance warranty with a remedy. Limited- and minimal-risk buys take a trimmed set: transparency under Article 50, change notification, and a basic warranty.

How is this different from an AI procurement policy or a vendor questionnaire?

They sit at three layers. The procurement policy is the standing rulebook deciding which buys get scrutinised and who signs off. The questionnaire is the artefact you send to collect the vendor's answers. The contract converts those findings into enforceable obligations with remedies. A questionnaire "yes" carries no consequence; a clause does. You need all three: the policy for consistency, the questionnaire to gather facts, and the contract to make them stick.

Why does the Article 25 provider flip belong in the contract?

Under Article 25 a deployer becomes a provider — inheriting the full Article 16 obligation stack — if it puts its name or trademark on a high-risk system, makes a substantial modification (Article 3(23)), or changes the intended purpose so the system becomes high-risk. This usually happens after signing, when a team repurposes a tool. A role-allocation clause warranting the supplier's role, a duty to notify before any triggering change, and an indemnity surface the reclassification before an audit does.

What should the incident-cooperation clause require to satisfy Article 73?

It must make the supplier notify you of any serious incident (Article 3(49)) early enough that you can meet the shortest applicable reporting window to the market surveillance authority: 15 days after awareness in general (Article 73(2)), 2 days for widespread infringement or serious-and-irreversible critical-infrastructure disruption (Article 73(3)), and up to 10 days where a death occurred (Article 73(4)). Set the supplier's notice clock to run from its own awareness and require it to cooperate with the authority's follow-up.

Can I just rely on a vendor's attestation that it is compliant?

For high-risk systems, no. Article 26 requires you to verify the provider's conformity, and an attestation carries no evidential weight without the documentation behind it. Build a documentation-access clause: a right to the Annex IV file or an adequate summary sufficient for Article 13 use, delivered within a fixed window rather than "on request", plus the EU Declaration of Conformity (Article 47). A standing warranty helps only when backed by a remedy. For minimal- or limited-risk tools, a lighter posture is proportionate.

Which deadline should I draft the compliance warranty against — 2 August 2026 or 2 December 2027?

Draft against the adopted 2 December 2027 high-risk deadline. Stand-alone high-risk Annex III classification (Article 6(2)) originally read 2 August 2026 in the statute. The Digital Omnibus, adopted by the European Parliament (16 June 2026) and the Council (29 June 2026), defers it to 2 December 2027; entry into force is pending Official Journal publication, and the "stop the clock" variant was rejected.

Do these clauses apply to a SaaS product that only has an AI feature?

Yes, where the AI feature performs a function that is high-risk under Annex III — for example automated CV screening is Annex III point 4(a) whether standalone or embedded in an HRIS. Your deployer obligations under Article 26 attach to the AI feature regardless of packaging, so the documentation-access, change-notification and incident-cooperation clauses should cover it. If the supplier cannot tell you whether its AI feature has been classified, that gap is itself reason to harden the warranty and audit clauses before signing.

---

Related guides

• AI procurement policy
• AI vendor questionnaire template
• provider vs deployer roles
• Article 25 value-chain responsibilities
• AI due diligence checklist