How Town Planning Works | TPW-0175 — The Restrictive Covenant Test: Why Planning Permission Can Say Yes While a Private Land Covenant Still Says No

Series ID: TPW-0175

The planning authority approves the extension.

The drawings comply with the zoning envelope. The building permit pathway is clear. The contractor is ready.

Then a solicitor reads an old deed and finds a covenant saying that no additional building may be erected without consent—or that the land must remain one private dwelling—or that part of the garden must remain open.

The public planning system has said yes.

A private land obligation may still say no.

Planning permission controls what public law allows. A restrictive covenant can control what private land rights allow. Solving one does not automatically solve the other.

The reader job: separate public planning approval from private title obligations before you buy land, design a project or start work

This article owns the public-permission-versus-private-restriction problem.

It does not re-own easements; those are mapped in The Easement Map. It does not replace zoning verification in The Zoning Verification Letter. It does not replace the question of whether a use needs or has planning approval in The Change of Use Test.

The distinct job here is to ask:

Even if the city permits this project, does someone else have a private right to stop, limit or condition it?

Current Upper Tribunal guidance states the separation directly

HM Courts & Tribunals Service updated its guide to restrictive covenants in July 2026. The guide describes a restrictive covenant as a legally binding restriction imposed on land through agreement and makes an unusually clear planning point: restrictive covenants are private arrangements and can prevent development even where planning permission exists.

That one distinction prevents a large category of development mistakes.

Planning permission is not a universal property-rights clearance.

A restrictive covenant usually tells the landowner not to do something

The exact law varies by jurisdiction, but typical restrictive covenants can limit:

additional buildings;
subdivision of a plot;
business use;
multiple dwellings;
building height or style;
use of front gardens;
signage;
parking of particular vehicles;
alterations without prior consent;
or uses considered inconsistent with an estate scheme.

The covenant can be far older than the current zoning code and far narrower than modern planning policy.

A positive covenant is a different kind of obligation

A positive covenant generally requires someone to do something—for example maintain a road, repair a fence or contribute to an estate facility—whereas a restrictive covenant generally limits what may be done.

The legal treatment of positive and restrictive covenants can differ substantially. The current Upper Tribunal restrictive-covenant process in England and Wales, for example, is directed at restrictive covenants and does not give the tribunal the same power to discharge or modify positive covenants or easements through that route.

For development due diligence, category matters because different problems require different legal solutions.

A covenant is not an easement

An easement gives someone a right over land—such as a right of way or utility access.

A restrictive covenant constrains land use or development.

A single title can contain both. A rear site might benefit from a driveway easement and simultaneously be burdened by a covenant restricting it to one dwelling.

Solving the access right does not solve the dwelling restriction.

A covenant is not a zoning condition either

A zoning or planning condition is imposed through public law as part of a governmental approval.

A private covenant arises through land arrangements between private or institutional parties.

The planning authority administers the first. The beneficiary or other legally entitled party may enforce the second.

This means the planning case file may not answer the covenant question at all.

Planning officers do not normally certify your private title position

When a planning authority approves a building, it usually decides the planning application before it. It does not guarantee that the applicant owns every necessary right to implement the project.

The applicant may still need landlord consent, neighbour rights, easements, covenant releases, party-wall procedures, title corrections or other private arrangements.

Public approval answers a public question.

Property rights answer another.

Singapore’s current planning guidance makes the broader separation visible too

URA’s current exemptions guidance, updated in September 2026, reminds owners that even works exempt from planning permission may still need other clearances and may remain subject to caveats, by-laws and Management Corporation rules.

The legal instruments are not identical to English restrictive covenants, and they should not be collapsed into one category. The planning lesson is nevertheless the same: not needing a planning approval does not mean every other property or governance restriction disappears.

The title register is a starting point for the private-rights search

A property buyer should obtain the relevant title records and the documents referred to in them where necessary.

In England and Wales, HM Land Registry guidance addresses notices, restrictions, development schemes, covenants and other third-party interests. In Singapore, SLA land-title searches provide registered title information through the relevant title and lot records.

The key discipline is not to rely on a sales brochure, agent statement or planning portal alone when the development depends on private rights.

The short title entry may point to the long document that matters

