Programming, Events & Community Engagement

The umbrella policy this whole phase implements Bylaws Article 25 through, and the document every other document in this phase ultimately answers to. No Council-sponsored activity — a small workday gathering, a listening session, a full festival day — proceeds without working through this policy's approval chain, in order:

1. Internal concept approval. The Event Lead completes an Event Concept / Internal Approval Brief (8-02); the Board or Programs Committee approves it as a concept before anything is submitted to CPD.
2. CPD approval, using the correct process for the activity's scale. Routine PAC activity uses the Activity Request process from CPD's own PAC Guidelines appendix (8-03); larger or public-facing events use CPD's Special Event Permit Application (8-05). This step is never skipped and never scaled down for a small event — a small gathering still needs Park Supervisor/Area Manager sign-off, just via the lighter-weight of the two real CPD processes.
3. Permit determination. The Permit Determination Checklist (8-06) is run for every event to catch amplified-sound, food, tent, vending, sponsorship, and alcohol triggers before they're discovered the week of the event.
4. Insurance, where required. A Certificate of Insurance (8-08) is obtained before the event, not requested retroactively.
5. Budget. Every event has a line in the annual budget or an approved out-of-cycle expenditure per the Delegation of Authority Matrix (Phase 2, 2-36) — no event proceeds on an assumption that money will be found afterward.
6. Safety and accessibility planning scaled to the event (8-10 through 8-13) — a listening session needs less than a festival day, but every event needs something.
7. Vendor/partner compliance where applicable (8-14 through 8-19, 8-26 through 8-30).
8. Closeout. The Post-Event Report (8-44) is completed within two weeks, closing the event file and feeding the next planning cycle.

The Programs Committee owns this policy and reviews it annually alongside the Policy Sunset schedule (Phase 6, 6-36); any Council member proposing a new kind of activity not clearly covered by an existing step in this chain should bring it to the Programs Committee before proceeding, not interpret ambiguity in the Council's favor.

The internal go/no-go step before anything is submitted to CPD — the Board or Programs Committee approves the concept here first, so CPD sees a coherent, already-vetted request rather than a work-in-progress idea being thought through in real time on a call with the Park Supervisor. The Event Lead completes this brief and brings it to the next regular Board meeting or, for time-sensitive opportunities, to the Executive Committee (Phase 2, Article 15) for provisional approval subject to full Board ratification. Approval at this stage is not a rubber stamp: the Board should be able to say no, or ask for a smaller/different version of the idea, before the Council's name is attached to a CPD submission. Once approved, the brief becomes the source document for the CPD Activity Request or Special Event Permit Application (8-03/8-05) and the Event Operations Plan (8-09) — later documents should not silently drift from what was actually approved here without the Board being told.

The written or email confirmation of CPD's approval, retained in that event's file. If approval hasn't been received in writing, the event does not proceed — a verbal "should be fine" from a conversation with the Park Supervisor or Area Manager is not sufficient documentation, no matter how confident the Event Lead is that approval is coming. The record includes: the date the request was submitted, who at CPD responded and when, the exact scope approved (date, location, activity type, any conditions attached), and a copy of the underlying Activity Request or Special Event Permit Application it corresponds to. If CPD attaches conditions to its approval (a capacity limit, a time restriction, a requirement to use a specific entrance), those conditions are copied verbatim into the Event Operations Plan (8-09), not paraphrased from memory.

Filed in addition to, or instead of, the Activity Request whenever an event meets CPD's special-event permit criteria (scale, amplified sound, food service, tents, alcohol, or other triggers identified in the Permit Determination Checklist, 8-06). CPD's real current process (chicagoparkdistrict.com/permits-rentals-101) runs in stages: pay the Initial Permit Application Fee, submit the completed Special Event Permit Application along with a site plan, go through CPD's application review, receive a "pending permit" (conditional approval) status, and only then receive the final issued Special Event Permit — the Council should not represent an event as CPD-approved during the "pending" stage. The Activity Request Form (8-03) may still be required as the PAC applicant's own internal submission alongside this permit; the two are not mutually exclusive. Given the fee and the multi-step timeline, this process should start well before the event date — the Event Lead confirms current processing times with the Park Supervisor or Area Manager when scoping the event in 8-02, not after a date has already been publicized.

Run this checklist at the 8-02 concept stage, not after a date has been announced — several triggers (alcohol, food, tents) add real lead time to the CPD approval process, and discovering them late is a common cause of a rushed or missed application window. A "no" answer to every trigger doesn't skip CPD approval itself (8-03 is always required regardless); it only determines which additional permits stack on top of the base Activity Request or Special Event Permit Application. The Event Lead and CPD Liaison complete this jointly and attach the completed checklist to the event file alongside the Activity Request Approval Record (8-04).

