Strategic Planning & Reporting

Long-term outcomes across every phase of this library: beach stewardship and habitat health (Phase 7), water safety and accessibility (Phase 7), cultural vitality and the drumming tradition relationship (Phase 8), governance maturity (Phases 2-3), and the resource development capacity (Phase 4) needed to fund all of it. Built once real evidence exists — Gate 0 resolved, at least one full annual cycle behind the Council, and at least one completed Community Needs Assessment (10-10) — rather than drafted from assumptions alone before the Council has actually operated.

Recommended structure, once drafted:

1. Mission & scope reaffirmation — restates Bylaws Article 2's purpose in light of whatever CPD recognition status actually exists by the time of drafting (Gate 0, Phase 0).
2. 3-5 goal pillars with 2-4 measurable objectives each. Illustrative pillars for a beach PAC: (a) Stewardship & Habitat — e.g., "increase supervised dune workdays from a baseline year to a target number within three years"; (b) Accessibility & Safety — e.g., "close 100% of accessibility-audit findings rated high-severity within one year of identification"; (c) Cultural Vitality — e.g., "formalize the drumming-tradition liaison protocol (8-21) through co-created agreement, not unilateral adoption"; (d) Governance Capacity — e.g., "achieve full officer slate with contested elections by year three"; (e) Resource Development — e.g., "establish the fiscal structure decided under 4-01 and complete one full audited/reviewed financial cycle."
3. Resourcing assumptions — realistic volunteer-hour and budget assumptions behind each pillar, cross-referenced to the Annual Operating Budget (Phase 4, 4-12).
4. Risk factors — cross-referenced to the Enterprise Risk Register (Phase 5, 5-43), especially the standing risk that Gate 0 resolves in a way that requires re-scoping this entire plan.
5. Refresh cadence — reviewed via the Strategic Plan Progress Report (10-29) each year, fully redrafted at the 3-5 year mark or sooner if Gate 0 resolves in a way that changes the Council's legal footing.

This plan is explicitly NOT drafted as part of this initial document library pass — the Board should not adopt long-term goals before the Council has any operating history to ground them in. What's captured here is the structure the eventual plan should follow, not the plan itself.

The one-year slice of the Strategic Plan (10-01) — adopted alongside the annual budget at the same Board meeting so goals and money are never set separately from each other. Draft process: (1) each standing committee (per the Standing Committee Charter Set, Phase 2, 2-37) proposes 2-4 objectives for its area at the annual planning meeting, typically held the month before the fiscal year begins; (2) the Strategy Committee consolidates proposals, flags budget conflicts, and checks alignment against the multi-year Strategic Plan (10-01) and prior year's Community Needs Assessment (10-10); (3) the Board adopts the consolidated plan by majority vote alongside the Annual Operating Budget (Phase 4, 4-12); (4) progress is tracked at each regular meeting via the Action Item Tracker (Phase 6, 6-16) and reported formally at mid-year and year-end.

Every objective adopted into the plan carries at least one measurable success measure tied to the KPI Framework (10-08) — a target with no way to tell whether it was met isn't a real objective, it's an intention. Where two committees propose objectives that compete for the same volunteer capacity or the same budget line, the Strategy Committee's consolidation step is where that conflict has to surface and get resolved before adoption, not discovered mid-year when both committees are already committed to work the Council can't actually support simultaneously. A committee whose proposed objective depends on Gate 0 resolving a particular way (Phase 0) should say so explicitly in the proposal, so the Board can decide whether to adopt it conditionally or hold it for the following year.

The plan is not frozen once adopted: the Board may amend an objective's timeline, scope, or owner by majority vote at any regular meeting if circumstances genuinely change, though frequent revision defeats the purpose of planning annually rather than meeting to meeting, so amendments should be the exception rather than the norm. An objective that consistently carries over unfinished for more than two consecutive years should be flagged in the Annual Policy & Bylaw Review (10-18) as either under-resourced or no longer a real priority — not silently rolled forward indefinitely. A completed Annual Work Plan file, once the year closes, becomes part of the record reviewed when drafting next year's plan, so the Council can see its own actual track record rather than starting each year's planning from a blank page.

