A Submission Creates the Agency’s Working Project Record
An entitlement package can begin months before the formal filing date. Early meetings shape the application list. Concept plans establish dimensions that later appear in technical studies. A preliminary application may preserve a housing project’s relationship to ordinances, policies, and standards in effect at a defined time. The full application supplies the materials the agency uses to determine completeness and begin processing. Each resubmittal then updates the record through which planners, engineers, environmental reviewers, fire authorities, utility providers, counsel, and decisionmakers understand the project.
These stages require a common factual baseline. A unit count stated in one form should align with the site plan, project description, parking table, utility demand, environmental assumptions, fee estimate, and subdivision request. A proposed access point should appear consistently in civil exhibits, fire access materials, traffic analysis, legal-description work, and agency correspondence. A phasing concept should carry through the maps, infrastructure narrative, improvement sequence, technical studies, and requested approvals.
California’s Permit Streamlining Act supplies several important process controls. Government Code section 65943 generally requires a public agency to make a written completeness determination within 30 calendar days after receiving an application for a development project. An incompleteness determination must identify the missing items, use the agency’s submittal checklist as its boundary, and describe the information required to complete the application. A resubmittal begins a new 30-day review period focused on the previously identified items. The statute also establishes an appeal process and a 60-day period for the agency’s final written determination on the appeal.
Housing development projects may have an additional preliminary-application stage under Government Code section 65941.1. That section identifies 17 items for a statutory preliminary application, permits a request for a preliminary fee and exaction estimate, requires a full development application within 180 calendar days, and provides a 90-day response period after an incompleteness determination to preserve the preliminary application. A revision involving a change of 20 percent or greater in residential units or square footage can require refreshed preliminary-application information under the statute, subject to the stated exclusions.
A completeness determination addresses whether the application contains the information required for processing. Separate agency work addresses consistency, environmental review, discretionary findings, technical adequacy, conditions, and the ultimate decision. A strong submission-control system makes that sequence visible and preserves the record needed for every stage.
Identify the Application Stage Before Building the Package
Use a short application-stage memorandum at the beginning of the workplan. The memorandum should identify:
- the applicant and property owner;
- the site and assessor parcel numbers;
- the project type and development program;
- the requested legislative, discretionary, subdivision, and ministerial actions;
- the responsible city, county, special district, utility, and outside agencies;
- the local pre-application process;
- the applicability of Government Code section 65941.1 to a housing development project;
- the full-application checklist and local filing procedures;
- the contemplated CEQA pathway and technical-study program;
- the desired filing date, agency decision path, and commercial milestone; and
- the professionals responsible for legal, planning, engineering, surveying, architectural, environmental, financial, and other specialized work.
This memorandum prevents a common source of drift: different contributors working toward different filing events. A conceptual review, statutory preliminary application, full entitlement filing, subdivision filing, and technical resubmittal may use overlapping materials while carrying distinct purposes, deadlines, and legal consequences.
A Nine-Part Submission-Control Framework
1. Define the Approval Architecture
List every approval needed to carry the development concept into implementation. Group the list by approving body and sequence.
The architecture may include a general-plan or specific-plan action, zoning action, development agreement, conditional use permit, site-plan or design review, tentative map, condominium map, density-bonus request, tree or hillside approval, coastal approval, resource-agency authorization, utility action, encroachment approval, grading permit, improvement-plan approval, and building permits.
For each item, identify:
- the application form and local checklist;
- the decisionmaker and any recommending body;
- the findings or approval criteria identified by the agency or counsel;
- required plans, studies, agreements, and ownership documents;
- public-hearing and noticing needs;
- dependencies on another approval or technical conclusion; and
- the requested sequence or consolidated hearing path.
The approval architecture should also identify approvals that arise later in delivery. Their requirements can influence the initial project description, utility strategy, off-site rights, improvement concept, and phasing plan.
2. Assemble the Controlling Agency Source Set
Collect the current application forms, submittal checklists, fee schedules, adopted plans, zoning provisions, objective standards, design guidelines, technical manuals, electronic-filing rules, and agency handouts that apply to the project.
Record the source date and retrieval date. Local forms and procedures change. A saved checklist should carry enough identifying information to establish which version supported the filing.
Create a source index with links to the official materials and a short note explaining the project relevance of each source. When agency staff provides written direction during a pre-application meeting, preserve the correspondence and connect it to the affected requirement. Counsel should assess legal significance where the direction bears on rights, deadlines, standards, or appeal procedures.
3. Control the Preliminary-Application Record for a Housing Project
For a housing development project using Government Code section 65941.1, create a dedicated preliminary-application package and receipt record.
Map each of the statute’s 17 information categories to a submitted page, plan, exhibit, or form field. Confirm the permit-processing fee and the delivery method accepted by the agency. Preserve the submitted package, transmittal, payment evidence, upload receipt, agency acknowledgment, and any written response.
Open a statutory milestone schedule that includes:
- preliminary-application submission date;
- fee and exaction estimate request, when used;
- agency response date for the estimate;
- 180-day full-application deadline;
- projected full-application filing date;
- any incompleteness determination on the full application;
- the 90-day deadline for the specified completion materials; and
- any project revision requiring review under the 20-percent provision.
The fee and exaction estimate under section 65941.1 is informational and nonbinding. Preserve it as a dated planning input. Connect each estimated item to the development-cost register so later fee schedules, agency calculations, imposed obligations, timing rules, credits, and payments can be reconciled.
4. Establish One Controlled Project Fact Sheet
Create a project fact sheet before consultants finalize their filing materials. Give every material project fact a defined value, source, owner, status, and effective date.
The fact sheet should address, as applicable:
- site area, parcel configuration, jurisdiction, and existing use;
- ownership, applicant authority, and relevant agreements;
- proposed uses, units, floor area, density, height, and lot coverage;
- affordability program, density-bonus request, incentives, concessions, waivers, and parking reductions;
- demolition, replacement-housing, and tenant information;
- parking, loading, access, fire circulation, and emergency access;
- grading, retaining systems, drainage, and earthwork assumptions;
- water, wastewater, dry utilities, and off-site improvements;
- common areas, private streets, shared facilities, maintenance concepts, and association structure;
- phase boundaries and development sequence;
- known hazards, biological resources, cultural resources, easements, and site constraints;
- requested maps, entitlements, agreements, and permits; and
- schedule assumptions and decision deadlines.
Use controlled status labels such as verified; professional confirmation pending; agency confirmation pending; sponsor decision pending; working assumption; superseded. Every downstream document should identify the fact-sheet version used in its preparation.
5. Map Requirements to Evidence
Build a requirement-to-evidence matrix with one row for each checklist item, application question, technical requirement, and agency direction.
Useful fields include:
- requirement ID;
- source and section;
- exact or faithful requirement summary;
- applicable approval;
- required deliverable;
- responsible preparer;
- supporting project fact;
- professional reviewer;
- internal due date;
- package location;
- quality-control status;
- open question;
- agency confirmation, when obtained; and
- final submission version.
The matrix should capture narrative requirements as carefully as plan-sheet requirements. Project descriptions, operational statements, phasing narratives, infrastructure explanations, findings support, and responses to prior agency direction often carry assumptions that affect several technical workstreams.
6. Coordinate the Technical-Study Program
Prepare a technical-study matrix that identifies the study scope, governing project assumptions, required data, agency reviewer, dependencies, schedule, and update triggers.
The program may include traffic and vehicle-miles-traveled analysis, air quality, greenhouse gas emissions, noise, biological resources, cultural and tribal cultural resources, geology and soils, hazards, hydrology and water quality, utilities, water supply, wastewater, fire and emergency response, shade and shadow, wind, fiscal analysis, market work, and other jurisdiction-specific studies.
Give each consultant the same controlled project description and plan set. Require an assumptions page or transmittal that identifies the version used. When a study relies on a quantity or design feature supplied by another professional, record the source. When an agency comment changes the premise, open a change item and identify every study, plan, form, and narrative that requires review.
7. Conduct a Cross-Document Preflight
Before filing, compare the complete package across five dimensions:
- Project identity: Confirm name, applicant, owner, site address, parcel numbers, legal description, acreage, and jurisdiction.
- Development program: Confirm uses, unit counts, floor areas, affordability, density, height, parking, open space, and requested concessions or waivers.
- Physical plan: Confirm boundaries, access, grading, utilities, easements, common areas, improvements, facilities, and phase lines.
- Approval request: Confirm that every form, narrative, plan, and study describes the same discretionary actions, maps, and implementation sequence.
- Source and version: Confirm dates, revision numbers, consultant seals or signatures where required, electronic file names, and the relationship between the transmittal index and uploaded files.
Create an exception report for unresolved discrepancies. Assign each item to the professional or sponsor decisionmaker with authority to resolve it. Release the package when the remaining open items have a defined treatment and the project team has accepted the filing record.
8. Control the Completeness Review and Resubmittal
When the agency issues a completeness determination, capture the letter exactly and freeze the received version. Number each comment. Identify the checklist source, requested information, responsible contributor, professional reviewer, sponsor decision need, and target response date.
For a resubmittal under Government Code section 65943, connect every response to the agency’s identified item. Prepare a response matrix with:
- the agency comment;
- the project response;
- the affected document or plan sheet;
- the revision description;
- the professional responsible for the revision;
- any legal or procedural issue routed to counsel;
- any agency clarification obtained; and
- the final file name and version.
Track the new 30-day period from agency receipt of the resubmittal. Preserve proof of delivery and the complete package. For a housing project proceeding from a statutory preliminary application, track the separate 90-day period for submission of the specific completion information identified by the agency.
A request that appears outside the initial completeness list or local checklist should be documented and routed promptly to the project manager and counsel. The project team can then determine the appropriate procedural response while continuing to address the technical substance required for project processing.
9. Transition the Controlled Record into Substantive Review
After the application reaches completeness, carry the same project record into planning review, CEQA, technical corrections, hearings, conditions, findings, and implementation.
Update the project fact sheet to identify the accepted application baseline. Preserve later changes through the project’s change-review protocol. Connect agency comments to the responsible workstream, decision, and source. Maintain a hearing and decision schedule. Begin the conditions and commitments register before adoption so the project team can test draft requirements against design, mapping, infrastructure, public-report, budget, phasing, and delivery assumptions.
Completeness is a milestone in the record. The operating system should remain active through the final agency decision and the handoff into map, permit, construction, DRE, sales, and operations work.
The Submission-Control Register
A complete register can include the following fields:
- application or approval ID;
- responsible agency and decisionmaker;
- application stage;
- statutory or local procedure;
- source checklist and version;
- filing prerequisites;
- project-fact-sheet version;
- required forms, plans, studies, and agreements;
- preparer and professional reviewer;
- sponsor decision owner;
- internal target date;
- filing date and proof of receipt;
- statutory agency-response date;
- completeness status;
- comment or missing-item IDs;
- resubmittal date;
- appeal or procedural-review milestone;
- related CEQA and technical activities;
- current risk or open decision;
- next action and responsible person; and
- last review date.
Use defined status terms. A useful sequence is: scoping; source collection; in production; internal coordination; professional review; preflight; ready to file; agency intake; completeness review; resubmittal; complete; substantive review; hearing; decided; implementation handoff.
Five Submission Gates
Gate 1: Filing Path Confirmed
The requested approvals, application stages, governing procedures, and responsible agencies are identified.
Gate 2: Project Record Controlled
The fact sheet, plan set, application forms, technical scopes, and ownership information use one current project baseline.
Gate 3: Requirement Coverage Verified
Every checklist item and agency direction is linked to a deliverable, preparer, package location, and quality-control status.
Gate 4: Filing Package Released
Cross-document discrepancies are resolved, the transmittal index matches the uploaded files, and proof-of-submission controls are ready.
Gate 5: Completeness Cycle Closed
The agency determination, response matrix, resubmittal record, timing milestones, and transition into substantive review are complete and preserved.
Questions to Resolve
- Which approvals and application stages are included in the current submission?
- Does the project qualify for and use the housing preliminary-application procedure in Government Code section 65941.1?
- Which local checklist version governs the full application?
- Which project facts remain assumptions, and who has authority to confirm them?
- Do all forms, plans, studies, narratives, and fee inputs use the same development program and physical plan?
- Which technical studies depend on another consultant’s conclusion or an agency decision?
- Which completeness comments require a project decision, professional judgment, legal review, or agency clarification?
- What evidence establishes each filing and resubmittal date?
- Which changes after filing require review across the complete project record?
Practical Next Steps
Write the Application-Stage Memorandum
Define the approvals, agencies, local procedures, statutory milestones, filing objectives, and professional roles in a concise project document.
Build the Project Fact Sheet
Record each controlling project fact, its source, current status, owner, and effective date. Issue the same version to every contributor.
Create the Requirement-to-Evidence Matrix
Map the local checklist, forms, technical requirements, and agency direction to specific deliverables and package locations.
Run the Cross-Document Preflight
Compare the project identity, development program, physical plan, approval request, and source versions across the full filing set.
Open the Completeness Response Log
Preserve each agency item, assign the response, control revisions, track statutory dates, and maintain one indexed resubmittal package.
