Final Map Readiness: A Workplan for Approval, Recordation, and Handoff

1. Define the Map Scope and Controlling Record

Begin with a final-map charter that identifies:

• the approved tentative map and all approved revisions;
• the tentative-map approval and expiration dates;
• extensions, development-agreement provisions, moratoria, litigation effects, or other items affecting map life, as confirmed by counsel and the agency;
• the portion of the tentative map included in the proposed final map;
• the project phase, lots, units, parcels, streets, easements, and facilities within that portion;
• the target approval and recordation dates;
• the local agency and county offices involved; and
• the project representative authorized to coordinate the package.

Where the project anticipates several final maps, identify the sequence and the assumptions connecting them. Section 66456.1 permits multiple final maps when the statutory conditions are satisfied and preserves local authority to impose reasonable conditions related to multiple filings.

Readiness output: a one-page map charter with scope, authority, expiration, sequence, target date, and responsible parties.

2. Build the Tentative-to-Final Conformance Matrix

Create a matrix that traces each material feature of the approved tentative map and its conditions into the final-map package. The matrix may address:

• boundaries, lotting, parcel configuration, and numbering;
• streets, access, dedications, and easements;
• grading, drainage, utilities, and improvement concepts;
• open space, common areas, public lots, and facilities;
• phasing and multiple-map assumptions;
• off-site improvements and property rights;
• conditions due before map approval or recordation;
• notes, statements, certificates, and map references; and
• approved revisions or substantial-conformance determinations.

Identify the controlling source, final-map location, responsible preparer, agency reviewer, open issue, and closure evidence for each item. A difference between the tentative and final map should enter the project’s change-review process early enough for agency, legal, surveying, engineering, environmental, and sponsor review.

Readiness output: a conformance matrix linked to the conditions register and current map-check comments.

3. Reconcile Title, Ownership, and Map Interests

Final mapping can create, dedicate, reserve, acknowledge, or depict interests that depend on the current title record. Government Code section 66436 generally requires a signed and acknowledged consent statement from parties holding record title interests, subject to its stated exceptions and procedures.

Coordinate the surveyor and title team with counsel and the sponsor to identify:

• the legal owner and vesting shown in current title materials;
• deeds of trust and other title interests requiring attention;
• existing easements, rights-of-way, restrictions, mineral interests, and public or utility interests;
• dedications, offers, reservations, abandonments, and new easements shown on the map;
• signatures, acknowledgments, subordinations, consents, and omission procedures;
• documents that must record before, concurrently with, or after the map; and
• title changes that could affect execution or the map record.

Maintain a signature-and-interest matrix showing each party, interest, required action, document form, responsible coordinator, execution status, and recording sequence.

Readiness output: a current title-and-signature plan tied to the exact map version and recording package.

4. Coordinate Plans, Specifications, and Technical Map Checks

Government Code section 66456.2 addresses improvement plans prepared by a registered civil engineer for public improvements required as a condition of final-map or parcel-map approval. Local procedures determine plan-check sequence, technical standards, estimates, and execution requirements.

Create one integrated technical-review record covering:

• final-map check cycles;
• improvement plans and specifications;
• survey closure and boundary review;
• grading, drainage, street, sewer, water, utility, and related plans;
• geotechnical, hydrology, fire, traffic, landscape, or other supporting materials;
• engineer’s estimates and security calculations;
• interdepartmental and utility comments;
• approved deviations or design decisions; and
• documents whose execution depends on approved technical content.

Use a common issue ID where one agency comment affects both the final map and an improvement plan. Record the decision once and carry it through each package.

Readiness output: a coordinated map-and-plan review log with current versions, comment ownership, dependencies, and approval status.

5. Resolve Improvement Agreements and Security

Government Code section 66462 requires an agreement where required public improvements remain incomplete and unaccepted at final-map approval under the circumstances described in that section. The local agency must require performance security specified by the Subdivision Map Act.

The workplan should identify:

• each incomplete public improvement;
• the governing condition and approved plan;
• the agreement form and responsible agency;
• estimated cost and security calculation;
• performance, labor-and-material, warranty, or other required security;
• execution parties and authority;
• insurance, indemnity, or related requirements;
• completion, inspection, acceptance, and release procedures; and
• the schedule relationship between agreement execution and map approval.

Counsel, the engineer, financial institutions or sureties, and the local agency retain responsibility for their respective legal, technical, underwriting, and approval functions. The project coordinator should maintain the dependency record and obtain early confirmation of form, amount, signatory, and processing sequence.

