Review cycles
Each configuration type has a review cycle, set on its Settings step in Manage Configuration Types. It decides how often configurations of the type are reviewed.
| Review cycle | A configuration is due |
|---|---|
| Never (the default) | Never: the type is not reviewed. |
| Once | Until it has been reviewed once; never again after that. |
| Every Month | 30 days after its last review. |
| Every Quarter | About 90 days after its last review. |
| Every Six Months | About 182 days after its last review. |
| Every Year | 365 days after its last review. |
| Every Two Years | 730 days after its last review. |
| Every Three Years | 1,095 days after its last review. |
A configuration that has never been reviewed is due as soon as its type has a cycle other than Never.
Where “due” shows
Section titled “Where “due” shows”- In the Configuration Checklist, a due configuration counts under Need Review and as a Warning. A reviewed configuration within its cycle counts under Reviewed. Under Once, a configuration already reviewed counts under neither.
- In MTX, Configs, Review lists the due configurations a review ticket can be generated for: active ones, with no open review ticket, of companies whose type is flagged as your active customer base. See Set up configuration reviews.
What counts as reviewed
Section titled “What counts as reviewed”A configuration is recorded as reviewed when its review ticket is completed with every review task marked. The review date is the day the ticket was completed.