Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Alcohol Policy topic
No spam. Unsubscribe anytime.
Committee debates alcohol/drug-free facilities exceptions, security requirements and vetting
Summary
Committee reviewed linked drug-free workplace and alcohol-free facilities policies, debated whether to separate 'reporting for duty' from 'attending sponsor function' language, and agreed to route exception requests through Operations/superintendent and revise forms to require attendance and security details.
Richmond Community Schools’ policy committee discussed two linked policies: the district’s drug-free workplace policy and the alcohol-free facilities and board-approved exceptions policy. The conversation centered on employee obligations, intoxication criteria, security requirements for events serving alcohol, and whether frequent partner events could be approved on an annual basis.
Speaker 1 explained the concern: if a staff member attends a sponsored event where alcohol is served, would they be in violation of the district’s drug-free workplace policy? Committee members recommended separating the language that addresses employees who report for duty (on-duty standards) from language that addresses employees who attend corporation-sponsored events (off-duty attendance while representing the district) to avoid confusion.
The group agreed that a clear test for 'exhibits effects of being intoxicated' is needed and that any disciplinary consequences should be described in appropriate documents (for example, cross-referenced in handbooks or administrative guidelines). Speaker 2 suggested routing exception applications through Operations or cabinet for review and said the superintendent could designate someone for that vetting.
Committee members also discussed whether partners who hold multiple events could submit a single annual application (and provide insurance/certification) rather than submitting forms for each event. Some members noted insurance policies can lapse and that event-by-event review provides necessary protection; others favored one-time approvals for trusted local partners to reduce administrative burden.
The committee asked staff to revise the event form to specify expected attendance and type of security personnel (existing staff vs. outside hire) and to clarify which office receives and vets the form before it reaches the board. No board vote was taken; staff were instructed to redline and return recommended language and form edits.
What’s next: Operations will be asked to propose clarified wording separating 'report for duty' from 'attend sponsor function' language, update the event form to capture attendance and security details, and recommend whether annual partner approvals are appropriate.
