Portfolio Audit

Check a small batch before compliance work turns urgent

Start with a fixed-scope £395 Compliance Sprint for up to 10 rental properties. Locastica checks Renters' Rights evidence gaps plus HMO, additional, and selective licensing exposure, then returns the official sources, freshness notes, fee context, and review flags in a file your team can keep.

Request the £395 sprint Download CSV template

What you get back

A red, amber, or green evidence status for each submitted property
Renters' Rights evidence gaps plus HMO, additional, and selective licensing exposure
Official council source links and published fee context where available
Freshness notes and address or boundary review flags kept visible

Built for the post-deadline evidence gap

A file upload, an embedded panel, or one API call is enough to get started. The first sprint is deliberately bounded: small enough to move quickly this week, but detailed enough to show which rows need evidence, source review, or licensing action before a landlord query, tenant complaint, or council issue becomes harder to handle.

01: Send a small real batch: up to 10 postcodes or full addresses.
02: Locastica checks Renters' Rights evidence status plus source-backed HMO, additional, and selective licensing exposure.
03: You get a reviewed red/amber/green file in 48-72 hours with source links, fee context where available, freshness, and review-required rows clearly marked.

Send postcodes, addresses, or the file you already have

A spreadsheet helps, but it is not the point of the sprint. The point is to get a defensible property-by-property view: what evidence is missing, which council source applies, and which rows need address or boundary review before anyone relies on them.

Minimum CSV columns

Address line 1 * (address_line_1): Primary street address or building name/number.
Postcode * (postcode): Required for property-level matching and council routing.
Property reference (property_reference): Your internal ID or portfolio reference if you have one.
Address line 2 (address_line_2): Flat, unit, or building detail when needed.
Town or city (town_or_city): Useful when the export is messy or spans similar postcodes.
UPRN (uprn): Helps reconcile large portfolios if your system already stores it.
Property type (property_type): Useful context such as HMO, single-let, flat, room-let, or unknown.
Occupancy context (occupancy_context): Optional detail such as occupants, households, bedrooms, or known HMO status.
Workflow notes (workflow_notes): Optional context such as branch owner, portfolio segment, or urgency.

Common header mappings

Address line 1 (address_line_1): address1, address_1, property_address, address_line1, building_number
Postcode (postcode): zip, postal_code, post_code
Property reference (property_reference): property_id, reference, asset_id
Address line 2 (address_line_2): address2, unit, flat
Town or city (town_or_city): town, city, locality
UPRN (uprn): uprn_number, unique_property_reference_number
Property type (property_type): type, property_kind, letting_type, tenure_type
Occupancy context (occupancy_context): occupancy, hmo_status, hmo, occupants, households, bedrooms
Workflow notes (workflow_notes): notes, comment, branch_notes

Download field guide JSON

What comes back in the reviewed file

The output is designed for a working evidence file, not a black-box lookup. Rows can be marked review-required where a council scheme depends on a ward, designation boundary, property type, occupancy context, or source freshness check.

Property reference (property_reference): Echoed back so your team can reconcile each reviewed row into the source system.
Matched address (matched_address): Normalized property address used for the reviewed result.
Postcode (postcode): Returned in the delivery file for routing, matching, and downstream joins.
Council name (council_name): Council responsible for the licensing position.
Council code (council_code): Useful for repeat audits, joins, and later API mapping.
Licensing decision (licensing_decision): Property-level answer summarising whether a licence may be required.
Scheme name (scheme_name): Named scheme or designation context behind the answer when applicable.
Scheme type (scheme_type): The scheme family such as additional, selective, or mandatory HMO.
Fee context (fee_context): Licence fee note where the council source publishes one.
Evidence URL (evidence_url): Official council source kept attached to the row.
Last verified at (last_verified_at): When Locastica last verified the position behind the row.
Review context (review_context): Freshness, pending review, or caveat note visible before you rely on the answer.
Soft flag (soft_flag): Explicit trust cue showing whether the row needs extra operator judgment.

Download example output CSV

Request the Compliance Sprint

Use this form if you want the fixed £395 sprint for up to 10 properties, or if you want to send a representative export before confirming a larger paid scope.

For larger batches, recurring checks, or API/embedded use, we quote the next step only after the first rows prove the evidence workflow.

Name *

Work email *

Company *

Role

Phone

Current system

Portfolio size *

Batch file readiness *

First batch size *

Target delivery window *

What do you need this for? *

Scope notes

Representative sample CSV

Optional. Upload one representative CSV export up to 2MB and we will capture the file with its header-compatibility summary.

Need a clean starting point first? Download the starter CSV or the field guide JSON.

Helpful to send

Up to 10 postcodes or full addresses for the fixed GBP 395 sprint
Whether each row is HMO, student, room-let, single-let, or unknown
Any Renters' Rights, council, renewal, complaint, or landlord deadline in scope

Check a small batch before compliance work turns urgent

Built for the post-deadline evidence gap

01: Send a small real batch: up to 10 postcodes or full addresses.

02: Locastica checks Renters' Rights evidence status plus source-backed HMO, additional, and selective licensing exposure.

03: You get a reviewed red/amber/green file in 48-72 hours with source links, fee context where available, freshness, and review-required rows clearly marked.

Send postcodes, addresses, or the file you already have

Minimum CSV columns

Address line 1 * (address_line_1): Primary street address or building name/number.
Postcode * (postcode): Required for property-level matching and council routing.
Property reference (property_reference): Your internal ID or portfolio reference if you have one.
Address line 2 (address_line_2): Flat, unit, or building detail when needed.
Town or city (town_or_city): Useful when the export is messy or spans similar postcodes.
UPRN (uprn): Helps reconcile large portfolios if your system already stores it.
Property type (property_type): Useful context such as HMO, single-let, flat, room-let, or unknown.
Occupancy context (occupancy_context): Optional detail such as occupants, households, bedrooms, or known HMO status.
Workflow notes (workflow_notes): Optional context such as branch owner, portfolio segment, or urgency.

Common header mappings

Address line 1 (address_line_1): address1, address_1, property_address, address_line1, building_number
Postcode (postcode): zip, postal_code, post_code
Property reference (property_reference): property_id, reference, asset_id
Address line 2 (address_line_2): address2, unit, flat
Town or city (town_or_city): town, city, locality
UPRN (uprn): uprn_number, unique_property_reference_number
Property type (property_type): type, property_kind, letting_type, tenure_type
Occupancy context (occupancy_context): occupancy, hmo_status, hmo, occupants, households, bedrooms
Workflow notes (workflow_notes): notes, comment, branch_notes

Download field guide JSON

What comes back in the reviewed file

Property reference (property_reference): Echoed back so your team can reconcile each reviewed row into the source system.

Matched address (matched_address): Normalized property address used for the reviewed result.

Postcode (postcode): Returned in the delivery file for routing, matching, and downstream joins.

Council name (council_name): Council responsible for the licensing position.

Council code (council_code): Useful for repeat audits, joins, and later API mapping.

Licensing decision (licensing_decision): Property-level answer summarising whether a licence may be required.

Scheme name (scheme_name): Named scheme or designation context behind the answer when applicable.

Scheme type (scheme_type): The scheme family such as additional, selective, or mandatory HMO.

Fee context (fee_context): Licence fee note where the council source publishes one.

Evidence URL (evidence_url): Official council source kept attached to the row.

Last verified at (last_verified_at): When Locastica last verified the position behind the row.

Review context (review_context): Freshness, pending review, or caveat note visible before you rely on the answer.

Soft flag (soft_flag): Explicit trust cue showing whether the row needs extra operator judgment.

Download example output CSV