top of page

Can a Developer Refuse to Fix a Snag Because You Reported It Late?

  • barbarosdenlisoz
  • Aug 12
  • 7 min read

You find a problem in your new-build home, report it to the developer and get a frustrating response:


“That should have been reported within the first 7, 14 or 30 days.”


Does that automatically mean they can refuse to deal with it?


Not necessarily.


A short initial snagging window can be relevant to obvious cosmetic damage, where it becomes harder to prove when the damage occurred after you have moved in.


But that is different from a construction defect that may have existed from the day the home was built and only became apparent months later.


There is also another deadline homeowners need to be aware of: the initial two-year defects or builder responsibility period commonly found in UK new-build warranty arrangements.


If you find a potential defect during this period, report it promptly and keep evidence of when you did so. This could become important if the developer does not resolve the problem and you later need to approach your warranty provider.








Can a developer set a 7, 14 or 30-day snagging deadline?

Developers can ask homeowners to report snags within a particular timeframe.


This is especially understandable for obvious cosmetic damage, such as:

  • scratched glazing;

  • chipped sanitaryware;

  • damaged flooring;

  • dents to kitchen units;

  • or marked finishes.


If you report a scratched bath 18 months after moving in and have no earlier photographs, it may be difficult to establish whether the damage existed at completion.

But that does not necessarily mean the same short deadline should apply to every construction defect.


Some problems simply cannot reasonably be discovered during the first few days in a new home.


What if the problem only becomes obvious months later?

A defect can exist from construction without being immediately visible.


For example, problems may only become apparent after:

  • prolonged heavy rain;

  • colder winter weather;

  • regular use of the heating;

  • materials drying out;

  • repeated operation of doors or windows;

  • or simply living in the property for longer.


Imagine you discover a section of an external wall is unusually cold 14 months after moving in. Further investigation suggests insulation may be missing.


You did not know about the problem at completion, but the insulation would still have been installed — or not installed — during construction.


Now compare that with a kitchen worktop that was fine when you moved in but was accidentally chipped 14 months later.


Both problems are reported after 14 months.

But their origins are completely different.


The important question is therefore not simply:


“How long have you lived there?”


It is also:


“Is this likely to be a construction defect, or something that happened afterwards?”



IMAGE SUGGESTION 2 — HERE

Split graphic:

DISCOVERED LATERMissing insulation / leaking windowMay have existed from construction

vs

HAPPENED LATERChipped worktop / accidental damageMay have occurred during occupation




Why the two-year defects period matters

Most homeowners will hear the first couple of years described as the two-year defects period, although the formal terminology differs between warranty providers.


You may instead see phrases such as:

  • builder warranty period;

  • defects period;

  • defects insurance period;

  • developer liability period;

  • or after-sales period.


Major UK warranty arrangements including NHBC, LABC Warranty, Premier Guarantee and Build-Zone commonly distinguish an initial period of around two years from the longer structural insurance cover that follows.


The exact wording, responsibilities and notification requirements vary, so always check your own warranty documents.


The practical point is much simpler:


If you discover a potential defect during this period, report it promptly.


Do not deliberately wait until the two-year date approaches.


Keeping evidence that the developer was notified within the relevant period may be important if:

  • the problem remains unresolved;

  • repair attempts fail;

  • responsibility is disputed;

  • or you later need to seek assistance from your warranty provider.


Depending on your policy, notification during the relevant period can affect whether the warranty provider may subsequently be able to help.



Does reporting something within two years mean the developer has to fix it?

No.


The two-year period is not an automatic guarantee covering everything that goes wrong with your home.


A developer may have reasonable grounds for rejecting an item.

For example:


Wear, maintenance or deterioration

Homes require maintenance and some materials deteriorate through normal use.


Accidental or homeowner damage

Damage that occurred after occupation is different from defective construction.


The item may not actually be defective

Something may look unusual while still complying with the applicable specification, manufacturer requirements or accepted construction tolerances.


Another warranty may apply

Some appliances and components are covered separately by manufacturers.


There may not be enough evidence

This is particularly relevant to cosmetic damage reported long after moving in.

So the fact that you reported something within two years does not automatically make the developer responsible.


It does, however, create a record that the issue was raised during that period.



What if you reported the snag within two years but it still isn't fixed?

Keep the original evidence showing when you first reported it.


A problem might be reported at month 18 but still be outstanding after the two-year date because of:

  • delayed appointments;

  • unsuccessful repairs;

  • contractor availability;

  • repeated investigations;

  • or slow aftercare.


