Management Dashboard — Properties & Imports

The Properties area holds your property stock. It's the register surveys are raised against, and where you bulk-import from your housing management system. Tiered — Basics for importing and browsing, Deep dive for the file format and matching, Technical for how it's stored and searched.

Basics — importing your stock

Open Properties → Import.
Click Example file to download a template.
Fill it in. The minimum is address line 1 and postcode; UPRN, local authority, tenure and archetype are optional but recommended.
Upload it as CSV or Excel (.xlsx).
Review the preview: the count of properties ready, and any skipped rows listed with the reason (e.g. missing postcode, duplicate UPRN).
Confirm the import. Done.

Re-importing is safe. Rows are matched on UPRN — re-importing the same UPRN updates the property, it never creates a duplicate.

Deep dive — file format & matching

Accepted formats: CSV and Excel .xlsx. Legacy .xls isn't supported — save as .xlsx or CSV first.
Header auto-mapping: column names are matched flexibly and case- insensitively. For example "address", "address line 1", "line1" and "street" all map to the first address line; "post code", "postcode" and "zip" all map to postcode.
Row validation: rows missing an address or postcode are skipped and listed. A UPRN with no digits is flagged. Duplicate UPRNs within one file keep the first occurrence and warn on the rest.
What each column is for: UPRN is the stable identity (and the merge key); local authority and tenure feed reporting and Awaab's Law context; archetype helps group similar construction types.

Technical — storage & search

Identity: where a UPRN is provided it becomes the record key, so imports are idempotent (re-import = update, not duplicate). Properties without a UPRN are flagged for review.
Linkage: surveys can be linked to a property so evidence chains onto that property's timeline; a work order carries the property reference.
Search at scale: properties are indexed for prefix search on address, so large estates stay responsive.
Tenant-scoped: properties belong to your organisation only; isolation is enforced server-side.
Parsing: the CSV/Excel parsers (BOM handling, quoted fields, header aliasing, UPRN normalisation) are unit-tested and gated in CI.

Tenancy register

Alongside your property stock, Properties → Tenancies holds who lives where — tenant contact details, occupancy dates and status, linked to the property by UPRN or your own reference. It's a lean, operational register: no vulnerability or special-category data is stored here, and (unlike survey evidence) tenancy records are ordinary data, not sealed or hash-chained.

Add tenancies one at a time, or import a CSV: tenancy reference, UPRN, tenant name(s), contact email/phone, occupancy start and status. Re-importing on the same reference (or UPRN + name) updates the existing record rather than duplicating it; rows that can't be matched are flagged needs review rather than silently dropped.
Export the whole register as CSV at any time, or push it straight to your own SFTP server — see SFTP (Platform plan).
Raising a work order or drafting a resident letter for a property with a matching tenancy suggests that tenancy's contact automatically, so you're not retyping a name and email you've already recorded.

Next: Work orders & Awaab timeline (in progress), or back to the help index.