Build a Review Queue for a Health Information Site

A review queue gives editors one place to see which pages need attention, why they need it, and who will decide the next step. Start with a page inventory and add an item when a scheduled review is due, a source changes, or a reader reports a possible problem. Each item should lead to a recorded decision, including when the reviewer decides that the published text can stay as it is.

Connect each question to the page version and evidence. Specify the section and the source that needs checking.

Create an item that can be acted on

Give each item a stable identifier and a link to the page. Record the page title, the affected section, the version currently published, and the reason for review. Add the source or report that raised the question and a short description of what is uncertain.

A practical queue entry can include:

  • Page and location. The public address, section heading, and any related download or summary that may need checking.
  • Trigger. A scheduled review, changed source, broken link, reader message, or another clearly described event.
  • Owner and reviewer. The person coordinating the item and the person with the right knowledge to assess the question.
  • Next action and date. A specific action, the date it is due, and a place to record delays.
  • Evidence and result. References to the versions checked, the decision, and any remaining question.
  • Publication check. The status of the approved change and a record of what was observed on the live page.

Keep a distinction between the person who coordinates a task and the person who can assess its content. A site editor may be able to fix a broken link, while an interpretation question may need a reviewer with relevant subject expertise. Record that assignment instead of allowing a technical fix to close the whole item by accident.

Combine scheduled reviews with new events

A scheduled review asks whether a page and its sources still support the published text. Choose an interval through the publication’s own editorial policy, and keep the reason for that choice in the page record. Different pages may need different review dates. A page’s previous review date is evidence of a past check only when the team can identify what was actually reviewed.

A triggered review begins with a specific event. For example, a cited organization may publish a new version of a document, a reader may report a date that does not match the source, or a link may stop working. Capture the event and identify the affected sentence before deciding whether to change the page.

Do not wait for the next scheduled date to record a question that needs attention now. Give the item an owner, describe what the team knows, and decide whether the page needs an interim status while the question is investigated. If an item depends on another team, record the request and the next follow-up date.

Set priorities that the team can explain

Use a small set of statuses and priorities that editors apply consistently. Priority can reflect the nature of the question, the number of affected surfaces, and whether the relevant wording remains available to readers. The queue should let a lead editor distinguish an unverified claim question from a broken navigation link without assuming that either task is already resolved.

Review the queue for items without owners or next steps and for overdue work. If several pages rely on the same source, link their individual records to a shared investigation.

A useful status sequence might be “new,” “assigned,” “in review,” “awaiting publication,” and “verified.” Add a separate outcome for “reviewed, no change” so that a completed assessment remains visible. Reopen an item when the published result does not match the approved decision.

Follow a fictional item through the queue

Imagine that a reader reports a broken source link in a page about a publisher’s review process. The coordinator creates item Q-14, records the page and paragraph, and assigns an editor to find the source. The editor discovers that the publisher moved the document to a new address and also issued a revised edition.

The editor records both versions and sends the relevant passages to the assigned reviewer. In this fictional example, the reviewer finds that the sentence on the page describes the earlier edition accurately but needs a different date to describe the new one. The team agrees to update the date and the reference together. The queue item records the approved wording, the source version, and the person responsible for publishing.

After publication, another editor opens the live page, follows the new link, and checks that the date matches the approved revision. The item moves to “verified,” with the check date and a reference to the evidence. The team also creates a related task for a downloadable summary that contains the old date. The original item links to that task, so the outstanding copy remains visible.

Record reviews that produce no change

A completed review should say what was checked and what the reviewer decided. If the current page remains appropriate, list the source versions inspected, the review date, the reviewer, and the reason no revision was needed. Set the next review date under the publication’s policy.

Connect approval and public verification to the item. Give a separate question its own follow-up and owner.

Frequently asked questions

Should every page have its own queue item? Keep an inventory entry for every page. Create or activate a review item when there is a scheduled or triggered task, using a consistent method that your team can maintain.

Who sets the next review date? Assign that decision to the page owner under the publication’s editorial policy. Record the date and the basis for it so the next editor can understand the schedule.

What if the source link works again before review? Check that it leads to the intended document and version. Record the outcome and close the link task only after the relevant page has been verified.

Can an item be closed when the editor approves a change? Use a publication-verification step before closing it. Check the live wording and link, then record any related copies that remain open.