How to Get Your Developer to Actually Fix Your Snags

If you want your developer to actually fix your snags, the trick is not chasing harder, it is reporting them properly the first time and building a record so solid that ignoring you becomes the harder option. New build snags not fixed on time are almost always a documentation problem, not a rights problem: you are entitled to have genuine defects put right during the builder period, but a vague verbal complaint gets deprioritised while a clear, dated, evidenced list gets actioned. This guide is the practical playbook - how to report snags so they land, how to document them so they cannot be waved away, how to set reasonable deadlines, how to chase without being a pushover, and exactly how to escalate when a developer goes quiet.

A quick, honest note before we start. This is practical guidance, not legal advice, and the exact rules depend on your warranty provider, your reservation agreement and which consumer code your developer signed up to. For the detailed explanation of your rights, the warranty phases and the formal escalation routes, read your new build rights alongside this. Here we focus on what to actually do.

Why snags get ignored (and why you have the right to a fix)

Developers are not usually being malicious when snags drift. They are juggling a lot of buyers, a backlog of remedial work, and trades who are busy on the next site. In that environment, the path of least resistance is to deal with whoever is loudest and clearest, and to let vague or poorly evidenced complaints slide to the bottom of the pile. A phone call that nobody logged, a half-described "the kitchen's not right" message, a snag reported to the site manager who has since moved on - these are the ones that get lost.

None of that changes your position. During the builder period - typically the first two years from completion, though always check your own warranty - defects in the build are the developer's responsibility to put right at no cost to you. You should not be paying tradespeople or claiming on your own home insurance for genuine new build defects. The right exists. The job is to make it easy for the developer to act on, and hard for them to dodge. We explain the full rights and warranty picture in your new build rights and the snagging period explained.

Report them properly the first time

Most of the battle is won or lost in how you first report. Get this right and a lot of the chasing never becomes necessary.

Send it to the right place

Send your snag list to the developer's customer service or aftercare team, not just the site manager. Site managers are focused on building, lists handed to them on site get misplaced, and the person you spoke to may not be there next month. The customer care team is the part of the business set up to log, track and action defects, and sending it there creates an official record. If you do also talk to the site manager, follow it up in writing to the customer care inbox so it is on file.

Put it in writing, always

Report by email or the developer's customer portal, never by phone alone. A phone call you cannot later prove is worth almost nothing if things go wrong. Email gives you a timestamped, undeniable record of what you reported and when - the audit trail that protects you and that every escalation route later relies on. If you do phone, follow up with an email summarising the call ("further to our call today, confirming I reported the following...").

Make it clear, itemised and evidenced

A good snag report is not a paragraph of grumbling. It is an itemised, numbered list where each entry has:

• A clear description in plain terms. "Deep scratch across the kitchen worktop, roughly 15cm, to the right of the sink" beats "worktop damaged" every time.
• A photo, ideally two - one close-up of the defect, one wider shot showing where it is in the room.
• A location - the room, and where in the room.
• A date - when you found it.

Group the snags by room, number them so you and the developer can refer to "snag 14" rather than re-describing it, and bundle the whole thing into a single, tidy document. A PDF is the standard format because it is easy to send, easy to file and hard to argue with. The clearer and more professional that first document looks, the more seriously it gets treated.

The single biggest lever: documentation

If there is one thing that decides whether your snags get fixed quickly or get argued over for months, it is the quality of your evidence. Every part of the system that can compel a developer to act - their own complaints process, your warranty provider's resolution service, the New Homes Ombudsman - runs on a paper trail. The strength of any complaint rests almost entirely on what you can show: dated photos, dated emails, the developer's acknowledgements (or the lack of them), and a clear record of each defect.

This is also your protection against the most common pushback, which is a developer suggesting you caused the damage after moving in. A photo dated within days of getting the keys settles that argument before it starts. It is exactly why thorough documentation from day one matters so much, and why you should never start fixing things yourself - a self-attempted repair muddies who was responsible and can undermine your claim.

What a bullet-proof record looks like, per snag:

1. A plain-English description of what is wrong.
2. Photos - close-up plus context shot.
3. A precise location - room, and a pin on a floor plan so there is genuinely no doubt where it is.
4. A date - when you found it.

Keep your own copy of everything, send it in a way that creates a record, and keep the list live as items are fixed (or not). For the full method, see how to document snags so they can't be dismissed. The documentation is not busywork - it is the thing that turns your right to a fix into an actual fix.

