Tenancy & Deposit Register
The pack already prices a rent ledger and a deposit statement. This is the tenancy itself: which unit, who is in it, when the term ends, how much deposit is held and where it was protected. A small landlord's two worst surprises are a term that rolled over unnoticed and a deposit whose protection nobody can evidence, and both are a blank cell in a register nobody kept. It asserts no protection rule and no notice period - those are your jurisdiction's, they carry penalties and they change - it tells you which rows have nothing recorded at all.
Your database
Fields
| Field | Type |
|---|---|
| Unit / address | text |
| Tenant(s) | text |
| State | select |
| Term start | date |
| Term end / review | date |
| Rent (amount and how often) | text |
| Deposit held | text |
| Deposit protected — scheme and reference | text |
| Protected on | date |
| Notes | text |
Frequently asked
Where is this stored?
Only on this device, in your browser. Nothing is uploaded and there is no account. Export to CSV or JSON to back it up, hand it to an auditor, or move it to another machine.
Does it know my deadlines and required frequencies?
No, and that is deliberate. Inspection intervals, retention periods and review cadences are set by your standard, your jurisdiction, your certifier or your own procedure, and they change. This runs offline and cannot know if one changed last month, so it never asserts one. You enter the dates that apply to you and it does the arithmetic on those.
Does it know my deposit-protection deadline?
No. That rule is jurisdiction-specific, carries statutory penalties and changes, so a tool running offline has no business asserting it. What it does is show you every tenancy where a deposit is held and nothing whatsoever is recorded about protecting it.