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

Context: City Council deferred the planned development on August 25, 2026, after the City Plan Commission had carried it 10-3 on May 21, with both recommendations conditioned on a conceptual plan and conditions; the matter has appeared twice.

Recommended: Pull the August 25 City Council hearing record, including the deferral motion and any stated concerns, and compare it with the conceptual plan and conditions recommended by staff and the City Plan Commission. Determine whether the next submission needs revisions or additional findings before Council acts, rather than assuming the prior recommendations resolve the outstanding issue.

Context: On August 25, 2026, City Council deferred the Walnut Hill Lane planned development despite staff and City Plan Commission recommendations for approval subject to a conceptual plan and conditions; the matter has appeared twice.

Recommended: Obtain the conceptual plan and staff-recommended conditions, then test the proposed R-5(A) single-family layout against each condition before revising design or pricing. The City Plan Commission and staff support was expressly conditional, so an unverified plan change could jeopardize the approval when City Council returns to the deferred hearing.

Context: The City Plan Commission carried the application 10-3, with Hampton, Kocks, and Coffman opposed and Kingston out for a declared conflict, before City Council deferred it on August 25, 2026; the matter has appeared twice.

Recommended: Request the August 25 Council hearing materials and the City Plan Commission discussion record to establish why Council deferred a staff- and commission-supported single-family rezoning. Ask whether organized neighborhood opposition, the 10-3 split, or Commissioner Kingston’s declared conflict affected the unresolved concerns.

Context: The 'approved as amended' vote on December 10, 2025 creates binding conditions that may include triggers or deadlines not present in the applicant's original submission.

Recommended: Compare the adopted amended ordinance to the original application to surface any time-limited conditions — such as a specific use permit expiration window or required development agreement — that now bind the property owner.

Context: City Council approved this zoning case 'as amended' on December 10, 2025, meaning the recorded ordinance is the controlling document, not the applicant's original filing.

Recommended: Pull the adopted ordinance as amended to confirm the exact permitted uses, setbacks, and any attached conditions — the final entitlement may differ materially from the original application submitted.

Context: The December 10 Council session processed 18 zoning cases in a single meeting and required corrections to seven items before final action, raising questions about pre-vote review depth for individual cases.

Recommended: File a public records request for the original application, any staff-drafted amendments, and the final adopted ordinance to determine what was changed between application and approval and who requested the amendment.

Context: Case Z-26-000015 was adopted "As Amended" by City Council on 2026-06-24, diverging from the Plan Commission's unanimous 14-0 recommendation on 2026-05-21.

Recommended: Pull the adopted ordinance and compare its conditions to the Plan Commission's May 21 recommendation — Council approved the case "As Amended" rather than adopting the Commission's unanimous vote outright, so confirm whether the change required additional public notice or triggered a protest-petition supermajority requirement.

Context: Case Z-26-000015 was approved "As Amended" by City Council on 2026-06-24, after the Plan Commission recommended it 14-0 on 2026-05-21.

Recommended: Get the certified copy of the ordinance as adopted before drawing site plans or filing permits — because Council amended the case rather than adopting the Plan Commission's May 21 version, the approved setbacks, retail mix, or use limits for the manufactured home and community retail development may differ from what was in the application file.

Context: Case Z-26-000015 was tabled at the 2026-05-07 Plan Commission meeting, carried 14-0 on 2026-05-21, then was approved "As Amended" by Council on 2026-06-24 with no public record of what the amendment changed.

Recommended: Request the staff memo or redline showing what changed between the Plan Commission's unanimous recommendation and Council's final vote, and ask planning staff to explain the May 7 tabling — the case took an unusual three-step path before Council altered it at adoption.

Context: Case Z-26-000015, a Planned Development for manufactured home and community retail uses on Haymarket Road, was approved "As Amended" by City Council on 2026-06-24.

Recommended: Review the approved site plan for screening, setback, and retail-hours conditions — a manufactured home community and community retail development is now entitled for the Haymarket Road property, and those conditions determine how close construction and commercial traffic will sit to existing houses.

Context: City Council's August 12 approval expressly included a resolution accepting deed restrictions volunteered by the applicant, but the supplied record provides no restriction terms or implementation milestone.

Recommended: Request the adopted ordinance, Council resolution, and executed deed restrictions, then identify the exact use and property obligations they impose before permits or property transactions proceed. Without those documents, the record does not establish the enforceable restriction language.

Context: On August 12, City Council approved Community Retail District zoning and accepted deed restrictions for the Chalk Hill Road property after City Plan Commission approval.

Recommended: Obtain the accepted deed restrictions and test the proposed retail program, access, and site layout against their actual terms before commissioning final plans. Council approved the community retail zoning subject to applicant-volunteered restrictions, whose contents are not supplied here.

Context: The matter appeared on May 7 and May 21 before City Plan Commission, where it carried 14-0, and then was approved by City Council on August 12 with deed restrictions.

Recommended: Request the May 7 City Plan Commission materials, the May 21 motion record, and the final deed restrictions to determine what changed during the three appearances and what limits were added before Council approval. The public record shows a two-week Commission interval followed by a later Council decision, but not the substance behind that progression.

Context: Item 6 shows the Plan Commission's original motion was amended 13-0 on April 23 to readvertise as a planned development, then required a second 14-0 vote on May 21 before Council adopted it June 24.

Recommended: The case was amended mid-hearing to readvertise as a planned development instead of straight zoning, which triggers a fresh notice requirement to nearby property owners — confirm renotification was completed correctly, since a defect here could still expose the adopted ordinance to a validity challenge despite the unanimous votes.

Context: On April 23 the Plan Commission amended the original motion 13-0 to readvertise the case as a planned development instead of straight zoning (Item 6).

Recommended: This case was switched mid-hearing from a straight zoning change to a planned development, so the entitlement now carries site-specific conditions instead of standard district rules — pull the final ordinance and site plan before assuming any use is allowed by right.

Context: The Plan Commission amended its own motion 13-0 on April 23 to readvertise as a planned development, forcing a second hearing and 14-0 vote on May 21 before Council approved it June 24.

Recommended: Request the staff report or commission minutes explaining why the April 23 motion was amended to readvertise this case as a planned development rather than approving it as originally filed — a mid-hearing pivot like this usually means the commission couldn't resolve a concern within the original district's rules.