Daylight and amenity conditions: wording that actually works

Most amenity conditions attached to residential permissions could not be enforced if anyone tried. They refer to a report rather than to a physical outcome, they use words like "adequate" and "satisfactory", or they require something to be demonstrated after the building is finished, when the only remedy left is demolition. A condition has to pass six tests, and precision and enforceability are two of them.

If you are drafting suggested conditions for an officer, the useful discipline is to write each one as an instruction a building inspector could check on site with a tape measure.

Why amenity conditions are often unenforceable

The six tests in national guidance are that a condition must be necessary, relevant to planning, relevant to the development permitted, enforceable, precise, and reasonable in all other respects. Amenity conditions fail on the last three more often than on the first three.

Three recurring failures.

A condition requiring the development to be carried out "in accordance with the submitted Daylight and Sunlight Assessment". That report is an analysis of a design, not a specification of works. There is nothing in it to build to and nothing to enforce against.

A condition requiring an outcome to be "demonstrated to the satisfaction of the local planning authority" without saying what the standard is. Precision fails, and so does enforceability, because nobody can say whether it has been met.

A condition requiring post-completion verification of daylight to neighbouring windows. It is a real requirement, and it is unreasonable, because the only response to a failure is to alter or remove a completed building.

Obscure glazing and fixed light wording

This is the most common amenity condition in the country and the easiest to get right.

A workable condition names the specific windows by elevation and by drawing reference, states the obscuration level required, states the height below which the window must be non-opening, and requires the arrangement to be retained. Councils usually specify a level on the standard obscure glazing privacy scale, and the height below which opening is prevented is commonly 1.7 m above finished floor level, which is above standing eye height.

Two drafting points that save arguments later.

Say "measured from the finished floor level of the room served" rather than "from floor level", because on a split-level plan those are different. And avoid conditioning a whole elevation where only one window matters, because a blanket condition catches windows the neighbour never sees.

Where the concern is a flank window on an extension, remember that Class A of Schedule 2 Part 1 to the General Permitted Development Order 2015 already requires upper floor side elevation windows to be obscure-glazed and non-opening below 1.7 m. A condition that duplicates that adds nothing and fails the necessity test.

Conditions fixing window positions and sizes

Where the daylight case depends on a specific window, condition the window rather than the report.

Good practice is to tie the approval to a numbered drawing showing the window at a stated size and sill height, then add a condition removing the relevant permitted development rights so the arrangement cannot be altered later without consent. Removal of rights has to be justified: national guidance expects it to be exceptional, and the justification here is that the daylight relationship was the reason the scheme was acceptable.

Where a scheme relies on a rooflight or a light well for internal daylight, condition its position and glazed area. A rooflight moved 2 m during construction changes the internal result and nobody notices until occupation.

Conditions tied to a submitted report revision

There is a version of this that works. Condition the mitigation, and reference the report only for identification.

Compare two forms:

The right-hand column can be checked on site. The left-hand column cannot.

An Overshadowing Study or a Daylight and Sunlight Assessment should still be listed in the approved documents condition, because that fixes what the permission was granted on the basis of. It is an evidential record rather than a work instruction.

The six tests applied to amenity conditions

Run each proposed condition through this sequence before you send it to the officer:

1. Necessary. Would refusal be justified without it? If the answer is no, delete it.
2. Relevant to planning. Is it about land use and amenity rather than about a private dispute?
3. Relevant to this development. Does it relate to what is being permitted rather than to something else on the site?
4. Enforceable. Could a council officer establish a breach by inspection?
5. Precise. Does it state the standard, the location and the timing?
6. Reasonable. Is compliance within the applicant's control, and is the remedy for breach proportionate?

Test 6 is where post-completion verification dies, and test 4 is where "to the satisfaction of the authority" dies.

Where a condition has to be met before work starts, section 100ZA of the Town and Country Planning Act 1990 and the 2018 regulations on conditions that bite before work starts require the applicant's written agreement, subject to the exceptions in the regulations. That is a lever worth knowing about when an officer proposes a condition that would delay a start on site for no benefit.

Drafting a condition you can live with

Write the condition yourself and offer it. Officers under time pressure use the wording in front of them, and a condition drafted by the design team is more likely to be buildable than one lifted from a precedent list.

Keep to a structure: what must be done, to what standard, by when, and for how long. "The windows marked A and B on drawing X shall be fitted with obscure glazing to Level 3 and shall be non-opening below 1.7 m above the finished floor level of the room served, before the development is first occupied, and shall be retained in that form thereafter."

Every element in that sentence is checkable. That is the whole test.

Illustrative example: a two-storey side extension where the officer proposed a condition requiring "no overlooking of the adjoining property". The design team offered a replacement naming the two landing windows, the obscuration level, the non-opening height and the retention requirement. The officer took it verbatim. This example is illustrative.

Varying an amenity condition later

Two routes. A section 73 application varies or removes a condition and produces a new permission with the condition changed, and it is the right route where the change is substantive. A section 96A non-material amendment deals with minor changes only and cannot be used to alter a condition in a way that matters.

There is a third option that people forget: appeal the condition under section 78 when the permission is issued. That has to be done within the appeal period, and it puts the six tests in front of an inspector who applies them strictly.

Design the condition at application stage and none of this arises.

PlanScope drafts the Design and Access Statement and amenity documents that sit behind these conditions, structured to UK planning policy, with modelled results left to a qualified assessor. Browse the full report list to see what an amenity case usually needs.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.