ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

ADMT duties explained for software vendors and the businesses that deploy their tools

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. Deployers owe the person the notice, the explanation and the review; vendors owe deployers the facts those duties consume — per-decision factors, versioning, records and override support. Confusing the two sides is how duties fall into the gap between a product and its customer. This guide draws the line as the regimes draw it, and as ReviewDesk's workflows assume it: the deployer's name on the notice, the vendor's evidence behind it.

What is vendor and deployer duties?

In ADMT frameworks, a deployer is the business that uses a decision tool on people in its own operations; a developer or vendor is the business that builds and supplies the tool. ReviewDesk's regimes place the person-facing duties principally on the deployer, while the vendor's obligations run to the deployer — transparency about the tool's role, factors and limits — increasingly written into contracts and, for vendors selling into regulated buyers, into the product itself.

Why does the split matter in practice?

Because each side's failure looks identical from the applicant's chair: no notice, a vague letter, a review that cannot see the file. Organisations exploit the ambiguity unconsciously — the deployer assumes the vendor's documentation discharges the notice; the vendor assumes the deployer's counsel handles disclosure — and the applicant discovers the gap. Drawing the line in advance, per workflow, is the entire remedy: this decision, this tool, this deployer name on the notice, these vendor facts annexed to the contract.

The split also explains market behaviour. Vendors who build evidence features — per-decision factors, versioning, export — are selling deployers their duty-discharge capacity, and sophisticated deployers now buy on exactly that basis, as the vendor-questions guide sets out. The regimes, without naming most vendors at all, have quietly rewritten the feature roadmap of decision software.

What does the deployer owe, in one list?

The notice before use, in the deployer's name and voice, placed where the person actually passes. The explanation after adverse outcomes, written from the decision record with principal reasons. The correction route and the human-review path, staffed and clocked. The records — audit trail, traces where the plan carries them, three-year retention. And the scope determination: the deployer's own judgement, on the worksheet, of whether the tool materially influences the decision. Every item is an operational artefact, which is why ReviewDesk sells deployers a desk rather than a document pack.

The deployer's non-delegable core is judgement. A vendor can host your notice; it cannot decide your criteria, weigh your reviewer's overturn, or write the reason this applicant was declined. Deployers who internalise that boundary stop asking vendors for compliance and start asking them for evidence — a much more productive conversation, and the one the evidence engine is built to serve.

What does the vendor owe, in one list?

An honest account of what the tool does: its decision role, its factor structure at letter-printable resolution, its known limits and error patterns, its data sources. Versioned outputs: every decision stamped with the model or rules version that produced it, and advance notice of material changes. Records and export in documented formats the deployer can independently use. Override and correction mechanics that persist — a deployer's human decision must not be silently re-asserted away by the product downstream. And candour in sales: the tool's capabilities described as they are, because deployers will build notices on those descriptions.

Vendors should notice what is absent: the vendor does not owe the applicant a letter, and should not send one. Person-facing communications belong to the deployer, on the deployer's record. Vendor tooling that generates applicant-facing artefacts does so as the deployer's instrument, branded and governed accordingly — the distinction ReviewDesk observes in its own position as a workflow vendor: the desk is the deployer's, the letters are the deployer's, the record is the deployer's.

How do the duties meet inside a workflow?

At the trace. The deployer's pipeline files a decision trace — the vendor's output, version and factors, the deployer's outcome, notice and review flags — and that single record is where the two sides' contributions become one evidence object. If the vendor's side of the trace is thin, the deployer's packs show 'not recorded' in the vendor-shaped holes, which is why factor and version quality is ultimately a vendor feature the deployer can measure. The trace is, in effect, the contract's technical annex made executable.

They meet again at review. The deployer's reviewer overturns; the vendor's product must record the overturn against the decision, respect it in every downstream surface, and report overturn patterns in aggregate. A vendor whose roadmap treats overturn data as the deployer's gold — model feedback of the highest grade — will build that loop gladly. A vendor who experiences overturns as reputational threat will resist the instrumentation, and that resistance is diligence information.

What should the contract between them say?

