Clause and Effect: What 'Pause' Would Have to Mean in a Heathrow Consent Order

Expansion is back on the agenda, and so, inevitably, is the softer vocabulary that accompanies it. We are told the programme will be approached 'sensibly', that the next stage will be 'phased', that nothing will proceed until the conditions are right. Each of those phrases sounds like restraint. In planning law, however, restraint is not a mood. It is a clause — or it is nothing at all.

This briefing is written for the parish councillor, the residents' association secretary and the campaigner who will one day sit in a village hall reading a Development Consent Order and trying to work out what it actually permits. It is about the difference between a pause that binds and a pause that merely reassures.

The Two Kinds of Pause

There is an administrative pause and there is a conditional one. An administrative pause is granted by the developer, to the developer, and may be lifted whenever the developer's board decides the weather has improved. It requires no permission, no scrutiny and no explanation. It is, in substance, a diary entry.

A conditional pause is a different animal. It is written into the consent itself as a requirement: a set of circumstances which, once independently established, legally suspend the authorised works. The developer does not choose to engage it. The condition engages it, and the developer's only remaining discretion is over how quickly it stops.

Any expansion consent that reaches the Planning Inspectorate should be tested against that distinction first. Everything else is detail.

Drafting Test One: The Trigger Must Be Automatic

Useful language looks roughly like this: no works forming part of the authorised development shall commence, and any works already commenced shall cease within a specified period, unless and until the Secretary of State has certified that the conditions in Part X are met.

The words that matter are 'unless and until' and 'certified'. A formulation that permits works to continue 'pending the Secretary of State's consideration' is not a pause; it is a queue. Nor should certification be a single, unrepeated event. A properly drafted requirement would operate at defined gates — before commencement, before the runway becomes operational, and at fixed intervals thereafter — so that a condition met in one year cannot be assumed to hold in the next.

Drafting Test Two: The Carbon Test Must Be Cumulative

The temptation, throughout the last decade of aviation policy, has been to measure only what happens inside the airport perimeter. A serious pause clause cannot accept that boundary. It should require that the scheme be assessed against the UK's legally binding carbon budgets, including aviation's share of international emissions, and against the Climate Change Committee's published advice on how that share should be managed.

In practice that means the trigger should bite if the Committee advises that the expansion is incompatible with the budget period in force, or if the sector's cumulative emissions exceed the trajectory assumed in the consent. It should not be possible for a developer to pass the test by purchasing offsets, by projecting fleet replacement further into the future, or by counting sustainable aviation fuel that does not yet exist at scale. If a condition can be satisfied by a spreadsheet assumption, it is not a condition. It is a forecast wearing a lanyard.

Drafting Test Three: Noise Thresholds With Named Numbers

Noise conditions are where drafting becomes most evasive. Phrases such as 'no significant adverse effect' and 'insofar as reasonably practicable' have absorbed more community objection than any minister ever has.

A defensible clause would specify contour values, the metric used, the population count affected and the year against which compliance is measured. It would treat the night period separately, because sleep is not a daytime average, and it would require the developer to publish the modelling behind every compliance statement. Crucially, the threshold should be a ceiling, not a target. A target invites a report explaining why it was nearly met. A ceiling engages a stop.

Drafting Test Four: Independent Verification, Openly Done

The single most consequential line in any pause clause is the one naming who decides whether the trigger has fired. If the answer is the applicant, the clause is decorative.

Verification should sit with a body the developer does not appoint and cannot dismiss: the Climate Change Committee for the carbon test; an independent noise panel, drawn from acoustics and public health expertise and appointed with the consent of affected local authorities, for the noise test. Its working papers, data and disagreements should be published. Where a condition depends on traffic modelling, the model itself should be open to inspection by councils and community groups, with a published log of assumptions and revisions. A pause clause that cannot be audited from outside the room is a promise, and promises are not enforceable.

Drafting Test Five: Surface Access Before Take-off

Surface access commitments have a habit of arriving after the aircraft do. The clause should invert that sequence. No operational flights until the rail and bus infrastructure specified in the consent is running, at the capacity claimed, with mode share demonstrated by measured data rather than modelled aspiration. A trigger should fire if car trips attributable to the airport rise above an agreed baseline for two consecutive reporting years.

This is not an unreasonable standard. It is simply the standard the applicant's own case requires, since a scheme justified by public transport connectivity should be able to prove that connectivity exists.

Drafting Test Six: Consent That Is Actually Local

Community consent is harder to draft than to demand, but it is not impossible. A workable mechanism would require the formal agreement of the affected principal authorities, and a statutory role for parish and town councils in certifying that compensation, blight and relocation matters have been settled before works begin. A residents' ballot in the affected wards, run on a published register and supervised independently, would give the test democratic weight rather than consultative colour.

The objection will be that this hands a veto to a small number of people over national infrastructure. The answer is that the people holding the veto are the ones who will live with the noise, the traffic and the compulsory purchase orders. Their consent is not an obstacle to legitimacy; it is where legitimacy comes from.

The Off-Ramp Must Lead Somewhere

Finally, a pause should specify what happens while it operates. Works suspended, land restored to an agreed condition, a bond sufficient to cover restoration drawn down if necessary, compensation settled rather than deferred, and no claim against the public purse for the developer's losses. A pause that leaves the community holding an unfinished earthwork and a legal bill is not a pause. It is a hostage situation with better stationery.

What Campaigners Can Ask For

When a scheme appears, whether in a consultation, a local plan or an examination, the questions are portable. Which conditions are automatic? Who verifies? What are the numbers? When are they measured? Who consents? What happens if the trigger fires? A council that asks those six questions in public has already improved the document.

The campaign's demand has never been a permanent 'no'. It is a genuine opportunity to establish whether expansion can be done within the limits the country has set itself. That question can only be answered honestly if the consent contains a real off-ramp — one that works without the applicant's cooperation, and one that a resident can read, understand and hold to account.