Reference
Review policy
Set how long published guidance stays valid before it is due for re-validation, overall and per content type, and the default deadline and priority for assigned reviews.
Settings → Review policy sets two separate clocks for your agency. Open it from Organization → Settings, then the Review policy card.
- The re-validation interval is a deadline for the content: how long published guidance may go without anyone confirming it is still right.
- The assignment SLA is a deadline for a person: how long a reviewer has once a review is handed to them.
They answer different questions and apply at different stages, so the page keeps them in separate cards: the SLA runs while an item waits in review, and the re-validation interval runs once it is published. See how re-validation works.
Re-validation interval
| Field | What it does | Range |
|---|---|---|
| Default interval (days) | How long any published item stays valid before it is due for re-validation | 1 to 3650 |
| Per type | An override for one content type: Guides, Articles, Checklists, Quizzes, Video, Audio | 1 to 3650 |
Leave a per-type box blank to use the default — the blank box shows the default as a grey placeholder. A swiftwater checklist usually needs re-checking far more often than a background article; this is where you say so. Numbers outside the range are pulled back to the nearest limit as you type.
How the clock is counted
An item's interval runs from its last-reviewed date, or from when it was published if it has none. The last-reviewed date is set when someone marks the item reviewed, and also whenever a publisher publishes it or saves changes to it while it stays published — saving a published item from the editor counts as re-confirming it. Nothing else restarts the clock.
Where the interval is used
One setting drives everything that talks about "overdue", so no two screens disagree:
- The Review due (opens the admin console) page lists published items past their interval and shows the interval that applies to each. See Review due.
- The editorial calendar places each published item's review-due marker by it.
- The dashboard's Going stale widget counts items past their interval or within 30 days of it.
- Once a day, the database checks every published item against the same setting. For each item past its interval it sends a bell notification — "“title” is overdue for re-validation" — to every member who holds Publish. While the item stays overdue, the reminder repeats at most once every 30 days.
The database reads this page's setting directly, which is why the daily reminder and the Review due page cannot disagree about what overdue means.
Assignment SLA
The defaults applied when a review is assigned without its own due date or priority.
| Field | What it does | Range |
|---|---|---|
| Turnaround (days) | How many days a reviewer gets from the moment a review is assigned to them | 1 to 365 |
| Default priority | The priority given to a newly assigned review | Low, Normal, High, Urgent |
What happens when someone assigns a reviewer on the Review queue (opens the admin console):
- If the item has no due date yet, it gets one: today plus the Turnaround.
- If the item's priority is still Normal, it is set to your Default priority.
- The assigner can change either on the queue row afterwards. Unassigning clears the due date, so the next assignment starts a fresh SLA.
The queue's header repeats the current turnaround ("New assignments default to … days"). See Review queue for assigning and prioritising.
Defaults for a new agency
A new agency starts with a 365-day default interval, no per-type overrides, a 14-day turnaround and Normal priority. The same values apply if the setting is ever missing.
Save
Select Save. The button reads Saving… while it works, then "Saved." appears beside it. Both cards save together.
The new interval applies straight away to the Review due page, the calendar and the dashboard the next time they load, and to the next daily reminder run. A shorter interval can therefore put a batch of items on Review due at once.
If the save is refused, the database's message appears at the top of the page and nothing changes. The page appears only for people who hold Manage settings, and the database refuses changes to the policy from anyone else. Everyone in the agency can read it — the queues and the calendar need it to work out their dates.
See also
- ReferenceReview duePublished content that has gone past its re-validation interval — see how overdue each item is and mark items reviewed once they have been re-checked, one at a time or in bulk.
- ReferenceReview queueEvery item waiting for review — assign a reviewer, set a due date and priority, give a second approval, or send an item back to its author — and published items with changes awaiting release.
- ReferenceCalendarScheduled publishes, publish history and re-validation deadlines on one month, week or agenda view — filter by type, status or author, and drag a scheduled item to another day.
- ReferenceDashboardEvery widget on the dashboard, what it counts, why it might not be there, and which page owns the work behind it.
- How it worksHow publishing worksThe path a piece of content takes from a blank draft to something an operator can read offline — and what the database will and won't let you skip.