Council Tax Data for HMO Detection: A Practical Guide

Council tax data is one of the most valuable yet underused intelligence sources for identifying unlicensed Houses in Multiple Occupation. Every local authority holds detailed council tax records for every domestic property in its area, including information about liable persons, exemptions, discounts, and property banding. When analysed systematically, this data can reveal properties that are likely to be HMOs but do not hold the required licence. The challenge is not the availability of data but the analysis. Council tax teams and housing enforcement teams often operate in silos, with limited data sharing despite being part of the same organisation. Breaking down these silos is one of the most cost-effective steps a council can take to improve HMO detection.

Several council tax data points serve as indicators that a property may be an HMO: 1. Multiple council tax exemptions or discounts at a single address: Where multiple Class N exemptions (students) apply, the property is likely a student HMO. 2. Frequent changes of liable person: A high turnover of names on the council tax account suggests a shared property with changing occupants rather than a single household. 3. Class W exemptions: These apply to annexes occupied by a dependant relative, but are sometimes incorrectly applied to properties that are actually separate HMO units. 4. Properties in Band D or above with multiple liable persons: Higher-banded properties with evidence of multiple occupants are strong HMO candidates. 5. Properties where the liable person is not the occupant: Where a landlord or agent pays the council tax (common in HMOs to simplify billing), this indicates a managed rental property. 6. Council tax reduction claims from multiple occupants at the same address: This can indicate multiple households sharing a property. None of these indicators is conclusive on its own, but when combined they produce a strong probability score for HMO status.

The real power of council tax data emerges when it is matched against licensing records. The process is straightforward: 1. Extract all properties from the council tax database that show HMO indicators (as described above) 2. Match these against your HMO licensing database by UPRN or address 3. Any property that shows HMO indicators but does not hold a licence is a potential enforcement target This matching exercise should also include selective licensing records (where applicable), EPC data (large properties with multiple EPCs suggest subdivision), and landlord registration data from the PRS Database once it launches in late 2026. The accuracy of this matching depends on data quality. UPRNs are the gold standard for property matching, as address text matching is prone to false negatives due to spelling variations, flat numbering differences, and other inconsistencies. Councils that have not yet standardised their property references to UPRNs should prioritise this work.

Sharing council tax data within the council for enforcement purposes is lawful, but teams should follow proper procedures: The legal basis for data sharing between council tax and housing enforcement is the council's statutory duties under the Housing Act 2004 and the Local Government Finance Act 1992. Processing is necessary for the performance of a task carried out in the public interest (GDPR Article 6(1)(e)). However, councils should have a data sharing agreement or protocol in place between the revenues and housing departments. This should specify what data is shared, how it is stored, who has access, and how long it is retained. The council's Data Protection Officer should review any new data sharing arrangement. In most cases, sharing council tax data for housing enforcement purposes is uncontroversial, but formal documentation protects the council and ensures compliance with data protection principles. Council tax data should not be shared externally (e.g., with other councils or agencies) without a formal data sharing agreement under Section 14 of the Digital Economy Act 2017 or equivalent authority.

Councils that want to move from ad hoc analysis to systematic HMO detection should invest in an automated pipeline: 1. Set up a regular data extract from the council tax system (weekly or monthly) 2. Apply the HMO indicator scoring rules to produce a ranked list of suspected HMOs 3. Match against licensing records to exclude known, licensed HMOs 4. Feed the resulting list into the enforcement team's case management system 5. Prioritise cases by risk score, complaint history, and geographic area This pipeline can be built using existing tools (Excel, SQL databases, or Python scripts) or through purpose-built enforcement platforms. The investment in automation is repaid quickly: a systematic approach identifies more unlicensed HMOs than reactive, complaint-driven enforcement, and the resulting civil penalty income can fund the system. With the PRS Database launching in late 2026, building this infrastructure now positions the council to immediately cross-reference national registration data against local intelligence, multiplying the detection capability.