Set reasonable deadlines and keep a paper trail

Once your list is in, do not leave the timeline open-ended. A polite, specific request for a response by a date keeps things moving and gives you a clean record of who is behind, without being aggressive.

A few principles:

• Ask for acknowledgement. A good developer confirms they have received your list. If you hear nothing within a few days, chase in writing. Under the New Homes Quality Code, developers signed up to it are expected to acknowledge a formal complaint quickly (the Code references a written acknowledgement within around five business days and a written "path to resolution" within about ten days), so a short wait for a reply is reasonable, but silence is not.
• Be realistic on the fix itself. Repairs take weeks rather than days. Trades get booked in batches, parts get ordered, and one visit often does not clear everything. Expecting same-week fixes for cosmetic snags sets you up for frustration. A reasonable ask is acknowledgement quickly, a plan within a couple of weeks, and the work scheduled and completed over the following weeks. Many developers work to a defects window measured in months.
• Prioritise safety items. Anything that is a genuine hazard - an electrical fault, a leak, no hot water - should jump the queue, and it is reasonable to flag those separately and ask for them to be treated as urgent.
• Log every interaction. Keep a simple running record: the date you reported, the date they acknowledged, what they promised, what they did, what is still outstanding. Every email saved, every call summarised in writing. This log is what makes escalation work later, because you can show exactly where and when things stalled.

How to chase professionally

When something stalls, how you chase matters. The goal is to be impossible to ignore and impossible to dislike - firm, factual, and on the record. Keep it in writing (email, not phone), reference your numbered list, state plainly what is outstanding and what you are asking for, and give a clear, reasonable timeframe for a response.

A simple structure that works for a chase email:

• Reference - "Further to my snag list sent on [date] (attached again for ease), and your acknowledgement on [date]."
• What is outstanding - "The following items remain unresolved: snags 3, 7 and 12 (see attached)."
• What you are asking - "Please can you confirm a date for these to be inspected and repaired."
• A reasonable deadline - "I would be grateful for a response by [date, e.g. within the next 7 days]."
• A calm close - no threats, no capital letters, just a clear expectation.

You do not need to mention escalation in early chases. Stay polite and proportionate. If you do reach the point of a formal complaint, you can reference your rights and the relevant code calmly and factually - escalating the formality of your language, not your temper, is what carries weight. A buyer with a tidy paper trail and a measured tone is exactly the buyer a developer (and later an Ombudsman) takes seriously.

Escalate step by step when they go quiet

If polite chasing is not working and legitimate defects are still not being fixed, you escalate - in order. The system expects you to climb the ladder one rung at a time, and skipping steps usually just bounces your complaint straight back. We cover the rights detail in your new build rights; here is the practical sequence.

Step 1: Raise a formal complaint with the developer

Stop "chasing" and start "complaining" - formally and in writing. Ask the developer to treat your message as a formal complaint under their complaints procedure, reference your warranty and (if it applies) the consumer code your developer signed up to, and attach your evidenced list. This starts an official clock. Under the New Homes Quality Code, the developer is expected to follow a set timetable: acknowledge it, send you a written path to resolution, then a fuller response, and if it is still not closed, an "eight-week" (around 56-day) letter. Keep copies of everything and note every date.

Step 2: Let the developer's process run to its end

Frustrating as it is, you generally have to let their formal complaints process run its course and get their final written response (or wait out the defined period without an adequate response) before the next route opens up. The escalation bodies will check that you gave the developer a fair chance first, so completing this step is what unlocks the rest. Under NHBC's framework, for example, you typically need to have completed the builder's process (or waited a set period without resolution) before NHBC's own service will step in.

Step 3: Use your warranty provider's resolution service

If you are not satisfied with the developer's final decision, or they have not responded in time, you can ask your warranty provider to step in. NHBC, for instance, offers a resolution/claims service once the builder's process is exhausted: in broad terms it contacts the builder, and if there is a genuine dispute it can investigate, issue recommendations and timescales for the remedial work, and ultimately arrange for the work to be done if the builder still does not act. Other providers (Premier Guarantee, LABC Warranty, Checkmate) have their own equivalents. This is the warranty's backstop role kicking in. Check your own provider's exact process in your warranty booklet.

