The modules and how they fit together
Module | What it does | Where it lives |
Controls | The measures that mitigate a psychosocial risk |
|
Records | The evidence that a control is in place: documents, policies, and tests, on a renewal cadence |
|
Incidents | Events that have happened, including worker reports from My ReFresh |
|
Investigations | The structured workflow that runs after a substantiated incident |
|
Consultations | Formal records of worker engagement |
|
Reviews | Formal sign-off, including re-rating how effective a control is |
|
Tasks | The action items that thread across everything above |
|
Documents and policies live in Records: Documents and policies are managed together in a single Records surface. See Records - documents, policies, and tests.
How a risk becomes defensible action
A risk gets controls. Risks identified during assessment (and obligations from any framework you activate) have controls attached. See The control library.
Each control needs evidence. You attach Records (a document, policy, or test) to prove the control is in place. Records renew on a cadence, so evidence stays current. See Adding evidence to a control (Records).
Incidents get reported and triaged. Workers report through My ReFresh, or an admin logs an incident directly; admins then triage each one. See Reporting an incident (admin view).
Substantiated incidents trigger investigations. A structured workflow with scoped access, statements, and findings. See Investigating an incident.
Consultations are recorded against risks, controls, incidents, and more: your evidence of worker engagement.
Reviews re-rate effectiveness. A control's status tells you whether evidence is current; a Review is how a person judges whether the control actually works.
Tasks tie it together. Any module can spin off a task, tracked centrally with a due date, owner, and priority.
Status is not effectiveness: A control's status (Overdue, Due Soon, Incomplete, Complete, Deactivated) reflects whether its evidence is present and current; it is calculated automatically. Effectiveness (whether the control is actually reducing the risk) is a separate judgement made by a person through a Review. A control can be fully evidenced (status Complete) and still be rated less than fully effective, or Not Assessed. See Control effectiveness.
Finding incidents in the nav: Incidents and investigations sit under the Incidents group in the left-hand nav, which expands to Triage Queue, All Incidents, and Investigations. This article names each module by its function and route.