ReviewDesk
← Back

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

How can a small business meet ADMT notice and review duties without a compliance department?

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

The short answer. Inventory your automated decisions (most small businesses have one or two), put the strongest one on a free workflow, publish its notice where applicants or customers meet it, name one person to clear the inbox each morning, and generate letters from the record instead of drafting them. That is the whole programme at small scale — an afternoon to build, an hour a week to run — and it covers the duty's actual shape: notice, explanation, correction, review, records.

What is small-business ADMT compliance?

Small-business ADMT compliance is the proportionate operation of the automated-decision duties — pre-use notice, adverse-outcome explanation, correction and human review, three-year records — at the scale of a business without dedicated compliance staff. In ReviewDesk it maps to the free tier's shape: one decision workflow in one jurisdiction, with the hosted notice, letter generator, inbox and audit trail included.

How many automated decisions does a small business actually have?

Usually one or two, and naming them is most of the battle. The common candidates: a screening feature inside the hiring platform you already pay for, a tenant-screening service if you let property, a booking or eligibility tool if you serve consumers. Software that merely stores, schedules or totals is not deciding about people. Walk each customer- and applicant-facing process with the two discretion questions from the ADMT guide — does the output drive the outcome, does a human genuinely re-decide — and write down the answers. Most owners complete the inventory in an hour and find the list shorter than their anxiety suggested.

Do not skip the bundled features. Small businesses rarely buy 'AI'; they buy a hiring platform whose scoring toggle is on by default, or a screening report whose recommendation they always follow. The duty follows the effect, not the purchase order. If the recommendation is adopted nine times in ten, it is your decision process — measure it, file the scope call, and let the workflow carry it.

What is the minimum programme that is genuinely complete?

Five pieces, all present, none gold-plated. A notice, hosted, linked where the decision's subjects meet it. Letters generated from the decision record, with real reasons, sent promptly after adverse outcomes. A correction route that a named person checks daily. A review path to a person who can change the outcome — at small scale, often the owner, acting as a distinct reviewer on the full file. And records kept by the desk rather than by memory. Missing any one piece, the programme has a hole shaped exactly like the missing piece; with all five, it is small but whole — and wholeness is what examiners, complainants and courts actually test.

The free ReviewDesk workflow is deliberately that minimum: one workflow, one jurisdiction (CO, CA or IL), hosted notice, letter generator, inbox, audit trail. Start there. Paid tiers add scale and machinery — more workflows, clocks, the vault, traces — when volume, states or decision types grow into them, per pricing. Nothing in the free shape needs unbuilding later.

How much time does it take each week?

At typical small-business volumes, an hour or less, structured as rhythm rather than project. A ten-minute morning sweep on business days: new requests acknowledged and assigned — often to yourself, wearing the reviewer hat at a set hour. Letters generated the day adverse outcomes occur, in the same sitting as the decisions themselves, while the reasons are fresh and the record is open. A monthly half-hour: read the aggregates, sample two letters, check the oldest open case. A quarterly hour: re-read the notice against the live process, test the export if you are on a paid plan, re-run the scope question if the tool changed.

The honest comparison is not with zero. It is with the unstructured version: the complaint that takes a week because nothing was recorded, the applicant question nobody can answer, the afternoon reconstructing a decision from three inboxes. Small programmes are cheap precisely because they replace archaeology with filing. Owners who run the rhythm for a quarter routinely report the desk saves time net — the requests were always arriving; now they arrive organised.

Which jurisdiction and decision come first?

The live one. If you hire in Illinois, its employment notice duties are already in force — start there. If your exposure is Colorado or California decisions, build ahead of the 1 January 2027 start so the records accumulate from your first decisions under the regime. Decision-wise, start where the tool's influence is strongest and the subjects most numerous — usually applicant screening. The setup sequence in the setup guide is written to be followed by a non-specialist in an afternoon, including the synthetic test case that teaches the choreography before a real person's case depends on it.

Resist starting with a policy document. Small businesses do not need a twelve-page ADMT policy; they need a working notice, a working inbox and a habit. Paper programmes without the machinery decay into the exact gap this fleet keeps describing — the promise with no docket behind it. Machinery first, and the one-page internal note about who owns what can be written from the working system in week two, accurately, because it describes something real.

What are the small-business-specific traps?

