Skip to content
Hendl
GUIDES  /  MEETING THE COMPLAINT HANDLING CODE, EVERY…9 min read
Housing

Meeting the Complaint Handling Code, every time

H
Hendl
Editorial team · updated May 2026
9 min read

Most Code breaches aren’t judgement failures — they’re calendar failures. A stage-one response that’s a day late, an acknowledgement that never went, a stage two that started informally. The fix is to make the Code the process, not a checklist beside it.

01

Encode the Code once

Stage definitions, timescales, required content and escalation rights become the complaint case type’s template. Every complaint then runs against the same rules — and when the Code changes, you change one template, not a hundred habits.

02

Let agents run the clock

Acknowledgements go out on receipt, reminders escalate before deadlines rather than after, and extensions are recorded with reasons. Officers stop being diary managers and go back to being decision-makers.

03

Evidence by construction

Every communication, delay and decision is logged as it happens, so an Ombudsman request is an export, not an archaeology project. Teams tell us this changes how it feels to be inspected.

Take with you
Make the Code the case template, not a separate checklist.
Escalate before deadlines, never after.
If the file is complete by construction, inspection is an export.

See this working on your own casework. In weeks.

© 2026 Hendl Labs Ltd. All rights reserved.
Services AgreementPrivacy PolicyTrust Center