Residential identity
Housing history that belongs to the resident, not to an estate
A person may live in five homes over fifteen years and still have no structured record of any of it. A residential profile keeps that history continuous, with the source of every claim attached to it.
The model
A user is not a resident, and a resident is not owned by an estate
A platform user is an authenticated identity. Being a resident is a relationship with a property over a period of time. Estates come and go from that history; the history itself does not restart each time.
Current tenancy
The property, the period, the rent obligation, the landlord or manager, and the lease held against it.
Previous residences
Homes lived in before joining the platform, declared by the resident and strengthened as evidence arrives.
Documents
Leases, receipts and tenancy paperwork attached to the residence they belong to, held in private storage.
Rental obligations
What was owed, for which period, so a payment can be matched to the obligation it settles.
Payment evidence
Platform-recorded payments plus supporting evidence for payments made before or outside the platform.
Verification
The source that backs each record, kept visible rather than flattened into a single tick.
Verification
A declaration must never look like a verified fact
This is the part that decides whether the record is worth anything. Every entry keeps the source that supports it, and the difference is visible at a glance — through an icon and a label, never through colour alone.
- Platform verifiedThe record was created by activity on the platform itself.
- Financially verifiedA payment was confirmed against a financial record, not just asserted.
- Landlord verifiedThe landlord or property manager independently confirmed the tenancy.
- Document verifiedA lease or receipt was supplied and checked against the record.
- Resident declaredThe resident entered this themselves and nothing independent supports it yet.
- Pending verificationSubmitted and waiting on a check or a confirmation from someone else.
- RejectedThe evidence did not support the claim, and the record says so.
There are 8 states in total, including one for records that need refreshing. The point of keeping them separate is that a landlord reading a shared record can tell the difference between something the platform observed and something the resident typed in.
Portable record
The Residential Passport
Verified tenancy and payment history is assembled into a summary a resident chooses to share — with a prospective landlord, an agent, or an estate they are applying to join.
- Generated from source records, never maintained as a separate truth
- Shows identity status, current residence, previous residences and payment consistency
- Keeps the verification source visible on every line
- Shared by the resident, scoped to a recipient, and withdrawable
Privacy
Cross-estate history is not a shared asset
An estate administrator sees what they need to run the estate. That is not the same as reading everywhere a person has ever lived.
Scoped by default
Estate roles are scoped to an estate. Records from other estates are outside that boundary unless the resident shares them.
Resident-initiated sharing
A shared summary is created by the resident, aimed at a recipient, and can be withdrawn afterwards.
Private document storage
Leases, IDs and payment evidence live in private storage behind authorization — never on a permanent public link.
Give residents something worth taking with them
Talk to us about how residential records would work for your estate and the people living in it.