Common coordination roles
Make decisions and interfaces visible
The roles below describe common coordination contexts. They do not identify or imply a partnership, endorsement, certification, or current commercial relationship with any organization or vendor.
01Owners and executive sponsors
Set business outcomes, risk tolerance, funding, schedule priorities, and the decision path for competing needs.
- Which guest, event, production, and operating outcomes matter most?
- Who can resolve scope, schedule, risk, and acceptance decisions?
02Venue IT leaders and operators
Own enterprise architecture, service continuity, operating standards, support readiness, and the long-term technology lifecycle.
- Which standards and support boundaries apply?
- What evidence does the operating team need at handoff?
03Carriers and connectivity providers
Deliver circuits and external connectivity with physical paths, demarcations, routing, service levels, and escalation responsibilities to coordinate.
- Are physical and logical diversity assumptions confirmed?
- Who owns testing, escalation, and recovery at each boundary?
04AV, broadcast, and media teams
Bring time-sensitive production, content, IPTV, control, remote contribution, and event-specific workflows into the shared environment.
- Which media flows and control dependencies are in scope?
- How will representative production workflows be validated?
05POS and ticketing teams
Depend on reliable, secure connectivity for entry, transactions, concessions, premium spaces, and event operations.
- What are the normal and degraded operating modes?
- Which vendor, cloud, device, and support paths are required?
06Physical security teams
Operate video, access control, credentialing, incident, and life-safety-adjacent workflows that require explicit network and support boundaries.
- Which systems, operators, retention paths, and remote users communicate?
- How are access, monitoring, and exception decisions approved?
07Facilities and operational technology
Operate building controls, lighting, environmental, vertical transport, metering, and other systems with distinct lifecycle and availability needs.
- Which legacy protocols and vendor-access paths are required?
- How will segmentation changes be tested without disrupting operations?
08Construction and program teams
Coordinate design packages, procurement, dependencies, site access, sequencing, punch lists, schedule, and turnover across the project.
- Which decisions are needed before procurement or installation?
- How will technology readiness align with construction milestones?
09Low-voltage teams
Deliver pathways, spaces, copper, fiber, labeling, testing, and documentation that network and venue systems depend on.
- Are pathway, distance, density, resiliency, and testing requirements explicit?
- How will installed state and test results be handed off?
10Integration partners
Configure and connect systems across domains, making interface definitions, versions, dependencies, and acceptance ownership essential.
- Who owns each interface and cross-system issue?
- Which versions, configurations, and representative workflows will be accepted?