Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Local Governance topic

No spam. Unsubscribe anytime.

Oak Park trustees debate updates to board protocols on calendars, alerts and motions

Village Board of Oak Park · January 20, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Deputy Village Manager Lisa Shelley led a line‑by‑line review of revised board protocols covering annual calendar posting, agenda-publication timing, email aliases, time estimates for agenda items, emergency trustee notifications, and rules about motions and waiving a return meeting; trustees directed staff to clarify language and return the protocols on the consent agenda after edits.

Deputy Village Manager Lisa Shelley summarized proposed updates to the Village Board’s protocols and walked trustees through questions staff received in advance. The board discussed multiple operational changes designed to improve transparency and internal workflow.

On calendars and agendas, trustees asked that the annual meeting calendar be posted where both the public and trustees can easily find it (Legistar offers only a three‑month view). Shelley said communications could post the adopted annual calendar on the board web page and staff will include a reminder of the full calendar in future agenda packages. Trustees asked for a simple listing of dates and times alongside the pictograph annual calendar.

Trustees discussed a protocol that allows a short preview period before public posting (comments by noon on Thursday with a preview appearing earlier) so trustees can catch obvious errors in timing; staff said the rule was intended to avoid public confusion and that legal constraints (items must be locked 48 hours before a meeting) will be respected. Several trustees asked staff to add a short disclaimer to public previews that the agenda order remains subject to change.

On communications, trustees supported creating a VMO staff email alias (one address that reaches manager’s‑office staff) and asked staff to clarify board vs clerk email usage. Trustees also asked IT to explore automatic routing rules (hub transport) so a single outgoing message could BCC board members or otherwise include staff without creating public confusion.

Trustees asked staff to include estimated presentation and Q&A times for agenda items (visible to trustees while not necessarily displayed to the public) and debated whether to start meetings earlier when more than two substantive items are scheduled; staff said timing estimates are a best effort and that executive sessions and member schedules complicate a hard start-time rule.

Trustees also sought clearer guidance on when staff will phone trustees for urgent incidents versus simply issuing email alerts. Staff said VM alerts will continue and that for significant incidents (deadly crash, large fire) trustees will receive phone calls and a unified staff statement; trustees said alert messages should include what happened, what staff is doing, and whether trustees should appear publicly.

On motions, the board discussed a rule requiring funding requests or new actions to return for a final vote at a subsequent meeting. Trustees favored keeping the two‑meeting review as the default but agreed the board should be able to waive the return requirement in urgent situations; staff will add explicit waiver language and bring the protocols back on the consent agenda with those edits.

Shelley said staff will revise the protocols to reflect trustee feedback and return them on the consent agenda. The board had multiple operational follow-ups — calendar posting, email alias creation, and language clarifications — all of which staff will incorporate before the item returns for formal adoption.