Glossary

The Whitley principle and conditions discharged late

6 min readBy PlanScope Editorial Team

Under the Whitley principle, work carried out in breach of a condition precedent does not implement the permission. Here is how the rule works, and how to avoid it.

The Whitley principle is the rule that work carried out in breach of a condition precedent is not work authorised by the permission, so it does not implement it. The practical effect is brutal. A developer can dig foundations, spend money, believe development has begun, and find years later that the permission expired on its original date because one condition had never been formally discharged.

It takes its name from Whitley & Sons v Secretary of State for Wales (1992), where the Court of Appeal held that an operation contravening a condition cannot properly be described as beginning the development authorised by the permission. The reasoning is simple enough to state and difficult to escape: the permission is the grant, the conditions define its scope, and work outside that scope is not done under it.

Why a start in breach is not a start

Section 91 of the Town and Country Planning Act 1990 sets the time limit within which development must be begun. Section 56 defines when it is begun, by reference to a material operation comprised in the development.

Put those together with a condition that says no development shall take place until a scheme has been approved, and the trench you dug is not a material operation comprised in the permitted development at all. It is unauthorised development. It cannot start the clock because the clock only runs on authorised work.

That is the whole of the principle. Everything else in this area is argument about which conditions it applies to.

Which conditions are true conditions precedent

Not every condition worded as a prohibition is one. The courts have drawn a line between conditions that go to the heart of the permission and conditions that regulate a particular aspect of the development.

In R (Hart Aggregates Ltd) v Hartlepool Borough Council (2005) the High Court held that a condition requiring a scheme to be submitted and approved did not necessarily prevent the whole development from starting where it regulated one element rather than prohibiting commencement outright. In Greyfort Properties Ltd v Secretary of State for Communities and Local Government (2011) a condition requiring approval of finished floor levels before development began was treated as a true condition precedent, and the permission was held not to have been implemented.

The distinction turns on wording and purpose together. A condition requiring approval of a construction management plan before any works begin usually regulates an aspect. A condition requiring approval of levels, or contamination remediation, or a phasing plan on which the whole layout depends, is far more likely to be fundamental.

Read decisions of this kind as indicative of how the courts have approached the question rather than as a formula. The outcome is fact sensitive and the wording of your condition will not be identical to the wording in any reported case.

The exceptions the courts have recognised

Three routes out have developed, and none of them is comfortable.

The first is retrospective discharge. Where an application to discharge the condition was made in time and the authority approves it before the permission expires, the earlier works can be treated as lawful. The sequence matters. An approval given after the expiry date does not retrospectively rescue a permission that has already lapsed.

The second is the aspect condition analysis above, where the condition is found not to be fundamental.

The third is practical rather than legal. Where the breach is historic, enforcement time limits may have run, so the authority cannot act on the unauthorised works even though the permission was never implemented. That protects the works. It does not revive the permission, which matters if later phases depend on it.

Effect on time limits, levy and obligations

The expiry of the permission is the headline consequence. Section 73 cannot be used to extend a time limit for implementation, so there is no tidy variation route.

Levy liability follows commencement of chargeable development, so a failed implementation creates an awkward position: money may have been demanded on a commencement notice for a development that, on the Whitley analysis, never lawfully began. Authorities take different views and the sums are rarely small.

Section 106 obligations drafted around triggers such as "prior to commencement of development" face the same problem in reverse. If the development never lawfully began, the trigger arguably never fired, which sounds helpful until a purchaser's solicitor asks you to prove the obligation has been performed.

Where an obligation involves a payment such as a commuted sum, get the position confirmed in writing before completion rather than arguing it afterwards.

Remedies once the point is discovered

Order of preference, on most sites.

  1. Check whether the condition was in fact a true condition precedent. Half of the alarm calls end here.
  2. Check whether a discharge application was made and determined before the expiry date, including any application dealt with informally by email, which is more common than it should be.
  3. Apply under section 73A for permission for development carried out without complying with conditions, where the works are the issue.
  4. Apply for a fresh permission for the unbuilt remainder, accepting that current policy, the biodiversity gain condition and current levy rates will apply.
  5. Apply under section 191 for a certificate of lawfulness where enforcement time limits have expired and you need the position on record.

Route four is the honest one on a stalled site. A permission granted before the mandatory biodiversity gain regime came in, re-applied for now, will carry the gain condition and an approved biodiversity gain plan requirement, and the viability position changes accordingly.

