Legal & Compliance

Every other compliance document in this library exists to satisfy a specific obligation with a specific legal or CPD source. Kept separately, those obligations tend to live in individual officers' heads — which is exactly how a nonprofit misses a filing: the person who knew about it stopped being Treasurer three years ago. This matrix is the single place all of them are listed together, cross-referenced to the document that actually implements each one, so continuity survives officer turnover.

Structure. Each row records: the obligation in plain language; its legal or CPD source (statute citation, CPD Guidelines section, or "Board policy" if self-imposed); the frequency or trigger; the responsible officer or committee; the document in this library that implements it; and the date it was last confirmed current. New rows are added the moment a new obligation is identified — during onboarding a new committee, signing a new type of contract, or reviewing this library itself — not batched for a future update.

Reviewed at least annually alongside the Year-End Records & Filing Closeout Checklist (Phase 10, 10-28), and cross-checked against the Annual Compliance Certification (5-48) each officer signs — any obligation the certification can't honestly confirm should already be a row here with a corrective-action owner, not a surprise discovered while filling out the certification.

A maintained link to the current text of the General Not For Profit Corporation Act of 1986 (805 ILCS 105), plus a short internal digest translating the sections that actually matter for this Council's size into plain language for officers who aren't lawyers and shouldn't have to parse a statute mid-meeting to know their own obligations. The digest is always explicitly subordinate to the statute's actual current text — it exists to make the Act more usable day-to-day, not to substitute for it if the two ever appear to conflict, and any apparent conflict is resolved by re-reading the statute (or asking Counsel), never by trusting the digest over the source.

Sections the digest should actually translate: director/officer fiduciary duties (care, loyalty, obedience) and how they differ from a general member's much lighter obligations; corporate member inspection rights and their limits (5-13); default meeting and notice rules the Bylaws can supplement but not undercut; the statutory amendment and dissolution procedures the Bylaws (Articles 29-30) were written to track; and what happens if this Council's Bylaws are ever silent on a point the Act addresses directly — the Act fills the gap, not informal practice.

Maintenance. The link and digest are checked against the Illinois General Assembly's own published text at least annually and immediately after any legislative session that amends Chapter 805; a digest section that no longer matches the current statute is corrected the same week the discrepancy is found, not queued for the next scheduled review. Where a specific governance question turns on a provision this digest doesn't yet translate — a novel officer-removal scenario, an unusual member-vote threshold — the Secretary flags the gap to Counsel rather than extrapolating from an adjacent section, and the answer, once settled, is added to the digest so the same question doesn't require Counsel's time twice.

The recurring state filing that keeps the corporation in good standing — due annually on a date tied to the anniversary of the original Articles filing (1-23), not the calendar or fiscal year, so the Treasurer's compliance calendar (Phase 6, 6-21) needs the Council's own specific due date, not a generic "sometime in the spring" placeholder. A lapsed filing here doesn't just risk state administrative dissolution; it also removes the very evidence (5-04) CPD's current guidance expects the Council to produce annually as proof of continuing not-for-profit status, which can put CPD recognition itself at risk on top of the corporate consequence.

Filed via the Secretary of State's current online system, with the filing fee paid from Council funds under normal disbursement authorization (Phase 4, 4-20). The Secretary prepares the filing at least 30 days before the due date so any required information (current officer list, registered agent) is confirmed accurate before submission, not corrected after a rejected filing. Confirmation of each year's filing is retained permanently in the Corporate Records Book (5-07), not just in whatever inbox received the confirmation email.

A missed due date is not treated as a minor administrative slip: Illinois will administratively dissolve a corporation that lapses on this filing for the statutory period, which would in turn invalidate the Certificate of Good Standing (5-04), jeopardize the bank account's standing documentation (Phase 4, 4-07), and hand CPD a legitimate basis to question the Council's continued recognition — none of which is recoverable quickly. For that reason the 30-day pre-filing checkpoint is itself logged on the Annual Operations Calendar (Phase 6, 6-21), and a missed checkpoint (not just a missed filing) is escalated to the President the same week, so a second officer is watching the deadline before it actually arrives.

Ordered from the Secretary of State (fee applies) whenever a bank, funder, partner, or CPD itself asks for current proof of good standing — verified at least annually even absent a specific request, since discovering a lapse only when someone asks is the worst possible time to find out. The Certificate itself is only ever as current as the last Annual Report (5-03) actually filed; ordering one does not fix a lapsed filing, it just documents that the lapse exists.

Kept on hand (a recent copy, not necessarily a brand-new order every time) for three recurring uses: opening or maintaining the Council's bank account (Phase 4, 4-07), responding to a grant or fiscal-sponsorship application that asks for proof of good standing, and satisfying CPD's own annual evidence requirement under the current PAC Guidelines. A copy accompanies the Annual CPD PAC Report (10-03) each year as supporting documentation.

Filed with the Secretary of State the same week the registered agent or registered office (Phase 1, 1-24) actually changes — a stale registered agent means the Council may never receive service of process, state correspondence, or notice of an administrative dissolution proceeding, so this is not a filing to defer until "the next batch of paperwork." A registered agent who is a departing officer or a volunteer's home address that's about to change is itself a trigger to review this filing proactively, not just react to it after the fact.

