City Plan CommissionThursday, May 7, 2026 · 9:00 AM · Council Chambers, 6TH Floor

Why now: Z-26-000015 appears under two separate item numbers (9 and 15) on the May 21, 2026 City Plan Commission agenda, both recorded as 14-0 carried, with Item 9 specifically noted as tabled and heard out of sequence — no explanation appears in the public-facing timeline for three appearances spanning April 9 through May 21.

What to do: File a public records request for the May 21 City Plan Commission clerk tally sheets, audio recording, and amended agenda — the vote data shows this corridor rezoning carrying 14-0 under both Item 9 (explicitly noted as tabled and re-heard after the Subdivision Docket) and Item 15 at the same meeting, meaning the commission either voted twice on substantive questions during a single session or one entry is a procedural motion mislabeled as a carried recommendation, and the distinction determines whether the official record forwarded to City Council is procedurally sound.

Act before: After records request response (typically 10 business days)

Why now: Z-26-000015 received its 14-0 City Plan Commission recommendation on May 21, 2026 — over four weeks ago — and no council hearing date has been established as of June 18, 2026, despite the matter having cleared three separate commission appearances.

What to do: Contact the council district office covering this corridor this week and ask specifically when Z-26-000015 will appear on the zoning or consent agenda — with two consecutive unanimous City Plan Commission recommendations and no opposition on record, this should qualify for consent docket placement, but cases with no active sponsor at City Hall routinely sit unscheduled for months after a favorable commission vote, and delay past the next budget cycle could push this into a new council term.

Act before: After item appears on City Council agenda

Applies if: You own or have a purchase contract on a parcel along the Ferguson Road corridor

Why now: Z-25-000164 is corridor-scoped, and the exhibit map — not the street name — controls which parcels legally convert from R-7.5(A) single-family to TH-3(A) townhouse upon ordinance adoption.

What to do: Pull the Z-25-000164 case exhibit map from Dallas Development Services to confirm whether your parcel falls within the corridor scope before finalizing a site plan — corridor boundaries can exclude adjacent addresses that share the same street. If your parcel is inside, three consecutive unanimous CPC carries (13-0, 12-0, 14-0) since March 26 mean the TH-3(A) townhouse entitlement is politically settled and you can advance engineering without waiting for final adoption.

Act before: After ordinance effective date

Why now: Z-25-000164 has been carried unanimously three consecutive times (13-0, 12-0, 14-0) over 10 weeks with no final vote, and the May 7 docket shows a carry in the vote data but no outcome in the public timeline — a direct contradiction that may indicate undisclosed conditions.

What to do: File a records request for the verbatim May 7 CPC minutes and audio recording, specifically asking what occurred during the 14-minute recess (2:14–2:28 p.m.) on Item 16 — the vote data shows a 14-0 carry, yet the public timeline records no result for that date, and a mid-hearing recess on a case already carried unanimously twice before typically signals a last-minute condition negotiation that has not surfaced in the public record.

Act before: After records request response (typically 10 business days)

Why now: Case Z-26-000050 has appeared three times before the Commission (May 7 and two entries on June 11) with no recorded final outcome, despite all five corridor cases being scheduled to return for action on the same 84-item June 11 docket.

What to do: File a public records request for the June 11 City Plan Commission action minutes and compare outcomes across all five under-advisement corridor cases (#17–#21) — if any were continued a third time after being listed as returning for Commission action, serial deferral across the entire corridor docket is a story the agenda alone does not tell. The May 7 record separately logs Commissioner Rubin as out of the room but counted in the 14-0 vote, a procedural anomaly worth documenting before the case closes.

Act before: After records request response (typically 10 business days)

Why now: The pre-June 11 briefing window has closed without a recorded final vote, and the case now shows three appearances (May 7 and two June 11 entries) still unresolved, making a new hearing likely and a new access window imminent.

What to do: Contact City Plan Commission staff today to confirm whether this case was continued at June 11 and obtain the next scheduled hearing date — then reach individual commissioners before that session, while their positions on the corridor zoning question are still open rather than set by a prior floor discussion. Waiting until the agenda posts will compress your access window the same way the 84-item June 11 docket did.

Act before: After final Commission vote on this case

Why now: Z-25-000229 appears twice on the June 11 agenda after being pulled from the consent docket by a 14-0 procedural vote on May 7 — three appearances without final adoption is atypical, and the double June 11 entry is anomalous for a single zoning case.

What to do: Request the verbatim minutes for both June 11 City Plan Commission entries on this case and compare any condition language between them — a mid-session condition change on a case already under advisement, without a separately noticed public hearing, is a procedural defect that could support a challenge after adoption. The statutory challenge clock runs from final adoption, but the defect must be documented now while the record is fresh.

Act before: After statutory challenge period expires

Why now: Z-25-000229 has appeared on May 7 and twice on June 11 without final adoption, meaning conditions have been actively renegotiated across at least two under-advisement periods with no public posting of the current draft.

What to do: Contact the assigned City Plan Commission planner directly to request the working conditions package — with the case deferred across three hearings since May 7 and still no adoption after June 11, negotiated conditions may differ substantially from the original filing, and the next hearing date has not been publicly posted. Waiting for the staff report to appear publicly means reading conditions the same day as the vote with no time to respond.

Act before: After final ordinance adoption

Why now: The June 11 City Plan Commission agenda carries 40 zoning cases with 30 staff-recommended approvals, yet all 10 non-routine entries are continuations of exactly five corridor cases — an unusual concentration that does not occur by chance on a routine docket.

What to do: File a public records request for the applicant names, attorneys of record, and ownership entities behind all five under-advisement corridor zoning cases listed as items #17–#21 on the June 11 agenda — having all 10 non-routine entries on an 84-item docket be continuations of exactly five related corridor cases is a pattern the vote record alone will not explain, and if a common party or attorney is managing multiple corridor parcels simultaneously that is the story. Once any of the five cases reaches final adoption, the deliberation history becomes significantly harder to reconstruct.

Act before: After records request response (typically 10 business days)

Why now: The case has been deferred across three hearings since May 7 with no publicly scheduled return, and the June 11 docket carried 84 substantive items, meaning this corridor case received compressed floor time with no pre-hearing alignment opportunity.

What to do: Contact the City Plan Commission administrator this week to find out when Z-25-000229 will next appear — the return date has not been publicly posted, and once it is, the window for direct commissioner outreach before the hearing compresses to days. The June 11 hearing produced no final vote for the third time, so the next hearing is the definitive window to shape conditions before adoption locks them in.

Act before: After next hearing date is publicly posted

Why now: Four zoning cases were scheduled to return from under advisement at the May 21 meeting, but Z-26-000034 was specifically noted as 'Heard individually from consent docket' despite passing 14-0, suggesting a condition, recusal, or stakeholder concern unique to this case that is not captured in the vote record.

What to do: Cross-reference the May 21 City Plan Commission agenda to determine whether the other three zoning cases returning from under advisement passed on consent or were also pulled individually — if this corridor case was uniquely separated while the others cleared consent, pull the meeting video to identify who raised the floor issue and why it does not appear in any written summary.

Act before: After records request response (typically 10 business days)