Skip to Content

Vendor Oversight

Vet and Choose Tools owns the decision to adopt a tool: the questions to ask, how to weigh the answers, whether to proceed. This Firm Function owns everything after that decision. Vetting is a moment and oversight is a duration, and the gap between them is the whole subject — because the product a firm evaluated is not reliably the product it is using a year later, and nothing about that change has to pass through the firm to happen.

Key ideas

Vetting has a shelf life

This is the asymmetry that makes AI vendors different from conventional software vendors. The underlying model behind a product can be replaced, upgraded, or retired. Capabilities appear that change what the tool does with what it is given. Defaults shift. Features that were opt-in become standard. None of this requires the firm to install anything, accept anything, or click anything — it arrives through a service the firm is already using, usually announced in a changelog nobody in a two-person firm is reading. A conventional software vendor mostly changes the product when the firm chooses to update it. An AI vendor changes it underneath. So a decision to adopt is not a permanent finding; it is a finding with an expiry the firm never sees printed anywhere.

Terms change unilaterally, and the notice is a page update

The firm’s obligations do not move on the vendor’s schedule, and they do not care how the vendor chose to tell it. A revised data-handling page is a complete notice as far as most vendors are concerned, whether or not anyone at the firm saw it. The practical consequence is that the firm has to decide for itself what events send it back to the terms, rather than waiting to be told something changed. Compliance and Supervision covers that trigger habit and how it relates to the required review cadence.

There is a chain behind the vendor

A tool is rarely one party. A product may route requests to a separate model provider, keep data with an infrastructure provider, and pass information through services the firm never chose and cannot name. These downstream parties — subprocessors, in the language most terms pages use — inherit access to whatever the firm sends, on terms the firm negotiated with someone else. Automation platforms are the sharp case, because they sit between the firm’s other systems by design, which means they touch nearly everything the firm handles rather than one workflow. Oversight of a vendor that is really a chain means knowing whether the chain is disclosed at all, and noticing when it changes.

None of that chain absorbs the firm’s own obligations. Where customer information is compromised, Regulation S-P’s safeguards rule  leaves the firm responsible for making sure affected individuals are told, even if a provider does the work or an agreement has the provider send the notices. A vendor can be engaged to do the work. The responsibility for it having been done stays where it was.

Exit, which almost nobody plans

Oversight includes knowing whether the firm can leave. Whether stored history comes out in a form that is usable somewhere else, what happens to it on termination or a downgrade to a cheaper plan, and how long access survives a lapsed subscription are all questions with answers, and the answers are much easier to get before the firm needs them. Records and Documentation covers the other half of this — whether the firm can produce a record it is holding. This page covers the half about getting out: the firm’s ability to stop using a vendor without losing what it built there.

The free and consumer tiers are the hardest to oversee

Firms treat these as the easy case and they are the opposite. There is usually no contract to negotiate, no notice obligation running to the firm, no account manager to ask, and no counterparty with any duty to explain a change. The firm’s entire leverage is the decision to use the tool or not to. That means oversight of a consumer tier has to happen before and instead of a relationship rather than within one — checking on a schedule the firm sets, because no one is going to prompt it, and being prepared to stop using something rather than to raise an issue about it.

Due diligence is itself documentation

What the firm looked at, what it concluded, and when is the only evidence the oversight happened at all. Oversight that leaves no trace is indistinguishable afterward from oversight that did not happen. Some of this is obligation and some of it is sound practice, and the distinction is worth keeping: Regulation S-P’s safeguards rule reaches oversight of service providers that handle customer information, while a dated note recording why the firm re-checked a tool in a quiet month is simply good practice. Records and Documentation covers the recordkeeping side of both.

Concentration multiplies all of it

Operations and Back Office argues that routing everything through one tool turns a single vendor’s failure into a firm-wide one. The narrower point here: concentration risk raises the cost of every item above, because one vendor’s model change, terms revision, or subprocessor addition now lands on every workflow at once rather than on one.

Where it shows up in the process

  • Sort Your Data: The tool categories the data matrix rests on are themselves vendor facts, so the matrix quietly ages whenever a vendor changes what it does with inputs.
  • Vet and Choose Tools: That step ends in a decision; this Firm Function starts at the same moment, because the decision begins aging as soon as it is made.
  • Review and Keep Records: The scheduled review is the backstop that catches vendor drift when nothing prompted a look sooner.

Common misconceptions

  • “We vetted it before we adopted it, so it’s covered.” Vetting establishes what was true on a date. It says nothing about what is true now, and with these products the gap is wider than with most software.
  • “The terms haven’t changed, or we’d have heard.” Most vendors change terms by updating a page. Not hearing about it is the expected outcome, not evidence that nothing happened.
  • “It’s one vendor, so one set of terms.” The vendor the firm contracted with may pass data to parties the firm has never evaluated and cannot see.
  • “We can export our data whenever we want.” Possibly — on the current plan, while the account is active, in whatever format the vendor offers. Each of those conditions is one the vendor controls and can change.

At a larger firm, this is somebody’s function: procurement and vendor risk management, contracts that carry notice provisions and sometimes audit rights, and a person whose job includes noticing when a vendor changes something. The firm has standing to be told, and occasionally standing to object. A small firm takes the terms as offered, has no notice rights at all, and cannot negotiate anything — so its real control is choosing and re-choosing, which is a weaker instrument and worth naming as weaker rather than dressing up as diligence. The honest version is that a small firm’s oversight is mostly attention, applied on a schedule it sets for itself.

Go deeper