The Whitley principle and unlawful implementation

The Whitley principle in planning means that work carried out in breach of a condition that had to be discharged before development began is not work carried out under the permission. It does not count as a start on site. If the permission then runs out of time, the applicant is left holding a consent that was never lawfully implemented and can no longer be implemented, with foundations already in the ground and no way back.

The principle takes its name from Whitley and Sons v Secretary of State for Wales, decided by the Court of Appeal in 1992. A mineral permission carried a condition requiring a scheme to be approved before working began. Working began anyway. The court held that operations carried out in contravention of the condition could not properly be described as operations carried out under the permission.

That one holding has cost more permissions than almost any other rule in English development control.

What the principle holds

Read it as a question about authority rather than a question about enforcement. A planning permission authorises development subject to its conditions. Where a condition prohibits development until something has been approved, the permission on its true construction does not authorise anything until that approval exists. So the digger on site in week one is not implementing the permission. It is carrying out development without permission.

Two consequences follow, and practitioners tend to see only the second. The first is that the clock under section 91 of the Town and Country Planning Act 1990 keeps running, because nothing has begun. The second is that the works themselves are unauthorised and open to enforcement.

The first consequence is the expensive one. Enforcement can be regularised. An expired permission cannot.

True conditions precedent and ordinary conditions

Not every condition worded "before any development starts" bites this hard. In Hart Aggregates, decided in the High Court in 2005, Sullivan J drew the distinction that now governs most arguments: a condition only prevents implementation where it is a true condition precedent, going to the heart of the permission, rather than a condition regulating some aspect of a development that is otherwise authorised.

A condition requiring approval of the whole quarry working scheme, or of the finished floor levels of houses in a flood-prone field, is capable of going to the heart of the permission in that sense. A condition requiring approval of boundary fence colour, or of a landscape maintenance programme, almost certainly does not, even if its wording says development must not start first.

The test is on the substance, not the drafting. Officers sometimes argue that any pre-commencement condition is precedent because the words say so, and that argument usually loses. Applicants sometimes argue the opposite about a condition that plainly fixes the acceptability of the scheme, and that loses too.

Where the condition is ambiguous, read it with the officer report and the reason given for imposing it. The reason is part of the permission's context and often settles whether the condition was controlling the principle of the development or tidying its detail.

What happens when work starts before discharge

The authority has several routes, and they can run together. A breach of condition notice under section 187A requires compliance and carries no right of appeal. An enforcement notice can require the works to be removed or altered. Where the development is operational and substantial, the practical outcome is usually a retrospective application under section 73A of the 1990 Act for the development as carried out.

Time limits matter here. The Levelling-up and Regeneration Act 2023 moved the immunity period for most breaches in England to ten years, and commencement provisions should be checked against the current position before anyone relies on waiting it out. Relying on immunity is in any event a poor plan for a housing scheme that needs a mortgage, a warranty and a clean title.

None of these routes restores the original permission. They produce a different permission for what is on the ground, usually with the conditions the council wanted in the first place, and often with the loss of anything the original scheme had secured on viability or affordable housing.

Whether a later approval cures the breach

Sometimes, and only on narrow facts. Whitley itself recognised that where a valid application for the required approval was made before the permission expired, and that approval was later granted, the development can be treated as having been lawfully begun. The approval reaches back over the works already done.

The pleading point is the date of the application, not the date of approval. An application submitted inside the life of the permission can be determined months after it. An application submitted after expiry cures nothing, because by then there is no permission for the approval to attach to.

In Greyfort Properties, decided by the Court of Appeal in 2011, an old permission carried a condition requiring approval of finished floor levels before development began. Levels were never approved. Work had been done. The permission was held not to have been lawfully implemented, and it had long since expired.

Legitimate expectation has been tried as a rescue. In Henry Boot Homes v Bassetlaw District Council in 2002 the Court of Appeal accepted in principle that a council's conduct might in exceptional circumstances prevent it from relying on the breach, then found that the facts fell well short of that. Treat that route as theoretically open and practically closed. Verbal assurances from a case officer that it will be fine are worth nothing against it.

The effect on the life of the permission

Section 91 gives most permissions three years from grant unless a different period is imposed. Once that period passes without a lawful start, the permission is spent. There is no procedure to extend it, the temporary extension scheme of the early 2010s having gone.

A variation application cannot save it either. Section 73 variation of planning conditions only works on a live permission, because the application varies conditions attached to a subsisting consent. Where the consent has lapsed, there is nothing left to vary and the only route is a fresh application judged against the development plan as it now stands. On a site where the plan has changed, or where standing advice from planning consultees has hardened since the original grant, the fresh application is a different and harder proposition.

That is the real exposure. Not the enforcement notice. The policy that has moved on underneath the site.

A drainage condition, illustrated

The following example is illustrative. A permission for five houses carries a condition requiring a surface water drainage scheme, including infiltration testing and attenuation volumes, to be submitted to and approved in writing by the local planning authority before any development starts, with the reason given as the prevention of flooding on and off the site.

The contractor strips the site, digs footings and lays drainage runs in March. The drainage scheme goes in for approval in June. The permission expires in September and approval arrives in October.

On these facts the works in March were not a lawful start, because the condition went to the acceptability of the scheme in drainage terms. But the application for approval was made in June, inside the life of the permission, and the later approval can be read back. The development is treated as lawfully begun. Move the submission date to October and the answer reverses completely, with five part-built houses sitting on a lapsed consent.

Change the condition to one requiring approval of gully grating finishes and the analysis changes again, because that condition regulates detail and does not go to the heart of the permission.

Avoiding the problem on a live scheme

1. Schedule every condition the week the decision notice arrives, splitting pre-commencement from pre-occupation and recording the reason given for each.
2. Argue pre-commencement wording down at the drafting stage. The Planning Practice Guidance on the use of planning conditions expects these conditions to be used sparingly, and written consent to pre-commencement conditions is required before they are imposed on most permissions.
3. Submit discharge applications in batches with a target of eight weeks before any site mobilisation, and get the submission date recorded.
4. Where mobilisation cannot wait, limit early works to things that are not development under section 55, such as site survey and ground investigation, and document the limits.
5. If a start has already happened in breach, establish the expiry date first, then decide between a pending-application argument, a section 73A application and a fresh submission.

Conditions discharge is unglamorous work that sits badly in fee proposals, and it is where permissions are quietly lost. A drafted Planning Statement and supporting documents set does not help if the schedule behind the permission was never read properly.

This is general guidance, not legal advice. Whether a particular condition is a true condition precedent turns on its wording, its stated reason and the permission as a whole, so check the position with your local planning authority or a qualified professional before relying on it. The only formal route to confirm that works already carried out are lawful is a certificate of lawfulness under sections 191 or 192 of the 1990 Act.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. Enter a postcode on PlanScope to see which reports a site is likely to need before the conditions arrive.