The Vendor Compliance Checklist
Run through these before signing, or before renewing an existing contract. Each item is something you should be able to get a direct, specific answer to, not a general reassurance.
1. Can they classify the system’s risk tier?
Ask the vendor to state, in writing, which EU AI Act risk tier the system you’re commissioning falls under: prohibited, high-risk, limited-risk, or minimal-risk.
A vendor who cannot answer this specifically, or who answers with “we’ll figure that out if it comes up,” has not done the classification work the Act requires before development starts.
This matters even for a system that looks minimal-risk today. Adding one feature, like a scoring step or an automated decision, can move a system into a higher tier without anyone updating the paperwork.
Ask how the vendor re-checks classification when scope changes, not just at project kickoff.
2. Do they maintain a technical file?
For anything high-risk, the Act requires a technical file documenting how the system was built, tested, and monitored. Ask to see a redacted example from a past project.
A vendor assembling this kind of documentation for the first time, under audit pressure, produces a much weaker file than one built alongside development.
3. Who owns AI risk on their side?
There should be a named person or team, not “the engineering lead handles it when needed.”
Growing numbers of vendors now have a dedicated AI Governance Specialist role precisely because this needs continuous ownership, not an ad hoc assignment.
4. Can they name your system’s obligations under the current timeline?
A vendor who still cites the original August 2026 high-risk deadline without mentioning the Digital Omnibus delay is working from outdated information; that same vendor may also be behind on other regulatory changes that affect your system.
Regulatory currency is itself a signal of governance maturity.
5. How do they document model evaluation?
Ask what their evaluation process looks like and who signs off on it. If the answer is entirely automated with no human review step, that is a gap for anything high-risk.
Some vendors now route this through a dedicated AI Evaluator & Trainer function rather than leaving it to whoever built the model.
6. What is their data lineage and permissioning story?
Ask where training and fine-tuning data came from, and how they know it was permissioned for that use.
This overlaps with GDPR wherever personal data is involved, and a vendor with a clean answer here usually has the rest of their governance program in reasonable shape too.
7. Do they carry their own AI liability coverage or contractual indemnity?
This will not remove your own legal exposure as the deploying company, but it tells you whether the vendor has priced their own risk realistically.
In-house legal teams can confirm what that indemnity actually covers by running the vendor’s agreement through AI-assisted contract analysis before signing.
A vendor who has never considered this has probably not considered much else on this list either.