The core annual filing the Minimum Compliance Dashboard requires for continuing recognition — submitted using CPD's current official report format (see Phase 11, 11-93 for the working evidence checklist), assembled from records already maintained elsewhere in this library rather than reconstructed from scratch each year. Assembly checklist: (1) current election records confirming officers in good standing (Phase 1, 1-16, 1-32); (2) evidence of Illinois Not-For-Profit status, current within the year (Phase 5, 5-03/5-04); (3) confirmation the PAC Binder (Phase 6, 6-01) is complete and current at the park; (4) a financial summary consistent with what Treasurer's Reports showed at meetings that year (Phase 4, 4-14); (5) any officer changes filed via the Officer Update process during the year (Phase 1, 1-27/1-28); (6) confirmation the Council met the CPD-required quarterly minimum (Bylaws Article 12). Submitted to CPD's Department of Legislative and Community Affairs by whatever deadline the current official report instructions specify — the Secretary should confirm that deadline fresh each year rather than assuming it matches the prior year's. Only relevant once Gate 0 confirms this Council has a CPD relationship that requires this filing at all; until then, this document remains a template, not an active filing obligation.

Holds the copy of the Illinois NFP Annual Report actually filed under Phase 5 (5-03), plus an internal checklist confirming: the report was filed by the Illinois Secretary of State's due date (tied to the Council's incorporation anniversary month, not the calendar or fiscal year); the filing fee was paid and the confirmation receipt retained; the resulting Certificate of Good Standing or equivalent status evidence (5-04) was obtained fresh, not reused from a prior year; and that evidence was actually provided to CPD as part of the Annual CPD PAC Report (10-03), since CPD's own recognition depends on seeing current, not historical, NFP status. If the Illinois filing lapses for any reason, this file should also capture the reinstatement steps taken and the date good standing was restored, since a lapse can jeopardize CPD recognition independent of anything else the Council has done correctly that year.

Bundles copies of whatever federal/charity filings actually applied that year into one annual file, so "did we file everything we owed this year" has a single answer, not five scattered ones. Contents, only as triggered: the IRS Form 990/990-EZ/990-N (Phase 4, 4-54) if the Council holds its own federal tax exemption rather than using a fiscal sponsor; the Illinois Attorney General charity registration (Phase 4, 4-41) if the Council solicited and received more than $15,000 in charitable contributions in the 12-month period ending December 31 (the exact statutory threshold under 225 ILCS 460); and the Illinois AG990-IL annual report (Phase 4, 4-42) if registered. Each entry in this pack records the filing date, confirmation number if any, and the staff/officer who filed it. If NONE of these thresholds were triggered in a given year — a realistic outcome in the Council's early years — this pack should say so explicitly ("no federal or charitable-registration filings were required this year, because...") rather than being left blank with no explanation, so a future officer reviewing the file isn't left guessing whether something was simply missed.

The annual report CPD's current conduct guidance requires whenever the Council has actually handled funds, including the bank statement evidence CPD asks for — assembled directly from the Annual PAC Fundraising Report file (Phase 4, 4-40), not drafted separately. Minimum contents: total funds raised and spent that year by category (program, stewardship, events, administration, per the Chart of Accounts, Phase 4, 4-09); a current bank statement or equivalent evidence showing the Council's account balance; a summary of any capital fundraising activity and its status in the Phase 4 capital-partnership chain (4-56 through 4-60); and confirmation that no funds were used to pay a salary to any PAC member, CPD staff, or other organization for their efforts, which current CPD guidance prohibits outright. If the Council raised no funds in a given year, this report should state that plainly rather than being silently omitted, since CPD's compliance dashboard treats "no fundraising activity" as a valid, reportable status rather than nothing to report.

The plain-language public companion to 10-03 through 10-06's compliance filings: what the Council actually did this year, what it observed about the beach's condition, what the community raised as concerns, where money went, and what's planned next. Published per the Public Document Publication Schedule (Phase 9, 9-26), timed to follow the Annual Meeting (10-27) so it reflects whatever the membership actually discussed there rather than being finalized before members weigh in.

