FIELD TOOLS / 02
The AI vendor buyer checklist
Bring the same evidence request to every shortlisted team. Keep required answers open until the responsible reviewer can inspect them.
12 checks before the next commitment
| Check | Question to resolve | Suggested owner | Artifact |
|---|---|---|---|
| 01. Task boundary | One user task, permitted outputs and excluded actions | Product owner | Brief and current workflow |
| 02. Architecture fit | Build/buy rationale and a simpler baseline | Technical lead | Architecture decision and comparison scope |
| 03. Delivery team | Named role coverage, availability and substitution | Buyer engineering lead | Proposed staffing plan |
| 04. Relevant experience | Supplier role and permitted reference evidence | Procurement owner | Approved walkthrough or reference notes |
| 05. Data permission | Approved sources, purposes and environments | Data owner | Source inventory and permissions |
| 06. Access controls | Tenant, role and document boundaries | Security owner | Permission mapping and scoped demonstrations |
| 07. Evaluation | Versioned cases, rubric and held-out checks | Domain lead | Evaluation plan and reviewed outcomes |
| 08. System behavior | Tool authority, timeouts and duplicate actions | System owner | Integration and control evidence |
| 09. Commercial scope | Build, runtime, review, exclusions and change rules | Budget owner | Comparable cost schedule |
| 10. Ownership | Project assets, background IP and third-party licenses | Contract owner | Rights and deliverable inventory |
| 11. Handoff | Receiving-team access and an agreed transfer exercise | Receiving engineer | Exercise record and unresolved gaps |
| 12. Operation and exit | Support coverage, containment and access removal | Operations owner | Runbook, coverage and exit schedule |
Use three evidence states
- Verified
- The named reviewer inspected relevant evidence for the stated scope. Record its version and date.
- Open
- A required answer or artifact is missing. Assign the next action and owner; retain the uncertainty.
- Reject
- Observed evidence conflicts with a mandatory requirement. Record the conflict and affected commitment.
The CSV starts with every row open. It contains no assessments of the ten listed companies. These suggested states are a purchasing tool, not a validated rating model.
How to use the files
- Save a separate register for each supplier and the same brief version.
- Replace role labels with actual owners and choose which checks are mandatory.
- Attach or reference evidence through your approved internal process.
- Review unresolved mandatory rows before authorizing the next stage.
Downloads are static templates. Editing the saved files does not send their contents to this site. Avoid including secrets or personal data in a document shared with a supplier without the appropriate approval.