Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Ethics Code topic
No spam. Unsubscribe anytime.
City Methods Committee debates ethics code language on conflicts, recusal, budgets and gifts
Summary
At its March 31 meeting the city Methods Committee continued work on a draft ethics code, debating how to define 'conflict of interest', whether to treat 'company' as 'entity', how recusal and disclosure should operate, and whether gift rules would unintentionally bar routine donations; members assigned follow‑up drafting tasks.
Get email alerts on the Ethics Code topic
No spam. Unsubscribe anytime.
The City Methods Committee met March 31 to continue drafting an ethics code that would govern city public servants. Members debated key definitions, recusal procedures and the scope of prohibitions on gifts and financial interests, and agreed on several follow‑up drafting tasks.
The meeting opened with a brief personal dedication from a committee member (Committee member (S1)), then moved into substantive review. Chair (Chair (S3)) guided the discussion as members worked through draft language on confidential information and definitions. Committee members debated whether the draft should use the word 'entity' instead of 'company' to ensure the code covers nonprofits, volunteer groups and other non‑business organizations; the draft was updated accordingly, Corp counsel (Corp counsel (S4)) said.
Discussion centered on a proposed overarching principle that public servants have a duty to avoid conflicts of interest and on whether the code should be interpreted 'liberally' or 'narrowly.' Corp counsel (Corp counsel (S4)) explained the difference between liberal and narrow construction of legal language; several members favored a short, clear policy paragraph followed by non‑exhaustive examples. As Chair (Chair (S3)) put it, the code should provide both a binding statement of principle and illustrative examples rather than an exhaustive catalogue.
Members tasked Jenny (referenced in the meeting) with drafting a plain‑language definition of 'conflict of interest' for placement in the definitions section so the committee can review and refine it outside the meeting. Chair (Chair (S3)) and others asked staff to track marginal comments and remove items marked 'resolved' from future drafts.
The committee also debated how the code should treat budget votes. Draft language discussed a carve‑out—commonly used in municipal codes—that would permit councilors to participate in and vote on the municipal budget as a whole while recusing from deliberation or votes on specific line items where they have a direct conflict. Corp counsel (Corp counsel (S4)) said staff would prepare a version aligned with existing city council language and broaden it where needed for other public servants.
On gifts, Corp counsel (Corp counsel (S4)) warned that an unqualified ban on accepting gifts from any person or entity that holds a city contract, license or permit could have unintended consequences, such as barring a local business from providing pizza to a fire station after an emergency. "The public servant shall not accept any gifts from a person or entity who has a contract, license or permit with the city," Corp counsel (Corp counsel (S4)) noted in describing the draft, but added the committee must decide whether to narrow or clarify that language to avoid prohibiting commonplace, benign acts.
Other procedural items included approving the prior meeting minutes as amended and confirming that there were no public commenters present that night. The committee recorded action items (including the drafting assignments noted above), planned to incorporate relevant city council code language on budgets, and agreed to continue work at the next meeting. Chair (Chair (S3)) closed the discussion after a motion, second and hand vote to adjourn.
The committee also voted to enter an executive session earlier in the meeting to consider a citizen submission; corp counsel recommended citing "1 MRS section 405 subsection 6(e)" as the legal basis to discuss privacy‑sensitive material. The executive session motion passed with no opposition or abstention reported.
Next steps: staff will produce the recusal and conflict‑of‑interest definition drafts (Jenny to draft conflict definition; Rachel and staff to incorporate council language on budget carve‑outs), circulate redlines, and bring revised language back to the committee for further review.
