By the Coral Gables Gazette editorial board

Residents who attend Tuesday’s Sunshine Neighborhood Meeting on the University Station Rapid Transit Overlay District will hear a discussion centered on a single site: 6100 Caballero Boulevard, near the Gables Waterway. The proposal to include that property in the overlay has drawn attention for its location, visibility, and the scale of development it could enable.

One week later, the City Commission is scheduled to vote on something larger.

The April 14 agenda includes not only the addition of the Caballero site but also a set of zoning and land-use changes affecting multiple properties across the corridor, along with site plan approval for a major mixed-use development at 1250 South Dixie Highway. The scope of that vote extends beyond the focus of the neighborhood meeting. The difference between the two frames — what is discussed and what is decided — defines the issue.

This is not a question of legality. The Sunshine Neighborhood Meeting fulfills a required step in the amendment process. Residents may attend, ask questions and offer input. The City Commission will consider that input before voting.

It is a question of clarity.

Public participation depends not only on the opportunity to speak, but on a clear understanding of what is at stake. When a meeting centers on a single site while the subsequent vote includes broader changes to density and land use across multiple parcels, the connection between discussion and decision becomes less direct. Residents focused on the Caballero proposal may not see the full scope of the changes moving alongside it.

The structure of this process reflects a more complex reality. Development near Metrorail stations in Miami-Dade County operates within a framework that allows developers to pursue approval through the county’s Rapid Transit Zone program rather than through municipal review. That framework limits the city’s ability to block projects outright and places a premium on creating a local process that developers will choose to use.

The University Station overlay emerged from that condition. It offers an alternative path — one that preserves local design standards, review boards, and planning tools such as Transfer of Development Rights. It also requires the city to act with a degree of coordination and timing that aligns policy, zoning, and project review. That context explains why multiple elements appear together in a single legislative moment.

It does not remove the need for clarity.

The city should ensure that future Sunshine meeting notices describe the full scope of what the commission will vote on — not just the immediate subject of the neighborhood discussion — so that the public record reflects the decisions residents are actually being asked to engage. That standard is achievable within the constraints the city faces. It requires no additional hearings, no delays, and no abandonment of the overlay framework. It requires only that the notice match the vote.

The changes under consideration are not temporary adjustments. They are amendments to the Comprehensive Plan and Zoning Code that will govern development in the corridor over time. They redefine allowable density, building height, and land use across multiple properties. Once adopted, they establish a framework that will shape what can be built — and where — for years to come.

Decisions of that permanence benefit from a public process that reflects their full scope.

Coral Gables has chosen to engage the realities of transit-oriented development rather than defer entirely to county jurisdiction. That approach carries both opportunity and responsibility. It allows the city to shape growth within its borders. It also requires that the process by which that growth is defined remains as transparent and legible as the standards it seeks to enforce.

The April 14 vote will determine the next phase of development in the University Station corridor. The framework for that decision is already in place. The task now is to ensure that the public understanding of that framework is as complete as the framework itself.