PRS Database Implementation: A Council Officer's Guide

The PRS Database is a national register of all privately rented properties in England, mandated by the Renters' Rights Act 2025. Every landlord must register their properties before they can lawfully market or let them. The database will hold property addresses, landlord details, tenancy information, and key compliance records including gas safety certificates, Electrical Installation Condition Reports (EICRs), and Energy Performance Certificates (EPCs). Unlike existing local licensing schemes, the PRS Database is universal. It covers every privately rented property regardless of whether the local authority operates selective or additional licensing. For enforcement teams, this creates a comprehensive register that eliminates the guesswork of identifying which properties in their area are privately let.

Local authorities will have query access to the PRS Database for properties within their geographic boundary. The data fields available to councils are expected to include: the registered landlord's name, contact details, and any managing agent details; the property address and UPRN; the tenancy start date and current rent; gas safety certificate status and expiry date; EICR status and expiry date; EPC rating and certificate reference; HMO status declaration; and any enforcement history recorded against the property or landlord. This data can be cross-referenced with existing council records, council tax data, and licensing registers to identify discrepancies. Properties that appear on council tax as single-occupancy but are registered on the PRS Database as multi-tenant, for example, could indicate an undeclared HMO or council tax fraud.

The PRS Database will provide an API for local authority access, allowing councils to query data programmatically rather than relying on manual portal searches. To prepare for integration, housing teams should work with their IT departments now to audit current case management systems, identify what data fields they currently hold on PRS properties, and map out how PRS Database data will flow into existing workflows. Key questions to resolve include: which team members will have access credentials; how often will bulk data extracts be refreshed; will integration be automated or manual; and how will data from the PRS Database be reconciled with existing licensing and enforcement records. Councils already using modern cloud-based enforcement platforms will find integration straightforward. Those relying on spreadsheets or legacy systems should use this as an opportunity to upgrade.

The PRS Database creates several new enforcement opportunities. First, failure to register is itself an offence carrying civil penalties of up to £7,000. Councils can identify unregistered properties by comparing the database against known PRS properties from council tax, licensing records, and complaint data. Second, providing false or misleading information to the database is a separate offence with penalties up to £40,000. Cross-referencing database declarations against actual property conditions found during inspections can identify false declarations. Third, the database enables systematic compliance screening at a scale that was previously impossible. Rather than waiting for tenant complaints, councils can proactively identify every property with an expired gas safety certificate, an overdue EICR, or an EPC below the minimum E rating. This shifts enforcement from reactive to proactive, which is where the greatest improvements in housing conditions are achieved.

The PRS Database is expected to launch in late 2026, with landlords given a registration window before enforcement of the registration requirement begins. Councils should use the intervening months to complete the following preparation checklist. Audit your current PRS property data and identify gaps. Review your case management system's ability to accept external data feeds. Train officers on the new offences related to database registration. Develop standard operating procedures for bulk compliance screening. Establish data sharing agreements with your IT department and any third-party software providers. Review your enforcement policy to include database-related offences and set appropriate penalty levels. Engage with MHCLG consultations on the database's technical specification as they are published. Councils that prepare early will be able to leverage the database from day one, while those that wait will face a scramble to build processes after launch.

Access to PRS Database information will be subject to data protection requirements. Councils must process the data in accordance with the UK GDPR and the Data Protection Act 2018. This means establishing a lawful basis for processing (which for enforcement purposes will typically be 'public task'), completing a Data Protection Impact Assessment for the new data flows, ensuring data is stored securely, and establishing retention periods for extracts from the database. Officers should only access data for legitimate enforcement purposes, and audit trails of queries should be maintained. Sharing PRS Database information between council departments (for example, with council tax or planning teams) will require clear data sharing protocols. These governance arrangements should be established before the database launches to avoid delays in utilising the data.