A register can refer to a transfer, conveyance, deed or schedule containing the actual covenant wording.

That original wording matters because tiny differences can change the development problem:

“no building” is different from “no building without consent”;
“one private dwelling” is different from “residential use only”;
“no trade or business” is different from a restriction on nuisance;
“no subdivision” is different from “no additional dwelling”;
and a covenant benefiting named retained land is different from a vague estate rule whose beneficiary must be established.

Do not paraphrase away the legal problem before a qualified professional has interpreted it.

The first question is not “Is there a covenant?” but “Who can enforce it?”

Old deeds can contain restrictions whose practical enforceability is uncertain because land has been divided, ownership has changed, beneficiaries are difficult to identify or the legal tests for transmission of benefit are complex.

The 2026 Upper Tribunal guidance notes that old conveyancing documents may need examination even where land is registered because identifying who can enforce a historic covenant can be difficult.

A covenant should therefore be analysed through at least four questions:

What exactly does it restrict?
What land is burdened?
Who holds or may hold the benefit?
What remedy or consent route is available?

“Nobody has complained for years” is not a due-diligence conclusion

A covenant can be forgotten socially while remaining relevant legally.

Neighbours may tolerate one breach but object to a larger redevelopment. A previous owner may have obtained informal consent that does not bind successors. A beneficiary may only act once construction makes the threat visible.

Silence is an observation. It is not automatically a release.

The age of a covenant does not automatically make it irrelevant

Some restrictive covenants date from housing estates laid out generations ago. Their original physical context may have changed radically.

Yet current tribunal guidance explicitly recognises that restrictive covenants imposed in the twentieth or nineteenth centuries can remain live questions today.

Age can become relevant to interpretation, benefit, practical utility or an application to modify or discharge. It is not a universal expiry date.

Estate schemes explain why old covenants can still shape neighbourhood form

Developers have long used covenants to create consistent estate conditions: residential-only use, building lines, architectural controls, limits on subdivision, shared spaces and restrictions on commercial activity.

The public zoning map might later permit denser or more mixed development while the private estate scheme continues to express an older spatial bargain.

This creates a real planning tension between public policy change and private land arrangements.

A covenant can preserve low density after zoning has changed

Imagine a neighbourhood rezoned to permit duplexes or small apartment buildings.

An old private covenant restricts certain lots to one detached dwelling.

The zoning reform increases public development rights, but the covenant can prevent some owners from using them unless the private restriction is released, modified or otherwise resolved.

Public upzoning does not guarantee uniform private buildability.

A covenant can also prohibit business where zoning allows it

A mixed-use or residential zone may permit specified home businesses or professional uses.

A private covenant may be stricter.

The business owner must therefore pass both tests: public land-use rules and private title restrictions.

Private consent language creates a negotiation pathway rather than an absolute prohibition

Some covenants prohibit development unless the original seller, estate owner, council, management body or another beneficiary gives written consent.

This changes the problem from “Can never be built” to “Who may consent, on what criteria, for what fee and with what legal documentation?”

Current local-authority covenant processes in England demonstrate how formal that can become: authorities can require title documents, the covenant deed, plans, legal advice, application fees and sometimes consideration for release or variation.

Consent is not necessarily release

A beneficiary can consent to one proposal without removing the covenant from the land altogether.

That distinction matters for future redevelopment. Today’s approved rear extension may not authorise tomorrow’s subdivision. A purchaser should know whether the document is:

specific consent to particular works;
a variation of the covenant;
a partial release;
a full release;
or merely informal correspondence.

The legal effect should match the development strategy.

A release by one party may not clear every beneficiary

A council, developer or former estate owner may hold some benefit while neighbouring owners or other parties hold separate enforceable rights.

Coventry City Council’s current guidance makes this practical point: a council release only deals with whatever residual benefit the council itself holds and does not extinguish rights held by other parties.

This is why “the council signed it” should never be treated as a universal private-rights clearance without checking the legal structure.

The modification or discharge route is jurisdiction-specific

In England and Wales, section 84 of the Law of Property Act 1925 provides a statutory route through the Upper Tribunal for certain applications to discharge or modify restrictive covenants. The current tribunal guidance explains the process, and the July 2026 fee schedule lists the application fee for that type of proceeding.