Readiness output: an agreement-and-security matrix with forms, amounts, parties, prerequisites, approvals, and release conditions.

6. Address Off-Site Improvements and Required Property Rights

A tentative-map condition may require an off-site improvement on land outside the subdivider’s control. Government Code section 66462.5 establishes procedures for certain final-map conditions where the subdivider and local agency lack sufficient title, easement, or license at filing.

For each off-site obligation, identify:

• the improvement and governing condition;
• the property affected and current ownership;
• the right needed for design, construction, access, maintenance, and acceptance;
• the party responsible for acquisition or agency proceedings;
• appraisal, negotiation, agreement, condemnation, or other required steps;
• design and utility coordination;
• cost responsibility and funding;
• the agreement path under section 66462.5 where applicable; and
• the effect on map approval, construction timing, and phase delivery.

The statutory path and local implementation require project-specific legal and agency review. The workplan should surface the property-rights question while schedule and design options remain available.

Readiness output: an off-site-rights schedule connecting property, authority, design, funding, agreements, and delivery dates.

7. Track Local Clearances, Certificates, and Execution

Government Code section 66492 requires a tax or assessment certificate or statement under the county’s procedures before filing the map with the legislative body, subject to the statute’s terms. Government Code section 66464 addresses transmission of an approved map to the county recorder and the additional section 66493 process where applicable.

The local checklist may also include fees, signatures, agency clearances, utility approvals, executed agreements, security deposits, county-surveyor review, clerk certificates, recorder review, and related instruments. Build the checklist from current written procedures and direct confirmation with the responsible offices.

For each clearance, record:

• the responsible office;
• the governing requirement;
• the required application, certificate, payment, signature, or evidence;
• the earliest submission date;
• processing sequence and dependencies;
• expiration or refresh requirement;
• current status; and
• the person responsible for follow-through.

Readiness output: a local-clearance matrix arranged in the actual approval and recording sequence.

8. Conduct the Approval and Recordation Readiness Review

Before the final approval package advances, hold a formal readiness review with the sponsor, surveyor, engineer, title team, counsel, and other responsible contributors. Confirm:

• final-map conformance and agency map-check completion;
• current title and execution status;
• completed conditions due at the map milestone;
• approved plans and estimates required for agreements or security;
• executed or execution-ready agreements;
• security form, amount, and delivery;
• tax, fee, and local clearance status;
• related documents and recording order;
• authorized signatories and delivery logistics;
• county-recorder formatting and submission readiness; and
• contingency ownership for any rejection, correction, or delayed signature.

Freeze the recordation version and assign one package controller. Any change after the freeze should receive an impact review covering signatures, acknowledgments, certificates, legal descriptions, related instruments, and agency approvals.

Readiness output: a signed readiness certificate or internal gate record identifying completed items, approved contingencies, and authority to proceed.

9. Complete the Recordation Handoff

Recordation creates a new source set for the project. Assemble and distribute:

• the recorded final map and recording information;
• concurrently recorded deeds, easements, declarations, agreements, or other instruments;
• the approved improvement plans and executed agreements;
• security records and release conditions;
• conditions completed at recordation;
• conditions and improvements continuing after recordation;
• updated title information;
• changes to lot, parcel, phase, ownership, or facility references;
• impacts on permits, construction, public-report filings, budgets, disclosures, financing, sales, and operations; and
• the next responsible owner for every continuing obligation.

Update all project systems that rely on the map. The recorded map should replace draft map references in document indexes, public-report workplans, community-structure materials, closing checklists, and implementation records where appropriate.

Readiness output: a recordation book and continuing-obligations handoff delivered to each affected workstream.

Obtain the Current Local Checklist

Collect the jurisdiction’s final-map procedures, subdivision ordinance provisions, map-check requirements, agreement and security forms, fee and tax instructions, and recorder specifications.

Build the Conformance and Conditions Matrices

Trace the approved tentative map and every map-stage condition into the final-map, plan, agreement, clearance, and evidence records.

Open the Title, Signature, and Recording Plan

Reconcile current title interests with the map, required consents, dedications, easements, related instruments, execution sequence, and recording order.

Confirm Agreements, Security, and Off-Site Rights Early

Identify forms, amounts, parties, property rights, agency steps, and lead times before they reach the final approval package.

Establish the Recordation Freeze and Handoff

Define the final version-control gate and prepare the recorded-document distribution, system updates, and continuing-obligation assignments in advance.