Recommended sections: (1) a one-page executive summary suitable for a flyer or social post; (2) year-in-review highlights across stewardship, accessibility, cultural programming, and volunteer activity; (3) condition observations from the year's Facility/Asset Condition Assessment (10-13) and Beach Stewardship Metrics (10-22), stated plainly including anything that got worse, not only improvements; (4) a plain-language financial summary (not a full audited statement — that lives in Phase 4) showing roughly what came in, what went out, and by category; (5) community concerns actually raised through the Public Comment Procedure (Phase 6, 6-15), Listening Sessions (Phase 8, 8-33), or the Public Records Request Log (Phase 5, 5-19), with the Council's response to each; (6) priorities for the coming year, tying directly to the next Annual Work Plan (10-02). A report that only lists accomplishments and omits problems observed that year is not transparent reporting — it's marketing, and undermines the credibility this whole library is built to establish.

A KPI is only useful if someone actually owns collecting it and it gets reviewed on a fixed schedule — this framework assigns both. Each indicator above has a designated data source already maintained elsewhere in this library (the Board Meeting Attendance Register for quorum, the Membership Roster for growth, Phase 6 volunteer logs for hours, Phase 7 cleanup logs for stewardship, Phase 7 accessibility audits, Phase 8 event records, Phase 4 budget-to-actual reports, and the Phase 6 Issue & Escalation Log respectively) so tracking KPIs doesn't create a second, parallel recordkeeping burden. Targets are set annually as part of the Annual Work Plan (10-02) — a KPI without a target attached to it is just a number, not a management tool.

The seven example indicators above map directly to the goal pillars a future Strategic Plan (10-01) would organize around — governance and membership indicators support the Governance Capacity pillar, volunteerism and stewardship support Stewardship & Habitat, accessibility supports Accessibility & Safety, events supports Cultural Vitality, and fundraising supports Resource Development. That mapping is deliberate: a KPI that doesn't trace back to a pillar the Council has actually said it cares about is a vanity metric, not a management tool, and should be retired from the framework rather than tracked out of habit. Most of these are lagging indicators (they measure what already happened); where practical, the Strategy Committee should also identify at least one leading indicator per pillar — something that predicts the lagging result before the year ends, such as volunteer sign-up rate as an early signal for eventual total volunteer hours — so problems surface in time to act on them.

The Strategy Committee reviews the full set quarterly and reports a condensed version publicly via the Annual Performance Dashboard (10-09). Adding a new KPI or retiring one requires Board approval, not a unilateral Strategy Committee decision, since KPIs shape what the whole Council pays attention to. A KPI that consistently misses target for two consecutive years should trigger a specific discussion at the next Strategic Plan Progress Report (10-29) about whether the target, the approach, or the resourcing behind it needs to change — the default response to a missed target is diagnosis, not simply lowering the number until it's met.

A concise scoreboard against the KPI Framework (10-08) — updated quarterly for internal board use, condensed and published annually as part of the State of the Beach Report (10-07). Format: one row per KPI showing current value, prior-year value, target, and a simple on-track/at-risk/off-track flag — deliberately not a dense spreadsheet dump, since the point is a Board member can scan it in under two minutes at a meeting and know where attention is needed. Trends matter more than any single year's number: a KPI slightly below target but trending upward is a different conversation than one that's been flat or declining for three straight cycles. The Strategy/Data Lead maintains the internal version continuously; the Board reviews it as a standing agenda item at each regular meeting rather than only at year-end, so course corrections happen mid-year when they're still useful rather than as a retrospective note in the annual report.

Structured evidence, not impressions: results from the Annual Community Survey (Phase 8, 8-32) and Public Listening Sessions (Phase 8, 8-33), direct observations from stewardship workdays and event feedback, relevant CPD data, and partner input — conducted before drafting or refreshing the Strategic Plan (10-01), not after the plan is already written.

Method: combine at least three input channels so no single loud voice dominates the picture — (1) the structured survey instrument (8-32), distributed both digitally and on paper at meetings/events to reach members without reliable internet access; (2) at least one in-person listening session per year (8-33), scheduled to avoid conflicting with the drumming circle's usual time; (3) staff/volunteer field observations logged through the year via the Beach Facility Condition Walkthrough (Phase 7, 7-34) and Accessibility Audits (7-31); (4) where relevant, CPD's own data on beach usage, incidents, or facility requests, clearly labeled as CPD-sourced. Materials for the survey and listening session are made available in the languages the Language Access Policy (Phase 5, 5-30) identifies as most spoken in the surrounding community — an assessment that only reaches English-speaking respondents isn't measuring the community's actual needs, it's measuring the needs of whichever part of the community happens to speak the language the survey was written in.

