Evidence review dates and staleness

Evidence goes stale quietly: the policy gets superseded, the diagram stops matching the network. Review dates make staleness visible instead of discovered.

Setting a review date

  1. Edit the record (in the Evidence tab, or via add-detail when creating it).
  2. Set review due to when the document should next be checked, typically its owner's review cycle.

The flags

  • Due soon: within 30 days, the date shows amber in the library.
  • Overdue: past the date, the record is flagged and treated as not yet firm evidence, which feeds the dashboard's non-firm line.
  • Records without a review date are never flagged; the mechanism is opt-in per record.
Example
Review dates in the library: amber when due within 30 days, flagged and treated as not yet firm when overdue.

After a reassessment

Copied records keep their review dates, and any already overdue are flagged in the new assessment as possibly out of date. That makes the reassessment's evidence-refresh work visible on day one: re-confirm or update the flagged records, push their review dates forward, and the flags clear.

Can't find what you need? Browse the Resources articles or use the feedback button inside the app.