Blog › ICP guides

Land use planner on retainer: zoning advisory, entitlement strategy, CEQA review, and planning commission preparation on monthly retainer

July 29, 2026 · ~22 min read

A residential developer is three days from submitting a 240-unit mixed-income apartment project for a conditional use permit when the retained land use planner flags a general plan consistency problem. The project is on a 3.2-acre parcel designated Medium-High Residential in the general plan, which the developer’s project manager has interpreted as permitting up to 36 units per acre — consistent with the 240 units at 75 units per acre proposed in the project program. The land use planner reviewing the application package opens the general plan land use element and finds that the Medium-High Residential designation in this jurisdiction describes a net density range of 18 to 36 units per acre, calculated on net site area excluding streets, rights-of-way, and open space areas dedicated to the public, but the project’s program density calculation uses gross site area including the 0.6-acre public access easement along the creek that bisects the parcel.

Recalculating on net site area — 3.2 acres minus the 0.6-acre easement equals 2.6 net acres — the 240-unit program density is 92 units per acre, which exceeds the general plan’s 36 units per acre maximum for the Medium-High designation. The project as designed is not consistent with the general plan and cannot receive a conditional use permit approval without a general plan amendment or a reduction in unit count to comply with the net density limit. The maximum unit count at 36 units per acre on 2.6 net acres is 93 units.

The land use planner calls the developer’s project manager before the application is submitted, documents the net density calculation and the maximum unit count in a two-page analysis memorandum, and identifies the three paths forward: redesign to 93 units on the net site area, pursue a general plan amendment concurrently with the CUP to increase the maximum density in the Medium-High designation, or apply under the state density bonus law to allow units in excess of the general plan base density in exchange for affordable unit commitment. The developer elects to redesign to 93 units and reserves the density bonus pathway for the project’s next application phase. The application is delayed two weeks for the program revision but submitted correctly. Filing the 240-unit application without catching the density inconsistency would have generated an incompleteness notice from the planning department, triggered a formal application resubmittal after program revision, and extended the entitlement timeline by four to six months while the application sat in incomplete status.

The advisory time for the land use planner to identify the density calculation error, research the general plan designation, and produce the analysis memorandum was six hours over two days. That advisory work — invisible to the developer as a discrete line item until it prevented a four-month entitlement delay — is the kind of land use planning retainer work that saves multiples of the retainer fee in a single engagement.

Zoning compliance and entitlement strategy advisory

Zoning compliance and entitlement strategy advisory is the land use planning retainer function that analyzes applicable regulatory requirements, evaluates permit pathway options, develops the entitlement strategy for development projects, and coordinates with planning departments to resolve regulatory ambiguities before applications are submitted. The land use planner advising on zoning and entitlement does not typically prepare all of the project’s planning application documents from scratch — that work may be shared between the development team, the project architect, and the land use planning consultant — but provides the regulatory analysis and strategic guidance that determines which permits are needed, in what order, and with what probability of approval at each step.

General plan consistency and zoning code analysis

General plan consistency analysis evaluates whether the proposed development project is consistent with the applicable general plan land use designation, housing element goals and policies, circulation element access and level-of-service requirements, conservation and open space element resource protection standards, and any applicable community-specific plans or area plans. A project that is inconsistent with the general plan cannot be approved by the planning commission or city council without a general plan amendment, and general plan amendments for individual projects are discretionary decisions subject to CEQA review and substantial public and political scrutiny.

Zoning code analysis evaluates whether the project complies with the applicable zoning district’s permitted uses, density and intensity limits, setback and yard requirements, height limits and FAR caps, parking requirements, landscaping standards, and design standards. Zoning code analysis is most complex for projects in overlay districts, specific plans, form-based code areas, or mixed-use districts where multiple regulatory documents must be read together, and where the most restrictive standard applies unless the overlay or specific plan explicitly supersedes the underlying zoning. The zoning code provisions that most frequently produce compliance errors are: density calculation methodology (gross vs. net site area, whether accessory dwelling units count against density limits, how mixed-income projects calculate density for base zoning compliance before density bonus is applied); parking requirements for mixed-use projects (which parking tables apply to each component of the use mix, whether parking is shared between uses, and how the off-street parking reduction for transit proximity is calculated); and nonconforming status of existing structures on the site (a project that includes retention of an existing nonconforming structure must verify that the proposed improvements do not trigger a requirement to bring the nonconforming element into conformance per the applicable nonconforming use and structures provisions).

