Skip to main content

Safety Orchestration overview

Safety Orchestration is the cluster of ReFresh modules that turn identified risks into trackable, defensible action: controls, evidence, incidents, investigations, consultation, tasks, and the policy and document library.

Written by Harrison Kennedy

Safety Orchestration is the cluster of ReFresh modules that turn identified risks into trackable, defensible action: controls, evidence, incidents, investigations, consultation, tasks, and the policy and document library.

  • Controls are the measures that mitigate psychosocial risks

  • Evidence is the proof a control is in place; uploaded to controls and renewed on a defined cadence

  • Incidents capture events that have happened, including worker reports through My ReFresh

  • Investigations are the structured workflow that runs after an incident

  • Consultations record formal worker engagement

  • Policies and Documents are the managed library that auto-link as evidence

  • Tasks are the action items that thread across all of the above


Where these modules live in the sidebar

In the admin sidebar:

  • Tasks at the top of the sidebar

  • Detection group: Incidents (Triage Queue, All Incidents, Investigations)

  • Risk Assessment group: Consultations

  • Compliance group: Controls; Evidence (Documents, Policies)

  • Governance group: Reviews

The split mirrors the lifecycle: detect what is happening, act on it, prove it, govern it.


How the modules connect

  1. Risks identified during assessment have controls attached (Compliance → Controls).

  2. Each control needs evidence uploaded; documents and policies in the library auto-link as evidence (Compliance → Evidence → Documents / Policies).

  3. Incidents are reported via My ReFresh or admin; admins triage them (Detection → Incidents → Triage Queue).

  4. Substantiated incidents trigger investigations (Detection → Incidents → Investigations).

  5. Consultations are recorded against any of the above (Risk Assessment → Consultations).

  6. Tasks are created from any module and tracked centrally (Tasks).

  7. Reviews capture formal sign-off on controls, documents, and policies (Governance → Reviews).


Related articles

  • The control library (4.2)

  • Reporting an incident (admin view) (4.6)

  • Recording worker consultation (4.9)

  • Managing the policy and document library (4.10)

  • Managing tasks (4.13)

Did this answer your question?