ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
How can an agency run ADMT desks for multiple client businesses?
Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing
The short answer. One desk, many businesses, strict separations: each client's workflows, notices, inboxes and records are their own, while the agency's bench, standards and rhythm are shared. ReviewDesk's Team plan is built for exactly this — everything in Pro, multiple businesses under one desk, and licence terms aimed at agencies and HR-tech resellers. The craft is in the boundaries: a client must be able to see, export and leave with their own file, untouched by every other client's.
What is agency-run ADMT desks?
An agency ADMT desk is a service operation in which one provider runs automated-decision workflows for several client businesses: each client has its own workflows (decision types in their jurisdictions), its own hosted notices and inbox cases, and its own three-year records, while the agency supplies the staffing, the process discipline and the platform. In ReviewDesk this maps to the Team plan's multiple-businesses structure.
Why do clients buy the desk instead of the duties?
Because the duties are a practice, not a purchase. A small employer or landlord group can understand the notice-explanation-review pattern in an afternoon and still fail it by March, because nobody's job is the morning sweep. Agencies sell the sweep: the staffed inbox, the clock-watching, the letter discipline, the quarterly reads. What the client must never outsource — and the agency must never absorb — is the decision itself and its accountability: the client's name on the notice, the client's criteria, the client's reviewer authority for outcomes that bind the client. The desk operates the machinery; the client owns the decisions.
That boundary is also the agency's protection. An agency that quietly becomes the decision-maker inherits the client's exposure without the client's knowledge of their own applicants. Keep the authority map explicit per client: who sets criteria, who can overturn, whose name signs outcomes. ReviewDesk's per-business structure keeps the map enforceable, because each business's workflows and roles are configured separately rather than pooled.
How must client separation work technically?
absolutely: notices branded and addressed per client; inbox cases visible only within the client's business; exports scoped to one client's file; reviewers' access granted per client, not across the desk. Separation failures in agency settings are catastrophic in a specific way — they contaminate trust in every client relationship at once, because each client reasonably asks what of theirs another client saw. The platform's business boundary is the control; the agency's access discipline is its enforcement, audited like any other control.
Separation extends to the learning layer. Aggregate benchmarks across the desk — median days to outcome, correction shares — are the agency's legitimate management data, anonymised by construction. A client's cases are never training material for another client's reviewers beyond those anonymised patterns. Write the rule into client terms before the first case arrives; retrofitting confidentiality norms onto habits is the kind of sentence that appears in post-mortems.
How does the bench serve several masters fairly?
By making capacity a visible, contractual quantity. Each client's clocks run on the same board discipline — ageing visible, escalation on read — but the agency's internal board aggregates across clients so a surge in one client's hiring round does not silently consume another's review capacity. Service levels are set per client (acknowledgement targets, decision tempos matched to their cycles), and the desk's staffing model is built from the sum of the promises, not from optimism. When promises conflict in a peak week, the board shows it early enough to hire, borrow or renegotiate — the three honest options, in that order.
Reviewer assignment gains one dimension: client context. A reviewer carrying three clients' tenancy cases needs each client's criteria at hand, because criteria differ and the decision history will be read by the client it belongs to. The assignment discipline from the assignment guide applies per client, with the client's own sample reviews as the calibration loop — the client reads their cases monthly, which is both quality control and the agency's retention strategy.
What should the client see, and how often?
Their whole file, on demand, and a rhythm of summaries they did not have to demand. Monthly: volumes, coverage, median days, overturn and correction shares, breaches with causes — computed from their real cases, in the spirit of the history guide. Quarterly: the sampled letters read together, the corrections log's lessons, upcoming clock or rule changes. On request at any time: a scoped export of any decision file from their vault. A client who can see everything rarely asks to; a client who must chase visibility always wonders what else is chased.
The commercial point deserves stating plainly: in a market where compliance services often amount to a policy PDF and a prayer, demonstrable operation is the differentiator. The agency that shows a client their own live coverage gauge — real answered-over-total, per the coverage guide — is selling something a PDF vendor cannot counterfeit: the work, happening.
How do client exits and audits work?
By export, completely, without hostage-taking. The client's decision files — notices' history, traces, letters, case histories — are the client's records; the Team structure and vault export exist so an exit is an administrative event, not a negotiation. Define the exit mechanics in the initial terms: export scope, format, the retention the agency keeps (ordinarily none beyond its own engagement records) and the timetable. Agencies that make exit easy win referrals from the clients who test it; agencies that make it hard eventually explain themselves to someone else's counsel.
Audits follow the same principle per client: the examiner of Client A's files sees Client A's workspace, scoped, with Client B nowhere in the building. Rehearse it: run one client's mock export quarterly on rotation. An agency's separation claims should be as demonstrable as its coverage claims, and for the same reason — they will eventually be examined by someone whose job is doubt.
What should an agency charge for — and never promise?
Charge for operation: workflows run, cases answered, clocks watched, reporting produced. Never promise outcomes the desk does not control — approval rates, regulatory absolution, 'compliance guaranteed'. The honest promise is narrower and stronger: every notice live, every request answered on the record, every file exportable, every breach owned. Team's never-expires licence terms for agencies exist because the desk is an operating asset, not a campaign; price it like one, in retainers matched to volume, with surge terms agreed before the surge.
Sell the first client a single workflow, run it flawlessly for a quarter, and let its evidence pack close the second client. In this market the sales asset is a quarter of real cases with real coverage — the same demonstration logic as the reseller guide. Agencies that begin by selling the full estate to everyone spend their first year explaining; agencies that begin by proving one desk spend it expanding.
Your five actions for agency-run ADMT desks
- Draw the authority map per client in writing: their name, their criteria, their overturn authority — the agency operates, never decides.
- Enforce business-level separation technically and in access grants; rehearse a one-client export quarterly.
- Staff from the sum of the clients' promises, on one aggregated board, with per-client service levels visible.
- Report monthly from each client's real cases — coverage, days, overturns, corrections, breaches with causes.
- Contract the exit before the entrance: complete export, defined timetable, no retained copies beyond engagement records.
Worked example: a two-person agency runs desks for nine landlords
A fictional agency — Deskwork Partners, two operators — runs tenant-screening workflows for nine small landlord groups on a Team desk. Each landlord's applicants see that landlord's notice and write to that landlord's inbox; Deskwork's bench works one aggregated board where clocks, not client size, set the order. Monthly packs go out per landlord from their own cases: the largest shows 143 requests with a five-day median; the smallest shows 6 requests and the same discipline.
In month five, one landlord sells a property portfolio and exits. The export — two years of files for the transferred properties, scoped and sealed — takes an afternoon, and the buyer's own adviser verifies it without a single call to the agency. Deskwork loses a client and gains its best reference in the same transaction. The exit was not a failure of the model; it was the model, demonstrating exactly what it promises every client on entry.
Frequently asked questions
What does the Team plan add for agencies?
Everything in Pro — workflows, clocks, opt-out handling, vault, evidence engine — plus multiple businesses under one desk and licence terms aimed at agencies and HR-tech resellers. See pricing for the current terms.
Who owns the decisions when an agency runs the desk?
The client. The client's name is on the notice and letters, the client's criteria govern, and overturn authority sits with the client. The agency operates the machinery — inbox, clocks, generation, reporting — under an explicit authority map.
How is client data kept separate?
By the platform's business boundary plus the agency's access discipline: per-client workflows, notices, inboxes and exports, with reviewer access granted per client. Separation is rehearsed through quarterly scoped mock exports.
What happens when a client leaves?
A complete export of the client's decision files — notices' history, traces, letters, case histories — on the timetable set in the initial terms. The records are the client's; exit is an administrative event, not a negotiation.
Is this guide legal advice?
No. ReviewDesk is templates and workflow tooling, not legal advice. The agency model is ReviewDesk's operating pattern; consult counsel for your client terms.
Keep reading: How can HR-tech resellers offer ADMT notice and review tooling to their clients? · How can a small business meet ADMT notice and review duties without a compliance department? · What should a startup build first when its product or hiring uses AI screening? · A landlord's step-by-step plan for compliant automated tenant screening · How should a fintech lender build its ADMT workflow — from application flow to evidence pack? · 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.