In one zoning code advisory, a land use planner was retained by the developer of a proposed 18,000-square-foot artisan manufacturing and retail project in an urban mixed-use district. The project’s architect had designed the building with retail uses on the ground floor, light manufacturing on the second floor, and three live-work loft units on the third floor. The land use planner’s review identified that the zoning district’s definition of “artisan manufacturing” limited the use to production activities where the goods produced are sold primarily at retail on the premises, with a maximum floor plate of 10,000 square feet for the production component. The project’s 8,400-square-foot second-floor manufacturing area was within the limit, but the design showed a separate loading dock accessed from the alley, which the zoning code classified as a distribution use rather than a retail manufacturing use and required a conditional use permit. Identifying the distribution use trigger before the application was submitted allowed the developer to redesign the loading approach to serve the ground-floor retail rather than the manufacturing floor, eliminating the conditional use permit requirement and removing one permit application from the entitlement critical path.

Conditional use permit strategy and discretionary permit applications

Conditional use permit strategy advisory evaluates the factors that influence the planning commission’s or hearing officer’s decision on a CUP application, develops the findings narrative that supports the four standard CUP findings (consistency with the general plan, consistency with the zoning code, no significant adverse effect on the health, safety, and welfare of the surrounding area, and compliance with any applicable specific plan or design guidelines), and identifies the conditions of approval that the planning department is likely to recommend so that the developer can address them proactively in the project design or application before the staff report is written.

Conditions of approval that are not anticipated and addressed before the staff report are substantially more expensive and difficult to negotiate than conditions identified early. Planning staff conditions in the staff report carry the implicit endorsement of the planning department; opposing them at the hearing requires the applicant to make findings on the record that the recommended condition is not supported by the evidence, which is a high bar for a discretionary decision and creates an adversarial dynamic with planning staff that complicates the ongoing entitlement relationship. Conditions identified in advance and resolved in pre-hearing coordination with planning staff are resolved through informal negotiation where the applicant has substantially more flexibility and leverage.

In one CUP strategy advisory, a land use planner was retained by the owner of a proposed drive-through coffee kiosk in a commercial corridor subject to a city overlay district that discouraged auto-oriented uses. The land use planner’s pre-hearing analysis of the city’s prior drive-through approvals and denials in the corridor identified that the planning commission had denied two previous drive-through applications citing circulation conflicts and pedestrian safety impacts. The land use planner recommended three design modifications before the CUP application was submitted: a pedestrian priority zone between the parking lot and the building entry, a drive-through stacking lane design that kept queued vehicles from blocking the adjacent sidewalk, and a pedestrian-activated crosswalk at the drive-through exit. The planning commission approved the CUP with five conditions of approval, all of which had been incorporated into the project design before the hearing. The developer’s project manager estimated that the pre-hearing modifications saved $65,000 in redesign and three months of schedule compared to receiving the same conditions post-approval.

CEQA and NEPA environmental review advisory

CEQA and NEPA environmental review advisory is the land use planning retainer function that evaluates the applicable environmental review pathway, reviews the adequacy of environmental documents, advises on mitigation measure development, and supports the lead agency’s environmental determination through the public review period and potential appeal. Environmental review advisory is one of the highest-liability land use planning functions because a flawed environmental document is the most common basis for a legal challenge to a project approval, and successful CEQA challenges can invalidate project approvals and require years of additional environmental review before a project can proceed.

Categorical exemption applicability and initial study adequacy

Categorical exemption applicability analysis evaluates whether the proposed project qualifies for a CEQA categorical exemption under CEQA Guidelines Sections 15301 through 15333 and whether any of the exceptions to categorical exemptions in Guidelines Section 15300.2 apply. The categorical exemption classes that are most frequently applied but subsequently challenged or overturned on appeal are: Class 1 (existing facilities) for tenant improvement projects where the agency characterizes the project as minor alteration of an existing facility but the project involves a change of use that triggers traffic, parking, or public service demand analysis; Class 3 (new construction) for small commercial projects in jurisdictions where the local planning guidelines define “small” more narrowly than the state guidelines’ categorical exemption thresholds; and Class 32 (infill exemption) for urban infill projects where the site has documented contamination, the traffic study is missing or inadequate, or the biological survey for the site is more than five years old, triggering the unusual circumstances exception.

