The build sequence and why the order matters
Load-in follows a fixed sequence for good reasons. Power distribution goes in first, because nothing else can be tested without it. Rigging follows, because kit cannot go in the air until the structural points are confirmed, the motors are up, and any truss is in position. Staging goes in before any AV infrastructure is laid on it. Then cabling runs across the installed floor surface rather than have staging built over cables that were laid first. Hardware follows cabling. Lighting states get programmed once the physical rig is complete. Audio is tuned to the room with the staging in place, because the room acoustic changes when a large stage is installed. Technical rehearsal is the final stage, run at performance volume and with all content in the timeline.
When agencies push to run steps in parallel to recover schedule, the risk is usually worth taking on some steps and not others. Cabling can run alongside staging install if the teams are coordinated. Lighting programming can begin while audio testing runs in a different part of the room. But trying to run a technical rehearsal before the audio system has been tuned to the room produces a rehearsal that does not reflect what the event will sound like.
The agency PM role during load-in
The PM role during load-in is logistics and communication, not creative direction. The technical director owns the rig. The PM owns the relationship with the venue, the content delivery from the creative team, the client approval process, and the schedule. Those four responsibilities are more than enough to occupy a full working day during a major load-in, and conflating them with the technical role creates confusion on the site team.
The most effective agency PMs during load-in are the ones who are clear about what they need to know and when. A check-in with the TD every ninety minutes is usually sufficient. Both parties need to understand what the milestone gates are: what needs to be complete by what time for the schedule to hold. If a gate is missed, the PM needs to know immediately, not at the next scheduled check-in.
The productions that go wrong are almost always the ones that skipped the technical walk-through because the schedule was running forty minutes late. Forty minutes during load-in is recoverable. A walk-through that does not happen is not.
When the schedule slips: what to prioritise
Schedule pressure during load-in almost always comes from delayed venue access, late content delivery, or an unexpected venue constraint discovered on site. When time is short, the hierarchy of priorities is: audio system tuned and functioning, presentation content playing correctly on all screens, confidence monitors and presenter comms tested, lighting atmosphere states programmed. Specialist lighting programming, fine-tuning of speaker positions, and any aesthetic adjustments come last.
Getting explicit agreement from the client or account lead on the minimum acceptable state is a conversation worth having before load-in, not during it. If the event can run with basic lighting atmospherics and a fully tuned PA, and the elaborate gobo programming is aspirational, knowing that in advance means the TD can make sensible calls without escalating every decision.
The sign-off process that protects you and the client
A formal sign-off process at the end of load-in is standard practice and worth reinforcing at every event. The four stages are: technical check (every piece of equipment in the rig operating correctly, all content playing on all outputs), lighting state review (the account lead or creative director walks the room and confirms the lighting atmospherics), sound check with any live talent or speakers, and a final walk-through with the client representative before doors open.
The walk-through is not about reassurance. It is about identifying anything that needs to change while there is still time to change it. A client who sees the room for the first time and asks for the stage to be moved two metres to the left on walk-through is a problem that sign-off cannot solve. A client who approved the staging design six weeks earlier, watched a technical rehearsal recording, and walked the room ninety minutes before doors is in a position to make any final adjustments that are within the scope of what the schedule allows.
Working on a production with a tight load-in window?
Send us the schedule and we will tell you whether it is achievable and where the risk points are.
Frequently asked questions
How long does a typical AV load-in take for a large corporate event?
For a 400 to 600 person corporate event with a full PA system, staging, LED wall, and lighting rig, allow a minimum of eight hours from venue access to technical rehearsal. Ten to twelve hours is more comfortable for an event with bespoke scenic elements or a complex content workflow. Less than six hours for a rig of this scale creates risk that most experienced TDs would want to document and escalate.
Who is responsible for content delivery during load-in?
Content delivery is an agency responsibility, not a production company responsibility. The production company needs content in the agreed format by the agreed deadline. What that means in practice is that the agency PM must confirm with the creative team that all files are export-ready before load-in begins, and that there is a named person responsible for delivering updates if anything changes.
What happens if content arrives late?
Late content is absorbed into the technical rehearsal window, which means the rehearsal is compressed or removed. A compressed rehearsal increases risk. The TD will advise on what is and is not achievable given the available time, but the decision about how to proceed belongs to the agency and the client.