Operational & Administrative Manuals

The in-park compliance file CPD's current PAC Guidelines expect to exist at the recognized meeting location — distinct from, and narrower than, the permanent Corporate Records Book (Phase 5, 5-07). Contains, matching CPD's own required-contents list verbatim ("bylaws, financial statements, meetings agendas, minutes, sign in sheets, and evidence of Not-For-Profit status with the State of Illinois"): the current Bylaws (2-02) and NFP status evidence (5-04), the current CPD Code of Conduct (1-02), the last twelve months of agendas and approved minutes (6-12), recent Treasurer's Reports (4-14), and sign-in sheets/attendance records (6-13). Established the moment CPD recognition is confirmed (Phase 0/1), and self-audited quarterly against the CPD PAC Binder Compliance Checklist (Phase 5, 5-14).

A cloud mirror of the PAC Binder plus everything the in-park binder can't hold: full corporate history, every policy, every event and grant file, and this Organization document library's source material. Role-based access — officers and committee chairs get what their role needs, not blanket access to everything (donor records, background-check details, and active legal-hold material stay restricted regardless of officer rank). This public library at /bbpac/organization/ is deliberately the public-facing front door onto this repository: what's published here is what the Council is comfortable with anyone reading; what's not published (personal data, in-progress drafts, sensitive logs) stays in the private repository even after this page-by-page rollout is complete.

The index of all 510 documents in this checklist — which, as it happens, is not an abstraction here: it's literally the data.js file powering the search catalog at /bbpac/organization/documents/, where every document's ID, title, classification, owner, and drafting status already lives as a maintained, machine-readable record. Updating that file each time a document is drafted, adopted, or revised is keeping this register current — there is no separate spreadsheet to reconcile against it.

Every governing document in this library moves through the same lifecycle, and its current position in that lifecycle is always visible on the document itself, not left to inference: Draft (being written, not yet ready for review) → Proposed (drafted and posted publicly, awaiting Board adoption — the status every document in this library currently carries) → Adopted (formally approved by Board vote, per the Policy Adoption / Amendment Procedure, Phase 2, 2-38) → Superseded (replaced by a later version but retained, not deleted) or Retired (no longer applicable). Only the Board can move a document from Proposed to Adopted; the Records Officer cannot change a document's substantive status alone, though they do own the mechanical version marker day to day.

Each document carries a version marker (v1, v2, v3…) that increments on any substantive content change — a new procedural step, a changed threshold, a corrected fact — but not on a typo fix or formatting cleanup, which is noted in a changelog line instead of bumping the version. A single authoritative-copy location exists for every document: for anything published in this public library, that location is the library itself; for internal-only records, the Digital Governance Repository (6-02). No second "working copy" is ever treated as authoritative, even temporarily during a revision — edits happen directly against the authoritative copy or a clearly marked draft, never in an untracked duplicate that could quietly diverge.

This matters most at the exact moment it's easiest to get wrong: when an officer is working from a printed or downloaded copy that quietly became outdated after a later revision. The rule is simple and absolute — the version in the authoritative location always controls, and any copy elsewhere (a printout, an email attachment, a personal drive) is treated as potentially stale until checked against it. When a document is superseded, the prior version is archived with its version marker and adoption date intact, not deleted, so the Council can always answer "what did this policy say when that decision was made" — a question that matters disproportionately during a dispute, an audit, or a CPD inquiry into past practice. The new version's adoption date is recorded per the Policy Adoption / Amendment Procedure (Phase 2, 2-38), and the Master Document Register (6-03) is updated the same day a status or version changes, never on a delay.

A folder structure mirroring this checklist's own 12 phases (Governance, Board, Finance, Legal, Operations, Stewardship, Programming, Communications, Strategy) plus year-based subfolders for meetings, events, and grants, adopted before the Digital Governance Repository accumulates enough files that retrofitting a structure becomes painful — restructuring a repository with hundreds of files already in it is far more disruptive than adopting a sensible structure on day one. File names follow a consistent pattern: YYYY-MM-DD_DocumentID_ShortTitle_vN (e.g. 2027-03-14_4-12_Annual-Operating-Budget_v2), so a file's date, source document, and version are legible from the name alone without opening it. The Records Officer audits the taxonomy annually and folds in any ad hoc folder that's sprung up outside the standard structure.

A year-end snapshot: every final record produced that year, exactly where it lives, and which retention category (Phase 5, 5-10) governs how long it's kept. This index is what makes the Records Retention Schedule actually enforceable in practice — without it, "retain for five years" is a rule with no way to know which specific files it applies to once enough time has passed that nobody remembers. Completed as part of the Year-End Records & Filing Closeout Checklist (Phase 10, 10-28).

