Make code changes easier to review.

Comment on the section, not the whole document

A code amendment is a set of specific changes. Page-level comments let a reviewer say exactly which provision they are responding to.

• Comments attached to a page and a version
• Comment period with an open and close date
• Categories for the issues the amendment covers

Education content next to the question

Most objections to a code change come from a misreading of what it does. Put the plain-language explanation beside the draft text and the comments get sharper.

• Summary documents published with the draft
• Explanatory maps for districts and standards
• Questions and answers for the amendment

Issue-specific surveys

Instead of one open comment period, run a short survey per issue. The results are countable, and staff can see which provisions drew the most response.

• One survey per topic
• Single choice, ranking, and scale questions
• Results by issue as soon as the survey closes

Maps for districts and standards

Zoning is spatial even when the document is not. Show the affected areas on a map and collect comments where they belong.

• Map comments on affected parcels and districts
• Before-and-after map exhibits
• Mapped comments exported for the record

Updates as the amendment moves

Code updates move through several hearings. Publish each revision in the same project space so people can follow the version they commented on.

• Dated project updates
• Each document version kept with its comments
• One project link for the life of the amendment