Skip to main content

How content review dates and notifications work

Log in to add to favourites

Page last updated 19 November 2026

Each published entry has its own review clock, set by the review schedule on its content type. This guide explains how that clock works, what restarts it, and which emails you can expect.

How the review schedule works

You set the schedule once, on the content type, using two values:

  • Review period (days) is how long after publishing an entry is due for review.
  • Review window (days before due date) is how early the entry is flagged before it is due.

Every entry of that content type follows the same schedule. You cannot give a single entry its own review period, or combine the content type schedule with a different one on an entry.

For each published entry, Contensis works out two dates:

  • Due date is the publish date plus the review period.
  • Review window opens the number of window days before the due date.

For example, an entry published on 2 March 2026 in a content type with a 180-day review period and a 30-day review window has a due date of 29 August 2026. Its review window opens on 30 July 2026.

What restarts the review clock

The clock restarts every time the entry changes.

  • Saving an edit to a published entry clears its pending review and any reminders that were due.
  • Republishing the entry schedules a new review for the publish date plus the review period, with a new review window.

This applies however small the edit is. Correcting a typo and republishing restarts the full review period, so an entry that is edited often may never reach its review window.

What happens when you enable or change the review schedule

When you enable scheduled reviews on a content type, or change its review period or review window, and publish the content type, Contensis recalculates the due date of every published entry as its publish date plus the review period.

Entries published longer ago than the review period become overdue straight away, and Contensis sends an overdue email for each one. For example, if you change a content type from 365 days to 180 days, any entry published more than 180 days ago is immediately overdue. The same happens if you enable reviews with a 180-day period on a content type that has entries published years ago. Reviewers can receive a large number of overdue emails at once.

Scheduled reviews and on-demand requests

A scheduled review is created automatically for every published entry. An on-demand request is a one-off review that someone starts from the content review panel using Request a review.

Scheduled reviewOn-demand request
Created byContensis, from the content type scheduleA person, from the content review panel
Due datePublish date plus the review periodSet by the person who requests it, 14 days from today by default
RepeatsYes, each time the entry is republishedNo, it is a single review
Reminder emailsYes, see belowNo

Requesting a review replaces the entry's scheduled review until the requested review is completed or the entry is edited. It does not start a repeating cycle of its own.

Which emails Contensis sends

For each scheduled review, Contensis sends at most two emails, and each is sent once:

EmailWhen it is sent
Entry awaiting your reviewWhen the review window opens, which is the due date minus the review window days.
An entry is overdue for your reviewWhen the due date passes.

Contensis does not send repeating reminders while an entry stays overdue.

Both emails go to the assigned reviewer. If no reviewer is assigned, they go to everyone who has review permission for that entry.

Other review emails

These are sent once, when the event happens:

  • You are assigned as a reviewer.
  • A review is requested. This is the only email an on-demand request sends. Requesting a review removes the entry's due and overdue reminders and does not create new ones.
  • A review fails.

You can turn off email notifications in your user profile. See Understanding email notifications.

Still need help?

If you still need help after reading this article, don't hesitate to reach out to the Contensis community on Slack or raise a support ticket to get help from our team.
New support request