Citizen Portal
Sign In

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

Get email alerts on the Committee Rules topic

No spam. Unsubscribe anytime.

Governance Committee discusses standardizing committee rules, seeks more time to finalize resolution

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

The Governance Committee discussed a draft resolution to standardize committee rules on April 7 but did not adopt final rules; members asked for more detail and for a follow-up work session before returning a formal resolution.

The Governance Committee held a substantive discussion on April 7 about proposed committee rules and procedures intended to standardize practices across council committees, but members did not adopt rules and asked staff to return with a more formal resolution.

Committee members and staff reviewed an attachment posted with the agenda that covered meeting notice, quorum, agenda filing, public testimony, recording and minutes, motions and amendments, documents accompanying items, suspension of rules and conflict of interest. The item was a discussion only; the committee did not vote on final rules.

Members and commenters pressed several recurring themes:

- Notice and agenda timing: Committee members debated aligning committee posting language with existing Portland City Code language that requires at least 24 hours’ posting, but several members and public commenters urged longer public notice (for example one-week advance notice or two business days) so members of the public and community groups have time to prepare testimony. Councilor Pertelgini said the city has two levers—the referral list and the agenda posting—that could be used together to increase public notice.

- Minutes and recordings: Staff recommended aligning committee minutes language with full-council practice and ORS (Oregon Revised Statutes) requirements, allowing either a recording or written minutes. Committee members supported adding the option of written minutes to accommodate offsite hearings with limited technology.

- Impact statements vs impact analyses: Council offices and staff sought clarity on which office prepares impact statements that accompany agenda items and which offices provide formal impact analyses (for example budget or economic analyses). Several committee members said analyses should come from administrative (executive) staff or the city budget office to maintain impartiality; council operations said it should be possible for legislative staff to contribute to draft statements when offices prepare items.

- Scheduling and committee access: Public testimony urged clear procedures for how items are scheduled, what happens if a chair does not schedule an item, and whether an item could languish without a hearing. Terry Harris, a frequent public commenter, urged clearer rules and suggested the committee consider a Committee of the Whole option for large, multi-day hearings.

- Substantive amendments and rule suspension: Committee operations staff noted it’s important to define what counts as a substantive amendment and when committee rules can be suspended; members asked staff to provide clearer limits in draft language.

Multiple councilors recommended a programmatic follow-up: hold a work session (all members, nondecision forum) to workshop the draft rules and then return to governance committee with a formal resolution for adoption. Councilor Ryan and others emphasized the need for clarity on testimony handling and predictable notice so community groups and advisory bodies can fully participate.

No formal votes were taken on the rules during the meeting; staff and council operations will revise the draft based on committee feedback and public testimony and return with a resolution for future consideration.

Speakers quoted or referenced in this article are identified by name and role where provided in the meeting record.