Other jurisdictions use different statutes, courts, tribunals or land-registration procedures.

The planning lesson is not to transplant one country’s legal remedy. It is to identify the correct local mechanism before assuming a covenant is either permanent or easy to remove.

A covenant application can become a project programme risk

Planning approvals often have timelines. Financing has timelines. Construction contracts have timelines.

A private covenant negotiation can introduce another clock: locating beneficiaries, valuation, negotiation, deed preparation, mortgagee consent, tribunal procedure, objections and registration.

If the development only works after covenant modification, that pathway should sit on the critical programme from the beginning.

Do not demolish first and solve the covenant later

Starting work before private rights are resolved can convert a manageable due-diligence issue into an enforcement dispute.

Depending on the jurisdiction and facts, remedies for breach can be serious. The project may face injunction risk, damages, negotiation under pressure, financing concerns and difficulty on resale.

Current council guidance in England warns owners that unauthorised covenant breaches can lead to demands for work to cease or be undone and can complicate later sale.

The cheapest covenant problem is the one found before construction.

Indemnity insurance is a risk tool, not a magic consent

In some property markets, title or restrictive-covenant indemnity insurance may be considered where a covenant risk cannot be eliminated cleanly.

Such insurance does not automatically make prohibited development lawful, alter the covenant or guarantee that every project circumstance is covered. Insurers can impose conditions, exclusions and limits, and contacting beneficiaries can affect availability.

The decision belongs with qualified legal and insurance advisers who understand the transaction.

A lender will care because the covenant can affect collateral value

If a project’s value assumes ten apartments but a private covenant may limit the site to one house, the title issue reaches directly into valuation and loan security.

The lender may require legal opinions, releases, insurance, amendments or conditions precedent before funding.

Private rights become finance because development value is built from legally usable options.

A land option should identify covenant risk before the option price becomes emotionally sunk

Developers often control land through options or conditional contracts while seeking planning permission.

If the contract assumes planning approval is the only condition, a covenant discovered later can leave the buyer with permission that cannot be implemented.

Land-control documents should allocate private-rights risk deliberately: who investigates, who negotiates, who pays, and whether the buyer can walk away if the restriction cannot be solved.

Land-control transparency is itself becoming a planning-policy issue

In 2026, the UK government introduced new requirements—coming into force in April 2027—for information about certain contractual control agreements such as options, conditional contracts and pre-emption rights affecting registered land to be submitted to HM Land Registry.

These agreements are not the same as restrictive covenants, but the reform illustrates a wider planning concern: ownership alone does not reveal who can control how land is used or developed.

The modern land map increasingly needs a control map as well as an ownership map.

Restrictive covenants can conflict with public housing policy

A city may want more homes near jobs and transit. Zoning reform may legalise additional dwellings. Infrastructure may have capacity.

Private covenants can still restrict some parcels to lower intensity.

This creates a policy question beyond the individual title: how should societies balance long-standing private bargains against changing public needs?

Different legal systems answer that question differently. Good planning analysis should at least see the conflict rather than pretending the zoning map is the only map.

Heritage character can be protected twice

A neighbourhood can be subject to public conservation rules and private design covenants at the same time.

An owner may therefore need conservation approval from the planning authority and separate consent under the estate documents.

Passing one design review does not automatically pass the other.

Management-corporation rules create another private-governance layer in dense cities

Strata and condominium environments often contain rules governing common property, renovations, external appearance, access, services and use.

URA’s September 2026 exemptions guidance explicitly reminds owners to consider Management Corporation rules even where works fall within planning exemptions.

This is not the same legal instrument as a freehold restrictive covenant. It belongs in the same due-diligence habit: identify every layer of authority over the project.

Lease covenants can constrain use even when zoning is generous

A commercial lease can restrict alterations, assignment, underletting, signage or use. A tenant may obtain public planning permission and still need landlord consent under the lease.

Again, the public approval solves only one layer.

For leased development, the planning programme and landlord-consent programme should run together.

Local land charges are yet another category and should not be confused with private covenants

Public charges, planning obligations, conservation designations and other statutory matters can be recorded through local or governmental search systems depending on the jurisdiction.

