How Town Planning Works | TPW-0117 — The Entitlement Clock: How Approvals Expire, Vest, Extend and Return Dormant Capacity to the Planning System

Series ID: TPW-0117

A planning approval is not always forever.

That sounds obvious until a city discovers thousands of homes approved on paper but not built, old permits relying on outdated standards, projects that began with a token trench only to preserve rights, or land whose nominal development capacity has been reserved for years by approvals that may never proceed.

Time is one of the hidden variables in development control.

A permit can be valid, invalid, vested, lapsed, commenced, extended, suspended, phased, renewed or superseded. Each status changes what the owner may do, what rules apply, what infrastructure capacity should be reserved and whether the planning authority can rely on the approval as part of its housing or growth pipeline.

This article calls that system the entitlement clock: the rules that determine how long development rights remain alive, what action keeps them alive, when later law can still apply, and when unused approvals return to the wider planning system.

The clock is jurisdiction-specific. England commonly requires development to begin within three years unless a different period is imposed. New South Wales guidance states that a development consent generally lasts five years unless another period is specified or physical commencement occurs. California subdivision law uses its own map-expiration and vesting structures, while other permit types have different periods again. The exact number is local. The planning problem is universal.

The reader job: understand why an approval needs both certainty and an expiry logic

This article explains why approvals expire, what vesting means, how commencement is defined, how extensions work, why dormant entitlements distort capacity planning, and how a city can avoid two opposite errors: destroying legitimate investment by changing the rules too easily, or freezing obsolete approvals indefinitely.

Neighbouring articles already own adjacent mechanisms. The Development Agreement owns long-term negotiated certainty. The Time Layer owns sequencing of the town. The Concurrency Test owns infrastructure capacity and timing. The By-Right Approval owns the distinction between objective compliance and discretion.

The Entitlement Clock owns a different question: how long should an approval control the future when the project has not yet fully arrived?

Approval creates option value

An approved project is more than a drawing.

It can increase land value, support financing, reduce development risk and allow the owner to proceed within an approved envelope.

That means approval creates an option.

The owner can build now, sell the land with the entitlement, wait for finance, wait for prices, redesign within permitted limits or sometimes extend the approval.

If the option never expires, land can carry old rights indefinitely even when public policy, infrastructure, hazard knowledge or building standards have changed.

If the option expires too quickly, complex projects cannot secure finance, complete engineering or coordinate utilities before losing the rights they spent years obtaining.

Expiration is not punishment

A time limit does not necessarily express distrust of the applicant.

It recognises that planning decisions are made under a set of assumptions that age.

The road network changes. Flood maps change. Building codes improve. Housing policy changes. A school opens. A station is cancelled. A habitat is discovered. The market shifts from offices to homes. A neighbouring parcel develops in a way that changes access.

An expiry rule gives the planning system a point at which an unimplemented approval may need to be reconsidered under current conditions.

The clock should begin at a clearly defined event

When does the approval period start?

The decision date? The date appeals expire? The date a permit becomes effective? The date a development agreement is executed? The date a final map is recorded?

A clock with an unclear starting point creates legal uncertainty before the project even begins.

The approval should state the effective date and the expiry date or the rule used to calculate it.

Different approvals can have different clocks

A large development often carries several approvals.

planning or land-use approval;
subdivision or tentative map;
site-plan approval;
environmental approval;
building permit;
grading permit;
utility connection;
heritage approval;
development agreement;
special operating permit.

If those clocks are not coordinated, a project can become legally incoherent: the site plan remains valid after the subdivision map lapses, or the environmental approval expires before the building permit is ready.

Complex projects need an approval schedule, not merely a folder of separate permits.

Commencement is the critical word

Many systems stop the approval from lapsing if development begins within the required period.

That immediately creates a new question: what counts as beginning?

Clearing vegetation? Driving one pile? Pouring one footing? Constructing a permanent road? Completing a substantial part of the approved work?

