Skip to content

Risk Management

Risk management illustration

The Risk Register provides a comprehensive view of your organisation’s risk landscape. Assess inherent and residual risks, link them to SCF controls, and visualise your risk posture using an interactive 5x5 matrix.

Navigate to Risk Register in the sidebar (under the Risk & Third Party section).

Risk TypeDefinition
Inherent RiskThe risk level before any controls are implemented — the raw exposure
Residual RiskThe risk level after controls are in place — the remaining exposure

The goal of risk management is to reduce inherent risk to an acceptable residual level through effective controls.

Risks are plotted on a matrix of Likelihood (1-5) vs Impact (1-5):

Likelihood Scale:

ScoreLabelDescription
1RareMay occur only in exceptional circumstances
2UnlikelyCould occur but not expected
3PossibleMight occur at some time
4LikelyWill probably occur in most circumstances
5Almost CertainExpected to occur in most circumstances

Impact Scale:

ScoreLabelDescription
1InsignificantMinimal impact, easily absorbed
2MinorSome impact, manageable with existing resources
3ModerateNoticeable impact, requires management attention
4MajorSignificant impact, potential harm to operations
5SevereCritical impact, could threaten organisation viability

The product of Likelihood × Impact determines the risk level:

Score RangeLevelColour
1-4LowGreen
5-9MediumYellow
10-16HighOrange
17-25CriticalRed

The matrix displays all assessed risks as dots in their corresponding cells:

  • Toggle Inherent/Residual — Switch between viewing inherent or residual risk positions
  • Click a cell — See which risks fall in that likelihood/impact combination
  • Summary bar — Shows count of risks at each level (Low/Medium/High/Critical)

Toggle to list view for a tabular format showing:

  • Risk code and name
  • Current likelihood and impact scores
  • Inherent and residual risk levels
  • Treatment status
  • Risk owner
  • Last updated date

Click any risk to open it full-width, with a breadcrumb back to the Risk Register, a “k of N” pager and ←/→ to step between risks. It shows:

  • Full risk description from the SCF risk catalog
  • Likelihood and impact scores (editable)
  • Treatment status and notes
  • Linked controls from the SCF catalog
  • Risk owner assignment
  1. Click on a risk in the matrix or list
  2. In the detail panel, set the Likelihood (1-5)
  3. Set the Impact (1-5)
  4. The inherent risk level calculates automatically
  5. Click Save

After implementing controls:

  1. Open the risk assessment
  2. Scroll to Residual Risk section
  3. Set Residual Likelihood and Residual Impact
  4. The system shows how much risk reduction you’ve achieved
  5. Click Save

Track your response to each risk:

StatusMeaning
IdentifiedRisk has been identified but not yet assessed
AnalysedRisk has been assessed and awaits a treatment decision
TreatingImplementing controls to address the risk
TreatedTreatment is complete
MonitoringControls in place, ongoing monitoring
AcceptedRisk accepted at its current level. See Risk Acceptance for the admin approval it needs
  1. Open the risk assessment
  2. Click the Owner dropdown
  3. Select a team member
  4. The owner is responsible for monitoring and treating this risk

Accepting a risk is a decision someone answers for. The platform records it with the admin who approved it, when, a rationale and an expiry date, so you can show an auditor who accepted each risk, why, and until when. Use it when your organisation decides to live with a risk rather than treat it further, including a documented exception to one of your standards (see Custom Organisation Risks).

Risk acceptance supports the SCRMS Prioritized Implementation Guide (PIG).

Supports PIG steps 2b, 3b, 3e and 28.

Who can do it: everyone can see a risk’s acceptance. Only an organisation admin can accept, approve, renew or withdraw one. The admin who records the decision is recorded as the approver. Changing the risk’s scores withdraws the approval, whoever makes the change, until an admin approves it again. For custom risks, so does changing a linked control or document.

Editors and viewers see the same Risk acceptance panel without its buttons: the badge, the approver, the expiry date and the rationale, with the note “Only an organisation admin can accept a risk or withdraw an acceptance.” The buttons are hidden rather than shown and refused. An editor can still set Treatment Status to Accepted, but that records an acceptance with no approval (“Accepted · not approved”) until an admin approves it.

  1. Open the risk from the Risk Register.
  2. In the Risk acceptance panel, select Accept risk.
  3. Enter the Rationale: why the organisation accepts this risk.
  4. Set Expires on to a date after today.
  5. Select Record acceptance.

What you’ll see: the risk’s treatment status becomes Accepted, and a badge reading “Approved · expires date” appears in the risk header and in the panel. The panel shows who approved it and when, the expiry date and the rationale.

BadgeMeaning
Approved · expires dateApproved, with more than 30 days to run
Approved · expires in N days, or Approved · expires todayApproved, expiring within 30 days
Acceptance expiredThe expiry date has passed. Renew or withdraw it
Accepted · not approvedTreatment status is Accepted, but no admin has approved it

