Compliance6 April 20269 min read
Property Licensing: Tracking Compliance Across Your Borough
Practical guidance for local authority teams on tracking licensing compliance rates, managing renewals, and identifying non-compliant landlords across the borough.
Introduction: Beyond the Application
Granting a property licence is not the end of the process. Effective licensing requires ongoing compliance monitoring throughout the licence period, typically five years. Licence holders must meet conditions, maintain safety standards, and keep the council informed of changes. Yet many councils struggle to track compliance systematically, often only discovering breaches when a tenant complains.
With the PRS Database launching in late 2026 and the £18.2 million enforcement fund available for capacity building, councils have an opportunity to establish robust compliance tracking systems that maximise the value of their licensing schemes.
Key Compliance Requirements to Track
Every property licence includes conditions that must be monitored. The main categories are:
Mandatory licence conditions (set by statute):
- Annual gas safety certificates provided to the council
- Electrical installation condition reports (five-yearly EICR)
- Smoke alarms and carbon monoxide alarms maintained in working order
- Minimum room sizes maintained (HMOs)
- Maximum occupancy limits observed
- Terms of occupation provided in writing
Discretionary conditions (set by the council):
- External property maintenance
- Waste management and refuse storage
- Anti-social behaviour management plans
- References for new tenants
- Notification of changes to occupancy, management, or ownership
Tracking these conditions requires a system that records what has been submitted, when it was due, and whether it meets the required standard. A simple spreadsheet becomes unmanageable once a scheme covers more than a few hundred properties.
Building a Compliance Dashboard
A compliance dashboard provides a real-time view of licensing compliance across the borough. Key metrics to display include:
- Total licensed properties vs. estimated PRS properties (licence coverage rate)
- Licences approaching renewal within 3, 6, and 12 months
- Overdue gas safety certificates (by number and percentage)
- Overdue EICRs
- Properties awaiting first inspection
- Properties with outstanding compliance actions
- Civil penalties issued (number and total value)
- Applications in progress (by stage)
These metrics should be available at borough, ward, and individual property level. Officers need the detail; managers and elected members need the summary.
Tools for building dashboards range from Power BI (commonly available in councils) to purpose-built licensing management systems that include reporting modules. The important thing is that the dashboard draws from live data, not periodic snapshots.
See how PRSCheck can help your team
Automated compliance screening, HMO detection, and enforcement pipeline management built for the PRS Database.
Automated Reminders and Escalation
Compliance tracking is most effective when it includes automated prompts:
1. Renewal reminders: Sent to licence holders six months, three months, and one month before licence expiry. Properties that lapse create enforcement risk and administrative burden.
2. Document due reminders: Gas safety certificates are due annually. The system should send reminders to licence holders at 11 months and follow up at 12 months if no certificate is received.
3. Inspection scheduling: Properties should be inspected at least once during the licence period. The system should schedule inspections on a risk-based timeline, with higher-risk properties inspected sooner.
4. Escalation alerts: When a document is overdue or a condition breach is identified, the system should escalate to an enforcement officer. After a defined period (e.g., 28 days), escalation to a senior officer or formal enforcement action should follow.
Automation reduces the administrative burden on officers and ensures that compliance failures do not slip through the cracks. It also creates an audit trail that supports enforcement action: a landlord who was reminded multiple times and still failed to comply is harder to sympathise with at tribunal.
Dealing with Non-Compliance
When a licence holder breaches a condition, the council's enforcement policy should set out a clear response:
Level 1 (minor, first breach): Written warning with a compliance deadline. For example, a late gas safety certificate that is subsequently provided within 14 days.
Level 2 (repeated or moderate breach): Formal review of the licence. The council can vary licence conditions to add more stringent requirements or reduce the licence period.
Level 3 (serious or persistent breach): Civil penalty for breach of licence conditions (up to £30,000) or prosecution. Consideration of licence revocation.
Level 4 (licence revocation): Where the licence holder is no longer fit and proper, or conditions are persistently breached, the licence should be revoked. The council must then consider whether to make a management order.
All enforcement actions should be recorded in the compliance system and reflected in the dashboard. Consistent, proportionate enforcement drives improved compliance rates over time.
The Renters' Rights Act 2025 adds further weight: enforcement history will be visible on the PRS Database, meaning that breaches in one council area follow the landlord nationally.
Preparing for PRS Database Cross-Referencing
The PRS Database will require landlords to declare their licensed properties. This creates a powerful cross-referencing opportunity:
- Properties registered on the PRS Database in your area that are not in your licensing system: potentially unlicensed
- Properties in your licensing system that are not on the PRS Database: the landlord may have failed to register nationally
- Compliance declarations on the PRS Database that conflict with your local records: further investigation needed
To exploit this cross-referencing, your licensing database must use standardised property references (UPRNs) and landlord identifiers. Begin the data cleansing work now so that matching is accurate when the PRS Database goes live in late 2026.
Frequently Asked Questions
Register Your Interest
Be first to know when PRS Database integration goes live.