How Town Planning Works | TPW-0183 — The Permit Expiration Clock: How Planning Approvals Stay Alive, Get Extended, or Quietly Die Before Construction Starts

Series ID: TPW-0183

A planning approval can exist on paper and disappear before a shovel touches the ground.

A developer wins a site-plan approval, subdivision, conditional use or other land-use permit. Financing takes longer than expected. Construction prices rise. A partner changes. A utility connection is delayed. The building permit is never filed.

Two years later, the owner assumes the approval is still waiting.

The planning code may say otherwise.

Most mature development systems impose some form of expiration, commencement, utilisation, vesting, extension or inactivity rule so approvals do not remain alive forever when nothing is built.

Current practice shows how active these questions remain. San Luis Obispo County operates a current land-use permit time-extension process for approvals that have not yet expired. Santa Cruz County’s recent records show applicants seeking specific one-year extensions of commercial development permits and master site plans. A 2026 Sausalito public notice concerns a one-year extension of approved design review and a vesting tentative map. Gig Harbor’s current permit notices state defined approval periods and extension routes. Local codes elsewhere use shorter or longer clocks and different commencement tests.

The details vary by jurisdiction and approval type. The planning problem is universal.

The reader job: understand when an approval stops being a current planning decision

This article explains why planning approvals expire, what counts as commencement, how extensions work, how appeals and litigation can affect the clock, how phased projects should be treated, what happens to dormant rights, and how authorities can avoid both indefinite entitlements and unfair expiration during delays outside an applicant’s control.

The ownership boundary matters. The Planning Condition Lifecycle owns how conditions become dischargeable and complete. The Planning Appeal owns review of land-use decisions. The Development Agreement owns long-term negotiated certainty and phasing. The Nonconforming Use owns continuation of lawful development after rules change.

The Permit Expiration Clock owns a different question: after approval is granted but before the project becomes established, how long does the permission remain usable and what must happen to keep it alive?

Expiration exists because planning decisions are made in a time context

A permit is based on facts that can change.

Traffic conditions change. Infrastructure capacity is consumed. Flood maps are updated. Housing policy changes. Neighbouring development alters the context. Building and fire codes evolve. A comprehensive plan is amended. A road project that justified an access arrangement is cancelled.

If a project approved in 2012 can begin unchanged in 2042 without any review, the planning authority may be implementing a decision made for a city that no longer exists.

Expiration therefore protects the currency of the planning decision.

But expiration also creates investment risk

Development takes time.

Land acquisition, environmental review, utility design, finance, procurement and building permits can consume years. Major infrastructure projects can be delayed by agencies outside the developer’s control.

If approval periods are too short, applicants may rush bad construction sequencing merely to preserve a permit or repeatedly seek extensions that consume public staff time.

The expiration period must therefore balance two forms of certainty: the public needs stale approvals to lapse; the applicant needs enough time to act on a real approval.

The clock should start from an event everyone can identify

Does the approval period begin when the board votes? When the written decision is issued? When the appeal period ends? When litigation finishes? When conditions are accepted?

A vague starting point creates avoidable disputes.

The decision notice should state the effective date, expiration date where practicable, and any event that changes that date under local law.

San Luis Obispo County’s current guidance points applicants back to the Notice of Final Action or Final Findings and Conditions for the approval date used to determine expiration. This is good administrative design: the clock should be visible in the same record that creates the approval.

Different approvals can have different lifespans

A small zoning permit may need only enough time to obtain a building permit.

A tentative subdivision map may need years because infrastructure design and final platting are complex. A planned unit development may be phased. A conditional use may require the activity to begin within a period. A development agreement may establish a much longer term.

One universal expiration period can therefore be crude.

The code can classify approval types and give each a period proportionate to the work reasonably needed to activate it.

The hardest question is what counts as commencement

Suppose a permit expires unless development “commences” within two years.

Is filing a building permit enough? Issuance of that permit? Clearing the site? Pouring one footing? Completing foundations? Beginning the approved use? Spending a minimum amount?

If the code does not define commencement, applicants can perform token work simply to keep an approval alive.

A credible commencement test should correspond to meaningful implementation of the approved project.