The Digital Governance Repository (6-02) is backed up automatically by its cloud provider, but automatic backup is not the same as a tested restore. Annually, the Technology Lead performs (and logs) an actual test restore of a sample file set — corporate records, current financials, and the current Bylaws at minimum — to confirm backups are real, current, and usable, not just present.

The end-to-end procedure implementing Bylaws Articles 12-13 and the Voluntary Open-Meeting Transparency Standard (Phase 5, 5-16). Every regular meeting follows the same sequence so no step depends on any one officer's memory:

1. Calendar published. The Annual Meeting Calendar (6-09) is posted every January, or immediately upon CPD recognition if that happens mid-year.
2. Notice issued. At least 14 days before a regular meeting (48 hours for an emergency or special meeting), notice goes out through every channel on the Meeting Notice Checklist (6-10) — the posted location, the website, and the mailing list — and proof of posting is saved before the meeting, not reconstructed after.
3. Agenda finalized. Committee chairs and officers submit items to the Secretary by the deadline in the Agenda Development Procedure (6-11); the President and Secretary lock the final order, always including the Public Comment slot (6-15) and any pending CPD item.
4. Quorum confirmed. Before the meeting is gaveled into business (not after a vote is already underway), the Secretary counts attendance against the quorum threshold in Bylaws Article 14 and records the count in the minutes.
5. Recording consent, if applicable. If any recording is planned, the Chair announces it at the start per the Recording Consent Procedure (Phase 5, 5-20); if any participant present objects, no recording happens, full stop — this is checked before the meeting starts, not treated as a formality to skip.
6. Business conducted. Motions, seconds, and votes follow Robert's Rules per Bylaws Article 28; conflicts of interest are disclosed and recused per Article 18 as they come up, not retroactively.
7. Minutes drafted and approved. The Secretary drafts minutes per the Minutes Preparation Standard (6-12) and circulates them for correction before they're formally approved at the following meeting.
8. Follow-through. New action items go into the Action Item Tracker (6-16) that same week; any formal decision is logged in the Decision Register (6-17); approved minutes are posted per the Public Document Publication Schedule (Phase 9, 9-26).

This Manual is adopted by the Board and reviewed annually alongside the Annual Governance Review Checklist (Phase 2, 2-40) — if a step in practice consistently gets skipped or reordered, that's a signal to amend this Manual to match reality, not a reason to quietly let the gap persist.

Published every January (or upon CPD recognition, whichever comes first): a recurring monthly meeting schedule — day, time, and location — for the full calendar year, consistent with the "at least quarterly" floor set by Bylaws Article 12 and current CPD guidance. This is the specific document that fulfills the "annual meeting calendar is published in advance" commitment made in the Voluntary Open-Meeting Transparency Standard (Phase 5, 5-16).

The proof-of-posting file is what actually demonstrates the Voluntary Open-Meeting Transparency Standard was followed for a given meeting, not just asserted after the fact. If a meeting is cancelled, notice of the cancellation is posted immediately and the Park Supervisor or Area Manager is informed.

A predictable rhythm so agenda-building isn't reinvented each meeting, run in the same sequence every time:

1. Item collection. Committee chairs and officers submit agenda items to the Secretary by a set deadline — five days before the meeting is the working default, extended to seven days for any item requesting a vote on spending above $500 or any policy change, so members have real time to review before being asked to decide.
2. Draft ordering. The Secretary drafts a proposed order following the Council's standing template: call to order/quorum check, approval of prior minutes, Treasurer's Report, standing committee reports, old business (Action Item Tracker follow-ups, 6-16), new business, Public Comment (6-15), and adjournment.
3. Consent-agenda grouping. Routine, low-discussion items — the financial report, standing committee updates with no action requested, approval of prior minutes — are grouped into a single consent section the Board can approve together with one vote, unless any single Board member asks to pull an item out for individual discussion, which they may always do without needing to give a reason.
4. President and Secretary finalize. The two review the draft together, reserve real discussion time for substantive business rather than letting it get squeezed at the end by routine items running long, and confirm any pending CPD staff item has a slot.
5. Posted before the meeting. The final agenda is posted per the Notice Checklist (6-10) — never handed out at the door, since a late-arriving agenda defeats the purpose of advance notice.

Late items may still be raised as "new business" at the meeting itself but cannot be voted on that same night unless the Board waives notice by unanimous consent — this protects members who planned their attendance around the posted agenda from being surprised by a vote they didn't know was coming. If two committee chairs request conflicting time for the same meeting, the President has final say on ordering, with the losing item guaranteed a slot at the next meeting rather than dropped. The Public Comment slot (6-15) and any pending CPD staff item always appear on the agenda when applicable.

