Core Fields: Risk

Modified on Thu, 3 Sep at 4:55 PM

Core Fields: Risk

The configurable fields available for the Risk module, and what each one is for


Contents


1. Introduction & Context


This article lists every core field available for the Risk module, what each one is for, and where to control whether it appears in list views, the New and Edit forms, Mass Edit, and the record's Show View (detail page).


Who is it for? This is configured by Clew Admins in Admin Settings, under Custom Types > Risk.

What does it impact? These settings control what your team sees and can enter on Risk records, not the underlying data itself. Turning a field off in a given screen hides it there, but does not delete any information already stored against existing records.

Note: This article assumes you already know how List View Columns and Core Field Settings work. For a general explanation of the mechanics, including what the All Visible, New Form, Edit Form, Mass Edit Form, and Show View columns mean, see Core Fields: Overview first.

2. Key Features & Functions

  • 38 configurable core fields: covering ownership, approval, risk assessment content, dates, record metadata, and classification, listed in full in Section 4.
  • 6 fixed fields: Type, ID #, Risk Title, and the three risk rating fields (Inherent, Residual, and ALARP) are always available and not part of the configurable list.
  • Default list view columns: out of the box, the Risk list view shows Type, ID #, Inherent Risk Rating, Residual Risk Rating, ALARP Risk Rating, Risk Title, Status, Register, Location, and Review Date.

3. Requirements

  • Clew Admin access, to open Admin Settings and Custom Types > Risk.
  • The Risk module must already be enabled in Clew.

4. Step-by-Step Guide

Risk: Core Field Visibility

  1. Go to Admin Settings and open Custom Types.
  2. Select Risk.
  3. Scroll to Core Field Settings. Use the search box to find a specific field if the list is long.
  4. Update fields individually using the eye icons, or select several rows and use Mass Edit. See Core Fields: Overview for how these controls work.

Risk: Field Reference

The configurable core fields available for the Risk module, grouped by what they're used for:

Ownership & Approval

FieldWhat it's for
OwnerThe person accountable for managing the risk.
Owner RoleThe role the Owner holds.
AssigneeThe person the record, or an action arising from it, is currently assigned to.
Assignee RoleThe role the assignee holds, shown alongside or instead of their name.
AssigneesEveryone currently assigned to the record, where more than one person can be assigned.
Assignee RolesThe roles of everyone assigned, where a record supports more than one assignee.
AuthoriserThe person who authorises the record, for example signing off the risk assessment.
Authoriser RoleThe role the authoriser holds.
Approver RoleThe role (rather than a named person) responsible for approving the record.
Risk ApproverThe person responsible for approving the risk assessment.
SanctionerThe person who gives final sign-off on the risk, as an additional approval step beyond the Approver.
Sanctioner RoleThe role the Sanctioner holds.
Project.OwnerThe owner assigned at the project level, where the risk is linked to a specific project.
Project.Owner RoleThe role of the project-level owner.
Project.ApproverThe approver assigned at the project level.
Project.Approver RoleThe role of the project-level approver.

Risk Assessment Content

FieldWhat it's for
Risk Description/SummaryA written description summarising the risk.
CausesThe underlying cause(s) that could lead to the risk occurring.
ConsequencesThe potential outcomes or impacts if the risk occurs.
IndicatorsKey risk indicators or early warning signs associated with the risk.
RatingsThe overall risk rating(s) calculated for the record, combining factors such as likelihood and consequence.
Business ObjectivesThe organisational objective(s) that this risk relates to or could affect.
Business UnitThe business unit or department the risk belongs to.
LocationThe physical or organisational location the risk relates to.
HubsThe organisational hub(s) or grouped site/location the risk is linked to, for organisations that use hubs.
RegisterThe register the risk belongs to, for example Strategic or Operational.

Dates & Scheduling

FieldWhat it's for
Action WindowThe period during which an action linked to the risk is expected to be actioned.
Risk WindowThe period during which the risk is considered active or relevant (shown as separate Start and End dates on some forms).
Review DateThe date the risk is next due to be reviewed.
Original Due DateThe due date originally set for the risk or its actions, before any extension.

Record Metadata

FieldWhat it's for
Created atThe date and time the record was first created.
Created byThe user who created the record.
Updated atThe date and time the record was last updated.
Closed atThe date and time the record was closed.

Classification & Status

FieldWhat it's for
StatusThe record's current position in its workflow, for example Draft, Open, or Closed.
ModeA classification field on the risk record.
MaterialFlags whether the risk is considered material, that is, significant enough to warrant particular attention such as board-level reporting.
SensitivityFlags whether the record is sensitive, which can restrict who is able to view it.

A small number of additional fields are fixed and always available, rather than being configurable through Core Field Settings:

  • Type: the record type classification, distinguishing this custom type (Risk) within its module.
  • ID #: the unique identifier number automatically assigned to the record.
  • Risk Title: the short name or title given to the risk record.
  • Inherent Risk Rating: the risk rating before any controls or mitigations are taken into account.
  • Residual Risk Rating: the risk rating that remains after existing controls and mitigations are applied.
  • ALARP Risk Rating: the risk rating assessed against the As Low As Reasonably Practicable (ALARP) principle, used to judge whether further mitigation is warranted.

5. Common Issues & Troubleshooting


These issues apply to Risk the same way they do to every module. See Core Fields: Overview for the general troubleshooting table and best practices.

IssueLikely CauseSolution
A Risk field doesn't appear on a form or Show ViewThat specific column is switched off for the field in Risk's Core Field SettingsOpen Custom Types > Risk > Core Field Settings and switch on the relevant column for that field
A field isn't listed under Risk's Available Fields or Core Field Settings at allThe field has not been enabled for your organisationRaise a request with Clew support to have the field enabled for Risk

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article