Building permit issuance is a common but incomplete proxy

Some zoning permits remain valid if the applicant obtains a building permit within the stated period.

This is easy to administer because the event is documented.

But obtaining a building permit does not always mean construction will proceed. Building permits themselves can expire. Large projects can hold permits while finance remains uncertain.

The planning code should decide whether building permit issuance permanently secures the land-use approval, merely extends it, or must be followed by active construction.

Token construction should not preserve a major entitlement forever

A developer digs one trench the day before expiration and claims the 2,000-home master plan has commenced.

That may satisfy some legal regimes and fail others.

From a planning perspective, the problem is obvious: a trivial act should not necessarily freeze decades of development rights if the code’s purpose is to ensure timely implementation.

Definitions can require substantial commencement, active construction, completion of a named phase, expenditure thresholds, permit milestones or other evidence of real implementation where legally appropriate.

Vesting and expiration are related but not identical

Vesting generally concerns which regulations apply to an approved or properly filed project and when rights become protected against later rule changes.

Expiration concerns how long the approval remains usable if required action does not occur.

A project can have vested rights under one doctrine and still face an expiration rule under another, depending on local law.

Planning staff should not use the words interchangeably. The file should identify what is vested, what deadline applies and what action preserves the approval.

Extensions exist because delay is not always abandonment

A project can remain real while missing the original deadline.

Utility design takes longer. A lender pauses financing. A public road project is delayed. Litigation prevents action. A disaster disrupts construction markets. The applicant may have invested substantially while circumstances outside its control slowed implementation.

A time-extension process allows the authority to decide whether more time is justified without pretending the original approval should remain alive indefinitely.

San Luis Obispo County’s current system requires the extension request before the permit expires. Santa Cruz County records show specific development permits moving through formal time-extension applications. Sausalito’s 2026 notices likewise demonstrate extensions being considered publicly for a long-running residential project.

An extension request should arrive before expiration

This is the cleanest administrative rule.

If the permit is still alive, the authority decides whether to extend an existing approval.

If it has already expired, the legal question can become different: can the authority revive a dead permit, or must the applicant file a new application?

Late extension requests can therefore create disputes over authority rather than merits.

Digital systems should alert applicants well before expiration: 180 days, 90 days, 30 days, or whatever intervals fit the approval type.

Submitting the extension can toll the clock where the law allows

Suppose the applicant files a valid extension request one month before expiration but the planning board cannot hear it for three months.

It can be unfair for the permit to die while the applicant waits for the government to process a timely request.

Some systems therefore preserve the approval while a timely extension application is pending. San Luis Obispo County currently explains that a timely submitted request can remain eligible for processing even when the hearing occurs after the original expiration date, subject to its stated requirements.

If tolling applies, the code should state it explicitly.

Extension criteria should be more than “the applicant needs more time”

Almost every applicant seeking an extension needs more time.

The authority should ask why the original approval remains a sound planning decision.

Have zoning or plan policies materially changed?
Have hazard maps or infrastructure conditions changed?
Have approval conditions been satisfied or become obsolete?
Has the applicant made meaningful progress?
Was delay caused by government processing, litigation or circumstances outside the applicant’s control?
Would extending the permit prejudice later applicants relying on scarce infrastructure capacity?
Is the project still substantially the same?

Extension should be a planning judgment about the continuing validity of the approval, not an automatic subscription renewal.

But extensions should not become a second full application every time

If nothing material has changed and the applicant has made genuine progress, repeating every study, notice step and hearing from the beginning can waste resources.

The extension process can focus on changed circumstances.

This is a proportionality question. The more time that has passed and the more the policy environment has changed, the more substantive the extension review may need to become.

Extension length should have a reason

Why one year? Why three?

An extension should be long enough for the applicant to complete the next meaningful milestone.

If the remaining obstacle is a building permit expected within six months, a short extension may be sufficient. If the project depends on a funded regional infrastructure project opening in two years, a longer period may be rational.

A standard extension period is administratively simple, but decision-makers should understand what it is intended to accomplish.

Limit the number of routine extensions

