- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Chief Risk Officer
- Code
- MGT-05
It keeps the risks of the bank's change programmes current, scores them on the bank's operational risk matrix and decides whether each is treated in the programme or escalated to the operational risk register. Risks that touch customer harm, regulatory breach or financial crime are escalated whatever their score.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the operational risk register: the programme's open risks, linked controls, related incidents and the risk appetite statements..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Chief Risk Officer with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the operational risk register: it updates the programme risks and raises register entries for escalated risks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The operational risk framework: the impact and likelihood matrix, risk appetite statements, the operational risk register, the risk and control self-assessment, and the escalation rules for conduct and regulatory risk.
Reads from
the operational risk register: the programme's open risks, linked controls, related incidents and the risk appetite statements.
Acts in
the operational risk register: it updates the programme risks and raises register entries for escalated risks.
Hands back
A list with one entry per risk, each with risk_id, description, score, type, owner, mitigation, due_date, decision (treat_in_programme, escalate_to_register or close) and reason.
Asks a person when
A risk scores at or above 15, is one of customer harm, regulatory breach, financial crime, data breach, or the programme would hold residual risk above the low appetite.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Score that goes to the risk register | 15 | Impact times likelihood at or above this is escalated to the operational risk register. |
| Score at which a risk may close | 4 | A risk at or below this after mitigation may be closed. |
| Mitigation overdue after (days) | 7 | A mitigation this late is flagged. |
| Programme risk appetite | low | How much residual risk the programme may hold. |
| Risk types always escalated | customer harm, regulatory breach, financial crime, data breach | Comma-separated. These go to the risk register at any score. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score each risk as impact times likelihood; at or above 15 it goes to the operational risk register.
- Any risk of type customer harm, regulatory breach, financial crime, data breach goes to the register and the Chief Risk Officer whatever its score.
- Every risk needs a named owner and a mitigation with a date; one missing either is flagged.
- A mitigation 7 days late is flagged to the owner and the programme manager.
- A risk closes only when its residual score is at or below 4 and within the low appetite.
See the Risk Tracking Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.