Hire Event Vendors

FAQs

1. What should I verify about Wi‑Fi capacity, coverage, and performance to ensure reliable connectivity?

Define expected concurrent users, device types (smartphones, laptops, POS terminals, streaming devices), and peak usage patterns. Ask the provider for site‑specific capacity planning: required throughput per user (typical event baselines: 1–3 Mbps for basic browsing, 3–8 Mbps for video conferencing, 8–25 Mbps for HD streaming), total aggregate bandwidth, and headroom (recommend 25–50% extra). Request a heat‑map or coverage plan showing access‑point placement, antenna types, and expected signal strength (RSSI) at key areas—stage, registration, exhibitor booths, catering, and outdoor zones. Verify channel planning for 2.4 GHz vs 5 GHz, spectrum congestion analysis, and plans to mitigate interference (DFS channels, channel width limits). Confirm whether the provider will perform an on‑site spectrum survey and if they offer wired Ethernet drops for critical devices.

2. What should a clear quote and contract include, and what hidden costs should I watch for?

The quote should itemize bandwidth (Mbps or Gbps), cost for dedicated circuits vs. shared access, access‑point rental and quantity, installation/setup fees, onsite technician hours, and teardown/removal. Contract must state service windows, SLA metrics (uptime, latency, packet loss), remedies for missed SLAs (service credits), and IP addressing/port/access policies. Watch for hidden costs: surge charges for bandwidth overages, fees for additional SSIDs or VLANs, charges for onsite power or conduit work, costs to extend service to outdoor areas, per‑device licensing, static IPs, firewall/NAT rules, and charges for changes made day‑of. Require a written change‑order process and clear cancellation/weather/refund terms.

3. How do I evaluate redundancy, throughput, and security for event networks and streaming?

Ask about upstream redundancy (dual carriers, bonded circuits, or cellular bonding) and failover testing plans. Verify backhaul capacity and whether they provision separate circuits for public Wi‑Fi vs production/streaming VLANs to prevent contention. Confirm latency and jitter guarantees for real‑time needs and request throughput test results from similar events. Review security measures: WPA2/WPA3, unique per‑event WPA keys, client isolation for guest networks, VLAN segmentation, ACLs, and intrusion detection or logging. Ask if the provider offers managed firewalls, DDoS protection, and regular patching for network devices.

4. What logistics and on‑site coordination should I confirm before and during the event?

Provide a site map with power locations, preferred AP mount points, load‑in access, and staging areas for equipment racks and modems. Confirm arrival/setup windows, whether the provider needs ladder access or scissor lifts, and venue rules for cabling and conduit. Agree on test procedures and a schedule for pre‑event speed and load tests, and confirm on‑site technician coverage hours, response SLAs for outages, and escalation contacts. Verify who will manage captive portals, branding, guest portals, and any integration with event registration systems or payment terminals.

5. What deliverables, monitoring, and post‑event responsibilities should I require to protect my event?

Require a pre‑event acceptance test and post‑event report showing uptime, bandwidth usage, client counts, peak throughput, and any incidents with timestamps and resolution notes. Ask for real‑time monitoring dashboards during the event and on‑site or remote NOC support. Specify deliverables: configuration backups, inventory of equipment installed, IP addressing scheme, and logs for a defined retention period. Include remedies for SLA breaches, a change‑order process for mid‑event scope changes, and clear asset‑return terms for rented hardware.