The fact that time has passed since you originally reported the issue does not change the date you first notified the developer.


Keep copies of:

  • the original snag report;

  • photographs;

  • emails;

  • developer portal submissions;

  • repair appointments;

  • and photographs after attempted repairs.


Recent Consumer Code for Home Builders adjudication decisions have also highlighted the importance of dealing properly with issues that were raised during the relevant after-sales period rather than simply treating them as finished because time subsequently passed.


Your exact position will depend on the warranty and consumer protection arrangements applying to your home, but the original reporting date can matter.






What should you do if the developer says “too late”?

Keep your response simple and factual.


1. Ask what deadline they are relying on

Is it an initial cosmetic snagging deadline, a warranty deadline or something else?

Ask them to explain.


2. Check your warranty documents

Confirm:

  • your warranty provider;

  • when the initial defects period ends;

  • the notification requirements;

  • and how unresolved defects should be escalated.


3. Find your original evidence

Check emails, photographs, previous snag reports, developer portals and repair appointments.


You may already have evidence that the problem — or an earlier symptom of it — was reported.


4. Ask why the item has been rejected

If the response is simply “too late”, ask whether the developer considers it:

  • cosmetic damage;

  • maintenance;

  • wear and tear;

  • homeowner damage;

  • within tolerance;

  • or otherwise outside their responsibility.


A clear reason is much easier to assess than a one-line rejection.


5. Escalate if necessary

If aftercare is getting nowhere, check the developer's complaints procedure, your warranty provider's process and any consumer code or ombudsman scheme applying to your home.



Good records make disputes much easier

One of the biggest problems homeowners face is that defect information ends up scattered everywhere.


There may be photographs in your camera roll, an old email to aftercare, contractor appointments in text messages and no clear record of what remains outstanding.


For each snag, try to keep:

A clear description - What is actually happening?

The exact location - Which room and where within it?

Photographs or video - Particularly useful for intermittent defects.

The date you noticed it

The date you reported it

Repair history - What was attempted, when, and whether it worked.


The objective is not to create a huge evidence file for every minor snag.

It is simply to make sure important information does not disappear.


Record and track your snags with the SnagClear App

The SnagClear App was built to make this easier for new-build homeowners.


You can photograph defects as you find them, organise them by room, add descriptions and create a clear PDF report to send to your developer.


You can then continue tracking the issues afterwards, so you have a clearer record of what has been repaired and what remains outstanding.


That becomes particularly useful as you approach the end of your initial defects period and need to know which problems are still unresolved.


Record. Report. Track.


Use SnagClear on iPhone to keep your new-build defects organised from discovery through to repair.



Not sure whether the developer's rejection is reasonable?


Sometimes the difficult part isn't getting a response.

It is working out whether that response actually makes sense.


Your developer might say a problem is:

  • maintenance;

  • normal wear;

  • within tolerance;

  • caused by condensation;

  • homeowner damage;

  • or outside their responsibility.


That may be reasonable — but if you're unsure, you may want an independent view before deciding what to do next.


SnagClear Independent Review

The SnagClear Independent Review Service can review the information you have, including photographs, your description of the issue and the developer's response.


The aim is to provide a neutral, independent assessment of the information available, helping you understand whether the developer's position appears reasonable and what practical next steps may be worth considering.


It can be particularly useful before spending money on specialist investigations or escalating a relatively straightforward dispute.





Frequently asked questions


Can a developer insist cosmetic snags are reported within seven days?

They may set a short deadline for obvious cosmetic damage because establishing when damage occurred becomes more difficult after occupation.


That does not necessarily mean the same deadline applies to every construction defect discovered later.


I found a defect 18 months after moving in. Should I report it?

Yes. If you think it could be a construction defect, report it promptly rather than waiting for the two-year point.


Does my ten-year warranty cover ordinary snags for ten years?

Generally, no.


The initial builder or defects period and the longer structural warranty period are usually different forms of protection.


Check your own policy for the exact terms.



The key thing to remember

Missing a developer's initial 7, 14 or 30-day snagging deadline does not automatically mean every defect discovered afterwards is your responsibility.


Some construction problems take months to become apparent.

But don't delay reporting them.


If you discover a potential defect during the initial two-year defects or builder responsibility period:

Record it. Photograph it. Report it promptly. Keep the evidence.


That gives the developer an opportunity to investigate and leaves you with a much clearer record if you later need to use their complaints process or approach your warranty provider.


And if the only response you receive is:

“Too late.”

Ask them to explain why.


 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page