Findings are synthesized into a short written summary (not a raw data dump) identifying the 3-5 most consistently raised themes, explicitly noting where input channels disagreed with each other rather than smoothing over the disagreement — for example, if the survey shows broad satisfaction but the listening session surfaces a specific, sharply felt concern from a smaller group, both facts belong in the summary, since the second doesn't disappear just because it wasn't the majority view. Timed to complete before the Strategic Plan (10-01) refresh or the Annual Work Plan (10-02) drafting cycle begins, not after — running the assessment and drafting the plan in parallel defeats the purpose, since committees end up justifying objectives they'd already decided on rather than actually being shaped by what the assessment found.

The completed assessment, and the raw survey/listening-session data behind it, are retained per the Records Retention Schedule (Phase 5, 5-10) so a future assessment can compare against prior years' themes rather than treating each year as a clean slate — a theme that has recurred for three consecutive years and never made it into a Work Plan objective is itself a finding worth naming plainly to the Board. This assessment directly feeds the Strategic Plan (10-01) and Annual Work Plan (10-02) — a plan built without a current needs assessment behind it is really just the Board's own preferences, not the community's.

Names who actually has a stake in 63rd Street Beach beyond the Council's own membership: regular beach users, immediate neighbors, the drumming tradition community, schools, environmental and accessibility advocates, nearby businesses, the specific CPD units the Council interacts with (Park Supervisor/Area Manager, the Department of Legislative and Community Affairs, Aquatics, Natural Areas), Jackson Park Advisory Council, and relevant elected offices — kept current, not drafted once and forgotten.

Reviewed at least annually alongside the Strategic Plan refresh (10-01) and whenever a new committee is formed, since a new committee often surfaces stakeholders the original map missed.

Distinct from the Stakeholder Map (10-11), which names everyone with an interest in the beach; this register tracks only active or prospective formal Council partnerships with defined agreements or agreements under negotiation. Reviewed by the Partnerships Committee before each partnership renewal date and summarized annually in the Programs & Events Impact Report (10-23).

Rolls up the year's Beach Facility Condition Walkthroughs (Phase 7, 7-34) and Accessibility Audits (Phase 7, 7-31) into one periodic assessment for CPD advocacy purposes — a community observation report, explicitly not a substitute for CPD's own engineering inspection, and never represented as one to CPD, donors, or the public.

Conducted at the start, mid-point, and end of each beach season (aligning with the Accessibility Audit cadence, 7-31), covering: restrooms and showers, the historic Beach House exterior/interior condition, the accessible shoreline walk and beach wheelchair access point, walkways and lighting, signage, and the dunes/natural area boundary. Each finding is rated by severity (safety-critical, functional, cosmetic) and routed immediately to CPD via the Facility Maintenance Referral Log (Phase 7, 7-35) rather than held for the annual report — this assessment is a periodic SUMMARY of referrals already made, not the first time an issue surfaces. Feeds directly into the Capital Improvement Priority List (10-15) when a finding is severe or recurring enough to warrant a capital request rather than routine maintenance.

Transparent criteria, adopted before any specific project is scored against them — so prioritization can't be retrofitted to favor whichever project someone already wanted. Recommended approach: each criterion scored 1-5 by the Capital Committee, with safety and accessibility impact weighted more heavily than cosmetic or convenience improvements, consistent with the Council's Article 23 accessibility commitment. Scores and rationale are recorded in the Capital Improvement Scoring Matrix (Phase 11, 11-95) so a member or CPD staffer can see exactly why one project outranked another — not just the final ranking.