Private title covenants live in a different legal architecture.

A serious property search therefore does not ask for “the restrictions” as if one database contains every constraint. It assembles evidence from the correct systems.

Planning conditions can expire or be discharged while covenants remain

A planning condition may be satisfied through construction or discharged by the authority.

A private covenant can continue to affect the land after the planning file is closed.

The timelines of public regulation and private rights are different, which is why a clean final inspection does not answer every title question.

A covenant can affect design even when everyone expects consent

Suppose a beneficiary is likely to approve an extension but wants it set farther from a boundary and constructed in specified materials.

The planning authority might have approved a larger building. The private consent process produces a smaller one.

Development design is therefore the intersection of all binding constraints, not the maximum envelope of one system.

Do not assume neighbouring breaches cancel your covenant

Seeing extensions, businesses or subdivisions elsewhere on the estate can be useful evidence about context, but it is not automatically proof that your restriction is unenforceable.

Other owners may have obtained releases. Their deeds may differ. The beneficiary structure may differ. Their works may be breaches that were never challenged.

Comparable development should trigger document research, not assumptions.

Do not ask the architect to solve a title interpretation

The architect can show how a proposed building relates to the site and can redesign around constraints.

The architect should not be expected to decide who legally benefits from a nineteenth-century covenant or whether a restriction is enforceable under local law.

Likewise, a lawyer should not be expected to calculate fire-appliance turning geometry.

Good development work gives each discipline the right question.

The planning strategy can sometimes help the covenant strategy

A well-reasoned public planning approval may demonstrate that the proposal is consistent with current policy, causes limited planning harm or serves a recognised public need.

That does not remove the covenant, but it can become part of the factual background in negotiation or any lawful modification process where relevant.

Public permission and private rights remain distinct, yet they can influence the commercial strategy around each other.

The reverse is also true: covenant resolution does not grant planning permission

A beneficiary may release a covenant allowing two dwellings.

The planning authority may still refuse the two dwellings because of access, design, heritage, flood risk, infrastructure or land-use policy.

Removing a private “no” does not create a public “yes.”

Development feasibility should contain a private-rights line, not merely a planning line

A feasibility spreadsheet often includes land price, construction, finance, professional fees, planning contributions and contingency.

Where title constraints exist, it should also account for:

legal investigation;
beneficiary tracing;
valuation advice;
consent fees;
release or variation consideration;
tribunal or court costs where applicable;
insurance if appropriate;
programme delay;
design change;
and the possibility that the restriction cannot be solved at an acceptable price.

A title problem is financially real even before anyone files a claim.

Worked example one: planning permission for the garden house

An owner obtains permission for a second dwelling in a large rear garden.

An old conveyance restricts the property to one private dwelling. The neighbouring owners may hold the benefit.

The owner now has a valuable planning permission but not yet an implementable project. The covenant is investigated and resolved before construction.

Worked example two: the home business

Local planning rules permit a low-impact home office.

The estate deed prohibits trade or business from the property.

The homeowner therefore needs to understand the private covenant separately rather than relying on zoning permissibility.

Worked example three: the extension requiring estate consent

A householder obtains planning permission for a two-storey side extension.

The transfer deed also requires the former estate owner’s written consent for external alterations. The estate owner agrees subject to revised materials and a modest design change.

The final building is shaped by two approval systems, each doing a different job.

Worked example four: the release that was not complete

A developer pays a former council landowner for a covenant release and assumes the site is clear.

Further title analysis shows neighbouring owners may also hold benefit under the estate scheme. The council could release only its own interest.

The lesson is structural: identify every potential beneficiary before treating one signature as universal clearance.

Worked example five: the apartment conversion in a leasehold building

A commercial tenant obtains planning permission to change use.

The lease prohibits residential use and major alterations without landlord consent.

The planning approval is valid, but the tenant cannot implement the proposal without solving the lease position.

Worked example six: the strata renovation

An apartment owner proposes works that fall within a planning exemption.

The Management Corporation rules still restrict alterations affecting common property and external appearance.

No planning application is needed, but another consent remains necessary. Exemption from one process is not exemption from every process.

Worked example seven: the upzoned neighbourhood

A city permits fourplexes across a low-density district to increase housing supply.

