What Are Grampian Conditions? A Simple Guide

If you’ve ever looked into getting planning permission—whether for a new home, an extension, or a larger scheme—you may have come across the slightly odd phrase “Grampian condition.”

It sounds like something to do with Scotland (and it is, in origin), but today it’s a common planning tool used all over England and Wales. And despite the jargon, the basic idea is pretty straightforward.

This article explains what Grampian conditions are, why planners use them, and when you should or shouldn’t agree to one.

What Is a Grampian Condition?

A Grampian condition is a negatively-worded planning condition that stops development from starting or being occupied until a specific action has been completed. Crucially, that action usually takes place on land outside the applicant’s control, or requires approval from another organisation.

In practice, the condition might say something like:

“No development shall commence until X off-site works have been completed…”

Instead of forcing you to carry out work on land you don’t own or control, the council uses a Grampian condition to make sure essential off-site measures are in place before the development proceeds.

Why Are They Called “Grampian” Conditions? The Case That Started It All

The term “Grampian condition” comes from a landmark planning case in the early 1980s:

Grampian Regional Council v City of Aberdeen District Council (1984).

The case involved a large proposal to change land from agricultural use to industrial use. The key issue was highway safety. Access to the site relied on a road that joined a dual carriageway at a point the decision-maker considered unsafe.

The planning inspector believed the only way to make the development acceptable was to close part of that road—but doing so required approval from another authority.

Because the road closure couldn’t legally be guaranteed by the applicant, the Inspector decided he couldn’t impose a condition requiring it, and therefore refused permission.

Grampian Regional Council challenged that view in the courts. They argued that the Inspector could have granted permission with a condition preventing the development from going ahead until the road closure had been confirmed.

The House of Lords agreed with Grampian.

Their reasoning introduced the principle that underpins today’s Grampian conditions:

• A positive condition (telling an applicant to carry out works on land they don’t control) is usually unenforceable.

• A negative condition (preventing development from starting until certain external actions occur) is enforceable and can be reasonable.

The court emphasised an important point:

Planning permission does not force anyone to build. If the off-site action never happens, the developer simply cannot implement the permission—not all permissions have to be capable of immediate use.

This decision confirmed that councils can grant permission subject to off-site matters being completed first, even when those matters sit outside the applicant’s ownership or control.

And that is why such conditions have, ever since, been known as “Grampian conditions.”

Why Do Councils Use Grampian Conditions?

Local planning authorities often use these conditions to deal with issues such as:

• Highway safety improvements

• New or upgraded drainage connections

• Utility capacity upgrades

• Infrastructure required off-site

• Third-party approvals or land access

If the development is acceptable in principle but relies on something external being sorted, a Grampian condition lets the council approve the application now while protecting the public interest.

When Are Grampian Conditions Appropriate?

A Grampian condition should only be used where:

1. The off-site action is necessary for the development to be acceptable.

2. There is a realistic prospect that the action will happen within a reasonable timeframe.

3. The requirement is clear, specific and enforceable.

Councils must consider whether such a condition is a workable solution before refusing permission. In some appeal cases, failure to consider a Grampian condition at all has been ruled procedurally unfair.

When Should You Accept a Grampian Condition?

In our experience, accepting a Grampian condition makes sense when:

• The required works are already planned or funded.

• The relevant authority (Highways, utilities etc.) is supportive in principle.

• There is a clear pathway to obtaining the necessary approval.

• The condition applies to occupation rather than commencement, allowing you to keep construction moving.

For many applicants, a Grampian condition is a practical way to secure planning permission earlier.

When You Should Be Cautious

A Grampian condition may be problematic if:

• The external works are unlikely to happen.

• You’ve been advised that another body will not agree to the works.

• Timescales are uncertain or could cause commercial delays.

• The condition is vague or lacks clarity about what must happen.

If there is no prospect at all of the off-site action being delivered, the condition should not be used—and accepting it may leave you with a permission you cannot implement.

How to Respond if a Grampian Condition Is Proposed

Here are practical steps we recommend to clients:

1. Engage early with third parties

Get written confirmation or in-principle agreement from the relevant authority or landowner.

2. Seek clarity on exactly what the condition requires

Ask the local planning authority to confirm the trigger: commencement or occupation.

3. Provide evidence that the off-site action is deliverable

Clear evidence can persuade the council or an Inspector that approval is appropriate.

4. Negotiate alternative wording if needed

Often the same objectives can be achieved with a more flexible or precise condition.

Final Thoughts

Grampian conditions are a useful planning tool—but only when used correctly. They can unlock permission for developments that depend on off-site improvements, but they must be realistic, justified and clearly worded.

If you need advice on whether to accept a Grampian condition, or support navigating the planning system more broadly, our team can help you understand your options and move your project forward with confidence.

About Me

Andrew Ransome is the planning director at ADP and is a chartered member of the RTPI, with over 22 years of town planning experience.

Andrew has extensive experience offering strategic planning solutions to challenging projects in both rural and urban settings. Follow him on Linkedin.