ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
How does an applicant status link change the experience of waiting for a review?
Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing
The short answer. The applicant sees what you see, minus the internals: their case exists, its stage, its deadline, and its outcome when decided — through a personal link that needs no account. Silence is the complaint-generator in every review process; a status link removes the silence without adding correspondence. ReviewDesk's SLA workflow provides the link per case, fed by the same docket the reviewers work from, so the applicant's view can never promise what the queue is not doing.
What is the applicant status link?
An applicant status link is a per-case, tokenised page showing the public state of a human-review request: received, assigned, in review, decided, with the case's deadline and, at the end, its outcome. In ReviewDesk it is generated for each case in the SLA workflow and reads from the case record itself — the same assignment and deadline data the reviewers see.
Why does waiting generate more complaints than losing?
Because an adverse outcome is information, and silence is a vacuum the imagination fills — usually with indifference or conspiracy. Applicants consistently report that the wait, not the decision, is what radicalised them: the unanswered days convert a person who wanted a correction into a person who wants an investigation. Every process designer in this fleet eventually learns the same arithmetic: the cost of a status update is near zero once the docket exists, and the cost of a complaint is measured in staff-weeks. Silence is the most expensive communication strategy available.
The status link is the industrial form of the update: always current, never forgotten, immune to the assignee's holiday. It converts the applicant from a supplicant refreshing their inbox into a watcher sharing your own view of the queue. That shift in posture — from chasing to watching — is the entire experiential difference between a process people describe as fair and one they describe as a wall.
What should the status page show — and hide?
Show: the case reference, the stage in plain words, the date each stage was reached, the deadline the case is working to, and what happens next in one sentence. At decision, the outcome and the full outcome communication. Hide: internal assignee names, other cases, internal notes beyond the applicant-facing summary, and anything about other applicants. The page is a window onto one case, cut exactly to the applicant's legitimate interest — the same scoping discipline as an evidence export, applied to a webpage.
Stage names matter. 'In review' must mean a person has the file open; if your stages are cosmetic — the case displays 'in review' from the moment it arrives — the page becomes a small lie told continuously, and applicants detect it the first time a stage changes seconds after they phone. ReviewDesk's stages derive from the case record — assignment and decision events — so the page can only say what the docket has done. Build any status surface on events, never on timers.
How does the link stay private without an account?
By capability: the link carries an unguessable token bound to the one case, so possession of the link is the credential. That keeps the barrier at zero — no password for an applicant who may interact with you exactly once — while the token's entropy does the security work. The link should be delivered inside the acknowledgement and the outcome letter, never published, and it should expose nothing enumerable: no sequential case numbers that let a stranger walk the queue.
Treat the link as personal data's key. It belongs in the case's own communications, it expires gracefully long after the case closes, and its access is not logged against the applicant in any way that could colour the review. A reviewer should never know how often an applicant checked their status; the watcher must be free to watch. That separation is a small integrity rule with large trust consequences.
How does the status link change reviewer behaviour?
For the better, through visibility. A queue whose stages are publicly worn is a queue that keeps its stages honest: assignment happens promptly because 'received' ages visibly; decisions communicate because 'decided' without an outcome letter is a visible contradiction. Reviewers working under a status link describe the sensation as being accompanied rather than surveilled — the applicant's patience is visible in the design, which quietly raises the moral cost of letting a case drift.
It also disciplines escalation. When a case escalates, the applicant's page shows the stage honestly with the applicant-facing summary of the escalation note — the practice from the escalation guide. Reviewers who know the note will be summarised publicly write better notes: factual, dated, next-step clear. Publicness, dosed correctly, is a quality system.
What should the decided state deliver?
The complete outcome, not a teaser. The decision, the reviewer's reasons in their engaged form, what was corrected if anything, what happens next and what remains open to the applicant — correction of anything still wrong, re-application where relevant. Making the applicant phone for the substance after a link told them 'decided' would squander the entire pattern at its moment of truth. The outcome letter generated from the case record supplies the text; the status page is its always-available copy.
Keep the decided page alive. Applicants return to outcome letters — before re-applying, when advising a friend, when a similar decision arrives from another organisation. A decided case page that persists with its full history is a small permanent embassy for your process. Its tone will be quoted; write it accordingly, with the care from the letter-tone guide.
How do you introduce a status link into an existing process?
At the acknowledgement, which is where anxiety peaks. The acknowledgement message gains one line — 'follow your case here' — and the link does the rest. No applicant education campaign is needed; the pattern is familiar from every delivery and application tracker in modern life, which is precisely its power: your review process inherits the trust grammar of systems people already understand. ReviewDesk generates the link per case automatically in the SLA workflow, so introduction is a template line, not a project.
Measure what changes: inbound 'any update?' contacts should fall within a month, and complaint language should shift from silence to substance. If contacts do not fall, read the page as an applicant would — the stages may be too vague, the next-step sentence missing, the deadline unexplained. The link is a product surface; iterate it like one, from the case record outward, never by decorating the page while the docket behind it stays opaque.
Your five actions for the applicant status link
- Generate a per-case status link at acknowledgement, reading stages from real case events — assignment and decision, never timers.
- Show stage, stage dates, the deadline with its meaning, and one next-step sentence; hide assignees and all internal data.
- Use an unguessable per-case token; no account, no enumerable case numbers, and never let reviewers see view counts.
- Deliver the complete outcome on the decided page — reasons, corrections, next steps — and keep the page alive after closure.
- Track 'any update?' contacts after launch; if they do not fall, fix the page's clarity before anything else.
Worked example: the applicant who stopped phoning
A fictional lettings group — Harbor Lets — used to field around sixty 'any update?' calls a week across its offices, each one pulling a file, each one answered from memory by whoever picked up. After switching its screening workflow to ReviewDesk with status links in every acknowledgement, the calls fall to under fifteen in the first month — and the remaining callers mostly ask substantive questions about their documents, because the status question has already been answered by the page.
One applicant's case escalates in its final third while a court record is verified. Her status page shows the escalation summary — record confirmation outstanding, chased, next update on a named date — and she waits without a single call. Her eventual approval letter closes a case she watched happen. Harbor Lets' staff describe the change plainly: the phone stopped being the status system, so the phone could become the help system again.
Frequently asked questions
What is an applicant status link?
A personal, tokenised page showing one review case's public state — received, assigned, in review, decided — with its deadline and full outcome. In ReviewDesk it is generated per case in the SLA workflow and reads from the case record itself.
Does the applicant need an account?
No. The link's unguessable token is the credential, keeping the barrier at zero for a person who may interact with you once. The page exposes only that case — no assignee names, no internal notes, nothing enumerable.
What if a case is delayed?
The page shows the escalation honestly with the applicant-facing summary: what is awaited, what has been done, the next update date. A visible managed delay generates far fewer complaints than silence.
Can the reviewer see how often the applicant checks?
No — and that separation is deliberate. The applicant must be free to watch without the watching becoming part of their file.
Is this guide legal advice?
No. ReviewDesk is templates and workflow tooling, not legal advice. The status link is described as ReviewDesk implements it; consult counsel for your situation.
Keep reading: How should human-review cases be assigned across a team? · What should a review case's decision history record? · How does the 3-year evidence vault export a complete decision file? · What should you ask a software vendor before you rely on their tool for consequential decisions? · ADMT duties explained for software vendors and the businesses that deploy their tools · 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.