Beach & Environmental Stewardship

The comprehensive baseline every other stewardship document in this phase refers back to, rather than re-describing the site from scratch. It is organized in six categories: (1) Water & shoreline — the designated swim zone, the distance-swim area (parallel to shore between the 1st and 3rd buoys, per CPD's own facility page), and the non-motorized boat launch; (2) The historic Beach House — restrooms, showers, drinking fountains, and the event/rental space, each tracked separately since they have different maintenance owners and different condition-reporting cadences (see 7-34); (3) Accessibility infrastructure — the ADA-accessible beach walk and the beach wheelchair access point, tracked with enough specificity (surface type, width, current condition) to support the seasonal audits in 7-31/7-32; (4) Natural area — the roughly 12-acre "Jackson Park - 63rd St. Beach Dunes," CPD's own exact facility name for it, home to over 200 bird species including black-crowned night herons, least bitterns, piping plovers, and snowy owls; (5) Access & circulation — adjacent paths and parking; and (6) Cultural & public-art features — including the longstanding drumming gathering area, cross-referenced to the respectful-engagement protocol in Phase 8 (8-21) rather than described here as Council property.

The inventory is first created once the boundary/scope map (Phase 0, G0-02) is CPD-confirmed, since it should describe exactly the site the Council is actually authorized to advise on — not a larger or smaller footprint than Gate 0 resolves to. It is reviewed and re-verified against current CPD facility pages every spring before the beach season begins, and any discrepancy between what CPD's site currently lists and what the Council's inventory says is resolved in favor of CPD's current page, with the inventory updated to match — never the reverse.

Reviewed at the start and midpoint of every beach season at minimum, and immediately any time a volunteer or officer notices CPD's posted rules have changed. Anyone drafting volunteer training material, the Facility Fact Sheet (7-03), or any public-facing safety content pulls the current rule language from here, not from memory or from last year's version.

A one-page, plain-language fact sheet built from verified CPD sources (7-02, 7-05) and the site inventory (7-01): hours and season, accessibility features, lifeguard coverage window, the swim-flag system explained in one sentence per color, CPD contact points (Park Supervisor/Area Manager, and the beach's own contact address where CPD publishes one), and a short facility list. This is the thing handed to a new volunteer on day one, or posted at an information table, that doesn't require reading the full CPD rules reference to get oriented.

Reviewed seasonally and re-verified against 7-02/7-05 every spring, since hours, staffing, and even accessibility program details can change year to year; a stale fact sheet handed to a volunteer is worse than no fact sheet, so this document is explicitly dated on every printed or posted copy.

The annual plan tying this whole phase together, drafted by the Stewardship Committee and adopted by the Board each spring before the beach season starts. It sets, in five concrete categories, what the Council actually intends to do this season rather than what the library's documents generically permit it to do: (1) cleanups — target number and rough schedule, tied to the Beach Cleanup SOP (7-15); (2) habitat objectives — which specific CPD-authorized dune/habitat work the Council will pursue this year under 7-08, not a wish list of unauthorized ideas; (3) accessibility audits — confirming the season-start/midpoint/end cadence in 7-31 will actually happen and who's responsible; (4) education efforts — the currents/wave-hazard campaign (7-25) and any other public-safety-education push; and (5) CPD referrals — an honest look at what's currently unresolved from last year's Facility Maintenance Referral Log (7-35) and Shoreline/Erosion Log (7-14) that this year's plan should follow up on.

Drafting starts in late winter so the Board can adopt a finished plan before the Friday before Memorial Day, when the season itself begins — not a rough outline the Committee is still filling in once volunteers are already showing up. The Stewardship Committee chair presents a first draft to the full Board at least one regular meeting before the target adoption date, giving the Board a real chance to question priorities rather than rubber-stamp a plan seen for the first time at the vote. Each of the five categories names a specific person responsible for that category's follow-through, not just the Committee collectively, since a target with no named owner tends to quietly slide.

If conditions change mid-season — an unexpected CPD-authorized habitat opportunity arises, a target cleanup has to be cancelled for weather and can't be rescheduled, or a referral turns out to need more Council follow-up than planned — the plan is amended in writing at the next regular Board meeting rather than quietly abandoned. The amendment and its reason are recorded in the minutes so the fall report (7-41) can explain any gap between the original plan and what actually happened, instead of the gap simply going unmentioned.

The plan is reported against each fall through the Annual Beach & Stewardship Condition Report (7-41) — a direct, numbered comparison of "what we said we'd do" versus "what actually happened and why" — and that comparison directly feeds the following year's plan and the Council's broader Annual Work Plan (Phase 10, 10-02). A plan that isn't reported against its own targets isn't a plan, it's a wish list; this document exists specifically to prevent that.

The controlling rule set for the dunes/natural area — CPD's real current page title is "Natural Areas Rules and Regulations," not a generic "FAQ" page, and should always be cited by that exact title. The rules are absolute, not merely discouraged: no collecting, hunting, trapping, removal, or damage to plants, animals, fungi, or other natural features (wood, stems, leaves, flowers, seeds, and inorganic material are all specifically named); no fires in natural areas (grilling only in designated areas elsewhere in the park, never in the dunes); staying on marked paths and trails; and never entering fenced-off areas regardless of how minor the reason seems.

Maintained the same way as 7-02: current CPD source, archived with a checked date, never a Council-invented substitute or a softened paraphrase. Every dune/habitat document below (7-06 through 7-13) operates strictly inside these rules, not around them — and this reference is the document any volunteer or member should be pointed back to whenever a proposed habitat activity's compliance is in question.

CPD's own program governing authorized volunteer stewardship in natural areas citywide, real and confirmed name "Community Stewardship Program (CSP)," with its own named Handbook and Policy Guide and its own contact address (stewardship@chicagoparkdistrict.com). Volunteers advance through the program via a real apprenticeship track toward the real "Lead Stewards" tier, which CPD itself describes as the foundation of the program's success — worth naming as a concrete goal for any Council volunteer who wants to grow into a habitat-work leadership role, rather than a generic "senior volunteer" title the Council would otherwise have to invent.

The Council obtains and follows the current CSP Handbook/Policy Guide before any dune/habitat volunteer work begins, and re-confirms it hasn't changed at the start of each season. This is the entry point into the authorization chain that 7-07 through 7-11 depend on: no site agreement, no work authorization request, and no work log entry means anything unless the underlying volunteers involved are following CSP's current rules, not the Council's own improvised version of them.

The written CPD authorization naming exactly what work is approved in the dunes, by whom, with what tools, after what training, and within what site boundaries — the single gate the "do not disturb natural areas without authorization" boundary runs through. At minimum, the agreement specifies: the named individuals or defined volunteer group authorized to work (not "the Council" generically); the exact geographic boundary of authorized activity, referenced against the site inventory (7-01); the specific tasks approved (e.g., litter removal only, versus litter removal plus approved invasive-species work); required tools and personal protective equipment; any CSP training (7-06) each authorized volunteer must complete first; and an effective period, after which the agreement must be renewed or re-confirmed rather than assumed to still apply.

The Environmental Committee initiates renewal at least a month before the current agreement's effective period ends, rather than letting it lapse and only noticing when someone asks whether a planned workday is actually still authorized. A lapsed agreement means no authorized habitat work until it's renewed, full stop — there is no grace period where work continues on the assumption renewal is a formality.

No habitat work of any kind — not even work that seems obviously harmless — proceeds without this document in hand covering that specific work. If a volunteer wants to do something the current site agreement doesn't cover, the answer is to request an amendment or a new Habitat Work Authorization (7-10) before acting, not to act first and explain afterward. The signed agreement itself is kept in the PAC Binder (Phase 6, 6-01) and the digital repository (6-02) so any officer or volunteer can confirm current authorized scope without having to ask the Environmental Committee chair directly.

Site-specific, CPD-approved objectives for the native dune/shoreline habitat — the "Jackson Park - 63rd St. Beach Dunes," CPD's exact facility name for this roughly 12-acre natural area, home to over 200 bird species including black-crowned night herons, least bitterns, piping plovers, and snowy owls. The plan sets objectives in three tracks: (1) habitat quality — supporting the site's migratory-bird value by monitoring vegetation health and identifying priority invasive species for removal, always under the authorization chain in 7-07/7-10; (2) erosion and physical condition — tracking the observations logged in 7-13/7-14 against a baseline so trend, not just single incidents, drives priorities; and (3) volunteer capacity — how many CSP-trained stewards the site currently has and what apprenticeship/Lead Steward pipeline (7-06) the Council is building toward.

Each track's objectives are written as specific, checkable statements rather than general aspirations — "identify and propose removal of the two highest-priority invasive species stands flagged in this year's 7-11 log" rather than "manage invasive species" — precisely because a vague objective can't be honestly reported against in 7-04's fall accounting, and because CPD reviewers evaluating whether to authorize a given season's habitat requests respond better to a specific, defensible ask than a broad one.

Drafted jointly with CPD Natural Areas staff, not unilaterally by the Council — CPD's concurrence on the plan's objectives is what turns it from a wish list into something CPD will actually authorize work against. The draft goes to CPD Natural Areas for review and comment before the Board adopts it, and any objective CPD flags as unlikely to be authorized is either revised or dropped before adoption rather than adopted anyway and quietly never pursued.

Revisited at least annually, and specifically any time a Habitat Work Authorization (7-10) approves work materially different from what this plan anticipated, so the plan stays a true description of what's actually happening rather than a stale document nobody checks. Migratory-bird considerations under the Nesting Protection Protocol (7-12) are checked against this plan's timeline before any habitat-quality objective is scheduled, since timing relative to the nesting season can determine whether a given task is even eligible for CPD authorization that year.

Completed and reviewed by the on-site supervisor before every single workday, not just for large events — the document that turns the site agreement (7-07) and any specific work authorization (7-10) into an actual day's plan a volunteer can follow.

Used for anything beyond what the current site agreement (7-07) already covers as routine maintenance: planting, invasive-species removal, fencing, signage, or restoration work. The request describes the specific task, area, timeline, and tools, and is submitted to CPD Natural Areas before the work is scheduled — never after the fact, and never as a courtesy notification about something already planned. Approval (or CPD's requested changes) becomes part of that workday's authorization file (7-09) and, where the scope is significant, feeds an update to the Dunes & Habitat Stewardship Plan (7-08).

Records only work that was actually CPD-authorized under a specific site agreement or work authorization reference — never a running log of whatever ecological activity happened to occur, which would blur the line this whole subsection exists to keep sharp. A log entry with no authorization reference is a sign something went wrong, not a minor paperwork gap, and should be flagged to the Environmental Committee immediately.

Guidance for volunteers working near or observing the dunes during migratory/nesting season, given the site's confirmed value to over 200 bird species: keep a respectful distance from any observed nesting activity or dense vegetation that may shelter nests; do not attempt to move, touch, or "rescue" an apparently distressed bird or nest yourself; photograph from a distance rather than approach for a closer photo; and refer any observed distress, injury, or unusual activity to CPD Natural Areas or a qualified wildlife-rescue partner rather than intervening directly.

The protocol applies year-round in principle but matters most during spring and fall migration windows, when the dunes see the heaviest transient bird activity and the greatest chance a volunteer encounters an active nest or a grounded migrant unfamiliar with the site. Any scheduled habitat work under 7-09/7-10 that would occur in or near an active nesting area during the relevant season is flagged for CPD Natural Areas review before proceeding, since timing can matter as much as the work itself — a task that's routine in August may need to wait or be relocated in May.

Volunteers doing any dune-adjacent work receive this protocol as part of their CSP training path (7-06) before their first authorized workday, not as a verbal aside once they're already on site. A volunteer who observes something concerning — an injured bird, an apparent nest disturbance, an unusual die-off — records it the same way as any other environmental observation (date, location, description, photo if safely possible) and reports it to the Environmental Committee lead the same day, who is responsible for the CPD or wildlife-rescue-partner referral rather than leaving that judgment call to whichever volunteer happened to notice it.

Drafted with input from CPD and any partnering conservation organization familiar with the site's specific bird species, not invented internally by volunteers without ornithological expertise. Reviewed before each migration season to confirm the guidance still matches current CPD and partner-organization best practice, since species presence and site conditions can shift year to year.

Tracks recurring public foot-traffic damage to the dunes for CPD's awareness and possible signage/fencing response, checked at least monthly during the beach season. The Council observes and reports what it sees; it does not install its own barriers, signage, or path markers without CPD authorization, no matter how obviously helpful a quick fix would be.

Maintained on a regular seasonal cadence (at least monthly) and always within 48 hours after any major storm, high-wave event, or reported flooding — a documented, dated, photographed record is what makes later capital-advocacy conversations (Phase 10, 10-13/10-15) credible evidence rather than anecdotal impressions. Anything showing a safety hazard (exposed infrastructure, undermined pathways) is escalated to CPD the same day it's observed, not held for the next regular log update.

Every cleanup, from a two-person weeknight pass to a multi-organization event, follows the same five steps: (1) define the footprint from the site inventory (7-01) — cleanups stay within the Council's CPD-confirmed advisory scope and never wander into the dunes/natural area, which has its own stricter authorization chain (7-07/7-10); (2) brief before starting — every volunteer, including repeat volunteers, hears the safety gear requirement (gloves at minimum, closed-toe shoes recommended) and the hazardous-item escalation rule (7-17) before picking anything up, not just new volunteers; (3) segregate waste as it's collected — recyclables, general trash, and anything flagged as hazardous are kept separate from the start, not sorted afterward; (4) complete the debris log (7-16) before volunteers disperse, while counts are fresh; and (5) notify CPD in advance for larger group cleanups — a cleanup large enough to need its own staging, signage, or coordination with beach operations may itself trigger an Activity Request under Phase 8 (8-03), and the Stewardship Lead confirms that before publicizing the event, not after.

The pre-cleanup brief (Step 2) is delivered by a named Volunteer Lead, not left to whoever happens to be first on site, and covers four things every time regardless of group size or how many repeat volunteers are present: the day's footprint and any areas that are off-limits (dune edge, any active habitat-work zone); the gloves-and-closed-toe-shoes minimum; the hazardous-item rule in 7-17, including a live reminder of the 311 number; and where the first-aid kit and nearest emergency access point are for that specific stretch of beach. Volunteer sign-in and any required waiver (Phase 6, 6-24) happen at the same check-in table before the brief, not after volunteers have already dispersed to start working.

For a group cleanup large enough to need its own staging area, signage, or coordination with beach operations — a rough working threshold is anything drawing more participants than the Volunteer Lead can personally brief and supervise as one group — the Stewardship Lead confirms with CPD in advance whether an Activity Request (Phase 8, 8-03) or something larger is actually required, rather than guessing based on past events. Confirming this before publicizing the cleanup avoids the far worse outcome of promoting an event to the community and then discovering days beforehand that it needs an approval the Council hasn't sought.

This SOP is reviewed and re-briefed before every single cleanup — not assumed to be common knowledge even among volunteers who've done several before, since the point of a written SOP is that the safety-critical steps don't depend on any one person's memory. The SOP itself is reviewed by the Stewardship Committee at least once a season and updated immediately if a near-miss or incident report (6-30) reveals a gap in the current steps.

Completed before volunteers disperse from every cleanup, per 7-15's Step 4. Feeds both the Beach Stewardship Metrics Report (Phase 10, 10-22), where cumulative bags/weight becomes real, quotable evidence of the Council's stewardship impact, and — when something unusual turns up — triggers the escalation protocol in 7-17.

The four categories named above are deliberately broad rather than an exhaustive list, because the point of this protocol isn't memorizing a checklist of hazard types — it's the instinct to stop and escalate whenever something falls outside routine trash and recyclables, even if a volunteer isn't sure exactly what category it belongs in. When in doubt, the item is treated as hazardous until someone qualified says otherwise, not the reverse.

"The appropriate emergency channel" in Step 3 means 911 for anything posing an immediate danger to a person on site (an aggressive or clearly rabid animal, a leaking container with a strong chemical odor) and 311 for routine hazardous-debris pickup that isn't an active emergency — the Volunteer Lead present at any cleanup is expected to know this distinction and make the call personally rather than deferring to whichever volunteer found the item. Photographing the item from a safe distance, without touching or moving it, helps both the responding agency and the incident log, but is never done at the expense of keeping a safe distance.

This protocol is read aloud — not just handed out as a page in a packet — at the start of every cleanup involving any volunteer who hasn't done one before, and posted visibly at the check-in table for every cleanup regardless of group size. Any incident triggering Step 3 is also entered in the Incident Reporting & Escalation SOP (Phase 6, 6-30) in addition to this protocol's own log, since a hazardous-debris find is exactly the kind of event that log exists to capture Council-wide.

The reason this boundary is written as procedure rather than left as a general principle is that water-quality communication is exactly the kind of thing a well-meaning volunteer might improvise under pressure — a swimmer asks directly "is it safe today?" and a quick, confident answer feels more helpful than "let me check CPD's posting." Every volunteer with any communications or safety role is trained specifically to give the second answer, every time, regardless of how routine the question seems or how confident they personally feel about the water conditions.

The Communications lead named in the Beach Flag/Advisory Communication Checklist (7-24) is the only person authorized to post or repost water-quality content on the Council's channels, precisely so this rule has one accountable owner rather than being everyone's loose responsibility and therefore no one's. That person checks CPD's current posted status immediately before every post or repost — not from memory of what it said that morning — and sets a same-day reminder to re-check and, if necessary, correct or remove the post if CPD's own information changes before the day is out.

The Council never publishes an independent judgment — from a volunteer's own observation, a rumor, or anything short of CPD's official posting — that the water is or isn't safe. If a volunteer observes something concerning (discoloration, odor, dead fish), the correct action is to report it to CPD/Aquatics per the referral channels in this phase, not to post a public warning themselves. That observation is logged the same way as any other environmental observation and, if it involves a public-facing question the Council is being asked directly, the honest public answer is "we've referred this to CPD and are waiting on their assessment," not a Council-formed opinion.

Maintained through the beach season, checked at minimum weekly, for the sole purpose of spotting seasonal trends worth raising with CPD later (Phase 10, 10-25 Environmental/Water-Information Dashboard) — not for making any real-time public safety call itself, and not published as a live public feed without CPD's own advisory language attached per 7-18.

Any proposed sampling, collecting, monitoring, or research project — even a well-intentioned, informal-sounding community-science effort like "let's count the bird species we see each week" or "let's take a few water samples ourselves" — requires CPD/natural-area research authorization before it starts, per CPD's own real "Research Permit" process. The procedure has three steps: (1) the Environmental Committee documents exactly what's proposed (what's being observed/collected, how often, by whom); (2) that description is submitted to CPD Natural Areas for review before any activity begins, not as a courtesy notice about something already underway; and (3) if approved, the specific terms of approval become the Research Permit / Partner Study File (7-21) governing that project.

This procedure is the checkpoint that catches good intentions before they become an authorization problem — the risk isn't that a volunteer would knowingly break a rule, it's that an activity framed as casual community observation ("we just count what we see") can, without anyone intending it, drift into actual data collection, sample-taking, or repeated site disturbance that CPD would classify as research requiring a permit. Any Council member proposing an ongoing observation activity brings it to the Environmental Committee for this review before publicizing or starting it, even if it seems obviously informal.

For a research project approved under 7-20: the CPD permit documentation itself, the project's methods and scope, any data-sharing terms with CPD or the partnering institution, ethics considerations (especially if the project has any human-subjects component, such as visitor surveys), and the final findings once the project concludes. Created per project, not as a single running document, and retained as part of the Partnership Landscape (Phase 10, 10-12) so the Council has a durable record of who it has worked with and under what terms.

Implements Bylaws Article 22. A single designated Safety Committee contact — not a rotating or ad hoc volunteer — checks in with beach/lifeguard staff (CPD's Aquatics Unit, under the Captain of the Guards for the beach) on a regular cadence: at minimum once before the season opens, once at mid-season, and immediately whenever a specific safety concern arises. The purpose of each check-in is narrow: sharing community safety-education ideas the Council is planning (7-25) so they don't conflict with CPD's own messaging, and escalating any hazard the Council's observation logs (7-14, 7-27) have surfaced.

The pre-season check-in happens before Memorial Day weekend, early enough that any concern raised can actually be addressed before lifeguard coverage begins, and covers: introducing that season's designated contact if it's changed, confirming the current swim-flag and advisory posting process hasn't changed from what 7-02 has on file, and flagging any planned Council activity (a cleanup, a workday, an event) that will bring volunteers or crowds near the swim zone during the season. The mid-season check-in is a shorter temperature check — anything the designated contact should be aware of, anything CPD wants relayed to volunteers.

"A specific safety concern" triggering an immediate, off-cadence check-in includes anything surfaced through the observation logs in this phase — a damaged or missing life ring (7-27), a buoy or marker out of position (7-29), a pattern of near-misses reported informally to a Council volunteer — as well as anything a lifeguard or CPD staff member raises with the Council directly. The designated contact treats these as same-week, not same-season, priorities.

The liaison never directs lifeguard staffing, positioning, hours, or any other operational decision, which remain entirely CPD's authority regardless of how well-intentioned a Council suggestion might be. Every check-in is logged (date, topics discussed, any follow-up needed) so the relationship has a paper trail, and the relationship itself is built with beach staff input from the start — proposed to them as a partnership, not designed unilaterally by the Council and presented as a fait accompli. If the designated contact role changes hands, the incoming contact is personally introduced to CPD Aquatics staff, not just notified by memo, since the relationship this SOP depends on is a working one between actual people.

Applies to any post referencing the beach flag system, a swim ban, or any safety advisory — whether on the Council's own channels or shared/reposted from CPD's.

Delivered as a pre-season push timed to the two weeks before Memorial Day, when lifeguard coverage begins, using CPD's and the National Weather Service's own authoritative messaging about dangerous currents and wave hazards — never Council-invented safety claims. Channels are the Facility Fact Sheet (7-03), a dedicated flyer at the check-in area, and social posts following the Beach Flag Checklist (7-24) for accuracy. Content covers what a rip current looks like, what to do if caught in one (swim parallel to shore, don't fight the current), and — explicitly — what the education plan does not claim: it is purely educational, and any volunteer delivering this content is trained to say clearly, if asked, that they have no rescue role and cannot perform one.

A short refresher push runs again at mid-season, since the volunteers and repeat beachgoers who heard the pre-season messaging in May aren't the same audience present on a hot August weekend, and Lake Michigan's current and wave hazards don't become less relevant just because the initial campaign has run its course. Any volunteer delivering this content in person — at a table, during a cleanup, at an event — is trained on it the same way as the Swim/Rescue Non-Interference Policy (7-28), since the two documents' messages need to be consistent: educate freely, never claim a rescue role.

Any Council-run outdoor activity — a workday, a cleanup, an event — pauses or cancels based on current CPD/NWS conditions, not the Council's own weather judgment call. Specific triggers requiring an immediate pause: any lightning within audible/visible range; a National Weather Service severe thunderstorm, high-wind, or extreme-heat warning covering the site; or a swim ban/red flag posted by CPD during any activity involving water contact. A single designated person per activity (named in that day's Stewardship Workday Plan, 7-09, or Event Operations Plan, Phase 8 8-09) holds the go/no-go decision and is responsible for notifying registered volunteers/attendees immediately, using the Severe Weather / Cancellation Plan template (Phase 8, 8-11).

The designated decision-maker checks conditions before the activity begins, not only once it's underway, and has the sole authority to delay a start, shorten an activity, or cancel outright — no volunteer overrides that call because they personally feel comfortable continuing. During an extreme-heat warning specifically, the decision-maker also confirms shade, water, and rest-break availability are adequate for the activity's actual duration before deciding to proceed at all, rather than treating heat as a lesser trigger than a storm.

Activities do not resume until conditions clear per the same authoritative sources that triggered the pause — typically a defined waiting period after the last lightning strike or the expiration of the relevant NWS warning — and the decision to resume is made and communicated the same way the pause was, not left to volunteers to individually judge whether it feels safe enough to continue.

Checked visually during every scheduled workday or cleanup as a standing item, not just when something looks obviously wrong. Volunteers report; they never repair, replace, reposition, or relocate public safety equipment themselves, regardless of how minor the fix might seem — a life ring moved "to somewhere more visible" by a well-meaning volunteer is still a life ring CPD didn't authorize moving.

This is deliberately the strictest boundary in this phase, because the failure mode it prevents is the most serious one: a volunteer who feels responsible for the beach and, in a moment of genuine emergency, believes helping means physically entering the water. It doesn't, and this policy exists precisely so that instinct is overridden by a rehearsed response instead of an improvised one. A volunteer who is also a certified lifeguard is not exempt from this boundary while wearing a Council hat — if they act, they act as a private citizen or under an authorized CPD program's own supervision, never presented as "the Council's lifeguard."

The same non-interference principle applies to a person already being assisted by an on-duty lifeguard: a well-meaning volunteer does not enter the water to help, direct bystanders, or otherwise insert themselves into an active rescue, since an uncoordinated second responder can make a lifeguard's job harder rather than easier. The volunteer's role in that moment is limited to keeping other beachgoers at a safe distance and being available if the lifeguard or responding officers ask for specific, non-water assistance (crowd control, directing EMS to the scene).

This policy is acknowledged in writing, not just verbally explained, by every volunteer whose role could plausibly put them near the water (Phase 6, 6-24), and is reinforced specifically at the start of any event or workday that takes place near the swim zone. New volunteers hear it as part of orientation (Phase 6, 6-25) before their first shift, not only at the point they happen to be assigned a beach-adjacent role.

A feedback and observation channel specific to the designated distance-swim area, which CPD's own 63rd Street Beach page describes as running parallel to shore between the 1st and 3rd buoys. The Safety Committee's role is twofold: (1) collecting swimmer feedback on buoy/marker visibility and water conditions and passing it to CPD/Aquatics, rather than acting on it directly; and (2) a periodic visual check (at minimum monthly during the season) that the buoys, markers, and any signage are in place, upright, and legible, logged the same way as the Life Ring log (7-27). Again, observation and referral only — the Council does not place, move, or maintain any buoy or marker itself.

Covers the 63rd Street non-motorized launch: periodic observation of condition and use patterns (congestion at peak times, any damaged launch surface, unclear right-of-way), basic user education where the Council chooses to post it (right-of-way expectations, posted rules restated per CPD's own wording), and referral of any safety or maintenance issue to CPD through the Facility Maintenance Referral Log (7-35). The Council has no operational control over the launch — it does not manage scheduling, enforce right-of-way, or perform maintenance — and does not represent otherwise in any public-facing material.

A structured walkthrough of the ADA-accessible beach walk and shoreline access route, conducted at three fixed points each year: at season start (before Memorial Day), at mid-season, and at season end (after Labor Day), so findings capture both baseline condition and any degradation from a full season's use. Each walkthrough documents surface condition (cracking, sand encroachment, uneven transitions), obstacles (temporary or permanent), signage clarity, and — the part a purely technical inspection would miss — a plain, first-person description of the actual visitor experience for someone using a wheelchair, walker, or other mobility equipment, written by or with a person who has that lived experience where possible.

The Accessibility Committee actively seeks out participants with lived mobility-equipment experience for these walkthroughs rather than defaulting to whichever able-bodied volunteer is available — a technically accurate surface-condition note ("minor cracking, 2-inch gap") and a lived account ("this stretch is genuinely difficult to cross without help") are both valuable and neither substitutes for the other. Where no such participant is available for a given walkthrough, the summary says so explicitly rather than presenting a technical-only inspection as the full picture.

Findings are compiled into a short written summary and go to CPD as advocacy input supporting the accessibility priorities in the Council's capital-improvement recommendations (Phase 10, 10-13/10-14) — explicitly framed as community observation, not a Council-issued engineering assessment, since the Council has no authority or expertise to certify ADA compliance itself. The season-end summary specifically compares against the season-start baseline so any real degradation over the season (versus a condition that was simply always there) is visible in the record CPD sees.

Reviewed seasonally, at the same time as the Facility Fact Sheet (7-03), so the public-facing information about CPD's free beach-wheelchair service (available with a valid ID, per CPD's own program) stays current.

Applied by whoever is planning a cleanup, workday, or Council event, before it's publicized — not as an afterthought once volunteers have already signed up.

A regular (at least monthly during the season) walkthrough of the Beach House and general facility condition — distinct from 7-31's accessibility-specific audit, though the two are often done together to save volunteer time.

The downstream tracking log for every issue surfaced by 7-32, 7-34, or any other observation log in this phase once it's actually referred to CPD or 311 — the CPD Liaison checks open items at least monthly and follows up on anything without movement, rather than treating a submitted referral as the end of the Council's involvement.

Documents the Beach House's cultural and historic significance (a Classical Revival-style pavilion completed in 1919 and renovated in 2000, per CPD's own facility page), tracks its physical condition over time using the same walkthrough discipline as 7-34, and identifies respectful-use guidelines for events held there — including that any event use of the building follows CPD's real venue process (the Special Event Venue Application, Preferred Professional List caterers, and insurance minimums described in Phase 8, 8-07), not a Council-invented alternative. Findings and priorities feed the Council's capital-priority advocacy (Phase 10, 10-14/10-15).

The plan's advocacy component is specific rather than a general "we care about this building" position: it names the current condition issues found through 7-34's walkthroughs, ranks them by urgency and by how visible they are to the public using the space, and states what the Council is actually asking CPD to prioritize — a repair, a restoration study, funding for a specific improvement — rather than leaving the ask implicit. A condition finding with no corresponding ask tends to get noted and then forgotten; this plan exists so that doesn't happen to the Beach House specifically, given its irreplaceable historic value.

Respectful-use guidelines cover both formal rentals and informal community use: any group planning to use the building for an event confirms the correct CPD process in advance rather than assuming Council sponsorship is sufficient authorization on its own, and any signage, decoration, or setup respects the building's historic fabric (no permanent alterations, no attachment methods that could damage original materials). The Historic Preservation lead is a standing point of contact for anyone with questions about appropriate use of the space.

Drafted with CPD input, not unilaterally, given the building's status as CPD property — the Council's role is to document, advocate, and support respectful use, never to control access or make maintenance decisions on the building's behalf. Reviewed annually alongside the Facility Condition Walkthrough (7-34) findings so the advocacy priorities stay current rather than repeating the same ask year after year without acknowledging what's actually changed.

A catalog of Beach House architectural features, any public art at the site, and the longstanding cultural traditions present there — most notably the beach drumming gathering, which is addressed with its own respectful-engagement liaison protocol in Phase 8 (8-21) rather than catalogued here as if it were a Council-owned asset. This inventory is built within the CPD-confirmed scope (Phase 0, G0-02) and describes what exists at the site; it makes no claim of Council ownership or control over community culture the Council did not create and does not govern.

Council-wide commitments applied across every event and operation, not just stewardship activities: minimizing single-use plastics at Council-run events, preferring reusable or compostable serving materials where the Council controls the choice, providing recycling collection alongside trash at any Council-organized gathering, and factoring habitat protection into every planning decision that touches the dunes or shoreline before that decision is finalized, not as an afterthought.

These commitments are written as things the Council actually controls — its own event supply choices, its own planning process — rather than aspirations about the beach as a whole that the Council has no authority to enforce. Where a commitment depends on a vendor's choices (a food vendor's packaging, for instance), it's implemented as a term in that vendor's agreement (Phase 8, 8-16) rather than left as an unenforced hope that vendors will simply comply.

The habitat-protection commitment specifically means: before any Council event, workday, or facility use decision that could plausibly affect the dunes or shoreline is finalized, someone checks it against the current Dunes & Habitat Stewardship Plan (7-08) and the Migratory Bird Protection Protocol (7-12) — not as a formality, but as an actual point where a planned activity could be adjusted (timing, footprint, route) if it conflicts with an active habitat concern.

This is a values statement other phases' event and stewardship documents are expected to actually implement, not just cite — the Event Operations Plan (Phase 8, 8-09) and Waste/Recycling Plan (Phase 8, 8-41) should reflect these commitments concretely, and the Board reviews at least annually whether Council practice is actually matching this policy or has quietly drifted from it. That annual review is documented (what was checked, what if anything wasn't being followed, what corrective step was taken) rather than a verbal confirmation that everything's fine.

A Board-adopted statement naming explicitly that equitable beach access, shoreline safety, public health, habitat protection, and genuine community voice are connected, not separate concerns — that a beach without reliable accessible infrastructure, or a community whose health concerns about water quality go unheard, is not equitably served regardless of how well its dunes are protected. This statement is meant to inform priority-setting across every phase of this library, from accessibility audits (7-31 through 7-33) to capital advocacy (Phase 10) to who gets asked for input before decisions are made (Phase 8, 8-31 Community Engagement Policy) — reviewed alongside the Annual Governance Review (Phase 2, 2-40) to confirm it's shaping real decisions, not sitting unused.

Tracks longer-term patterns a single season's observation logs (7-14 shoreline/erosion, 7-27 safety equipment, 7-34 facility condition) don't reveal on their own: frequency of heat events triggering activity pauses under 7-26, storm frequency and severity, high-wave days affecting the swim area, erosion trend lines rather than single incidents, flooding events, and any sign of infrastructure stress at the Beach House or accessible walk tied to weather rather than routine wear.

The plan works by pulling a small, consistent set of counts from each season's already-existing logs — number of Severe Weather Protocol activations (7-26), number of "storm damage" entries in the Shoreline/Erosion Log (7-14), number of facility issues in 7-34's walkthroughs that specifically cite weather rather than ordinary wear — rather than creating a new, separate data-collection burden on volunteers. The value is entirely in aggregating what's already being recorded elsewhere and looking at it across multiple seasons rather than one season at a time.

A single unusual season (one bad storm, one heat wave) proves little on its own; what this plan is built to catch is a pattern that only becomes visible in year three or four — erosion accelerating rather than holding steady, heat-triggered activity pauses becoming more frequent than they were when this library was first drafted. The annual summary states plainly whether the current year continues, breaks, or is too early to judge against the established trend, rather than treating every year's numbers as a fresh, unconnected data point.

Reviewed annually, aggregating that year's incident-level logs into a trend summary, to inform both CPD advocacy priorities (Phase 10, 10-14) and the next year's Beach Stewardship Plan (7-04) — the point is to notice a pattern across three seasons that no single season's log would show on its own. Once several years of data exist, the summary itself becomes part of the Council's evidence base for capital-improvement conversations with CPD, since "this has been getting measurably worse for three seasons" is a stronger advocacy position than any single incident report.

The public year-end synthesis of this entire phase, structured around the same categories the Beach Stewardship Plan (7-04) set goals in each spring, so the report reads as a direct accounting against those goals rather than a disconnected summary: cleanups run (drawing on 7-16's cumulative totals), CPD-authorized habitat work completed against the Dunes & Habitat Plan's objectives (7-08), accessibility audit findings (7-31), facility referrals submitted and their resolution status (7-35), notable observations from the Climate Resilience log (7-40), and next year's priorities.

Published alongside the Annual State of 63rd Street Beach / Community Report (Phase 10, 10-07) as the stewardship-specific half of that story — written for a general community audience, not as an internal Committee memo, since this report is one of the clearest, most concrete things the Council can point to when demonstrating it has actually done what it said it would.