Findings: The Sentences That Hold an Approval Together

An approval is not a vote in favor of a building. It is a set of written statements the decision-maker has to be able to make truthfully, supported by evidence in the record. Those statements are the findings.

Findings are the least glamorous part of a land use file and the part that most often decides a legal challenge. Projects rarely lose because someone disliked them. They lose because a required sentence could not be honestly written, or was written with nothing behind it.

What a finding is

A finding is a factual conclusion that bridges the raw evidence and the legal standard. The code says a permit may be granted only if certain things are true. The finding is the body stating that those things are true here, on this parcel, for these reasons.

The classic formulation is that findings must bridge the analytic gap between the evidence and the decision. A conclusion with nothing under it is a restatement, not a finding. Copying the code language and adding the word "is" produces a sentence that reads like a finding and does none of its work.

Every discretionary approval carries its own required set. A conditional use permit has one list, a variance a different and considerably harder one, a subdivision map another, and a design approval another again. The lists are not interchangeable, and each has to be satisfied on its own terms.

Why they are the attackable part

Courts reviewing a local land use decision generally do not re-decide whether the project was a good idea. They ask a narrower question: did the body make the required findings, and is there substantial evidence in the record supporting them?

That framing is why challenges land here. An argument that a project is too large is a matter of judgment the city is entitled to make. An argument that a required finding was made with nothing in the file behind it is a legal defect rather than a difference of opinion.

It also explains why staff reports contain long, careful paragraphs under a findings heading. Staff are building the record that the finding rests on, in advance, in writing.

How to read them on a real file

• Locate the required list. Find the code section governing that permit type and read the findings it demands. Then compare it to the ones actually proposed.
• Check for evidence, not adjectives. A finding supported by a study, a plan sheet, a photograph, or a site condition is doing its job. One supported by the word "appropriate" is not.
• Watch for conditions doing the lifting. Findings are frequently made possible only because a condition is attached. That is legitimate, but it means the finding depends on the condition surviving and being enforced.
• Look for the hardest one. Each permit type has a finding that is difficult to make. On a variance it is usually the one about circumstances peculiar to the property. That is where to read closely.

Findings for denial exist too

A body that denies a project also needs findings, and they are subject to the same standard. It cannot simply announce a denial after public testimony and move on. It must state which required finding it is unable to make and why the record does not support it.

This is often a surprise to residents who assume opposition alone is sufficient. It is not. Public sentiment is part of the record, but a denial resting entirely on the volume of comment rather than on an unmet standard is exposed on appeal.

The practical consequence is that useful public testimony aims at a finding. Explain why a specific required statement cannot honestly be made on this parcel, and you have given the body something it can act on.

Findings and conditions are different animals

People conflate them constantly. A finding is a statement about why the approval is lawful. A condition is an obligation imposed on the applicant. Findings justify; conditions control.

They are linked because a condition often supplies the fact that makes a finding possible. If the finding on drainage depends on a condition requiring a retention system, then removing that condition quietly removes the basis for the finding. This is why late-stage condition edits deserve attention, and why the fine print on a project is worth reading alongside the findings themselves.

Where findings live after the meeting

Adopted findings appear in the resolution or the notice of decision, not only in the staff report. The staff report proposes them; the adopted document is what the city actually stands behind. When a body modifies findings from the dais, the adopted text controls and the report becomes background.

Ask for the adopted resolution if you are evaluating an approval after the fact, whether as a neighbor, a buyer, or a future applicant on the same parcel. Prior findings on a site are useful precedent and occasionally an obstacle.

The practical takeaway

If you want to understand whether an approval is solid, do not count the votes. Read the findings and ask what evidence each one stands on. A well-supported set is durable. A set of conclusory sentences is a liability the city is carrying.

Verify the required findings for any permit type against the current code and the adopted resolution for the specific case. General descriptions do not bind anyone; the code and the resolution do.

Start at our City Development hub for the wider system, and read how variances work for the permit type with the strictest findings of all.

Anthony Grynchal has been licensed in California since November 2009.