A project receiving a one-year extension every year for fifteen years has effectively acquired a permanent entitlement through serial administration.

Codes can limit the number of administrative extensions, require later extensions to return to the original decision-maker, or require a new application after a maximum period.

The escalation reflects increasing uncertainty as the original planning context ages.

Phased projects need a separate expiration architecture

A 500-lot subdivision cannot be treated like a small shop permit.

Does commencement of Phase 1 preserve all later phases? Must each phase begin within a separate period? Does approval of a final plat preserve only the land included in that plat? What happens if Phase 2 remains dormant for ten years?

The code or development agreement should answer these questions before the first phase begins.

Otherwise the city can discover decades later that a small amount of early work allegedly preserved an enormous unbuilt entitlement.

Each phase should have a viable interim state

Expiration planning is also physical planning.

If the project stops after the first phase, are roads connected? Is drainage complete? Are temporary cul-de-sacs safe? Did promised park space arrive? Are utilities maintainable?

A phasing plan should not assume every later phase will certainly arrive.

The possibility of expiration makes interim completeness important.

Appeals can complicate the expiration clock

An applicant may be legally unable or commercially unwilling to begin construction while an approval is under appeal.

If the permit clock continues running through a long appeal, the applicant can lose much of the implementation period before finality.

Some jurisdictions toll approval periods during appeals or litigation; others calculate effectiveness differently.

The rule should be explicit. The current Planning Appeal article explains why the appeal period itself is part of the approval lifecycle.

Government-caused delay needs deliberate treatment

Imagine a development cannot obtain its building permit because a public utility has not completed a connection agreement it promised to process within six months.

Allowing the land-use approval to expire solely because another government body missed its deadline can be difficult to justify.

Extension criteria can recognise documented agency delay, moratoria, court injunctions or other events beyond the applicant’s control.

This should be evidence-based. “Government delay” should identify the agency, required action, expected timeline and steps the applicant took to advance it.

Market delay is real but different

Interest rates rise. Buyers disappear. Construction costs make the project temporarily infeasible.

Market conditions can justify an extension in some systems, but they do not automatically create a right to hold old entitlements indefinitely.

The authority should ask whether the project remains likely to proceed and whether maintaining the approval interferes with new planning objectives, infrastructure allocation or scarce land.

Capacity reservations should not survive forever without milestones

An approved project may reserve sewer, water, school or transport capacity.

If the project remains dormant for ten years while preserving that capacity, newer projects can be blocked by demand that exists only on paper.

Expiration and concurrency therefore need to speak to each other.

The current Concurrency Test article explains why capacity ledgers need reservation-expiry rules. When an entitlement lapses, associated capacity should return to the available pool unless another lawful instrument preserves it.

Do not confuse a dormant approval with an abandoned nonconforming use

These are different legal states.

A dormant approval concerns development that has not yet been established under the permit. A nonconforming-use abandonment rule concerns an existing lawful use that later stops.

The timelines, evidence and rights can be completely different.

Planning records should label them precisely rather than using vague language such as “grandfathered permit” or “inactive approval.”

Permit expiration can reveal speculative approvals

Some approvals are pursued mainly to increase land value or preserve optionality.

There is nothing inherently improper about obtaining approval before finance is complete. But large pipelines of dormant entitlements can distort housing and infrastructure forecasts.

A city may report 30,000 “approved homes” even though half are attached to projects that have made no progress for years and may expire soon.

Planning dashboards should distinguish active, commenced, extended, dormant, expired and completed approvals.

An expired permit should be visibly expired

Property records often continue displaying old approvals without status.

A buyer sees “Site Plan Approved 2018” and assumes it remains valid.

The digital file should show the lifecycle: approved, effective, appealed, commenced, extended, expired, superseded or complete.

Expiration should update the public-facing property record automatically.

Revival after expiration should not be improvised

An applicant arrives two weeks after the deadline and asks staff to “just extend” the permit.

If local law does not authorise revival, staff cannot create the power through sympathy.

The code should state whether expired approvals can be reinstated within a grace period, require a new application, or have another formal route.

This is important for equal treatment. The well-connected applicant should not receive an informal resurrection that the next applicant is denied.

