HAILIE AI Development Sprint
Complaints, Housing Ombudsman Service determinations, and open sector learning: proof that modern AI tools can dismantle years of data friction in hours.
Executive Summary
The Housing Ombudsman Service (HOS) publishes some of the most objective evidence there is on how social landlords perform. Each of its determinations is an independent ruling on how a landlord treated a resident, and it has issued more than 16,000 over the past five years.
Complaint outcomes are only one lens on performance, alongside measures such as tenant satisfaction, but they are among the hardest for a landlord to present in a flattering light. The difficulty is not the data itself, it is access to it. The evidence sits across three disconnected forms — summary statistics, an in-year report for each landlord, and more than 16,000 individual determination PDFs — and none of them, on its own, allows a fair, like-for-like comparison or shows how a landlord is changing over time.
In a single-day AI Development Sprint, a small team of AI enthusiasts built a pipeline to extract, clean and consolidate this data, enriched it with landlord size, region and Tenant Satisfaction Measures (TSMs), and normalised it so that landlords of very different scales can be compared fairly. The result, for the first time, is a five-year, like-for-like view of complaint performance across the sector, and proof that modern AI tools can dismantle years of data friction in hours.
What was the goal?
The primary objective of the sprint was to build a system that automatically gathers, cleans and categorises the Ombudsman's data into a single database that can be enriched and analysed. There were two phases:
Phase 1: Database Construction (Completed in this Sprint)
Build an integrated determination database by developing an extraction pipeline to ingest more than 16,000 siloed PDF determinations. The same pipeline then went landlord to landlord, extracting the Ombudsman's individual performance report for each provider to capture their official current-year figures. The combined data was enriched with landlord identifiers to create a normalised, relational database.
Phase 2: The HAILIE Interactive Dashboard (Next Step)
With a robust, validated database in place, Phase 2 will deploy an interactive dashboard that lets users cross-reference variables to uncover bespoke insights. Because the data architecture is now finalised, building the interface, visualisations and filters is fully unblocked.
The Data: Three views of the sector
The sprint drew on the three forms in which the Ombudsman publishes its complaints data. Each is valuable, and each is incomplete on its own. Bringing them together is what makes fair, longitudinal comparison possible, and the sprint captured all three.
| Source | Strengths | Weaknesses |
|---|---|---|
| 1. Annual complaints review (sector summary) |
Authoritative sector-wide totals and official definitions; the published benchmark. | Aggregate only; a single year at a time; no landlord-level or size-normalised detail. |
| 2. In-year individual landlord reports | Official current-year figures for each landlord: maladministration rate, findings, homes, compensation and category breakdown. | One year only (2024-25); published only for landlords with five or more findings; issued as separate PDFs. |
| 3. The 16,000 individual determinations (five years) |
Decision-level and multi-year, so it supports trends and fair normalisation to stock size. | Roughly half of all determinations reach publication; unstructured PDFs requiring AI extraction and cleaning. |
The first two sources give an authoritative but static picture of the present. The third, once extracted and structured, is what unlocks the trends and the like-for-like comparisons that follow.
What did we do?
The sprint ran as two parallel workstreams, governed by a shared data ontology.
1. Data Engineering
- Built a custom data ontology: a set of guidelines that let an AI model categorise determinations without relying on rigid text formatting.
- Taught language models to read the semantic intent behind the Ombudsman's wording, so the system could categorise determinations and their severity accurately.
- Created an ethical extraction pipeline to move data from the HOS website into our own database, then structured and cleansed the PDF text.
- Captured, for every determination: landlord name, landlord type, case ID, decision date, determinations and findings.
- Captured individual landlord reports: adding official current-year figures (maladministration rate, stock size, compensation and category detail) to validate and complement the extracted determinations.
2. Analytics and Quality Assurance
- Validation: benchmarked the extracted data against the HOS 2024-25 Annual Report. Where summary statistics could not be reproduced, we investigated the Annual Report's own parameters and exclusions.
- Enrichment: appended external landlord metadata, adding organisational size (stock volume), regional data and Tenant Satisfaction Measures (TSMs).
- Normalisation: to compare providers of very different scales fairly, we expressed volumes as adverse findings per 1,000 homes. Adverse findings are defined as determinations of service failure, maladministration or severe maladministration.
- Analytics: formulated hypotheses and designed the visualisations that follow, which will feed into the dashboard.
What were the challenges?
The sprint met several challenges. Each became a learning opportunity, and getting the database right matters because everything the dashboard will do depends on it.
Pre-Extraction Challenges
| Challenge | Description | Solution / Next Step |
|---|---|---|
| Ethical data acquisition | The HOS website is designed for retrieving individual cases, so permissions and licensing for bulk access were unclear. | Proactively sought clarification from HOS on legal and ethical compliance (a response is awaited, and we will publish in accordance with it). |
| Rate limiting and server respect | Processing 16,000+ PDFs at once risked overwhelming the HOS server and triggering blocks. | Engineered strict rate-limiting and throttled download speeds to preserve the site's performance for public users. |
Post-Extraction Challenges
| Challenge | Description | Solution / Next Step |
|---|---|---|
| Discrepancies with official aggregates | Extracted finding counts differed from the HOS 2024-25 Annual Report summary (about a 50% difference). | Reconciled the data and submitted a Freedom of Information request to understand the Ombudsman's exclusion parameters. |
| Inconsistent formats | Phrasing varied widely across five years of determinations, complicating categorisation. | Iteratively improved the extraction rules and the ontology to build a more robust model. |
| Integrating HOS and TSM datasets | Landlord identifiers did not match cleanly between datasets, and the HOS data spans a wider range of providers (for-profit, local authority, ALMO and TMO). | Used AI assistance to resolve the mapping and align the datasets precisely. |
| The complaint-handling skew | Conflating the original service failure with the landlord's handling of the complaint distorted trends. | Tightened the text classification to separate the cause of a complaint from its handling. |
What were the findings?
The consolidated database does two things the published record cannot. It lets us compare landlords of very different sizes on a fair basis, and it lets us see how performance has changed across five years. We begin with the current picture, then turn to the trends the data unlocks.
Two views of the same year: rate versus intensity
The Ombudsman's headline measure is the maladministration rate, the proportion of findings upheld. On that measure the regions of England look much alike, ranging only from 65% to 73%. But normalise adverse findings to the size of a landlord's stock and a sharp divide appears: London landlords record 5.9 adverse findings per 1,000 homes, close to five times the North's 1.2. The rate conceals what the intensity reveals. This distinction, between how often a landlord is found at fault and how much maladministration is reported and escalated to HOS, frames everything that follows.
Maladministration Rate (%)
Adverse Findings per 1,000 Homes
The trend behind the headline: a steep rise, now easing
Across the five years the sector's maladministration rate climbed from the mid-40s to around 70%, as complaint volumes grew and residents became more aware of their right to redress, before easing to about 62% as the statutory Complaint Handling Code embedded through 2024 and 2025. This recent drop in the maladministration rate may reflect a mixture of shifting regulatory definitions such as internal thresholds or legal language adjustments, alongside actual operational improvements by landlords.
Up until this point, individual landlords took very different routes: Peabody's rate more than doubled, London & Quadrant sat above the sector line throughout, Notting Hill Genesis began below the average before crossing above it and Clarion sat in the middle of the pack before significantly lowering their rates. A single year's figure cannot tell a board whether its landlord is improving or deteriorating. The trend can, and this is the central capability the sprint unlocked.
The London gap is widening
The regional divide is not a fixed feature of geography; it is growing. In 2020-21 every region sat clustered near the bottom of the scale. Since then London has pulled steadily away, reaching about 4.2 adverse findings per 1,000 homes while the North has stayed near 0.8, so the gap has widened from roughly three-fold to five-fold. Two checks give us confidence: the finding aligns with the Ombudsman's own published analysis, which records London as having the highest volume of complaints per property of any region, and it holds even after the three largest London landlords are removed, so it reflects a general regional pressure rather than a few providers.
The changing face of failure: damp and mould
What drives maladministration is shifting. Damp and mould's share of all adverse findings roughly tripled over the period, from around 5% to 14%, taking ‘property condition’ as a whole past a third of all adverse findings. The rise tracks the heightened attention that followed the Awaab Ishak inquest and anticipates the phased introduction of Awaab's Law. Complaint handling itself remains the single largest category throughout, a reminder that how a landlord responds to a complaint can matter as much as the fault that prompted it.
The Scale Myth: bigger is not worse
There is no linear relationship between a landlord's size and its rate of adverse findings. The largest providers are not systematically worse per home than smaller ones; scale, in itself, neither protects nor condemns. The highest-intensity outliers are small and mid-sized landlords, but almost all of them are in London (shown highlighted), so what first looks like a size effect is largely the same geography effect seen above. The practical lesson is that landlords should be benchmarked against genuine peers of similar size and region, not against the sector as a whole.
Perception and reality align: satisfaction predicts adverse findings
We had expected that self-reported satisfaction and objective Ombudsman findings might diverge. The data shows the opposite. Landlords whose tenants report lower overall satisfaction (the TP01 measure) record markedly higher adverse-findings intensity, a strong negative correlation of r = -0.62. Tenant Satisfaction Measures, far from being disconnected from regulatory outcomes, are among their better predictors. This strengthens the case for reading satisfaction data and complaints data together, exactly the kind of cross-referencing the enriched database is built to support.
The analysis draws on the roughly 16,000 published determinations gathered in the sprint. Because coverage is broadly consistent across landlords, regions and years, comparisons of rates, shares and trends are reliable even though the absolute counts are lower than the Ombudsman's internal totals (the subject of our ongoing FOI request). The widening regional gap is expressed as a ratio between regions, which is robust to the sector-wide growth in the Ombudsman's caseload. Regional labels follow each landlord's predominant region, so “London” denotes landlords whose stock is mainly in London rather than the location of each complaint.
What were the “AI wins”?
Automation versus the human alternative
A human analyst would need six to twelve months to extract and cross-reference thousands of PDFs by hand. AI reduced this to overnight automated extraction and a single day of database construction.
Intent-based classification
The language models were tuned to read narratives like a human investigator, using semantic intent rather than fixed wording. This let the system categorise determinations and their severity accurately despite inconsistent phrasing across five years of reports.
A mid-sprint pivot
The team spotted the complaint-handling skew mid-sprint and rewrote the extraction and classification logic on the fly, a good demonstration of how quickly an AI-assisted workflow can adapt.
What are the next steps?
Complete the FOI request
Establish exactly which cases the Ombudsman excludes from its published summaries. Understanding why roughly half of identifiable determinations are omitted is important both for sector-wide data integrity and for validating our database.
Refine the data architecture
Adjust the pipeline for the Ombudsman's non-publication thresholds (for example, where a very small landlord's cases risk identifying a resident), so these do not systematically skew the data.
Deploy the HAILIE dashboard
Build and launch the interactive tool so providers, boards and residents can cross-reference the data. Indicative features include peer benchmarking against landlords of similar size and region, five-year trend tracking for any landlord or region, and risk mapping of where adverse and severe findings concentrate.
Sources and Licence
- Housing Ombudsman Service determinations and annual reviews (official data sources).
- Regulator of Social Housing TSM dataset 2024-25.
The code and methodology developed in this sprint are open artefacts. Content is available under CC BY-SA 4.0.