.png){kind=logo}
Somewhere in retrofit delivery this week, an engineer's van has broken down, or an installer has called in sick, and a resident who took a day of annual leave to wait in doesn't yet know their appointment isn't happening. The breakdown doesn't decide how that day ends. What decides it is whether anyone calls to say so before the resident finds out for themselves, hours later, by ringing to ask where everyone is.
That distinction, telling someone quickly versus letting them find out, is nearly the entire skill of delivering bad news gently. It sounds too simple to be a genuine capability gap. Our research into communication in domestic retrofit found it's one of the most consistently avoided conversations in the sector, and one of the most consequential.
It's tempting to treat proactive bad-news calls as a nice-to-have, the kind of thing a well-resourced team does when they have spare capacity. That framing gets the economics backwards.
A resident who is told about a delay can rearrange their day. A resident who isn't told loses the entire day waiting for someone who was never coming, and the identical underlying cause, a broken-down van, a sick engineer, generates two completely different outcomes. One is a minor inconvenience, absorbed and forgotten. The other becomes a formal complaint, an escalation, sometimes a resident who disengages from the rest of the programme entirely.
Retrofit programmes run on long timelines with plenty that can and does go wrong: engineers, weather, deliveries, funding rule changes, subcontractor issues. Almost none of it is within a frontline team's control. What is within their control, every time, is whether the resident hears about it from them, proactively, or has to chase it down. That single choice, not the underlying problem, is what most residents are actually reacting to when they complain about "poor communication."
The pattern across the organisations that do this well has little to do with cleverness or a particularly good script. What matters is speed and honesty, applied even when the news is uncomfortable to deliver.
James Bishenden, Admin Project Manager at CCS, described a team member who had to call a resident to cancel an appointment that had already fallen through twice before. She dreaded making the call. She made it anyway, immediately, before the resident had any other way of finding out. The resident was angry at first, reasonably, given the history. Then she recognised it wasn't the caller's fault, and ended up praising the team for the honesty rather than filing a complaint about a third wasted day.
The same instinct scales up beyond individual conversations. At Equans, when a delivery of materials ran late on one project, Tony Doyle, Head of Customer Care for People & Communities South, didn't let his team distance the business from the supplier. Taking direct ownership, rather than explaining that it was technically someone else's fault, earned more trust from residents than any accurate but defensive explanation would have. Residents aren't asking contractors to be infallible. They're asking to be told, honestly, by someone willing to own the answer.
There's a version of this that sticks as an organising principle for the whole sector. As James puts it:
"One thing we're never going to get complaints about is a lack of communication."
Complaints about missed appointments or delays, yes, those happen regardless of how well a team communicates. But nobody should be able to say they weren't told.
If the logic is this straightforward, why does the avoidant version keep happening?
The honest answer is fear, not laziness. People who dread making a bad-news call are usually anticipating the same anger the resident would eventually express anyway, and freezing rather than facing it early. That fear is entirely understandable and completely counter-productive: the anger a resident feels on being told immediately is almost always smaller than the anger they feel after hours of being left to wonder.
There's also a confidence gap that has nothing to do with knowing what to say. Most people know, intellectually, that a proactive call is the right move. What they lack is the practised experience of making that specific kind of call, apologising for something outside their control, and staying on the line through the resident's initial reaction, without it going badly. Without that experience, the safer-feeling option is to delay the call and hope the problem resolves itself before anyone notices. It rarely does.
And under pressure, that same fear produces a worse failure mode: people who do pick up the phone sometimes agree to things they can't deliver, or confirm a measure is included when it isn't, simply to get off an uncomfortable call quickly. That short-term relief creates a much bigger complaint later, when the resident discovers the promise wasn't real.
Make the proactive call the default the moment a problem is known, not the moment a resident asks. If an installation team knows on a Tuesday morning that they can't make an appointment, the call should happen within the hour, not at the end of the day when it's convenient.
Separate the apology from the excuse. Residents generally aren't looking for a detailed explanation of why a van broke down. They're looking for an acknowledgement that their time mattered and a clear next step. Lead with both, and keep the explanation brief.
Build organisational ownership into the language teams use. Taking responsibility on behalf of the wider team or company, rather than pointing at a subcontractor or supplier, consistently earns more trust, even when the underlying fault genuinely does sit elsewhere.
And rehearse the call before it's needed for real. The confidence to deliver bad news calmly, without over-promising to escape the discomfort, is built the same way any other skill is: by practising it somewhere the stakes are low, before doing it live with a resident whose stakes are not.
It's worth measuring this deliberately rather than assuming it's happening. Call logs and complaint records already contain the evidence: how often is bad news reaching a resident before they have to chase it, and how long is the gap between a team knowing about a problem and a resident hearing about it. Most organisations have this data already. Very few are using it to see whether proactive communication is actually the norm, or the exception dressed up as one.
Every retrofit programme will have delays, cancellations and things that go wrong. None of that is avoidable at scale. What is avoidable is the gap between a problem happening and a resident finding out about it on their own terms rather than the team's.
This is one of six communication skills we explore in full in our research report, The Retrofit Conversation Gap, alongside the evidence for why organisations that treat it as trainable, rather than a matter of individual temperament, see measurably better resident outcomes. Download the report for the complete findings.
If you want your team to build the confidence to make that call proactively, before it's a live situation with a genuinely frustrated resident, we've developed interactive role-play scenarios that let them practise exactly this conversation and get personalised feedback on how they handled it. Get in touch to find out more.
