Venues data model with rooms, travel data, and reporting

Need: A structured venue object with name, address (city/state), rooms/sites, travel time vs distance, driving/parking instructions, and persistent notes (Wi-Fi, load-in, security). Key requirements: Travel cost calculation based on venue distance/time Rooms/sites as sub-locations within a venue Deduplication to prevent duplicate venue records Reporting by venue and city/state for co-marketing and staffing View all events at a venue Venue contacts separate from venue (event managers change per event) Pain point: Current system duplicates venues, has no reporting by venue/city, and travel time vs distance mismatch causes inaccurate cost estimates. Source: Hope Mckellip DJEP walkthrough, 09/09/2026