A portfolio that knows which unit every request belongs to

Because a person and a tenancy are different things that change at different times. If the tenancy lives on the tenant row, then renewing overwrites the old term, moving flats loses the previous address, and a joint tenancy has nowhere to go. Making the Lease its own record linking a Unit to a Tenant means somebody can hold three tenancies over six years and every one of them keeps its own dates and rent.

Yes, and this is the change most worth making after the build. Any table can publish a public form at an unguessable URL, so a maintenance form can write straight into Maintenance Requests without the tenant needing an account. Submissions arrive as ordinary records with a ticket number, ready to be prioritised, and the server validates every field so what can be submitted is exactly what you allowed.

It tracks what is owed, not the money movement. Leases carry a Monthly Rent and the dashboard totals active lease revenue, which answers what the portfolio should be producing. Taking payment is your bank's job or your agent's; if you want payments recorded here, a Payments table linked to the lease is about ten minutes of work and gives you arrears as a rollup.

That was in the sentence that produced it — forty buildings across three cities — and City came out as a Select on Buildings rather than free text, so filtering and grouping by city work properly rather than tripping over spelling. The building addresses also drive a map view, so a portfolio spread across several places is something you can look at rather than sort.

Yes. Permissions run at folder, table and field level, so a contractor can be given the maintenance queue without seeing rents or tenant contact details, and read-only viewers cost nothing at all. That matters more here than in most trades, because tenant data is personal data and the fewer people who can see it, the better.