Executed whenever an event uses the reservable Beach House or another CPD-managed event space, per CPD's own reservation process (see Phase 7, 7-36 for the Beach House stewardship context). This agreement is with CPD, not a Council-issued reservation of Council-controlled space. For the 63rd Street Beach House specifically, the real current process runs through a "Special Event Venue Application" submitted to CPD's "Special Event Manager" for that venue (a distinct point of contact from the general Park Supervisor), requires a Non-Refundable Reservation Down Payment plus a Refundable Security Deposit, and is only available June through September (excluding holiday weekends). Catering must come from CPD's "Preferred Professional List" unless an outside caterer is approved at least six months in advance; a minimum of two security officers is required; and General Liability insurance of $1M ($2M if alcohol is served) applies. Parking at the venue is limited, metered, and never guaranteed — plan attendee logistics accordingly.

Proof of coverage and any required endorsements (naming CPD as additionally insured, where required) for permitted activities and any participating vendors/partners — cross-checked against the Insurance Register (Phase 6, 6-35) and the broader Insurance Review Policy (Phase 5, 5-41). At minimum this file holds: the certificate itself, the policy period (confirmed to actually cover the event date), the named insured, any additional-insured endorsement naming the Chicago Park District, and, for the 63rd Street Beach House specifically, coverage meeting the venue's own real minimums ($1M general liability, $2M if alcohol is served, per 8-07). The Risk Lead confirms the certificate is on file at least two weeks before the event — not the day before — since a missing or deficient certificate is one of the more common reasons an otherwise-approved event gets pulled at the last minute.

Written for any event beyond the smallest gathering, this plan is the single document a volunteer showing up on event day should be able to read and understand their own role from, without needing to ask the Event Lead to explain it verbally. Site layout shows where the event footprint sits relative to the approved CPD boundary, where vendors/tables go, where the accessible route runs, and where emergency vehicles could access if needed. Run of show is a timed schedule from setup through breakdown, not just the public-facing program times. Staffing/volunteer roles names who is doing what — check-in, vendor liaison, cleanup lead, accessibility contact — with a named backup for each role, since volunteers sometimes don't show. Check-in covers how attendees (and, separately, volunteers) are welcomed and oriented. Vendor load-in/out gives vendors a specific window and route so they aren't improvising around attendees. Sanitation/waste cross-references 8-41's container plan. Communications names how the Event Lead reaches the team in real time (a group text thread, radios, or similar) and who the single point of contact is if something goes wrong. The plan is finalized at least one week before the event and walked through with all named role-holders, not distributed for the first time on event morning.

The plan stays live through the event cycle rather than freezing at first draft: if CPD attaches conditions after this plan is first written (8-04), or the actual event drifts from what the Board approved as a concept (8-02), the plan is updated to match and the change is flagged to every named role-holder — not left for someone to discover on-site. It also names, for each role, what that person does if their own backup also fails to show, since a plan that only accounts for the primary volunteer isn't really a contingency plan. Once the event closes, this plan and the Post-Event Report (8-44) are retained together as a matched pair; a future Event Lead planning a similar event should be able to pull both from the file and start from something real instead of a blank page.

Emergency contacts, weather thresholds, evacuation routes, medical/public-safety referral procedure, and a missing-person protocol (cross-referencing Phase 6, 6-31) for any event of meaningful size. This plan is drafted before the event, reviewed with on-site volunteers in a short briefing before doors open, and never improvised in the moment. It names: the nearest 911-appropriate access point for the site; who calls 911 or CPD security versus who simply flags down a lifeguard or Park District staff member for a lower-severity issue; where the on-site first-aid kit (if any) is kept and who's trained to use it; the evacuation route and rally point if the site needs to be cleared; and the specific script volunteers use if a child goes missing (immediately notify the Event Lead and the nearest lifeguard/CPD staff, do not conduct an independent search first). Throughout, Council volunteers observe and communicate — they do not direct lifeguards, perform rescues, or substitute for CPD security or first responders, consistent with the Swim/Rescue Non-Interference Policy (Phase 7, 7-28) and the Incident Reporting SOP (Phase 6, 6-30). Any incident that occurs is logged on the Event Incident Report (8-43) the same day, while details are fresh.

The pre-doors briefing is not optional for a "just this once" small crew — every volunteer with an assigned safety role hears the plan out loud from the Risk or Event Lead, and confirms out loud that they understand their own specific action, before the event opens. For any event held annually or repeatedly at the same scale, the plan is reviewed and updated before each recurrence rather than assumed unchanged — a lifeguard rotation, a new access restriction, or a change to the nearest first-aid resource can all go stale between events without anyone noticing until it matters. Where a pattern emerges across multiple events (the same near-miss, the same access-point confusion), it is raised with the Risk Management Policy's Risk Register (Phase 5, 5-42/5-43) rather than re-solved independently at each event as if it were new.

