Skip to content
HazardClock

Complaint Handling Code Self-Assessment: What Small Housing Providers Need to Submit

By Crocker Digital Ltd · Published 24 June 2026

For small registered providers, the annual Complaint Handling Code self-assessment is one of those obligations that is easy to underestimate until the submission window arrives. It is not a quick form. Since the Code became statutory in April 2024, the self-assessment is a legal requirement, it must be approved by your governing body, and it has to be grounded in real complaint-handling data — not a best-guess narrative written the week before the deadline.

This post walks through what the self-assessment actually requires, the evidence that stands up to scrutiny, and the pitfalls that most often trip up small teams.

For the full Code, including the per-complaint deadlines, start with The Housing Ombudsman Complaint Handling Code: A Plain-English Guide.

What the Self-Assessment Is

The Complaint Handling Code requires every member landlord to produce an annual complaints performance and service improvement report. That report must include a self-assessment against the Code — a structured confirmation that the landlord's complaint-handling policy and practice remain compliant with each of the Code's requirements.

Two features make it more than a formality:

  1. It is statutory. Since 1 April 2024 the Code is legally binding, so the annual self-assessment is a compliance obligation, not a voluntary disclosure.
  2. It must be approved by your governing body. The self-assessment must be reviewed and approved by the landlord's board (or equivalent) at least annually. That puts complaint-handling performance on the board's agenda and makes it a governance issue, not just an operational one.

What You Actually Have to Produce

The self-assessment works through the Code requirement by requirement. In practice, for each requirement you are confirming one of: compliant, not compliant, or partially compliant — with evidence and, where relevant, an improvement action. The areas it covers include:

  • Complaint definition and scope — that your policy defines a complaint in line with the Code and does not improperly exclude issues.
  • The two-stage process — that your process matches the statutory structure with the correct working-day deadlines (acknowledge within 5 working days; Stage 1 response within 10 working days of acknowledgement; Stage 2 acknowledge within 5 working days; Stage 2 final response within 20 working days of acknowledgement).
  • Accessibility — that residents can complain through multiple channels and are supported to do so.
  • Putting things right — that the policy provides for remedies and learning.
  • Performance data — actual figures on complaint volumes, response times against the deadlines, and outcomes.
  • Learning and service improvement — what the complaints told you and what you changed as a result.

The performance-data element is the one small teams most often struggle with, because it requires a year of accurate, dated records — not a reconstruction.

The Evidence That Holds Up

The difference between a robust self-assessment and a weak one is the evidence behind the claims. "We respond to Stage 1 complaints within 10 working days" is a claim. The evidence is a dated record, per complaint, showing the date received, the date acknowledged, the date responded, and the working-day gap between them.

If that record exists as a running log throughout the year, the self-assessment writes itself: you report your actual on-time percentage, identify the cases that breached, and describe what you changed. If the record does not exist — if it is scattered across an inbox, a spreadsheet someone updated intermittently, and a few memories — then the performance figures are guesses, and a guess is exactly what scrutiny exposes.

The same discipline that protects you on Awaab's Law repair deadlines protects you here: capture the timestamps as events happen, calculate the working-day windows consistently, and keep the record at case level. The deadline calculator shows how working-day calculation behaves around bank holidays — the same logic applies whether you are counting toward a repair deadline or a complaint-response deadline.

Common Pitfalls

Small providers tend to hit the same problems. Watch for these:

  1. Reconstructing data at submission time. If you are calculating your on-time response rate in the week before the deadline, from scattered sources, the figure will be unreliable and the underlying records will not survive an Ombudsman query.
  2. Treating extensions as routine. The Code allows an extension of no more than 10 working days where complexity justifies it, with the reason explained to the resident. If your data shows extensions used as a standard buffer, that is a finding against you, not a defence.
  3. Skipping board approval until late. The self-assessment needs governing-body sign-off. Boards meet on a fixed cycle; leaving approval to the last moment risks missing the submission window entirely.
  4. Confusing the report with the policy. The annual report and self-assessment are a point-in-time confirmation; the underlying policy and process have to be right all year. A polished report on top of a non-compliant process is the worst of both worlds.
  5. Ignoring the learning requirement. The Code expects service improvement, not just performance reporting. A self-assessment that records complaints but shows no resulting change reads as a box-ticking exercise.

Avoiding a Failure Notice

Failing to meet the annual submission requirement is one of the triggers for a Complaint Handling Failure Notice from the Ombudsman. The way to avoid it is structural, not last-minute: keep accurate records year-round, calculate deadlines consistently, schedule board approval into the governance cycle, and treat the self-assessment as the output of a system rather than a standalone task.

How HazardClock Fits

The self-assessment is only as strong as the running record behind it. HazardClock is being built so that the same per-case discipline that tracks Awaab's Law repair deadlines also produces the dated, working-day-accurate complaint-handling record that the annual self-assessment depends on — turning the submission from a scramble into a report you can generate from real data.

Join the waitlist to be notified when the full tracker launches. In the meantime, work through your case lifecycle with the compliance checklist.

This is general guidance for UK registered providers and social landlords, not legal advice. Complete your self-assessment against the current version of the Complaint Handling Code as published by the Housing Ombudsman.

Sources

Stop Tracking Deadlines in Spreadsheets

HazardClock calculates every Awaab's Law deadline automatically, sends countdown alerts before they expire, and builds an audit trail for investigations.

No spam. Unsubscribe any time. Privacy policy

Related Articles