Translate the lists into obligations: decision-role description as a factual warranty of behaviour; per-decision factor and version outputs as a product commitment; change notice periods tied to the deployer's notice-update duties; retention and export specifications; correction propagation service levels; audit and evidence cooperation. Add the failure conversation while everyone is friendly: what happens when a version ships that changes outcomes materially without notice — because the deployer's notices and scope worksheet are now wrong in production, and the contract should price that risk before it is realised.

Keep the contract honest about its limits. It can allocate cost and compel cooperation; it cannot transfer the deployer's person-facing duties, and clauses pretending otherwise create false comfort. Counsel on both sides increasingly know this; procurement templates that still promise 'vendor handles compliance' should be retired on sight. The deployer's desk — notice, inbox, letters, vault — remains the deployer's to run, which is the assumption underneath every ReviewDesk workflow.

How does this play out for small vendors and small deployers?

Proportionally. A five-person vendor selling screening to local employers cannot staff a compliance department, but it can do the four things that matter: describe the tool's role and factors honestly, version its outputs, export its logs in a readable format, and respect overrides. A ten-person deployer cannot run an enterprise programme, but it can put its name on a notice, generate letters from the record, and clear an inbox. The regimes' centre of gravity is conduct, not headcount — small actors doing the real things beat large actors performing them.

ReviewDesk exists for that proportionality: the free workflow gives a small deployer the whole duty shape for one decision type, and the same desk scales to multi-workflow, multi-jurisdiction operations without changing products. Vendors selling into that world should design for the deployer's desk — factors out, versions stamped, overrides honoured — because that is the integration surface the duties have created.

Your five actions for vendor and deployer duties

  1. Name the deployer on every notice and letter; never let a vendor's documentation impersonate your disclosure.
  2. Annex the vendor's decision-role, factor and versioning facts to the contract as obligations, not aspirations.
  3. Meet at the trace: file the vendor's output and the deployer's outcome as one record per decision.
  4. Verify the product respects overrides and propagates corrections before promising either to applicants.
  5. Retire any contract language claiming the vendor 'handles compliance' — duties allocate evidence, not responsibility.

Worked example: a vendor and a deployer divide the work properly

A fictional screening vendor — ClearMark Screening — supplies tenant-screening to a fictional landlord group, Dovecote Properties. Their agreement is a model of the split: ClearMark warrants the factor list and per-decision factor returns, stamps model versions, gives thirty days' notice of material changes, and exports decision logs in a documented format. Dovecote's name is on the notice and every letter; its officers run the inbox; its scope worksheet records the determination, informed by ClearMark's measured acceptance data.

When a namesake error surfaces — an applicant's file carrying another's filing — both sides' machinery engages in its own lane: Dovecote corrects, re-assesses and answers the applicant inside the week; ClearMark fixes the matching rule and the fix ships as a versioned change with notice, visible in subsequent traces. Neither party ever tells the applicant to talk to the other. The applicant experienced one decision, owned by one name, evidenced by two systems that were designed to meet.

Frequently asked questions

Who is the deployer and who is the vendor?

The deployer is the business using a decision tool on people in its own operations — the employer, landlord, lender. The vendor (or developer) builds and supplies the tool. The person-facing duties sit principally with the deployer.

Can a deployer contract away its ADMT duties to the vendor?

No. Contracts can compel the vendor's evidence and cooperation — factors, versioning, export, change notice — but the notice, explanation and review the person experiences remain the deployer's. Clauses claiming the vendor 'handles compliance' create false comfort.

What should a vendor build to serve deployers' duties?

Honest decision-role and factor documentation, per-decision factor returns, versioned outputs with change notice, documented record export, and override and correction mechanics that persist inside the product.

Where do vendor and deployer duties physically meet?

In the decision trace and the review loop: the trace joins the vendor's output, version and factors with the deployer's outcome, notice and review flags; the review loop joins the deployer's overturn with the vendor's obligation to record and respect it.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. The division is described as the frameworks and ReviewDesk's model frame it; consult counsel for your contracts.

Keep reading: How do you set up your first ADMT workflow, step by step? · What makes a hosted pre-use notice page work better than a PDF or a policy link? · How should the review-request form on a notice page be designed? · How do you write an ADMT notice in plain language that people actually understand? · How do you write an adverse-outcome letter that de-escalates instead of inflaming? · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.