Before the Agenda Posts
Why the first public hearing is the worst time to introduce a project, and what developers should do earlier to reduce risk.
March 4, 2026
If the first time a community hears about a project is when a city council or commissioners court agenda item gets posted, you’re already in reactive mode.
It’s rarely intentional. It’s what happens when diligence is still moving, nobody wants to overstate certainty, and then the permitting process triggers a hearing and the calendar outruns the communications plan.
In a perfect world, development would be a straight line from site control to diligence to permits to construction. But in reality, it is a rolling set of business decisions made under uncertainty: deal fundamentals, utilities and deliverability constraints, diligence findings, regulatory and permitting pathways, local leadership dynamics, election cycles, public sentiment, and the story the community starts telling about what is coming.
From the inside, it is a constant balancing act across variables that do not wait politely for the permitting timeline. They collide, they shift, and they force hard calls about timing, sequencing, and what can responsibly be said in public.
In early development, you’re managing two kinds of risk at the same time: project risk and reputational risk. Project risk is feasibility, timeline, approvals, conditions, cost, and execution. Reputational risk is credibility, trust, leadership relationships, and whether the project becomes “the thing people fight about” even if it is technically sound. The catch is they’re linked. Reducing one can accidentally inflate the other.
Some projects fail because a permit gets denied. Others get delayed, conditioned, resized, or reshaped because one variable moves and the rest of the stack starts to wobble.
That’s what this piece is about: development as variable management. You’re not just building a facility. You’re underwriting a community context with imperfect and evolving information, and the outcome depends on whether you can keep feasibility, governance, and community expectations aligned at the right pace and in the right order.
THE REAL STACK DEVELOPERS ARE BALANCING
Every project is running on multiple tracks at once. The mistake is treating them as separate. In reality, they are coupled. When one variable moves, everything else has to be recalculated.
In a perfect world, development would be linear: site control → diligence → permits → construction.
In reality, it’s variable management under uncertainty.
1) Deal Variables: The Project Has to Pencil
Customer certainty: signed agreement vs “in progress” vs “likely,” and how quickly that can change
Capex and financing: cost of capital, internal capital allocation, timing pressure
Incentives and tax posture: what is needed to compete, what is defensible publicly, what conditions get attached
Risk tolerance: speed to market vs reputation posture, and what “acceptable delay” actually means
Reputation posture: how much volatility the developer is willing to absorb before the brand, future pipeline, or local relationships start taking real damage
2) Deliverability Variables: Can This Actually Be Built
Power path realism: interconnection timelines change, upgrades expand, assumptions get revised
Water and wastewater capacity: not just availability, but drought sensitivity and perception
Land use and permitting pathway: by-right vs discretionary approvals, hearings, conditions, and sequencing
Construction capacity: contractor availability, supply chain, workforce, schedule risk
3) Governance Variables: How Decisions Actually Get Made Locally
Elected leadership and professional staff carry different risks: staff protect process and defensibility; electeds absorb the public heat
“Ownership” matters: is this being led by a city manager, an EDC, a planning director, a mayor, a county judge, or a coalition behind the scenes?
Election cycles and shifting coalitions: today’s aligned council is not guaranteed to be tomorrow’s council
Institutional memory: residents filter new proposals through old disappointments, whether that was jobs hype, a broken promise, or a previous fight that left scars
Sometimes the council and city manager are fully supportive from day one. That support helps, but it also becomes a variable to manage. Supportive leaders still need process integrity, public credibility, and protection from “closed door” narratives if the project becomes controversial.
4) Narrative Variables: What People Think Is Happening
The project people imagine is often not the project being proposed
Trigger issues show up quickly: water, traffic, noise, taxes, secrecy, “outsiders,” property values, growth changing the identity of the place
Information velocity is real: local media, civic groups, and Facebook groups where the story can harden overnight
The organized few vs the quiet middle: opposition is not always a majority, but it is often the most disciplined and persistent presence
“Don’t let the public agenda be your launch plan. If people meet the project for the first time at public comment, you’re managing surprise and distrust.”
THE HARDEST DECISION IN EARLY DEVELOPMENT: WHEN TO TALK ABOUT IT
Developers get trapped between two bad options.
Talk too early and you are out ahead of diligence. You feed a rumor engine with gaps. If assumptions change, the community hears, “they changed their story.” That’s reputational risk turning into project risk, because now every change has to be defended as a credibility issue.
Talk too late and people feel acted upon. Local leaders feel boxed in. The narrative gets written without you, and you are responding to it instead of shaping it. That’s project risk turning into reputational risk, because the first impression becomes “they did this to us,” even if the process is still technically open.
The right approach is not “announce” or “stay silent.” It is sequencing.
Governance Calendar Is a Variable
There is one moment that consistently creates avoidable turbulence: the first public hearing or vote where residents can speak, like a city council meeting or commissioners court agenda item with public comment.
That is not the moment to make the first communication about a project.
By the time an item is posted, people interpret it as a decision already in motion. They start asking, “Why are we only hearing about this now?” The meeting becomes a referendum on process and trust, not a discussion of facts. And the developer and local officials are forced into reactive mode on the most visible stage.
Treat those calendar moments as a variable that requires foresight. If a public agenda item is the first time the community is introduced to a project, you’re not communicating. You’re managing surprise.
A practical rule: Clear three thresholds before you “go public”
Feasibility threshold: Is this real enough to stand behind without walking it back?
Leadership readiness threshold: Are local leaders briefed and prepared so nobody is surprised or left exposed?
Explainability threshold: Can you clearly state what’s decided, what’s not, and what the community can influence?
A practical test: if a hearing or vote is scheduled before you’ve cleared explainability, you’re already behind.
The combinations matter:
(1) + (2) without (3): The project is real and leaders are aligned, but the story isn’t explainable. That’s where vague statements and information vacuums create fast reputational risk.
(1) + (3) without (2): You can explain it, but leadership isn’t prepared. Officials get blindsided, governance friction rises, and process slows down.
(2) + (3) without (1): The message is ready and leaders are supportive, but the project isn’t firm enough. Changes later become credibility problems, and project risk rises.
All three: You can brief leaders responsibly and engage the community without overpromising. Projects stabilize earlier and spend less time reacting.
Bottom line: thresholds are a risk tool. They help you sequence engagement without trading project risk for reputational risk.
”Supportive local officials need cover - process, clarity, and defensibility”
WHEN LOCAL OFFICIALS ARE FULLY SUPPORTIVE, THE ENGAGEMENT BAR OFTEN RISES
In some communities, the local governing leadership is fully supportive early on. That may be a city manager and council. It may be a mayor, a county judge, or an economic development team with strong alignment from elected officials. They want the investment, they see the upside, and they are ready to move.
That support can accelerate a project. It can also create backlash if residents interpret it as a decision already made, especially if the first time the public hears about the project is after leaders have already signaled enthusiasm. The political risk doesn’t disappear because local officials are supportive. It often concentrates on the people who supported it first.
In these situations, engagement is not about winning local officials over. It’s about helping supportive local leaders lead without becoming the target.
What local leaders typically need:
Clear lines between what’s settled vs still under diligence so they do not overcommit publicly
Plain-language answers to predictable concerns (utilities, water, traffic, taxes) they will be asked to defend
A defensible process and timeline that shows where public input fits and how it will be handled
This is how you protect leadership alignment as an asset while still respecting the broader community.
WHAT THIS LOOKS LIKE IN REAL MEETINGS
A planning director asks, “What exactly is the zoning ask, and why does it need to change here?”
A city manager asks, “If we move forward, what are we committing the city to over time?”
A council member asks, “Why am I hearing about this from a community group before I heard it from you?”
A resident asks, “How much water, exactly, and what happens in drought conditions?”
A business leader asks, “What is the local workforce outcome, not just the tax base story?”
An opposition organizer asks, “Why should we trust you when the last big deal overpromised?”
“If you wait to explain, you inherit whatever story forms first. Community context is part of diligence, not a follow-on task.”
THE GOAL IS NOT UNANIMITY. THE GOAL IS STABILITY.
The goal is that when the hearing happens, it is not the first introduction. It is a decision point in a process people have already seen.
Every community will have disagreement. That is normal. The goal is to reduce preventable turbulence:
Avoid surprises
Respect process and people
Communicate uncertainty honestly
Make commitments specific and verifiable
Take critics seriously without letting them define the whole community
Because development is not a single approval moment. It is a long operating relationship with a place. And you cannot manage that relationship if you never underwrite the community context.
WHERE COOVER | GOSS FITS: LISTENING AS DUE DILIGENCE
Traditional diligence focuses on land, permits, utilities, and legal risk. Those are necessary. But they are not sufficient.
We treat listening and local intelligence as a form of diligence because it reduces uncertainty inside the variable stack. It clarifies the landscape internally for developers, and it creates stability externally for local leaders and the broader community, especially when local officials are aligned and moving fast.
Our work is designed to surface what the project cannot see from the outside
Stakeholder reality mapping (formal and informal influence)
Governance dynamics (who carries risk, who needs what to stay credible)
Narrative and risk signals (what will trigger concern here, and why)
Trust baseline assessment (neutral, skeptical, supportive)
Friction testing (where the story breaks under pressure)
Sequencing support (briefing leaders, engaging residents, communicating uncertainty)
When you understand the community context early, it changes better business decisions: how incentives are structured and explained, how commitments are framed and documented, how engagement is sequenced, and how uncertainty is communicated without walking into credibility traps.
A better sequence looks like this: brief local officials early so they’re not surprised, build a simple explanation of what’s decided vs not decided, and create an initial first touch with the community before the agenda post. Sometimes that’s small-group conversations. Sometimes it’s a public-facing FAQ. Sometimes it’s a listening session.
“Development is not a single approval moment. It is a long operating relationship with a place. And you cannot manage that relationship if you never underwrite the community context.”
Coover | Goss is a Texas-based strategic communications and community engagement firm supporting infrastructure developers and operators across the energy and digital infrastructure landscape. We help teams build durable local permission through research-driven engagement strategy, stakeholder mapping, and on-the-ground execution.