Ninety minutes before doors, the room looks quiet. The production manager is already moving, phone in hand, checking the client's latest presentation, the venue contact's access note, the stage manager's cue list and the agency producer's timings. The screens are dark, the microphones are still in their cases and the audience hasn't arrived, but the event is already being controlled through decisions, ownership and handoffs.
That's the practical meaning of team roles and responsibilities in AV delivery. A well-defined structure doesn't just make an organisation chart look tidy. It gives people a reliable answer to four questions: who decides, who does the work, who needs to be consulted and who must be told. That clarity supports safe working, faster communication and calmer problem-solving when the plan changes.
Why Roles Matter More Than Kit
The most expensive equipment in a venue won't rescue an event where nobody owns the decision to pause, change or proceed. A production can have capable technicians, a detailed brief and a strong supplier, yet still become stressful when the client assumes the venue is handling access, the venue assumes the producer has checked power, and the crew waits for someone else to approve a change.
The HSE guidance on managing an event frames the organiser or duty holder as responsible for overall event safety. That includes co-operation and co-ordination, relevant risk information, staff competence, compliance monitoring and review. The point matters operationally: responsibility can't stop at the edge of one person's patch.
A responsibility map controls the pressure
Before load-in, I want a named owner for every decision that could affect delivery. That usually includes:
- Access and site readiness: The venue contact confirms when the room, loading route and working areas are available.
- Show control: The stage manager owns the live running order, cues and communication with presenters.
- Technical readiness: Each technical lead confirms that their system is tested and that known limitations are visible to the person controlling the show.
- Client changes: The client liaison gathers requests and routes them to the person with authority to approve their effect on time, safety and scope.
- Emergency response: The duty-holder structure identifies who can stop activity and how the instruction reaches every relevant worker.
This is why strong teams resemble championship-winning team structures. Different specialists can work at speed because the wider structure makes decision rights and dependencies clear. The lesson isn't that every event needs layers of management. It's that every important handoff needs an owner.
Ad-hoc allocation creates hidden risk
Ad-hoc role allocation often feels efficient during planning. Someone is already on the call, so they agree to “keep an eye on” the venue, the client or the stream. That phrase hides several separate duties, and those duties compete for attention when doors are approaching.
A written stakeholder communication plan makes the operating model visible. It should show who receives updates, which channel carries urgent instructions and who has authority to change the plan. The event feels calm when those answers have been settled before the room becomes busy.
Practical rule: If a responsibility matters during a failure, it must have a named owner before the event starts.
The Core Team on an AV Event
An event team works across three conversations, not one hierarchy. The client-side conversation defines purpose and approvals. The production-side conversation turns that purpose into a workable show. The venue-side conversation controls the building, access, infrastructure and site rules.
The project manager sits across all three. They translate the brief into a plan, coordinate resources and escalate decisions that exceed an individual role. The agency producer protects the creative and editorial intent, while the client liaison confirms what the client wants and prevents technical staff from receiving conflicting instructions.
Client-side ownership
The client liaison owns the relationship with the client during delivery. They collect presentation changes, speaker concerns and approval requests, then hand those requests to the project manager or relevant lead rather than passing informal instructions directly into the crew.
The agency producer owns the event's wider creative direction and programme intent. Their handoff is a usable brief, including running order, content priorities, brand requirements and any moments where timing or presentation quality is more important than convenience.
Production-side ownership
The project manager owns coordination, schedule control and the overall delivery picture. The stage manager owns show flow, presenter readiness, cues and the live instruction path. The sound engineer owns microphone, playback and audio system decisions, handing tested inputs and known issues to show control.
The lighting designer owns the visual lighting plan and the operating requirements needed to achieve it. The video technician owns presentation playback, screen outputs, switching, recording or streaming elements included in the brief. Each technical lead should report exceptions early, not wait for a fault to become visible in front of the audience.
Venue-side ownership
The venue contact owns access arrangements, building constraints, approved working methods and coordination with venue operations. They're not merely a person who opens a door. Under the HSE duty-holder approach, co-operation, competence, risk information and monitoring sit within the wider event control system. Practical guidance on event management risk compliance is useful when those responsibilities need to be made explicit between parties.
A venue contact may also hand over restrictions on rigging, power, noise, loading, fire routes or working hours. The production manager then makes sure those constraints reach the relevant technical lead and appear in the working plan.
For a clearer explanation of the technician's place in this chain, the AV technician role and its event responsibilities is a useful reference. The role is practical, but it still depends on knowing where technical execution ends and production authority begins.
Production Roles and What They Actually Do
Technical roles become easier to manage when each lead receives the same four-part brief: what the event must achieve, what they own during setup, what they hand over during the show and what they must confirm before leaving site.
Consider a hybrid conference using two rooms and a live stream. The main room has presenters, confidence screens and audience microphones. The second room carries overflow content. The stream depends on reliable video feeds, clean audio and a stable show rhythm. A late change in one room can affect every other role.
Sound engineer
The sound engineer needs the session plan, speaker list, microphone requirements, playback sources, room layout and any remote contributor details. During setup, they own system deployment, input checks, gain structure, monitoring and the audio consequences of room changes.
During live delivery, the handoff is usually to the stage manager through cue readiness and clear status updates. If a presenter changes slides, adds a video or introduces a remote speaker, the engineer needs that information early enough to check playback audio and communication paths.
Breakdown responsibility includes identifying hired or venue-owned equipment, confirming faults and leaving the system safe for removal. The engineer doesn't own the running order, but they must tell show control when an audio change affects a cue.
Lighting designer
The lighting designer needs the room plan, stage dimensions, camera positions, scenic elements, speaker positions and any brand or presentation requirements. Their setup ownership covers fixture placement, focus, control, looks and safe working coordination with the venue and other departments.
For a streamed conference, the lighting plan must support the cameras as well as the audience. A lighting change that looks attractive in the room may create an exposure or colour problem on camera, so the lighting designer hands relevant changes to the video technician and stage manager.
At breakdown, they confirm which fixtures, stands, cables and control equipment belong to the production and which remain with the venue.
Video technician
The video technician needs the final presentation files, screen map, aspect requirements, playback list, camera plan, switching requirements and streaming destination information. They own signal paths, playback, screen outputs, switching and any recording or stream operation included in the brief.
In the two-room example, the critical handoff is between content, camera and show control. The stage manager calls the moment, the video technician executes the change and the sound engineer confirms whether the source carries audio. A remote presenter may require a separate check with the stream operator, client liaison and speaker support.
Stage manager
The stage manager needs the run sheet, cue language, presenter order, access plan, rehearsal notes, emergency contacts and authority to hold the show. They own the live sequence, presenter movement, backstage readiness and communication between the stage and technical departments.
The stage manager doesn't decide every technical method. They decide whether the show is ready to move to the next cue, based on status from the relevant leads. During breakdown, they confirm that presenters, crew and programme assets have cleared the operational area before de-rig proceeds.
Mapping Responsibility With RACI
RACI is useful because job titles rarely answer the question that causes trouble at the venue. A project manager may coordinate the event, but that doesn't automatically mean they can approve a safety decision, override a venue instruction or accept a technical compromise.
The four letters create a decision record:
- Responsible: The person completing or driving the work.
- Accountable: The person who owns the outcome and has authority to approve it.
- Consulted: The person whose expertise must inform the decision.
- Informed: The person who needs the result, but doesn't approve or execute it.
Use one accountable person for each decision. If two people are jointly accountable, the matrix usually needs a clearer escalation rule.
RACI matrix for a mid-size conference
| Decision | Project Manager | Stage Manager | Sound Engineer | Video Technician | Venue Contact | Client Liaison |
|---|---|---|---|---|---|---|
| Go or no-go on a video switcher failure | A | R | C | R | C | I |
| Late client change to the run sheet | A | R | C | C | I | R |
| Approval of final presentation files | A | C | I | R | I | R |
| Microphone or playback change during rehearsal | I | A | R | C | I | C |
| Decision to hold the show for a safety concern | C | R | C | C | A | I |
| Evacuation procedure and venue instruction | C | R | I | I | A | I |
The matrix is a starting point, not a substitute for a briefing. A video technician can be responsible for diagnosing a switcher failure, while the project manager remains accountable for the delivery decision. The venue contact stays accountable for venue emergency arrangements because that authority belongs to the site's control structure.
Keep it honest on the day
Review the matrix when staffing changes, the scope shifts or a supplier replaces a named lead. At the production meeting, ask each owner to confirm their decisions aloud. Then add the escalation route beside any decision that could stop the show.
For an intimate gala, combine roles where practical, but don't remove the responsibilities. One person may cover project management and client liaison, while the stage manager also coordinates the technical cues. A large activation may need separate leads for multiple zones, content, broadcast, rigging and crowd movement. The matrix should expand with the decision load, not with habit.
Sample Briefs for Different Event Types
The same role titles don't carry the same weight at every event. A conference usually prioritises repeatable timing and clear content flow. A product launch puts greater pressure on secrecy, visual impact and press handling. A charity gala needs a dependable programme around dinner service, speeches, auctions and guest experience.
The team shape should follow the failure that would hurt delivery most.
Corporate conference for 400 delegates
The core team includes a project manager, client liaison, stage manager, sound engineer, lighting designer, video technician and venue contact. Add presentation support where the programme contains multiple speakers, remote contributors or complex playback.
The project manager owns schedule and stakeholder control. The stage manager owns the running order. Sound and video leads own their systems, while the venue contact controls access, building rules and site coordination.
The critical handoffs are presentation collection to video, speaker readiness to stage management and venue restrictions to technical leads. The structure is driven by programme continuity. A small content change can affect confidence screens, playback, audio and the next speaker, so the client liaison must route it through the agreed process.
Product launch with press and live stream
The team needs the same core structure, but the brief gives more authority to video, content control and the client or agency producer. Press arrivals, embargoed material, camera positions, interview areas and stream requirements need clear ownership before load-in.
The agency producer owns the creative sequence and brand moments. The client liaison controls approvals. The video technician owns playback and switching, while the stage manager protects the live reveal and prevents unscheduled movement around the stage.
The important handoff is between approved content and live playback. The main risk is an uncontrolled change to a sensitive asset or camera position. That calls for a locked content version, a named approval route and a clear rule for what can change during rehearsal.
Charity gala with dinner and auctions
A gala may need fewer technical layers, but the stage manager and venue contact become particularly important. The programme must work around service, speeches, auction lots, music, guest movement and any awards or fundraising appeals.
The sound engineer owns speech intelligibility and playback transitions. The stage manager coordinates presenters, auctioneers and venue service timing. The client liaison handles last-minute changes from the charity or host, while the project manager protects the overall schedule and supplier coordination.
The main risk is a collision between hospitality and show flow. The handoff between venue operations and stage management must be active, with agreed signals for service pauses, presenter readiness and any change to the auction sequence.
Handoffs, Shift Changes and Common Pitfalls
Most event failures don't begin with a dramatic equipment fault. They begin when one person assumes another person has received, approved or acted on information. The four breakdowns below appear repeatedly because each sits between roles rather than inside one technical department.
Unclear go or no-go authority
A switcher fails during rehearsal. The video technician proposes a workaround, the client wants the original look and the stage manager is waiting for a decision. Without a named accountable person, the discussion spreads while doors approach.
The prevention is a short decision protocol:
- The technical lead states the fault, impact and workable alternatives.
- The stage manager states the next deadline affected.
- The project manager or named accountable owner decides whether to proceed, hold or change.
- The client liaison communicates the approved client-facing result.
- The stage manager records the decision on the run sheet.
Silent camera-plan changes
A camera moves during rehearsal because the original position blocks a presenter route. The change may affect lighting, sightlines, cable paths and the stream composition. If the video technician changes the plan without informing the lighting designer and stage manager, the show can remain technically functional while looking visibly unprepared.
Record camera positions, movement permissions and the person who approves changes. Any alteration should be called out during the rehearsal debrief, not passed through informal conversation.
Late vendor handovers during breakdown
A supplier leaves before confirming which cases, cables and accessories are ready for collection. Another vendor then starts removing equipment without knowing what remains live, what belongs to the venue or what must be preserved for the next session.
Assign de-rig responsibility by area. The handover should confirm equipment ownership, isolation requirements, collection status, damaged items and the person accepting the area.
Missing communication during rotation
Multi-day events and overnight work create a different risk. A crew member arrives with an incomplete understanding of changes made by the previous shift, while the outgoing person assumes the shared folder tells the full story. It rarely does.
Use a verbal handover supported by a written log. Include current system status, open faults, changes to the plan, welfare concerns, lone-working arrangements and the next decision deadline. The duty holder remains responsible for co-ordination, so communication can't be treated as a personal preference.
The production schedule guidance can help turn those handoffs into timed actions rather than loose intentions. A schedule should show who owns the check, when it happens and what evidence confirms completion.
A handover isn't complete when information has been sent. It's complete when the next person confirms they understand the current state and their next action.
Building a Responsibility Map for Your Next Event
Start with the duty-holder question: who owns the event outcome and who has authority to stop or change the work? That answer may sit with the organiser, production company, venue or a defined combination of parties. Write it down, then identify the people who must work under that structure.
Next, name the smallest viable team for the actual brief. Don't copy the staffing pattern from a larger event. Keep the responsibilities even when one person covers several roles, and check that combined duties don't create a conflict during critical moments.
Four steps to a usable map
- Define the deliverables. List the show, room, stream, presentation, audience and venue outcomes that must work.
- Name the owners. Assign the project, stage, sound, lighting, video, client and venue responsibilities.
- Map the handoffs. Note what each lead receives, what they produce and who confirms acceptance.
- Set decision points. Add deadlines for content lock, rehearsal approval, safety review, show readiness and de-rig.
The load-in file
By load-in, the responsibility map should be supported by a compact set of working documents:
- Contacts sheet: Names, roles, mobile numbers and escalation order.
- RACI matrix: The six key decisions, including show readiness, client changes, technical faults and evacuation.
- Run sheet: Timings, cues and a named owner for every operational action.
- Risk assessment sign-off: Identified controls, responsible parties and approval status.
- Emergency contacts: Venue, duty holder, first aid and relevant escalation details.
- De-rig plan: Equipment ownership, isolation requirements, collection arrangements and area sign-off.
Run one final communications test before doors. Confirm the primary channel, backup channel, call signs or naming convention, who monitors urgent traffic and how a safety instruction reaches every crew member. In hybrid teams, also record who is working remotely, who can approve changes and how performance or support issues are raised, rather than leaving those expectations implied.
London Audio Visual Hire can support event planning with project management, sound, lighting and video technicians, helping clients define responsibilities from the initial brief through to final de-rig. Visit London Audio Visual Hire to discuss the technical team shape and handoff plan for your next event.