Any Capital Committee member with a personal or financial connection to a proposed project — a project that would benefit a business they own, a family member's property, or an organization they lead — discloses that connection per the Conflict of Interest Policy (Phase 5, 5-22) and does not participate in scoring that specific project, though they may still take part in scoring every other project on the list that cycle. A project proponent who believes their project was scored inconsistently with these criteria may request the Capital Committee walk through the scoring rationale with them before the final list goes to the membership vote (10-15) — this isn't a formal appeal process with a different outcome guaranteed, just a transparency check consistent with the whole point of scoring against public criteria rather than by closed-door judgment.

Scoring is scheduled with enough lead time to actually inform CPD's own capital planning cycle, rather than happening reactively after CPD has already set its own priorities for the year — the Capital Committee should confirm the current timing of CPD's relevant planning process and back-schedule the Council's own scoring to precede it where possible. This policy itself is reviewed every 2-3 years via the Policy Sunset Review (10-30) to confirm the weighting still reflects the community's actual priorities as captured in the Community Needs Assessment (10-10), not priorities that were current when the policy was first adopted.

The actual ranked list produced by applying 10-14's criteria, updated annually and submitted through CPD channels — a recommendation to CPD, not a Council-authorized capital budget, since the Council has no independent authority to build anything on CPD property. Typically 3-7 ranked items, each with a one-paragraph justification tied directly to the scoring criteria, an order-of-magnitude cost estimate where known, and current status in the capital-partnership process (Phase 4, 4-56 through 4-60). Presented to the membership at the Annual Meeting (10-27) before submission to CPD, so the ranking reflects a vote of the full Council, not just the Capital Committee's own judgment.

Tracks every capital idea from concept through the Letter of Intent, Pledge, Proof-of-Funds, and Executed Agreement chain in Phase 4 (4-56 through 4-60) to final closeout, signed by the PAC and CPD's General Superintendent or designee (4-59). Unlike the Priority List (10-15), which shows only this year's top-ranked recommendations, this register keeps every project ever proposed — including ones CPD declined or the Council shelved — so institutional memory survives officer turnover and the same rejected idea isn't unknowingly re-proposed a few years later without understanding why it didn't move forward the first time.

The annual review that refreshes the Enterprise/PAC Risk Register (Phase 5, 5-43) — scoring governance, safety, event, financial, environmental, cyber, and reputational risks by likelihood and impact, and confirming mitigation owners are actually assigned, not just risks named and left unaddressed. Conducted by the Risk Lead with the full Board at least once annually, typically ahead of budget season so identified risks can actually influence the coming year's Annual Operating Budget (Phase 4, 4-12) — for example, an insurance gap identified here should show up as a line item in that budget, not just as a note in a report nobody revisits.

Scoring method: each risk is rated Low/Medium/High on likelihood and separately on impact, and the two ratings are combined into a simple 3x3 priority grid rather than a false-precision numeric score — the goal is to sort risks into "needs a mitigation plan now," "worth monitoring," and "acceptable to accept as-is," not to produce a number nobody can defend. A risk landing in the "needs a mitigation plan now" cell without an assigned owner and target date by the end of the same meeting is a process failure, not an acceptable outcome of the review.

Standing risk categories to score every year, at minimum: Gate 0 recognition status changing unexpectedly or resolving in a way that requires re-scoping the Council's structure (Phase 0); loss of a key officer with no successor identified (cross-referenced to the Succession & Leadership Development Review, 10-26); a safety incident at a Council-run event; a data breach affecting member/donor records (Phase 5, 5-38); and non-renewal of the Council's fiscal sponsorship arrangement, if applicable (Phase 4, 4-01/4-02). A risk that materializes between annual reviews — an actual incident, not a hypothetical — is added to the register immediately through the Compliance Exception / Corrective Action Log (Phase 5, 5-49) rather than waiting for the next scheduled Risk Assessment to acknowledge it formally. Each identified risk gets an assigned owner, a target mitigation date, and a status at the next review — a risk register with no owners assigned to any risk is a list of worries, not a risk management tool.

Executes the Annual Governance Review Checklist (Phase 2, 2-40) and Policy Sunset Schedule (Phase 6, 6-36) as an actual annual report: which documents in this library were reviewed this year, what changed, what was formally adopted, and what got retired as obsolete — the mechanism that keeps a 510-document library from calcifying into 510 documents nobody ever looks at again.

