Portfolio Audit

Check a small batch before licensing work becomes expensive

Start with a fixed-scope £250 audit for up to 15 rental properties. Locastica checks council licensing sources and returns the evidence, fee context, freshness, and review flags in a file your team can keep.

Request the £250 audit Download CSV template

What you get back

A row-by-row licensing position for each submitted property
HMO, additional, and selective licensing context where relevant
Council evidence links and published fee context where available
Freshness, confidence, and address or boundary review flags kept visible

Built for pre-application triage

A file upload, an embedded panel, or one API call is enough to get started. The first audit is deliberately bounded: small enough to test quickly, but detailed enough to show whether source-backed licensing checks would improve your current council-by-council process.

01: Send a small real batch: up to 15 postcodes or full addresses.
02: Locastica resolves the relevant council context and checks source-backed HMO, additional, and selective licensing evidence.
03: You get a reviewed file 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 offer. The point is to test a real licensing workflow: which council source applies, what evidence supports the answer, 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 audit trail, not a black-box lookup. Rows can be marked review-required where a council scheme depends on a ward, designation boundary, property type, 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 first paid audit

Use this form if you want the fixed £250 audit for up to 15 properties, or if you want to send a representative export before confirming scope.

For larger batches, recurring checks, or API/embedded use, we will quote the next step only after the first rows prove the 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 15 postcodes or full addresses for the first paid audit
Whether each row is HMO, single-let, or unknown if you know
Any councils, deadlines, renewals, or application decisions in scope

Built for pre-application triage

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

02: Locastica resolves the relevant council context and checks source-backed HMO, additional, and selective licensing evidence.

03: You get a reviewed file 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