Initial study adequacy review evaluates whether the initial study checklist analysis is supported by substantial evidence, whether the project description accurately describes the proposed project and its environmental context, and whether the proposed mitigation measures in the mitigated negative declaration reduce impacts to less-than-significant levels. The initial study analysis sections that most frequently produce inadequate findings are: traffic (the project’s vehicle miles traveled analysis must use the SB 743-compliant VMT methodology per Transportation Code Section 21099 for projects subject to SB 743; initial studies that still rely on level-of-service analysis for projects subject to SB 743 are facially inadequate); air quality and greenhouse gas (the quantitative thresholds established by the applicable air quality management district for significance, the applicability of the screening criteria for small projects, and the mitigation measures required to reduce identified emissions to less-than-significant levels must be correctly applied); and biological resources (the adequacy of the biological survey depends on survey timing, seasonal presence of special-status species on the site, and the qualifications and methodology of the biologist who conducted the survey).

In one initial study advisory, a land use planner was retained to review the initial study for a proposed 72-unit multifamily housing project on a vacant infill site in an urbanized area. The initial study concluded that the project would have no significant biological resource impacts based on a biological survey conducted in February, noting that the site was a graded vacant lot with minimal vegetation. The land use planner’s review identified that the site was within the mapped range of the burrowing owl and within 500 feet of a drainage channel with documented seasonal wetland characteristics, and that the February survey was conducted outside the breeding season survey window (April through August) required for the species. The land use planner recommended that the developer request a pre-application meeting with the city to discuss whether a breeding season survey was required or whether the city’s biology consultant would require it during the initial study review period. The city’s response confirmed that the February survey was inadequate and that a breeding season survey was required before the initial study could be circulated. Addressing the biological survey requirement before the initial study was circulated added four months to the entitlement timeline; discovering the requirement after the initial study was circulated for public comment would have required recirculation and restarted the 30-day public comment period.

EIR scoping, alternatives, and mitigation monitoring

EIR scoping advisory supports the developer through the environmental impact report process for projects that cannot be approved with a mitigated negative declaration. The EIR scoping memo defines the project’s environmental baseline, identifies the significant environmental effects that must be analyzed, and establishes the range of project alternatives that the EIR must evaluate as required by CEQA Guidelines Section 15126.6. The alternatives analysis is the most litigation-sensitive component of an EIR because a court reviewing a CEQA challenge will evaluate whether the lead agency considered a reasonable range of alternatives that would reduce the project’s significant environmental effects, and whether the record supports the agency’s rationale for selecting the proposed project rather than the environmentally superior alternative.

Mitigation monitoring and reporting program development identifies the specific, feasible mitigation measures that will reduce identified significant impacts to less-than-significant levels, assigns responsibility and timing for each measure, and establishes the verification mechanism by which the lead agency will confirm that each measure is implemented. The MMRP provisions that most frequently produce mitigation effectiveness disputes or enforcement failures are: mitigation measures that are stated as performance standards rather than specific actions (“the project shall reduce VMT” is unenforceable without specifying the mechanism); mitigation measures that are assigned to an applicant but verified by an agency that lacks the authority or resources to conduct verification at the timing specified in the MMRP; and mitigation measures that are not included as conditions of approval in the project’s conditional use permit or development agreement, creating an MMRP that is legally required but not legally enforceable against the applicant.

Public agency coordination and hearing preparation advisory

Public agency coordination and hearing preparation advisory is the land use planning retainer function that manages the developer’s relationship with planning staff throughout the application review period, prepares for public hearings and planning commission presentations, analyzes recommended conditions of approval, and supports post-approval compliance and any appeals or legal challenges. Agency coordination and hearing preparation is the most time-intensive component of a land use planning retainer during active entitlement proceedings and is the function that most directly determines the developer’s relationship with the planning department and the quality of the project’s approval.

Staff report analysis and conditions of approval negotiation

Staff report analysis evaluates the planning department’s draft or final staff report for the project’s public hearing, including the project description accuracy, the recommended findings for each permit action, and the recommended conditions of approval. Conditions of approval that are legally unsupported, technically infeasible, or inconsistent with similar conditions imposed on comparable projects in the jurisdiction require a response on the record at the hearing or in written comments before the hearing to preserve the developer’s right to challenge the condition on appeal. Conditions that are not challenged at the hearing and are incorporated into the approval action become final conditions that the developer must satisfy, regardless of their legal or technical merit.

