Approval Creates a Project Baseline
Project approval establishes a defined record. That record may include the application, project description, approved plans, maps, findings, conditions, mitigation measures, technical studies, agreements, hearing materials, and agency decisions. Final mapping, permits, construction documents, public-report filings, governing materials, budgets, disclosures, and implementation plans build from that baseline.
Projects continue to evolve. A sponsor may revise unit mix, architecture, circulation, grading, infrastructure, phasing, ownership, common facilities, maintenance responsibility, construction sequencing, or offering strategy. A field condition, utility requirement, agency comment, market decision, or consultant recommendation may create the same need for change.
California Public Resources Code section 21166 identifies the circumstances in which substantial project changes, changed circumstances, or new information can require subsequent environmental review following an environmental impact report. CEQA Guidelines sections 15162 and 15164 provide additional rules for subsequent environmental documents and addenda. The lead agency determines the applicable CEQA path on the project record. DRE’s current amendment forms also distinguish categories of public-report changes and direct applicants to report material changes affecting an offering.
A disciplined change-review protocol helps the project team assemble the facts needed for those determinations and keeps the approved baseline, professional work, agency record, and downstream implementation aligned.
The Change Intake
Every proposed change should begin with the same concise intake record. The record should identify:
- a unique change ID and descriptive title;
- the person requesting the change and the reason;
- the decision required from the sponsor or project team;
- the affected location, phase, lots, units, buildings, facilities, or systems;
- the proposed change in measurable terms;
- the approved condition or current assumption that would change;
- the requested decision date and implementation date;
- available plans, studies, correspondence, cost information, and photographs;
- known agency, technical, legal, schedule, budget, sales, or operational implications; and
- the person responsible for coordinating review.
The intake record should describe the proposed outcome and preserve the current approved condition. A marked plan, redline, table, or before-and-after summary often gives the team the clearest starting point.
A Seven-Lens Change Review
1. Entitlements, Conditions, and Agency Decisions
Identify every approval, condition, finding, agreement, permit, or agency representation that relies on the current project fact. Review the proposed change against:
- permitted uses, density, intensity, unit or lot count, and development standards;
- approved site, grading, landscape, architectural, circulation, and infrastructure plans;
- tentative-map conditions and map notes;
- conditions tied to timing, phasing, facilities, access, utilities, or operations;
- hearing commitments and findings;
- development, improvement, reimbursement, utility, or maintenance agreements; and
- later permits or agency actions that incorporate the approved plan.
Record the agencies and decision makers with authority over each affected item. Counsel and the appropriate planning and technical professionals should advise on the required amendment, substantial-conformance, plan-check, permit, or other process. Capture agency direction in writing and connect it to the change record.
Key output: an entitlement-impact table identifying the controlling source, affected provision, review path, agency contact, required material, and decision status.
2. CEQA and the Environmental Record
Compare the change against the project description, impact analysis, technical assumptions, mitigation measures, alternatives, findings, statement of overriding considerations where applicable, and mitigation monitoring or reporting program.
The review should identify:
- the environmental topics and technical studies affected;
- changes in location, footprint, intensity, operations, construction, access, utilities, grading, drainage, infrastructure, or phasing;
- changed circumstances surrounding the project;
- new information relevant to the prior analysis;
- mitigation measures or project-design features that require revision;
- the next discretionary agency action, if any; and
- the evidence the lead agency and its consultants may need to evaluate the change.
The project team should provide a complete factual record to the lead agency and environmental professionals. The lead agency makes the subsequent-review determination under the applicable CEQA standards. The change record should identify the resulting documentation, decision date, and any revised mitigation or monitoring responsibilities.
Key output: an environmental change memorandum or intake package prepared for lead-agency and professional review.
3. Mapping, Plans, and Technical Studies
Map the change across the technical record. Relevant materials may include tentative and final maps, civil plans, architectural drawings, landscape plans, utility plans, grading and drainage studies, traffic analyses, fire access plans, geotechnical work, biological or cultural-resource materials, acoustical studies, water and wastewater analyses, and other discipline-specific documents.
For each affected document, identify:
- the current version and preparer;
- the fact or assumption that changes;
- the required analysis or revision;
- professional review and signature requirements;
- agency or utility review;
- related drawings, calculations, specifications, or reports; and
- the date by which the updated document must enter the next package.
One change may produce several technically acceptable options with different entitlement, cost, schedule, environmental, public-report, or operational consequences. Present those options together so the sponsor can make one informed decision.
Key output: a document-impact matrix with responsible professionals, revision scope, review path, and release date.
4. Conditions, Mitigation, and Implementation Commitments
Review the conditions and commitments register for obligations whose scope, location, timing, evidence, owner, or acceptance path would change. Determine whether the proposed revision:
- creates a new action;
- changes a formal trigger or internal target date;
- affects an improvement agreement or security;
- changes the required evidence of compliance;
- alters the entity responsible for construction, maintenance, monitoring, or reporting;
- affects a continuing obligation after closing or turnover; or
- changes a representation already made to an agency, purchaser, lender, association, or other stakeholder.
Update the register after the decision is authorized. Preserve the earlier entry, the decision source, the effective date, and every dependent action.
Key output: a change-to-obligation crosswalk showing additions, revisions, continuing actions, and new closure evidence.
5. Public Reports, Offering Materials, and DRE Filings
Determine whether the change affects a fact represented in a DRE filing, public report, purchase or escrow material, governing document, disclosure, budget, reserve input, completion arrangement, facility description, phase plan, assessment structure, or marketing statement.
DRE’s current forms library includes separate amendment and renewal materials. RE 635A identifies several categories of change that call for a full amendment or renewal application, including certain changes involving governing instruments, common-interest phasing, budgets and financial conditions, maintenance or subsidy arrangements, and completion security. RE 635B addresses a defined non-substantive amendment path and requires prompt reporting of material offering changes.
Counsel and the responsible public-report professional should determine the filing path and required disclosures in coordination with DRE. Record the affected file number, report type, phase, documents, submission timing, and sales or closing constraint.
Key output: a DRE and offering-impact sheet identifying current representations, affected materials, professional review, filing path, and release restriction.
6. Community Structure, Budgets, and Operations
For a common interest development or another project with shared ownership and maintenance, test the change against the community operating model. Ask:
- Does ownership, use, access, maintenance, repair, replacement, or cost allocation change?
- Does a component move between phases, associations, districts, owners, or service areas?
- Does the quantity, timing, or standard of a budgeted service change?
- Does the change affect reserve components, start-up funding, subsidy assumptions, assessment levels, or the period over which costs are allocated?
- Do governing materials, easements, reciprocal arrangements, disclosure documents, or management plans require attention?
- Does the operational team need new procedures, contracts, staffing, access controls, or turnover materials?
Route legal questions to counsel and financial or reserve questions to the responsible professionals. Keep the physical plan, ownership structure, governing materials, budgets, disclosures, public-report record, and operating plan on the same approved assumption.
Key output: a community-impact summary with affected components, responsibilities, financial inputs, documents, and operational actions.
7. Commercial, Schedule, and Delivery Consequences
Complete the review by showing the sponsor how each option affects the project’s delivery plan. The analysis may include:
- design and consultant cost;
- agency, utility, and professional review time;
- entitlement, mapping, permit, construction, public-report, financing, sales, closing, and occupancy milestones;
- procurement, lead-time, and contractor effects;
- conditions, fees, security, agreements, and property-rights requirements;
- sales commitments, disclosures, lender covenants, and third-party agreements;
- phase economics and operating costs; and
- fallback options if the preferred change encounters delay or denial.
Use a defined decision date. Delay in the sponsor decision can become its own critical-path event even when the proposed change remains feasible.
Key output: an options-and-consequences table stating cost range, schedule effect, approvals, dependencies, risk, and recommendation from each responsible discipline.
The Change Decision Package
A sponsor or authorized project decision maker should receive one controlled package containing:
- Decision statement: the exact choice requiring authorization.
- Baseline and proposed condition: plans, quantities, phases, and assumptions.
- Reason for change: field condition, agency direction, cost, market, design, operations, or another identified driver.
- Seven-lens review: concise findings from each affected workstream.
- Professional and agency input: advice, determinations, open questions, and required follow-through.
- Options: available paths and their cost, schedule, approval, and delivery consequences.
- Recommendation: the sponsor-side recommendation and its assumptions.
- Authorization: decision, date, authority, conditions, and implementation restrictions.
- Distribution list: every document owner and workstream receiving the decision.
- Release plan: revisions, submissions, approvals, evidence, and the date the change may enter implementation.
The decision package should state any remaining contingency. Authorization can be conditional on agency confirmation, professional completion, agreement execution, security, a revised budget, a DRE action, or another defined event.
Five Control Gates
Gate 1: Intake Complete
The proposed change, current baseline, affected area, reason, target date, and available evidence are clear enough for review.
Gate 2: Review Scope Confirmed
The project has identified the affected approvals, environmental record, technical work, conditions, public reports, community documents, budgets, operations, schedule, and responsible reviewers.
Gate 4: Documents and Agency Actions Complete
Required plans, studies, findings, approvals, agreements, filings, budgets, disclosures, and implementation records reflect the authorized change.
Gate 5: Implementation Released
The project has confirmed that every prerequisite to construction, marketing, closing, occupancy, operations, or phase delivery is complete and recorded.
The Change Register
Maintain one register showing:
- change ID and title;
- requestor and date;
- location and phase;
- current approved condition;
- proposed condition;
- reason and decision deadline;
- affected workstreams and documents;
- responsible reviewers;
- agency and professional determinations;
- options and sponsor decision;
- required follow-through;
- release conditions;
- current status;
- evidence links; and
- completion and distribution dates.
Useful status terms include: intake; scoping; under review; awaiting agency input; awaiting professional input; sponsor decision; authorized with conditions; document revision; agency processing; implementation hold; released; closed.
Questions to Resolve
- Which approved fact, plan, condition, mitigation measure, agreement, or representation would change?
- Which agency or professional determines the applicable review path?
- Which technical studies and source assumptions require revision?
- Which map, permit, public report, governing document, budget, disclosure, or operating plan carries the current assumption?
- Which project milestone depends on the decision?
- What evidence and approvals are required before implementation?
- Which fallback path preserves the project’s critical objective?
Practical Next Steps
Establish the Approved-Project Baseline
Index the operative approvals, plans, environmental documents, maps, conditions, agreements, filings, budgets, and disclosures. Assign a current version and owner to each source.
Adopt a One-Page Change Intake
Require the same baseline, proposed condition, reason, location, phase, decision date, and supporting materials for every project change.
Connect Change Control to Existing Registers
Link each change to the conditions register, document index, agency-comment log, public-report matrix, project schedule, risk register, and decision log.
Run a Pilot on One Active Change
Use a current design, infrastructure, phasing, or offering issue to test the protocol. Refine the intake fields, review sequence, decision package, and release gate based on the pilot.

