·¬ÇÑÉçÇø

The following examples describe Brightspot's review-cycle timelines.

Cycle duration and warning duration

An editorial board wants to implement the following review policy for the asset Terms and Conditions:

• A new revision of the asset is published every 30 days.
• A banner appears in the asset's content edit form 10 days before the new revision is due.
• Notifications are sent to relevant editors seven days before the new revision is due.
• Notifications are again sent to relevant editors three days before the new revision is due.

The following diagram illustrates this policy.

Referring to the previous diagram—

• An editor publishes the asset on April 1.
• On April 20 (start of the banner warning duration), the content edit form includes a banner indicating that the review is coming due.
  

  

• On April 23 (start of the first notification warning duration), Brightspot sends notifications to editors subscribed to review cycle messages.
• On April 27 (start of the second notification warning duration), Brightspot again sends notifications to editors watching the asset.
• By May 1, an editor starts a new revision of the asset and publishes it.

Restarting review cycles

An asset's review cycle restarts on the most recent date the asset was published. Suppose an asset is on a 30-day review cycle, but an editor published the new revision 10 days late. In this case, the second review cycle starts on day 40, and ends 30 days after that.

Similarly, for the same asset, an editor published the new revision five days early. In this case, the second review cycle starts on day 25, and ends 30 days after that.