How Public Staff Recommendations Really Get Written and How Developers Influence Them
ASK:
Staff says they support projects objectively. How are staff recommendations actually formed?
ANSWER:
Public staff recommendations are not written in isolation, and they are not written at the last minute. They are shaped gradually over the life of a project, long before anything appears on a public agenda.
After nearly twenty years working inside and alongside entitlement processes, one thing is consistent. Staff reports reflect accumulated trust, preparation, and follow-through. They are not reactions to a single hearing, presentation, or submittal.
Staff are responsible for protecting the city. Their role is to balance policy compliance, operational feasibility, political awareness, and public accountability. Their recommendation is not meant to advocate for the applicant. It is meant to ensure the project aligns with adopted plans and can be implemented without creating risk for the jurisdiction.
Developers who understand this dynamic are far more effective.
In practice, staff recommendations are shaped by three primary factors.
- How well the project aligns with adopted plans, zoning, and code requirements.
- How responsive and prepared the development team has been throughout the process.
Third, how much uncertainty still exists when the report is drafted.
Uncertainty is the fastest way to weaken support. When staff still have unresolved questions, unclear mitigation strategies, or concerns about execution, those issues show up as added conditions, neutral recommendations, or cautious language in the staff report.
At I&D Consulting, we focus on influencing staff recommendations long before they are written. We engage early to clearly explain the project and establish a concise, consistent narrative. We make sure plans, studies, and applications tell the same story. When staff provides feedback, we close loops quickly and document resolutions so there is no ambiguity about how issues were addressed.
Our goal is not to persuade staff at the end of the process. It is to remove uncertainty throughout it.
Staff support is earned through predictability and follow-through. Developers who treat staff as partners in implementation, rather than gatekeepers to approval, consistently see staff reports that read differently.
KEY TAKEAWAYS:
- Staff recommendations reflect the cumulative process, not single meetings
• Uncertainty weakens staff support
• Early engagement shapes outcomes
• Predictability and follow-through build trust
People Also Ask
1) Can staff change recommendations late in the process?
Yes. Recommendations can change if new information surfaces or unresolved concerns remain, particularly after public noticing or community feedback. Developer-led neighborhood meetings and early outreach often help identify and address these issues before they escalate late in the process.
2) Do staff recommendations determine outcomes?
Often, but not always. On discretionary approvals where judgment and conditions play a role, staff recommendations carry significant weight. However, public testimony, political context, and broader policy considerations can also influence commission and council decisions.
3) How should developers communicate with staff?
Development is a relationship-driven process. Clear, consistent communication and documented follow-through build trust with staff. That trust enables more productive conversations and leads to projects that are better aligned with community needs and expectations.
