Job to be done · Vendor due diligence

Ask before the contract, not after the audit.

AI vendor due diligence belongs before you sign: buying the tool does not pass your duties to the vendor.

No card · EU-hosted · 5 minutes to a first classification
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

The reality

What procurement misses.

What we hear

“We asked for their SOC 2 and stopped there.”

What the product does

A security attestation says the vendor can hold data safely, not that you can operate the system lawfully.

What we hear

“The contract was signed before anyone asked about the model.”

What the product does

The model underneath can change the behaviour you assessed. Ask first, while you can still choose.

What we hear

“The vendor told us it was not high-risk.”

What the product does

Their classification governs their duties. Yours follow your deployment, which can be Annex III high-risk.

What you get

An AI vendor due diligence record that outlives the sales call.

01

The instructions, or the gap

Log the Art. 13 package with a dated receipt. If nothing arrived, the register shows the gap.

02

Intended purpose, written down

The stated purpose is the use you are permitted. Once recorded, later drift shows as a change.

03

The model underneath, named

Which general-purpose model, on what terms, and what happens if it changes, so someone revisits it.

04

Ready for the next buyer

When your own customers run a security review on you, the same register answers it.

In practice

Three purchases, three questions that mattered.

Use case 01

An HR team buying a CV-screening tool.

  • Annex III point 4 follows their deployment, not the sales pitch.
  • Art. 13 instructions requested before signature.
  • Oversight and the worker notice planned into the rollout.
Obligation registerDerived by the engine
12obligations applyDeployerHigh

12 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register0
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend and inform where use may present a risk
Art. 25(1)Watch for the changes that make you the provider
Computed by the engine for one system · switch the role to compare
Use case 02

A product team embedding a third-party model.

  • Which GPAI model, on what terms, and notice if it changes.
  • Whether embedding it makes them a provider under Art. 25.
  • The intended purpose recorded, so drift becomes visible.
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
Use case 03

A firm renewing a tool bought before the Act applied.

  • Renewal is the moment to classify what never was.
  • Instructions for use made a condition of renewal.
  • A vendor that cannot answer is itself the finding.
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

Also included

What sits either side of the purchase.

Straight answers

Straight answers on due diligence.

What is the single most important thing to ask a vendor?

Ask for the instructions for use. The provider of a high-risk system must supply them (Art. 13), and you must use the system in accordance with them (Art. 26). Without them, you cannot meet your own duty.

Is a CE mark enough?

No. A CE mark is the provider's claim about their own conformity. It says nothing about your oversight, input data, logging or worker notification, which stay yours under Article 26.

The vendor says they are not high-risk. Do we accept that?

Their classification governs their duties, not yours. Risk class follows intended purpose and deployment: one model can be limited risk in one use and Annex III high-risk in another.

What about GPAI models underneath the product?

Ask which general-purpose model sits underneath and on what terms, because a change there can change the behaviour you assessed. Write the answer down: if nobody records the dependency, nobody revisits it when it changes.

Where does this fit with security questionnaires?

Alongside them, as a separate check. A security review asks whether the vendor can keep data safe; this asks whether you can operate the system lawfully. Neither replaces the other.