Community Finance Committee debates role, charter review and subteams to tackle projections and EBF work

Members of the Oak Park–River Forest School District 200 Community Finance Committee discussed the committee's future charge, the scope of work it may originate, how the committee should organize subteams, and open‑meeting (OMA) and quorum implications of committee membership.

Graham opened the discussion by asking that the committee move from an administration‑driven “dog and pony” approach toward initiating projects that draw on the committee's expertise and a changed district financial landscape. He and other members noted that District 200 is, for the first time in about 20 years, operating with a normalized fund balance target (25–33% of operating revenues), that Project 2 construction will conclude next summer, and that Project 3 and major collective‑bargaining negotiations loom in 2026 — factors that justify a more proactive committee role.

Committee members discussed practical ways to operate. The group endorsed two‑person subteams to “divide and conquer” work: Michelle and Bob are already working on an EDF/EBF (evidence‑based funding) sanity check and metrics that link finance to academic outcomes; a projections subteam was proposed to analyze five‑year projections, identify variable drivers (teacher contracts and enrollment were highlighted), and model low‑point fund balance/cash‑flow timing. Tony (administration) and Graham recommended routing requests for district data through the district’s staff (Tony) so that administration can allocate resources and set timelines.

Members raised governance and OMA concerns. The committee's charter, as read aloud by participants, defines membership as five community members, two board members and two administrators (nine positions). Several members noted ambiguity about which members count as voting members for quorum and how non‑voting liaisons factor into the majority‑of‑quorum OMA rule; committee members repeatedly cautioned about conducting substantive discussions in email threads and advised no substantive replies when members receive informational emails. The group agreed that the charter should be reviewed and clarified to resolve: (1) whether board members and administrators are voting members for quorum calculations, (2) the role and authority of co‑chairs, and (3) allowable subteam membership rules so subteams do not create a de facto quorum.

Graham volunteered to read the charter and circulate initial recommended changes; he said he would deliver proposed comments to the committee ahead of the next meeting. Several members volunteered to form or serve on subteams; the committee agreed it is acceptable for subteams to work between meetings, provided they funnel requests for data through Tony and avoid conducting policy decisions that would require board authority. Participants also discussed practical meeting procedures: agenda‑setting would likely follow a small pre‑meeting with two board leaders (president and vice president in the past) who then translate topics into the district’s board platform (Diligent) for packet publication. Members asked that committee packets include clear “asks” and visuals (timelines) to allow reviewers to prepare substantive feedback in advance.

Why it matters: committee members framed this work as setting longer‑term fiscal strategy and creating institutional memory so the committee can sustain financial oversight across administrative and board turnover. The group scheduled charter review and refinement of the projected subteam scope for the next meeting. No formal vote was recorded.