Minutes are a record of decisions and actions, not a transcript — they record, at minimum: date/time/location, attendance and quorum confirmation, every motion with its exact wording, maker, second, and vote count (including any abstention), any conflict-of-interest recusal (Phase 5, 5-22) with the reason stated, officer/committee reports (by reference to the written report, not restated in full), and action items assigned. What minutes deliberately do not record: verbatim debate, individual members' side comments, or characterizations of tone — the goal is an accurate, defensible record of what the body decided, not a narrative of how the conversation felt.

The Secretary circulates draft minutes to the Board within ten days of the meeting for correction; corrections are proposed as amendments at the next meeting, not negotiated privately beforehand, so the full Board sees and votes on the exact change rather than trusting a private edit. If a proposed correction is substantive rather than typographical — it changes what the record shows a vote actually decided — the amendment itself is recorded in the following meeting's minutes with the original wording quoted alongside the correction, so neither version is ever silently overwritten. Once approved, minutes are posted publicly per the Public Document Publication Schedule (Phase 9, 9-26) — this posting step is the specific fulfillment of the Voluntary Open-Meeting Transparency Standard's (Phase 5, 5-16) "minutes are posted within a set number of days" commitment — and a copy goes in the PAC Binder (6-01) and the Digital Governance Repository (6-02).

If, months later, a minutes entry turns out to have recorded a vote or motion incorrectly in a way that matters (a contract term, a resolution number, a dollar figure), the fix is a formal correcting amendment approved at a subsequent meeting under this same procedure — never a quiet edit to an already-approved, already-posted document. The Secretary keeps a running note of any such corrections in the Master Document Register (6-03) so a researcher years later can find both what the record says now and that it was once corrected.

Sign-in sheets exist for one purpose — proving attendance and quorum for CPD compliance and the Council's own records — and are designed to collect the minimum needed for that purpose: name and, as an optional separate line, an email opt-in for the mailing list. They never collect phone numbers, home addresses, or other personal data with no compliance purpose, consistent with the Data Privacy Policy's minimization principle (Phase 5, 5-34). Original sign-in sheets go into the PAC Binder (6-01) after each meeting; a scanned copy goes into the Digital Governance Repository (6-02). Access to the underlying names/emails (as opposed to a public headcount reported in the minutes) is limited to the Secretary and Membership Lead, and the list is never shared with a sponsor, partner, or third party without the consent procedure in the Mailing List Consent / Subscription Record (Phase 9, 9-14).

Implements Bylaws Article 13, which caps any individual virtual/hybrid meeting at three consecutive occurrences before an in-person meeting is required. Before the meeting:

1. Platform decided and published. The platform, dial-in number, and any access code are included in the meeting notice (6-10) — not sent separately or only to those who ask, since that would create two tiers of access to the same public meeting.
2. Advance materials posted. Per current CPD guidance, the agenda and the prior meeting's approved minutes are made available at least three days before the virtual meeting takes place, and CPD staff are notified that the meeting will be held virtually so they can join or flag any concern in advance.
3. Access tested. The Technology Lead confirms the meeting link and any public dial-in number actually work at least a day ahead — discovering a broken link at meeting time defeats the entire purpose of publishing one.

During the meeting: remote attendees count toward quorum the same as in-person attendees and may vote using the platform's polling or hand-raise feature, with each vote logged in the minutes identically to an in-person vote (no notation distinguishing "remote yes" from "in-person yes"). The Chair confirms at the start that remote attendees can hear and be heard before gaveling into business. A technical failure affecting a material portion of the meeting — a dropped connection during a vote, an extended platform outage — is noted in the minutes with its duration and may trigger a re-vote at the next meeting if the Board determines the failure could have changed the outcome or excluded someone from a vote they were entitled to participate in. Any recording of a virtual or hybrid meeting follows the same consent procedure as an in-person meeting (Phase 5, 5-20) regardless of format — a virtual meeting is not treated as inherently "already recorded" just because it runs on a platform capable of recording.

A standing agenda item at every regular meeting, open to any member of the public (not just voting members) — this is the document that fulfills the Voluntary Open-Meeting Transparency Standard's (Phase 5, 5-16) "public-comment period appears on every regular agenda" commitment. Speakers sign up on arrival or are recognized in the order they raise a hand, in person or, for a virtual/hybrid meeting (6-14), through the platform's queue; each gets 2-3 minutes, with a total time cap for the whole comment period that the Chair may extend at their discretion if turnout warrants it. Anyone who cannot attend the meeting itself may submit a written comment to the Secretary by the day before the meeting; written comments are read into the record by the Secretary (or summarized by topic if several address the same point) with the same standing as a comment made in person.

