VI.N. Community Improvement Program

From BSC Policy
Jump to navigationJump to search

VI.N.1. COMMUNITY IMPROVEMENT PROGRAM PURPOSE

The purpose of the Community Improvement Program is to foster member engagement with the Board and standing committees and with the city, student, and cooperative community-at-large.

VI.N.2. COMMUNITY IMPROVEMENT PROGRAM REQUIREMENTS

1. Participation in Community Improvement (CI) Events is optional. Members are encouraged, but not required, to engage in community, cooperative, or civic activities that support leadership development and cooperative engagement.
2. At the beginning of the Fall and Spring Contract periods, the VPEA and EACom may update the list of voluntary Community Engagement Opportunities by soliciting ideas from the Recruitment Team, DARCom, Board Directors, and House Presidents.
Board Directors and House Presidents may inform members of the optional engagement opportunities and share the Community Engagement Opportunities document.
3. The following activities qualify as optional community engagement opportunities:
(a) Activities organized by the Recruitment Team
(b) Activities organized by DARCom
(c) Attendance at Board or Board committee meetings
(d) Any activity listed on the Community Engagement Opportunities document or approved by EACom.

VI.N.3. COMMUNITY IMPROVEMENT PROGRAM PROJECTS

At the unit level, Board Directors will answer more specific questions regarding the Community Improvement Policy. Should members wish to propose a unit-level Community Improvement project, their Board Director should coordinate with the VP of External Affairs or Summer Vice President. The VPEA or SVP can assess whether a proposed project qualifies to meet the Community Improvement Policy guidelines.

VI.N.4. COMMUNITY IMPROVEMENT PROGRAM OVERSIGHT

Unit level Presidents and Board Directors will track members’ fulfillment of CI Commitment and report to the VPEA. EACom will submit fines to accounting.


[Updated Section VI.N.2 as per approval at Board #5 (12.04.2025)]

[Updated as per approval at SumCom #4 (07.10.2024)]

// Original policy approved by Board 05/07/20 //