A new application after expiration should use the current rules unless law says otherwise

One purpose of expiration is to prevent stale approvals from bypassing later planning changes.

If a permit lapses and a new application is required, the new filing ordinarily enters the current regulatory system subject to whatever vested-rights or transition provisions local law recognises.

The applicant may reuse studies or drawings where still relevant, but should not assume the old approval criteria remain controlling.

Extensions should examine policy change at the right scale

Not every new policy justifies denying an extension.

A minor update to landscaping standards may be irrelevant to the continued validity of a large housing approval. A new wildfire hazard map affecting the entire site can be highly relevant.

The decision-maker should identify material changes, not simply count how many code amendments occurred since approval.

The extension test should ask whether the original planning conclusions remain reliable enough for more time to be granted.

Conditions may need updating without reopening the entire approval

An old condition may require connection to a road design that has since changed or a utility standard that no longer exists.

An extension process can sometimes modify technical conditions while preserving the core approval, if local authority permits.

The modification should remain within the scope of the extension power. A major density increase or new use should not be smuggled through as a “time extension.”

Public notice may be appropriate for major extensions

A one-month administrative extension of a small permit and a five-year extension of a controversial master plan are not the same public decision.

Some jurisdictions require hearings or notice for specified extension types. Sausalito’s 2026 public notices include a zoning administrator hearing for an extension of a substantial residential project.

The code should match process to consequence. Extensions that materially prolong major entitlements may justify public visibility even when the underlying approval has already been debated.

Automatic emergency extensions should be explicit and temporary

Major disasters, pandemics, wars or government shutdowns can disrupt thousands of permits simultaneously.

Legislatures or local governments may respond with blanket tolling or automatic extension.

That can be more efficient than processing thousands of identical extension requests.

The emergency rule should state which approvals qualify, how much time is added, whether subsequent individual extensions remain available and when the emergency provision ends.

Do not extend an approval merely because staff failed to track it

A permit can sit unnoticed in a database until somebody asks about it years later.

Administrative neglect does not necessarily preserve an approval that expired by operation of law.

The system should track dates automatically so staff and applicants receive alerts before the issue becomes historical reconstruction.

Expiration should be managed prospectively, not discovered archaeologically.

The property buyer needs to know the clock

Land can be sold on the assumption that an approval has value.

A buyer should confirm the approval date, current expiration date, extensions already granted, commencement status, outstanding conditions, appeal history and whether the approval transfers with the property.

A permit with thirty days remaining is economically different from one with three years.

Planning due diligence should treat time as part of the entitlement.

Lenders also need the permit lifecycle

A lender financing construction needs assurance that the land-use approval will remain valid through closing, building-permit issuance and commencement.

If an extension is discretionary and not yet granted, that is financing risk.

Official zoning or permit-status letters can make the current lifecycle visible without forcing lenders to interpret decades of planning minutes.

Serial ownership changes should not reset the clock automatically

If a planning approval runs with the land, selling the property should not ordinarily create a new full implementation period unless the law expressly says so.

Otherwise an entitlement could be preserved indefinitely through transfers between related entities.

The expiration date should attach to the approval, not to the identity of the latest owner.

Completion and commencement are different milestones

Some approvals require commencement by one date and completion by another.

This can prevent token commencement followed by years of abandoned construction.

Completion rules need flexibility for large projects and real construction delays. The authority can use phase-specific deadlines, continuous-construction requirements or extensions where justified.

The purpose is to avoid a half-built site becoming a permanent state merely because the first deadline was technically met.

Inactivity after commencement can matter

A project may start and then stop.

If construction pauses for several years, does the approval remain alive?

Some codes include inactivity or abandonment rules for development approvals. Others rely on building-permit expiration, nuisance powers or specific phase deadlines.

The trigger should be measurable. A vague requirement for “continuous progress” invites disagreement unless the code defines what progress means.

Expired approvals should inform code maintenance

Why do permits expire?

If one type of approval repeatedly expires before applicants can obtain another agency’s permit, the sequence may be unrealistic. If extensions are routine because the standard period is always too short, lengthen it. If projects sit dormant because infrastructure is unavailable, connect planning approvals more closely to capital programming.

