Skip to main content
The Review Queue is where qualified people sign off on governed content before it is released. When the Quality Gate finds that a document needs medical, legal, compliance, brand, or editorial review, those reviews are assigned to members who hold the matching qualification, and each decision is recorded against the exact version reviewed.
Required reviews gate publication. Before any send to a publishing destination, WriterzRoom requires a current approval for every required review role, bound to the exact version being released. A changed document, a waiver, or a reviewer who has lost the qualification or access to the uploaded evidence holds the release until it is reviewed again. See Publishing.

Qualifications and Permissions

Review qualifications describe subject-matter competency. Workspace roles describe product access. They are separate controls. An administrator does not automatically qualify for any governed review. Organization admins set qualifications under Workspace → Team after a member accepts the invitation.

Review Categories

One document can require several categories, reviewed in stages. Filter the queue by category to work one discipline at a time.

How Assignment Works

  1. The Quality Gate records required approvals in the asset’s content passport.
  2. The generation finalizer persists those obligations as review records.
  3. For each role, WriterzRoom selects an active organization member with the matching qualification.
  4. Selection is deterministic for the request-and-role pair, so retries do not move work unexpectedly.
  5. Reviews at the same stage can proceed in parallel; later stages wait until earlier required reviews are resolved.
If no qualified member exists, the obligation remains unassigned. Adding a qualification assigns matching pending work immediately. Removing a qualification revokes that member’s pending assignments and reroutes them when another eligible reviewer exists.

Review an Asset

1

Find the work

The queue lists reviews you own and reviews assigned to you, pending first, with counts of assigned, overdue, and escalated work.
2

Inspect the record

Open a review to see the full document with everything a decision needs: why it was routed to this role, the release under review, uploaded evidence, anything still unresolved before release, and how many required reviews have cleared.
3

Record a decision

Choose Approve, Request changes, Reject, or Waive. Every decision other than an approval needs a reason: unsupported claim, missing evidence, inaccurate statement, missing disclosure, regulatory risk, brand or tone, not applicable, or other (explained in the notes). Required later-stage reviews remain locked until the current stage is resolved.When an applying policy requires separation of duties, the asset’s author cannot approve it, and one reviewer cannot approve two review roles on the same version. Release rechecks both.
4

Request evidence when needed

A changes request can name the claim, source index, and missing substantiation so the next revision has an auditable checklist rather than only free-form feedback.
5

Decide in bulk

Select all decidable reviews selects every pending review in view that you can decide, without opening each one. One set of notes applies to every selected item, and a rejection needs a reason. Each decision is bound to the version the queue loaded; an asset that changed since is refused and reported rather than approved. Stage order and separation of duties still apply per item: every selected role at a document’s earliest open stage is decided together, and later-stage selections stay selected until that stage clears.
Each review is one role on one document, so a document routed to legal and compliance is two reviews.

Review States

Every review is in one of these states: If the release or the assignment changes after you open a review, your decision is refused rather than recorded against a version you did not see. Reload the review and decide on the current version.

Recovery and Escalation

An internal hourly sweep repairs missing or partial review routes, assigns unassigned work when qualified members become available, and marks overdue approvals for escalation. Immediate routing remains the normal path; the sweep is a recovery control. Every assignment — immediate or from the sweep — emails the reviewer, respecting their notification preference. It is not a webhook and does not fire on decisions, only on assignment.

API

All endpoints below use the standard API base URL and authenticated user API key. reason_code is required for rejected, changes_requested and waived, and must be omitted for approved. Values: unsupported_claim, missing_evidence, inaccurate_statement, missing_disclosure, regulatory_risk, brand_or_tone, not_applicable, other (requires notes).

Content Governance

Learn how review obligations are derived and recorded.

Workspace

Manage organization members and permissions.
Last modified on October 25, 2026