LANDMARK · 7 MIN · STEWARD
AI procurement
After this landmark, you can list the questions an AI procurement process needs to ask before an organization adopts a third-party AI tool.
↗
This concept is shared, but the Everyday lens is less central here.
You can still explore it. We’re showing the shared explanation and a related practical view without hiding the knowledge.
Procuring an AI tool is procuring a dependency whose behavior you don’t fully control and whose failures can become your organization’s liability regardless of whose model caused them. A real AI procurement process asks what a traditional software review might skip: what data the tool sends to the vendor and where it’s processed, whether the vendor can point to evidence of testing and risk classification for their own system, what the vendor’s incident and update-notification process is, and, under the EU AI Act, whether your organization is a deployer with its own resulting obligations, not just a customer.
This is the canonical concept. It stays the same across learner lenses so personalization never changes the underlying facts.
◌ EVERYDAY LENS
What this looks like for you
Before connecting a personal or work account to a new AI tool, glance at what data it collects and where; the procurement questions below scale down to a version anyone can ask before clicking ‘allow.’
MAKE A DECISION
A company is evaluating a third-party AI tool for screening job applications; a use case that would likely be high-risk under the EU AI Act. What should procurement specifically verify before purchase?
CARRY THISFor one AI tool your organization has adopted or is considering, write down what data it sends externally and whether that was reviewed before adoption.
- Regulation (EU) 2024/1689 (Artificial Intelligence Act)Official Journal of the European Union · 2024-07-12
First-pass citations, limited to primary sources; a reviewer will broaden and verify these before this entry leaves draft.