ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
What makes a hosted pre-use notice page work better than a PDF or a policy link?
Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing
The short answer. A hosted page wins on four properties a document cannot match: one address that never changes, one current version everyone reaches, a review form that routes requests into the inbox, and a history the audit trail can evidence. ReviewDesk publishes each workflow's notice as such a page — generated from the workflow record, so the promise and the machinery behind it are designed together and versioned together.
What is the hosted notice page?
A hosted pre-use notice page is the web page, published at a stable address, that carries a workflow's ADMT disclosure: the tool, the decision, the factors, the person's rights and the request form. In ReviewDesk it is generated from the workflow record, linked from every collection point, and versioned inside the audit trail for the decision file's three-year life.
Why does one stable address matter so much?
Because notices are cited. The applicant quotes the notice in their review request; the letter references it; the evidence pack records its version. If the notice lives at an address that changes with every website redesign — or worse, as an attachment whose filename mutates — citations rot and versions multiply. A hosted page decouples the notice's identity from your marketing site's lifecycle: the redesign happens around it, the link in a two-year-old letter still resolves, and the page the applicant saw is the page the trail describes.
Stability also disciplines the author. A page with a permanent address gets maintained like a product surface — because it is one — while a PDF in a shared drive gets maintained like a rumour. When the tool changes, the hosted page is edited once, in place, with the change timestamped; the PDFs keep circulating with the old factors, and nobody can recall them. The version question is the next section's subject, but it begins here: one address is what makes 'the current version' a coherent idea.
How should versions be handled on a live page?
The live page always shows the current version; the history lives in the record. Each material change — factors, tool, decision scope, rights routes — creates a new recorded version with its effective date, and the audit trail keeps superseded wordings retrievable for the files of people decided under them. What the page must never do is silently accumulate edits with no version trail: the difference between version 3 and version 4 is exactly what a February applicant's case may turn on.
Date the page visibly and keep a short change note in the record — not on the public page, where a changelog would clutter the disclosure, but in the workflow history where a reviewer can find it. ReviewDesk's generation model helps structurally: because the page renders from the workflow record, changing the workflow changes the page, and the workflow's own audit events timestamp the change. Document-driven notices drift from operations; record-driven notices cannot drift without leaving evidence of the drift.
What belongs above the fold?
The decision, the tool's involvement and the person's headline rights — in that order, in the first screen, in plain words. A visitor should learn within ten seconds that a tool will help decide something about them, what that something is, and that they can ask for a person. Detail follows: factors, data categories, the human architecture, the routes in full. The structure mirrors the letter discipline in the plain-language guide: the page is written for a person deciding what to do next, not for a reviewer scoring its completeness.
Resist the banner-summary temptation — a short version at the top that the long version quietly contradicts. Lawyers sometimes draft the summary for warmth and the body for safety; readers trust the summary and feel deceived by the body. One text, layered by headings, honest at every depth: the person who reads only the first screen and the person who reads every line should carry away the same facts at different resolutions.
How does the review form belong on the notice page?
As the page's working half. The notice promises review; the form is the promise's handle. It should ask for the minimum that routes the request — identity, contact, the decision concerned, what the person wants examined, in their own words — and file it directly into the inbox as a classified docket row, per the form-design guide. A notice whose review path is 'contact us' with an email address has described a right and withheld its mechanism; the form is the mechanism, and its presence on the page is the difference between a disclosure and a system.
The form also sets expectations at the point of filing: what happens next, the timeframe the workflow works to, and the status link that will let the person watch. Expectations set at filing are worth a dozen set in the eventual reply, because they govern the waiting — and the waiting, as the status guide argues, is where complaints are born.
How should the page be placed and linked?
Everywhere collection happens, one step before the tool. Application flows, intake forms, partner pages, printed materials through a short link or code — and internally, wherever staff describe the process, so the organisation's own answers quote the same page applicants read. Placement is an audit task: list the doors, verify the link at each, re-verify after every website or process change. Doors multiply quietly — a new partner, a new landing page, a seasonal intake form — and each new door without the notice is a cohort of people the tool processed unwarned.
Link text matters. 'Your rights when we use automated screening' brings the reader in the right frame; 'Privacy notice (PDF)' loses them before they start. The page is part of the decision journey, and its links should read like it. ReviewDesk's hosted pages are built to be linked exactly this way — stable, self-contained, and carrying their form — so placement is a linking exercise, not a development project.
How do you keep the page honest over time?
By assigning its truth to the workflow owner's recurring rhythm: re-read the page against the live process quarterly — factors as actually run, routes as actually staffed, timeframes as actually met. The quarterly read catches the classic drifts: the vendor changed a data source in March; the review team's timeframe slipped in May; the page still promises February's world in June. Each drift is small; their sum is a notice that describes a process nobody runs, which is worse than a sparse notice describing the real one.
Pair the read with the scope re-test and the risk cycle, so the page, the worksheet and the assessment are refreshed in the same pass from the same facts — the calendar alignment in the assessment guide. One afternoon per quarter keeps the public promise, the internal determination and the annual evidence telling one story. That is the whole game, and the hosted page is where the story is published.
Your five actions for the hosted notice page
- Publish the notice at one stable hosted address, decoupled from marketing-site redesigns.
- Version every material change with an effective date; keep superseded wordings retrievable in the record.
- Put the decision, the tool and the headline rights in the first screen — one text, honest at every depth.
- Embed the working review form on the page, filing directly into the inbox with expectations set at filing.
- Audit placement after every process or website change, and re-read the page against the live process quarterly.
Worked example: the PDF graveyard, replaced by one page
A fictional training provider — SkillBridge Academy — once kept its screening notice as a PDF. An internal search during a complaint finds five versions across its drives, two linked from live pages, one quoting a screening vendor it stopped using the previous year. The applicant in the complaint had been shown the oldest. Nobody acted in bad faith; the artefact simply had no single home, so it had five.
SkillBridge moves the notice onto its ReviewDesk workflow page, redirects the live links, and deletes nothing — the old PDFs are archived into the record with their dates, because past applicants' files reference them. A year later a similar query takes four minutes: one address, current version on screen, the applicant's version one click into the history. The complaint itself was never really about the notice's words. It was about an organisation that could not say what it had told people — and now always can.
Frequently asked questions
Why is a hosted page better than a PDF notice?
One stable address, one current version, an embedded working review form and a recorded version history. PDFs multiply across drives and links, silently diverge from the live process and give requests nowhere structured to land.
Should old notice versions be deleted?
No — they are part of past applicants' decision files. The live page shows the current version; superseded wordings stay retrievable in the audit record with their effective dates.
What should the first screen of the notice say?
The decision, the tool's involvement and the person's headline rights, in plain words, within ten seconds of reading. Detail follows below — but summary and body must never contradict each other.
Does the free tier include a hosted notice page?
Yes. The hosted public pre-use notice page is part of the free workflow, together with the letter generator, inbox and audit trail. The notice builder also runs free with no account for drafting.
Is this guide legal advice?
No. ReviewDesk is templates and workflow tooling, not legal advice. Page practice is described as ReviewDesk implements it; consult counsel for your disclosure obligations.
Keep reading: 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? · How do you answer every human-review request — without sounding like a bot? · 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.