We recently asked over a hundred UK housebuilders the same question: what do you call it when something’s wrong with a plot after handover?

The answers split three ways.

42% call it a snag. 46% call it a defect. 11% call it an issue. A handful went their own way: “punch list item,” “remedial,” “non-conformance.”

It’s the kind of poll result that looks like a quirk of language. It isn’t. The word a business uses for the thing that’s gone wrong tells you a surprising amount about how that business handles aftercare, and how its buyers feel about the experience.

“Snag” is a builder’s word

Snag is the language of the site. It’s casual, low-stakes, almost affectionate. A snag is something you spot on a final walk-through and scribble on a clipboard. It’s a to-do, not a problem.

The 42% of builders who lead with “snag” tend to be the ones whose aftercare process grew organically out of their site management. The site manager is involved. The fix is usually quick. The customer is told “we’ll snag that for you” and the conversation moves on.

The risk with “snag” is that it can feel dismissive to a buyer who’s just moved into a £400,000 home and found their kitchen tap leaks. To them, it’s not a snag. It’s a problem with the most expensive thing they own.

“Defect” is a contract’s word

Defect is the language of the warranty. NHBC uses it. Building Regs use it. The legal documents the buyer signed all use it. It’s precise, slightly cold, and it carries weight. A defect implies a standard has not been met.

The 46% of builders who say “defect” are usually the ones whose aftercare is run by an admin or customer-care function rather than the site team. The paperwork is cleaner. The categorisation is sharper (warrantable vs. non-warrantable, structural vs. cosmetic). The buyer feels heard because their complaint has been given a serious name.

The risk with “defect” is that it can escalate things unnecessarily. Call a chipped skirting board a defect and the buyer starts wondering what else is wrong with the house.

“Issue” is a hedge

Only 11% use “issue,” and they tend to be the builders trying to thread a needle. “Issue” is neutral. It doesn’t promise a fix the way “defect” does, and it doesn’t trivialise the problem the way “snag” can.

In practice, “issue” usually means the builder hasn’t settled on a process. The same problem might be a snag on Monday and a defect on Thursday depending on who’s logging it.

Why the inconsistency costs you money

Here’s the thing the poll doesn’t capture: most builders don’t actually pick one. They use all three, interchangeably, across different parts of the same business.

The sales team logs a snag in their notes. Aftercare receives it as an issue by email. The site manager records it as a defect on the snagging sheet. Three words, three systems, one buyer waiting for someone to come and fix their tap.

The cost shows up in four places:

1. Reporting is a mess. You can’t measure what you can’t categorise. If the same problem has three names, your aftercare data is noise.
2. Buyers feel passed around. Every time the language changes, the buyer suspects they’re starting over.
3. Trends get missed. A recurring fault on a particular plot type only shows up in the data if it’s tagged consistently. Otherwise it hides in three different buckets.
4. The NHBC star rating takes the hit. Customer satisfaction scoring at one-year and two-year stages is sensitive to how complaints are handled, not just whether they’re handled.

Pick a word. Then pick a process.

There isn’t a “right” answer to snag vs defect vs issue. There’s only a right answer for your business, and the right answer is the one everyone in the business uses.

If you’re a smaller builder where the site manager runs aftercare, “snag” probably fits. If you’re a regional developer with a dedicated customer-care function, “defect” probably fits better. The word matters less than the consistency.

What matters more is what happens after the word is logged:

• Is it in one system, or three?
• Can the buyer see its status without having to ring up and ask?
• Can the site team mark it resolved from the plot, on their phone, without writing it up later?
• Can the customer-care manager see, at a glance, every open item across every plot?

Aftercare doesn’t fail because builders don’t care. It fails because the snag, defect or issue lives in someone’s head, or someone’s notebook, or someone’s inbox, and the buyer is the one chasing it.

The fix isn’t a new word. It’s a single place where they all live.