Comments are heard respectfully and logged in the minutes by topic, not transcribed verbatim; the Board is not required to respond substantively in the moment, since public comment is for listening, not for immediate debate, but any comment raising something needing a real answer is followed up per the Public Contact & Response Service Standard (Phase 9, 9-30) within that policy's target response window, and the follow-up is noted against the original comment in the Issue & Escalation Log (6-20) if it isn't resolved same-day. The Chair may limit repetitive comments on the same point once it has clearly been made, and may ask a speaker to move to a private conversation if a comment concerns a specific personnel or safety matter better handled outside a public meeting — but may never exclude a viewpoint because the Board disagrees with it, and any such redirection is itself noted in the minutes so it isn't mistaken for suppression.

Reviewed as the first substantive item of every meeting, before new business — an item that's been open past its deadline is flagged out loud, not quietly rolled forward another month without comment. The Secretary maintains this tracker as a standing document, not something reconstructed from old minutes when someone asks "did we ever finish that?"

A chronological, numbered index of every formal Board/membership decision — separate from the minutes themselves so a later question ("did we actually vote on that, and when, and by what margin?") has a one-line answer instead of requiring a search through a year of meeting minutes. Numbered sequentially (2027-01, 2027-02, ...) so a resolution can be cited by number in later documents, contracts, or CPD correspondence without ambiguity.

