HMOwatch
BlogContactFAQHow it worksUse cases
Join the waitlist
HMOwatchJoin the waitlist
HMOwatch
HomeBlogContactFAQHow it worksUse cases
Join the waitlist
HMOwatch
BlogContactFAQHow it worksUse cases
TermsPrivacyData Processing

© 2026 HMOwatch

[ HOW IT WORKS ]

400+ councils. One live feed. Zero gaps.

UK HMO licensing is scattered across hundreds of council websites, each with its own format, schedule, and quirks. HMOwatch runs automated scrapers against every one of them — continuously — and turns that raw fragmentation into a single, structured alert stream.

  1. STEP 01 — DISCOVER

    Every local authority register, mapped

    HMOwatch identifies and catalogues the HMO register published by each UK local authority — the licensing lists, selective licensing zones, and mandatory HMO registers. No council is skipped. No register is assumed static.

  2. STEP 02 — SCRAPE

    Continuous, automated data collection

    Automated bots visit every discovered register on a rolling schedule, pulling down the latest landlord and property data. When a council updates its list — a new licence issued, a property added, a landlord removed — the bot captures it.

  3. STEP 03 — NORMALISE

    Fragmented formats become structured data

    Every council publishes in its own format — PDFs, HTML tables, CSV exports, bespoke search portals. The pipeline normalises all of it into a consistent schema: property address, licence type, landlord details, licence status, and effective dates.

  4. STEP 04 — ALERT

    Changes surface as real-time alerts in your dashboard

    The moment a change is detected — a property you track gains a licence, loses one, or appears on a register for the first time — HMOwatch raises an alert. Your dashboard surfaces it instantly, so you act on the right information before it becomes a compliance failure.

console
0.1sScanning gov.uk council index...
0.4sRegister endpoints resolved: 427
0.8sCouncils queued for initial crawl
0.0sbot:crawl Birmingham CC HMO register
0.3s3 new records detected
0.6s1 record removed
0.9sChanges staged for processing
0.2sparse:pdf Manchester licensing export
0.5sMapped 61 fields to unified schema
0.8sRecords committed to central register
0.1salert:trigger LICENCE_CHANGE / prop:SW1A1AA
0.4sAlert routed to team dashboard
0.7sStatus: ACTIVE — awaiting review
[ CHANGES / LIVE ]

Every register change, captured and dated

The Changes view gives you a chronological record of every addition, removal, and modification across all monitored councils. Filter by council, by date range, or by property — know exactly what shifted and when.

  • Additions and removals tracked separately

  • Timestamped to the scrape cycle

  • Filterable by council or property address

HMOwatch Changes dashboard — chronological list of register changes
SCRAPER:BOTCrawl complete — Leeds City Council HMO registerjust now
PARSER:PDFNormalised 44 records from Manchester export1m ago
ALERT:ENGINELicence change detected — Bristol prop ref BR-00413m ago
SCRAPER:BOTNew register endpoint resolved — South Oxfordshire DC7m ago
PARSER:HTMLSchema mapped — Birmingham selective licensing table12m ago
ALERT:ENGINEProperty added to mandatory HMO register — Sheffield18m ago
SCRAPER:BOTCrawl scheduled — 427 councils in rolling queueongoing
SCRAPER:BOTCrawl complete — Leeds City Council HMO registerjust now
PARSER:PDFNormalised 44 records from Manchester export1m ago
ALERT:ENGINELicence change detected — Bristol prop ref BR-00413m ago
SCRAPER:BOTNew register endpoint resolved — South Oxfordshire DC7m ago
PARSER:HTMLSchema mapped — Birmingham selective licensing table12m ago
ALERT:ENGINEProperty added to mandatory HMO register — Sheffield18m ago
SCRAPER:BOTCrawl scheduled — 427 councils in rolling queueongoing
SCRAPER:BOTCrawl complete — Leeds City Council HMO registerjust now
PARSER:PDFNormalised 44 records from Manchester export1m ago
ALERT:ENGINELicence change detected — Bristol prop ref BR-00413m ago
SCRAPER:BOTNew register endpoint resolved — South Oxfordshire DC7m ago
PARSER:HTMLSchema mapped — Birmingham selective licensing table12m ago
ALERT:ENGINEProperty added to mandatory HMO register — Sheffield18m ago
SCRAPER:BOTCrawl scheduled — 427 councils in rolling queueongoing
SCRAPER:BOTCrawl complete — Leeds City Council HMO registerjust now
PARSER:PDFNormalised 44 records from Manchester export1m ago
ALERT:ENGINELicence change detected — Bristol prop ref BR-00413m ago
SCRAPER:BOTNew register endpoint resolved — South Oxfordshire DC7m ago
PARSER:HTMLSchema mapped — Birmingham selective licensing table12m ago
ALERT:ENGINEProperty added to mandatory HMO register — Sheffield18m ago
SCRAPER:BOTCrawl scheduled — 427 councils in rolling queueongoing
HMOwatch Alerts dashboard — live compliance alerts panel
[ ALERTS / ACTIVE ]

Alerts that tell you exactly what to act on

When a scrape cycle detects a meaningful change — a licence expiry, a new listing, a property no longer appearing on a register — HMOwatch surfaces a structured alert. Not raw data dumps. Actionable signals with context: what changed, which council, which property.

  • Alerts tied to specific properties and councils

  • Status tracking from raised to resolved

  • Team-visible — everyone sees the same picture

[ COUNCILS / INDEX ]

See every council we monitor, live

The Councils view gives you full visibility into which local authorities are in scope, the status of their last scrape, and any known data anomalies. You are never guessing whether a council has been checked recently.

  • All 400+ local authority sources in one index

  • Last-crawled timestamp per council

  • Source health status visible at a glance

HMOwatch Councils dashboard — index of all monitored local authorities
[ DASHBOARD / OVERVIEW ]

All of it, in one view

The main dashboard pulls together your properties, active alerts, recent council changes, and scraper activity. When you log in, you see the current compliance picture — not a report from yesterday.

HMOwatch main dashboard — compliance overview

Common questions about the process

Right now, HMOwatch identifies local authority HMO registers across the country, aggregates that data into one place, and keeps it continuously updated. Instead of manually hunting across dozens of council websites, you get a single, living view of licensed HMO landlords and properties in the areas that matter to you.
The data comes directly from official local authority HMO registers — the same public records councils are legally required to maintain. HMOwatch doesn't generate or infer this information; it pulls from the source and keeps it current as councils update their registers.
We're not publishing a fixed number here because coverage expands as new registers are identified and integrated. The scope is designed to be as comprehensive as possible across England and Wales. For specifics on your target area, details are available on request.
The scraper runs on a continuous basis, so the data reflects council registers as they change rather than sitting as a one-time snapshot. That said, the freshness of any given record depends partly on how frequently the relevant council updates its own register — something outside our control.
HMOwatch has one feature shipped: the HMO Data Scraper. Additional capabilities are in development. If you want to understand the roadmap or discuss whether the current feature serves your specific use case, the honest answer is to get in touch directly.
Anyone who needs to know who the licensed HMO landlords and properties are in a given area — whether that's investors scoping a market, compliance professionals tracking licensing, or businesses prospecting within the HMO sector. If you regularly find yourself cross-referencing council websites to build that picture, HMOwatch replaces that process.
[ EARLY ACCESS ]

The register is live. Get on it.

HMOwatch is running. The scrapers are active, the registers are being monitored, and alerts are firing. Join the waitlist and be among the first letting agents and landlords to put this data to work.

Questions? Email us at sf-core-org-support-hmowatch@saas-factory.ai