Skip to Content
ToolsVendor Checklist

Vetting a Vendor

Use this checklist to check one AI tool, for one use, against the five things that decide what the firm may put into it. It is the companion to Vet and Choose Tools, which explains the reasoning.

What this measures

This checklist looks at one tool, for one use. It does not compare vendors or produce a short list.

It produces no score: each check has an answer and a source, and the result is a dated decision.

Before you start

Have three things in front of you: the use-case list entry this tool is meant to serve, the duty map for that use, and the cell of the data matrix it would fill — the outputs of the first three steps; build any you lack first. The matrix crosses four tiers of information — public, internal, client-identifying, and restricted — with four kinds of tool: the consumer tier of a general-purpose tool, a paid business tier of the same tool, a tool under a signed agreement, and an advisor-specific platform.

Two ground rules:

  • Read the tool’s own pages. Use its terms-of-service, data-handling, and privacy pages and any agreement offered — not a summary, review site, or sales page.
  • Check it like any other tool. An advisor-specific platform gets the same five checks, in the same order.

What to check

Work through them in this order.

CheckWhere to lookWhat a clear answer says
1. Whether inputs are used to train the modelData-handling page; plan terms; any agreementWhether what you type, paste, or upload is used to improve the service, and whether that is a setting or a commitment
2. The retention periodData-handling page; any agreementHow long inputs and outputs are kept, and what ends that period
3. Whether the vendor will sign an agreement acting as the firm’s service providerAccount terms; the agreement itselfYes or no, and what the agreement covers
4. Whether subprocessors are disclosedA published list, or the agreementThe parties the vendor passes data to, by name or by role
5. What happens to data on cancellationTerms-of-service; any agreementWhether you can take your data out, and whether the vendor deletes what it holds

On the first check, a setting someone can switch back on is weaker than a commitment in the terms; write down which you found.

On the second, the period is the vendor’s to set and change, so this guide prints none; read it from the vendor’s current terms.

On the third, a service-provider agreement is one in which the vendor handles the firm’s data on the firm’s behalf. Write down whether each commitment sits in that agreement or only on a public page. For an SEC-registered adviser, Regulation S-P’s safeguards rule requires the firm’s policies to cover oversight of a service provider, including how quickly it must report a breach to the firm (17 CFR 248.30(a)(5) ) — see Vendor Oversight in this year’s figures. A state-registered adviser is under the FTC Safeguards Rule  and its state’s requirements instead. That rule asks the firm to pick providers able to protect the information, to write those protections into the contract, and to reassess each provider from time to time, according to its risk (16 CFR 314.4(f)).

On the fourth, a readable list counts as disclosure; a reference to unnamed partners does not.

What you found

For each check, write the answer as the tool’s own pages state it and name the document it came from. Where a page is silent, write “not stated”. The example below is a fictional note-summarizing tool, checked by an adviser named Pat Example for summarizing client meetings; the meeting notes it takes in are client-identifying information.

CheckWhat the terms sayWhere it is written
1. TrainingInputs are not used to trainSigned agreement
2. RetentionKept for a stated period, then deletedData-handling page
3. Service-provider agreementSigned; covers this useSigned agreement
4. SubprocessorsPublished list, by namePublic subprocessor page
5. CancellationNot stated—

Watch the third column: “Your decision” turns on which answers sit in a signed agreement. Date the whole table on the day you read the pages.

Your decision

Start from the tier in the data matrix cell. Public or internal information may go into any of the four kinds of tool. Client-identifying information needs a tool under a signed agreement that covers this use, or de-identifying before it goes in; restricted information — client-identifying information the firm has promised, in writing or by rule, to handle a set way — needs that agreement, and only if the promise allows the use. A public terms page alone qualifies for neither. The guide sets no pass mark for the training, retention, subprocessor, and cancellation answers: the tier and the signed agreement set the bar. Record all four; any answer the approver cannot accept for this use becomes a condition or a decline. A “not stated” on any check is not a pass: ask the vendor, and approve at most on the condition that the answer arrives in writing.

DecisionWhen it fitsWhat you write down
Approve for this useEvery check has an answer, and the tool meets the bar for this tierThe use, the tier, the approver, the date
Approve with a conditionThe tool clears only once something changes, such as a setting switched off, an agreement signed, or a missing answer put in writingThe condition, and who confirms it is met
DeclineThe tool cannot meet the bar for this tier, or the vendor will not put the answer in writingThe check that failed

Then add two lines:

  • Who approves. Name the person in the firm who can approve a new tool. The approval refers to the use-case list, the duty map, and the data matrix by name, not “looks fine to me.”
  • When it is checked again. Set a re-check trigger: a material change to the tool’s terms, a new use proposed for it, or a fixed review interval the firm chooses — whichever comes first.

In the example, cancellation reads “not stated,” so the decision is approve with a condition: that answer, in writing, before client information goes in.

What this checklist does and does not tell you

It tells you whether this tool clears the bar for this one use, on the terms you read.

It does not tell you whether the tool does the task well, or how it ranks against another tool. It says nothing about your fiduciary duty to the client, which stays with the firm whatever tool did the drafting.

And it is true only on the date you read the pages.

What to do with it

Date the checklist, sign the decision, and keep it with the firm’s working files. It is the kind of record a firm may be asked to show in an examination.

Keep each dated copy. Where the checklist is a record the firm has to keep, how long it keeps it is set by rule — see Records and Documentation in this year’s figures — and a state-registered adviser checks what its own state requires.

If what you found puts the tool in a different category than you assumed, move it to the right row of your tool list before anyone uses it. Then carry the approved tool, and any condition on it, into Write the AI Policy.

At a larger firm

At a larger firm, tool approval usually runs through a vendor management or IT security process the adviser does not own. Use this checklist to prepare what you bring to that process — the use, the tier, and the duties it touches — not to replace it. The firm may already hold a negotiated agreement with the vendor, so ask for it before reading public pages. Approval of a tool for someone else’s use is not approval for yours.