Discharging conditions: bundling, fees and the eight weeks

The conditions on your decision notice are a programme. Some have to be dealt with before a spade goes in, some before anyone moves in, and some are standing obligations for the life of the development. Sorting them into those three groups on the day the permission arrives is the single most useful hour you will spend on the project.

Get it wrong in the first direction and you have a delay. Get it wrong in the second and you may find the permission was never lawfully implemented at all.

Reading conditions for the trigger point

Take the decision notice and go through it line by line, writing the trigger against each condition. The language is fairly consistent.

Conditions that begin "no development shall take place until" or "prior to the start of development" have to be discharged first. Conditions that say "prior to first occupation" or "before the building is brought into use" can wait, and often should, because you will have better information later. Conditions that impose a standing requirement, such as hours of operation or the retention of parking, are never discharged at all; they simply apply.

A fourth category catches people out: conditions tied to a specific stage, such as "prior to the installation of external materials" or "before the drainage is laid". Those need a diary entry against the construction programme rather than a date.

Before-start, before-occupation and compliance conditions

Legislation restricts the use of conditions that must be satisfied before development begins: the authority has to seek the applicant's written agreement before imposing one. That agreement is negotiable. If a council proposes a landscape condition that has to be discharged before you can dig a foundation, ask for it to be re-triggered to before occupation, and say why. Officers agree more often than applicants expect, because a condition that delays a start delays their completion figures too.

Bundling requests into one application

The fee is charged per request, not per condition. So five conditions in one application cost the same as one condition in one application, and the arithmetic pushes towards bundling.

The counter-pressure is speed. A bundle is determined as a whole, so a straightforward materials condition submitted alongside a drainage condition that needs a consultee response will be held until the drainage answer arrives.

The workable compromise is to bundle by consultee:

1. Group conditions decided by the case officer alone, such as materials, boundary treatments and details of joinery.
2. Group conditions that go to the highway authority.
3. Group conditions that go to the lead local flood authority or the drainage engineer.
4. Keep ecology conditions separate, because they may depend on a survey season.
5. Submit each group as it becomes ready rather than waiting for the whole set.

That usually means three or four fees instead of one, and it usually saves more in programme than it costs in fees.

Illustrative example: a nine-unit scheme with fourteen conditions, six of them before-start. Submitted as one bundle in January, the drainage strategy condition attracts a query from the lead local flood authority in week six, and the whole application is determined in week eleven. Split into three, the materials and boundary conditions come back in week four and the site can be set up while the drainage question is resolved.

Fees and the eight-week period

The council has eight weeks from validation to determine an application for approval of details, unless a longer period is agreed in writing. The period is the same whether the request covers one condition or ten.

Two things slow it down more than anything else. Incomplete submissions, where the officer has to write back asking which condition a document relates to. And consultee dependency, where the council is waiting on someone else and has no ability to hurry them.

Both are within your control. Label every document with the condition number it discharges, provide a covering schedule listing each condition, the requirement, and the document that answers it, and send the technical material to the consultee's usual standard rather than a summary of it.

Where a council misses the period, a deemed discharge procedure exists, but the exclusions are wide enough that it rarely helps on a real site. Conditions concerning flood risk, highways, contaminated land and development subject to environmental impact assessment sit outside it, and those are exactly the conditions that take longest.

What happens if you start early

This is the part worth taking seriously. Where a condition has to be satisfied before development begins, and work starts without it, the works are carried out in breach and may not amount to lawful implementation of the permission.

The practical consequence is that the three-year period keeps running. A developer who starts in year three in breach of a before-start condition may find, when the period expires, that the permission has lapsed with nothing lawfully begun. Enforcement is the visible risk. The lapsed permission is the expensive one.

There is a narrower version of the same problem on sale or refinancing, where a solicitor reviewing the title finds a before-start condition with no discharge notice and raises a requisition that stops the transaction.

If work has already started, say so and apply anyway. Councils deal with retrospective discharge routinely, and the position is much easier to regularise while the development is under construction than afterwards.

Where the permission is close to expiring and a before-start condition is outstanding, take advice before doing anything on site. There are recognised ways of implementing a permission lawfully, and there are ways that look like implementation and are not, and the difference between them is worth a professional opinion rather than a guess.

Keeping the compliance file

Open a folder on the day permission is granted and keep it for the life of the building. It should hold the decision notice, the approved drawings, every discharge application with its reference, every discharge decision notice, and a one-page schedule showing each condition and its status.

A construction management plan and similar documents often satisfy more than one condition, so record which conditions each document was submitted against. And keep the correspondence with consultees, because on a later application the same officer will ask the same question.

The file has a second use. Where a scheme is varied under section 73, the new permission carries its own conditions, and a discharge obtained under the original permission does not automatically satisfy the equivalent condition on the new one. A tidy schedule makes that reconciliation a morning's work instead of a fortnight of guessing.

Browse the report types a discharge submission commonly needs or enter your postcode on PlanScope to see what a site's constraints are likely to require.

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.