Clubhouse alcohol / off-duty-officer requirement (two Crest records)
This is a public record hosted on the source's public portal. Open or verify it at the source below; the file hash was checked against the capture manifest. This site has not necessarily content-reviewed the full text yet.
Relevant excerpt / transcription (labeled)
“If alcohol will be present, a constable or sheriff contract must be submitted at the time of booking.” / rental agreement: alcohol “consumed or permitted.”
Source location: See source link
Source identity
- Title
- Clubhouse alcohol / off-duty-officer requirement (two Crest records)
- Record date
- 2026
- Publisher / source
- Crest Management (public amenity record + rental agreement)
- Source type
- Public amenity record + form
- File type
- application/pdf
- Pages
- —
- Published
- August 27, 2026
- Archive record ID
- clubhouse-alcohol-rule
Summary
Two Crest-published records use presence-based language: the amenity entry requires a constable/sheriff contract “if alcohol will be present,” and the rental agreement requires hiring an off-duty officer when alcohol is “consumed or permitted.”
What this establishes
- The written rule ties the requirement to alcohol being present, consumed, or permitted — not only to alcohol served by the host.
What this does not establish
- That any specific event involved alcohol, was a covered reservation, or lacked required security; and it does not establish that any speaker knew the rule.
Why it matters
A narrowly stated inconsistency is possible between the presence/permission rule and any statement that a host did not personally serve alcohol; the statement does not answer the presence condition.
Open questions — records still needed
- Event-specific facts and any authenticated statement connecting a speaker to a covered event.
Known limitations
Rule text only; not connected to any specific event on this record.
Integrity information
- Original filename
- Community Clubhouse Rental Agreement.pdf
- File size / extent
- —
- SHA-256
- D49EA48589AAEB1F4F18455396FCFBE12AD5B1BF18DF84D9645BC7AE353592F0
- Complete or excerpted
- Excerpt / partial (original retained privately)
- Redaction status
- None required.
“Verified” refers to file provenance or capture integrity; it does not mean every statement inside the record is true.
Corrections and responses
No corrections or responses have been published for this record yet. Verified corrections and any full Board, management, vendor, or named-person response will be dated and linked here.
Request a correction for this recordRevision history
- August 27, 2026Record created for first public release.
Last reviewed: August 27, 2026