What Is a Complaint Handling Failure Notice? How Small Providers Can Avoid One

For small registered providers, the phrase "Complaint Handling Failure Notice" tends to surface at exactly the wrong moment — after a deadline has been missed, when the Ombudsman is already involved. Understanding what triggers one, and the difference between a Notice and an Order, is the first step to making sure your organisation never receives either.

This post explains both mechanisms in plain English and sets out the practical steps that keep small teams on the right side of the Complaint Handling Code.

For the Code itself and its deadlines, see The Housing Ombudsman Complaint Handling Code: A Plain-English Guide.

Notice vs Order: Two Different Things

The Housing Ombudsman has two enforcement mechanisms that are frequently confused. They address different failures.

Complaint Handling Failure Notice (CHFN)

A Failure Notice is issued where a landlord:

• does not respond to a complaint within the Code's timescales, or
• fails to meet the Code's requirements — including the annual submission obligations (the annual complaints performance and service improvement report and self-assessment).

In other words, a Failure Notice is about missing the Code's own rules: the deadlines and the submissions.

Complaint Handling Failure Order (CHFO)

A Failure Order is issued where a landlord:

• does not provide information the Ombudsman has requested during an investigation, or
• does not comply with orders the Ombudsman has made after an investigation.

A Failure Order is about non-cooperation with the Ombudsman's process — not following the investigative procedure or ignoring orders, rather than missing the Code's deadlines.

The simple way to remember it: a Notice is for breaking the Code's own requirements; an Order is for not cooperating with the Ombudsman. Both are published, and both signal a compliance problem that the Regulator of Social Housing can take into account.

What Triggers a Failure Notice in Practice

For a small provider, the realistic routes to a Failure Notice are mundane, not dramatic:

• A missed response deadline. A Stage 1 complaint that slips past the 10-working-day response window, or a Stage 2 final response that misses the 20-working-day window, because the deadline was tracked by hand and the team was stretched.
• An overlooked acknowledgement. Failing to acknowledge a complaint within 5 working days at either stage.
• A late or missing annual submission. Not producing the annual complaints performance and service improvement report, or not getting the self-assessment approved by the governing body in time.

None of these requires a catastrophic failure. They require only a tracking gap — exactly the gap that opens when statutory deadlines are managed in fragmented spreadsheets and inboxes.

Why Small Providers Are Most Exposed

Larger providers usually have dedicated complaint-handling teams, case-management systems, and governance calendars built around the submission cycle. A small registered provider often has one compliance lead handling complaints alongside repairs, Awaab's Law deadlines, and everything else.

That concentration is the risk. When one person is tracking complaint-response deadlines and Awaab's Law repair deadlines across separate spreadsheets, a single period of leave, a busy month, or a lost email can be enough to miss a deadline — and a missed deadline is a Failure Notice trigger. The enforcement environment is not lenient toward small organisations: the Ombudsman applies the Code regardless of size.

The same enforcement pressure runs through the repairs side. For how missed Awaab's Law deadlines surface through litigation, the Ombudsman, and the Regulator, see Awaab's Law Enforcement: What Ombudsman Severe Maladministration Findings Mean for Small Providers.

How to Avoid Both

Avoiding a Failure Notice or Order is a matter of system, not heroics:

1. Track every complaint deadline automatically. Acknowledge within 5 working days, respond within 10 (Stage 1) or 20 (Stage 2) working days of acknowledgement. Calculate these against bank holidays rather than counting by hand — the deadline calculator shows how working-day windows fall.
2. Flag at-risk complaints before they breach. A "two working days remaining" alert lets the team act; an "overdue" alert is too late.
3. Keep the annual cycle on the calendar. Schedule the annual report and self-assessment, including governing-body approval, well ahead of the submission window. Board approval cannot be rushed.
4. Document every extension. The Code permits an extension of no more than 10 working days where complexity justifies it, with the reason explained to the resident. Record the justification each time.
5. Keep a clean audit trail. If the Ombudsman requests information during an investigation, being able to produce a complete, dated case record promptly is what keeps a Notice from escalating into an Order.

How HazardClock Fits

A Failure Notice almost always traces back to a tracking gap — a deadline that was not calculated, flagged, or recorded in time. HazardClock is being built so small providers track complaint-handling deadlines with the same working-day engine and at-risk alerting that handle Awaab's Law repair deadlines, with a clean audit trail ready for any Ombudsman request.

Join the waitlist to be notified when the full tracker launches.

This is general guidance for UK registered providers and social landlords, not legal advice. Refer to the current Complaint Handling Code and the Housing Ombudsman's published enforcement guidance for the authoritative position.

Sources

• The Complaint Handling Code — Housing Ombudsman
• Complaint Handling Code 2024 — Housing Ombudsman
• Complaint Handling Code becomes statutory — Housing Ombudsman