What a tenancy agreement needs to survive a deposit dispute

This is about evidence, not law. Whether a clause is enforceable where you operate is a question for a lawyer, and nothing here is advice. What follows is the narrower, more practical question: eleven months after a signature, what do you actually need to be able to show?

It is worth separating because most operators are well served on the legal side, where the template came from a solicitor and the clauses are fine, and badly served on the evidential side, where the whole record is an email thread and a PDF with a picture of a signature in it.

The four questions a dispute asks

Who signed it? Not "whose name is typed at the bottom", but who actually put their hand to it. If your process is emailing a PDF to an address, what you can show is that somebody with access to that mailbox returned a document with a name on it. That is usually enough. It stops being enough the moment the other side says it was not them.

When? The date typed into the document is the date somebody typed. The date it was signed is a different fact and occasionally an important one. A tenancy that began before the agreement was executed is a conversation you would rather have with a timestamp than without.

What exactly did they sign? This is the one that catches people. If you can open the document and edit it, so can anyone arguing with you, and "this is not the version I agreed to" is a claim you cannot answer by producing a file. What answers it is a hash: a fingerprint of the document as signed, recorded at the moment of signing, that changes if a single character does.

Can you find it at all? Unglamorous and the most common actual failure. The agreement is in an inbox belonging to somebody who left, or in a folder structure from two naming conventions ago.

What a signing record should contain

Independent of any product, the useful set is small:

• The signer's name and the address the invitation went to.
• A timestamp for each meaningful event: sent, opened, signed.
• The IP address and user agent at the moment of signing.
• A hash of the exact document that was signed.
• The countersignature, recorded the same way.

None of that proves identity in a strong cryptographic sense, and any vendor claiming otherwise about a browser signature is overselling. What it does is make the ordinary story checkable rather than asserted: a person received a unique link at their own address, opened it from a plausible place, and signed this exact text. In practice that is what settles a deposit argument, because the alternative is two parties describing an email thread from memory.

The deposit-specific part

Deposits generate more disputes than everything else combined, and almost all of them are arguments about condition rather than about the agreement. Two things reduce them, neither of which is software:

Photograph the flat at check-in and check-out, and attach the photographs to the tenancy. Not to a phone, not to a WhatsApp thread with a cleaner. To the record. The asymmetry is stark: five minutes at handover against an afternoon of correspondence eleven months later.

Write the deposit-return timeline into the agreement and then meet it. A surprising share of disputes are not about the deduction at all; they are about silence. Somebody is owed money, hears nothing for six weeks, and escalates out of uncertainty rather than disagreement.

If you take nothing else

Keep the agreement, the signing evidence and the condition photographs attached to the tenancy rather than to a person or an inbox. The tenancy is the thing that will still exist and still be findable in two years, when whoever handled it has moved on.

The Quarters does this because we got tired of the alternative, and the signing record above is the one it keeps. But the ordering matters more than the tool: an operator who photographs handovers and files agreements against the tenancy in a folder structure is in better shape than one with excellent software and neither habit.