Mesa has taken another step toward the proposed Legacy Park development near Ellsworth and Williams Field roads, but the council action needs a careful distinction: the August 27 vote concerned a notice of intent for a tax-incentive agreement, not final approval of the development agreement itself.

The council adopted the notice in a 6–1 vote, with Councilmember Jenn Duff opposed, according to Mesa Independent reporting by Janet Perez, excerpted by Rose Law Group Reporter. Mesa’s online meeting record still lists draft minutes and does not yet display the roll-call result, so that tally is attributed to the published reporting.

For the location, proposed retail and resort components, and longer-term construction outlook, see our Legacy Park Mesa development guide.

What did the August 27 vote cover?

The item was Resolution No. 12568, city file 26-0793, for the combined Legacy Park and Gateway Crossing project area near State Route 24.

Mesa’s August 27 council report explains that the notice must precede consideration of the agreement by at least 14 days. It explicitly says approval of the notice does not approve the development agreement.

The proposed arrangement would reimburse a portion of construction sales tax, retail sales tax and transient lodging tax generated by the project for certain public infrastructure. Staff describes that infrastructure investment as necessary for the planned commercial development.

The report identifies no fiscal impact from adopting the notice itself. That statement applies to this preliminary notice; it does not establish the financial terms or cost of a future agreement.

What changed at the August 31 council meeting?

A separate set of land-use actions followed. Mesa Independent reported that the council introduced three ordinances on August 31: annexation measures for roughly 196 acres at Legacy Park and 5 acres at Gateway Crossing, plus a rezoning measure for the Legacy Park parcel.

The zoning request is ZON25-00891, covering approximately 196.3 acres at the northeast corner of Ellsworth and Williams Field roads. It seeks a change from Light Industrial to Planned Community District for a mixed-use community.

Introducing an ordinance is a step toward a later decision. Readers should not interpret the August 31 introduction as evidence that the annexation and rezoning ordinances have already received final adoption.

Why do Legacy Park acreage figures differ?

The documents describe different boundaries. The zoning case covers approximately 196.3 acres. The August 27 council report describes Legacy Park as approximately 209 gross acres and neighboring Gateway Crossing as approximately 37 gross acres. The notice resolution’s Exhibit A identifies approximately 233 acres of project real property.

Those figures should stay attached to their specific documents and purposes. They are not interchangeable measurements of the zoning parcel.

What happens next?

Staff’s August 27 report identifies September 14, 2026, at 5:45 p.m., or a later council meeting, as the intended time for consideration of the development agreement. That is a planned next step, not a guaranteed vote date. Check the City of Mesa meeting calendar for the posted agenda and any changes before attending.

The next agreement and council materials are where residents should look for reimbursement limits, eligible infrastructure, deadlines and developer obligations. Final annexation and zoning actions also need to be tracked separately.

What this means for nearby residents

For Cadence at Gateway and other southeast Mesa neighborhoods, these actions are milestones to follow as the proposed district moves through city review. They do not supply a groundbreaking date, a tenant opening date or a construction traffic schedule.

This coverage concerns the proposed mixed-use Legacy Park development beside Arizona Athletic Grounds. The sports complex previously used the Legacy Park name; the two should not be confused.

We will add substantive council decisions and confirmed project announcements to the main Legacy Park guide and coverage timeline. This update reflects records and reporting reviewed September 6, 2026.