Vesting Tentative Maps: A Project-Reliance Framework for Filing, Approval, Final Mapping, and Permit Delivery

1. Confirm Eligibility and Local Filing Procedure

Start with the local subdivision ordinance, application forms, map-content requirements, fee schedule, filing instructions, and staff procedures. State law supplies the vesting framework; the local agency administers the filing and approval process through its adopted procedures.

Confirm:

• whether the project uses a tentative tract map or tentative parcel map;
• whether the local procedure applies to the project type and proposed development;
• the exact label required on the map face;
• additional application materials required for a vesting filing;
• the agency body responsible for completeness, environmental review, recommendation, and approval;
• whether the project requires concurrent legislative or discretionary actions;
• the local appeal route; and
• the ordinance governing the duration of rights after final-map recordation.

Local ordinances can contain filing details that affect the reliability of the record. The project’s checklist should cite the applicable ordinance section and current form version. Keep written agency direction with the filing package.

2. Fix the Controlling Baseline Date

Government Code section 66474.2 generally focuses tentative-map review on the ordinances, policies, and standards in effect when the application is determined complete. The project team should preserve the completeness determination and the complete package that produced it.

Create a baseline certificate that identifies:

• the completeness date;
• the agency letter, portal record, or other evidence;
• every document included in the complete application;
• each plan-set version and revision date;
• the development program reflected in the package;
• the property and phase boundaries;
• the requested approvals; and
• the local code, plan, policy, standard, manual, and fee materials collected as of that date.

Address section 66474.2’s exceptions in a separate schedule. Identify proceedings initiated and publicly noticed before completeness, together with the final measures adopted through those proceedings. Record applicant-requested changes that later become applicable to the project.

A date without the underlying source set creates an incomplete reliance record. Preserve the actual code provisions, policy documents, standards, maps, fee materials, and agency publications relied upon by counsel and the project team.

3. Define the Development Covered by the Map

The vested position follows the development presented through the approved map and associated project record. Build a concise project-definition schedule that covers:

• land uses;
• unit, lot, building, and nonresidential quantities;
• density and intensity;
• building envelopes and development areas;
• circulation and access;
• grading concept;
• drainage and utility systems;
• open-space and common-area structure;
• public and private improvements;
• phasing;
• affordable-housing commitments;
• community-facility and district assumptions;
• off-site work; and
• requested deviations, waivers, or legislative actions.

Compare this schedule with the CEQA project description, tentative map, entitlement plans, technical studies, development agreement, conditions of approval, and financial model. Resolve conflicts before the approval record becomes fixed.

Later teams should be able to determine whether a proposed change remains within the approved development and the substantial-compliance framework. That assessment belongs in a documented change review led by the appropriate agency, counsel, and professionals.

4. Build the Applicable-Rules Schedule

Create a source-by-source schedule of the ordinances, policies, and standards that may govern later development. Organize the schedule by workstream:

• permitted uses and development standards;
• subdivision and mapping requirements;
• design and architectural criteria;
• grading and drainage standards;
• streets and circulation;
• utilities and infrastructure;
• landscape and open-space requirements;
• fire, life-safety, and emergency-access requirements;
• housing and affordability requirements;
• environmental commitments and mitigation;
• fees, dedications, and improvement obligations;
• permit procedures; and
• phase-specific requirements.

For each item, record the source, section, version date, baseline status, applicable project component, later approval affected, responsible reviewer, and open interpretation issue.

The schedule should identify which items counsel considers within the statutory vesting framework, which items arise from separate approvals or agreements, and which items remain subject to later agency judgment. Avoid broad labels such as “all 2026 codes vested.” Use discrete source entries and a written legal assessment.

5. Identify Reserved Authority, Exceptions, and Later Conditions

Government Code section 66498.1 preserves local authority to condition or deny later actions where the statutory health-and-safety or state- and federal-law provisions apply. It also permits reasonable conditions on later approvals that are authorized by the ordinances, policies, and standards within the vested framework.

Create an exceptions and reserved-authority schedule that identifies:

• health-and-safety findings raised by the agency;
• new state or federal requirements;
• permit-specific findings and discretionary standards;
• building-code and technical-code questions;
• environmental-review and mitigation issues;
• conditions expressly deferred to later approvals;
• utility-provider and outside-agency requirements;
• changed factual conditions; and
• agreement provisions governing later rules.

Counsel should define the legal significance of each item. The project team should translate the analysis into schedule, cost, design, and decision impacts.

6. Reconcile the Approval Record

After approval, prepare an approval reconciliation that connects the vested baseline to the final resolution, map conditions, environmental action, associated entitlements, and any development agreement.

For each condition or approval term, identify:

• the operative language;
• the project component affected;
• the rule or source supporting the requirement;
• the milestone for compliance;
• the responsible party;
• required evidence;
• professional review;
• agency acceptance;
• effect on later permits; and
• status.

