Resources · Template
Risk register template: fields, scoring and example
What is a risk register?
A risk register is the record of identified risks and what is being done about each. The template matters because consistency matters: ISO 27001 asks that repeated assessments produce consistent, valid and comparable results.
Define your likelihood and impact scales before you start. The example uses a 1 to 5 scale for each and multiplies them; use your own documented method.
The risk, its cause and consequence, and who owns it.
Likelihood and impact, the treatment option, and the actions.
The residual score, who accepted it, and when it will be reviewed.
Risk register template
Fifteen fields. The example follows one risk.
| Field | Example | What to write |
|---|---|---|
| Risk reference | R-011 | A unique number |
| Risk description | Former staff retain access to systems after leaving | What could happen |
| Asset or process | Finance system; HR leaver process | What is affected |
| Cause | Leaver notices reach IT by email and are sometimes late | Why it could happen |
| Consequence | Unauthorised access to financial data | What it would lead to |
| Risk owner | Chief financial officer | Who is accountable and accepts the residual risk |
| Likelihood (inherent) | 4 of 5 | Before treatment, on your scale |
| Impact (inherent) | 4 of 5 | Before treatment, on your scale |
| Inherent score | 16, high | By your documented method |
| Treatment option | Reduce | Reduce, avoid, share or accept |
| Treatment actions | Link account removal to the HR leaver process (controls A.5.18, A.6.5) | What will be done, and the controls involved |
| Action owner and due date | IT operations lead; 30 Nov 2026 | One person and one date |
| Residual score | Likelihood 2, impact 4: 8, medium | After treatment |
| Acceptance | Accepted by the CFO, 5 Dec 2026 | Who accepted the residual risk, and when |
| Next review | June 2027, or on change | Planned date |
The example values are illustrative. Copying pastes the table as rows and columns into a spreadsheet or document.
How do you fill it in?
- Set the method first
Scales, the scoring rule and the level that needs treatment.
- Describe each risk specifically
Asset, cause and consequence.
- Score before treatment
Name the risk owner at the same time.
- Choose the treatment and the controls
Link the actions to your Statement of Applicability.
- Score again and get acceptance
The risk owner accepts what remains.
- Review on a schedule and on change
Record the date of each review.
What goes wrong most often?
Scales without definitions
'Likely' means different things to different people.
Instead: describe every level.
Residual equals inherent
The scores never change after treatment, or always drop to low.
Instead: re-assess honestly once the control is working.
No acceptance recorded
Nobody has formally accepted the remaining risk.
Instead: record who accepted it and when.
Do you need a template at all?
Risks scored on your own matrix, each with an owner, a treatment and a review date, linked to controls and audits.
Risk register template: common questions
What fields should a risk register have?
A reference, description, asset, cause, consequence, owner, likelihood, impact, score, treatment option and actions, action owner and date, residual score, acceptance and review date.
What are the risk treatment options?
Reduce the risk with controls, avoid it by stopping the activity, share it with another party such as an insurer, or accept it.
Who should own a risk?
Someone with the authority to decide how it is treated and to accept what remains. That is often a business leader, not the security team.
Is this template free?
Yes. It is on this page, with no form to fill in.
Risks scored, treated and reviewed in one register
The record lives with the audit, linked to its controls, findings and report.