The conditions of approval that most frequently require negotiation or challenge are: traffic impact fees calculated using a fee program that was not in effect at the time the application was filed (vested rights to the fee schedule in effect at application filing depend on the jurisdiction and the type of approval; the land use planner must identify and document the applicable fee at the time of application if the developer wants to preserve a vested right against later-adopted fee increases); dedication and improvement conditions that exceed the project’s fair share of the infrastructure need (the Nollan/Dolan rough proportionality standard requires that conditions requiring dedication of private property or payment of fees be roughly proportionate to the project’s impact on the public resource being protected; conditions that impose the full cost of a regional infrastructure improvement on a single project that is one of many contributors to the need are legally vulnerable); and design conditions that conflict with the adopted design standards for the district and impose a higher standard on the project than was applied to comparable approvals.

In one conditions of approval advisory, a land use planner was retained by the developer of a 120-unit affordable housing project to review the planning department’s staff report and prepare the developer’s hearing presentation. The staff report recommended 34 conditions of approval. The land use planner’s analysis identified 6 conditions that the developer wanted to negotiate: a traffic signal upgrade condition that imposed 100% of the cost of a signal modification on the project rather than the project’s pro-rata share based on the project’s traffic volume contribution; a condition requiring a minimum 10-foot landscape setback from the rear property line that conflicted with the rear yard setback provision in the zoning code, which required only 5 feet for multifamily residential in the district; and four conditions that were not tailored to the project’s specific impacts and instead incorporated generic standard conditions from the department’s boilerplate that did not apply to the project type. The land use planner negotiated all six conditions to acceptable language with planning staff in the week before the hearing, avoiding a contested hearing and preserving the developer’s relationship with planning staff for the project’s subsequent building permit phase.

Appeals strategy and administrative record management

Appeals strategy advisory evaluates whether a project approval denial or onerous approval condition warrants an appeal to the next level of the administrative process — from hearing officer to planning commission, from planning commission to city council, or from city council to superior court under CEQA or the planning and zoning law. The appeal analysis must evaluate the standard of review at each level, the likelihood that the appeal will succeed based on the record, the cost and timeline of the appeal process relative to the benefit of a successful appeal, and whether the appeal itself will generate political opposition that complicates the project’s long-term relationship with the jurisdiction.

Administrative record management is the land use planning function that assembles and organizes the complete administrative record for a discretionary permit decision — all staff reports, correspondence between the applicant and the agency, public comments, hearing transcripts, and agency findings — in a format that supports an administrative appeal, a CEQA judicial review petition, or a planning and zoning law mandamus action. An incomplete or disorganized administrative record at the time an appeal is filed significantly increases the cost and risk of the appeal because the record must be reconstructed from emails, hearing recordings, and agency files rather than from a pre-organized document set. In one administrative record advisory, a land use planner was retained after a planning commission denied an entitlement for a 48-unit residential project on a split vote. The developer wanted to appeal the denial to the city council. The land use planner assembled the administrative record within 72 hours of the denial, identifying three procedural irregularities in the hearing process: a public comment submitted during the comment period that was not included in the staff report addendum provided to commissioners, a commissioner who made statements during the hearing that suggested the commissioner’s decision was based on considerations outside the scope of the applicable findings, and a staff report that cited a design standard that had been repealed before the application was filed but remained in the department’s standard condition boilerplate. All three irregularities were documented in the appeal brief as independent grounds for council to sustain the appeal.

Development agreement and specific plan advisory

Development agreement and specific plan advisory is the land use planning retainer function that reviews specific plan compliance for projects within adopted specific plan areas, advises on development agreement terms and conditions, evaluates vesting rights and regulatory certainty provisions, and manages development agreement amendment proceedings when project changes require modifying previously approved terms. Development agreements are among the most valuable entitlement instruments available to developers of large or long-term projects because they provide regulatory certainty for the duration of the agreement term, typically 10 to 25 years, in exchange for public benefits that the developer commits to provide.

Specific plan compliance review evaluates whether a project within an adopted specific plan area complies with the specific plan’s land use designations, development standards, design standards, phasing requirements, and infrastructure improvement obligations. Specific plans frequently supersede the underlying zoning code for projects within their boundaries, but the interaction between specific plan standards and general zoning code provisions is frequently ambiguous for project elements not explicitly addressed in the specific plan. In one specific plan advisory, a land use planner was retained to review the entitlement compliance of a proposed 280-unit townhome project within an adopted specific plan area. The specific plan allowed residential uses at up to 15 units per acre with a maximum building height of 35 feet. The project’s architect had designed three-story townhomes at 34 feet, within the specific plan height limit, but the townhomes were sited on a graded pad 6 feet above the adjacent public street grade. The specific plan measured building height from finish grade at the base of the structure, producing a measured height of 34 feet; the city’s municipal zoning code, which the specific plan incorporated by reference for measurement methodology, measured building height from natural grade before grading. Measured from natural grade, the townhomes were 40 feet tall — 5 feet above the specific plan maximum. Identifying the measurement methodology conflict before application submittal allowed the architect to reduce the first-floor plate height from 10 feet to 8 feet, bringing the building to 32 feet from natural grade without affecting the unit mix or the project economics.