Step 4: Escalate to the New Homes Ombudsman or your code's scheme

If your developer is registered with the New Homes Quality Board, you can take an unresolved complaint to the New Homes Ombudsman Service - free of charge - once you have been through the developer's process and the relevant waiting period has passed (the Code references being able to refer a complaint after 56 days from the complaint start date, within set deadlines). The Ombudsman can make decisions the developer has to act on, including requiring action or compensation. If your developer is instead under the older Consumer Code for Home Builders, that code has its own independent dispute resolution scheme you can use. Either way, the dated, evidenced record you have been keeping is the thing that wins it.

What not to do

A few mistakes can weaken an otherwise strong position. Avoid these:

• Do not rely on phone calls. If it is not in writing, it did not happen as far as any escalation is concerned. Always create a written record.
• Do not fix the snags yourself. A DIY repair on a genuine defect can hand the developer an argument that you caused or worsened the problem, and it muddies who was responsible. Report it and let them fix it.
• Do not sign anything off until you are genuinely happy. Handover and completion forms, and "snag closed" confirmations, are records. Take your time at handover, do not tick items as resolved that have only been partially fixed, and re-check each repair before you agree it is done. It is common for a fix to be incomplete or to create a new snag.
• Do not let it go quiet from your side. Open-ended silence works in the developer's favour. Keep a steady, dated, polite cadence of follow-ups so the record shows continuous, reasonable pressure.
• Do not withhold money or take drastic action on impulse. Withholding payment or threatening legal action early can backfire and is rarely the right first move. Work the proper process - it is more powerful than it looks, precisely because it builds the record an Ombudsman acts on.
• Do not lose your temper on the record. Angry, scattergun emails read badly later. Calm, factual and persistent is what wins.

Frequently asked questions

What if my developer just ignores my snag list?

Escalate in order, in writing. First raise it as a formal complaint under the developer's complaints procedure and let that process run to a final response. If you are not satisfied, or they do not respond in time, ask your warranty provider's resolution service to step in. If your developer is registered with the New Homes Quality Board, you can then take it to the New Homes Ombudsman; if you are under the Consumer Code for Home Builders, use that code's dispute scheme. Keep everything dated and evidenced. The full route is in your new build rights.

How long should a developer take to fix snags?

Realistically, weeks rather than days for the work itself, with acknowledgement much sooner. Developers signed up to the New Homes Quality Code are expected to acknowledge a formal complaint within a few business days and set out how they will resolve it within around ten days. The repairs themselves get scheduled in batches and can take several visits. Safety issues should be treated as urgent. Always check your own warranty and code for the specific timescales that apply to you.

Should I email or phone my developer about snags?

Email, or use the developer's customer portal. Phone calls leave no record you can later prove, and every escalation route depends on a written paper trail. If you do speak by phone, follow up immediately with an email summarising what was agreed so it is on file.

Can I withhold money or refuse to complete until snags are fixed?

This is risky and rarely the right first move - it can put you in breach and create more problems than it solves. The stronger approach is to document everything, snag thoroughly before completion where you can, and work the formal process and escalation routes, which are designed to compel a fix. If you are considering withholding payment or legal action, take proper advice first. See your new build rights for where you actually stand.

Does good documentation really make a difference?

Yes, more than anything else. Every body that can force a developer's hand - their complaints process, the warranty resolution service, the Ombudsman - decides on evidence. A clear, dated, photographic, itemised record gets your snags actioned faster and wins escalations; a vague verbal complaint gets deprioritised and is easy to dismiss. Documentation is the single biggest lever you have. See how to document snags.

The bottom line

Getting your developer to actually fix your snags comes down to making the right thing the easy thing. Report properly the first time - to the customer care team, in writing, as a clear, itemised, photographed and dated list in a single PDF. Set reasonable deadlines and keep a running paper trail of every interaction. Chase professionally - firm, factual, on the record. And if they go quiet, escalate one rung at a time: the developer's formal complaints process, then the warranty provider's resolution service, then the New Homes Ombudsman or your code's dispute scheme.

The thread running through all of it is evidence. If you are buying or have just moved into a new build, for new build buyers ties this together with your rights, and new build snagging explained covers the wider process. When you are ready to build the record that does the heavy lifting, SnagPal is a free, offline, no-account iOS app that turns your photos and notes into the dated, developer-ready PDF that makes every one of these steps easier.