Pillar 03 · Automation
A3 Severity Policy
Critical failures stop bad data. Everything else tells someone.
Form Document
What it's for
A check that only reports is a description of a problem after it has happened. A library where every check blocks the load stops the business. Severity decides which is which, so that the few checks protecting investor figures and High-tier AI answers stop data, and the rest alert the right owner without holding up the day.
This policy sets three severity levels, how to assign them, what happens when a Critical check fails, and who may release a blocked load. It applies to every check in the library (A1) and every threshold in a data contract (A2).
What you get
- Three levels Critical, Warning, Info
- Assigning severity Two questions set the level
- When a Critical check fails Six steps
- Releasing a blocked load Overrides are allowed, recorded and rare
How it connects
It sets the severity of every A1 check and every A2 threshold, by the highest S1 tier that reads the data; a released load goes in its override log.
A flavour of the worked example
| Check (A1) | A-05b |
|---|---|
| Dataset | fact_rent_roll |
| Why released | Rent review at Unit 4 settled at 62% above the previous rent; confirmed by asset manager |
| Approved by | Head of Asset Management, Steward lead, Head of Fund Reporting |
| Threshold to change? | No |
A few fields from one record of the toolkit's worked example, with long text shortened.
Next step
Guided build coming next.
Request access
Ask for access to the guided builds, including this kit's when it is ready.