Skip to main content

Adopting risks from the scenario library

The scenario library is ReFresh's set of pre-built psychosocial risk scenarios, mapped to your active frameworks. Adopt one and it lands in your risk register already populated with indicators and linked controls, ready to assess.

Written by Taylor Laing

Opening the library

From the Risk Register, click Explore Library to open the Scenario Library. It presents the scenarios in four tabs:

  • Strongly Recommended: the highest-priority scenarios for your active frameworks

  • Recommended: scenarios commonly adopted in your context

  • Optional: scenarios available but not flagged for your context

  • All Scenarios: the full library

Each tab shows a count of the scenarios it contains, and you can filter the library by hazard category and hierarchy level.

What each scenario shows

Each scenario lists its name and code, the active frameworks it applies to, its psychosocial category, and its recommended hierarchy-of-controls target level. Scenarios already in your register are tagged as such.

Adopting a scenario

Open a scenario to see its full description, indicators, and pre-linked controls, then adopt it. Adopting a scenario:

  • Adds it to your Risk Register as a new risk

  • Pre-populates its indicators and recommended controls

  • Sets the Source to Adopted

  • Leaves the assessment in its initial state, ready for you to rate inherent and residual risk

You can adopt the same scenario at more than one organisational level: for example an org-wide assessment and a site-specific one.

Framework activation and scenarios

Activating a framework adds its controls, documents, and policies to your register; it does not auto-create risk assessments. You adopt the scenarios you want from the Scenario Library, where the tabs help you prioritise (Strongly Recommended first).

Customising an adopted scenario

Once a scenario is in your register you can edit its title and description, adjust the inherent and residual ratings as you assess it, add or remove linked controls, and move it through the lifecycle. Its link back to the source library entry is preserved, so you can always compare your version to the original.

Did this answer your question?