If the threshold is too weak, applicants can make a token intervention solely to preserve an approval indefinitely. If the threshold is too demanding, legitimate projects can lose permission even after meaningful capital has been committed.

The definition of commencement should reflect the legal system and the planning purpose of the time limit.

Token commencement creates zombie permissions

A zombie permission is alive in law but inactive in the city.

A small amount of work preserves the entitlement, then the site sits untouched for years.

This can create several planning problems. Old standards remain embedded in the approval. Housing-pipeline numbers exaggerate delivery. Infrastructure capacity may remain reserved. Neighbours expect construction that never arrives. The land market prices the site as entitled even though the approved product may no longer be viable.

Some systems address this through substantial-commencement tests, staged deadlines, completion requirements or new review when long inactivity occurs.

Vesting answers a different question from expiration

Expiration asks whether the approval remains alive.

Vesting asks which rules govern the project while it remains alive.

A vested approval may preserve certain development rights against later zoning changes or policy shifts. The exact point at which rights vest varies significantly across legal systems and permit types.

Vesting protects reliance. An owner should not spend heavily on a legally approved project only to discover that the fundamental land-use rules changed after every major commitment was made.

But vesting is not necessarily immunity from every future law.

Safety codes often continue to evolve

A project may have vested land-use rights while still needing to comply with later building, fire, accessibility or health standards at the time of permit issuance.

That boundary is jurisdiction-specific and can be legally complex.

The planning principle is to distinguish the parts of the project that need investment certainty from the public-safety systems that legitimately evolve.

Extensions are not all the same

An extension can be automatic, administrative, discretionary or statutory.

Automatic extensions may apply during emergencies, litigation, government moratoria or specified statutory periods. Administrative extensions may be granted if objective criteria are met. Discretionary extensions may require a public body to decide whether circumstances justify additional time.

Each model balances certainty and policy review differently.

The extension test should ask what has changed

A request for more time should not necessarily require the entire project to be approved from zero.

But the authority should ask whether material conditions changed during the approval period.

Has the zoning changed?
Has a new hazard map altered the site?
Has infrastructure capacity been consumed by other development?
Has the road network changed?
Has a protected resource been identified?
Has the project remained substantially the same?
Has the applicant made meaningful progress?
Would an extension prejudice another approved public project?

The extension process should focus on the reasons time matters rather than mechanically repeating every earlier review.

Complex projects need longer clocks

A two-home subdivision and a twenty-year regeneration district do not have the same pre-construction path.

Large projects may need land assembly, environmental remediation, utility relocation, financing, institutional agreements and phased infrastructure before vertical construction begins.

Time limits should therefore be calibrated to project complexity or supplemented by development agreements and phased approvals where the law permits.

A clock that is too short can force artificial commencement rather than genuine implementation.

Simple projects should not receive eternal option value

The opposite problem also exists.

A straightforward infill approval may require little infrastructure and modest design work. Repeated extensions can allow an owner to hold old permissions for speculative value while the community’s rules change around the site.

The extension framework can consider project complexity, progress and reliance rather than treating every entitlement identically.

The housing pipeline should distinguish approved from buildable

Governments often announce that tens of thousands of homes are “approved”.

That number can include projects with no finance, expired utility offers, unresolved conditions, ownership disputes or economically obsolete designs.

A more useful pipeline separates stages.

zoned capacity;
application submitted;
planning approval granted;
approval vested or final;
conditions substantially cleared;
building permit issued;
construction commenced;
under construction;
completed.

The entitlement clock determines whether a project remains in the pipeline or should return to the pool of potential future applications.

Dormant approvals can consume infrastructure capacity

Suppose a wastewater basin has capacity for 5,000 additional homes.

An old approval reserves capacity for 2,000 homes but has shown no meaningful progress for eight years.

Should new housing be refused because the old project might still use that capacity someday?

The answer depends on the legal status of the reservation, but the planning system should not ignore the problem.

Capacity reservation and entitlement expiration need to speak to one another. When approvals lapse or reservations expire, unused capacity should return to the ledger.