Minimum annual scope: (1) the Bylaws (Phase 2, 2-02) — even if no amendment is proposed, confirm they still match current CPD guidance, since CPD's own materials change (this library's own terminology audit found real gaps between a prior draft and CPD's actual Feb 2025 guidelines); (2) any policy flagged for review that year under the Policy Sunset Schedule's 1-, 2-, or 3-year cycles; (3) any policy that generated a Compliance Exception or Corrective Action Log entry (Phase 5, 5-49) during the year, since a policy that keeps getting worked around in practice may need to change rather than keep being violated; (4) the Master Document Register / search catalog itself (Phase 6, 6-03), to confirm every document's status label is current.

Each reviewed item gets a one-line disposition: no change needed, amended (with the amendment recorded per 2-38), or retired (per the Policy/Committee Sunset Review, 10-30). An amendment to the Bylaws specifically requires the membership vote threshold Article 30 sets, not just Board sign-off — this review can recommend a Bylaws amendment, but the Governance Committee has no authority to treat that recommendation as adopted until the membership actually votes on it. For policies below the Bylaws (individual documents throughout Phases 3-10), the Board's ordinary majority-vote adoption process applies unless the specific policy states otherwise.

Because CPD's own PAC Guidelines and a peer council's bylaws have already been found, during this library's terminology audit, to use different names for the same complaint body ("PAC Governance Committee" versus "Complaint Review Committee (CRC)," Phase 5, 5-46), this review is also the annual checkpoint for confirming whether that ambiguity has since been resolved by LCA — if CPD clarifies the correct current name, every document in this library that cites both names pending confirmation should be updated in the same review cycle, not left citing an ambiguity that's already been resolved. Published as part of the Annual Meeting Report (10-27) so the membership sees governance maintenance happening, not just program activity.

The completed, written-up version of the Board Self-Assessment tool (Phase 3, 3-18) — engagement, compliance, strategic contribution, financial oversight, and succession readiness, with specific improvement actions assigned to specific people, not just observations left unaddressed. Conducted anonymously where possible (a simple written survey each officer/director completes independently before discussion) so junior or newer board members feel able to raise concerns about more senior officers without it becoming personal in the room. Results are discussed as a group, with the President recusing from facilitating that specific discussion if the assessment raises concerns about the President's own performance — the Vice President or Governance Committee chair facilitates instead. Findings feed directly into the Succession & Leadership Development Review (10-26) and, where relevant, into candidate conversations ahead of the next election cycle.

Measures whether members and the broader community actually trust the Council, find meetings worthwhile, feel heard, and agree with its stated priorities — distinct from the Annual Community Survey (Phase 8, 8-32), which asks about the beach itself rather than about the Council's own performance. Core questions, asked consistently year over year so trends are actually comparable: satisfaction with meeting quality and accessibility; whether respondents feel their input to the Council is actually heard and acted on; trust in the Council's financial stewardship and transparency; awareness of how to reach the Council with a concern (Phase 9, 9-30); and overall satisfaction with the Council's responsiveness to the community. Conducted annually or biennially depending on capacity, distributed through the same multi-channel approach as the Community Needs Assessment (10-10) to avoid over-sampling only the members most already engaged. Low or declining trust scores should trigger a specific conversation at the next Board meeting, not just a note in the annual report.

An estimated dollar value of donated time (using a standard published volunteer-hour valuation) belongs alongside the hours total — this is often the single most persuasive figure in a grant application or sponsorship pitch, since it demonstrates community investment funders can't buy. Retention rate specifically distinguishes long-term Adult Volunteer Application holders (Phase 1, 1-27) from one-day/group volunteers (Phase 6, 6-24), since the two groups have very different retention expectations and treating them as one number obscures whether the Council is actually building a durable volunteer base or just running one-off events.

