top of page

Download Your Ultimate New Build Snagging Checklist

  • barbarosdenlisoz
  • Apr 7
  • 3 min read

Updated: 4 days ago

When Should You Report Snags to Your Developer? (UK Guide)


One of the most common questions homeowners have with a new build is:


“When should I actually report my snags?”


There’s no single “perfect” moment, and in reality, most people end up reporting snags at multiple stages. Understanding when and how to do it properly can make the whole process smoother — and help avoid unnecessary delays or frustration.


When Can You Report Snags?


There are typically three key stages where snagging and reporting can take place.


1. Before completion (pre-handover)

This usually happens during a home demonstration or pre-completion visit.

  • You can raise obvious issues before legally completing

  • The developer may be able to fix some items before you move in


However:

  • Time is often limited

  • Not everything will be visible at this stage


👉 Think of this as your first pass, not your only opportunity.


2. Shortly after moving in

This is when most homeowners build their main snagging list.

Once you’re living in the property:

  • You start using everything properly

  • Lighting conditions change

  • Day-to-day use highlights issues


Common examples:

  • doors catching

  • uneven finishes becoming more noticeable

  • plumbing or heating issues


👉 This is typically the most important stage for reporting snags.


3. During the defects period (usually 2 years)

Most new build homes come with a defects period, often around two years.

This allows you to report:

  • issues that develop over time

  • shrinkage cracks

  • defects that weren’t obvious earlier


👉 It’s important to review your property before this period ends, as it may be your final opportunity to raise certain issues.


Should You Send One List or Multiple?


In theory, one clear snagging list sounds ideal.

In reality:

  • most homeowners identify issues over time

  • additional snags appear after moving in

  • repairs don’t always happen all at once


This often leads to:

  • multiple emails

  • updated lists

  • confusion over what’s been addressed

👉 There’s nothing wrong with reporting snags more than once — but how you manage that process matters.


How Developers Typically Deal With Snags


Understanding how developers work can help set expectations.


In many cases:

  • snags are grouped and dealt with in batches

  • different trades may return at different times

  • some issues are prioritised over others


It’s also common for:

  • repairs to require follow-up visits

  • items to be marked as “complete” but need re-checking


👉 This is where a clear record becomes important.


Common Mistakes to Avoid

A lot of frustration comes from how snags are reported, not just what is reported.


Sending multiple unstructured emails


Issues get lost or duplicated, making it harder for developers to track.


Being too vague


For example:

“Wall damaged”

Instead of:

“Visible dent and uneven paint finish on wall beside window”

Not including photos


Photos provide clarity and reduce back-and-forth.


No clear record of progress


It becomes difficult to know:

  • what’s been raised

  • what’s being worked on

  • what’s actually resolved


The Most Effective Way to Report Snags


The goal is simple:


Make it as easy as possible for your developer to understand and work through your list.

A good approach is to:

  • group snags by room

  • use clear, factual descriptions

  • include photos for each issue

  • keep everything in one place

  • update your list as things progress


This creates a much clearer picture than a chain of emails or messages.


Managing Snags Over Time


Snagging isn’t just about the first list — it’s an ongoing process.


As repairs happen, it helps to:

  • keep a record of updates

  • note when work has been carried out

  • track which items are still outstanding


This becomes especially useful if:

  • issues need to be revisited

  • multiple contractors are involved

  • you’re approaching the end of your defects period


A Practical Approach


Some homeowners choose to manage this manually, while others prefer a more structured system.


If you’re doing it yourself, the key is consistency.

  • keep everything organised

  • avoid scattered communication

  • maintain a clear record from start to finish


👉 If helpful, you can download our snagging checklists or use SnagClear to record issues, add photos, and generate structured reports as your list develops.


Final Thoughts


There’s no single “right” time to report snags — most homeowners will do so at multiple stages.


What matters more is how clearly and consistently those issues are recorded and managed.


Taking a structured approach can make the process far easier to handle and help avoid unnecessary confusion or delays.


SnagClear is designed to support that process — helping you keep everything organised, clear, and easy to share with your developer from start to finish.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page