The owner-as-everything trap: the same person configures the tool, makes the decisions, reviews the challenges and writes the record — legal at small scale, but the review must be a distinct act: different sitting, full file, fresh note, per the review checklist. The vendor-assurance trap: believing the screening service 'handles compliance' because its brochure says 'compliant platform' — the duties sit with your decisions, as the vendor-deployer guide explains; ask the five diligence questions. And the nephew trap: a well-meaning relative or freelancer set up the tools, holds the logins and the knowledge, and leaves — records and access must live in the business's own accounts from day one.

The fourth trap is waiting for certainty. The regimes' broad shape is settled — notice, explanation, review, records — and a real programme built now adapts to guidance as it lands far more easily than a standing start in the deadline quarter. Build the small whole thing, run it, and let your own case data teach you where your risks actually live.

How does the programme grow without breaking?

By adding workflows, not by redesigning. The second jurisdiction is a second workflow drawing on the same factor source, per the jurisdictions guide. The second decision type likewise. Volume growth adds a deputy inbox owner before it adds tooling. The paid clocks earn their upgrade the first time a deadline month gets busy; the vault earns its the first time someone asks for a complete file; traces earn theirs when you need to answer a pattern question about your own decisions. Each upgrade is a response to a felt need with a name — the healthiest growth pattern a compliance programme can have.

Keep the owner's dashboard embarrassingly simple throughout: requests in, answered, oldest open, last letter sampled. Four numbers and a date. A programme an owner can hold in their head at that resolution is a programme that survives the owner's busy season, which is when programmes usually die. The desk holds the detail; the owner holds the rhythm. That division is the whole secret at this scale.

Your five actions for small-business ADMT compliance

  1. Inventory the business's automated decisions in one hour — including scoring features bundled inside platforms you already pay for.
  2. Stand up the free workflow for the strongest decision in the live-est jurisdiction: notice placed, inbox owned, letters generated.
  3. Run the rhythm: ten-minute morning sweep, letters on decision day, monthly aggregates, quarterly notice re-read.
  4. Keep the owner's review a distinct act — full file, fresh note, different sitting — even when the owner is every role.
  5. Grow by adding workflows in the same desk, and upgrade tiers only against a named, felt need.

Worked example: a nine-person company's whole programme

A fictional nine-person company — Bravo Build, a renovation contractor — hires through a platform whose screening ranks applicants by licence, availability and experience markers. The owner spends one afternoon on the inventory and scope call (the ranking materially influences who is interviewed — filed), one on the workflow: notice generated and linked in the job advert and application flow, inbox owned by the office manager with the owner as reviewer, letters generated for the first batch of declines with reasons from the screening record.

The steady state settles at forty minutes a week. In the first quarter, eleven requests arrive: eight corrections (mostly availability recorded wrong after a form change — the platform's form gets fixed), three reviews, one outcome changed. When a declined applicant's adviser writes a formal letter in month three, the reply — notice version, decision record, letter, review history — assembles in under an hour from the desk. Bravo Build has no compliance department. It has a programme, and the difference turned out to be an afternoon plus a rhythm.

Frequently asked questions

Does a small business really have ADMT duties?

If software materially influences consequential decisions about people — hiring above all — yes, in the regimes covered here, with Illinois employment duties already live. Most small businesses have one or two such decisions; the free workflow is sized exactly for that.

What does the minimum complete programme include?

A hosted notice where subjects meet it, letters with real reasons generated from the decision record, a correction route checked daily, review by a person who can change the outcome, and records kept by the desk. All five pieces — the free tier holds them for one workflow.

How much time does it take to run?

About an hour a week at typical volumes: a ten-minute morning sweep, letters generated on decision day, a monthly half-hour on aggregates and sampling, a quarterly notice re-read. Less than the reconstruction work it replaces.

My screening vendor says their platform is compliant — is that enough?

No. The duties attach to your decisions: your name belongs on the notice, your reasons in the letters, your inbox behind the review route. Ask the vendor the diligence questions in the vendor guide and build your side on the desk.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. The programme shape is ReviewDesk's operating model; consult counsel for your situation.

Keep reading: 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? · What are a staffing agency's duties when it screens candidates with automated tools? · How do automated-decision duties apply to gig platforms and marketplaces? · 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.