ReviewDesk
← Back

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

How do you set up your first ADMT workflow, step by step?

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

The short answer. Define one decision in one jurisdiction. Record the scope determination. Describe the tool and its factors from the record you'll actually keep. Generate the notice and publish it at the point of collection. Route its review form to the inbox, name the inbox owner, generate a test letter, and check the audit trail shows all of it. ReviewDesk's free tier covers exactly this shape — one workflow, one jurisdiction — because a first workflow done completely teaches more than a programme sketched broadly.

What is setting up an ADMT workflow?

An ADMT workflow in ReviewDesk is the unit of compliance work: one decision type, in one jurisdiction (Colorado, California or Illinois), with its hosted pre-use notice page, adverse-outcome letter generation, human-review inbox and timestamped audit trail. Paid plans run multiple workflows with the rule packs, SLA clocks, California opt-out handling, the evidence vault and the trace engine.

Step one: pick the decision and write its one-sentence definition

Choose the decision where automated influence is strongest or the next deadline bites hardest — most teams start with applicant screening or tenant screening. Write the decision in one sentence naming the decider, the tool's role and the consequence: 'The screening tool ranks applicants for warehouse roles; a hiring manager interviews from the ranking; applicants below the threshold are not interviewed.' If the sentence takes a paragraph, the scope is wrong — split it. One decision per workflow is the discipline that keeps notices honest, because a notice describing three decisions describes none of them checkably.

Attach the jurisdiction at this step, not later. The same decision in Colorado and California is two workflows with two notices, because the duties differ in machinery — Colorado's 30-day explanation, California's opt-out or appeal. The multi-workflow pattern is in the jurisdictions guide; for the first workflow, one state, chosen by exposure — Illinois if you hire there today, since its duties are already live.

Step two: record the scope determination

Run the measurements before the opinion: acceptance rate, median human review time, what the human actually sees. File the worksheet determination — materially influences, substantially replaces, or out of scope with the evidence — timestamped. This five-line record, described fully in the scope-test guide, is the workflow's founding document; everything after it is implementation. Teams that skip it build notices for systems they have not characterised, and discover the characterisation during their first review case.

If the determination is out of scope, stop here — the filed worksheet is the deliverable, and the workflow slot stays free for a decision that needs it. Honest negative determinations are programme assets, not wasted afternoons.

Step three: describe the tool and its factors

Write the tool description the notice will carry: what it does, the factor groups it uses, the output it produces, the human architecture around it. Source the factors from the vendor's documented per-decision returns where you have them — the diligence from the vendor guide — and from your own criteria where the tool is yours. Test the description by drafting the adverse letter it implies: can you write principal reasons from this description for a hypothetical declined applicant? If not, the description is not finished.

Keep the description at the resolution a person can act on. Factor groups, not mathematics; roles, not architecture. The notice builder at /try/notice takes this description as its input and returns the page — run it now, before the workflow exists, and read the result as an applicant. Most teams revise the description twice at this point, which is the cheapest revision cycle in the whole programme.

Step four: publish the notice and place it

Generate the hosted notice page from the workflow and place its link at every point of collection: application flow, intake form, partner referrals, the careers or listings page. Placement is a scavenger hunt through your own surfaces — wherever a person's information starts travelling toward the tool, the notice belongs one step earlier. Check the mobile rendering; most applicants will meet the notice on a phone, and a notice that breaks on a small screen has not been given in any sense that matters.

Confirm the page's review form routes to your inbox and file a test request yourself. You are rehearsing the applicant's entire journey — notice, form, inbox row — and any friction you feel is friction a real applicant would feel with higher stakes. The placement craft is detailed in the hosted-notice guide and the form's design in the form guide.

Step five: staff the inbox and set the clocks

Name the inbox owner today — a person, with a named deputy — and set the sweep rhythm: new rows acknowledged within your chosen target, reviews assigned to competent reviewers with authority. On paid plans, configure the statutory clocks for the jurisdiction and your internal targets inside them, per the clocks guide. On the free workflow, the audit trail's timestamps still discipline the queue; the habit matters more than the plan tier.

Run one synthetic case end-to-end before launch: a test adverse outcome, its letter, a review request, an outcome. Watch where the record forms and where it doesn't. Synthetic cases feel artificial exactly once — the first real case feels routine because the synthetic one taught the team the choreography. Choreography learned on real applicants is learned at their expense.

Step six: generate a real letter and read the trail

When the first real adverse outcome occurs, generate its letter from the workflow record the same day and read it cold before it sends: decision plain, reasons principal and specific, correction route concrete, review offer exact. Then read the audit trail for the whole workflow as a stranger would — notice published, decision recorded, letter filed, any requests and outcomes in order. The trail read is your launch review; if the story coheres, the workflow is live in the only sense that counts.

Schedule the recurring reads now, while the discipline is fresh: weekly letter sampling, monthly inbox aggregates, quarterly vault export test on paid plans. A workflow is a practice, not an installation. The teams whose programmes survive staff changes are the ones whose rhythm lives in calendars rather than in one conscientious person's habits — the same lesson the decision-history guide teaches at case level.

Your five actions for setting up an ADMT workflow

  1. Define one decision in one jurisdiction in a single sentence naming the tool's role and the consequence.
  2. Measure first, then file the scope determination with its evidence and timestamp.
  3. Write the tool and factor description at letter resolution, and test it by drafting the adverse letter it implies.
  4. Publish the hosted notice at every collection point, verify it on a phone, and file a test request through its form.
  5. Name the inbox owner and deputy, run one synthetic case end-to-end, then read the audit trail like a stranger.

Worked example: a first workflow live in a week

A fictional property manager — Juniper Rentals, fourteen staff — chooses tenant screening in Colorado as its first workflow. Monday: the one-sentence definition and the scope measurements, which show the screening recommendation is adopted in nine cases of ten — materially influential, filed. Tuesday: the factor description drafted from the screening service's documentation, tested against a sample decline letter. Wednesday: the notice generated, placed in the application flow, checked on two phones, and a test review filed and seen in the inbox.

Thursday the owner and deputy run a synthetic decline end-to-end. Friday the workflow is simply live — no announcement needed, because the next real application meets the notice as a matter of course. The first real decline the following week produces a letter the manager describes as the first decline she has sent without dread. One decision, one jurisdiction, completely wired: the free tier's exact shape, and the template for the workflows that followed.

Frequently asked questions

What is a workflow in ReviewDesk?

One decision type in one jurisdiction — Colorado, California or Illinois — with its hosted pre-use notice, letter generation, human-review inbox and audit trail. Free covers one workflow; paid plans add multiple workflows, clocks, opt-out handling, the vault and traces.

Which workflow should be first?

The decision with the strongest automated influence or the nearest live duty — Illinois employment if you hire there today, since those duties are already in force. One decision done completely beats a broad sketch.

How long does setup take?

The mechanics take an afternoon; the honest parts — scope measurements, the factor description at letter resolution — take a few days of part-time attention. The step order matters more than the speed.

Do I need an account to draft the notice or letter?

No. The notice builder and letter generator run free with no account and produce downloadable results. An account saves the workflow, publishes the hosted notice and keeps the audit trail.

Is this guide legal advice?

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

Keep reading: 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? · What does review coverage mean — and what breaks when requests go unanswered? · 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.