You don't run the scanning: Keeping frameworks current against the regulators is work ReFresh does for you. What you see is the result: an entry telling you something relevant changed, and a clear picture of what to review.
What triggers an update
ReFresh publishes a framework update when:
A regulator amends or replaces the underlying legislation, code of practice, or standard
A new obligation is added to an existing framework
An existing obligation is materially clarified or restructured
A framework is split, merged, or renamed
Each update is published with a description of what changed and which controls or documents it affects.
Where to see updates
Go to the admin sidebar, then Compliance, then Frameworks, and open the Recent Updates tab. The tab shows a count of updates currently relevant to your active frameworks. If the count is zero, your active frameworks are all on the latest published version.
Each entry carries a change-type tag, a title, a one-line summary, and a date:
Control Updates: changes to the controls behind a framework
Breaking Changes: changes that need your review of affected items
Requirement Updates: changes to a framework's obligations or requirements
Framework Changes: a framework being split, merged, renamed, or otherwise restructured
For example, you might see "New Digital Work and AI Controls" (tagged Control Updates and Breaking Changes) or "NSW Regulation 2025 mandates hierarchy of control" (tagged Requirement Updates).
Australian and international framing: Regulatory-change tracking follows the WHS and psychosocial legislation behind your active frameworks (Australian Commonwealth, state, and territory codes, plus the international ISO 45003 standard and the other jurisdictions ReFresh ships). It is not tied to any single national gazette.
Breaking vs non-breaking changes
Every update is classified so you can tell at a glance whether it needs action:
Breaking changes affect existing controls, obligations, or evidence in a way that needs your review. The status on the affected items resets so it's obvious what to look at.
Non-breaking changes are clarifications or wording adjustments that don't affect your existing controls or evidence. Nothing resets.
The framework's detail page shows the change description so you can see exactly what was modified.
What happens when a status resets
When a breaking change resets a status, the affected controls or documents are flagged for review so the change can't pass unnoticed. Any owners assigned to those items are prompted to reaffirm or update them, and the dashboard reflects the new gap until you address it.
Nothing is lost: The activity log retains the prior version, so you can always see what the previous state was and when it changed. Reaffirming an item after review clears the flag.
From update to action
A Recent Updates entry is the start of a short workflow:
Review the entry to understand what changed and which parts of your program it touches.
Check the affected items. Breaking changes reset the status of affected controls or documents so it's obvious what to look at.
Reaffirm or update. Update the affected controls, evidence, or policies, complete any reviews, and reaffirm the items.