Every registered-agent change is logged in the Authorized Signer-adjacent institutional-contacts record (Phase 4, 4-08's counterpart for non-financial contacts) so the Secretary always knows who the current agent is without having to look it up at the Secretary of State's site under time pressure.

Conditional — activated only if the Council's legal name, corporate purpose clause, or another Articles provision changes after initial incorporation (Phase 1, 1-22). Common triggers: Gate 0 resolving in a way that changes the Council's legal name or scope (Phase 0), a decision to formally add "Bongo Beach PAC" as the Council's registered assumed name rather than an informal public-facing label, or a purpose-clause update the Board finds too narrow after a few years of actual operation.

The file holds, in sequence: the Board resolution proposing the amendment and its rationale; evidence of the member vote required to approve an Articles amendment under the Bylaws and Illinois law; the amendment as filed with the Secretary of State; the confirmation and updated file number; and a cross-reference to which Bylaws or other document text needs to be updated to match. Retained permanently in the Corporate Records Book (5-07) alongside the original Articles, never as a standalone loose document.

The permanent corporate archive — distinct from, and broader than, the CPD PAC Binder (Phase 6, 6-01), which is the in-park compliance file CPD itself inspects. This book holds the Articles and every amendment (1-22, 5-06), the Bylaws and every amendment (2-02, 11-20), every board and member meeting's approved minutes, every formal resolution and its vote record, the full officer/director history back to formation, every state filing (5-03 through 5-06), and every federal filing (4-03, 4-04, 4-54). Never destroyed under any retention schedule (5-10) — this file is permanent by definition, and its permanence is precisely why it's kept separate from the shorter-retention operational binder at the park.

Maintained in both a physical binder (kept at a secure Board-designated location, not necessarily the park) and the Digital Governance Repository (Phase 6, 6-02), with the digital copy treated as the working reference and the physical originals as the authoritative record where the two would ever differ — e.g., an original signature page. Custody transfers to the incoming Secretary at every officer transition (Phase 3, 3-28), confirmed by a signed handover checklist, not a verbal "it's all in the drive somewhere."

The statutory record of who actually holds voting-member rights under Bylaws Articles 5-6 — a narrower and more sensitive list than the public Leadership Roster (Phase 3, 3-07) or the free community "Friends of Bongo Beach" signup, and never published or shared outside what Illinois member-inspection rights (5-13) actually require. Each entry records: name, contact information, date admitted to voting membership, Chicago-residency status (since that determines full-voting eligibility under Bylaws Article 5), and good-standing status.

Maintained by the Secretary and updated at the point a Membership Application (1-09) is approved and again whenever a member's good-standing status changes (suspension, termination for cause, or restoration). This roster, not the free community list, is the authoritative record used to determine quorum (Bylaws Article 14) and voting eligibility at any given meeting — a name on the public "Friends of Bongo Beach" list confers no rights under this roster unless the person has also separately completed the Membership Application process.

Implements Bylaws Article 19. Sets the floor at current CPD guidance's five-year minimum for ordinary PAC materials, but goes longer where other law requires it: corporate records (5-07) and tax-exemption records (4-04) are permanent; signed contracts are retained for the contract term plus the applicable statute-of-limitations period; incident/complaint files (5-47) are retained longer given potential future liability relevance. No record is destroyed while a Legal Hold (5-12) is active, regardless of what the schedule (5-10) would otherwise allow.

Governing principles. First, retain no less than any applicable law or CPD requirement demands — this policy is a floor, and an officer's personal judgment that "we probably don't need this anymore" never overrides a stated retention period. Second, retain no more than necessary once the applicable period lapses, particularly for records containing personal data (5-34): indefinite retention of old membership applications or donor contact information is itself a privacy risk, not a safety margin. Third, when in doubt about which category a record falls into, or when a record could plausibly belong to more than one category with different periods, apply the longer period rather than guessing short.

Roles. The Secretary (assisted by a designated Records Officer where the Board appoints one) owns this policy's day-to-day application; the annual archive process (Phase 6, 6-06) is the recurring checkpoint where records due for destruction are actually identified, checked against any active Legal Hold, and logged (5-11) before disposal. This policy is reviewed at least every two years, or immediately if CPD's own retention guidance changes.

Format-neutral. The retention obligation attaches to the record's content, not its format — a scanned copy of a paper original satisfies retention only where the original signature or physical artifact isn't itself the thing being preserved (an executed contract's wet-ink signature page, for example, stays in the Corporate Records Book (5-07) even after scanning). Digital records are retained in a format the Council can still actually open and read for the full retention period, which means the Digital Governance Repository (Phase 6, 6-02) migrates file formats proactively rather than discovering a decade-old file is unreadable only when someone needs it.

The actual category-by-category table implementing 5-09. "Permanent" means never destroyed under this schedule; every other period runs from the record's creation date or the closeout/resolution date noted, whichever the category specifies:

Reviewed and, where needed, amended by the Governance Committee whenever a new record type is created that doesn't cleanly fit an existing row — the schedule is meant to have no gaps, not to be treated as exhaustive on day one.

Completed for every destruction event, however small — this log is itself the evidence that destruction followed the policy rather than happening ad hoc. No record is logged as destroyed until a second person (not the one performing the destruction) has confirmed the Legal Hold check; for digital records, "destroyed" means unrecoverable, not moved to a trash folder that auto-empties in 30 days.

The moment litigation, a formal complaint (5-46), an audit, a CPD compliance inquiry, or any other claim is reasonably anticipated — not necessarily filed, just reasonably foreseeable — the President or Records Officer issues a written hold notice identifying the affected record categories, the reason for the hold, and every person who needs to preserve records in their custody. The Records Retention Schedule (5-10) is suspended for those categories immediately upon notice, regardless of whether a scheduled destruction date has already arrived.

Why this is a one-person trigger, not a committee decision. A hold has to be issuable the moment someone reasonably anticipates a claim — often before there's time or need to convene the Board — so any officer with actual knowledge of a triggering event can issue it unilaterally, and the full Board is notified afterward. Lifting a hold is the opposite: it requires either Counsel's written confirmation the underlying matter has fully resolved, or a Board vote if no counsel is engaged, because prematurely lifting a hold destroys evidence in a way that can never be undone. Everyone named in the hold notice acknowledges receipt in writing; the hold and its eventual release are both logged in the Corporate Records Book (5-07).

What "preserve" requires in practice. A hold notice is not satisfied by simply telling people not to delete anything — it specifically suspends any auto-delete rule on email, cloud storage, or messaging platforms for the named custodians, since a routine 90-day auto-purge on a shared inbox destroys evidence just as effectively as someone deleting it on purpose. The Technology Lead is looped in on every hold notice for exactly this reason: they, not the President or Records Officer, know which systems have an auto-delete rule that needs to be paused. A custodian who leaves the Council while a hold naming them is active hands off their preservation obligation explicitly, in writing, to their successor or to the Records Officer — it does not simply lapse when the person's role ends.

Illinois nonprofit law gives corporate members (as distinct from general "Friends of Bongo Beach" community members — see the Corporate Member Roster, 5-08) a statutory right to inspect certain corporate books and records for a proper purpose reasonably related to their interest as a member. This is a narrower, more specific right than the Voluntary Transparency Standard's (5-16) general openness — it can compel access to records the Council might not otherwise proactively publish, subject to statutory limits.

Process: a requesting member submits a written request identifying the records sought and the proper purpose; the Secretary acknowledges within 5 business days; for any request beyond routine minutes/financial-summary access, the Secretary consults Counsel before responding, since improperly withholding a valid request and improperly disclosing more than the statute requires are both real risks. The response either provides the records, provides them with a legally-justified redaction and a written explanation of what was withheld and why, or explains a legally-justified basis for declining — a bare "no" without a stated statutory basis is not an acceptable response. Every request and response is retained per the Retention Schedule (5-10), and any pattern of similar requests is a signal the underlying information should probably just be published proactively under 5-16 instead.

Distinguishing this from the general public procedure. A corporate voting member (5-08) invoking this statutory right is not the same as a member of the general public submitting a request under the FOIA-informed procedure (5-18) — the member's request draws on a specific legal entitlement with its own notice period and disclosure standard, and mislabeling one as the other risks applying the wrong response timeline or the wrong disclosure standard to a request that deserved the stricter one. Whichever officer first receives a records request confirms which category it actually falls into — asking the requester directly whether they're a voting member exercising this right, if it isn't already clear — before routing it, rather than guessing from the tone of the request.

A quarterly self-audit of the physical, in-park PAC Binder (Phase 6, 6-01) against current CPD requirements: current agendas and approved minutes, financial reports (4-14), sign-in/attendance records, current Bylaws and NFP status evidence (5-04), and the current CPD Code of Conduct (1-02). A binder that's missing any of these is the single most visible compliance gap a CPD site visit could find, and the easiest to prevent with a recurring checklist.

Completed by the Secretary, ideally with a second officer confirming, and the completed checklist itself is filed in the binder as evidence the self-audit happened — a binder that looks complete because no one checked it recently isn't actually verified compliant.

The correct position, and the one this Council adopts: OMA does not legally apply to this Council under current CPD guidance, so no OMA-specific notice period, closed-session rule, or minutes-publication timeline is legally mandatory here. Instead, the Council adopts a voluntary transparency standard (5-16) that in practice meets or exceeds what OMA would require of a covered public body — because good governance, not a statute, is the reason for doing it. This memorandum should be re-checked any time Illinois OMA is amended or CPD revises its PAC Guidelines on this point (see the Version-Control Notes in the source master checklist).

Why this matters in practice, not just on paper. Getting this backwards in either direction causes a real problem. Claiming OMA coverage the Council doesn't have would mean advertising legal protections and obligations (like a formal closed-session exception process) that don't actually exist and that a member of the public could reasonably rely on — a misrepresentation, however unintentional. Assuming no transparency law applies means "no transparency at all" would technically be defensible, which is not the kind of organization this Council intends to be and would badly undercut its credibility with CPD, JPAC, and the community it exists to represent. This memorandum is reviewed by the Governance Committee at least annually and the moment any officer becomes aware of a change in CPD's guidance or Illinois law on this point, and the finding — whatever it is — is reflected consistently across this entire document library, not just here.

Where this gets asked, and how it's answered. The most common context this comes up is a member of the public or a prospective sponsor asking why a meeting wasn't preceded by an OMA-length statutory notice, or why a particular topic was discussed in an informal session — the correct answer states plainly that OMA doesn't apply here under current CPD guidance and directs the questioner to the voluntary standard (5-16) the Council follows instead, never a vague "we don't have to" that sounds evasive rather than accurate. Any officer fielding this question who is unsure how to phrase it consults this memorandum directly rather than improvising an answer, since an imprecise answer here is exactly the kind of mis-statement this memorandum exists to prevent.

Because 5-15 establishes OMA doesn't legally apply, this standard is what the Council actually commits to instead — voluntarily, and describable to CPD, members, and the public as exactly that: a voluntary practice, never as a statutory OMA compliance claim. In practice: meetings are open to the public per Bylaws Article 12; the annual meeting calendar (Phase 6, 6-09) is published in advance; agendas are posted per the current CPD notice requirement (Phase 6, 6-10); minutes are drafted, approved, and posted (Phase 6, 6-12) within a set number of days after each meeting; and a public-comment period (Phase 6, 6-15) appears on every regular agenda. This standard is reviewed annually and may be strengthened, but should never be described using OMA's own statutory vocabulary ("closed session," "OMA-compliant") since that vocabulary doesn't actually apply here.

What the Council commits to beyond the bare minimum: meeting materials posted online (not only at the field house) wherever practical, so distance or mobility isn't a barrier to knowing what's on the agenda; a standing invitation for anyone, member or not, to attend and observe any regular meeting; and draft minutes available for informal comment before formal Board approval, catching errors while memories are fresh rather than only at the next meeting. None of this is legally required — it's adopted because a community advisory body that's harder to observe than the statute would require of a covered public body has no real claim to represent that community.

What can still be handled privately, and how that's disclosed. Because this standard is voluntary rather than statutory, the Council may reasonably discuss certain matters — an individual volunteer's disciplinary situation, active legal-hold material (5-12), a specific donor's financial circumstances — outside the open portion of a meeting without invoking any formal "closed session" mechanism, since that mechanism doesn't legally exist here. Even so, the fact that a private discussion occurred (not its substance) is noted in the minutes, and the standing default is toward the open portion of the meeting unless there's a genuine, describable reason not to — "the Board would rather discuss this privately" is not itself a sufficient reason under this standard.

Pending that determination, this memorandum records the working position: FOIA status is unresolved, counsel should be consulted before either asserting or denying FOIA coverage in response to a specific request, and — regardless of the eventual legal answer — the Council commits to the FOIA-informed voluntary practice in 5-18 so that "we're not sure if FOIA applies" never functions as an excuse to be less transparent than a covered public body would have to be. Re-evaluate this memorandum whenever the corporate structure, CPD relationship, or applicable case law changes.

Practical handling of an actual FOIA-citing request. If someone submits a request explicitly invoking FOIA, the response acknowledges the request in writing within a reasonable time, does not concede or deny FOIA jurisdiction as a legal matter, and processes the substantive request through the voluntary procedure (5-18) on essentially the same timeline a statutory response would require — so the requester gets a real answer either way, and the unresolved jurisdictional question doesn't become the requester's problem to litigate. Any request that appears likely to escalate into an actual dispute over FOIA coverage is routed to Counsel immediately rather than answered informally by whichever officer received it.

What could change this determination. The factors this memorandum names as unresolved — the final corporate/CPD-relationship structure, the degree of any CPD funding or delegated authority, and how comparable volunteer advisory bodies have fared in Illinois courts — are not abstract; each has a concrete decision point elsewhere in this library that could shift the answer. The fiscal-structure decision (Phase 4, 4-01) and the eventual Gate 0 (Phase 0) determination are the two most likely triggers for re-evaluation, and either one is a mandatory trigger for the Governance Committee and Counsel to revisit this memorandum, not merely an optional prompt to reconsider it eventually.

A simple public-facing intake (Phase 11, 11-48) that borrows FOIA's structure — written request, defined response window (this Council targets a substantive written response within 5 business days, mirroring the actual Illinois FOIA non-commercial-request timeline without claiming it legally applies here, with one possible additional 5-business-day extension for a genuinely complex request — mirroring FOIA's own extension provision, not an open-ended delay), and a short written response identifying what's being provided and what's being withheld and why — without claiming this is a statutory FOIA response. Requests touching genuinely sensitive categories (individual donor identities, minors' information, active legal-hold material, ongoing complaint files) may be narrowed or declined with a written explanation; routine requests for agendas, approved minutes, or financial summaries should essentially never be declined.

The Records Officer is the single point of intake so requests don't get answered inconsistently by whichever officer happens to receive one, and every request is logged (5-19) regardless of how it arrived — email, in person, or through the website. A denial (partial or full) is always accompanied by the specific reason, not a form rejection, and the requester is told they may appeal to the Board if they believe the denial was improper.

Appeal. An appeal of a denial goes to the full Board at its next regular meeting (or sooner, by special meeting, if the underlying request is time-sensitive), with the Records Officer's original reasoning and the requester's appeal both presented; the Board's decision on appeal is the Council's final word on that request and is communicated to the requester in writing with the reasoning stated, not just the outcome. A pattern of appeals succeeding against the same category of denial is itself a signal this procedure's declination criteria need Governance Committee review, not just a signal about that one Records Officer's judgment.

Reviewed quarterly by the Records Officer for response-time patterns — a rising number of overdue responses is an early signal the intake process needs more capacity or a clearer owner, not something to notice only when a requester complains.

Implements Bylaws Article 19's recording-consent clause and current CPD guidance: any proposed audio/video recording of a meeting is announced at the start of the meeting, and if any attendee objects, the recording does not proceed (or is stopped for that portion of the meeting). No recording is made surreptitiously under any circumstance, by an officer or anyone else present, and any Council member who becomes aware of a surreptitious recording reports it to the President immediately.

The announcement happens whether or not anyone actually intends to object — silence isn't treated as consent by omission, the Chair asks directly and waits for a response before proceeding. If a recording is already underway when a late-arriving attendee objects, it stops immediately for the remainder of that meeting; it does not need to be deleted retroactively unless the objecting party specifically requests it and the Board agrees. Objections, the point in the meeting they occurred, and the resulting outcome are all noted in the minutes so there's a record of how the consent process actually worked, not just that a recording exists.

A recording that is made with consent is treated as a Council record subject to the same Retention Schedule (5-10) and Data Privacy Policy (5-34) as any other — it is not kept indefinitely by default, is not shared publicly beyond what the Voluntary Transparency Standard (5-16) already commits to for minutes, and is accessible only to the officers who need it to prepare accurate minutes. A recording is never used as a substitute for approved written minutes, which remain the Council's official record of what occurred regardless of whether audio or video also exists.

Standard agenda line, read aloud by the Chair at the start of any meeting where recording is contemplated, not just printed and left for attendees to notice on their own: "This meeting may be recorded for minute-taking purposes. Please notify the Chair now if you object." Used whether or not anyone actually objects, so the offer-and-consent step is documented either way. For virtual meetings (Bylaws Article 13), the same statement is read at the start of the call and repeated in the chat/notes for anyone who joined a moment late.

Implements Bylaws Article 18 in operational detail. Requires written disclosure (Phase 3, 3-12) of any financial, family, or business interest that could reasonably affect an officer's or director's judgment on a Council matter; requires recusal from discussion and voting (not just voting) on any matter where a disclosed interest exists; requires the recusal itself to be recorded in the minutes (3-13); and applies without exception regardless of how small the transaction or how well-intentioned the interested party.

What counts as a conflict, concretely: a vendor contract where an officer or their immediate family owns or works for the vendor; a sponsorship decision involving a company an officer has a financial stake in; a hiring or contracting decision involving a friend or relative; and any situation where a reasonable outside observer, knowing all the facts, would question whether the officer's judgment was independent. The test is not whether the officer believes they can be objective — it's whether a reasonable person looking at the relationship would have doubts, and the policy errs toward over-disclosure rather than under-disclosure.

Process when a conflict surfaces mid-meeting (not caught by the annual disclosure): the officer states the conflict aloud as soon as they recognize it, leaves the discussion (not just abstains from the vote), and the Secretary records the disclosure, the departure, and the vote outcome without that officer present. A pattern of late-recognized conflicts on similar matters is itself something the Governance Committee should review — it may mean the annual disclosure process (3-12) needs a broader prompt, not that officers are acting in bad faith.

Enforcement. An officer who fails to disclose a conflict they reasonably should have recognized, or who participates in a discussion or vote after disclosing, is not automatically removed — the Governance Committee first assesses whether the failure was inadvertent (correctable through a reminder and a revote if the outcome could have been affected) or willful (a Code of Conduct matter routed to the Removal / Recall procedure, Phase 3, 3-27). Any vote taken in violation of this policy is voidable at the Board's discretion and, where the interested officer's presence or vote could plausibly have changed the outcome, is retaken without them.

Any contract or transaction involving an officer, director, or their immediate family or business (a vendor contract with a board member's company, for example) requires: advance written disclosure, comparison against at least one arm's-length alternative or quote where feasible, approval by disinterested officers/directors only, and documentation of all of the above retained in the Corporate Records Book (5-07) — not merely a conflict disclosure on file, but an actual comparative record showing the terms were fair to the Council.

Approval threshold. A related-party transaction below the routine-expense threshold in the Delegation of Authority Matrix (Phase 2, 2-36) may be approved by the disinterested officers alone; anything above it requires the full disinterested Board, and any related-party transaction involving the President specifically is approved by the Vice President and the remaining disinterested officers, with the President excluded from the approval discussion entirely, not merely from the vote. If disinterested officers/directors would number fewer than a quorum after recusals, the matter is referred to Counsel before proceeding rather than approved by whoever happens to remain in the room.

Why an arm's-length comparison, not just disclosure, is required. Disclosure alone tells the Board a relationship exists; it says nothing about whether the actual terms are fair to the Council. A related-party vendor contract awarded without at least attempting a comparison quote can be entirely well-intentioned and still leave the Council paying more, or accepting worse terms, than an unrelated vendor would have offered — and a Council that can't show it checked is poorly positioned to rebut that appearance later, whether the question comes from a member, a funder, or CPD. Where a true arm's-length comparison genuinely isn't feasible (a uniquely qualified related-party vendor, an emergency repair with no time to solicit quotes), the file documents why not, rather than silently omitting the comparison.

A short values statement, not a rulebook (the rules live in the specific policies around it): integrity in financial and public representations; public service ahead of personal or organizational benefit; honest, sourced communication about beach conditions and CPD operations (never inventing or exaggerating either); impartial treatment of all community members regardless of how long they've been involved; and stewardship of both the beach and the Council's own resources as a public trust, not a private asset.

How this Code is actually used. It is read aloud (or its key points summarized) at every new-officer orientation (Phase 3, 3-11) alongside the CPD Code of Conduct and Facility Users Code of Conduct, so incoming officers understand the Council's own values framework, not only the compliance rules layered on top of it. It has no independent enforcement mechanism of its own — a violation of these values that also violates a specific policy (Conflict of Interest, Anti-Harassment, the CPD Codes) is addressed through that policy's actual process; this Code exists to explain the "why" behind those policies, not to create a second, vaguer disciplinary track alongside them.

Why a values statement is worth having separately. A rulebook alone can be followed to the letter while missing the point of it entirely — an officer who never technically violates the Conflict of Interest Policy but consistently steers small favors toward friends is a governance problem this Code names even though no single policy captures it. When a situation arises that no specific policy quite covers, the Board and Governance Committee use this Code as the first reference for "what would the right call look like here" before treating the gap as evidence a new policy is needed.

The current CPD PAC Code of Conduct (Phase 1, 1-02) is mandatory and controlling. It is not the only CPD conduct standard that applies: current CPD guidance separately requires compliance with a distinct "Facility Users Code of Conduct" — "PACs and PAC members shall comply with the Facility Users Code of Conduct and the Park Advisory Council Code of Conduct" — so members and officers are bound by both, not the PAC Code alone. This document only adds Council-specific expectations that don't conflict with either: respectful engagement with the longstanding beach drumming community and other cultural traditions (see Bylaws Article 24), no use of Council channels for personal business promotion, and a reminder that supplemental rules never override either CPD Code where they would conflict.

Additional Council-specific expectations: represent the Council's positions accurately and distinguish them clearly from personal opinions when speaking publicly, especially to media or elected officials (Phase 9, 9-16); disclose any outside role (employer, other board seat, elected office) that could be perceived as a conflict, even if it doesn't rise to a formal Conflict of Interest disclosure (5-22); treat fellow members, CPD staff, and the public with the same respect regardless of disagreement over Council decisions; and acknowledge in writing, at the point of joining and annually thereafter, having read both CPD Codes and this supplement — the acknowledgment itself is retained per the Retention Schedule (5-10) as evidence the expectation was actually communicated, not assumed.

Any officer, volunteer, or member may report a good-faith concern about financial mismanagement, governance failures, safety issues, or legal violations directly to the President, or to the Vice President if the concern involves the President, without fear of removal, exclusion, or informal retaliation. "Good faith" does not require the concern to turn out to be correct — it requires the reporter to reasonably believe it at the time, and being mistaken is not itself a basis for any adverse consequence.

Reports are logged confidentially (accessible only to the officers actually handling the matter) and referred to the full Board, except that if the concern involves a majority of the Board itself, it is escalated directly to CPD's Department of Legislative and Community Affairs or to Counsel rather than handled internally by the very body it concerns. Retaliation against a good-faith reporter — exclusion from activities, removal attempts, public discrediting, or any other adverse treatment connected to the report — is itself a serious Code of Conduct violation subject to the Removal / Recall procedure (Phase 3, 3-27), and a reporter who believes they're experiencing retaliation may escalate that concern the same way as the original report.

Anonymous reports. A reporter may withhold their identity, and doing so does not disqualify the report from being investigated — but an anonymous report necessarily limits the Board's ability to follow up for clarifying detail, which is disclosed to the reporter as a tradeoff, not a reason to discourage anonymity. Where a report names a specific individual, that individual is not told who reported them unless disclosure becomes unavoidable to conduct a fair investigation, and even then only the fact of a report is disclosed, not speculation about the reporter's identity.

Prohibits harassment — including sexual harassment, intimidation, bullying, and hostile or abusive conduct — at meetings, events, volunteer activities, and in digital communications (email, social media, text, group chats), whether directed at a fellow Council member, a volunteer, a member of the public, or CPD staff. This applies regardless of the relative seniority of the parties involved — a longtime officer harassing a new volunteer is not treated more leniently because of tenure, and a founding member is not exempt from a standard applied to everyone else.

Reports route through the same Complaint Intake procedure (5-46) with heightened confidentiality protections for the reporter, including the option to report to any officer other than the one alleged to be involved. Interim measures (separating the parties at events pending resolution, for example) may be taken immediately, before the full complaint process concludes, if there's a reasonable safety concern — the Council doesn't wait for a final finding to take basic protective steps. Severe or substantiated conduct triggers the Removal / Recall procedure (Phase 3, 3-27) regardless of the reported party's office or tenure, and a single severe incident, not just a pattern, can be sufficient grounds.

Third-party conduct. This policy also covers harassment by a vendor, contractor, sponsor representative, or member of the public toward a Council officer or volunteer — the Council's response in that case is directed at the relationship (ending a vendor agreement, barring an individual from future events) rather than at internal discipline, but the reporting and interim-protection steps are identical. A volunteer or officer who experiences this kind of third-party harassment is not expected to simply tolerate it as a cost of the role.

Implements Bylaws Article 27 operationally: membership, committee service, volunteer roles, and event participation are open without regard to race, ethnicity, national origin, religion, sex, sexual orientation, gender identity, age, disability, or income, consistent with CPD's own inclusive-service expectations and the non-discrimination language in CPD's PAC Bylaws Template itself. This is not merely a passive non-exclusion rule — the Council actively reviews, at least annually, whether its actual meeting times, locations, communication channels, and volunteer-role design are functioning as unstated barriers to any of these groups, since a facially neutral policy can still produce an unrepresentative Council in practice.

Any participation barrier identified — physical (an inaccessible meeting space), linguistic (materials only available in one language), financial (dues or costs with no waiver option), or scheduling (meetings only at times that exclude shift workers) — is referred to the Accessibility Committee (5-29), the Language Access Policy (5-30), or the Board directly, and tracked to resolution rather than noted and left unaddressed.

Complaints under this policy route through the same Complaint Intake procedure (5-46) as any other, but with an added step: because a discrimination complaint often implicates a pattern rather than a single incident, the Governance Committee reviews whether similar concerns have been raised before, not just the specific incident reported, and any confirmed pattern is escalated to the full Board as a policy-level failure rather than resolved as an isolated case.

Sets an accommodation-request contact and response process for Council-run meetings, communications, and events (distinct from CPD's own beach-facility accessibility, tracked in Phase 7); commits to accessible meeting locations and virtual-participation options (Bylaws Article 13) as a standing accommodation, not a special request that has to be re-justified each time; and requires digital materials to meet the Digital Accessibility Standard (Phase 9, 9-23).

A request for accommodation — a sign-language interpreter, materials in an alternate format, a mobility-accessible meeting location, a break during a long meeting — goes to the Accessibility Committee chair or, if unavailable, the Secretary, and is fulfilled for the specific meeting or event in question wherever reasonably possible; if a specific accommodation can't be arranged for a particular date, the Committee works with the requester on an alternative rather than simply declining. The Committee reviews the Council's default meeting format annually against this standard, since building accessibility in from the start is more reliable than depending on individual requests to catch every gap.

Lead time. A request made with reasonable advance notice (the Council's stated target is 5 business days before a meeting or event) is fulfilled as requested wherever feasible; a request made with less notice is still accommodated to the extent practically possible rather than declined outright for lateness, and the Committee follows up afterward on whether the shorter notice created a real gap that a standing accommodation could prevent next time. Denying a reasonable accommodation is not a Board-level decision made lightly — it requires the Committee chair and at minimum one other officer to concur that no feasible alternative exists, documented in writing.

Identifies which materials get priority translation based on the community's actual language needs (starting with meeting notices and any safety-related public postings), sets a good-faith interpretation request process for meetings, and requires translated materials to go through a basic quality/accuracy review before publication rather than relying on unreviewed machine translation for anything safety-related.

Priority order: (1) any content describing a beach hazard, water-quality advisory, or emergency information — machine translation alone is never sufficient here given the stakes of a wrong translation; (2) meeting notices and agendas, so language isn't a barrier to knowing a meeting is happening at all; (3) membership and volunteer application materials; (4) general programming and event announcements. The Communications Committee reassesses this priority order and which languages it applies to at least every two years as the community's composition around the beach changes, rather than assuming the original assessment stays accurate indefinitely.

Interpretation at meetings. A request for live interpretation at a specific meeting, made with the lead time set in the Accessibility Policy (5-29), is fulfilled through a qualified volunteer or paid interpreter — never through an untrained bystander pressed into service on the spot for anything beyond the most casual clarification, since a mistranslated procedural point (a vote's actual outcome, a deadline) can have real consequences for the person relying on it. Where no interpreter is available for a specific language on short notice, the Chair says so plainly rather than proceeding as though the gap doesn't exist, and follows up with the requester afterward on what was missed.

The Council, its funds, its name, its meeting space, and its communications channels are never used to endorse or oppose a candidate for public office, contribute to a campaign, or otherwise intervene in a partisan political campaign — a restriction that applies with particular force if the fiscal-structure decision (4-01) selects Path A (501(c)(3) status), where campaign intervention risks the exemption itself, but is adopted as Council policy either way, independent of which fiscal path is chosen. Officers and members remain free to engage in individual civic and political activity on their own time, using their own resources, provided they do not present it as a Council position and do not use Council contact lists, letterhead, or accounts to do so.

Practical application: candidate forums may be hosted only if every candidate for the office is invited on equal terms; officers speaking at a public meeting about a beach-related issue identify themselves clearly as speaking for the Council on that specific issue, not as a general endorsement of any candidate present; and any officer running for public office themselves steps back from Council communications that could blur the line between their candidacy and their Council role for the duration of the campaign.

Distinguishes ordinary, nonpartisan advocacy (asking an alderman's office for a capital improvement, testifying at a Park District board meeting about 63rd Street Beach, writing a letter supporting a specific lakefront accessibility initiative) — which this Council may do freely and is arguably core to its mission — from formal lobbying, which carries specific recordkeeping and, if Path A (501(c)(3)) is selected in 4-01, statutory expenditure limits under federal tax law (the "substantial part" test or, if elected, the more precise 501(h) expenditure test).

Any activity that starts to resemble organized lobbying — repeated, resourced efforts to influence specific pending legislation, as opposed to a one-time letter or testimony on a matter directly affecting the beach — should be flagged to Counsel before it becomes a pattern, and if the Council anticipates a sustained advocacy campaign around a specific issue (a capital funding push, a proposed ordinance affecting the beach), the Board decides in advance how it will be tracked and reported, rather than discovering after the fact that it crossed a threshold no one was watching.

Recordkeeping. Whenever an activity is flagged as advocacy under this policy, the Treasurer logs any associated expenditure (staff/volunteer time is generally not a countable expenditure, but printed materials, travel, or paid outreach can be) separately from routine programming costs, so that if the "substantial part" or 501(h) question ever needs a real answer, the Council isn't reconstructing it from general ledger entries after the fact. This log is reviewed alongside the Annual Risk Assessment (Phase 10, 10-17).

Defines a short, specific list of what actually counts as confidential — individual membership application contact details, donor identities where requested, minors' information, active complaint files, legal-hold material, and any information an officer learns in a related-party recusal (5-23) that isn't otherwise public — and prohibits officers/volunteers from removing, copying, or forwarding it outside authorized Council systems, consistent with the CPD Code of Conduct's own data-handling expectations (Phase 3, 3-15). Everything not on this list is presumptively open, consistent with the Voluntary Transparency Standard (5-16) — this policy is deliberately narrow so "confidentiality" can't become a catch-all excuse to withhold routine information from members or the public.

An officer or volunteer who leaves the Council retains the same confidentiality obligations for information they learned during their term — departure doesn't release anyone from this policy, and the Digital Account Handover Record (Phase 3, 3-29) exists in part to ensure access to confidential systems actually ends when a role ends, not just in principle.

When confidentiality yields to a competing obligation. This policy does not override a legal-hold preservation duty (5-12), a member's statutory inspection right (5-13), a CPD compliance inquiry, or a mandatory report under the Youth Protection Policy (5-45) — where one of those obligations requires disclosure of information this policy would otherwise treat as confidential, the competing obligation controls, and the officer handling it consults Counsel when the two genuinely conflict rather than resolving the tension alone.

Governs what personal data the Council collects (membership applications, newsletter signups, donation and event records, volunteer sign-ins), why, how long it's kept (per 5-10), who can access it, and how it's disposed of. Data is collected only for the stated purpose it was gathered for — a membership application is not repurposed as an unrestricted mailing list, and event sign-in data is not shared with sponsors without separate, explicit consent from the individuals involved. Paired with the public-facing Privacy Notice (Phase 9, 9-25), which tells the public in plain language what this policy commits the Council to internally.

Minimum-necessary principle: every form or sign-in sheet the Council uses is reviewed for whether it actually needs every field it asks for — a beach cleanup sign-in doesn't need a home address, and a newsletter signup doesn't need a phone number. Access to any system holding personal data is limited to officers/volunteers whose role actually requires it (the Treasurer needs donor financial records; a Programs Committee member generally doesn't), consistent with the Digital Access Policy (5-37). A request from an individual to correct inaccurate personal data about themselves, or to be removed from a non-essential list like the newsletter, is honored promptly.

Third parties. Any vendor, platform, or partner organization that processes Council-collected personal data on the Council's behalf (an email marketing tool, an event-registration platform) is reviewed for its own data-handling practices before adoption — a free tool that monetizes user data is not treated as cost-neutral just because it charges the Council nothing — and the Council does not sell or trade personal data to any third party under any circumstance, a commitment stated plainly in the public Privacy Notice (Phase 9, 9-25) rather than left implicit.

Minimum controls for a volunteer-run organization with no dedicated IT staff: unique, strong passwords per account (no sharing a single login across multiple officers, which also makes the Digital Account Handover Record (3-29) meaningless if everyone already has everyone else's password); multi-factor authentication enabled on email, banking, and cloud-storage accounts wherever the provider offers it, treated as mandatory rather than optional for the Treasurer's and Secretary's accounts specifically; shared drives restricted to the minimum access each role actually needs; basic phishing awareness for anyone with financial or membership-data access, refreshed at least annually since attack techniques change; and regular, tested backups of anything that would be catastrophic to lose — a backup that's never been restored is not a verified backup.

The Technology Lead maintains a simple current inventory of every institutional account, who has access, and whether MFA is enabled — reviewed at every officer transition and at least annually otherwise. Any suspected compromise (an unrecognized login, a suspicious email from a Council account, a lost or stolen device with access) is reported immediately to the Technology Lead per the Incident Response Plan (5-38), not quietly worked around by whoever noticed it.

Personal devices. Where an officer or volunteer accesses Council systems from a personal phone or laptop (common for a volunteer-run organization with no issued equipment), that device is still subject to the same password-strength and MFA expectations for the Council accounts it touches, and the Technology Lead's account inventory notes which accounts are accessed this way — not to police personal devices generally, but because a lost personal phone with an unlocked email app is functionally the same exposure as a lost Council-owned one.

This Organization document library itself is a live example of what this policy governs — its first draft was produced with generative-AI assistance, under a named officer's direction, and is being published, reviewed, and corrected by the humans responsible for it rather than treated as self-authenticating. The Council does not pretend AI tools are absent from its work; it governs how they're used, because pretending otherwise is how ungoverned use happens by default.

The policy this practice implies: no confidential or personal data (5-33, 5-34) — donor financial details, minors' information, an individual complainant's identity — may be entered into an AI tool that isn't specifically approved and covered by an appropriate data-handling agreement; any AI-assisted content intended for public use (this library, social posts, official letters, grant narratives) is reviewed and approved by a responsible officer before publication, not published automatically on the assumption that the tool got it right; AI-assisted drafts are treated as drafts, explicitly and visibly, until that review happens, exactly as the "Proposed — Pending Board Adoption & CPD Determination" pill on every document in this library signals; and material factual claims — CPD rules, legal requirements, dollar figures, named CPD offices or committees — are checked against a real, current source before being relied upon or cited externally, exactly as the disclaimer on every page of this library already asks the reader to do.

An officer who is uncertain whether a given AI use falls inside or outside this policy treats it as outside until the Technology Lead or Governance Committee confirms otherwise — the cost of asking is a short delay; the cost of guessing wrong with donor or minors' data is not recoverable after the fact.

Every institutional account (email, website hosting, social media, cloud storage, banking portal, the domain registrar) is owned by the Council, not by whichever individual happened to create it — registered under an institutional email address where the provider allows it, never under a personal email address that outlives the officer's term, with access granted on a least-privilege basis (an Event Lead doesn't need banking-portal access; a Programs Committee member doesn't need website-hosting credentials) and multi-factor authentication required wherever the provider supports it.

Every account has a documented recovery contact who isn't the sole person with access to that account — a Council where one departed volunteer is the only person who remembers a password is a Council that has, in practice, lost the account. Access is revoked, not just "forgotten about," within 48 hours of an officer transition per the Digital Account Handover Record (Phase 3, 3-29): the outgoing officer's credentials are changed or removed, not left active "just in case," and the Technology Lead confirms in writing that revocation actually happened rather than assuming it did.

The Technology Lead maintains the master account inventory referenced in the Cybersecurity Policy (5-35) and is the point of contact for any officer who is locked out, suspects unauthorized access, or is unsure whether a tool or service they want to use should be treated as an "institutional account" under this policy — when in doubt, it is.

Creating a new account. No officer or volunteer sets up a new institutional account (a new social platform, a new scheduling tool, a new shared drive) unilaterally — the Technology Lead is looped in before creation, not after, so the account is registered correctly (institutional email, MFA enabled from day one, added to the inventory) rather than retrofitted later. An account created outside this process, however well-intentioned, is treated as a compliance gap to correct immediately once discovered, not as an acceptable shortcut because it saved time.

Drafted before the Council holds significant donor or personal data, not after an incident — a response plan written during a live breach is written under pressure and tends to skip steps. Covers, in sequence: immediate containment (revoke compromised credentials, isolate affected accounts, change shared passwords) by the Technology Lead the moment a suspected compromise per the Cybersecurity Policy (5-35) is reported; preservation of evidence (login records, the suspicious message itself, timestamps) before remediation activity destroys it; and a fact-gathering step — what data was actually accessible, to whom, for how long — before any public statement is made, so the Council isn't retracting an initial description later.

A decision process for whether and whom to notify follows, made jointly by the President and Counsel rather than by whoever discovered the incident: affected individuals if personal data was actually exposed, CPD if the incident touches a CPD-facing system or reputationally implicates the Council's status as a recognized PAC, law enforcement if it involves theft or fraud, and Illinois's own data-breach notification requirements if the volume or type of data exposed triggers them — that threshold determination is Counsel's call, not a volunteer's guess. Vendor/platform coordination (the bank, the email provider, the website host) runs in parallel, since several of them have their own required incident procedures.

Every incident, however minor, closes with a written post-incident review — what happened, what worked, what didn't — feeding directly into the Enterprise Risk Register (5-43) so the same gap isn't rediscovered the same way twice.

Specifies who may actually sign a binding contract on the Council's behalf — ordinarily the President, or the Treasurer for routine financial agreements within the dollar limits set by the Delegation of Authority Matrix (Phase 2, 2-36) — and, separately, who reviews a contract's substance before anyone signs it. A signature-authority limit only works if it's checked before the fact: no contract above the Matrix's threshold, and no contract containing an indemnification, exclusivity, or automatic-renewal clause regardless of dollar amount, is signed without prior review by the Governance Committee or Counsel.

Every contract template the Council uses — sponsorship agreement, vendor agreement, partnership MOU (Phase 4, Phase 8, Phase 9) — must include the Standard "PAC Is Independent of CPD" Clause (5-40) verbatim or as adapted by Counsel, so no agreement can be read as binding CPD, obligating CPD funds, or implying CPD's endorsement. A counterparty's own contract template (a sponsor's standard agreement, a vendor's boilerplate) is reviewed with the same scrutiny as one the Council drafted itself — familiarity with a counterparty is not a substitute for reading what was actually signed.

A signed original of every contract is retained per the Records Retention Schedule (5-10) and logged centrally, so the Board can answer "what are we currently obligated to, and to whom" without reconstructing the answer from individual officers' files.

What happens if this is skipped. An officer who signs an agreement outside their delegated authority, or without the required review, does not automatically bind the Council to an unauthorized obligation as a matter of internal policy — the Board reviews any such agreement immediately upon discovery, and if it's disadvantageous or improper, seeks to unwind or renegotiate it, with Counsel's guidance on what's actually achievable once a counterparty has already relied on a signature. Repeated disregard for this policy by the same officer is treated as a Code of Conduct matter, not merely a process reminder.

Standard language for insertion into any Council-signed agreement:

This clause exists because the Council's name, its recognized status as the CPD-affiliated advisory body for 63rd Street Beach, and its close working relationship with park staff could otherwise be mistaken by a counterparty — or represented by a counterparty to a third party — as authority the Council does not actually have. A sponsor cannot describe itself as "an official CPD partner" on the strength of a Council sponsorship agreement; a vendor cannot claim CPD approval of its services because it contracted with the Council.

Used verbatim (or as adapted by Counsel for a specific agreement, never removed) in every sponsorship, vendor, partnership, and MOU template across this library (Phase 4, Phase 8, Phase 9). Any counterparty who objects to including it is a signal to escalate to Counsel before proceeding, not a reason to drop the clause to close the agreement faster.

Requires a substantive coverage review — not just a renewal-date check — before any material event (a beach festival, a large youth program, anything drawing crowds beyond the Council's routine cleanup and meeting activity), before onboarding volunteers into higher-risk roles (stewardship workdays involving tools or water, youth programming), and before signing any contract containing an indemnification or hold-harmless clause. "Coverage review" means someone actually reads the policy's exclusions and limits against the specific activity planned, not just confirms a premium was paid.

The review confirms explicitly what current coverage does and doesn't include — general liability, event-specific riders, Directors & Officers (D&O), cyber — and, distinctly, identifies any benefit the Council may already receive through CPD's own coverage for park-permitted activity versus what the Council must independently obtain. Those two coverage layers are not assumed to be redundant or identical; the Insurance Register (Phase 4, 4-48) tracks which layer covers what, and any gap between them is flagged to the Board rather than discovered after a claim.

An event that outgrows its planned scope — more attendees, added activities, a rented inflatable — outgrows its insurance review too; the Risk Lead re-checks coverage against the activity actually happening, not just the activity originally proposed.

Additional insured requests. A venue, sponsor, or partner organization asking to be named as an "additional insured" on the Council's policy is a routine, expected request, not a red flag — but it is still routed through the Risk Lead to confirm the current policy actually permits it and at what cost, rather than promised in a contract negotiation before the insurer has confirmed it's possible. The Insurance Register (4-48) tracks every additional-insured endorsement issued, since an outdated one naming a past partner is itself a minor but avoidable gap.

Assigns risk ownership across the Council's actual risk categories — beach/safety, event, financial, environmental, cyber, and reputational — to specific committees or officers by name, not by category alone, because an unassigned risk is a risk nobody is actually tracking. The Programs/Events Committee owns event and beach/safety risk; the Treasurer and Finance Committee own financial risk; the Technology Lead owns cyber risk (5-35–5-38); the Board collectively owns reputational risk, since it rarely maps cleanly to one committee.

Each owner is required to feed identified risks into the Enterprise / PAC Risk Register (5-43) as they're identified, not only at the quarterly review — waiting for the scheduled review to log a risk that's already been spotted defeats the purpose of having a register. A defined escalation path (owner → Risk Lead → full Board → CPD/Counsel as needed) applies whenever a risk exceeds what its owner can mitigate alone, so a risk doesn't sit unaddressed simply because it doesn't cleanly belong to one committee or because its owner is reluctant to raise it.

This policy is reviewed at least annually and after any incident that reveals a risk category the Council hadn't previously named — the categories above are a starting point, not a ceiling.

A living document, reviewed quarterly at minimum and updated in real time whenever an owner identifies a new risk per the Risk Management Policy (5-42) — not held for the next scheduled meeting. Every entry names a specific, accountable owner, not a committee generically; "Programs Committee" as an owner tends to mean no one actually follow-ups.

The register should read as slightly uncomfortable: a register with nothing rated "High" after a genuinely candid review is more likely incomplete than genuinely risk-free, and the Risk Lead treats an unusually clean register as a prompt to ask what's being missed rather than as good news on its own.

Requires role-appropriate training before a volunteer takes on a task — a beach cleanup orientation is not the same training as leading a stewardship workday involving tools or water — and direct, in-person supervision by a designated adult lead for anything beyond routine cleanup or hospitality work. A hard list of tasks volunteers may never perform, regardless of individual skill or enthusiasm, applies without exception: any lifeguard or water-rescue function (which belongs to CPD-certified staff, not Council volunteers, under any circumstance); unauthorized work in natural or dune areas that could conflict with CPD's own habitat management; and any electrical, structural, or heavy-equipment work that isn't the volunteer's professional trade performed under proper authorization.

Every Council-run activity has a simple, known incident-reporting channel (Phase 6, 6-30) that volunteers are told about before they start, not discovered only if something goes wrong — an unreported near-miss teaches the Council nothing. Confirmation that CPD's current volunteer waiver and application process (Phase 1, 1-27; Phase 11, 11-59) is completed for every volunteer, one-day or recurring, before they begin any activity is a hard precondition, not a formality to be caught up on afterward; the Volunteer Coordinator, not the volunteer's own assurance, is the one who confirms it's on file.

Near-miss reporting specifically. A near-miss — a volunteer who nearly stepped on a hazard, a task that felt more dangerous than briefed, a supervision ratio that felt too thin in the moment — is reported through the same channel as an actual incident and reviewed with the same seriousness, because a near-miss is the cheapest possible warning the Council will ever get about a real gap. Volunteers are told explicitly, as part of orientation, that reporting a near-miss will never be treated as a complaint about their own performance.

Applies to any Council-run activity involving minors, whether a standalone youth program or a general event where minors are simply present. Requires current, CPD-approved background checks — completed and on file before the activity, not "in progress" — for anyone in an unsupervised or near-unsupervised role with youth (Phase 1, 1-29); this requirement applies to every such adult without exception, including long-tenured volunteers and Board members, since tenure is not a substitute for a current check.

A minimum adult-to-youth supervision ratio is set before the activity is planned, scaled to the activity's risk level (a calm classroom-style lesson needs less supervision density than an open-water beach activity), and is never improvised on the day based on who happens to show up. Written parent or guardian consent and emergency contact information (Phase 8, 8-24) is collected for every participating minor before the activity begins; a minor without consent on file does not participate, regardless of how minor the activity seems.

A no-lone-adult-with-a-single-minor rule applies to every Council-run activity without exception — any one-on-one interaction happens in view of other adults or is restructured to avoid it entirely. Any youth-safety concern, however small it seems to the person who notices it, is immediately reportable to the Youth Lead and, where warranted, escalated to CPD and appropriate authorities without delay; it is never handled quietly, informally, or "internally" at the volunteer level, and no officer has authority to decide otherwise.

Implements Bylaws Article 20. Any complaint — from a member, volunteer, or member of the public, about governance, conduct, safety, or finances — receives a written acknowledgment within 5 business days and a substantive written response within 30 days, with a copy filed at the park per current CPD guidance; complaints involving an officer are reviewed by disinterested officers only. If the complainant is dissatisfied with the Council's response, current CPD guidance gives them the right to appear before the general membership to be heard. If the matter is still unresolved after that, the real escalation path outside the Council runs: written appeal to the Park Supervisor or Area Manager → shared with CPD's Department of Legislative and Community Affairs (LCA) → shared with the CPD-side body holding final authority over PAC complaints. That body is named the "PAC Governance Committee" in CPD's current (Feb. 2025) PAC Guidelines and the "Complaint Review Committee (CRC)" in the Jackson Park Advisory Council's own current bylaws — the two real sources reviewed while drafting this library disagree on the name, so confirm the current correct name directly with LCA before citing it externally. Under either name, its decision (in partnership with LCA) is final and binding, and it is not the same body as this Council's own internal Governance Committee (Phase 2, 2-34/2-37; Phase 3; Phase 6) — that is the Council's own committee for its own internal governance work, with no role in CPD's complaint process.

Internally, every step above is timestamped and logged in the Complaint Case File (5-47) as it happens, not reconstructed afterward from memory — the 5-business-day and 30-day clocks in this procedure only mean something if the Council can show, on request, exactly when each clock started and stopped. A complainant is told in writing, at the time of acknowledgment, what the process is and roughly how long each stage takes, so "what happens next" is never a question they have to ask.

Interim measures pending resolution. A complaint alleging an immediate safety or conduct risk does not wait for the full 30-day process before any protective step is taken — the President or disinterested officers reviewing the matter may impose reasonable interim measures (temporarily restricting a role, separating parties at events) the moment the complaint is received, revisited once the substantive review concludes. Where a complaint is anonymous, it is still logged and reviewed on the same timeline, though the Council notes in the case file that acknowledgment to the complainant isn't possible and follows up publicly (in aggregate, not by naming the matter) only if the underlying issue has broader relevance.

One file per complaint, opened the moment a complaint is received and never assembled retroactively: the original complaint as submitted, the dated written acknowledgment, any hearing or review notes, the final written resolution, and any resulting corrective action (5-49) — and, for any complaint escalated per the procedure in 5-46, a record of the escalation and the CPD-side committee's final decision as well.

Held to a stricter confidentiality standard than most Council records (5-33), viewable only by disinterested officers reviewing that specific case, and retained for 7 years after resolution per the Retention Schedule (5-10), given the potential future relevance to a removal proceeding (Phase 3, 3-27) or an external inquiry from CPD or Counsel.

A short, signed statement each of the three key officers (President, Secretary, Treasurer) completes annually, individually and in their own words rather than as a joint form one person fills out for all three, confirming or explicitly flagging as incomplete each core recurring obligation tracked on the Compliance Matrix (5-01): the CPD Annual Report filed, the Illinois annual/biennial report filed, current evidence of NFP status on hand, background checks current for all officers with youth or vulnerable-population contact, and the Records Retention Schedule (5-10) actually followed for the year rather than merely referenced.

The point of the certification is candor, not a clean record — an officer who signs off on something that isn't actually true has created a worse problem than the original gap. Anything that can't be honestly certified as complete goes straight into the Compliance Exception / Corrective Action Log (5-49) rather than being certified anyway, and the certification itself is retained as evidence that the gap was identified and acted on, not concealed.

Timing. Certifications are completed at the close of the fiscal/reporting year used for the Illinois and CPD annual filings (10-03, 10-04), after those filings are actually submitted rather than before, so each officer is certifying what actually happened rather than what was merely planned. A newly elected officer completing their first certification reviews the prior year's with their predecessor as part of the Officer Transition Checklist (Phase 3, 3-28), so continuity of what's actually been true year over year isn't lost at a transition.

A missed filing, a CPD finding, or a gap surfaced by the Annual Compliance Certification (5-48) that's logged and fixed on a target date is a normal, expected part of running a volunteer organization; one that's quietly noted and never followed up on is how a small gap becomes a real problem, sometimes years later when it's much harder to fix. This log exists specifically so nothing falls into the second category — every entry gets a named owner and a target date at the moment it's logged, not "eventually."

Reviewed at every Board meeting until an item is closed, not filed once and revisited only at year-end; an item that's been open for multiple consecutive reviews without progress is escalated to the full Board rather than left with its original owner indefinitely.

A maintained-but-inactive template implementing Bylaws Article 30, reviewed periodically for continued accuracy even though it is activated only if the Council actually disbands. The packet exists precisely because dissolution, if it ever happens, tends to happen at a moment of organizational stress — declining participation, an unresolved conflict, loss of a key facility relationship — when careful, orderly process is hardest to execute from scratch. Having the steps already written down removes one source of difficulty from an already difficult moment.

The packet sequences: a Board vote to dissolve per the Bylaws' amendment/dissolution threshold; written notice to CPD, given the Council's recognized status as the advisory body for 63rd Street Beach; notice to and formal settlement with the bank or fiscal sponsor (Phase 4, 4-01/4-02), closing all institutional accounts per the Digital Access Policy (5-37); a final, audited-if-material financial report; and disposition of any remaining funds — general or donor-restricted — strictly consistent with donor intent and Illinois charitable-asset law, cross-referenced against the Fund Disposition Worksheet (Phase 4, 4-62), since restricted funds cannot simply be distributed as the dissolving Board sees fit.

The sequence closes with the formal Illinois corporate dissolution filing and a final notice to members and the community. Having this ready in advance, even though nobody expects to need it, is itself a marker of a well-governed organization — and protects the individuals serving as officers at the time from having to improvise a legally consequential process under pressure.