Domicium
Portfolios

Student Housing

An academic-year cycle, a lot of short tenancies turning over at once, and guarantors who are not the tenant. Volume is the problem, not complexity.

All portfolio types

Owners of hostels and rooms let to students.

What makes this hard

Everything turns over in the same fortnight

An entire hostel empties and refills around the academic calendar, and the admin lands in one burst.

The payer is not the occupant

A parent or guarantor usually pays, and the record has to hold both without confusing who lives there.

What Domicium does about it

  • Student housing as its own property type

    Recorded distinctly rather than as generic residential, so it can be searched for and reported on separately.

    Leases & Tenancies
  • Guarantor on the rental passport

    A renter records a guarantor's name and phone once, and it travels with every application they make.

    Verification & Trust
  • Rent advance flagged as residential

    Student housing gets the same advance protections as residential, because that is what it is.

    Leases & Tenancies
Manage → Portfolio
Properties, units, occupancy and monthly rent roll across the whole portfolio.
Properties, units, occupancy and monthly rent roll across the whole portfolio.

The screens you would live in

Captured from the running product, not drawn. Every figure came out of the database through the same code a customer uses.

Dashboard → My listings
A landlord's listings with their verification tier and status on each one.
A landlord's listings with their verification tier and status on each one.
Worth knowing

What it does not do for student housing yet

  • No bulk tenancy creation or renewal — a hostel turning over forty rooms creates them one at a time.
  • No room-sharing model: a room with two occupants is one tenancy.

Run student housing on Domicium

Start with one property and the ledger behind it. Nothing here needs a migration project to be useful in week one.

Also relevant