Every limit checked the moment its figure changes, and every breach traced to what caused it.
From board-approved risk appetite down to desk limits, each check reruns when its figure changes, and only the checks a change affects. A breach opens to the trade or price behind it, and shows whether every input was current.
A desk breaches its limit at 14:20 and is back inside by 16:00.
When the control runs on the end-of-day position, the evening report shows no breach, and nobody learns of it. With each check rerun as its figure changes, the afternoon goes like this.
The same afternoon, checked live
- 13:50
An early warning goes to the owning team as the figure nears its limit.
- 14:20
A sharp price move takes the figure over its limit. One alert goes to the team in Teams or its ticketing tool.
- 14:22
The second line opens the breach and sees the price move and the position behind it. You can open one yourself on the live limit board ↗, no sign-in.
- 16:00
The position is reduced and the figure is back within its limit. The breach leaves the board.
The second line and internal audit can see whether a control passed on current data.
- A check is marked stale the moment any input behind it is older than the tolerance set for its source, so a pass on old data no longer looks like a pass.
- Open any figure behind a control and see its full lineage, down to the raw data, and export it as a report for audit.
- Your team sets limits and who is told, for example from Excel. Each limit entered by hand is checked against the person's permissions and carries who entered it and when.
- If you let AI agents enter values, each can enter only what its person may, and its entries are marked "AI agent for" that person.
Basel's market risk standard asks banks with active intraday trading for “reports on intraday limits and respective utilisation and breaches”. Each breach sends one alert, however often its figure is recalculated, and goes where your team chooses.
In the product: Why did this figure change? (1 min 18 s)
Put the limits that breached last quarter on live checks first.
Your own people write the calculation behind each figure, or Calseda calls the engines you already run, in your own environment. Today's report carries on beside the live checks until you rely on them.
Catch the next intraday breach while it is still open
Become a design partner: one set of limits live in about six weeks, for a fixed fee. At the end you keep the framework, licensed to run what you built on one server.
For the second line and audit, on one page: Limits and controls (PDF).