Reading a Staff Report Before a Claremont Hearing

Before almost any public hearing on a project, city staff publish a written report. It is the single most useful document in the entire process, and most residents never open it.

People show up to the meeting instead. They hear the applicant, hear the staff summary, and try to form a view in real time. That is the hardest possible way to understand a proposal. The report was posted in advance precisely so you would not have to.

What a staff report is, and what it is not

A staff report is the professional planning analysis of an application, written by the planner assigned to the file and reviewed by the department. It states what is being asked for, what the rules require, whether staff believe the request can be approved, and on what terms.

It is NOT the decision. Staff recommend; the hearing body decides. A recommendation of approval can be rejected, and a recommendation of denial can be overturned. Treat the report as the best-organized argument in the room, not the outcome.

It is also not neutral in the way a court record is neutral. It is written by the department that has been working with the applicant for months. That does not make it dishonest. It does mean the report tends to describe a project in its revised, post-negotiation form rather than as originally submitted.

The anatomy of the document

• The cover summary. Applicant, location, the specific permits requested, and the recommended action. Read this first to learn what is actually on the table.
• Background. The parcel, its zoning and any overlay, the surrounding uses, and the history of prior applications on the site.
• Project description. The proposal in words, which should match the plans in the attachments. When they disagree, the plans control.
• Analysis. Staff walking the proposal against each applicable standard, one at a time.
• Findings. The specific legal statements the body must be able to make in order to approve.
• Environmental review. A statement of how the project was handled under state environmental law, including whether an exemption was applied.
• Conditions. The numbered obligations attached to any approval.
• Attachments. Plans, elevations, technical studies, correspondence received.

Read it backwards

The most efficient order is not front to back. Start with the conditions, because they describe the project that would actually get built. Then read the findings, because they are what an appeal or a lawsuit would attack. Then read the analysis for the reasoning that connects the two. The narrative background can wait.

Reading in that order also protects you from the most common mistake, which is arguing with the project description while the operative document sitting three sections later says something different. The conditions of approval are the fine print that survives the meeting.

What the analysis section is really doing

The analysis is staff demonstrating that each applicable standard has been addressed. Read it as a checklist rather than as persuasion, and look for three things.

First, standards that are met by a deviation rather than by compliance. If a dimension is achieved through a variance, an adjustment, an averaging provision, or a concession granted under state law, the analysis will say so, often quietly. That is where the real argument lives.

Second, standards handled by deferral. Language along the lines of a detail to be resolved at plan check, or a study to be submitted before permit issuance, moves a question out of the public hearing and into a staff-level review with no further notice. Sometimes that is routine. Sometimes it is the whole issue.

Third, silence. A standard that plainly applies and is never discussed is worth a question, and questions are cheaper to ask before the meeting than during it.

The attachments carry the facts

Narrative can characterize; drawings cannot. The site plan shows the footprint and the setbacks. The elevations show height and massing. A landscape plan shows what will actually screen a property line, and whether the screening is mature at planting or much later.

Technical studies are attached rather than summarized for a reason. A summary of a traffic or acoustic study is one sentence; the study itself states its assumptions, and assumptions are what a comment letter can meaningfully challenge.

Correspondence attachments matter too. They show what neighbors have already raised, which tells you whether your concern is new information or a repeat of something staff have already answered.

Getting the report, and the timing

Staff reports are published with the agenda packet ahead of the hearing, and the posting interval is set by state open meeting law and by local practice. The document is a public record either way. If you cannot find it online, ask the planning division for the packet for that agenda item by project address.

Read it as soon as it posts. Revisions and supplemental memos are sometimes released later, occasionally the day of the meeting, and a late memo can change a condition that your comments were built around. Check for one before you speak. Our guide to the planning commission for beginners covers what happens once the item is called.

Turning the report into a useful comment

The report tells you what the decision-maker is required to find. That is your target. A comment that identifies a finding the record cannot support is a comment the body has to deal with. A comment about how you feel about growth is one it may listen to politely and then set aside.

Cite the section. Name the condition number. Quote the sentence you disagree with. Precision is not pedantry here; it is the difference between a remark and an objection that has to be answered on the record.

The practical takeaway

The staff report is the map of the argument. Everything the hearing will discuss is in it, in writing, before anyone speaks. Reading it turns a confusing meeting into a short list of specific questions.

Verify every point here against the actual report and the city file for the specific application. General descriptions do not bind anyone; the document on the agenda does.

For how the wider approval system fits together, start at our City Development hub, and read how to read a development proposal before the report itself lands.

Anthony Grynchal has been licensed in California since November 2009.