Why your incident clock starts when someone decides to speak

November 11, 2026
Why your incident clock starts when someone decides to speak
New UK rules will put a clock on reporting operational incidents, including those that begin at a supplier. But the clock can only start once the right people know, and that depends on someone acting on what they see.

On 22 March 2023, a malicious file was unintentionally downloaded onto an employee's device at Capita. Within ten minutes, a high-priority security alert had been raised.

It was 58 hours before the device was quarantined. The target response time was one hour. That gave the attacker time to exploit Capita's systems. On 29 and 30 March, nearly a terabyte of data was taken. On 31 March, ransomware was deployed.

The personal data of 6.6 million people was affected. In October 2025, the Information Commissioner's Office fined Capita £14 million.

Capita was also a supplier. Its pensions arm processes data for more than 600 pension scheme organisations, and the ICO says 325 organisations were affected. For each of them, a serious incident began inside someone else's business.

The Pensions Regulator's lesson for trustees was blunt: "If trustees outsource administration, they are still responsible for ensuring scheme obligations towards members are met".

The alert worked. The response depended on people


It's tempting to read this as a technology failure. The ICO did find technical gaps. But several of its findings are about people and decisions.

Capita's security operations centre was understaffed. In at least six months before the incident, the ICO found, it fell well below the target response times for security alerts. Weaknesses in the control of administrative IT accounts had been "flagged as a vulnerability on at least three separate occasions but were not remedied".

Those findings point to decisions about resourcing and follow-through, taken in the months before the incident. We can't know what each person was thinking or doing in those 58 hours, and we shouldn't guess. But there’s a lesson to consider. The alert worked. What happened next depended on people: whether the right people were involved from the start, whether there were enough skilled people available to act, and whether the decision makers had an effective and timely understanding of the problem.

Fear of blame slows everything down


Capacity is one half of a response. The other is whether people feel able to act. We are not suggesting fear of blame played a part at Capita, but it is a familiar pattern elsewhere.

Liz Oakes, of the Bank of England's Financial Policy Committee, described it in a May 2026 speech. She said she had too often seen very capable people "not take the appropriate action for fear of blame". 

Her remedy was about delegation. Firms that give people responsibility so they can do their jobs, she argued, should not then complain when those people act. That is a strong risk culture in practice: people trusted to act early, and backed when they do.

The same is true inside your own firm. A relationship manager who hears of trouble at a supplier has to decide whether to escalate it, and whether being wrong will cost them.

Third party risk adds a second organisation to the problem. Picture an engineer at a supplier who spots trouble at 2am. They have to decide whether to wake a client, and their account manager may be worried about the contract. Every hour of hesitation on their side is an hour your firm cannot afford to lose. Depending on how important and time critical the service is, you also have to consider who on your team would receive the call at 2am. 

The new rules put a clock on what follows


The new FCA and PRA rules apply from 18 March 2027. Firms they cover must report operational incidents that meet set thresholds. The first report is due as soon as practicable. The FCA expects it within 24 hours of a firm deciding that a threshold has been met. Payment service providers keep their existing four-hour deadline.

For PRA-regulated firms, the PRA expects the Chief Operations senior manager, the SMF24, to hold overall responsibility for incident reporting. It does not expect that person to approve each report. So the speed of a first report is likely to rest on other, more junior, people in the firm, and on the authority they have been given.

Suppliers are already part of the picture. In 2025, 27% of incidents reported to the FCA were attributed to a third party issue, according to a joint FCA and PRA blog. Of those, 37% were cyber-related.

The regulators now expect the biggest providers to behave well under pressure too. In July 2026, four cloud providers were designated as critical third parties. The regulators said such providers must "maintain open, timely communication with regulators and the firms that rely on them, particularly during major incidents".

A rule can require a provider to communicate. In our view, culture matters as much as any rule. It decides whether the first call comes early, with half the facts and owner and a plan, or too late, with many more facts but the issue still not under control.

The relationship has to exist before the incident


None of this can be fixed during an incident. Most of it is cheap to fix beforehand.

  • Name people, not mailboxes: for each key supplier, know who will call you and who you will call. Swap numbers before anything goes wrong.

  • Check the contract: do notification clauses or service credits punish the supplier that tells you first?

  • Measure the time to tell: after each incident or near miss, ask how long the supplier's first warning took to reach someone who could act.

  • Welcome early, incomplete news: thank the supplier that calls early with half the facts. If early warnings bring blame, you'll get fewer of them.

  • Back your own people: say in writing who can escalate a supplier concern without waiting for proof, and support them when they do.

  • Bring in the specialists: specialists such as lawyers and compliance officers may be necessary for certain high impact issues, and they need to be part of the initial discussions if they are to be effective.  It’s important the response team understand when and where they need this support from the outset. 


The rules measure how fast you tell the regulator. Your culture, and your supplier's, decides how fast anyone tells you and how timely and effective your response is.

Dr Jon Baker is a Principal Consultant at Contexis. This is one of four Contexis articles on culture in third party risk. Our Risk Culture Index looks at how risk is understood, owned and acted on, and is built on the Pan-Industry Risk Culture model. Find out more about our risk and control work here. 

 
Related articles
Read
Humanising business – the new organisational imperative
22.05.2023
The role of business in society has changed. Profit alone is no longer enough. John Rosling explores why human-centred, purpose-led organisations build trust, wellbeing and better performance. But what does humanising business actually mean?
Read article
Read
How can you manage corporate risk through culture?
10.09.2024
Managing corporate risk is usually about processes and oversight to predict and avoid human error. But we all know it’s people that cause problems, and who will save you from them if they care enough. As Warren Buffett says “culture, more than rule books determine...
Read article
Read
Face the future with a lot more humility
05.12.2023
Purpose leads to higher engagement and profitability. But you cannot show whether your purpose is working if you cannot measure it and ESG does not measure purpose. We want to prove it's happening and the Contexis Index gives us a measure of where we go next.
Read article