Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Meeting Technology topic
No spam. Unsubscribe anytime.
City commission tests new web-based meeting software; members flag vote visibility and login issues
Summary
City commission staff and members ran a hands-on test of a new web-based meeting-management system that controls speaker timing, voting displays and minutes. Participants praised some features but reported login delays, synchronization problems when multiple users are signed in, and concerns about how individual votes are shown on-screen.
Commission staff and members ran a hands-on test of a new web-based meeting-management application during a practice session, focusing on speaker timers, vote tally displays, and administrator controls. The session included demonstrations of adding placeholder speakers, a “mark all yes” setting for votes, and toggles that show or hide individual voters on meeting screens.
The exercise highlighted several operational concerns that officials said could affect live meetings. Vicky, a staff member, demonstrated the ability to add a placeholder (for example, “speaker 1”) and then replace the placeholder with the speaker’s full name in the minutes after the meeting. Staff also showed that speaker times are entered from preset increments and that moderators can add 30-second increments while a speaker is live to extend a turn.
Participants raised privacy and influence concerns about the voting display. On the test system, a view exists that shows individual voting choices in real time; staff said that view can be turned off so members are not influenced by each other. Several participants said the mayor typically relies on a screen that shows who has or has not yet voted. Mike, the mayor, was described in the session as preferring that visibility; staff said the setting can be restricted so individual votes do not display on the public screen unless an authorized device or view is used.
Attendees also encountered technical problems. Multiple participants reported lag and difficulty when more than one person was signed into the web app simultaneously. One staff member said the web-based application “is really not designed to have two people in here,” and described synchronization delays between different administrators’ views. Password changes and logins were another problem: speakers reported a delay when updating a user password and said it could take as long as about 30 minutes to propagate in the system.
Staff walked through practical workarounds and operational settings. Vicky demonstrated a “mark all yes” convenience that an administrator can use, with the option to change individual votes afterward; she also explained how to add a speaker to the queue so the minutes will include a note that a speaker was called. Steven, a staff member, and other participants recommended checking network connections before official meetings — a repeated suggestion after several speakers experienced slow or failed logins during the test.
The practice session included routine agenda business as part of the rehearsal: the group moved and adopted the agenda, processed consent items, and concluded with a motion to adjourn. The transcript did not record formal vote tallies tied to individual names.
Officials said they will continue to test the system and recommended additional practice before using it in an official meeting to reduce the chance of delays or confusion. Staff also discussed administrator permissions and the option to assign a single device with chair privileges to preserve the mayor’s usual workflow while restricting vote visibility on the public screen.
