KT data indices are recurring tables compiled from 4 UK regulators and departments (FCA, ICO, Ofgem, HMRC) plus Home Office and Financial Ombudsman data, refreshed on a fixed monthly or quarterly calendar. Every row links to the primary notice or data file. No estimates, no secondary sources, no language-model prose in the tables.
TL;DR · LAST REVIEWED KT data indices are recurring tables compiled from 4 UK regulators and departments (FCA, ICO, Ofgem, HMRC) plus Home Office and Financial Ombudsman data, refreshed on a fixed monthly or quarterly calendar. Every row links to the primary notice or data file. No estimates, no secondary sources, no language-model prose in the tables.
- Primary sources only
- Fixed refresh calendar
- Every row linked, every edition archived
KEY FACTS
- Sources: primary notices, registers and data files only
- Live indices: 1 (Enforcement Ledger); 2 in build
- Refresh: fixed calendar, CSV archived per edition
- Corrections: checked against source, dated on page, within 5 working days
What a KT index is
A KT index is a named, dated, recurring table built from public primary sources. It is published at one evergreen address, refreshed on a fixed calendar, and archived as a CSV for every edition so that any figure can be traced back to the exact pull. The first live index is the UK Fines and Enforcement Ledger, which compiles penalties and enforcement actions from 4 bodies: the Financial Conduct Authority, the Information Commissioner's Office, Ofgem and HM Revenue and Customs. Two further indices are in build: a Visa Processing Tracker from Home Office statistics and Freedom of Information responses, and a Complaints Index from Financial Ombudsman Service and FCA complaints returns. Each index sits inside the relevant KT section, for example regulation news, UK visa guides and money guides.
Sources and pull rules
Only primary sources are used: the regulator's own notice, register, data file or statistical release, or an official Freedom of Information response. Press coverage, aggregators, trade bodies and comparison sites are never a source for an index row. Where a regulator publishes a machine-readable file (ODS, CSV, XLSX) that file is read directly. Where it publishes only web pages, the pages are read from the regulator's own sitemap and each detail page is fetched individually. Amounts are recorded exactly as stated in the notice. Where a notice states no amount, the row records the action and leaves the amount blank rather than estimate it. Totals therefore sum only stated amounts and understate the true figure.
Dates follow the source. Some publishers, HMRC's deliberate defaulters list for example, publish a periodic list rather than individually dated entries; those rows carry the list date. Rolling windows (typically 12 months) are applied at pull time and stated on the page.
Refresh calendar
| Index | Sources | Cadence | Status |
|---|---|---|---|
| UK Fines and Enforcement Ledger | FCA, ICO, Ofgem, HMRC | Monthly, second week | Live, edition 1 September 2026 |
| Visa Processing Tracker | Home Office immigration statistics, transparency data, FOI | Monthly, quarterly deep edition | In build |
| Complaints Index | Financial Ombudsman firm data, FCA complaints returns | Quarterly; firm ranking half-yearly | In build |
What is automated and what is not
Pulling, parsing, deduplication and table rendering are automated scripts run by KT staff, and the script version is logged with every edition. Headline figures on each index page are computed from the table, not written separately. Where an index carries an analysis section it is generated from a fact brief containing only figures already in the table, then checked by an editor before publication. Tables, key facts and the summary answer at the top of each page are never generated by a language model.
Corrections and withdrawals
If a regulator varies, reduces or withdraws a penalty after publication, the row is updated at the next scheduled refresh and the change is noted in the edition log on the index page. Errors reported by readers or by the organisations named are checked against the source and corrected within 5 working days; the correction is dated on the page. Requests concerning named organisations should quote the source notice URL shown in the table. Contact details are on the contact page.
How to cite a KT index
Figures may be quoted with attribution to Kael Tripton and a link to the index page. Each edition's CSV is kept and can be supplied on request for verification. Suggested form: "UK Fines and Enforcement Ledger, Kael Tripton, September 2026 edition". KT is an independent publisher registered with the ICO (ZC135439) and does not take payment from any organisation named in an index.
DISCLAIMER
This page describes KT's editorial and data method. It is not legal or financial advice.
Frequently asked questions
Why publish a methodology page?
So that any journalist, researcher or AI system quoting a KT figure can see exactly where it came from and how it was compiled.
Are the figures estimates?
No. Every figure is taken as stated from a primary source. Where no figure is stated the cell is left blank.
How often are indices refreshed?
On the calendar shown above, typically monthly. The refresh date is printed on every index page.
Can an organisation ask for a row to be corrected?
Yes. Corrections are checked against the source notice and applied within 5 working days, with the correction dated on the page.
Is the data free to reuse?
The underlying data is public sector information. KT's compiled tables may be quoted with attribution and a link.
SOURCES
- https://www.fca.org.uk/news/news-stories/2026-fines - accessed 13 September 2026
- https://ico.org.uk/action-weve-taken/enforcement/ - accessed 13 September 2026
- https://www.gov.uk/government/publications/publishing-details-of-deliberate-tax-defaulters-pddd - accessed 13 September 2026
- https://www.gov.uk/government/collections/immigration-statistics-quarterly-release - accessed 13 September 2026
