Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Ordinance Format Engineer Ai topic
No spam. Unsubscribe anytime.
Port Edwards committee debates 'village engineer' language and use of AI to reformat ordinances
Summary
Trustees discussed replacing 'village engineer' language in public-works ordinances with a director/engineer hybrid and considered using an AI tool (Claude) to reformat ordinances, add revision notes and produce side-by-side comparisons for committee review.
Committee members used the May 27 meeting to review proposed ordinance revisions and to debate where and when the term "village engineer" should remain in the public-works chapter given the village does not maintain a staff engineer.
Members proposed several options: retain 'village engineer' in provisions that clearly require professional engineering approval and route those matters to external engineering firms; or replace 'village engineer' with a combined title such as "director of public works/engineer" so that the administrator can determine when to use outside certified engineers. One trustee summarized the practical approach: roadway and subdivision design would continue to be handled by outside engineering firms, while the administrator or director of public works could handle lesser technical approvals internally.
The committee also discussed formatting and version control for the ordinances. A committee member demonstrated an AI-assisted workflow (identified in the meeting as Claude) that had been used to extract statutory references, produce revision notes and rewrite ordinance chapters into a consistent format. The member said the AI tool can produce a side-by-side redline and suggested the village could maintain a subscription (noted in meeting discussion as roughly $20–$24 per month) to support continued ordinance maintenance. "It took all the Wisconsin state statutes from 2 and 8 that are mentioned anywhere in 2 and 8," the committee member said, describing the tool’s ability to compile references.
Members agreed that any sustained AI use should be routed through FHR/IT and that funding for a subscription would need board-level approval; they also agreed that certain verbiage changes and any substantive legal edits should be cleared by counsel. Because some trustees did not receive the Chapter 8 draft before the meeting, the committee deferred final text approval and asked staff to distribute the document to all trustees for further review.
Outcome and next steps: Committee members decided to circulate the Chapter 8 draft more widely, mark sections where professional engineering approval is required, and return the chapter for discussion at the next meeting. Any format-change motion or deployment of paid AI tools will require further review and likely a separate recommendation to the full board.
