StackLift
All playbooks

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

1

Tier the vendor by the data and systems it will touch.

2

Check legal standing, ownership, and references.

3

Request security evidence and read what it actually covers.

4

Review data privacy terms, the processing agreement, and subprocessors.

5

Test continuity: backups, recovery, and exit terms.

6

Review delivery practice, IP terms, and change control.

7

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.

The complete guide

Vendor Due Diligence Checklist: the complete guide

Updated November 18, 2026 ยท Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A vendor due diligence checklist reviews a software or AI supplier across legal standing, financial health, security, data privacy, subprocessors, business continuity, delivery practice, and exit terms. Scale the depth to the data and systems the vendor will touch, ask for evidence rather than answers, and record a decision with conditions.

What is vendor due diligence?

Vendor due diligence is the review you do before you rely on a supplier. For software and AI, the supplier may hold your data, run part of your product, or write code you will own. A review tells you whether you can trust them with that role and what conditions to attach.

It is not one form. Security teams use a technical questionnaire, procurement and legal use a business and contract questionnaire, and a third-party risk review combines both. Treat the checklist below as a starting set and add what your industry or regulator requires. It gives you structure, not legal advice.

How deep should the review go?

Review depth should follow risk. A vendor that handles sensitive customer data or runs a core system needs far more evidence than one that supplies a low-stakes tool. Tier the vendor first, so you do not burn weeks on small suppliers or skim the one that matters.

Risk tiers and the review that fits
TierTypical vendorReview depth
HighHandles sensitive or regulated data, runs a core system, or has privileged access to your environmentFull checklist, current audit evidence, a penetration test summary, a signed data processing agreement, continuity plan, reference calls
MediumHandles some internal or customer data in a limited wayShorter questionnaire, security evidence, data terms, subprocessor list
LowNo access to data or systemsBasic legal and commercial check

Write down the tier and the reason. When the vendor's role changes, for example when a tool starts to process personal data, move it up and review again.

What should the vendor due diligence checklist cover?

The checklist below groups the common domains. For each row, note the evidence you received and who reviewed it. Mark each item pass, pass with a condition, or fail.

Vendor due diligence checklist
DomainWhat to checkEvidence to request
Legal and corporateRegistered entity, ownership, jurisdiction, litigation historyRegistration details, ownership statement
Financial viabilityCan the vendor stay in business for the length of your contractFinancial statements or a statement of standing, customer concentration
Information securityAccess control, encryption, patching, logging, secure developmentSecurity policy, audit report with scope, penetration test summary
Data privacyWhat personal data is processed, where, why, and for how longData processing agreement, privacy policy, data location statement
Subprocessors and fourth partiesWho else touches your dataCurrent subprocessor list and change notification terms
Business continuityBackups, recovery targets, incident responseContinuity plan, restore test evidence, incident process
Delivery practiceTesting, code review, release control, change managementProcess documents, sample reports, a demonstration
IP and ownershipWho owns the code, data, and models you pay forContract clauses, open-source and third-party component policy
AI-specificWhich models and providers, what data goes to them, retention and training useModel and provider list, data handling terms, review process for outputs
ReferencesSimilar work, outcomes, how problems were handledTwo or three references you can call
ExitHow you get data and code back, and how quicklyExport formats, transition support terms

How do you run the review, step by step?

  1. Define what the vendor will do and which data and systems it touches. Output: a one-paragraph scope of the relationship.
  2. Assign a tier and a review owner. Output: a recorded tier with the reason.
  3. Send the questionnaire and evidence request, with a deadline. Output: a package of answers and documents.
  4. Read the evidence, not just the answers. Output: notes on scope, dates, and exceptions for each document.
  5. Hold a call to clarify gaps and test the answers. Output: a list of open items.
  6. Check references and public records. Output: confirmation of delivery history.
  7. Decide: approve, approve with conditions, or decline. Output: a signed record of the decision.
  8. Set a re-review date and add conditions to the contract. Output: obligations the vendor has agreed to.

If you are choosing between several vendors, run the lighter parts of this checklist on all of them and the full version on the finalists. The software RFP template shows how to collect comparable answers up front.

How do you read security evidence such as an audit report?

Collecting a report is the start of the work. A security audit report such as a SOC 2 report is only useful if you check what it covers. Read who issued it, which service and period it covers, which controls were tested, and what exceptions the auditor noted. A report that covers a different product, or is out of date, tells you little about the service you will use.

What to check in a security report
QuestionWhy it matters
Does the scope include the service and systems you will useA report on a different product does not cover yours
Is it current, and has anything changed sinceControls drift, and a stale report can mislead
What exceptions did the auditor noteExceptions show where controls failed in testing
Which controls are left to youSome controls are the customer's job, such as access settings
Is there independent testing of the applicationA penetration test summary shows what an attacker could reach