Tracks material letters and emails with CPD, elected offices, funders, and partners — deliberately not routine day-to-day traffic (a scheduling email doesn't belong here), but anything that would matter to a future officer trying to reconstruct why a relationship stands where it does: the actual Letter of Intent correspondence (Phase 1, 1-04), a funder's written conditions on a grant, a partner's formal notice of a change in terms. The Secretary reviews open follow-ups from this register at the same cadence as the Action Item Tracker (6-16).

Every entry is phrased and logged as a referral to CPD, never as the Council itself performing the maintenance or safety work — consistent with the "Do Not Cross" boundary against directing CPD staff or substituting for CPD operations. This log doubles as the evidence trail if a referred issue drags on without resolution: a pattern of unresolved 311 referrals over several months is exactly the kind of concrete, documented finding worth raising directly with the Park Supervisor or Area Manager, rather than a vague complaint about "the park not being maintained."

Broader than the CPD Request/Referral Log (6-19) — tracks any unresolved community or operational issue at all, whether or not CPD involvement is expected (a community complaint about event noise, an internal committee capacity problem, a partner relationship that's stalled). Reviewed at every regular meeting so nothing sits unaddressed for months simply because no single document was tracking it and everyone assumed someone else had it.

A single combined calendar overlaying every recurring obligation the Council carries, so no two quietly collide: the Annual Meeting Calendar (6-09), beach season milestones (Memorial Day through Labor Day lifeguard coverage, the June-September Beach House event season), stewardship workdays, planned events, election timing (annually, per Phase 3), filing deadlines (the Master Legal & Regulatory Compliance Matrix, Phase 5, 5-01, and the Annual Filing Calendar Template, Phase 11, 11-97), and the budget cycle (Phase 4). Built and published each January alongside the Annual Meeting Calendar, and revisited at every regular meeting as a standing check for anything coming up in the next 60 days.

A practical, plain-language companion to the Bylaws and Officer Position Descriptions (Phase 3, 3-01), written for someone who has never served on a nonprofit board before — the Bylaws state the rule, this Handbook explains what actually doing the job looks like month to month. Covers, at minimum:

• What a Board report actually looks like. A committee report to the full Board is one page or less: what happened since the last meeting, any decision the Board needs to make (with a specific ask, not just an update), and any budget impact — not a narrative of every conversation the committee had.
• How an approval actually moves. Any spending, contract, or public commitment above an officer's individual authority follows the Delegation of Authority Matrix (Phase 2, 2-36) — the Handbook walks through two or three realistic examples (a $400 stewardship-supply purchase; a $3,000 event sponsorship) so a new officer can see which tier applies before making a costly assumption.
• Meeting cadence and preparation. What to actually do in the week before a regular meeting: submit agenda items by the Agenda Development Procedure's (6-11) deadline, review the prior draft minutes, check the Action Item Tracker (6-16) for anything assigned to you.
• Transitions. What "handing off the role" concretely means — see the Officer Transition Checklist (Phase 3, 3-28) and Digital Account & Credential Handover Record (Phase 3, 3-29) — walked through here in narrative form rather than just as a checklist to fill in blind.
• Where to go when something isn't covered. When a situation doesn't map cleanly onto any existing policy, the answer is to raise it with the President or the Governance Committee before acting unilaterally, not to guess.
• What "recognized" and "proposed" actually mean, day to day. Until Gate 0 resolves (Phase 0), the Council operates as a proposed body — new officers need this explained plainly, since it affects tone in every external conversation: enthusiastic about the vision, careful never to state as settled fact something CPD hasn't yet confirmed.
• The habit of writing things down. A decision made in a hallway conversation or a group text doesn't count until it's reflected in a motion, a minutes entry, or a resolution number (6-17) — new officers are walked through why this isn't bureaucratic caution for its own sake, but the difference between a decision the next officer can find and one that only lives in someone's memory.

New officers receive this Handbook, along with their specific Position Description (Phase 3, 3-01), before their first meeting in the role — not as onboarding paperwork to skim, but as the document they're expected to actually reference the first several times a real decision comes up. It is reviewed and updated whenever the Bylaws or Delegation of Authority Matrix change, so this Handbook never quietly drifts out of sync with the documents it's supposed to translate, and it is one of the specific items walked through in person during the Officer Transition Checklist (Phase 3, 3-28) rather than simply forwarded by email.

Companion to the Standing Committee Charter Set (Phase 2, 2-37) — the operating rules that apply across every committee regardless of subject, so each new chair isn't reinventing basic process:

• Requesting budget. A committee submits a written request to the Treasurer at least two weeks before the meeting where budget approval is needed, stating amount, purpose, and which line of the Annual Operating Budget (Phase 4, 4-12) it falls under.
• Reporting to the Board. Every standing committee reports at every regular meeting, even if the report is "no update this month" — silence from a committee for multiple consecutive meetings is itself a signal the Governance Committee should follow up on.
• Bringing in outside volunteers. A committee may recruit volunteers for its own work but cannot commit the Council to an ongoing partnership, sponsorship, or contract without Board approval under the Delegation of Authority Matrix (Phase 2, 2-36).
• Membership and quorum. Each committee's charter states its own membership size and quorum for internal votes; absent a charter provision, a committee acts by majority of its current members.
• Sunset review. Every committee's charter and continued existence is revisited on the schedule set in the Policy Sunset / Periodic Review Schedule (6-36) — a committee doesn't survive by default just because no one raised the question.
• Chair vacancy. If a committee chair resigns or becomes unavailable mid-term, the committee's remaining members recommend an interim chair to the President within two meetings rather than continuing indefinitely without one — a committee with no chair tends to quietly stop reporting, which is exactly the gap the reporting rule above exists to catch.

This Handbook is deliberately a companion, not a replacement, for each committee's own Charter (Phase 2, 2-37) — the Charter states what a specific committee exists to do; this document states how any committee, regardless of subject, actually runs day to day. A new chair reads both before their first meeting leading the committee.

The single document every volunteer actually reads before a workday or event shift. Organized around the questions a first-time volunteer actually has:

• "Which form do I need?" There is no single generic "CPD Volunteer Application" — the right one depends on the role. Officers, anyone handling Council finances, and anyone working with youth complete the Long Term Adult Volunteer Application and a CPD background check before starting (Phase 1, 1-27 through 1-29). Volunteers 16 and younger complete the Long Term Minor Volunteer Application. A single-day helper at one event or workday, with no finance/youth responsibility, completes only the shorter one-day Volunteer Waiver and Release before that shift.
• "What am I actually allowed to do?" Volunteer tasks are always support tasks: setup, check-in, cleanup, handing out information, staffing a table, walking a stewardship crew through an authorized task. Volunteers never direct CPD staff or lifeguards, never perform a rescue or medical response unless separately certified and acting under an authorized program, and never do habitat work (planting, removal, signage) without the specific written CPD authorization referenced in Phase 7. When in doubt, the answer is to ask the shift lead, not to guess and proceed.
• "How do I check in and out?" Sign in with the shift lead at arrival (name, time, role) and sign out at departure — the same sign-in principle as Council meetings (6-13): only what's needed to confirm who was present and for how long.
• "What if something goes wrong?" Any injury, hazard, or safety concern is reported immediately using the Incident Reporting & Escalation SOP (6-30) — call 911 or CPD/311 as the situation requires, then tell the shift lead; volunteers never handle the fix themselves.
• "What's expected of my conduct?" The Supplemental Member Code of Conduct (Phase 5, 5-25) and CPD's own Park Advisory Council Code of Conduct and Facility Users Code of Conduct all apply to volunteer shifts, not just to officers at meetings.
• "Does this count for anything?" Volunteer hours are tracked (6-26) and recognized under the Volunteer Recognition Policy (Phase 8, 8-36) — service is noted, not assumed unrecorded.

New volunteers complete the orientation in 6-25 before their first shift; this Handbook is the reference they keep afterward.

Short (20-30 minute) modules delivered before a volunteer's first shift, always in the same order so nothing gets skipped when time is tight:

1. Who the Council is and isn't. The CPD/PAC independence boundary, stated plainly, so a new volunteer never accidentally represents themselves as CPD staff or gives the impression the Council speaks for CPD.
2. Basic beach safety awareness. Where lifeguards are stationed, what the flag colors mean, and who to call for what — covered even for roles that never go near the water, since every volunteer should be able to point someone in the right direction if asked.
3. Natural-area rules, for any role touching the dunes (Phase 7) — what's authorized stewardship activity and what requires separate CPD sign-off.
4. The specific tasks for that day's role, walked through concretely rather than described in the abstract — what "staffing the check-in table" actually involves, step by step.
5. Code of Conduct expectations (Phase 5, 5-25), including that CPD's own Park Advisory Council Code of Conduct and Facility Users Code of Conduct apply to volunteers too, not just officers.
6. How to escalate an incident (6-30) — the one thing every volunteer needs to know cold before anything else, since it's the module most likely to matter under pressure.

Delivered in person for event-day crews, by short video for recurring roles, or as a written packet when neither is practical — the content covered matters more than the delivery format. A volunteer who completes the video or written version is asked three or four plain confirmation questions afterward (not a formal exam, just enough to confirm the material landed) before being logged as oriented in the Volunteer Training / Certification Log (6-26). Recurring volunteers refresh module 6 (incident escalation) and any module tied to a policy that's changed since their last orientation at the start of each new season, rather than relying on training from a prior year.

Maintained confidentially by the Volunteer Coordinator — this log confirms someone is cleared for a role and which volunteer track they're on; it deliberately does not store the actual background-check report contents (Phase 1, 1-28 covers that distinction and why it matters: a status log is not the same record as the sensitive report behind it). Checked before assigning anyone to a finance- or youth-facing role, since those specifically require the Long Term Adult track regardless of how minor the task seems.

Defines what Council volunteers actually do during severe weather, an injury, a missing person, or a major event disruption — and, just as importantly, what they don't. Every scenario below follows the same controlling principle: this plan is explicitly subordinate to CPD staff and 911/public-safety authority at every point; Council volunteers support communication, they never substitute for a lifeguard, medical responder, or CPD employee.

• Severe weather. When CPD/NWS conditions trigger a warning (Phase 7, 7-26's Severe Weather Beach Activity Protocol), the Event Lead or on-duty officer directs attendees toward posted CPD shelter guidance and pauses or ends the activity — volunteers do not make an independent call to continue an event against posted conditions.
• Injury. A volunteer who witnesses an injury calls 911 for anything beyond minor first aid, notifies the nearest lifeguard or CPD staff if the injury is water- or beach-related, and stays with the person only to provide comfort and information to responders — not to render medical care beyond basic first aid unless separately certified.
• Missing person. Handled per the Lost Person / Lost Child Escalation Protocol (6-31) — immediate notification to lifeguards/CPD/911 first, volunteer search support only as directed by responders.
• Major event disruption (crowd issue, equipment failure, unauthorized disturbance). The Event Lead assesses whether the event can safely continue, escalates to CPD staff or 911 if there's any safety concern, and communicates any pause or cancellation to attendees using the Emergency / Safety Post Approval Protocol (Phase 9, 9-19) for any public-facing message.
• Beach House / facility failure (power outage, plumbing failure, a locked-out restroom during an event). The Event Lead notifies CPD facilities staff immediately through the on-site contact or 311, adjusts the event plan around the affected space rather than waiting for a fix mid-event, and notes the failure in the CPD Request / Referral Log (Phase 6, 6-19) so a pattern of recurring facility issues is visible over time.

Every use of this plan — regardless of scenario — is followed by a short after-action note in the Incident Reporting & Escalation SOP (6-30): what happened, what the Council did, and whether the response actually matched what this plan describes. A gap between the two (the plan said X, but in the moment people did Y) is a signal to revise the plan, not evidence the plan failed — plans are living documents that improve from real use. This plan is reviewed and walked through with volunteer leads before every event of meaningful scale (Phase 8), not filed away and assumed remembered from the prior season.

Governance-level response to a serious crisis that isn't a physical-safety emergency: a financial irregularity, a leadership scandal, a data breach (Phase 5, 5-38), or a reputational incident. Unlike the Emergency Operations Plan (6-27), which handles what happens at the beach in the moment, this plan handles what the Board does in the hours and days after.

1. Convene. The President (or, if the President is implicated or unavailable, the Vice President) convenes an emergency Board meeting within 48 hours of the crisis becoming known, using the Virtual/Hybrid Meeting SOP (6-14) if an in-person meeting can't be arranged that fast.
2. Contain and preserve. Before any public statement, the Board directs preservation of relevant records (Legal Hold Procedure, Phase 5, 5-12) and, for a suspected financial irregularity, immediate suspension of the individual's signing/spending authority pending review (Phase 4's internal controls).
3. Decide who speaks. Only the President or a Board-designated spokesperson communicates publicly during the crisis, per the Media Relations / Spokesperson Policy (Phase 9, 9-16) — no officer freelances a public statement, even a well-intentioned one.
4. Decide when to bring in Counsel or notify CPD. Any crisis involving suspected fraud, a legal claim, or a matter CPD's Code of Conduct requires reporting is escalated to qualified counsel and to CPD's Department of Legislative and Community Affairs promptly — not held internally in hopes it resolves quietly.
5. Debrief. Once resolved, the Board conducts a written after-action review: what happened, what the response got right or wrong, and what changes to policy or practice follow — filed with the Compliance Exception / Corrective Action Log (Phase 5, 5-49).

Two situations get special handling. If the crisis involves a sitting officer as the subject of the concern, that officer is excluded from Step 1's convening and from any vote on their own suspension, per the same disinterested-officer principle used in the Complaint Intake procedure (Phase 5, 5-46). If the crisis becomes publicly visible before the Board can convene — a social media post, a press inquiry, a community rumor already circulating — the acting spokesperson may issue a single narrow holding statement ("the Board is aware and is looking into this; we will share more once we have accurate information to share") before the full process below runs, specifically to avoid the appearance of silence being read as either guilt or indifference, without getting ahead of facts the Board hasn't yet confirmed.

If the Council loses access to its primary records, bank, or leadership (illness, sudden resignation, a cyber incident) all at once, this plan says exactly who has emergency access to what, so recovery doesn't depend on improvising under pressure:

• Records access. At least two officers (never one) hold recovery access to the Digital Governance Repository (6-02), per the Digital Access / Credential Management Policy (Phase 5, 5-37) — no single point of failure on institutional records.
• Financial access. The bank account signatory chain (Phase 4, 4-08) always names at least two authorized signers, so a single officer's unavailability never freezes the Council's ability to pay an obligation or access funds.
• Minimum viable operations. If a majority of officers become unavailable simultaneously, the surviving officer(s) and the Governance Committee convene within two weeks to appoint interim replacements per the Vacancy Appointment / Special Election Packet (Phase 3, 3-25), rather than letting meetings and filings lapse indefinitely.
• Communications continuity. Institutional social media and email accounts remain accessible via the credential-recovery contacts named in the Digital Account & Credential Handover Record (Phase 3, 3-29), not tied to any one departed officer's personal recovery email or phone.
• Vendor and insurance continuity. The Contract & MOU Register (6-34) and Insurance Certificate / Permit Register (6-35) each name a secondary contact besides the primary owner, so an active vendor relationship or insurance renewal doesn't silently lapse because the one officer who normally handles it is unreachable.

Tested annually via a tabletop walkthrough — "what would we actually do if the Treasurer and Secretary both left tomorrow" is the standard scenario, rotated with a second scenario (a sudden loss of repository access, or an extended illness affecting the President) so the test doesn't just rehearse the same answer every year. Gaps found during the walkthrough are logged in the Compliance Exception / Corrective Action Log (Phase 5, 5-49) with a named owner and target date, the same as any other identified compliance gap — a continuity plan that's never been stress-tested is a plan the Council is only hoping works.

Any volunteer or officer who observes a safety hazard, injury, or incident follows the same sequence, every time:

1. Call first, document second. 911 for any emergency (injury, water rescue, missing person, fire); CPD or 311 for a non-emergency facility issue (damaged equipment, a safety hazard that isn't actively harming someone); the on-duty lifeguard directly for a water-safety concern. The call happens before anything else — do not stop to write notes while something urgent is unfolding.
2. Stay within your role. Never attempt a fix, rescue, or repair yourself unless you are specifically trained and currently authorized for that exact task (a certified lifeguard volunteering through an authorized CPD program, not through the Council, is the only case where a "volunteer" might render aid, and even then under that program's authority, not the Council's).
3. Document after the fact. Once the immediate situation is handled by the appropriate authority, complete the Incident Report Form (Phase 11, 11-55): what was observed, who was called, when, and the outcome.
4. Notify the Risk Lead within 24 hours for any incident involving injury, a near-miss, or property damage, even if it was fully resolved on-site — pattern-spotting across many small incidents is often how a real hazard gets caught before it causes a serious one.

Incidents are classified by severity when logged, since the response to a scraped knee and the response to a water rescue shouldn't look the same on paper: Minor (no injury or a first-aid-level injury, no property damage beyond routine wear) is logged and reviewed at the next quarterly cycle; Moderate (an injury requiring care beyond basic first aid, a near-miss with real potential for harm, meaningful property damage) triggers Risk Lead notification within 24 hours as above and a review at the next regular meeting rather than waiting for the quarterly cycle; Severe (any injury requiring emergency response, a missing person, or anything triggering the Emergency Operations Plan, 6-27) triggers same-day notification to the President in addition to the Risk Lead, and is reviewed at a specially called session if the next regular meeting is more than two weeks away.

Reported incidents are logged and reviewed at least quarterly by the Risk Lead against the Enterprise / PAC Risk Register (Phase 5, 5-43) — a rising count of Moderate incidents in one category (e.g., repeated minor injuries at one specific activity) is treated as a signal to revisit that activity's own safety plan, not just logged and left for the next review cycle to notice on its own.

For a missing child specifically, the sequence is non-negotiable and does not wait to see if the child turns up on their own:

1. Call 911 immediately. Not after a few minutes of looking around — immediately, every time, without exception for a reported missing child.
2. Notify the nearest lifeguard and CPD staff in the same breath, since a beach setting means water is always a possibility.
3. Support the search only as directed by responders — spreading an accurate description, watching a specific assigned area, helping keep the family calm and informed — never launching an independent, undirected search that could waste responder time cross-checking who's already covered what area, or that pulls a volunteer's attention away from other event responsibilities.
4. Stay with the family if one volunteer can be spared for it, as the point of continuous contact and reassurance while official responders work.

For a missing adult (no immediate danger indicators), the same escalation order applies but with slightly more room for judgment — lifeguards/CPD/911 are still notified promptly, especially if water involvement is possible, and if the adult is a known vulnerable individual (a person with dementia, a young teenager separated from a group) the response defaults to the child-level urgency rather than the more measured adult default.

Once the person is found or responders take over the search, the volunteer or officer who first raised the alarm completes the Incident Report Form (Phase 11, 11-55) the same day per the Incident Reporting & Escalation SOP (6-30), logged as Severe regardless of outcome — even a quick, happily-resolved case is reviewed, since the point is confirming the protocol actually worked as designed, not just that the story ended well. This protocol is walked through out loud with all event-day volunteers before any event with meaningful attendance, not just handed out as a page to read, and is re-walked-through at the start of each new beach season even for returning volunteers.

Found property is turned over to CPD staff or the Beach House front desk the same day it's found, not held informally by a volunteer "just in case someone comes back for it." A brief note is made in the Issue & Escalation Log (6-20) only if the item is high-value or the finder needs a record of the handoff — routine items (a towel, sunglasses, a toy) don't need individual documentation. This simple rule avoids both liability (the Council is not equipped to secure or verify ownership of found property) and the appearance of the Council operating an unofficial, unregulated lost-and-found alongside CPD's own.

Opened the moment a vendor or partner relationship is approved, not backfilled after invoices start arriving — a missing document in this list (most commonly, an insurance certificate no one asked for until an event was already booked) is one of the most preventable gaps in nonprofit vendor management, and this standard exists specifically to catch it before the relationship starts, not after.

Every MOU, MOA, and contract the Council signs — from the templates in Phase 8 (8-28, 8-29) to vendor agreements (8-16) — gets one line here the day it's executed, not weeks later when someone remembers. Reviewed quarterly by the Secretary and Treasurer together so a contract never auto-renews or silently lapses by accident, and so an expiring insurance requirement is caught before an event depends on coverage that's no longer in force.

Central log so no event or partnership proceeds on a certificate of insurance that quietly expired the week before.

Assigns every adopted policy a review cycle based on risk: high-risk/fast-changing policies (cybersecurity, AI use, insurance) reviewed annually; moderate-risk policies (most operational SOPs) every 2 years; low-risk/stable policies (code of ethics, non-discrimination) every 3 years. Feeds directly into the Policy Register & Version History (Phase 2, 2-39) and the Annual Policy & Bylaw Review Report (Phase 10, 10-18).

The living answer to "why do we do it this way, and who do we actually call at CPD" — the institutional memory that otherwise walks out the door with whichever officer happens to be leaving. Built gradually over the Council's first year and updated at every officer transition, covering:

• Recurring relationships. Who the current Park Supervisor and Area Manager are, which CPD department handles which kind of issue (LCA for registration/complaints, the Planning Department for capital projects, the Aquatics Unit for beach/water questions), and how those relationships have actually behaved in practice, not just their formal roles.
• The reasoning behind past decisions. Not just what the Council decided, but why — a decision that looks arbitrary to a new officer two years later often made complete sense given a constraint (a CPD preference, a past incident, a scheduling conflict) that isn't otherwise written down anywhere.
• Open initiatives. Anything a past officer started that outlived their term — a partially-negotiated partnership, a stewardship idea CPD hadn't yet approved, a grant application in progress — logged clearly enough that the next person can pick it up instead of it quietly dying.
• Where things actually live. A short, current map of where each category of record actually lives — the PAC Binder (6-01), the Digital Governance Repository (6-02), this public library — since a new officer's first practical question is usually "where do I even find X," not a governance question at all.

Maintained as a single living document rather than a folder of disconnected notes, and specifically reviewed with an outgoing officer before they leave — the Officer Transition Checklist (Phase 3, 3-28) includes a dedicated step for adding to this Manual, not just handing over passwords and files. This is, in a real sense, what the entire Organization document library exists to prevent: the Council's actual working knowledge living only in one departing officer's head, discovered to be missing only after they're already gone.