Citizen Portal

Get email alerts on the Development Policy topic

No spam. Unsubscribe anytime.

Council adopts development‑agreement policy into code to clarify expectations for developer benefits

Perry City Council · August 27, 2026

Summary

Perry City Council adopted Ordinance 26 D to add nonbinding development‑agreement policies and priorities into the municipal code and require an early informal review for development‑agreement proposals. The policy aims to balance developer benefits with community benefits and prioritize parks, orchards and quality design.

The council voted unanimously to adopt Ordinance 26 D, which inserts planning commission’s recommended development‑agreement policy and priorities into city code as nonbinding guidance. Bob Barnhill explained the change: "It's the policy of Perry City that such developer benefits be counterbalanced with relatively equal community and city benefits." The new code also requires applicants to submit a statement describing how a proposal meets code and the adopted priorities and creates an early, informal review by a designated planning commissioner, a designated council member, the community development director and the city engineer before a development agreement reaches the Planning Commission agenda.

Council members generally supported the policy as a way to give applicants clearer expectations without creating rigid new rules. The policy emphasizes measurable community benefits (detailed park plans, orchard preservation, architecture quality) and reiterates that standard code development remains a primary path; development agreements should demonstrate improvements over code. The council expressed interest in ensuring the pre‑application review is rapid and not unduly bureaucratic.

AI generated

The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.

AI can make mistakes, so if you spot one, and we will fix it for everyone.

Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.

Source