Even a clean report does not replace your own checks. Confirm that the settings and permissions in your own account match your needs. For your own launch controls, see the production readiness checklist.

What should you confirm about data privacy and subprocessors?

Ask what data the vendor will process, for what purpose, where it is stored, how long it is kept, and who else can reach it. A data processing agreement should state these terms, and many privacy laws require one when a vendor processes personal data for you. A subprocessor list names the other companies the vendor uses, such as a cloud host or an AI model provider.

  • A signed data processing agreement with the purpose, security measures, and breach notice terms.
  • A current subprocessor list and a promise to tell you before it changes.
  • Data location and any transfers across borders, with the legal basis.
  • Retention and deletion: how you request deletion and how it is proven.
  • Whether your data is used to train models, and a written answer in the contract.
  • Breach notification: how quickly and through whom the vendor tells you.

Your legal team should confirm which laws apply to you. The checklist only makes sure the right questions are asked and answered in writing. Our security page describes how StackLift approaches delivery controls.

What extra checks apply to AI vendors?

AI vendors add questions beyond the standard set. The vendor may pass your data to a model provider, store prompts, or let an agent act in your systems. Ask where each of those happens and what controls limit it.

Additional checks for AI vendors
TopicAskWhy
Model providersWhich models and providers are used, and can they change without noticeYour data may reach another company
Data useIs customer data retained, logged, or used for trainingPrevents surprise reuse of your content
Output reviewWho checks outputs, and where does a person approveAI can be wrong in confident ways
EvaluationHow is quality tested before and after changesModels and prompts change over time
Agent permissionsWhat can an agent read, write, or send, and what is blockedLimits the damage from a mistake
Cost controlsHow is usage metered and cappedPrevents runaway spend

The AI agent evaluation checklist lists what a vendor should be able to show you, and the enterprise AI readiness checklist covers your side of the work.

What should you check when the vendor builds software for you?

A development partner holds your code, your designs, and often your access. The risks differ from those of a software subscription. Look at who owns what, how work is controlled, and how you can leave.

  • Code lives in repositories your organization controls, with full history, from the first day.
  • Work is reviewed and tested, and releases go through a pipeline you can see.
  • Scope, change requests, and approvals are written down, with a clear change request path.
  • Production secrets are never shared with individuals or kept in code.
  • Handover terms and documentation are agreed in advance. See the software handover checklist.
  • AI tool use in delivery is disclosed, with human review of what the tools produce.

At StackLift, agents work on feature branches, never push to the default branch, and never touch production secrets. Clients see live project state, approvals, invoices, and releases in the client portal. Use the same questions with any partner, including us. To compare approaches, read in-house vs outsourced development.

How do you decide, and keep watching after you sign?

A review ends in one of three outcomes: approve, approve with conditions, or decline. Conditions are things the vendor must do by a date, such as delivering a missing document. Record who decided and why. Then put the review dates in a calendar, because risk changes after you sign.

Ongoing monitoring
TriggerAction
Contract renewalRepeat the review, focused on what changed
Security incident at the vendorRequest an incident report and confirm what data was affected
New feature or change of subprocessorCheck data handling and update the record
Change in the data you sendMove the vendor to a higher tier if needed
Missed conditionEscalate and set a firm date

If you want help reviewing a delivery partner or scoping a build with clear ownership terms, contact us or start with the free estimate.

Questions people ask

What documents should you ask a software vendor for?

A current security audit report with its scope, a penetration test summary, a data processing agreement, a subprocessor list, a continuity and incident plan, proof of insurance if relevant, and references. Ask for what matches the risk tier.

Is a SOC 2 report or ISO certificate enough?

No. It is one piece of evidence. Check that it covers the service you will use, that it is current, and what exceptions it lists. Then confirm the controls that depend on your own configuration.

How long does vendor due diligence take?

It depends on the tier and how quickly the vendor responds. A low-tier check can take a day. A high-tier review with evidence, calls, and legal terms often takes weeks, so start before you need to sign.

What is the difference between a security questionnaire and a due diligence questionnaire?

A security questionnaire covers technical controls. A due diligence questionnaire covers business, financial, and contract matters, and is usually run by procurement or legal. Many teams combine both into one third-party risk review.

What is a subprocessor?

A subprocessor is another company the vendor uses to process your data on your behalf, such as a cloud host or an AI model provider. You should be able to see the list and be told when it changes.

When should you re-review a vendor?

At renewal, after a security incident or major product change, when the data you share changes, and on a schedule tied to the tier. Higher-risk vendors are reviewed more often.

Can a small vendor pass due diligence?

Yes. Size is not the test. A small vendor can show clear controls, honest answers, and sound terms. Judge the evidence and the match to your risk, and use conditions where a gap is fixable.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.