Skip to main content

TPRM Consulting

Financial Services · part 4

Who can say no?

Assessing and reporting supplier risk is half of governance. The other half is having someone with the authority to stop a supplier, and using it.

Clive Besterwitch, Founder and Director · Part 4 of 5

The third-party risk report is thorough. Every supplier has been assessed, findings are logged, the dashboard is green or amber, and the committee pack goes out on time. A supervisor reads it and asks one question: who can stop a risky supplier from going live, and when did that last happen?

The room goes quiet. Suppliers do go live with open findings, because the onboarding process is designed to move forward. The risk is documented, escalated, discussed and then accepted, usually because the business needs the service by a date.

We see this in many programmes that look busy and well run. Assessments are completed and metrics improve, yet very few findings ever change a decision. That is reporting. Control means the outcome of an assessment can change what happens next.

What the rules expect

DORA puts ICT risk, including third-party risk, on the management body. Article 5(2) makes it responsible for the ICT risk management framework and, in point (h), for approving and periodically reviewing the policy on arrangements with ICT third-party service providers. Article 5(3) asks firms to set up a role to monitor those arrangements, or to name a senior manager responsible for them. Article 28 expects firms to assess risks before entering an arrangement and to be able to end it where the risk can’t be managed.

In the UK, PRA Supervisory Statement SS2/21 expects the board and senior management to own outsourcing and third-party risk, with clear accountability under the Senior Managers and Certification Regime. In both regimes, accepting a risk is a decision someone is accountable for.

Why risk gets accepted by default

In our experience, the pattern has three causes:

  • The process has no stopping point. Onboarding moves to the next stage whatever the assessment found, so open issues travel with the supplier into production.
  • Nobody holds the authority to block. The TPRM team can raise concerns, but the decision sits with the business owner who needs the service.
  • Acceptance is informal. Risks are “noted” in a meeting, with no named approver, no expiry date and no follow-up on the actions that were meant to reduce them.

The result looks controlled on paper. The supplier was assessed, the risk was recorded and the committee was informed, but nothing about the risk changed.

What control looks like

Control doesn’t mean blocking more suppliers. It means each outcome is a real decision, made by the right person, with evidence. A working model has:

  • A defined point in onboarding where a supplier can’t proceed without a decision on open findings.
  • Risk acceptance authority set by risk level, with escalation to senior management for the highest risks.
  • Every acceptance recorded with the approver, the reason, any conditions and a review date.
  • Remediation tracked to closure with the supplier, and overdue actions escalated before they become accepted by default.
  • Reporting that shows decisions as well as activity: how many suppliers were stopped, delayed or approved with conditions, and why.

Where to start

Look at the last ten suppliers approved with open findings. For each one, find who accepted the risk, on what basis, and what has happened to the findings since. If the answers are hard to find, the problem is in the process, and fixing it will do more than another round of assessments.

Our view

A TPRM function shows its value in the decisions it changes. Clear authority to stop or condition a supplier, used and recorded, is what turns assessment into control, and it is what a supervisor will look for.

Sources: EUR-Lex, Regulation (EU) 2022/2554 (DORA), Articles 5 and 28; Bank of England, PRA Supervisory Statement SS2/21, Outsourcing and third party risk management; FCA, Senior Managers and Certification Regime.