ReviewDesk
← Back

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

How should the review-request form on a notice page be designed?

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

The short answer. Ask for the least that routes the request well: who you are, how to reach you, which decision, what you want examined — in your own words — and evidence attached if you have it. Then confirm with a reference, a timeframe and a status link. A form designed this way files straight into the ReviewDesk inbox as a classified docket row; a form designed like an interrogation suppresses exactly the requests the process exists to receive.

What is the review-request form?

The review-request form is the structured entry point on a workflow's public notice page through which an affected person files for human review, correction, opt-out or appeal. In ReviewDesk, submissions land in the workspace inbox as timestamped docket rows carrying the workflow, jurisdiction and request type — born classified, with the person's own text preserved verbatim.

What is the form actually for?

Two jobs at once. For the person, it converts a grievance or a worry into a filed, acknowledged, trackable request — the difference between asking and having asked. For the organisation, it captures the request in a routable shape the moment it exists, instead of reconstructing it later from an email thread. Every design choice should be scored against both jobs: a field that helps routing but humiliates the filer fails; a free-text-only form that honours the filer but cannot be triaged fails the other way. The balance is a short structured spine around one generous free-text heart.

The form is also a promise-check. The notice said a person could ask; the form is where the organisation proves the asking is easy. Organisations that would never design a checkout this obstructive routinely design request forms with nine mandatory fields, a document upload in one blessed format and a captcha gauntlet — and then report, sincerely, that few customers request review. Request volume is partly a design output. Design as if you want the requests, because the regime's premise is that you should.

Which fields earn their place?

Identity and contact, because the case needs a person and a reply route. The decision concerned — a selector drawn from the workflow's decisions, defaulting to the most recent — because routing depends on it. Request type in the person's vocabulary — 'I want a person to look again', 'Something in my information is wrong', 'I want to opt out' — mapped behind the scenes to review, correction and opt-out, because the taxonomy is yours, not theirs. One free-text field with a humane prompt: 'Tell us what you would like us to look at, in your own words.' And an optional attachment field, because proof often exists and friction against it is friction against accuracy.

Everything else must argue for admission against the filer's patience. Date of decision helps matching but the workflow can usually find it; demanding it excludes the person who lost the letter. Account numbers exclude the person who never had one. Each mandatory field is a small toll on a right; charge tolls only where the routing genuinely fails without them. ReviewDesk's form follows this spine, and the inbox receives what the spine captures with the case assembled around it.

How should the free-text field be handled?

As the most important data on the form. The person's own account routinely carries the decisive fact — the namesake, the stale record, the circumstance no field anticipated — in the order and emphasis they chose. Preserve it verbatim on the docket; never summarise it away in intake, never tidy it. Reviewers read it first, before the screening summary, because anchoring is real and the person's framing deserves the first hearing. The outcome note then answers the free text point by point, which is how the person knows the review was of their case and not of a category.

Prompt it well. 'Additional comments' invites nothing; 'What should the person reviewing your case understand?' invites the case. A line of microcopy under the field — 'For example: a record that is not yours, a payment that is missing, a circumstance we could not see' — teaches filers what kind of facts change outcomes, improving request quality more than any validation rule. The form is the first act of the review itself; design it with a reviewer's gratitude in mind.

What should happen at the moment of filing?

Confirmation that does three things: proves the filing (a reference and the timestamp), sets the expectation (what happens next, the timeframe the workflow works to), and hands over the watching tool (the status link, per the status guide). The confirmation screen and its email twin are the most-read texts in the entire process; write them at the standard of the letter, not of a web form's default success message. A filer who leaves with a reference, a date and a link has been treated as a case-holder; a filer who leaves with 'Thanks, we'll be in touch' has been treated as a suggestion box.

File the confirmation's content into the record too. What the person was told at filing — the promised timeframe especially — becomes part of the case's fairness story, and promised timeframes have a way of being remembered differently by both sides. The docket's memory is the settlement of that difference, as with everything else in this programme.

How do accessibility and language shape the form?

The filer population includes everyone the tool can affect: people on phones, on shared computers, with limited literacy in the form's language, with disabilities that make long forms ordeals. Short fields, plain labels, no time limits on completion, error messages that say what to fix rather than what went wrong, and a route that works without an account or a printer. If your process also takes requests by phone or post — many should — the same docket discipline applies: the officer files the request into the inbox on the person's behalf, verbatim where possible, and the confirmation reaches the person by their channel.

Language access deserves one explicit decision. The notice page's audience defines the form's languages; a screening process that recruits in two languages owes its form in both. Machine translation of the form's fixed text, reviewed by a human speaker, is a reasonable floor; the free text accepts whatever language arrives, because the fact matters more than the filer's fluency and translation at review time is the organisation's job, not the filer's toll.

How do you know the form is working?

By its conversion and its content. Filed requests as a share of adverse outcomes should sit in a plausible band for your decision type — very low rates usually signal friction or an unfindable form, not universal satisfaction; the band from the coverage guide gives the reasoning. Content quality is the second signal: requests that arrive with the decisive fact in the free text and documents attached are requests the form taught well. Sample monthly, read five filings as their reviewers read them, and fix the form where the filings stumble.

And test it as a stranger, quarterly, from a phone, against the clock — the same five-minute discipline as the opt-out test in the opt-out guide. Forms rot quietly: a workflow renamed, a selector stale, a confirmation promising a retired timeframe. The test is cheap; the discovery of rot by a real filer is not.

Your five actions for the review-request form

  1. Build a short structured spine — identity, contact, decision, request type in the person's words — around one generous free-text field.
  2. Make attachments optional and welcoming; every mandatory field must justify its toll on a right.
  3. Preserve the filer's text verbatim on the docket, and prompt it with examples of facts that change outcomes.
  4. Confirm filing with a reference, a timeframe and a status link — and file that confirmation into the record.
  5. Test the form quarterly as a stranger, on a phone, and read filed requests monthly for content quality.

Worked example: the form that doubled good requests

A fictional landlord group — Castlekeep Homes — replaces a nine-field review form, which demanded a tenancy reference and the decision's reference code, with the spine design: identity, contact, property, request type in plain words, free text with examples, optional attachments. Filings in the first month triple. More telling than the volume is the content: most filers now name the exact record they dispute and attach the disposition or statement on the first pass, because the form's examples taught them what a decisive fact looks like.

Review time per case falls by a third even as volume triples, because reviewers stop chasing documents the old form never thought to invite. Castlekeep's lesson travels well: a request form is not a filter for seriousness. It is a teaching instrument that decides, in advance, how much of the truth each request will carry when it lands.

Frequently asked questions

What fields should a review-request form have?

Identity and contact, the decision concerned, the request type in the person's own vocabulary, one generous free-text field, and optional attachments. Everything else must justify itself against the filer's patience, because each mandatory field is a toll on a right.

Why keep the free-text wording verbatim?

The person's own account often carries the decisive fact, in their framing. Preserving it verbatim lets reviewers answer the actual request point by point, and keeps the record honest about what was asked and when.

What should the confirmation include?

Proof of filing (reference and timestamp), what happens next with the workflow's timeframe, and the applicant status link for watching the case. The confirmation's promised timeframe is itself filed into the record.

How can we tell if our form suppresses requests?

Compare filed requests with adverse outcomes for your decision type; implausibly low rates usually mean friction or an unfindable form. Sample the filings' content, and test the form quarterly as a stranger on a phone.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. Form design is described as ReviewDesk implements it; consult counsel for your obligations.

Keep reading: 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? · How do you answer every human-review request — without sounding like a bot? · How do you run ADMT workflows across Colorado, California and Illinois at once? · 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.