Before the Tentative Map: Five Decisions That Define a Subdivision Strategy

1. What Development Outcome Should the Subdivision Support?

Begin with the sponsor’s intended outcome. A concise development thesis should address:

• the proposed land uses and product types;
• the working density, intensity, lot, parcel, or unit range;
• the anticipated ownership and disposition model;
• the role of common or shared property;
• the intended phasing and delivery sequence;
• the decision criteria for comparing alternatives;
• the target approval, financing, construction, and sales milestones; and
• the areas in which flexibility remains important.

The thesis should distinguish verified site and policy facts, sponsor direction, professional recommendations, agency input, and open assumptions. That distinction allows the team to refine the project while preserving a clear record of who decided what and why.

Useful work product: a one-page development thesis with objectives, decision criteria, current assumptions, open questions, and named decision owners.

2. What Interests, Boundaries, and Ownership Relationships Will Be Created?

The proposed end state should guide the technical and legal evaluation of mapping and ownership instruments. Engineers, surveyors, and counsel can then evaluate the boundary framework, recordation sequence, separate and shared interests, easements, condominium or planned-development concepts, and other instruments appropriate to the project.

The strategy review should address:

• the proposed external and internal boundaries;
• the relationship between lots, parcels, units, common areas, and shared facilities;
• access, utility, drainage, support, reciprocal, and maintenance easements;
• vertical or horizontal components, where applicable;
• future phases, annexation areas, remainder parcels, and transition points;
• ownership and maintenance responsibility during construction and after transfer; and
• the relationship between mapping, governing materials, public reports, financing, and sales.

A simple boundary-and-responsibility diagram can reveal issues that remain difficult to see in separate plans and memoranda. Label each component by proposed owner, user, maintainer, payer, phase, and source of authority.

Useful work product: a boundary, ownership, and responsibility diagram reviewed by the appropriate technical and legal professionals.

3. How Will the Site Systems Function?

A viable subdivision concept needs a working account of the systems that allow the project to function. Depending on the site and jurisdiction, the review may include:

• vehicular, bicycle, pedestrian, emergency, and service access;
• internal circulation and connections to the surrounding network;
• grading, drainage, stormwater, and flood considerations;
• water, sewer, dry utilities, and utility-provider requirements;
• fire protection and emergency-service inputs;
• public and private streets;
• off-site improvements;
• dedications, easements, and rights-of-way;
• common facilities, open space, landscape, walls, gates, and lighting; and
• long-term ownership, operation, maintenance, repair, and replacement.

For each system, record the current assumption, source, responsible professional, reviewing agency or provider, capacity or feasibility question, ownership and maintenance concept, phase, decision date, and downstream dependency.

This record helps the team identify which assumptions require early agency discussion, field investigation, technical study, title work, cost analysis, or sponsor direction.

Useful work product: a site-systems matrix showing current assumptions, evidence, owners, agency touchpoints, dependencies, and next actions.

4. Which Approvals and Environmental Assumptions Must Remain Aligned?

The subdivision strategy should map the anticipated approval path and the project definition that will support it. That path may involve land-use entitlements, subdivision approvals, design review, environmental review, infrastructure and utility approvals, development agreements, permits, and other jurisdiction-specific actions.

The State CEQA Guidelines require an environmental impact report’s project description to address the project’s location and boundaries, objectives, technical and related characteristics, intended uses of the document, participating agencies, and required approvals. A clear and controlled project definition also supports initial review, technical studies, agency consultation, and hearing preparation.

Build one approval-and-environmental roadmap that identifies:

• the lead and participating agencies;
• each anticipated discretionary and ministerial action;
• the current project description;
• the technical studies and source assumptions;
• pre-application and formal agency touchpoints;
• application, environmental, hearing, and decision milestones;
• the relationship between map revisions and study updates;
• the expected conditions, findings, monitoring, and follow-through; and
• the professional responsible for each submission and determination.

When the map concept changes, use a documented change review to identify which applications, plans, studies, disclosures, schedules, and agency communications require attention.

Useful work product: an integrated entitlement, environmental, and mapping roadmap with change-control triggers.

5. How Will Approval Move into Final Mapping and Implementation?

A subdivision strategy should reach through the first meaningful implementation milestone. The team should understand how a conditional approval would translate into final or parcel mapping, improvement plans and agreements, security and completion arrangements, permits, dedications, easements, public reports, construction, financing, sales, and phase handoffs.

Work backward from the target implementation milestone and identify:

• the conditions and findings that require action;
• the professional or agency responsible for each action;
• the evidence needed to demonstrate completion;
• the sequence for final documents, recordation, permits, and construction;
• the relationship between infrastructure delivery and phase release;
• the filing and document dependencies for public-report work;
• the points at which sponsor decisions become difficult or expensive to revise; and
• the contingency path for unresolved agency, utility, title, technical, or market questions.

A condition-and-implementation matrix should begin during strategy development and remain current through approval. Early ownership of conditions helps the team evaluate cost, timing, feasibility, and downstream document needs while alternatives remain available.

Useful work product: a condition, final-map, and implementation matrix organized by phase, responsible party, evidence, dependency, and decision date.

Write the Development Thesis

Document the intended outcome, current assumptions, decision criteria, open questions, and areas of desired flexibility.

Convene a Boundary and Systems Review

Bring the sponsor, engineer, surveyor, planner, architect, counsel, and other relevant professionals into one focused review of boundaries, access, infrastructure, easements, shared facilities, and phasing.

Build the Integrated Roadmap

Connect mapping, entitlements, environmental review, technical studies, agency touchpoints, hearings, final documents, and implementation milestones.

Open the Decision Log

Record sponsor choices, agency direction, professional recommendations, changed assumptions, and the workstreams affected by each decision.

Establish the Next Decision Gate

Define the evidence, professional input, agency feedback, and sponsor direction required before technical mapping advances to the next level of detail.