The calendar objection, answered
The clock starts without you.
A tenant reports damp at 11pm on a Friday. Nobody reads it until Monday. The statutory deadline began on Saturday — and it does not care that the office was shut.
The objection is a good one, and it deserves a straight answer: anyone can put a reminder in Google Calendar for free. If the pitch were reminders, the pitch would lose. Calendars are excellent at reminders. They are free, they already work, and you already have one.
So the claim has to be narrower than “we help you remember”. It is this: a calendar tells you what to do. It cannot tell anyone else what you did. You find out the difference on the one day you cannot afford to.
Five things people say they can just do
What each one actually gives you.
| “I can just…” | What it actually gives you | What the court, the council or the DWP asks for |
|---|---|---|
| Put the gas safety date in Google Calendar | Proof that you intended to book an engineer | The certificate, its issue date, and evidence you gave the tenant a copy within 28 days |
| Keep a spreadsheet of reminders | A file anyone can edit afterwards, with no record of when a row was written | A contemporaneous record. Anything retrospectively editable carries close to no weight once the other side's solicitor asks when it was created |
| Search my email and WhatsApp when I need it | Fragments across four systems and your memory | One bundle — chronological, dated, indexed — usually against a deadline you did not choose |
| Write up the support notes at the end of the week | A reconstruction | Time-stamped, named-worker-attributed notes written at the time. This is the specific thing housing-benefit clawback turns on |
| Ask my letting agent for the file | Whatever they happened to keep | The full trail — and if the agent kept it in another system, there is no export shaped like a court bundle |
The sharpest version of the point
A deadline that starts itself.
Under SI 2025/1042, a social landlord who becomes aware of a reported hazard has 10 working days to investigate, 3 further working days to issue a written summary of findings, and 5 working days to make the property safe. An emergency is 24 calendar hours.
The working-day clocks begin the day after awareness and exclude weekends and bank holidays. The 24-hour emergency clock does not — it is calendar hours, and it runs through the weekend.
Nothing in that sentence requires anyone to have opened the message. Awareness is the trigger, not attention. A calendar entry cannot start on your behalf, and it cannot afterwards evidence the hour the report arrived, the channel it came in on, or what was done in response.
Scope, stated honestly. These clocks bind social landlords today — section 10A applies to social-housing leases rather than licences. If you let privately, you are preparing for a standard rather than meeting one. PropFlow starts the statutory clocks automatically where they are statutory, and tracks the same response trail everywhere else.
Why this is credible
You do not keep the record. It keeps itself.
The mechanism is the part worth saying out loud, because it is what makes the promise possible rather than aspirational. The tenant messages on WhatsApp and it is triaged, threaded and timestamped. The job is dispatched and the visit and the photos are logged. The certificate is uploaded, the dates are read off it, and the reminder chain is stamped.
None of that is extra work. It is the work — captured as it happens, in a form that can be handed to somebody else. That is the thing a calendar structurally cannot do, and it is the entire reason the record exists on the day you need it.
A calendar is a plan for the future. A record is what you have afterwards.
See what the record looks like when it builds itself.