Skip to the production journey
BEHINDTHE SHOWLive Production,
Explained.

Start here / Live production

New to Live Production?
Start Here.

A live show begins long before the audience arrives.

An event brief becomes a production plan. Artists bring requirements. Venues impose constraints. Equipment has to be specified, prepared and moved. Crews build the systems, performers soundcheck, the show runs, and everything eventually has to come back down again.

Behind The Show explains each part of that process.

This page shows you how the pieces fit together before you explore them in detail.
01

The brief

What are we actually producing?

Every production starts with understanding the event.

Before choosing equipment, establish:

  • event type
  • audience
  • venue
  • programme
  • performers
  • timings
  • creative expectations
  • technical requirements
  • budget
  • responsibilities

A concert, corporate presentation, festival and private performance may all use sound, lighting and video, but they do not require the same production.

02

The venue

Where does the show have to work?

The venue changes the production.

A ballroom, arena, theatre, outdoor ground and club each create different considerations.

These may include:

  • audience capacity
  • stage dimensions
  • rigging
  • power
  • loading access
  • noise restrictions
  • sightlines
  • ceiling height
  • weather
  • internet
  • working hours
  • venue rules

The production plan has to work within the physical and operational reality of the venue.

03

The artist & technical rider

What does the performance require?

Artists and their technical teams communicate performance requirements through documents such as:

  • technical riders
  • stage plots
  • input lists
  • backline requirements
  • lighting requirements
  • video requirements

A rider is not simply an equipment order.

It needs to be reviewed against:

the venue + local inventory + production design + show schedule.

Where something cannot be supplied exactly, the requirement may need clarification or an approved alternative.

Connected knowledge / Technical Riders
04

Production design

Turn the requirement into a technical plan

Once the event, venue and artist requirements are understood, the production can be designed.

The major disciplines may include:

Sound

Capture, mix, monitor and reproduce audio.

Lighting

Make performers and environments visible while supporting the creative design.

Video

LED, projection, playback, cameras and visual content.

Staging

Stages, risers, structures, scenic elements and physical working areas.

Backline

The instruments, amplifiers and performance equipment musicians use on stage.

Power

Provide safe and appropriate electrical distribution for the systems that require it.

These disciplines are connected.

A decision in one area can affect several others.

Fig. 01 / BTS–START–001

From brief to show

  1. 01Event brief
  2. 02Venue + artist requirements
  3. 03Production design
  4. 04Equipment + people + logistics
  5. 05Load-in + setup
  6. 06System checks
  7. 07Soundcheck / rehearsal
  8. 08Show
  9. 09Strike + load-out
  10. 10Return + QC
A simplified view of the live-production lifecycle. Actual workflows overlap and vary according to the show, venue, artist and production structure.
05

People

Equipment doesn't produce a show by itself

Live production depends on people with different responsibilities.

Depending on the scale of the event, these may include:

  • producer
  • production manager
  • technical director
  • sound engineers
  • monitor engineer
  • system engineer
  • lighting designer/operator
  • video team
  • stage manager
  • backline technicians
  • RF technicians
  • riggers
  • stagehands
  • warehouse teams
  • drivers
  • runners
  • venue technical teams

Not every show requires every role.

What matters is that responsibilities are understood.

06

Equipment

Specify what the show actually needs

The equipment requirement should now emerge from the production plan.

AudioPA, consoles, microphones, DI boxes, monitors, wireless systems.

LightingFixtures, consoles, truss, rigging and control.

VideoLED, projection, processors, playback and cameras.

BacklineDrum kits, guitar amplifiers, bass rigs, keyboards and percussion.

StagingStages, risers, structures and scenic requirements.

The objective is not to create the longest equipment list.

It is to specify the right system for the production.

07

Logistics

The equipment still has to reach the show

Production planning also means answering practical questions:

  • Where is the equipment coming from?
  • When can the venue be accessed?
  • How long does unloading take?
  • Is there a loading dock?
  • Are freight lifts available?
  • Where can cases be stored?
  • How many crew members are needed?
  • When must each department be ready?
  • What happens between performances?
  • When can equipment leave?

Transport, access and scheduling are part of production design because they determine whether the technical plan can actually be executed.

08

Load-in

The production enters the venue

Load-in is the period when equipment, crew and production infrastructure enter the venue and installation begins.

A well-planned load-in considers:

  • departmental sequence
  • access
  • safety
  • rigging
  • stage readiness
  • power
  • cable routes
  • equipment positioning
  • dependencies between teams

Some systems cannot be completed until another department finishes its work.

The schedule needs to understand those dependencies.

09

Setup & system checks

Build it, then prove that it works

Equipment arriving at the venue is not the same as a system being ready.

Teams need to:

  • assemble
  • position
  • connect
  • configure
  • test
  • troubleshoot
  • verify

Audio systems may require system checks and line checks.

Lighting systems need addressing, patching and testing.

Video signal paths need verification.

Backline needs setup and functional checks.

The objective is to find problems before performers depend on the system.

10

Soundcheck & rehearsal

Now the performers enter the system

Soundcheck allows the artist and technical teams to confirm that the stage setup works for the performance.

This can include:

  • instrument setup
  • backline adjustments
  • input checking
  • monitor mixes
  • FOH balance
  • playback
  • RF
  • lighting cues
  • video cues
  • stage positions

Soundcheck is not the ideal time to discover unresolved rider questions.

Those should have been handled during the advance.

11

The show

Production becomes invisible

During the performance, the production team operates the systems and responds to what happens in real time.

Good production should allow the audience to concentrate on the event rather than the technology behind it.

The equipment, preparation and planning remain essential.

They simply stop being the audience's focus.

12

Strike & load-out

The show ends. Production doesn't.

After the audience leaves, the production has to come apart safely and systematically.

Strike is the process of dismantling the production.

Load-out moves equipment out of the venue.

The sequence still matters.

Teams may need to coordinate:

  • equipment shutdown
  • cable removal
  • backline packing
  • lighting and video removal
  • rigging
  • case movement
  • inventory checks
  • vehicle loading
  • venue handover

Fast does not mean uncontrolled.

13

Return & QC

The production lifecycle ends back at the inventory

Rental equipment returning from a show should not simply become "available" again.

It may need:

  • return scanning
  • quantity verification
  • condition inspection
  • functional testing
  • cleaning
  • charging
  • repacking
  • quarantine
  • repair
  • missing-item follow-up

This is where one production connects to the next.

14

The whole picture

Live production is a system

No single department creates the show.

The process connects:

requirements → decisions → equipment → people → logistics → execution → recovery

The precise workflow changes with every production.

The principle does not:

Understand the requirement before trying to solve it.
Where to go next

Start with a Knowledge Field