Review due

Review due lists published content that operators are still holding but nobody has re-checked within your agency's re-validation interval. Open it from the sidebar under Workflow → Review due; the sidebar shows it to people who hold Edit content or Publish.

It is not the review queue. The Review queue (opens the admin console) holds items an author has submitted and that are not yet live; this page holds items that are live and have gone stale. The two use different clocks.

How "overdue" is worked out

Every published item has a re-validation date: its last-reviewed date — or, if it has none, the date it was published — plus the interval for its content type. Once that date passes, the item appears here.

The interval comes from Settings → Review policy (opens the admin console): one default for everything, with an optional override per content type, so a swiftwater checklist can fall due every 180 days while a background article runs to two years. Out of the box, every type uses 365 days.

The last-reviewed date — and with it the clock — is reset when someone marks the item reviewed, on this page or in bulk from All content. It is also reset when a publisher publishes the item — from the editor or in bulk from All content — or saves changes to it from the editor while it is published.

Every item past its own type's date is listed, however long the default interval is: a 90-day checklist last reviewed 200 days ago appears even when everything else runs on 365 days.

Columns

Items are listed most overdue first.

People with Edit content but not Publish see the list without the checkboxes or the Action column — they can open each item, but not sign off that it was re-checked.

Mark reviewed

Re-check the item first: open it, compare it with current practice, and fix anything that has changed. Then select Mark reviewed on its row. What happens next:

• The item's last-reviewed date becomes now, and you are recorded as its reviewer.
• It leaves this list. Its next re-validation date is now plus the interval for its type.
• The content itself is untouched. Operators see no change and get no notification, and any two-person sign-off approvals on the item still stand.

Only people who hold Publish can change the last-reviewed date; the database refuses the change from anyone else, whatever the screen shows.

Marking several at once

Tick the items' checkboxes, or the checkbox in the header to select every overdue item. A bar appears above the table showing how many are selected, with Mark N reviewed and Clear. Mark N reviewed stamps every selected item in one go, with the same effect as marking each one individually. Clear drops the selection without changing anything.

Reminders in the bell

Once a day, the database looks for published items past their re-validation date — reading the same review policy this page uses, so the two always agree on what "overdue" means. For each one it finds, everyone who holds Publish gets a notification in the bell: "“…” is overdue for re-validation". Selecting it opens this page. These reminders are not emailed unless you tick Review overdue in your email preferences.

Each item triggers that reminder at most once every 30 days, so an item left overdue is raised again roughly monthly until someone marks it reviewed.

When the page is empty or fails

• Loading… shows while the policy and the list load.
• "Every published item is inside its review interval (default N days)." means nothing is overdue; N is your agency's default interval.
• If the list cannot be loaded, the error message appears in place of the table.

This page does not refresh by itself. Reload it to pick up items that fell due, or were marked reviewed by someone else, while you had it open.