Scattered records are why landlords lose winnable hearings
The evidence usually exists. It is in a camera roll, a text thread, an email account and a notes app — and it cannot be assembled, served and filed inside the RTB's deadlines. Here is where that fails and how to fix it.
There is a failure mode that looks nothing like negligence. The landlord did everything right. They inspected the unit, kept photos, answered every repair request quickly, and can describe the tenancy accurately from memory. They still lose, because none of that arrived at the hearing in a form the arbitrator could use.
The distinction that matters is not between landlords who document and landlords who do not. It is between landlords whose records are in one place and landlords whose records are spread across six apps that do not talk to each other.
General information about documentation practice, not legal advice. Confirm current deadlines and submission requirements with the Residential Tenancy Branch before relying on them — this was checked in August 2026 and procedural rules are revised periodically.
Deadlines assume your evidence already exists
For a participatory hearing, the Residential Tenancy Branch requires an applicant's evidence to be received at least 14 days before the hearing, and a respondent's at least 7 days before. When you count those days, the day the documents are received and the day of the hearing are both excluded — which quietly removes two days from the window most people assume they have.
There is a sharper version for landlords. Where the application concerns a Ten Day Notice to End Tenancy, the Branch requires the evidence to be submitted at the time of application. There is no assembly period at all. Whatever you can lay your hands on when you file is your case.
Read that against how most tenancy records are actually stored. The rent history is a bank app. The repair thread is in text messages. The lease is a photograph of a paper document. The condition report is in email, if it was ever sent. Reconstructing all of that under deadline is the task — and it is a much bigger task than anyone estimates while they are not doing it.
The upload limits nobody plans for
Evidence has to arrive in a format the Branch accepts, within a size it accepts. Non-video files are capped at 10MB; video files at 200MB. Documents are accepted as PDF, DOC, DOCX, TXT, RTF, ODT, XLSX, CSV and PPT; images as JPG, JPEG, PNG, TIF, TIFF and BMP.
A modern phone photograph is routinely 3 to 5MB. Two or three move-out photos can exceed a 10MB non-video limit on their own, which means the landlord with forty photographs of a damaged unit discovers at the deadline that their evidence does not fit — and starts compressing and re-exporting files on the day it is due, or worse, selecting a handful and hoping they are the right ones.
A screenshot of a text thread is a common substitute for a record, and it is a weak one. It carries no verifiable date, it is trivially incomplete, and forty of them are not a chronology — they are forty images an arbitrator has to order themselves.
What an organized record actually looks like
An arbitrator is reconstructing a sequence of events from documents. Everything that helps them do that quickly helps you. Everything that makes them hunt does not.
- A rent ledger showing what was owed, what was received, and the date each payment actually arrived — not just which months were marked paid.
- The tenancy agreement, with any addenda, as one document rather than a set of photographs.
- Condition inspection reports from both ends of the tenancy, with the photographs that support them.
- Each repair request with the date it was reported, what was done, and when it was resolved.
- Every notice served, together with proof of how and when it was served.
- A plain chronology naming each document, so the arbitrator can follow the sequence without assembling it.
Notice how much of that is produced automatically by simply running the tenancy in a system that dates things. The ledger is a by-product of recording payments as they arrive. The repair history is a by-product of handling requests in one thread. The chronology is a by-product of both.
The two-part rule about notices
The most expensive gap we heard in our landlord interviews was not a missing notice. It was a notice that had genuinely been served, by a landlord who could not prove the service. The notice and the proof that it was received are two separate records, and only keeping the first is the most common way a well-run tenancy becomes an unprovable one.
This is worth internalising as a habit rather than a rule: whenever you serve something, the question is not whether you sent it, but what you would show someone in nine months to demonstrate that you sent it, and when.
Build the record before you need it
Nobody assembles a good evidence package under a 14-day deadline. What actually happens is that people who kept an ordered record all along print it, and people who did not spend a fortnight excavating their phone and still arrive with gaps.
The practical test is simple, and you can run it today without a dispute in sight: pick a month from last year and try to produce, in ten minutes, what rent was paid and when, what repairs were reported, and what you served. If you cannot, the problem is not that you failed to document your tenancy. It is that your documentation is in six places.
Keep the record without thinking about it
Propsynk keeps leases, rent, deposits, maintenance and notices in one dated record, so the paper trail is a by-product of running the tenancy.
Related: Rent tracking · Maintenance · All guides