An extension should not silently extend every associated reservation

A land-use approval may deserve more time even when a utility reservation does not.

Water, sewer, school or road capacity may be governed by separate agreements and queues.

Extension decisions should therefore identify which associated rights and reservations continue and which need separate renewal.

Otherwise one simple planning extension can unintentionally lock scarce infrastructure for years.

Expiration dates can influence land prices

A site with ten years of remaining approval has different option value from the same site with three months remaining.

Extensions can therefore transfer economic value.

That does not make extensions improper. It means the policy should be predictable so owners, lenders and buyers can price risk rather than relying on political discretion.

Shorter clocks can encourage delivery but can also encourage gaming

Some planning systems use shorter commencement periods to discourage land banking and unimplemented permissions.

That can work where delay is discretionary.

It can also encourage minimal commencement solely to preserve the approval, or rush construction before finance and infrastructure are ready.

The rule should target the behaviour it actually wants to change.

Longer clocks can support complex delivery but can freeze old policy

A long approval period improves certainty.

It also increases the chance that the project will be built under rules written for a different moment.

The longer the term, the more important it becomes to state which later health, safety, environmental or technical standards can still apply.

Development agreements often handle this explicitly because long projects need a negotiated boundary between certainty and regulatory evolution.

Economic shocks justify system-wide responses better than ad hoc mercy

Recessions, pandemics, supply-chain crises and sudden interest-rate shocks can stall many projects at once.

If every approval requires an individual extension hearing, staff time is consumed deciding the same systemic problem repeatedly.

Some governments therefore enact temporary statutory extensions during exceptional periods. New South Wales retained transitional consent-extension rules after the pandemic, while California has periodically enacted broad subdivision-map extensions in response to economic conditions.

Systemic shocks often deserve systemic rules.

Litigation can pause the clock

An applicant should not necessarily lose approval time while a lawsuit prevents the project from proceeding.

Some legal systems toll or suspend expiration during specified litigation or government-imposed moratoria.

The rule should state when suspension begins, when it ends and how much time remains afterward.

A paused clock is different from a restarted clock.

Phased projects need phase-specific logic

A master approval may cover ten phases.

If Phase 1 is built, should that preserve all later phases forever?

Sometimes yes, where a development agreement or statute deliberately provides long-term vesting. Sometimes no, where later phases must meet milestones or record separate maps.

The approval should avoid ambiguity. State whether commencement of one phase preserves the whole project, only that phase, or the project subject to later deadlines.

Extension requests are planning data

If one project asks for more time, that may be project-specific.

If half the city’s housing approvals request extensions, the system is revealing a wider problem.

Maybe interest rates changed. Maybe utility connections are too slow. Maybe the approved product is no longer viable. Maybe permit conditions take years to clear. Maybe the zoning permits density that construction economics cannot support.

Track extension reasons. They are feedback about delivery.

Expiration can improve data quality

A pipeline full of dead approvals makes planning statistics unreliable.

When an approval clearly lapses, the city can remove it from committed supply, release capacity and update land assumptions.

This creates a more honest distinction between theoretical, approved and deliverable growth.

But forced expiration can destroy useful sunk work

Planning applications can involve years of surveys, engineering, environmental analysis and public review.

Requiring a full restart after a short delay can duplicate work without improving the outcome.

A mature extension process can preserve still-valid analysis while requiring targeted updates where conditions changed.

The goal is current evidence, not ritual repetition.

A renewal is different from an extension

An extension keeps the existing approval alive for longer.

A renewal can be structured as a new decision that revalidates the project under some updated requirements.

The distinction matters because renewal can create a checkpoint for changed policy while avoiding a complete restart.

Not every legal system uses those labels the same way, but the planning design choice remains useful.

Material project changes may deserve a new clock

An approved 200-room hotel becomes 500 apartments.

That is not merely more time.

The use, demand profile, infrastructure and public impacts have changed. A modification process should decide whether the revised project remains substantially within the original approval or requires a new entitlement.