Expiration data is not only administrative housekeeping. It reveals where the development system loses momentum.

A worked example: the 200-home project and the delayed pump station

Imagine a 200-home project receives site-plan approval with a two-year expiration period.

The wastewater authority confirms that a public pump-station upgrade must be completed before more than 80 homes can connect. The upgrade was scheduled for the following year but public procurement delays push completion eighteen months later.

The developer obtains building permits for the first phase and constructs 60 homes. The later phases cannot proceed because the public pump station is not ready.

A simplistic expiration rule might say the entire approval is safe because construction started. Another might say all unbuilt phases expire at year two. Neither necessarily matches the planning problem.

A better system asks what the approval and phasing rules actually say. Phase 1 can be recognised as commenced. Later phases can receive a documented extension tied to the funded public infrastructure delay. The extension can preserve the approved housing programme while updating technical conditions that changed during the delay.

The planning authority neither punishes the project for a public delay nor grants an indefinite entitlement.

A second worked example: the dormant shopping centre approval

A large retail centre was approved eight years ago. No building permit was obtained. The original two-year term was extended twice. The site remains vacant.

Meanwhile, the city adopts a new station-area plan calling for housing and mixed-use development. Bus routes change. Parking policy changes. A new flood model affects part of the site.

The owner requests another five-year extension.

This is precisely why extension review exists.

The authority should not ask only whether the owner still wants the shopping centre. It should ask whether preserving the old approval remains consistent with the current planning context and whether the code authorises another extension. If not, expiration allows the site to re-enter the current plan rather than remain permanently governed by an eight-year-old decision.

A permit expiration audit

Approval type: What permit, plan, plat or entitlement was granted?
Authority: What law or code controls its lifespan?
Effective date: When did the approval become effective?
Expiration date: What is the current deadline?
Start event: What event started the clock?
Commencement: What specific action keeps the approval alive?
Building permit: Is issuance enough, or must construction actually begin?
Substantial work: Does token construction preserve the entire entitlement?
Vesting: Which rules are protected and how does vesting interact with expiration?
Appeals: Does appeal or litigation toll the approval period?
Extensions: How many are allowed and for how long?
Deadline: Must an extension request be filed before expiration?
Pending request: Does a timely extension filing keep the permit alive while review occurs?
Criteria: What findings govern extension approval?
Changed policy: Have zoning, plans, hazards or infrastructure materially changed?
Progress: What meaningful implementation has occurred?
External delay: Was delay caused by government, litigation or another documented dependency?
Market delay: Is the project still realistically capable of implementation?
Phases: Does commencement of one phase preserve others?
Capacity: Is public infrastructure being reserved for a dormant project?
Conditions: Are approval conditions still relevant and administrable?
Modification: Is the applicant seeking project changes that exceed extension authority?
Notice: Does the extension require public notice or hearing?
Transfer: What happens if ownership changes?
Inactivity: Can an approval lapse after construction begins but then stops?
Record: Is current status visible to owners, buyers, lenders and staff?
After expiration: Can the permit be revived, or is a new application required?
Learning: Do repeated extension patterns show that the standard approval period or review sequence needs reform?

The expiration clock protects both planning relevance and development certainty

An approval is a decision made in time.

The applicant needs enough time to turn it into a real project. The public needs confidence that an approval cannot lie dormant forever while plans, hazards, infrastructure and policy move around it.

A good expiration system therefore does several things at once.

It starts the clock from a visible event. It gives different approvals realistic lifespans. It defines meaningful commencement. It allows extensions for genuine delay without turning them into automatic permanence. It distinguishes vesting from expiration. It handles appeals and government-caused delay explicitly. It gives phased projects separate logic. It releases unused infrastructure capacity when dormant projects die. It marks expired approvals clearly in the public record. And it uses extension data to improve the development process.

The strongest rule is neither “once approved, always approved” nor “miss the date by one day and start from zero regardless of circumstance.”

The strongest rule is a legible lifecycle: approval, effective date, implementation period, meaningful commencement, justified extension where appropriate, and a real endpoint when the project no longer belongs to the planning decision that created it.