![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
Organizations use the concept of freshness in one of two ways:
As an automated reminder to review and test proof linked to controls
As a way to review the accuracy of control language
When you set a freshness policy, you define its expiration period. At the end of this period, the freshness status automatically changes from Fresh to Expired. When freshness expires, the control manager determines if it needs to be updated and creates a task to collect updated evidence.
The freshness status is displayed throughout Hyperproof, including on program dashboards and work items, and is communicated via email notifications and dashboards (when items are set to expire). Expiration is a signal that you need to revisit your control and reexamine its contents to determine if any linked proof needs to be updated.
To use freshness
📝 Note
Your organization may choose to use freshness to trigger a review of control language instead of or in addition to reviewing proof.
Enable freshness for one or more controls or labels. See Turning on freshness on a control or label and Setting freshness on multiple controls or labels.
Review the proof on the controls and labels. If the proof is up-to-date, mark them as fresh and set an expiration date. See Step Two: Marking the control or label as fresh and Setting freshness on multiple controls or labels.
Use the Needs Attention panel on the Program dashboard to watch for controls and labels that are expired or nearing their expiration date. See Explore by and Work/Needs attention panels panels.
For more information see the Freshness on controls and labels tutorial:
🔗 Embedded content: Open link