Playbook
Vendor Due Diligence Checklist
Use this checklist before you sign with a software or AI vendor. It scales the depth of review to the data and risk involved, and shows what evidence to ask for.
Best reader
Procurement, security, legal, and product owners vetting a software or AI vendor
Outcome
A completed, evidence-backed vendor review and a clear approve, approve-with-conditions, or decline decision.
Use this sequence
Tier the vendor by the data and systems it will touch.
Check legal standing, ownership, and references.
Request security evidence and read what it actually covers.
Review data privacy terms, the processing agreement, and subprocessors.
Test continuity: backups, recovery, and exit terms.
Review delivery practice, IP terms, and change control.
Record the decision, conditions, and a re-review date.
Scale the review to the risk
A vendor that handles sensitive data needs a deeper review than one that supplies a design tool. Tier first, then ask for evidence that matches the tier.
High: sensitive data or core systems
Medium: some internal data
Low: no data access
Evidence beats answers
A questionnaire answer is a claim. A current audit report, a signed agreement, or a demonstrated control is evidence. Read the scope and exceptions, not just the cover page.
Audit reports and their scope
Penetration test summary
Data processing agreement
Subprocessor list
Plan the exit before you enter
Ask how you get your data and your code back, in what format, and how fast. A vendor that cannot answer clearly is a lock-in risk.
Data export
Code and IP ownership
Notice and transition support
Start in 60 seconds
Turn this checklist into a scoped plan.
Answer a few questions and get an AI-assisted, architect-reviewed scope, cost range, and timeline for your software project.
Frequently asked questions
Is a SOC 2 report enough?
No. It is one piece of evidence. Check that its scope covers the service you will use, that it is current, and what exceptions it lists. Then confirm the controls that apply to your own setup.
How often should you re-review a vendor?
At renewal, after a security incident or major product change, and on a schedule tied to the vendor's risk tier. Higher-risk vendors get reviewed more often.