Names the decision threshold (current CPD/NWS conditions, same standard as Phase 7's Severe Weather Beach Activity Protocol), who has authority to call it, how participants/vendors are notified, and whether rescheduling or refunds apply. The President or Event Lead makes the go/no-go call by a stated deadline before the event (e.g., by 8am for a same-day event, or 24 hours ahead for a multi-day one), using the same authoritative sources as Phase 7 — never the Council's own informal weather judgment. Once called, cancellation notice goes out through every channel used to promote the event (email list, social media, signage at the site if there's time) simultaneously, not staggered. If a paid registration, sponsorship, or vendor fee is involved, this plan states in advance whether the event reschedules, refunds, or forfeits deposits — attendees and vendors should know the answer before they commit, not find out after a cancellation.

Not every weather call is a clean cancel/proceed binary. The plan also covers a delayed start (holding the go/no-go call to a second, later deadline if conditions are borderline rather than genuinely dangerous), a mid-event stoppage (who has authority to pause or end an event already underway, and how that's communicated to people currently on-site versus people at home deciding whether to come), and a partial-program adjustment (moving an outdoor component indoors or cutting a program short rather than cancelling the whole event). Whoever makes the call documents the specific conditions and the source checked at the time of the decision — not just "it looked bad" — since that record is what the Council relies on if a vendor or sponsor later disputes a refund decision. If the event reschedules, the same CPD approval chain (8-03/8-05) is re-confirmed for the new date rather than assumed to carry over automatically.

For events at a scale where crowd management actually matters (roughly, anything approaching or exceeding the capacity thresholds CPD sets for the space being used — see the Beach House capacities in 8-07 as one concrete reference point): a stated capacity limit tied to the site and any CPD permit condition; where lines form and how they're kept from blocking the accessible route (8-13) or an emergency lane; who monitors capacity in real time and what they do if the site approaches the limit (slow entry, stop entry, or in the most severe case, initiate a partial evacuation); and confirmation that emergency-access lanes identified in the Event Safety & Emergency Action Plan (8-10) stay physically clear throughout, not just at setup. Not needed for a small workday or listening session — created only when scale genuinely warrants it, and the Event Lead documents in 8-02 why a given event does or doesn't need one.

Where the event has hired or CPD-required security (per the alcohol-service or scale triggers in 8-06/8-39), this plan names how the capacity-monitoring volunteer and security coordinate — specifically, that a volunteer identifying a capacity or crowd-safety concern flags it to security or CPD staff rather than attempting to manage a crowd situation directly, consistent with the Council's general non-interference posture toward functions requiring trained personnel (Phase 7, 7-28). Signage and, where practical, a visible person at the entrance communicate current status to arriving attendees (open, near capacity, temporarily holding) so people aren't left guessing in a line. After the event, the Event Lead notes in the Post-Event Report (8-44) whether the plan matched reality — a queue that formed somewhere unplanned, or a capacity limit that turned out too conservative or too loose — so the next similar event starts from an updated plan rather than the same assumptions.

Built from the Accessibility Committee's standing Accessible Event / Stewardship Participation Checklist (Phase 7, 7-33) and the site's actual accessible beach walk and beach wheelchair program (Phase 7, Bylaws Article 23) — not drafted from scratch each time. The plan names a specific accommodation contact whose name and phone/email appear on every public promotion of the event, not just "contact us with questions," and states how far in advance an accommodation request should ideally be made (e.g., 72 hours) while making clear that a late request is still handled in good faith, not turned away for missing a deadline. For events at the Beach House or another reservable CPD facility, this plan cross-references whatever accessibility features that specific facility already provides rather than duplicating them.

The accommodation contact's job doesn't end at the request — they confirm the accommodation is actually in place on event day (the requested seating is where it was promised, the accessible route is clear of tables or cabling that crept into it during setup) rather than trusting that a plan on paper became reality without checking. Any accessibility gap noticed during or after the event, whether or not it was formally requested in advance, is captured in the Post-Event Report's accessibility notes (8-44) and fed to the Accessibility Review Report (Phase 10, 10-24) so a recurring gap gets fixed at the policy level instead of being individually apologized for at every event.

Vendors add real value to Council events and real risk if not screened consistently, so this policy sets the same bar every time rather than leaving it to whoever is organizing a given event. Selection criteria: mission fit (does this vendor's presence support the event's purpose, not just fill a table), reputation, and — for food vendors specifically — a completed Food Vendor Compliance File (8-17) before anything is confirmed. Required documentation: business license where applicable, permits specific to what they're selling, and a certificate of insurance meeting the same standard as 8-08, all collected before the vendor is confirmed, not the week of the event. Conduct: vendors represent themselves, not the Council or CPD, in all marketing and on-site signage; a vendor may not imply Council or CPD endorsement of their product. Sustainability: vendors are asked to use reusable or compostable materials where feasible, consistent with the Environmental Sustainability Policy (Phase 7, 7-38). Fees and sales limits (if the Council charges a vendor fee or table cost) are set by the Finance Committee, not negotiated ad hoc per vendor. None of this substitutes for the underlying CPD event approval (8-03/8-05) — a fully-compliant vendor roster does not make an otherwise-unapproved event permitted.

A vendor who has participated before is still run through the same current checklist (8-15) each time, not waved through on reputation — insurance expires, licenses lapse, and a vendor in good standing last season isn't automatically in good standing this one. If a vendor's conduct at an event violates this policy (unauthorized sales beyond what was approved, a lapsed permit discovered mid-event, disrespectful conduct toward attendees or other vendors), the Event Lead has standing authority to require the vendor to stop or leave immediately, with the incident documented on the Event Incident Report (8-43) and reviewed by the Programs Committee before the vendor is invited back. A vendor consistently causing problems is removed from future consideration — the policy exists to protect the event and the Council's name, not to guarantee every vendor a repeat invitation.

The Council's own agreement with an approved vendor — it governs the vendor's relationship with the Council only, and states expressly that it grants no rights to CPD property beyond whatever CPD has separately permitted/approved for that event. At minimum it covers: what the vendor is approved to sell/do, the date/time/location of participation, any fee owed to the Council and when it's due, the vendor's own insurance and permit obligations (cross-referencing 8-15 and, for food, 8-17), a clause confirming the vendor carries its own liability for its products/services, the independence disclaimer confirming neither party can bind CPD (Phase 5, 5-40), and what happens if the underlying event is cancelled per the Severe Weather/Cancellation Plan (8-11). Signed by the vendor and an authorized Council officer before the vendor is added to the event's vendor roster (8-15).

Health-department food permits, insurance, and CPD approvals collected before any food vendor participates — food service is one of the more heavily regulated vendor categories and is verified individually, not assumed to be covered by a general vendor agreement. This file holds: the vendor's current health department license/permit (verified not expired), proof of food-handler certification for on-site staff where required, general liability insurance meeting the event's standard, and confirmation the food-service trigger has been reflected in the Permit Determination Checklist (8-06) and, if the event needs it, the Special Event Permit Application (8-05). A food vendor without a current, verifiable license does not participate, regardless of how informal the event is — this is not a category where the Council extends professional courtesy in place of documentation.

For paid or otherwise formally committed talent: scope of performance, fee, schedule, content expectations, cancellation terms, media/recording permissions, and a standard clause confirming the performer understands the Council is independent of CPD and cannot bind CPD to anything. This document is separate from, and does not apply to, the informal beach drumming tradition (see 8-21).

Whatever CPD/permit documentation applies to amplified music or sound at an event, obtained before the event — cross-referenced with the Noise Management Plan (8-40) for the operational side of the same issue. CPD's real permit language names amplified sound explicitly as a permit trigger ("loudspeakers, amplifiers, powered megaphones"), so any event using a PA system, DJ equipment, or amplified live music runs through the Permit Determination Checklist (8-06) and, where required, the Special Event Permit Application (8-05) — a small unamplified acoustic gathering does not trigger this file. This file is not used to authorize or regulate the unamplified beach drumming tradition (8-21), which is neither Council-run nor Council-permitted.

The general framework 8-21 and 8-22 operate under. Four commitments guide every cultural program the Council touches: community-rooted, not imported — programming grows from what's already happening at 63rd Street Beach and what the community actually wants, not from a generic "cultural programming" template applied to any beach; accurate and respectful representation — traditions are presented the way the people who practice them describe their own tradition, not a simplified or exoticized version for broader appeal; community members shape their own presentation — the Cultural Programming Committee consults tradition-bearers before, not after, deciding how their practice will be described, promoted, or scheduled (documented per 8-22); and protect, don't displace — new Council-organized cultural programming is evaluated for whether it competes with, crowds out, or commercializes an existing community practice before it's approved, with the drumming tradition (8-21) as the clearest and most important example of a practice the Council must never treat as raw material for its own programming calendar. Any Council member proposing new cultural programming brings it to the Cultural Programming Committee for review against these four commitments before any public announcement.

These four commitments are deliberately written as things the Council does, not things it decides about someone else's tradition — the Committee's role toward an existing community practice like the drumming tradition is to ask what support is wanted and then either provide it or step back, never to evaluate whether the practice itself is worth supporting. For genuinely new programming the Council originates (a workshop series, a listening session with a musical element, a new event format), the Committee documents which of the four commitments applies and how in the Community Consultation Record (8-22) before scheduling anything, and revisits that record after the program runs to check whether the commitment was actually honored in practice, not just stated in the planning conversation.

What the Council commits to: showing up to listen before proposing anything that touches the drumming circle's time, space, or visibility; never scheduling a Council event that displaces or crowds out the tradition's usual time and space without direct agreement from the people who sustain it; supporting logistics the tradition-bearers actually want support with (a CPD Activity Request if they want the added visibility of formal recognition, amplification permitting if requested, promotion if wanted) and not imposing support that wasn't asked for; and never presenting the tradition in Council materials, fundraising appeals, or media as something the Council runs, curates, or owns.

This protocol is meant to be co-created, not co-opted — its actual final language should be shaped directly by conversations with the musicians and community members who carry the tradition forward, not drafted in their absence and presented as finished. Until those conversations happen, treat this as a statement of intent and a standing invitation, not a completed agreement.

If a CPD requirement — a permit condition, a safety rule, a scheduling conflict with another event — ever appears to bump up against what the tradition's own participants want, the Cultural Programming Committee's role is to carry that conflict to CPD on the tradition-bearers' behalf if they'd like that help, or to step back entirely and let them deal with CPD directly if that's what they'd rather do. The Council never uses a CPD requirement as its own justification to unilaterally change how, when, or where the gathering happens; if a change genuinely becomes necessary, that conversation happens with the people who sustain the tradition first, and any resulting decision is theirs to make, not the Council's to make for them. One Committee member serves as a standing point of contact so anyone connected to the tradition who wants to reach the Council doesn't have to start from scratch each time — but that role carries no authority over the tradition itself; it exists only to make contact easier, and the tradition-bearers decide whether and how much to use it.

A real record, not a formality — if consultation didn't actually change anything about the proposal, that's worth noticing before proceeding, not after.

Implements the Youth Protection Policy (Phase 5, 5-45) for a specific program, filled out fresh for every youth program rather than reused generically. Supervision ratios are set before the program starts and match the age group and activity type (a beach cleanup with teenagers needs a different ratio than a craft session with young children). Background-check status of every adult in a youth-facing role is verified against the Officer Background-Check Compliance Log (Phase 3, 3-09) or the Volunteer Training/Certification Log (Phase 6, 6-26) before the program starts, not assumed because the adult is a familiar face — no adult without current clearance is placed in an unsupervised role with youth, full stop. Consent requirements route through 8-24 for every participant. Communication rules specify how parents/guardians are updated before, during (if needed), and after the program, and who the single point of contact is. Roles are defined so no adult is ever alone with a single child outside another adult's view — a standard "two-adult" or "open-door" rule, whichever fits the setting. The Youth Lead reviews this plan with every adult volunteer before the program, not just distributes it.

If a youth-safety concern arises during the program — however minor it seems to whoever notices it — the response follows the Youth Protection Policy's escalation rule exactly: report immediately to the Youth Lead, no informal handling at the volunteer level, and escalation to CPD or appropriate authorities if warranted (Phase 5, 5-45). The plan names, specifically for that program, who fills in if the Youth Lead is the one unavailable when something happens, since a plan naming only one escalation point isn't really a plan. After the program, the Youth Lead does a short debrief with the adult volunteers — not necessarily a full After-Action Review — checking specifically whether supervision ratios and the two-adult rule held up in practice, and whether anything about the program's design (space layout, timing, group size) made those harder to maintain than expected. A recurring youth program is not repeated on autopilot with a stale plan; it's refreshed against this debrief each time it runs again.

Data collected here is handled per the Data Privacy Policy (Phase 5, 5-34) — minimized, access-restricted, and never used as a general mailing list.

Separate from the meeting-recording consent procedure (Phase 5, 5-20/5-21), this release covers identifiable images of event/program participants used in Council materials — required for minors, and good practice generally whenever a specific individual (rather than a general crowd shot) is featured.

Sets the standard every partnership under 8-27 through 8-30 is measured against, so "we should partner with them" is answered by policy rather than by whoever happened to make the connection. Due diligence (8-27) is completed before any commitment is made, however informal the initial conversation felt. Genuine mission fit means the partner's involvement actually advances the Council's purposes under Bylaws Article 2 — not just that partnering with them would look good or bring in a recognizable name. Approval authority: routine, no-cost partnerships (a co-hosted listening session, a cross-promotion) can be approved by the President or relevant committee chair; anything involving money, a facility commitment, or youth access requires full Board approval. Branding/co-branding follows the Logo Usage Policy (Phase 9, 9-04) — a partner does not use the Council's name or logo without specific approval, and the Council is equally careful about how it represents a partner. Data-sharing is limited to what's necessary for the specific collaboration and never includes the Council's membership or donor lists wholesale. Money involved in a partnership follows the same financial controls as any other Council funds (Phase 4). Insurance is confirmed where the partnership involves shared liability. And every partnership has a stated way to end it — a term, a notice period, or both — decided at the outset, not improvised if the relationship sours.

Active partnerships are reviewed at least annually, not just at signing — the Partnerships Lead brings a short status update to the Board covering whether the partnership is still delivering the mission fit it was approved for, whether any conditions attached at approval are still being met, and whether it's due for renewal, renegotiation, or a planned end. A partnership that has quietly continued past its stated term without anyone re-approving it is treated as a governance gap to fix, not a convenience to preserve. Where a partnership involves the drumming tradition or another established community cultural practice, the Cultural Programming Committee is looped in alongside Partnerships before any commitment, since the standards in the Cultural Programming Policy (8-20) apply on top of, not instead of, this policy.

A non-contractual memorandum for defining roles, deliverables, and communication expectations with a partner — used for collaborative relationships that don't involve money changing hands or a formal legal obligation. Every version includes: a plain statement of what each party will and won't do; how often the parties check in and who represents the Council in that relationship; a start date and either an end date or a review date; and the standard independence clause from the Contract Review policy (Phase 5, 5-39/5-40) confirming the Council cannot bind CPD, and the partnership doesn't imply CPD endorsement of the partner or vice versa. Signed by the President or a Board-designated officer, not by an individual committee member acting alone, since an MOU — however informal it feels — still commits the Council's name to something.

Used instead of the lighter-weight MOU (8-28) when the relationship involves defined financial obligations, paid services, insurance requirements, or a formal termination process. Beyond the MOU's basics, this template adds: specific payment terms and amounts (tied to the Delegation of Authority Matrix, Phase 2, 2-36, for approval level); insurance requirements matching the standard elsewhere in this phase (8-08); a termination clause stating notice period and what happens to any work in progress or funds already paid; and a dispute-resolution step before litigation is even a conversation. Given the added legal weight, this template is reviewed by counsel before execution, not just by the Board — the Council does not treat "we've used this template before" as a substitute for review on a specific agreement with real money involved.

Covers educational, research, or volunteer activity involving a school or university, with the youth-protection and data-privacy protections from 8-23/8-24 and Phase 5 built in from the start rather than added after a relationship is already underway. Specifies: the scope of the educational/research/volunteer activity and its schedule; which institution's policies govern student conduct/safety versus which govern the Council's own site rules; background-check and supervision requirements matching 8-23 if minors are involved; data handling for any student information collected; and, where the activity touches the dunes/natural area, an explicit cross-reference to Phase 7's research-approval chain (7-20/7-21) — a university research proposal does not bypass CPD's own natural-area research-permit process just because it's framed as educational. The Partnerships Lead and, for anything touching youth or the natural area, the Youth Lead or Environmental Committee, jointly review before signature.

Standards for actual listening, not token consultation — the difference between engagement and its appearance is whether anything changes as a result, and this policy is built around making that difference checkable. Feedback loops that close: anyone who raises an issue at a meeting, through the Annual Community Survey (8-32), or via the public contact channel (Phase 9, 9-30) gets a response about what happened with it, even if the answer is "the Board considered this and decided not to act on it, here's why" — silence is not an acceptable response to a raised concern. Inclusion beyond the regulars: the Membership Committee actively tracks whether engagement methods (meeting times, language, format) are reaching people beyond the small group who already attend every meeting, and adjusts when they aren't — using the Language Access Policy (Phase 9, 9-24) and Digital Accessibility Standard (Phase 9, 9-23) as concrete levers, not just aspirations. Public reporting: the Annual State of 63rd Street Beach / Community Report (Phase 10, 10-07) includes a specific section on what community input changed that year, not just a list of activities completed. This policy is reviewed annually alongside the Annual Governance Review (Phase 2, 2-40).

What "actually changed" gets tracked, not just claimed: when the Annual State of 63rd Street Beach report cites community input as the reason for a decision, the Membership Committee can point to the specific survey response, meeting comment, or listening-session note behind it. This isn't bureaucratic box-checking — it's the difference between a Council that can defend its decisions to a skeptical resident or a CPD reviewer and one that's simply asserting good intentions. Where engagement data shows the same narrow group responding year over year despite outreach efforts, that's reported honestly in the annual cycle rather than smoothed over, and becomes its own agenda item for the Membership Committee rather than a footnote.

Annual measure of community priorities, safety/accessibility perceptions, programming interest, and stewardship concerns — feeds the Community Needs Assessment (Phase 10, 10-10) and the annual work plan (Phase 10, 10-02). Distributed in multiple languages consistent with the Language Access Policy (Phase 9, 9-24) and in both digital and paper form, since a survey only reaching people already comfortable with the Council's online channels undercounts exactly the input the Community Engagement Policy (8-31) is meant to capture. Uses the template at Phase 11, 11-84, and results are summarized publicly, not just filed internally.

A ready-to-use kit so a listening session doesn't need to be reinvented from scratch by whichever Board member is running it. The facilitation guide covers ground rules for respectful disagreement, how to keep one or two voices from dominating the floor, and how to close each topic with a clear "here's what we heard" summary before moving on. The issue-capture form records concerns in the community's own words, not pre-summarized by the facilitator, so nothing gets lost in translation between what was said and what gets reported. The follow-up report (using this same commitment as 8-31) goes out within two weeks, not "eventually."

If launched, defines what meaningful (not decorative) youth voice looks like in Council decisions — a Youth Advisory Group whose recommendations are actually brought to the Board and responded to, not a photo-op committee that meets once. Covers: how members join (age range, application or nomination process); how young participants are mentored by an assigned adult liaison rather than simply supervised; safe participation boundaries consistent with the Youth Program Safety Plan (8-23), including the same background-check and two-adult expectations for any adult liaison; how often the group meets and how its recommendations reach the full Board (a standing agenda item, not an occasional invited report); and a sunset/renewal review so the charter doesn't quietly go stale once the founding members age out.

Addresses accessibility needs, heat/safety considerations at outdoor events, seating and shade planning, and programming that genuinely reflects older beach users' interests rather than treating them as an afterthought to youth-focused programming. Concretely: every outdoor event plan (8-09) includes shaded seating as a standard line item, not an add-on requested after the fact; heat-safety messaging (water availability, a cooling/rest area) is built into event communications during summer months; and the Community Engagement Policy's outreach methods (8-31) are checked specifically for whether they reach older residents who may not use the Council's primary digital channels. The Community Engagement / Accessibility owner brings a standing item to the Programs Committee at least once a year asking whether current programming actually serves this group or just assumes it does.

Fair, consistent recognition for service milestones — kept within the reimbursement/gift limits already set by the Code of Ethics (Phase 5, 5-24), so recognition never drifts into something that looks like a conflict of interest or an under-the-table payment for volunteer labor. Recognition is applied the same way regardless of who's giving it or receiving it: a defined hours or years-of-service threshold triggers a specific, modest, non-cash recognition (a public thank-you at a meeting, a certificate, a small item within the ethics policy's gift limit) — never cash, and never anything that could function as disguised compensation, consistent with the Bylaws' prohibition on salaried officers. The Volunteer Coordinator tracks who's reached a milestone using the Volunteer Training/Certification Log (Phase 6, 6-26) so recognition happens consistently rather than only for the volunteers who happen to be top of mind.

Recognition is public when the volunteer wants it to be and private when they'd rather it wasn't — the Volunteer Coordinator asks rather than assumes. Board members and officers are eligible for the same service-milestone recognition as any other volunteer, applied on the same terms, so recognition never looks like it's reserved for leadership or, conversely, withheld from leadership as a matter of appearances. A volunteer leaving the Council after significant service gets the same acknowledgment regardless of the circumstances of their departure, unless that departure involved a Code of Conduct or ethics matter under separate review.

Event-specific sponsor placement (signage, program mentions, verbal recognition, logo placement on printed materials) consistent with both CPD's approval requirements for that event and the Naming/Recognition Policy (Phase 4, 4-36) — the Council cannot grant a sponsor rights to CPD property regardless of sponsorship level, and any signage or structure a sponsor wants to place on-site is itself subject to CPD approval as part of the underlying event permit (8-05/8-06), not something the Council can authorize on a sponsor's behalf. This plan sets recognition tiers matching the Sponsorship Policy's benefit levels (Phase 4, 4-34) so every sponsor at a given tier gets the same treatment, and confirms in writing with each sponsor, before the event, exactly what recognition they're receiving — avoiding a mismatch between what was promised in the sales conversation and what's actually delivered on-site.

For alcohol specifically, CPD's real current process splits into two tiers reflected in 8-06: "Alcohol Service Only" (free service, no sale) and "Service/Sales" (alcohol sold, subject to additional requirements) — either tier requires security personnel on-site per CPD's rules, arranged and documented the same way as any other event security need. Cannabis and smoking follow whatever current Chicago Park District and City of Illinois/Chicago rules apply at the time of the event, which the Event Lead confirms with the Park Supervisor or Area Manager rather than relying on a rule that may have changed since the last event. This reference sheet is reviewed and re-verified before each relevant event, not treated as a fixed, one-time-written policy.

Enforcement on-site is the hired/CPD-required security's job, not a volunteer's — a Council volunteer who observes a rule violation (underage service, drinking outside the approved area, smoking somewhere prohibited) reports it to security or CPD staff on duty rather than confronting the person directly, consistent with the Council's general posture of referral over intervention (Phase 7, 7-28). If the event's alcohol service is discovered mid-event to be out of compliance with what was actually permitted, the Event Lead has authority to suspend service immediately while the issue is resolved, and the incident is documented on the Event Incident Report (8-43) regardless of whether anything worse resulted.

Sound level limits, cutoff hours, and neighbor communication for any amplified programming, staying within whatever permit CPD issues under 8-19 — created whenever amplified activity is actually proposed, not as a blanket rule applied to every gathering including the unamplified drumming tradition (8-21), which this plan does not govern or reference as a comparison point. When amplified sound is planned, this document names: the specific cutoff time (matching whatever CPD's permit specifies, since the Council does not set a more permissive time on its own authority); a plan for reaching out to any nearby residential contacts if the event runs later or louder than usual; and who on-site is responsible for actually monitoring volume and enforcing the cutoff, since a plan that exists only on paper doesn't prevent a complaint.

If a neighbor or park visitor raises a noise complaint during the event, the on-site monitor's first move is to check the current level against the permit limit and adjust immediately if it's running high — not to wait for a second complaint or a formal escalation before responding. Every complaint received, resolved or not, is logged on the Event Incident Report (8-43) so a pattern of noise complaints at a particular time slot or location shows up in the record rather than being separately forgotten after each event. Where amplified programming recurs at a similar time and place across multiple events, the cumulative complaint history is one of the factors the Programs Committee weighs when deciding whether to keep approving that format going forward.

Container placement, which vendors/volunteers own which cleanup zones, habitat protection near the dunes (cross-reference Phase 7), and a final walkthrough confirming the site is left in the condition CPD expects — completed and signed off before the event file is closed (8-44). Waste containers are placed and clearly marked before attendees arrive, not set out reactively once trash accumulates; vendors are responsible for their own booth-area waste under the Vendor Agreement (8-16); and any activity near the dunes/natural area follows the same "do not disturb habitat" standard as Phase 7's stewardship documents regardless of event context. The final walkthrough is done by a named person (typically the Event Lead or Operations Lead), documented with a simple sign-off, and any damage or unusual mess is noted for the Post-Event Report (8-44) — CPD's expectation is that a site is left as found, and the Council treats that as non-negotiable rather than aspirational.

Where recycling and general waste are both offered, containers are placed side by side with clear signage rather than recycling being an afterthought stuck somewhere less convenient — a recycling bin that's harder to find than the trash can guarantees contamination. For events large enough to generate meaningful volume, the plan estimates roughly how many containers are needed for the expected attendance rather than guessing on the day, and names who arranges pickup/removal afterward if CPD's standard park receptacles aren't sufficient. If the final walkthrough finds the site not left in the expected condition — whether due to the Council's own event or a prior park user — that's documented and reported to the Park Supervisor or Area Manager rather than silently absorbed as extra cleanup, since an unreported pattern of poor site condition can unfairly reflect on the Council's own standing with CPD.

Tracks Council-owned equipment (tents, signage, radios, supplies) separately from anything CPD owns, consistent with the Asset Inventory distinction maintained in Phase 4 (4-47) — the Council's own equipment stays clearly its own, never commingled with or mistaken for Park District property. The Operations Lead checks equipment out before an event and confirms its return and condition after, so damaged or missing items are caught immediately rather than discovered the next time the item is needed and it's gone.

Documents anything a Council volunteer observed at an event — an injury, a safety concern, property damage — and its referral to CPD, first responders, or the Council's insurer as appropriate, using the standard Incident Report Form (Phase 11, 11-55). Completed the same day, while details are accurate, by whoever witnessed or was first notified of the incident, then reviewed by the Risk Lead. The report never characterizes fault or offers the Council's own medical/legal judgment — it records what was observed, who was notified (lifeguards, CPD staff, 911), and what happened next. A pattern of similar incidents across multiple events is flagged to the Risk Register (Phase 5, 5-43) rather than treated as isolated each time.

Completed within two weeks after every major event, while the team's memory is still accurate, and referenced the next time a similar event is planned — this report only earns its place in the file if someone actually reads it before repeating the event next year. The Event Lead drafts it, the Programs Committee reviews it, and any recurring issue (the same accessibility gap, the same vendor no-show, the same underestimated attendance) gets a specific corrective action assigned to a named person before the file is closed, not just noted as a "lesson learned" that quietly resurfaces at the next event.

For recurring programs (not one-off events), measures outcomes beyond headcount: whether the program actually served its intended community benefit and stayed aligned with the Council's mission, not just whether it happened again this year. Asks concretely: did the people the program was meant to reach actually show up (cross-referencing the Community Engagement Policy's inclusion standard, 8-31)? Did participants report the program was worth their time? Did it advance a specific goal in the Annual Work Plan (Phase 10, 10-02), or has it drifted into something the Council runs out of habit rather than purpose? A program that fails this evaluation two years running is brought to the Programs Committee for a real decision — continue as-is, redesign, or retire it — rather than continuing by default. Results feed the Programs & Events Impact Report (Phase 10, 10-23).

The evaluation is completed by whoever leads the program, but reviewed by the Programs Committee, not accepted at face value — a program lead who has run something for years can be too close to it to see that it's drifted from its original purpose, which is exactly what an outside review is for. Where a program serves a specific population (youth, older adults, a particular cultural community), the evaluation also checks against that population's own engagement framework (8-34, 8-35) rather than a generic satisfaction question, so "people seemed happy" doesn't stand in for "this actually served the group it was meant to serve."