It’s 4:47 on a Friday. A buyer at Plot 14 emails sales about a snag.

Sales forwards it to the site manager, who’s already off-site. The site manager forwards it to aftercare on Monday. Aftercare asks sales for context. Sales has moved on to next week’s reservations.

By Thursday, the buyer’s emailed again. This time copying the MD.

You know this email chain. You’ve been on it. Probably this month.

The thing the chain reveals isn’t that any one person dropped the ball. It’s that there was no ball. No single record. No owner. No clock running. Just an inbox tennis match between three departments who all assumed someone else was holding it.

This article is about why that keeps happening, and what actually fixes it.

The handover problem isn’t a person problem

The first instinct, when one of these chains escalates, is to find out whose fault it was. Sales didn’t follow up. Site didn’t reply. Aftercare didn’t pick it up fast enough. Someone gets a quiet word.

But the same chain plays out next week, with different people. And the week after that. Because the problem isn’t the people in the chain. It’s the chain itself.

Look closely at the Plot 14 example. Every person in it acted reasonably. Sales received an email outside their team’s remit and forwarded it to the people who could act on it. The site manager was off-site and quite reasonably picked it up Monday morning. Aftercare needed context. Sales had already moved on. None of these are mistakes. They’re the rational responses of busy people who don’t have a system pulling them in the same direction.

What’s missing isn’t effort. What’s missing is a shared object. A single thing that everyone in the chain is looking at, updating, and accountable to. Without that, every handover is an act of trust. Trust that the email got through. Trust that the receiver knew it was their problem. Trust that they’ll do it before they forget. Trust is brittle. By Thursday, it’s broken.

Three departments, three systems, no shared truth

In most housebuilders, the chain isn’t just between three people. It’s between three systems.

Sales lives in a CRM, or a spreadsheet, or Outlook. Site lives in their own site reports, a WhatsApp group, and the project management software the build team uses. Aftercare lives in an inbox, a snagging sheet, and increasingly some kind of ticketing tool. The buyer lives in whatever email thread they last hit reply on.

When a buyer’s snag has to travel from one of those worlds to another, it goes by email. Email is the bridge between systems that don’t talk to each other.

The problem with email as a bridge is that it isn’t accountable. Once you forward, you’ve offloaded. There’s no record of who saw it, when, or what they did about it. The buyer’s snag exists, but only in the memory of whoever last touched it. The MD finding out on Thursday is the inevitable result of an information system where nothing is owned by anyone in particular.

What “one record, one owner, one clock” actually means

The fix to this is simpler than it sounds, but it has to be all three things at once.

One record. The snag, defect, or issue is logged in one place. Not in an email, not in a notebook, not in three different systems. One record, with a unique ID, a description, the plot it relates to, who reported it, and when. Everyone who needs to act on it is looking at the same record, with the same status.

One owner. The record has a named owner. Not “aftercare,” not “the site team.” A person. The owner can change as the work progresses (logged by sales, assigned to site, closed by aftercare), but at any given moment, one person is responsible for moving it forward. When someone asks “where’s Plot 14’s snag at?”, the answer is a name.

One clock. Every record has a timer running. Logged at 4:47pm Friday, currently sat at 23 hours unassigned, currently sat at 4 days awaiting site response. The clock isn’t there to shame anyone. It’s there so that ageing items become visible before the buyer escalates. A snag at three days needs a chase. A snag at seven days needs a senior call. A snag at fourteen days is the email to the MD waiting to happen.

The clock is the most overlooked of the three. Most builders have some form of “one record” (a snagging sheet, a spreadsheet) and most have some sort of “one owner” (an aftercare manager, a customer-care lead). What almost no one has is a clock that’s visible to all three departments at once. Without it, an item sits patiently in a queue until the buyer’s frustration becomes its alarm.

The hidden cost of the Friday chain

It’s easy to look at the Plot 14 chain and think the cost is the irritation of the MD getting a copied-in email on a Thursday. That’s the visible cost. There are three more, larger, hidden ones.

The buyer remembers. They might still complete. They might still recommend you to a friend. But they remember that nobody answered them for a week. NHBC star ratings, Google reviews, and the half-conversations buyers have in WhatsApp groups all draw from that memory. You don’t lose a single buyer over a 4:47pm chain. You lose half a star, half a referral, half a future reservation, repeatedly.

The team distrusts the process. When the inbox tennis goes wrong often enough, people stop relying on it. Sales starts ringing the site manager directly rather than emailing. Site starts CC’ing the MD pre-emptively to cover themselves. Aftercare starts working from screenshots. The process collapses into a thousand workarounds, each of which adds friction.

The data is unusable. Even if every chain eventually resolves, you can’t learn from them. The data is scattered across inboxes. You can’t see which plot types generate the most snags. You can’t see whether one site is slower than another. You can’t see whether aftercare is improving over the year. The information is there, but it’s locked inside emails.

The fix isn’t more discipline. It’s a different shape.

The honest reason the 4:47pm chain keeps repeating isn’t that the people in it are bad at their jobs. It’s that they’re being asked to do their jobs through email, in three different systems, with no shared truth.

The housebuilders who’ve fixed this didn’t hire more aftercare staff. They didn’t write a stricter SLA. They put every snag, defect, and issue into one place. One record. One owner. One clock. Sales can see it. Site can see it. Aftercare can see it. The buyer can see it.

When the buyer at Plot 14 emails at 4:47pm on a Friday, the snag is logged before anyone goes home. It has an owner by Monday morning. The clock has been running the whole time. By Thursday, the buyer isn’t writing to the MD. They’re watching their snag move through a system they can see for themselves.

It’s not magic. It’s just shape.