Property-level regulatory answers for professional teams.
Search a rental property, understand which regulatory requirements apply and see the sources behind them — without researching every authority independently.
- Property
- uprn=100023336956
- Jurisdiction
- England
- Authority
- Example Borough Council
- Applies
Additional HMO licence
Trigger: 3+ occupiers forming 2+ households
- Applies
Selective licensing designation
Trigger: Property within designated ward
- Applies
Electrical safety report (EICR)
Trigger: Private rented tenancy
Source: council policy page
Effective from 2025-04-01
Reviewed 2026-02-11 · v4
What the Platform does, in the order you do it
The Platform is being designed around five professional jobs, from a single property assessment through to portfolio-wide change review.
- 01
Assess a property
Start from an address or property reference. Licenseye resolves the jurisdiction and responsible local authority, so you are not deciding which council rules to read before you begin.
- 02
Understand what applies
See the rental regulatory requirements relevant to that property and occupancy, rather than a generic national checklist. Triggers and conditions are shown alongside each requirement.
- 03
Verify the source
Open the authority reference behind any requirement — the page, document or designation the record was derived from, with its effective dates and review status.
- 04
Work consistently across a portfolio
Group properties and apply the same structured regulatory view across branches, teams and holdings, instead of each person researching independently.
- 05
See what changed
Review regulatory changes affecting a property or portfolio, with previous versions retained so an earlier position can still be explained.
Structured requirements with real-world context
Rules are stored as records rather than prose, so applicability is evaluated rather than interpreted line by line.
- Structured requirements
- Each requirement is a discrete record with a defined trigger and obligation.
- Applicability logic
- Records resolve against property and location context to return what actually applies.
- Jurisdiction & authority
- England, Scotland and Wales modelled alongside the specific issuing authority.
- Effective dates
- Start dates, end dates and designation periods held on the record.
A workspace built around professional routines
Letting and managing agents, property legal teams and portfolio compliance teams work with the same records that power the API.
- Property lookup & assessment
- Search a property and see the requirements attached to it.
- Portfolio views
- Group properties and review requirements across an entire holding.
- Plain-language summaries
- Readable summaries alongside the structured record.
- Evidence & source access
- Open the authority reference behind any requirement.
- Change visibility
- See what moved on a property or portfolio, and when.
- Shared consistency
- The same structured interpretation applied across branches, teams and cases.
Every record points back to its source
Provenance is a first-class field, not a footnote. It is what lets professional and support teams explain an answer.
- Source references
- The authority page, document or dataset a record was derived from.
- Human review
- A reviewer confirms interpretation and the cited source before publication.
- Version history
- Prior versions retained so changes can be compared over time.
- Review status
- Whether a record is draft, in review or approved for publication.
- Audit trail
- Who approved what, from which source, and when it took effect.
- Evidence notes
- Reviewer context describing how the requirement was interpreted.
Detect movement, then publish deliberately
Detection is automated. Publication is not. Change candidates are surfaced for review before they affect anyone.
- Source monitoring
- Registered authority pages and documents are watched on a defined cadence.
- Detected change workflows
- Differences are flagged against the last approved record.
- Controlled publishing
- Substantive changes pass reviewer approval before going live.
- Regulatory recensus
- Mapped authorities are revisited systematically, not only when something breaks.
Rule record anatomy
The fields a published record carries, whether it is read in the Platform or returned by the API.
- rule_idStable identifier for the requirement record
- jurisdictionEngland | Scotland | Wales
- authorityIssuing body, e.g. a local authority
- triggerConditions under which the requirement applies
- obligationWhat must be done, and by whom
- sourceReference to the originating page or document
- effective_fromDate the requirement takes effect
- review_statusdraft | in_review | approved
Put a maintained regulatory layer behind your property work.
Licenseye gives property professionals source-backed regulatory information, and gives software platforms the structured data to deliver the same answers inside their own products.