Staff Recommendation

Definition (first 40 words): A staff recommendation is the written opinion of a city or county's planning department staff on a land-use application — approve, approve with conditions, deny, or continue. Across tracked cases, staff recommendations predict the planning commission's final vote in approximately 80% of instances.

In short

The staff recommendation is the single most predictive field on any planning application. Before a rezone, variance, CUP, or site plan ever reaches the planning commission, professional planning staff analyze it against the zoning code, general plan, conditions of approval precedents, and community input — and write a formal recommended action. Commissioners overwhelmingly follow staff. CityMinutes data across 5,200 tracked cases shows staff recommendations match final commission votes ~80% of the time. Extracting this field from weekly meeting packets across 3,142 US counties gives land buyers, BD teams, and spec reps a structured probability-of-approval signal before the gavel ever drops.

What is a staff recommendation in the planning process?

A staff recommendation is the written professional opinion of a city or county's planning department on a pending land-use application. It is prepared by a staff planner (often the case planner assigned when the application is filed) and reviewed by a supervisor before release. The recommendation is published in the staff report — a document typically 15–60 pages long — distributed with the planning commission's meeting packet 5–10 days before the hearing. The recommendation is advisory; the commission is not bound to follow it, but in practice it usually does.

What do planning staff actually do?

Planning staff review every application against four lenses: (1) consistency with the zoning code — does the project comply with allowable use, density, height, setbacks, parking? (2) consistency with the general plan — does it fit the jurisdiction's long-range vision? (3) impact analysis — traffic, environmental, infrastructure, aesthetic, neighborhood fit. (4) public input review — what have neighbors, community groups, agencies, and tribes said during the public comment period? Staff then draft conditions that address their concerns, and write a recommendation.

The four types of staff recommendations

1. Approve — staff recommends the application be approved as submitted. Rare — occurs in roughly 7% of cases. Usually reserved for small, uncontested, code-compliant applications.
2. Approve with conditions — staff recommends approval subject to a list of conditions of approval. The most common outcome — roughly 71% of cases. Staff add 5–20 conditions addressing their concerns.
3. Deny — staff recommends the application be denied. Occurs in roughly 9% of cases, typically when the application conflicts with the general plan.
4. Continue / return to applicant — staff recommends the commission not vote, and instead continue the hearing to a future meeting or return the application for revisions. Occurs in roughly 13% of cases.

Why staff recommendations predict commission votes ~80% of the time

Four structural reasons:

1. Information asymmetry. Staff read every page of the application, meet with the applicant, and do site visits. Commissioners often skim the packet the night before. The information gap favors staff's analysis.
2. Professional norm. Planning is a profession with a code of ethics (AICP) and a shared analytical framework. Commissioners — who are volunteers, often laypeople — defer to professional analysis by default.
3. Procedural safety. Voting against staff creates appeal and litigation risk. If staff said approve and the commission denies, the applicant has clean grounds for appeal.
4. Consensus building. Staff negotiate conditions with applicants before the hearing — a recommendation "approve with 18 conditions" is often the pre-negotiated consensus, not a coin flip.

The ~20% where commissions override staff usually involves: highly contested projects with strong community opposition, projects that became politically charged between staff's report and the hearing, or projects where commissioners have preexisting views on the underlying policy question.

How to read a staff report

A typical staff report has eight sections. Read them in this order:

1. Recommendation (usually page 1 or 2) — the bottom-line action. Read this first.
2. Summary of the application — what the applicant is asking for.
3. General plan consistency — is it consistent with the long-range plan? Most important legal test.
4. Zoning consistency — does it comply with the zoning code?
5. Environmental review (CEQA/NEPA) — any environmental issues or exemptions claimed.
6. Conditions of approval — the specific obligations staff wants attached.
7. Public comment summary — what neighbors and agencies have said.
8. Findings — the legal basis for the recommendation.

Staff recommendation outcome vs final commission vote (cityminutes 2023–2025)

Staff recommendation	Commission concurs	Commission overrides
Approve	91%	9%
Approve with conditions	84%	16%
Deny	72%	28%
Continue	79%	21%
Overall	~80%	~20%

Why competitors don't extract staff recommendations

Staff recommendations are buried in unstructured PDF staff reports. There is no standardized format — each jurisdiction writes its own. Extraction requires LLM-assisted classification into the four categories plus parsing the conditions list. Shovels+ReZone's Decisions-data schema does not include staff recommendation as a structured field. Boardwalkai does not extract it. Regrid has no planning data. Staff recommendation is one of the four fields in cityminutes' defensible wedge.

Frequently Asked Questions

Is a staff recommendation the same as a planning commission decision?

No. Staff recommendations are advisory professional opinions. Planning commission decisions are the formal vote on the application. The commission can follow or override staff.

When is a staff recommendation released?

Typically 5–10 days before the planning commission hearing, bundled into the commission's meeting packet.

Can the applicant negotiate with staff before the recommendation is written?

Yes — and they usually do. Most contested applications go through 2–6 rounds of staff-applicant negotiation before the recommendation is finalized.

How do I find staff recommendations for pending projects?

Planning commission packets are public records, typically posted on city or county websites 5–10 days before meetings. CityMinutes extracts every staff recommendation from every packet across 3,142 US counties.

Can a commission override a staff "deny"?

Yes, and it happens in roughly 28% of denial cases in the cityminutes dataset. Typically requires the commission to make alternative findings on the record.

What's the difference between a staff recommendation and a staff report?

The staff report is the full document (15–60 pages). The staff recommendation is the specific recommended action embedded in the staff report.

Are staff recommendations binding on city council?

Not directly. Staff writes recommendations for planning commissions. Commissions make recommendations to councils. Councils take the final binding vote.

How cityminutes extracts this field

Staff recommendations are the keystone of the 4-field wedge. CityMinutes runs an LLM-assisted extraction pipeline that reads staff reports from covered planning commission packets across the 3,142-county target coverage map on a weekly refresh cycle. We classify each recommendation into one of four normalized outcomes, extract the underlying reasoning, link it to the application's parcel and project records, and surface it alongside the final commission vote.

CTA

See staff recommendations for every active rezone, variance, and CUP across 3,142 US counties.

Request a demo →

Related terms

• Planning commission
• Conditions of approval
• Rezone application
• Conditional use permit