Saying No on the Record: A Planning Director’s Playbook for Defensible Denials
Photo: Seattle Municipal Archives from Seattle, WA, CC BY 2.0, via Wikimedia Commons
Few tasks unsettle a planning director more than recommending denial of a development application that has already gathered political momentum. The applicant has spent money. The council has heard promises. Neighbors have organized. In that setting, a denial can feel like an act of institutional resistance rather than a straightforward application of policy. But saying no is part of the job. The question is whether the decision will be legible, consistent, and defensible. In 2026, with housing pressure, infrastructure constraints, and public scrutiny all bearing down on local government, the ability to deny well is a core leadership skill.
Anchor the Denial in Adopted Policy
When staff recommends denial, the recommendation should rest on adopted policy rather than staff preference. Cite the comprehensive plan, future land use map, zoning ordinance, design guidelines, small area plan, or adopted capital improvement program. Use specific provisions and explain how the application fails to satisfy them. If the proposal conflicts with several policies, present the conflict in a simple table that shows the policy, the requirement, and the application response.
This approach matters for two reasons. First, it gives the applicant a clear understanding of what would need to change. Second, it gives elected officials a defensible basis for their vote. A denial framed around staff taste invites accusations of arbitrary behavior. A denial framed around adopted policy invites a conversation about standards.
Planning directors should also resist the temptation to improvise policy at the dais. If the adopted plan is ambiguous, say so. If the code does not address a particular issue, acknowledge the gap. A deferral, a request for more information, or a recommendation to update the code can be more honest than a denial that stretches the text beyond its meaning.
Build the Record Before the Hearing
The administrative record should be assembled as the application moves through review, not reconstructed after a controversy. The staff report should state the request, the relevant code criteria, the findings, the evidence, the public comment summary, the applicant response, and the alternatives considered. Include traffic data, drainage analysis, fiscal notes, site photographs, and correspondence. Write in plain language. Avoid adjectives that suggest motive. Document site visits and meetings. If legal counsel reviewed the recommendation, note that review.
A strong record does more than protect the city. It respects the applicant. Developers and property owners may disagree with a denial, but they are less likely to feel ambushed when the reasoning is transparent. A clear record also reduces the risk of appeal and gives the planning commission or council a shared factual foundation.
Offer a Credible Alternative
A denial without a path forward feels arbitrary. Staff should identify what could make the proposal approvable: reduced height, added setback, preserved trees, improved access, traffic mitigation, affordable units, phased utilities, or a different site plan. This is not an invitation to negotiate away standards. It is a way to show that the department is solving a problem rather than simply closing a door.
If the site is fundamentally unsuitable, say so and explain why. Suggest other parcels or densities that align with the plan. If the applicant needs a different approval process, explain it. The goal is to leave the applicant with a clear next step, even if that step is a revised application or a different location.
Keep the Hearing Professional
At public hearing, staff presents findings, not arguments. Acknowledge the applicant’s investment and the seriousness of the decision. Avoid adversarial language. Refer to the application as submitted rather than the developer. If council members ask for options, provide them, along with the consequences of each. If the council overrides the recommendation, document the conditions and the rationale. Follow up with the applicant after the decision.
Constituents remember tone. They may forget the details of a parking calculation, but they will remember whether they were treated with respect. A professional denial preserves the department’s credibility for the next application, the next election, and the next comprehensive plan update.
Accept That Some Denials Will Be Unpopular
Some projects should be denied. They may be unsafe, incompatible with adopted plans, chronically noncompliant, or dependent on spot zoning. Approving them to avoid conflict erodes trust in the planning process. A well-documented denial is not a failure of collaboration. It is a professional act.
Planning directors should measure success by clarity, consistency, and fairness rather than approval rates. In 2026, public confidence in local institutions is fragile. The ability to say no on the record, with reasons and alternatives, strengthens the institution. The art of the no is not refusal for its own sake. It is making refusal understandable to the people who must live with the outcome.