Context Visualised home Talk to us
What you get · Controls

Know which controls work, team by team, before the committee asks.

A controls dashboard shows whether the controls behind your risks work. Context Visualised lists every control by the team that runs it, with its last test, its result and whether the next test is overdue. Evidence sits with the control, recorded where the work happens. So the risk team stops chasing, and every team sees its own score.

Talk to us Follow Halden

Halden is a fictitious Lloyd's managing agent. We run it in CoVi Analytics and publish its reports one at a time.

The problem

Every quarter, the risk team emails every team for evidence.

The control library lives in one place. The test results live in another. The evidence lives in someone's inbox. Each quarter the risk team sends the same emails, and each team stops its work to reply. By the time the results reach committee, they are a month old.

The weakest controls often sit where the work is hardest to see: with coverholders, fronting partners and outsourced claims. Lloyd's 2026 Market Oversight Plan puts delegated business at about 45% of the market's premium. That is a lot of control work happening outside your building. The PRA's 2026 priorities letter also expects DA oversight to cover how firms would exit unprofitable arrangements.

What you get today
  • A control library in a spreadsheet
  • Evidence requests by email, every quarter
  • Test results a month old at committee
  • No team-level view of what is weak
What you need
  • Every control with its owner team and last test
  • Evidence recorded where the work happens
  • Overdue tests visible the day they fall due
  • Each team's score, so the weak spots stand out
How we solve it

Every control, by the team that runs it.

This is the controls view of Halden, our fictitious managing agent. Teams are sorted weakest first. Open a team to see its controls, the risks they hold and when each was last tested.

  1. First you see
  2. Then you drill into
  3. Behind it

First you see the whole firm. Total controls, the share operating effectively, how many are not fully effective, and how many tests are overdue.

Halden · Controls · 30 Sep 2026

Are our controls working, and where are they weakest?

  • Controls158Mapped to 79 risks across nine teams
  • Operating effectively84%132 of 158 controls
  • Not fully effective26✕ 2 ineffective · 24 partial
  • Tests overdue29Across all nine teams

ClickTap to explore Click a team to see its controls.

  • Effective
  • Partially effective
  • Ineffective

Team score counts effective controls in full and partly effective ones at half. Strong is 90% and above, needs attention 75 to 89%, weak below 75%.

Halden is fictitious. Source: controls by team, risk register, incident log at 30 Sep 2026

Halden runs 158 controls. 84% operate effectively, 24 are partly effective and 2 are ineffective. 29 tests are overdue across nine teams.

  1. Callout 1: At Halden, claims (62%) and delegated authority (67%) are the weakest teams.Controls by team

  2. Callout 2: The two ineffective controls are coverholder audits and the fronting partner's claims authority agreement.Controls by team

  3. Callout 3: Halden's two ineffective controls hold its only two high risks.Controls by team; Risk register

A weak control is not a second-line statistic. At Halden, the failed coverholder audit let a coverholder write outside its territory for months, and Lloyd's had to be told.

What we think

Controls belong to the people who run them.

  • Score by team, not by framework

    A team can act on its own score. A firm-wide percentage hides where the problem is.

  • Evidence where the work happens

    If evidence is recorded as part of the work, nobody has to chase it at quarter end.

  • A control is only as good as what it holds

    Every control links to the risk it holds. A weak control on a high risk shows first.

In March 2026 the FCA found some firms lacked owners or target dates for remediation actions. Here each action shows its owner and date.

What's in it

What each control carries.

For every control:

  • the team that owns it, and the named owner;
  • the risk it holds, with that risk's residual rating;
  • its status: effective, partly effective or ineffective;
  • its last test date, and whether the next test is overdue;
  • the evidence, linked from where it was recorded;
  • any incident raised against it, and where in the business that control is mapped.

For every team:

  • a score, using the same rule for every team;
  • its controls in order of concern, ineffective first;
  • its overdue tests.

How it works

  1. We load your control library.

    Each control is linked to its owner team and the risks it holds.

  2. Teams record tests and evidence as they work.

    The result and the evidence sit with the control.

  3. The view updates as they do.

    Scores, overdue tests and exceptions are always current for the risk team and the committee.

Questions

Questions risk teams ask

How do you show control effectiveness to a risk committee?

Show it by team, sorted weakest first, with one scoring rule for all. Give each team's score, its ineffective and partly effective controls, and its overdue tests. Then link each weak control to the risk it holds. At Halden, our fictitious managing agent, that puts claims and delegated authority at the top.

How do you stop chasing control evidence every quarter?

Record the evidence where the work already happens, against the control it supports. The risk team then reads it in place, and nobody needs to email for it. The test date and result sit next to the evidence, so overdue tests show the day they fall due, not at quarter end.

Who uses this view

Every team runs controls. Each one sees its own.

Proof

See the controls view working at Halden.

Halden is our fictitious managing agent. Its controls report shows every team's score, and its weakest controls link through to the risks, incidents and processes they touch.

Want to stop the quarterly evidence chase?

Tell us which team's controls are hardest to evidence. We will show you how they would look, using Halden as the starting point.

Talk to us Take the risk reporting check

Built by Context Visualised, in London since 2016, Lloyd's Lab Cohort 2. Founded by Waleed Sarwar, former interim Head of Risk at Liberty Mutual, Markel and Bupa, who worked on Solvency II policy at the Bank of England.

Sources (3)
  • Lloyd's 2026 Market Oversight Plan. Delegated business is "circa 45% of the market's GWP". assets.lloyds.com
  • FCA, "Operational resilience: insights and observations one year on", 27 March 2026. "Some firms lack recorded remediation actions, owners, or target completion dates.". www.fca.org.uk
  • PRA, "Insurance Supervision: 2026 priorities", Dear CEO letter, 15 January 2026. DA oversight should include "how they would exit unprofitable arrangements". www.bankofengland.co.uk