Why it matters
Without this system, encounters may exceed welfare limits, keeper injuries can rise during crowded sessions, and scheduling errors risk accreditation and guest dissatisfaction.
From design to safety
Design
Design AI-enabled encounter framework
Defines data needs, privacy, welfare constraints, and booking rules for keeper talks, encounters, and educational programs across exhibits; aligns with SSP and ZIMS data standards and compliance checks.
- Education Center Plan
- Visitor Flow Model
- Scheduling Policy Document
Build
Build scheduling data pipelines
Ingests booking requests, welfare thresholds, exhibit times, staff availability, and backup rosters to form initial encounter catalogs, rules, and escalation paths for audits and governance reviews later.
- Booking Database
- Staff Rostering System
- Encounter Standards Guide
Operation
Operate dynamic encounter scheduling
Reads live attendance, talk durations, welfare signals, queue lengths, and feeder schedules; adjusts times, caps sessions, and triggers staff alerts with sharable dashboards for cross-venue use and daily reviews.
- Public Kiosk Interface
- Talk Timing Server
- Encounter Queue Monitor
Maintenance
Maintain welfare-checked encounters
Monitors welfare limits over time, recalibrates thresholds after field observations, updates rule sets post-review, and logs maintenance notes in ZIMS with version control for traceability and audits.
- Welfare Limits Monitor
- Encounter Rules Engine
- Maintenance Log System
Safety
Safeguard guest and animal safety
Enforces crowd control, ensures protected-contact limits, verifies permit and licensing approvals, and maintains incident logs for licensing audits and welfare reviews across exhibits and events.
- Barrier Control Panel
- Visitor Access Gates
- Animal Welfare Review Board
Part by part
- 1
Front-of-house booking terminal
- Watch for
- double-bookings or invalid time windows causing overbooked encounters
- AI action
- normalize schedules and flag conflicts for staff review
- 2
Keeper talk scheduling console
- Watch for
- talks conflicting with feeding or cleaning routines
- AI action
- reallocate talks and notify lead keeper or supervisor
- 3
Animal welfare limits monitor
- Watch for
- exceeding maximum guest contact duration or crowding at exhibits
- AI action
- pause talks, alert supervisor, and log welfare consideration
- 4
Exhibit audio-visual system
- Watch for
- excessive volume or rapid scene changes
- AI action
- adjust playback levels, queue quiet times, route to education channels
- 5
Education and encounter reservation ledger
- Watch for
- staff no-shows, repeated cancellations
- AI action
- trigger waitlist, auto-rebook, flag for supervisor review
- 6
Volunteer/keeper briefing station
- Watch for
- duplicate briefings, missing safety notes
- AI action
- require checklist completion and notify team lead
Worked example
Catching a seal talk before the feed
Illustrative scenario with sample data.
An AI-powered system detects a high turnout for a popular seal talk overlapping with the seals’ feeding window and potential welfare conflict.
Signal in
record_time: 09:45, session: Sea Talk, expected_attendees: 75, welfare_threshold: max_visitor_contact: 20 minutes, staff_available: 4, exhibit_status: ready, exhibit_temperature: 18.5C, noise_level: 58dB, weather: cloudy, special_event: summer camp, last_change: 08:12, zone_overview: exhibit A, feeder: rotated;
System out
alert: potential welfare conflict; action: reschedule talk to 10:15; notify lead keeper; update Kiosk schedule; log incident in welfare module; adjust feeder sequence; record override in encounter ledger; create family-access slots for later in day.
Human sign-off: Lead curator approves rescheduled time and informs education team; welfare lead signs off on temporary capacity cap for the revised slot; licensing liaison confirms permit consistency with the new timetable.
How to roll it out
Phase 1
Weeks 1 to 2
Baseline data collection, rule authoring, interface integration, and privacy testing across guest devices.
Phase 2
Weeks 3 to 6
Pilot tests in non-critical exhibits, refine welfare thresholds, calibrate alerts, and test manual override procedures.
Phase 3
Weeks 7 to 12
Full activation with live visitors, staff training, and routine monitoring; establish feedback loop and monthly review cadence.
Where people stay in charge
- All scheduling decisions involving override must be signed by the Education Director or designated senior keeper.
- Any change to welfare thresholds requires Animal Welfare Lead approval after welfare review.
- Escalation must occur to Zoo Licensing and Accreditation body if a major welfare risk or incident is detected and not resolvable on-site.
Questions owners and crews ask
What data feeds does the system require to schedule encounters?
The system relies on booking requests, attendance patterns, staff schedules, welfare thresholds, exhibit calendars, safety notes, and regional event calendars, with auditable change trails for every adjustment.
How does the system protect animal welfare during encounters?
Welfare monitors track contact duration, noise levels, crowd density, proximity, and simultaneous interactions; alerts trigger pauses, reallocation, or cancellation to keep within predefined welfare limits and staff oversight.
Who approves changes to encounter rules or thresholds?
The Education Director and the Animal Welfare Lead approve rule changes, with annual reviews by the Zoo Licensing and Accreditation body and formal board sign-off for high-risk updates.
How are guest experiences communicated during scheduling changes?
Guest-facing notices update in kiosk interfaces, venue screens, and staff briefings, with automatic email or SMS alerts when bookings are modified; staff receive an on-duty notification.