What Is a Snagging List? (And How to Write One That Gets Results)

barbarosdenlisoz
Apr 27
3 min read

If you’ve recently bought a new build home, you’ve probably heard the term “snagging list”.

But what exactly is it — and more importantly, how do you create one that actually gets your developer to take action?

This guide explains:

What a snagging list is
What should be included
How to structure it properly
How to improve your chances of getting issues resolved

🧠 What is a snagging list?

A snagging list is a record of defects, unfinished work, or poor-quality finishes identified in a new build home.

These issues (known as “snags”) are typically reported to your developer so they can be inspected and corrected.

Snags can include:

Cosmetic defects (paint, finishes, sealant)
Installation issues (doors, windows, fittings)
Functional problems (drainage, heating, ventilation)

👉 Snagging Guides

🕒 When is a snagging list used?

Snagging lists are commonly created:

Before completion (pre-handover inspection)
Shortly after moving in
During your 2-year developer warranty period

👉Snagging a New Build Home: When to Do It and What to Look For

⚠️ Why your snagging list matters

A poorly structured snagging list can lead to:

Delays in getting issues resolved
Miscommunication with your developer
Items being missed or ignored

A clear, structured list makes it easier for:

Developers to understand the issue
Contractors to locate and fix it
You to track progress

📋 What should be included in a snagging list?

Each snag should include:

1. Location

Be specific:

Room name
Wall, ceiling, floor, or feature

Example: “Kitchen – wall above worktop near window”

2. Description of the issue

Clearly describe what you can see — avoid vague wording.

❌ Poor: “Bad finish”

✅ Better: “Uneven paint finish with visible roller marks and patchiness in natural light”

3. Supporting photos

Photos help:

Show the issue clearly
Reduce disputes
Speed up resolution

Take:

Close-up photo
Wider context photo

4. Severity (optional but helpful)

You can group issues as:

Minor (cosmetic)
Moderate (noticeable but not urgent)
Major (affecting function or safety)

🧱 Example snagging list entry

Here’s what a good entry looks like:

Room: Bathroom Location: Wall behind basin Issue: Uneven tile alignment with inconsistent grout lines. Tiles appear misaligned when viewed straight on.

🧠 How to write a snagging list that gets results

This is where most people go wrong.

✅ Be specific

Avoid:

“Scratched wall”

Use:

“Scratch approximately 100mm long to painted wall, visible at eye level near door frame”

✅ Keep it neutral and factual

Don’t:

Assign blame
Use emotional language

Do:

Describe what you can see

✅ Group issues by room

This makes it easier for:

Site teams
Contractors

👉 It also keeps your list organised and easier to track.

✅ Use clear formatting

A messy list = slower response.

Use:

Bullet points
Consistent structure
Logical grouping

📱 Make it easier with SnagClear

Manually writing snagging lists can quickly become messy and difficult to manage.

SnagClear helps you:

Log issues room by room
Add photos instantly
Keep everything structured
Generate a clear, professional-style report

Download SnagClear App

Download, add snags and generate a preview report for free, before unlocking full report.

⚠️ Common mistakes to avoid

1. Being too vague

Developers can’t fix what they don’t understand.

2. Not recording issues properly

Verbal comments are easily forgotten.

3. Decorating too early

Painting or altering surfaces can:

Make defects harder to evidence
Lead to disputes about responsibility

When Is the Right Time to Paint Your New Build Home for Best Results

4. Not keeping a record

Without a clear record:

Issues may be missed
Progress becomes difficult to track

🔄 What happens after you submit a snagging list?

Typically:

Developer reviews your list
Contractors are instructed
Issues are inspected and addressed
Items may need revisiting

👉 This is where ongoing tracking becomes important.

📋 Final thoughts

A snagging list isn’t just a list — it’s your main communication tool with your developer.

The clearer and more structured it is:

The easier it is to resolve issues
The less back-and-forth you’ll have
The better your overall outcome

📱 Keep your snagging organised