Aggregates the year's Cleanup Waste Logs (Phase 7, 7-16), habitat work logs (7-11), observation logs (7-13, 7-14), and CPD referrals into one annual stewardship metrics report — feeding directly into the Annual Beach & Stewardship Condition Report (Phase 7, 7-41) and the KPI Dashboard (10-09). Core metrics: total cleanup events and volunteer-hours; debris removed by weight/bag count and any notable hazardous-material finds (Phase 7, 7-17); habitat/dune workdays completed under CPD authorization (7-08, 7-09) and acreage or linear footage covered; number of facility-condition and accessibility issues referred to CPD (7-34, 7-35) versus number resolved within the year; and any migratory-bird or erosion observations of note (7-12, 7-14). Presented with year-over-year comparison, not just the current year in isolation, since a single year's cleanup total means little without knowing whether the beach's condition is improving or the volunteer base is shrinking.

Rolls up each event's After-Action Review (Phase 8, 8-44) for the year: total participation, accessibility outcomes, cultural/community impact (with particular care for how programming interacted with the drumming tradition liaison, Phase 8, 8-21), finances, incidents, and lessons carried into next year's Annual Work Plan (10-02). The cultural-impact section in particular should be reviewed with, not just about, the drumming-tradition community and any other cultural partners before publication — this report should never be the first time tradition-bearers learn how the Council characterized the year's interaction with their community. Financial rollup ties to the Fundraising Campaign Files (Phase 4, 4-39) for each event rather than restating figures independently, so the two reports can never quietly drift apart. A year with zero incidents reported should be stated as a positive finding, not omitted as if there were nothing to say.

The annual synthesis across every accessibility touchpoint in this library: meeting accessibility (Bylaws Article 23), digital accessibility (Phase 9, 9-23), beach-walk/shoreline audits (Phase 7, 7-31), and event accessibility plans (Phase 8, 8-13) — one report naming what's working and what's still a gap, rather than each committee tracking its own piece in isolation. Written from the standpoint of actual accommodation requests received and how quickly/fully they were met (Article 23), not only from audit checklists — a beach walk can pass every item on a checklist and still fail a specific person's actual need if the checklist itself was incomplete. Findings that recur across multiple years without resolution (for example, a persistent gap in the accessible route's condition that CPD hasn't yet addressed despite repeated referrals) should be escalated explicitly in this report to the Board for a decision on further advocacy, not simply re-logged year after year as a known issue.

Combines the season's CPD Water Quality/Swim Advisory Archive Log (Phase 7, 7-19) with the Council's own habitat/erosion observations (7-13, 7-14) into one dashboard — every CPD-sourced figure clearly labeled as CPD's own data with a source and date, and every Council observation clearly labeled as the Council's own, never blended together in a way that could look like an official water-quality claim (Bylaws Article 22, Phase 7 7-18). The same "restate, don't reinterpret" boundary that governs any individual public post about water quality (7-18, Phase 9 crisis-communications tie-in 9-20) applies here too — a dashboard is still a publication, and aggregating CPD's data doesn't create license to characterize it differently than CPD does.

Maintained live during beach season (Memorial Day through Labor Day) rather than assembled only at year-end, since the whole point is timely information during the season it's actually relevant. Updated at minimum weekly, matching the check cadence set in the Archive Log (7-19), with the "last checked" timestamp visible on the dashboard itself so a viewer never has to guess whether what they're looking at is current. Access to edit the live dashboard is limited to the Environmental/Data Lead and one designated backup, consistent with the Digital Access Policy (Phase 5, 5-37) — a dashboard anyone can edit is a dashboard nobody can vouch for.

Outside the beach season, the dashboard is archived rather than left displaying stale in-season data, and a simple "beach season is currently closed; the live dashboard resumes [date]" notice replaces it — leaving a September reading visible in December risks exactly the kind of stale-information confusion this dashboard exists to prevent. The annual summary version — trends across the season, not day-by-day detail — is what appears in the State of the Beach Report (10-07); the live version stays internal/operational, since republishing daily swim-status detail risks it going stale and being mistaken for a current advisory after the fact. A pattern worth flagging to CPD directly and promptly (a season with unusually frequent advisories, for instance) should be raised outside the annual reporting cycle via the normal CPD Liaison channel, not held for the next State of the Beach Report months later.

