Reporting a suspected breach and what enforcement can do

If a neighbour is building something that looks wrong, the useful first step is to find out whether it is a breach at all, because most of what looks unauthorised turns out to be permitted development or covered by an approved plan. Where there really is a problem, the way to report a planning breach is in writing, with dates and photographs, to the council's planning enforcement team.

What comes next is the part people find hardest to accept. Enforcement is discretionary. A council that finds a breach is not obliged to take action, and it will only do so where it judges action to be expedient. Understanding that from the start makes the process much less frustrating.

What counts as a breach

A breach of planning control is defined in section 171A of the Town and Country Planning Act 1990 as carrying out development without the planning permission required for it, or failing to comply with any condition or limitation attached to a permission.

That covers three recognisable situations:

• development with no permission at all, where permission was needed
• development built differently from the approved plans
• development that breaches a condition, such as working outside permitted hours, failing to plant the approved landscaping, or occupying a building before a required measure is in place

It does not cover a great many things people report. Boundary disputes, covenants, party wall matters, high hedges, noise from ordinary domestic activity, parking on a public road and the behaviour of builders on site are each handled by other regimes or not at all. Nor does it cover work that falls within permitted development rights, which allow a surprising amount without any application.

Before reporting, check the council's online planning register for the address. Comparing the approved drawings against what is being built answers most queries in ten minutes, and the article on following an application through the public register explains how to read what you find there.

How to report it usefully

A good report makes the officer's job easy. A vague one gets triaged to the bottom.

1. Give the full address of the site and, if the breach is on part of a larger property, mark it on a sketch or a printed map.
2. Say what you have seen, in plain factual terms. Describe the structure, the use or the activity rather than characterising it.
3. Give dates. When did the work start, when did you first notice the use, how often does the activity happen. For a condition breach, the dates and times are the evidence.
4. Attach dated photographs taken from your own property or from public land. Do not enter the site.
5. Quote the application reference and condition number if you have found them.
6. Give your name and contact details.

On anonymity: councils will usually accept an anonymous report, but they cannot come back to you for the detail that makes a case, and your evidence may be what the case needs. Most authorities will keep a complainant's identity confidential during an investigation, though it can become disclosable if the matter reaches an appeal or prosecution. Ask what their policy is before deciding.

Keep your own record. A dated log of noise, deliveries or working hours kept over several weeks is worth more than a single complaint, because a condition breach has to be evidenced as a pattern rather than an incident.

Why enforcement is discretionary

This is the part that surprises people. Parliament gave councils the power to enforce, not a duty. The decision to issue a notice is a judgement, and it is made by officers under delegated powers in the great majority of cases.

The reason is practical. A breach that causes no harm, or trivial harm, is not worth public money to pursue, and national guidance is clear that enforcement should be proportionate. A shed 200 mm too tall at the back of a large garden harms nobody. A two-storey extension built a metre closer to a boundary than approved may harm a neighbour considerably.

Councils publish enforcement plans setting out how they prioritise cases, and the piece on planning enforcement complaint priorities explains how those priorities typically work. Unauthorised work to a listed building, loss of protected trees, breaches affecting highway safety and development in the Green Belt usually sit near the top. Householder breaches with limited impact sit near the bottom.

The expediency test

When an officer decides whether to act, they are asking whether enforcement action is expedient having regard to the development plan and other material considerations. In practice that resolves into a short series of questions.

Would the development have been granted permission if it had been applied for? If yes, a notice is hard to justify, and the officer will usually invite a retrospective application instead. Is the harm material, or is it technical? Is the breach still within the relevant time limit for action? Is the harm proportionate to the cost and the human consequence of the action, particularly where someone lives in the building?

Time limits matter and they have changed. Historically the position in England was four years for building and engineering operations and for change of use to a single dwellinghouse, and ten years for other changes of use and for breaches of condition. The Levelling-up and Regeneration Act 2023 provides for a single ten-year period in England. Which limit applies depends on when the breach occurred, so ask the authority to confirm the position for the specific breach rather than assuming.

The notices available

Each notice does a different job, and knowing which one is in play tells you what happens next.

The one worth understanding is the enforcement notice, because it is the main tool and the slowest. It must specify the breach and the steps required, it takes effect at least 28 days after service, and it carries a compliance period after that. Lodging an appeal suspends it entirely until the appeal is decided, which can add many months. The comparison in enforcement notice against breach of condition notice explains why a council sometimes chooses the one with no appeal right.

Timescales and why they feel slow

There is no statutory deadline for investigating a complaint. A typical sequence is acknowledgement within a week or two, a site visit within a few weeks, correspondence with the owner, a period during which the owner is invited to regularise or remove, and only then a notice.

That sequence exists because the courts expect councils to act reasonably, and serving a notice without giving the owner a chance to respond invites a successful appeal. From a neighbour's point of view it looks like nothing is happening. From the council's point of view the file is moving.

Where work is actively being carried out and the harm would be irreversible, a temporary stop notice can be used quickly. Say so explicitly in your report if that is the situation, because urgency has to be flagged to be recognised. The piece on reporting a breach of condition on a building site covers the live-construction case.

Following up and escalating

Ask for a case reference and the officer's name. Ask what the next step is and when it is expected. Then follow up at the interval you were given rather than weekly.

If nothing happens, the routes are the council's own complaints procedure first, then the Local Government and Social Care Ombudsman, which can investigate maladministration in how the council handled the case but cannot overturn a decision that enforcement was not expedient. Your ward councillor can ask officers for a progress report. A judicial review of a decision not to enforce is possible but rare, difficult and expensive.

The honest summary is that persistence and evidence change outcomes more often than escalation does. A log, photographs and a clear statement of the harm give the officer what they need to justify acting.

This is general guidance, not legal advice; check the position with your local planning authority before relying on it. You can browse the planning documents index if you want to understand what a developer should have submitted in the first place.