Prop-Pocket

5, 10 and 20 day Code deadlines: tenant complaints for landlords

Published 28 August 2026 by Prop-Pocket Team

Turn the Housing Ombudsman Code into a day to day complaints workflow. Meet the 5, 10 and 20 day deadlines, use copy ready templates, and keep audit ready...

5, 10 and 20 day Code deadlines: tenant complaints for landlords

Decorative title card illustration

Landlords must run a strict two-stage complaints process: acknowledge, log, investigate, and respond within the timescales set by the Housing Ombudsman's Complaint Handling Code. Miss those windows or bolt on an informal "stage zero" and you raise your Ombudsman risk sharply. Get the basics right and most disputes never leave your inbox.


TL;DR: - Landlords must log and respond to complaints within strict timescales, acknowledging within five days and providing full responses within ten days for Stage 1. - Oversight of complaints requires a designated person or role, a published policy, and reasonable adjustments for tenants with disabilities to ensure transparency and accountability. - Consistent complaint intake through a single channel is essential to prevent complaints from getting lost, delaying responses, or becoming Ombudsman cases. - Proper investigation, documented actions, and confirming resolution in writing are vital to avoid escalation or re-litigation of issues. - Automated logging, templated responses, and trend analysis tools aid compliance, reduce errors, and improve response times compared to manual or scattered processes.

Table of Contents

What the Complaint Handling Code requires

The Complaint Handling Code is statutory. It sets out a two-stage procedure, and it explicitly discourages landlords from inventing extra steps in between. An informal "stage 0" or an "early resolution" phase might feel helpful, but it delays a tenant's right to escalate and muddies your own complaints data.

Landlord recording tenant complaint digitally

The timescales are precise, not aspirational. Under the Housing Ombudsman's guidance, you must acknowledge a Stage 1 complaint within 5 working days and respond in full within 10. If the tenant escalates to Stage 2, you acknowledge within 5 working days again and issue a final response within 20.

Every landlord, however small, needs someone accountable for this. That does not necessarily mean a dedicated complaints officer on the payroll. It means:

Publishing that policy matters as much as having one. Tenants can only use their right to escalate if they know it exists.

How do you run a complaint-handling workflow day to day?

A workflow only works if every complaint enters through one door. Multiple inboxes, a WhatsApp number the property manager checks occasionally, and a paper form in the hallway all create the same problem: complaints get lost, and lost complaints become Ombudsman cases.

  1. Intake and acknowledgement. Log the complaint the moment it arrives, whatever channel it came through, and aim to confirm receipt promptly, signaling to the tenant that someone is actually listening.
  2. Triage by urgency. Not every complaint carries the same risk. Split incoming issues into rough bands: emergency (no heating, security breach, sewage leak), urgent (persistent leak, broken lock), routine (noise, minor repairs, service charge queries), and policy or legal (harassment, discrimination, illegal eviction threats). Each band gets its own internal SLA, tighter than the statutory deadline.
  3. Investigate properly. Speak to the tenant, check maintenance history, pull in contractors if needed, and get their account in writing. If a third party (an agent, a contractor, a neighbour) is involved, keep the investigation internal to your own process rather than creating a separate resident-facing stage for it.
  4. Act, and act visibly. Schedule the fix. If safety or habitability is at stake, put interim measures in place first, temporary heating, alternative access, immediate contractor attendance, and document them using a tenant safety responsibility checklist for landlords. That documentation is often what protects you later.
  5. Close the loop. Send a written resolution summary: what was found, what was done, what compensation or remedy (if any) applies. Ask the tenant to confirm in writing that the matter is resolved. A complaint isn't closed until they've said so.

Pro Tip: Treat "tenant confirms resolution" as a mandatory field in your process, not a nice extra. Closing the loop this way is one of the strongest ways to stop the same complaint resurfacing three months later as a Stage 2 escalation.

Recordkeeping, reporting and learning from complaints data

Your complaint file is your evidence in any dispute, so build it properly from day one. Each case record should capture the original complaint, every date (received, acknowledged, responded to, closed), all correspondence, contractor evidence and invoices, and the tenant's written confirmation of resolution.