Drafting so the trap never opens

Most of this is avoidable at the draft condition stage, and that stage is shorter than people think. Section 100ZA of the 1990 Act prevents an authority from imposing a pre-commencement condition without the applicant's written agreement, which gives you a formal moment to object.

Use it. When the draft conditions arrive, sort them into three piles.

Conditions that must bite before any work at all: contamination, protected species, archaeology, structural surveys of retained fabric. Accept these and programme for them.

Conditions wrongly attached to commencement: materials, landscaping, boundary treatments, external lighting, refuse storage, electric vehicle charging. Ask for the trigger to be moved to before the relevant works, before first occupation, or before the use starts. Officers usually agree, because the substance is unaffected.

Conditions that are ambiguous: anything using "no development shall take place" alongside a requirement that only makes sense later. Ask for redrafting. A condition that reads "no development above damp proof course level" is worth a great deal more to you than one that reads "no development".

An illustrative example. On a 14 unit scheme the draft conditions include eight pre-commencement requirements. The agent agrees to three, negotiates four onto an occupation trigger, and asks for the eighth to be reworded so it bites above slab level. The scheme starts on site four months earlier than it otherwise would, and the Whitley risk sits on three conditions instead of eight.

Before you commit to that negotiation, it helps to know which supporting documents the authority will expect at discharge stage, because the evidence a condition needs is what actually determines how long the discharge takes.

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.

Frequently asked questions

What exactly does the Whitley principle say?

That an operation carried out in breach of a condition cannot properly be described as commencing the development authorised by the permission. It follows from Whitley & Sons v Secretary of State for Wales (1992). Because only authorised work counts as a material operation, work done in breach does not start the clock under the statutory time limit.

Is every pre-commencement condition a true condition precedent?

No. The courts distinguish conditions going to the heart of the permission from those regulating one aspect of it. Conditions about levels, remediation or phasing are usually fundamental. Conditions about construction management or external details often are not. The outcome turns on the exact wording and purpose, so treat reported decisions as indicative.

Can a condition be discharged after work has started?

Sometimes. Where the discharge application was made in time and the authority approves it before the permission expires, the earlier works can be treated as lawful. An approval given after the expiry date does not revive a permission that has already lapsed, so the sequence and the dates are what matter.

What happens to levy and section 106 triggers if the start was invalid?

Both become uncertain. Levy liability follows commencement of chargeable development, so a payment may have been demanded for a development that never lawfully began. Obligations drafted to bite prior to commencement face the mirror problem. Get the authority's position in writing before a sale or a funding drawdown rather than afterwards.

How do I stop this happening on the next permission?

Use section 100ZA, which prevents an authority imposing a pre-commencement condition without your written agreement. Sort the draft conditions into those that must bite before any work, those wrongly attached to commencement, and those that are ambiguous. Ask for the second group to move to an occupation trigger and the third to be reworded.

Sources and further reading

planning conditionswhitley principleimplementationglossarysection 73

This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.

More in Glossary

View all →
Glossary7 min read

Liability notice and demand notice under the levy

A levy liability notice sets the chargeable amount and a demand notice sets the payment dates. Here is what to check on each, how instalment policies work, and where the review and appeal routes lead.

Read article →
Glossary7 min read

Assumption of liability for the levy

Assuming liability on the levy's Form 2 fixes who the council will pursue for the Community Infrastructure Levy. It has to be done before work starts, and before any relief claim, or liability falls back on the landowners.

Read article →
Glossary7 min read

Heads of terms for a planning obligation

Heads of terms are the schedule members vote on and the solicitors draft from. Here is what belongs in them, how to set triggers and indices, and which omissions hold up the deed after resolution.

Read article →
Glossary7 min read

Section 70A and declining a repeat application

Section 70A of the Town and Country Planning Act 1990 lets a council decline to determine a similar application made within two years of a dismissed appeal or two refusals. Here are the conditions, the similarity test and what to change.

Read article →
Glossary6 min read

The enforcement warning notice and how to respond

The notice is an invitation to apply, not something to comply with, and it records the authority view that permission would probably be granted. How to use that.

Read article →
Glossary6 min read

Revocation or modification of a planning permission

Implementation defeats revocation, and compensation for depreciation in land value is why authorities rarely make these orders. The confirmation procedure, the objection route and the sequence to follow.

Read article →