Why land use planning retainer hours are invisible between milestones

Land use planning retainers generate most of their value between visible project milestones. The CUP application submittal is visible. The planning commission hearing is visible. The approval with conditions is visible. What is invisible to the developer or owner are the hours the land use planner spent reviewing the general plan density calculation before the application was submitted, identifying the net vs. gross acreage inconsistency, communicating the finding, and identifying the three regulatory pathways forward — the six hours of advisory work that prevented a four-to-six-month entitlement delay and potentially a development rights reduction that would have required a fundamental program revision.

The invisibility problem is particularly acute in land use planning retainers because the regulatory research and agency coordination work that drives entitlement outcomes leaves almost no visible record when it succeeds. When the land use planner identifies a zoning code ambiguity and resolves it in a pre-application meeting, the developer never experiences the completeness notice that would have been generated by an application that interpreted the ambiguity incorrectly. When the land use planner identifies an inadequate CEQA survey before the initial study is circulated, the developer never experiences the recirculation delay and the additional public comment period that would have followed a challenged environmental determination. When the land use planner negotiates an onerous condition of approval before the staff report is finalized, the developer never experiences the contested hearing and the adversarial relationship with planning staff that would have followed from challenging the condition on the record.

Land use planners on retainer who use a structured work log — capturing the project, the specific regulatory task, and the finding or strategic decision made — can show clients what the invisible hours produced. The six-hour density calculation review becomes a work log entry that documents the net vs. gross acreage discrepancy and the maximum unit count under the general plan designation. The eight-hour initial study review becomes a record of the biological survey timing inadequacy and the breeding season survey required before circulation. The four-hour conditions analysis becomes documentation of the six conditions negotiated to acceptable language before the hearing.

HourTab is a retainer hours dashboard built for advisory relationships like land use planning retainers where the client value is created between milestones. The land use planner logs time against specific regulatory research and agency coordination tasks with notes on the findings and decisions made, and shares a public URL that gives the developer or owner a running view of the current hours balance and the work log from the current retainer period — without requiring status emails or monthly reporting calls to understand what the retainer hours produced.

Setting up a land use planning retainer agreement

Land use planning retainer agreements should define the scope with enough specificity to distinguish routine advisory work included in the monthly retainer from additional scope that requires a separate fee estimate. A retainer structured as “land use planning advisory, 20 hours per month” without specifying the regulatory scope, project stage, and deliverables creates scope ambiguity about whether public hearing attendance, CEQA document preparation, and agency appeal support are included in the monthly retainer.

A well-structured land use planning retainer specifies: the regulatory scope covered (zoning compliance research, CUP strategy, CEQA review, NEPA review, general plan amendment, specific plan, development agreement, or a defined combination); the project stage and activities within the retainer period (pre-application due diligence and zoning analysis, application preparation and submittal support, agency review period coordination, environmental review support, public hearing preparation, post-approval compliance and condition satisfaction); the specific deliverables (zoning compliance and entitlement strategy memo, CEQA exemption analysis, initial study peer review, conditions of approval analysis matrix, hearing presentation materials, administrative record index); the applicable jurisdictions and regulatory frameworks (city, county, coastal commission, state resource agencies, regional planning agencies); and the hours tracking mechanism that gives the developer or owner visibility into advisory work between application submittals and hearing milestones.

Monthly retainer amounts for land use planning advisory typically range from $3,000 to $10,000 per month depending on project complexity, the number of entitlement tracks being pursued, and whether the retainer includes public hearing attendance and agency coordination meetings. Developers and property owners who can see the land use planner’s work log throughout the entitlement process are better positioned to direct advisory hours toward the highest-risk regulatory issues, to recognize when a zoning code ambiguity or an environmental review finding requires immediate pre-application clarification, and to document the advisory work that prevented the application delays, conditions disputes, and hearing complications that never appear in the project’s entitlement history.


HourTab turns a time-tracker CSV into a public retainer-hours URL your client can bookmark. No client login. No portal setup. Start free →