← Back

Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice

← All guides

Vendor vs Deployer: Who Owes the ADMT Notice?

The short answer: Colorado's rules data settles the question in one duty: the duty sits with the deployer — the business using the tool owes the notice, not the vendor that sold the tool. The same source adds that no state lets a vendor claim of human oversight excuse the deployer notice duty (per the LexBlog employer ADMT roundup the kit is built from). Vendors have their own, different duties — in Colorado, developers owe deployers technical documentation and notice of material updates — but those duties support the deployer's; they never absorb them.

Check your duties and dates — free Build your first notice — free

What is a deployer? The business that uses an automated decision-making tool to make or inform its decisions about people. A developer builds or sells the tool. Most readers of this guide are deployers: you chose the tool, you feed it your applicants' or customers' data, and the decision carries your name. The person's notice therefore carries your name too — as the kit's template shows, generated from your business profile.

The deployer's non-delegable set

Everything person-facing is the deployer's: the pre-use notice, the adverse-outcome explanation, the correction path, the human review, the opt-out honouring, the access answers, and the record. None of it can be contracted away, because the duties attach to the decision, and the decision is the deployer's. A vendor's offer to 'handle compliance' can supply tooling, templates, and documentation — it cannot supply the duty's discharge, and a vendor white-label notice that names the vendor instead of you misidentifies the responsible party to the person reading it.

The practical test for any vendor claim: if the duty were questioned, whose name is on the decision the person received? That name owes the notice. Structure vendor relationships to support your discharge of the duty — documentation, data access, update notice — rather than to pretend the duty moved.

What developers owe: documentation and update notice

Colorado's checker data states the developer side: if you build or sell the tool, you also owe deployers technical documentation — intended uses, categories of training data, known limitations, and instructions for appropriate use and human review — and notice of material updates. For a deployer, this list is a procurement checklist: these are the artefacts to demand, in writing, before deployment and at every material update.

Each item maps to a deployer need. Intended uses bound your purpose statement. Training-data categories inform your risk assessment's data element. Known limitations belong in reviewer training. Human-review instructions shape your queue design. A vendor who cannot produce the documentation has told you something material about deploying their tool under these regimes — hear it before the contract, not after. The developer side gets its own guide at Colorado Developer Duties.

Worked example: Crosswinds Property Group

Example — fictional business, real duty structure. Crosswinds is a fictional housing operator that discovered, during its inventory, that its screening vendor's marketing had shaped its compliance posture. The correction, in sequence:

The vendor-claim trap: 'our tool has human oversight'

The kit's source line deserves quoting in substance: no state in the roundup lets a vendor claim of human oversight excuse the deployer notice duty. The trap is subtle — a vendor markets 'human-in-the-loop by design', the deployer hears 'your decisions are human', and the notices never get built. But the human-decision question is about your workflow: your reviewers, their competence, their authority, their actual practice — the subjects of Token Human Review. A vendor cannot supply your reviewers' authority, and their claim describes their software, not your process.

Treat every vendor oversight claim as a prompt for your own evidence: who reviews, with what training, changing what share of outcomes. If the answers are yours and documented, the claim is corroborated; if the only evidence is the vendor's brochure, the duty position is unexamined.

Contract and procurement: what to secure, in writing

Four clauses do the practical work. Documentation: the Colorado developer documentation set, delivered before deployment and refreshed on material change. Update notice: advance notice of material updates, with a window to re-run your assessment and reviewer training before the update reaches production decisions. Data access: your decision data — inputs, outputs, reasons data — exportable by you at any time, because your record duty outlives the contract. Sub-processing transparency: which embedded services touch the data, so your inventory's data-flow pass stays true.

Renewals are the leverage moments: the inventory register records each tool's renewal date for exactly this reason. A vendor conversation held at renewal, with the documentation list in hand, concludes differently from the same conversation held mid-incident. The procurement questions are collected in What to Ask Your AI Vendor Before January 2027.

When the vendor cannot support the duties: exits and the record

If a vendor cannot support the duties — no documentation, no data export, silent material updates — the deployer's options are to change the use (reduce the tool's role until it is genuinely minor), replace the tool, or stop the use. Continuing to deploy an unsupportable tool for covered decisions is a decision too, and it will be read as one. The register should record the finding and the chosen path with dates.

Whatever happens commercially, the record stays with you: notices given, explanations sent, reviews held — the 3-year chain is the deployer's evidence and must be exportable independent of the vendor relationship. That principle shaped the kit's design (one record, held by the business, exportable on demand), and it should shape your contracts the same way. Confirm your own duty position in the free checker — it asks about your use, not your vendor's claims.

  1. Write on the register, per tool: the deployer is us; the notice, explanation, correction, review, and record duties are ours
  2. Demand the developer documentation set in writing — intended uses, training-data categories, known limitations, human-review instructions
  3. Refuse the substitution: a vendor's human-oversight claim never replaces evidence about your own reviewers and workflow
  4. Secure four contract terms — documentation refresh, material-update notice, your data export at any time, sub-processor transparency
  5. If a vendor cannot support the duties, change the use, replace the tool, or stop — and record the finding and the path chosen

Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.

Build your first notice — free

Related guides

See all ADMT guides for the full set.

Frequently asked questions

Who owes the ADMT notice — us or our software vendor?

You do. Colorado's rules data states the duty sits with the deployer: the business using the tool owes the notice, not the vendor that sold the tool.

What does the vendor owe us?

In Colorado's data, developers owe deployers technical documentation — intended uses, categories of training data, known limitations, and instructions for appropriate use and human review — plus notice of material updates.

Our vendor says their tool has human oversight built in. Are we covered?

No. The kit's source states that no state lets a vendor claim of human oversight excuse the deployer notice duty. The human-decision question concerns your reviewers, their competence, authority, and practice.

Can a vendor send the notices on our behalf?

A vendor can supply tooling, but the notice must name the deployer — the business whose decision it is — and the record must be the deployer's. The kit generates notices from your business profile for exactly this reason.

What if our vendor will not provide documentation or data export?

Then the tool cannot support your duties for covered decisions. The options are to reduce the tool's role, replace it, or stop the use — and to record the finding and the path chosen in the register.

Build your first notice — free