If someone sets Treatment Status to Accepted directly, the risk is accepted but not approved.

  1. Open the risk. The panel says no admin has approved it.
  2. Select Approve acceptance.
  3. Enter the Rationale and Expires on date.
  4. Select Record approval.

Renew an acceptance before or after it expires.

  1. In the Risk acceptance panel, select Renew acceptance.
  2. Enter a new Rationale and Expires on date. The form starts blank: a renewal is a new decision.
  3. Select Record renewal.

The renewal replaces the previous decision. The audit log keeps the old one.

  1. In the Risk acceptance panel, select Withdraw acceptance.
  2. Confirm.

What you’ll see: the badge disappears and the risk’s treatment status returns to Analysed, ready for a new treatment decision.

What was approved must still be what is recorded. While an approval is in force:

  • Changing a score. Changing any likelihood or impact score, inherent or residual, withdraws the approval. You are asked to confirm first. The risk stays Accepted, shown as “Accepted · not approved”, until an admin approves it again.
  • Changing a custom risk’s links. Adding or removing a linked control, or changing a link’s supporting document, withdraws the approval. You are asked to confirm first.
  • Changing the treatment status. If an admin moves the status away from Accepted, the acceptance is withdrawn. If an editor tries, the status stays Accepted and their other changes are saved. Either way you are asked to confirm first.

When the expiry date passes, the badge changes to “Acceptance expired”. Where scheduled notifications are enabled, the approver and the risk owner are notified; if neither is still a member, the organisation’s admins are notified instead. Opening the notification takes you to the risk. Renew or withdraw the acceptance.

Message (or symptom)What to do
No Accept risk buttonYou are not an organisation admin. Ask an admin to record the decision
Record acceptance stays disabledEnter a rationale and an expiry date after today
“Waiting for this page’s changes to save…”Your other edits to the risk are still saving. Wait a moment
“Accepting a risk needs an expiry date after today”Choose a later date
“Status kept as Accepted: only an admin can withdraw an approved acceptance. Other changes saved.”Ask an admin to withdraw the acceptance

In addition to the SCF risk catalog, you can define custom risks specific to your organisation. Custom risks use R-ORG-N codes (e.g., R-ORG-1, R-ORG-2) and appear alongside SCF risks in the Risk Register under a “Custom” category.

Custom risks support:

  • The same 5x5 likelihood x impact assessment as SCF risks
  • Inherent and residual risk tracking
  • Manual control linking (unlike SCF risks which have pre-defined mappings)

For full details on creating and managing custom risks, see Custom Organisation Risks.

SCF catalog risks include pre-defined mappings between risk codes and control codes. When you view a risk, you’ll see:

  • Recommended Controls — SCF controls that address this risk
  • Control Status — Whether each control is implemented in your organisation

Custom organisation risks support manual control linking — you can search for and attach relevant SCF controls to demonstrate how your organisation addresses these risks.

Click any linked control to navigate directly to that control in the Control Scoping view. This helps you:

  • Verify the control is in scope
  • Check implementation status
  • View evidence attached to the control
  • Click any cell to filter the view to risks in that cell
  • Clear the filter by clicking outside the matrix
  • Search — Filter by risk code or name
  • Filter by Level — Show only Critical, High, Medium, or Low risks
  • Filter by Status — Show only risks in a specific treatment status
  • Sort — Order by risk score, name, or last updated

The dashboard header shows:

  • Total risks assessed vs. unassessed
  • Count at each risk level
  • Risks pending treatment
  • Risks accepted

Use the Export button to download:

  • Risk register as CSV
  • Risk matrix as image (for presentations)
  • Be consistent — Use the same criteria across all assessments
  • Document rationale — Add notes explaining your likelihood/impact scores
  • Review regularly — Reassess risks quarterly or when circumstances change
  • Involve stakeholders — Risk owners should participate in assessments

Focus treatment efforts on:

  1. Critical risks — Require immediate attention and escalation
  2. High risks — Should have treatment plans in progress
  3. Medium risks — Monitor and treat as resources allow
  4. Low risks — Accept or monitor with minimal intervention

To show auditors the value of your controls:

  1. Document inherent risk before control implementation
  2. Implement and evidence the control
  3. Reassess residual risk showing reduction
  4. The delta demonstrates control effectiveness

If a risk doesn’t show on the matrix:

  • Ensure both likelihood and impact are set (risks without scores appear as “Unassessed”)
  • Check you’re viewing the correct matrix type (Inherent vs. Residual)

Risk-control mappings come from the SCF catalog. If expected controls don’t appear:

  • Verify the control exists in your scoped controls
  • Check the SCF catalog mapping is correct

The risk level calculates automatically from Likelihood × Impact. If it’s not updating:

  • Ensure both values are saved
  • Refresh the page if needed