Extension rules should not become a route for converting old approvals into fundamentally new projects without appropriate review.

The clock should be visible to everyone

A public planning portal should show approval date, effective date, expiry date, extension history, commencement status and major phase deadlines.

Owners should not need a lawyer to discover whether their entitlement is still alive. Neighbours should not need to search archived meeting minutes. Utility agencies should not reserve capacity against approvals whose status is unknown.

Time status is core permit data.

Digital systems can automate the boring part

Once the legal rules are clear, software can calculate deadlines, send notices and flag approaching expirations.

It can also identify approvals where no building permit, inspection or phase milestone has occurred for years.

Automation should not decide contested legal questions about vesting or commencement. It should make the timeline visible so professionals can focus on the cases that actually require judgment.

A worked example: 1,200 approved homes that never start

Imagine a housing project approved during a strong market.

The approval lasts four years. The project reserves sewer capacity and appears in the city’s housing pipeline. Interest rates rise, the developer pauses, and no building permit is filed.

Six months before expiry, the owner requests a three-year extension.

A good extension review asks several separate questions.

Is the land-use policy still current?
Did flood, wildfire or infrastructure conditions materially change?
Has the project design changed?
Is the delay plausibly temporary?
Should sewer capacity remain reserved for the full project or only for an early phase?
Should updated technical standards apply even if the land-use entitlement is extended?
What progress milestone should be required before any further extension?

The result might be an extension of the planning approval combined with a shorter utility reservation and a requirement to obtain the first building permit within eighteen months.

One clock does not have to control every part of the system.

Another worked example: the technically commenced but abandoned project

A commercial project begins foundation work days before its permission would lapse.

Construction then stops for twelve years.

During that period, the area becomes a residential district, flood standards change and a new transit line opens.

If the legal system treats the original commencement as preserving the permission indefinitely, the city may have limited power to revisit the old approval.

This example shows why commencement definitions and abandonment rules deserve deliberate policy attention before the unusual case appears.

A practical entitlement-clock audit

Approval type: Which permit or entitlement is being timed?
Effective date: When does the clock begin?
Term: How long is the initial approval valid?
Commencement: What action prevents lapse?
Substantiality: Can token work preserve the approval indefinitely?
Vesting: Which rules are fixed during the approval period?
Later codes: Which health, safety or technical rules can still change?
Extension: Is more time automatic, administrative or discretionary?
Extension criteria: What evidence must the owner provide?
Changed conditions: Which policy, hazard or infrastructure changes trigger reconsideration?
Phasing: Does one phase preserve the whole project or only itself?
Litigation: Does legal challenge suspend the clock?
Moratorium: Does government-imposed delay toll the approval?
Emergency: Can systemic shocks produce automatic extensions?
Reservations: Do water, sewer, school or transport capacities expire on the same schedule?
Pipeline: How is the approval counted in housing and growth forecasts?
Ownership transfer: Does sale affect the approval or clock?
Modification: How much can the project change without requiring a new entitlement?
Renewal: Is there a middle route between full extension and complete reapplication?
Data: Is expiry status visible in the public permit record?
Feedback: Are repeated extension requests analysed for systemic delivery problems?

The entitlement clock is an agreement between planning and time

Development needs certainty.

Cities need the ability to adapt.

Those goals are not opposites. They are the two sides of an honest approval system.

The owner needs to know that a legitimate approval will not evaporate arbitrarily after investment begins. The public needs to know that unused approvals will not freeze old policy and scarce infrastructure forever.

The entitlement clock creates the boundary.

It says how long certainty lasts. It defines meaningful commencement. It explains which rules vest. It creates a route for justified extensions. It releases dormant capacity when rights lapse. It gives exceptional shocks a systemic response. It turns the vague idea of an “approved project” into a time-aware state that planners, utilities, lenders and residents can understand.

A planning approval should be durable enough to be financeable and temporary enough to remain connected to the city that actually exists when the project finally arrives.