Reviewed every year before elections, alongside the Board Recruitment & Succession Plan (Phase 3, 3-19): which offices have a viable pipeline of interested candidates, which don't, what training gaps exist, and what happens if a key officer leaves unexpectedly before their term ends. For each of the four required offices (President, Vice President, Treasurer, Secretary), this review asks plainly: is there at least one member, beyond the current incumbent, who could credibly step into this role within the next election cycle? If the honest answer is no for any office, that becomes an explicit recruitment priority in the next Annual Work Plan (10-02), not a risk quietly carried forward. Because CPD's current guidelines require officers to be Chicago residents (Bylaws Article 5), this review should specifically track whether the pipeline for each office includes enough Chicago-resident candidates, since that eligibility requirement can quietly shrink the real candidate pool if it isn't tracked deliberately.

The single presentation that pulls the year together for the full membership at the annual meeting: year-in-review highlights, the Treasurer's financial summary, election results if held that cycle, progress against the Annual Work Plan (10-02), and priorities for the year ahead. Structured as a genuine presentation to be delivered aloud and discussed, not a written report merely distributed and skipped over — the annual meeting is one of the only points in the year where the full general membership (not just the Board) gets a direct say, and this presentation is the vehicle for that. Time is reserved on the agenda for member questions and open discussion before any vote (such as bylaws amendments or elections) is taken, consistent with the Public Comment/Community Input Procedure (Phase 6, 6-15). The finalized slides/notes are archived in the PAC Binder (6-01) and inform the following year's State of the Beach Report (10-07).

Signed off by both the Secretary and Treasurer, with the President countersigning confirmation the checklist was reviewed at a Board meeting — not completed unilaterally by staff/officers without Board visibility into what's actually done versus outstanding.

A quarterly or semiannual check-in against the multi-year Strategic Plan (10-01) — are the annual work plans (10-02) actually adding up to the longer-term goals, or has the Council drifted, and if so, what course correction does the Board need to make now rather than at the next full plan refresh. Format is deliberately lightweight: for each of the plan's goal pillars, a brief status (on track / at risk / off track), the evidence behind that status (drawn from the KPI Dashboard, 10-09), and, for anything at risk or off track, a specific corrective action with an owner and date — not a restatement of the whole plan each time. This report is where "we haven't gotten to that yet" becomes visible early enough to actually address, rather than becoming a surprise at the multi-year refresh when it's too late to course-correct within the current plan's timeframe.

On a scheduled cycle (see the Policy Sunset Schedule, Phase 6, 6-36), asks a genuinely hard question of every standing committee and policy in this library: does this still need to exist, is it still doing anything, and if not, is retiring it the honest move rather than leaving it on the books unused. A living document that never sunsets anything isn't actually living — it's just accumulating.

Practical test for a committee: has it met on its stated cadence in the last review period, and has it produced anything (a report, a recommendation, a completed project) that the Board actually acted on? A committee that exists on paper but hasn't functioned should either be reactivated with a clear charge or formally dissolved — not left listed in the Standing Committee Charter Set (Phase 2, 2-37) as though it's operating. A dormant committee is also a governance risk on its own: it implies a level of oversight or capacity the Council doesn't actually have, which matters if CPD, a funder, or a member ever relies on that appearance.

Practical test for a policy: has anyone actually referred to it, cited it, or been held to it in the review period? A policy nobody has needed to reference may genuinely be unnecessary, or may simply need better visibility — this review should distinguish between the two rather than defaulting to retirement whenever a document goes quiet. A policy tied to an active legal or CPD requirement (anything carrying a CPD-R, IL-R, or FED-R classification elsewhere in this library) is not eligible for retirement on the "nobody's used it" test at all, regardless of how quiet it's been — silence doesn't remove a statutory or CPD-imposed obligation, it just means the obligation hasn't come up recently.

The review runs on the cadence the Policy Sunset Schedule (Phase 6, 6-36) sets — typically staggered across a 1-, 2-, or 3-year cycle by document type, so the whole 500-plus-document library is never all up for review in the same year — and is chaired by the Governance Committee with findings brought to the full Board for a vote on any retirement or reactivation, since neither decision belongs to the Governance Committee alone. Retirement decisions are recorded in the Policy Register & Version History (Phase 2, 2-39) with the reason, never simply deleted without a record that the policy once existed and why it was retired — a future officer should be able to find out that a policy existed and why the Council chose to let it go, not just find a gap where it used to be.