Sending it is not the hard part. Proving you sent it is.
Every document dated, every send recorded, every action logged and not editable afterwards. It builds while you work, which is the only way it is ever there when somebody disagrees with you months later.
What does landlord record keeping actually mean?
It means being able to produce, later, what you did and when you did it. Not the document itself, which most landlords have somewhere, but the date it was sent, the person it went to and the fact it arrived. That second half is what disputes turn on and it is the half that almost nobody keeps.
LetCompliance records it as a side effect of doing the work. Send a certificate and the send is logged against that tenant and that property, with the time. If the email is delivered, that is recorded too, and if it bounces, that is recorded instead, which is far more useful than assuming it landed.
Actions are written to a log that cannot be edited afterwards. Not by you, not by a colleague, not by us through the interface: entries are written by the system and pinned to the time they happened. A record you can go back and tidy is not a record, it is a draft, and the other side will say so.
Everything sits against the property and the tenancy rather than in a folder structure you have to maintain. When a tenancy ends, or a scheme asks, or a tenant remembers things differently, the answer is assembled already. Nothing has to be reconstructed from an inbox and a camera roll.
Three things a folder of PDFs cannot do.
Proof it was delivered, not just sent
Every document sent to a tenant carries the time it went and what happened to it: delivered, opened, or bounced. A bounce you know about is a problem you can fix; a bounce you never saw is a document you believe was served and was not.
A log that cannot be tidied up later
Entries are written by the system and pinned to the moment they happened, so nobody can go back and adjust the history, including you. That constraint is the entire value: a record anyone could have edited proves only that somebody typed something.
Filed against the tenancy, not in a folder
Certificates, agreements, notices, inspections and repairs all attach to the property and the tenancy they belong to. There is no filing system to keep up, which matters because the filing system is always the thing that gets abandoned first.
How the record builds itself
- 01
You do the thing
Send the move-in pack, log a repair, walk an inspection, serve a notice. The ordinary work of the tenancy.
- 02
It is dated as it happens
The entry is written at the time, by the system, and pinned there. Nothing depends on you remembering to record it afterwards, which is the step that never survives a busy month.
- 03
Delivery comes back on its own
Emails report what happened to them. Delivered, opened or bounced, all attached to the document and the person.
- 04
It is there when you need it
Months later, filtered by property, tenancy or date. Assembled already rather than reconstructed from an inbox.
The record is only strong because of what feeds it.
These are the moments that leave a trace, and they are all in the same login on the same properties.
Check-in and check-out walks, paired and dated
Deposit deductions with the working attached
Repairs reported by the tenant, with a date
Rent by Direct Debit, with late payments chased
A live 0 to 100 score for every property
SA105, Section 24 and capital gains figures
Questions, answered
- Why does proof of delivery matter more than the document?
- Because almost every landlord has the document. Far fewer can show when it went and that it arrived, and that is the part an argument turns on. A certificate in your downloads folder says you had one; a send recorded against that tenant on that date says you gave it to them.
- Can the log be edited?
- No, and that is the point. Entries are written by the system and pinned to the time they happened, so nobody can adjust the history afterwards, including you and including us through the interface. A record that could be tidied up would prove nothing.
- What happens if an email bounces?
- It is recorded as a bounce against that document and that person, rather than being quietly assumed to have arrived. That is the whole difference: a bounce you can see is a problem you can still fix, and a bounce you never saw is a document you wrongly believe was served.
- What if I served something outside the app?
- You can record that you did, with the date and how, so the trail stays complete rather than having a hole in it where you handed something over in person. A record that only knows about the things that happened online is a record with a gap in exactly the place people ask about.
- Do you claim this will win a case?
- No. What a court or a deposit scheme makes of any evidence is for them, and anyone telling you otherwise is selling. What we will say is what the record is: dated, not editable after the fact, and delivered provably rather than presumably.
- What does it cost?
- Free forever for one property, with paid plans from £14.99 a month and a 14-day full trial. The audit trail and document storage are on every plan, including the free one.
UK-built · Founder-led · GOV.UK-cited
Built by a landlord, for landlords.
I let property myself, and I was tired of juggling an agent, a spreadsheet and a handful of reminder apps just to stay on the right side of the law. So we built the one login I actually wanted: advertise the property, take applications, collect the rent, and keep every certificate and notice in order, each taken straight from GOV.UK.
The record you need in a year is the one you are making today.
It builds while you work, so there is nothing to reconstruct later. Free forever for one property, and no card to begin.
Start free trial