Capture appeal decisions, corrections, map revisions, and agency clarifications. Preserve the approved tentative map and every exhibit incorporated by reference. A clean reconciliation prevents later teams from relying on the application package while overlooking terms added during hearings or final action.

7. Preserve Rights Through Final-Map Approval

Section 66498.1 makes timely final-map approval a condition of continued vesting rights. Integrate the reliance framework with the map-life register and final-map workplan.

Track:

• the tentative-map expiration date;
• discretionary extensions and statutory adjustments;
• final-map phase boundaries;
• tentative-to-final conformance;
• title and ownership;
• signatures and consents;
• improvement plans;
• agreements and security;
• off-site rights;
• condition clearance;
• agency approvals; and
• final-map approval and recordation evidence.

Approval, recordation, and post-recordation rights can involve separate dates and legal effects. Counsel and the survey professional should confirm the controlling milestones for the project.

8. Control the Post-Recordation Period and Permit Bridge

Government Code section 66498.5 provides a local-ordinance period of one to two years after final-map recordation. For a project with several final maps, the initial period begins separately when the final map for each phase is recorded. The statute also addresses local-agency processing time after the first thirty days for certain complete grading, design, or architectural-review applications, a one-year extension request, and continuity through the expiration or extension of a building permit when a complete building-permit application is timely submitted.

Build a phase-specific calendar that includes:

• final-map recordation date;
• local post-recordation term;
• initial expiration date;
• grading, design, and architectural-review application dates;
• completeness evidence;
• agency processing intervals;
• extension application deadline;
• extension decision and appeal period;
• building-permit application date and completeness evidence;
• permit issuance, expiration, and extension dates; and
• responsible counsel and agency contacts.

Use conservative internal dates. Preserve proof of submission, completeness, agency processing, permit issuance, and extensions.

9. Route Project Changes Through a Formal Review

Project teams often want to use a later-adopted standard, modify the approved development, or seek a departure from the vested baseline. Government Code section 66498.2 provides an amendment path for securing a vested right to proceed under changed ordinances, policies, or standards before expiration. Section 66498.4 permits owners or designees to seek lawful approvals or permits that depart from the vested rules.

Open a change record that states:

• the proposed change;
• sponsor objective;
• affected map, phase, plan, study, approval, and permit;
• baseline rule;
• later rule or requested departure;
• required agency procedure;
• environmental-review implications;
• tentative- and final-map implications;
• condition, fee, infrastructure, budget, and public-report effects;
• legal position; and
• final decision and released documents.

Update the reliance register after agency action. Keep the original and amended baselines visible.

10. Preserve Continuity Through Assignment and Handoff

An acquisition, joint venture, builder transfer, lender review, or internal team change can separate the project from the people who created the vesting record. Prepare a reliance handoff package containing:

• the approved vesting tentative map and complete application;
• baseline certificate;
• applicable-rules schedule;
• initiated-change schedule;
• approval reconciliation;
• conditions and commitments register;
• map-life calculation;
• final-map record;
• post-recordation calendar;
• permit applications and completeness evidence;
• amendments and change decisions;
• agency correspondence;
• legal memoranda; and
• open reliance issues.

Identify the assignee or successor that holds the project interest and any agreement-specific assignment requirements. Counsel should confirm continuity of rights and obligations. The receiving team should acknowledge the current schedule and unresolved items.

Gate 1: Filing Path Confirmed

The map type, local procedure, labeling, application requirements, fees, approval bodies, and appeal route are documented.

Gate 2: Baseline Record Sealed

The completeness determination, complete application, operative source set, initiated changes, and applicant-requested changes are preserved.

Gate 3: Approval Reconciled

The approved map, resolution, conditions, environmental action, associated entitlements, and agreement terms use one controlled project description.

Gate 4: Final-Map Continuity Verified

Map life, phase boundaries, conformance, title, improvements, agreements, security, conditions, and final-map approval are current.

Gate 5: Post-Recordation Calendar Open

Each recorded phase has a confirmed vesting term, extension path, permit schedule, evidence plan, and conservative internal date.

Gate 6: Change Review Closed

Each material project or rule change has an agency path, legal assessment, cross-workstream review, decision, and released record.

Gate 7: Handoff Accepted

The current owner, builder, lender, consultant team, and internal leads have the operative reliance package and assigned open items.

Prepare the Baseline Certificate

Preserve the completeness notice, complete application index, plan versions, project description, and operative local source set.

Build the Applicable-Rules Schedule

Break the claimed baseline into discrete rules, policies, standards, approvals, exceptions, and later-permit questions.

Integrate Map and Permit Calendars

Connect tentative-map expiration, final-map approval, recordation, post-recordation periods, extension applications, and complete permit filings.

Open a Change-Review Protocol

Require every proposed project or regulatory change to identify its effect on the map, approvals, environmental record, conditions, fees, infrastructure, public reports, and delivery schedule.

Assemble the Reliance Handoff Package

Create a controlled package for acquisitions, financing, builder transfers, consultant changes, and phase releases.