Skip to content
Dharri
Estate operations · Residential identity

Better managed communities. A residential history that moves with you.

Manage residents, properties, payments, visitors, issues and community operations from one platform — while the tenancy and payment records built along the way stay with the resident when they move.

Built for estate and facility teams first, with a resident mobile app and a portable residential record following the same data.

The problem

Residential management is spread across too many places

Most estates already run on a dozen disconnected tools. Nothing reconciles, nothing is auditable, and when a resident moves out the record of their tenancy goes with the spreadsheet.

Today

  • Paper gate registers
  • WhatsApp payment reminders
  • Service-charge spreadsheets
  • Transfer screenshots
  • Phone calls to security
  • Lease files on somebody's laptop

On the platform

  • One resident and property register
  • Invoices, payments and arrears in one ledger
  • Time-bound visitor passes verified at the gate
  • Issues with owners, evidence and status
  • Announcements with a delivery record
  • Tenancy records that outlive the spreadsheet

Estate operations

The operational layer estate and facility teams actually work in

Six connected areas, one estate record. Facility managers stop reconciling between tools and start working from a single view of the community.

Estate operations feature groups

  • Residents & properties

    One register of units, blocks and zones with the people attached to them, and a record of who lived where and when.

    • Occupancy and tenancy state
    • Owner and tenant relationships
    • Move-in and move-out history
  • Payments & collections

    Service charges, levies and utility bills issued against units, with payment status, receipts and arrears in one ledger.

    • Invoices and demand notices
    • Reconciliation and receipts
    • Arrears and defaulter visibility
  • Visitors & access

    Residents invite guests ahead of time and security verifies a single-use code at the gate instead of a paper book.

    • Time-bound passes
    • Gate verification
    • Entry and exit logs
  • Issues & maintenance

    Faults are reported with location and evidence, assigned to someone, and tracked through to resolution.

    • Category and location
    • Assignment and status
    • Maintenance history
  • Communication

    Announcements and emergency notices reach the right blocks or the whole estate, with a record of what was sent.

    • Targeted audiences
    • Emergency notices
    • Sent history
  • Infrastructure

    Roads, drainage, power, water, streetlights, gates and shared facilities tracked as assets with faults and projects against them.

    • Asset register
    • Faults and downtime
    • Community projects

Residential identity

A resident can move home without losing the record of where they have lived

An estate has a membership relationship with a resident. It does not own that person's housing history. Moving creates a new tenancy on one continuous residential profile — not a new identity in someone else's spreadsheet.

  • Current tenancy

    Property, period, rent obligation, landlord or manager, and the lease on file.

  • Previous residences

    Homes lived in before joining the platform, added by the resident and strengthened with evidence over time.

  • Documents & payment evidence

    Leases, receipts and payment records attached to the tenancy they belong to, not scattered across chats.

  • Verification that stays distinguishable

    A resident-declared record never looks the same as one a landlord, a document or a payment confirmed.

How residential identity works

Residential Passport

A portable residential record the resident controls

As verified tenancies and rent payments accumulate, they can be assembled into a Residential Passport — a shareable summary a resident can send to a prospective landlord instead of a folder of screenshots.

  • Built from source records

    The summary is generated from tenancies, invoices and payment evidence already on the platform. Nothing is typed in twice, and nothing is edited after the fact.

  • Verification stays visible

    Every entry keeps the source that supports it — a confirming landlord, a document, a recorded payment, or the resident's own declaration.

  • The resident decides who sees it

    Sharing is initiated by the resident, scoped to a recipient, and can be withdrawn. An estate admin does not get automatic access to history from other estates.

Security & access

Access that is verifiable, and a gate log that is not a paper book

Visitor management is where most estates feel the gap first. The flow is deliberately short, because it has to work in a few seconds at a gate at night.

  1. 01

    Resident invites a guest

    A visitor is expected, so the resident creates a pass with a window of validity.

  2. 02

    A single-use code is issued

    The code or QR is sent to the guest and expires on its own — no standing access.

  3. 03

    Security verifies at the gate

    Gate staff confirm the code against the expected visit and see only what they need to do the job.

  4. 04

    Entry and exit are recorded

    Check-in and check-out are logged against the unit, so the estate has an actual access trail.

Incidents and faults follow the same discipline

A security incident, a broken barrier and a dead street light all become a tracked record with a location, an owner and a status — instead of a message that scrolls out of a group chat.

Who it is for

Three groups, one record

Everyone works from the same underlying estate and tenancy data, so nothing has to be re-entered at a hand-off.

Run the community from one place

  • One register of units, residents and occupancy instead of four spreadsheets
  • Billing, payments and arrears reconciled against the unit that owes them
  • Visitor access verified at the gate with an entry and exit trail
  • Issues assigned, evidenced and tracked to resolution
  • Announcements delivered to the right blocks with a record of what was sent
  • Reporting a board or association can actually be shown
For estates and facility teams

How it works

Operations first. The record builds itself.

Nothing here asks an estate to do extra data entry to produce residential history. The history is what normal estate operations already generate.

  1. 01

    The community is onboarded

    Blocks, zones and units are set up, charges are configured, and the people who run the estate get their roles and scope.

  2. 02

    Residents and units are connected

    Residents are invited and attached to the unit they occupy, as tenant or owner, with the tenancy period recorded.

  3. 03

    Day-to-day operations move across

    Billing, visitor access, issues and announcements run on the platform, so the estate record is a by-product of normal work.

  4. 04

    Verified residential records accumulate

    Every recorded tenancy and payment strengthens the resident's own housing history — and it stays with them after they leave.

Run your community with better visibility

Tell us about your estate and we will walk through how the platform would map onto how you already work.