Some parcels are subject to private single-dwelling covenants. Others are not.

The public map now shows the same zoning on every parcel, but private development capacity remains uneven.

Worked example eight: the old covenant beside a new station

Land near a new transit station is rezoned for apartments.

A historic covenant restricts one plot to low-rise residential use. The land’s market value depends on whether that restriction can be lawfully modified or released.

The planning gain exists on paper. The title decides whether the owner can capture it.

The restrictive-covenant development audit

Correct title: Have the current title and plan been obtained?
Source deed: Which document contains the covenant?
Exact wording: Has the full restriction been read rather than paraphrased?
Burdened land: What land is actually subject to it?
Proposed act: Does the project fall within the prohibited activity?
Use restriction: Does it limit residential, commercial or other use?
Building restriction: Does it prohibit additional structures?
Subdivision: Does it restrict plot division or multiple dwellings?
Design control: Does it regulate height, materials or appearance?
Consent clause: Is development possible with written consent?
Consent holder: Who can validly give that consent today?
Benefited land: What land receives the benefit?
Current beneficiary: Who now owns or controls that benefited interest?
Multiple beneficiaries: Could more than one person enforce it?
Estate scheme: Is the covenant part of a wider neighbourhood scheme?
Age: When was the covenant created?
Historic context: Why was it imposed?
Neighbourhood change: How has the surrounding area changed?
Comparable plots: Have similar properties been developed, and under what documents?
Prior consents: Have earlier owners obtained approvals or variations?
Prior breaches: Are there historic breaches on the site?
Neighbour breaches: Are apparent comparable breaches actually comparable?
Enforceability: Has qualified legal advice assessed whether the covenant remains enforceable?
Public planning: Does the project separately require planning permission?
Planning status: Has public planning approval been obtained?
Planning condition: Are there public-law conditions unrelated to the covenant?
Other private rights: Are easements also present?
Lease: Does landlord consent apply separately?
Strata rules: Do Management Corporation or similar rules apply?
By-laws: Are there governance rules outside planning?
Local charges: Have relevant statutory searches been completed?
Release: Can the covenant be fully released by agreement?
Variation: Can wording be changed to permit the project?
Specific consent: Would one-off consent be enough?
Partial release: Is only part of the site or restriction being cleared?
All beneficiaries: Does the proposed deed bind everyone who matters?
Mortgagees: Is lender consent needed to vary the rights?
Consideration: Will the beneficiary require payment?
Valuation: Has that payment been estimated?
Statutory remedy: Is a tribunal, court or statutory modification route available locally?
Grounds: What legal tests apply to that route?
Objections: Who may object?
Evidence: What plans, valuations and witness material are needed?
Programme: How long could resolution take?
Planning expiry: Could permission expire before covenant resolution?
Construction contract: Is work prohibited until private rights are cleared?
Insurance: Is indemnity insurance appropriate, available and acceptable to advisers and lender?
Insurance conditions: Would approaching a beneficiary prejudice cover?
Financing: What covenant evidence does the lender require?
Purchase contract: Can the buyer terminate if the restriction cannot be solved?
Land option: Who bears covenant-resolution cost and risk?
Resale: Will the solution remain clear to future purchasers?
Registration: Must the release or variation be recorded?
Planning exemption: Even if public permission is unnecessary, do private rules still apply?
Implementation: Does the final design match both public approval and private consent?
Final question: After every public and private layer is checked, does the owner actually have the legal freedom to build and use what the drawings show?

The deeper planning principle: the city is governed by more than government

Town planning is often drawn as a public system: laws, plans, zoning maps, permits and infrastructure.

Real land is also governed through deeds, leases, easements, covenants, management rules, options, licences and contracts.

These private instruments can outlive governments, owners and planning policies. They can preserve a neighbourhood pattern, coordinate shared property, protect a commercial bargain—or obstruct a development that current public policy actively wants.

That is why serious land analysis needs more than a zoning map.

The planning map tells you what the public system permits. The title tells you what private rights may still require. A buildable project exists only where those systems can coexist.

Sources and further reading

Continue reading: The Easement Map · The Zoning Verification Letter · The Change of Use Test · Full Town Planning Series Index.