The Code also requires something beyond individual case files: an annual self-assessment against the Complaint Handling Code, reported alongside your complaints performance data. That report should include:

Trend analysis is where this earns its keep. A cluster of complaints about one contractor, one property, or one recurring repair type tells you where the real problem sits, and it's rarely the tenant. Keep files organised well enough that, if the Ombudsman ever asks for evidence, you can produce it without a scramble.

Common pitfalls that trigger escalation

Most Ombudsman findings against landlords trace back to a small set of avoidable mistakes, not genuine disputes about facts.

Some complaints need to go beyond your own process entirely. Health and safety failures may warrant Environmental Health or council involvement; harassment or illegal eviction threats need legal advice immediately. Citizens Advice sets out the escalation route tenants are told to follow, so expect council or Ombudsman contact once your internal process is exhausted, and prepare your evidence accordingly.

Copy-ready wording for acknowledgement, updates and resolution

Standard wording saves time and keeps tone consistent, which matters more than it sounds. A defensive first reply can turn a routine repair complaint into a formal grievance.

  1. Acknowledgement. "Thank you for your complaint, reference [XXX], received on [date]. We've logged this as a Stage 1 complaint and will respond in full by [date, within 10 working days]. If you need to reach us in the meantime, contact [name/role]."
  2. Investigation update. "We're still investigating your complaint, reference [XXX]. [Brief reason for delay, e.g. awaiting contractor report]. In the meantime, we've arranged [interim measure] to address the immediate issue. We expect to respond fully by [date]."
  3. Resolution confirmation. "Following our investigation into complaint [XXX], we've [action taken/remedy offered]. Please confirm by [date] that this resolves the matter to your satisfaction, or let us know if you'd like to escalate to Stage 2."

Personalise each one with real dates and specifics before sending. Generic templates that skip the reference number or the actual timescale look automated in the wrong way, and tenants notice. Log every sent message against the case file. That confirmation line in the resolution template isn't decorative; it's the record you'll need if the tenant later disputes that the matter was settled.

Why most landlords still get this wrong

The instinct to smooth things over informally, a quick phone call, a verbal apology, an off-the-record fix, is understandable, but it's exactly what the Code is designed against. An unlogged phone call isn't a resolved complaint. It's a complaint with no evidence trail, which is the worst possible position if the tenant later escalates.

Vacant rental hallway showing maintenance details

Centralising intake changes the maths on this. When acknowledgements fire automatically the moment a complaint lands, and every message, repair job, and contractor note sits against the same property record, response times drop, and the audit trail builds itself rather than depending on someone remembering to file it. Dashboards that surface repeat issues by property or contractor turn your annual self-assessment from a guessing exercise into a five-minute pull of real data, and they make it obvious when one contractor is quietly generating a disproportionate share of your complaints.

None of this replaces judgment. But it removes the excuse of "we forgot to log it," which is where a surprising share of Ombudsman findings originate.

— Harv

Get your complaint process running properly with Prop-Pocket

Running a compliant two-stage process by memory and email folders is how landlords miss the 5-day acknowledgement window without even realising it. Prop-Pocket gives you a single place to log a complaint the moment it lands, timestamp it automatically, and track it against the Code's deadlines without building your own spreadsheet.

Prop-Pocket

The feature set covers what this article has walked through: templated responses you can personalise in seconds, a case history tied to the property record rather than scattered across inboxes, and reporting that pulls together the kind of trend data your annual self-assessment needs. The property overview dashboard also flags repeat issues at a glance, so a pattern of complaints tied to one contractor or one flat surfaces before it becomes a Stage 2 escalation. Your first property is managed free, with no card details required to start. Set up your account, load your first property, and see how much faster acknowledgement and closure become when they're not running through six different channels.

Sources

Recommended

Never miss a compliance deadline

Joinlandlords using Prop-Pocket to track certificates, manage repairs and stay compliant — for free.

Try Prop-Pocket Free

← Back to all articles