Regulatory data you can trace back to its source.
Collecting regulatory content is relatively easy. Maintaining an accurate, reviewable regulatory dataset over time is the difficult part — doing it repeatedly, consistently and accountably, with a record of who approved what, from which source, and when it took effect.
From official source to published record
Discover, collect, normalise, review, version, publish, monitor. Each stage produces something durable: a registry entry, a normalised record, a review decision, a version.
- 01
Discover official sources
National legislation and guidance, devolved frameworks, and the specific local authority pages, registers and documents that create or modify rental obligations are mapped into a maintained source registry.
- 02
Collect regulatory content
Registered sources are monitored — web pages, structured data where it exists, and published documents. Collection captures the material and the context needed to cite it later.
- 03
Normalise into a consistent structure
Source material becomes consistent records: jurisdiction, authority, trigger, obligation, dates and references. Different councils expressing the same idea differently end up comparable.
- 04
Human review and approval
Substantive additions and changes are reviewed before publication. A reviewer confirms interpretation, checks the cited source and sets the review state.
- 05
Version and retain history
Approved records are versioned and prior versions are retained, so information given last quarter can still be traced back to the record and source it came from.
- 06
Publish to the Platform and API
Current approved records reach the Licenseye Platform and the Licenseye API together, with provenance and dates attached.
- 07
Monitor and revisit
Mapped authorities and sources are revisited on an appropriate cadence, and detected changes re-enter the review loop rather than silently overwriting published data.
The same method, four different jobs done
One reviewed record set answers a question at the desk, in a legal file, across a portfolio, or inside another product.
A letting or managing agent
Checks a property and sees the applicable requirements, the responsible authority and the source behind each one.
A property legal team
Reviews rental regulatory context as part of due diligence, with authority, source and effective dates on record.
A portfolio compliance team
Monitors requirements across multiple properties and sees where local variation or a change affects the holding.
A software platform
Calls the Licenseye API and surfaces the same regulatory intelligence inside its own product workflows.
Why human review matters
Automation accelerates discovery and extraction. It is not the last word on what a professional or a product tells an agent, operator or landlord. Published regulatory information is reviewed, versioned and attributable — and it remains information, not legal advice.
Automation for reach
Monitoring and extraction cover far more sources, far more often, than manual research can.
Review for judgement
Interpretation, edge cases and ambiguous wording are decided by a person, and that decision is recorded.
Controlled publishing
Nothing substantive reaches the Platform or the API without passing an approval step.
No silent drift
Detected changes create candidates for review rather than overwriting live records.
See the method applied to your properties or your product.
Licenseye gives property professionals source-backed regulatory information, and gives software platforms the structured data to deliver the same answers inside their own products.