Credits: Deckmatics
Deckmatics
Deckmatics vector SVG generated on this page.
Live operations: load-in, line check and changeover
Show-day operations: load-in, cable paths, patch, line check, soundcheck and artist/DJ changeovers, with responsibilities, timings and common mistakes.
Show day is a sequence of few decisions and many actions: load, lay cables, patch, test, open, change and change again. When a night goes wrong, it almost never reflects mixing talent; the transition between phases failed because someone assumed the previous phase was complete.
This guide covers operations in six pieces: load-in, cable paths, patch, line check, soundcheck, changeover and DJ changeover. Every event shares these stages, from club to festival, and written routines outperform improvisation.
The show day
The day starts before the first case arrives: crew assembled, schedule distributed and responsibilities confirmed. Production explains the morning plan, technical direction clarifies testing order and the stage manager defines who works where. Five briefing minutes avoid two hours of scattered questions.
Keep a single source of truth: the show schedule with actual times. Mark each phase’s start and finish, deciding immediately where a delay will be absorbed. This pacing control distinguishes finishing on schedule from improvising the close.
Establish who communicates changes too. Separate approvals through each department’s channel produce contradictions; one production voice lets everyone else execute.
| Phase | Reference duration | Typical mistake |
|---|---|---|
| Load-in | 60 to 180 minutes | Disorganised unloading and poorly allocated access |
| Patch and line check | 20 to 45 minutes | Outdated input list and crossed channels |
| Soundcheck | 30 to 60 minutes | Tests without a time limit |
| Changeover | 10 to 30 minutes | Next artist's equipment out of position |
| DJ changeover | 5 to 15 minutes | Unchecked libraries or backups |
Reference duration and most common mistake in each phase
Load-in and cable paths
Load-in is organised by access: which truck unloads, in which order and into which zone. Equipment goes to its final destination rather than the middle of a corridor: stage cases to stage, consoles to booth, storage to storage. “Unload first, move later” is the fastest way to lose half an hour.
Define cable paths before laying: each cable family’s origin and destination, protected crossings, public-area routes and locations needing ramps or channels. Three rules solve most problems: separate audio from power, protect anything stepped on and label both ends.
Clear routes remove negotiation from cabling. Decide what gets laid now and what waits until after soundcheck too: laying cables through a test guarantees repeated work.
Patch and line check
The patch physically translates the input list: each signal enters its stage channel, reaches its destination and is documented. Follow the patch list with the right two people, one connecting and one verifying, because a patch error gives no warning: sound appears, but in the wrong place.
Line check then proceeds channel by channel: send a signal, listen at its destination, confirm name, level and polarity. Deliberately mechanical. Skipping a channel to save time makes it reappear during soundcheck, with people already waiting.
Documenting line-check changes from the patch list lets the rest of the team work without checking everything again.
Soundcheck
Soundcheck is the musical test with the artist: stage mix, monitor sends, overall level and verification of playback tracks. The goal is a valid starting point and outstanding-task list rather than perfect show sound.
Unlimited time is the greatest risk. Manage blocks: critical channels, overall balance, artist changes and close. Record unresolved work for changeover: extending tests does not improve results, only exhausts patience.
At the end, establish the reference level and protect the console: nobody changes base gain without notice. A written number prevents starting the night at a different volume.
Soundcheck also tests silent elements: light cues, video inputs, backing tracks and opening effects. With the artist present and no audience, checks cost minutes; afterwards, they cost an incident. Respond to off-plan requests with what remaining time permits rather than promises impossible once doors open.
Changeover
Changeover is the interval between artists: remove, position, patch new equipment and quickly verify. Plan duration and responsibilities in the run of show, rehearsing at least once during the day when several changes are scheduled.
Costly changes require system redesign. If artists enter on their own patch or a planned configuration, changing means replacing rather than rebuilding. That is where preproduction earns its earlier savings.
A solid changeover assigns four tasks: removal, connection, verification and timekeeping. Clear responsibilities allow parallel rather than sequential work, making the clock less threatening. Finish with minimum checks—signal, level and safety—before reporting stage readiness.
The stage manager directs the change, tracks time, calls critical minutes and decides when it is acceptable. A change that succeeds but leaves disorder makes the next one pay.
DJ changeover
DJ changeover moves between DJ sets: players or laptop, mixer, libraries, cue points, screens and power. Checks are short and specific: audio through both channels, powered screens, active cue lights, local backup and protected starting level.
Never assume the library. Check startup using an artist’s own USB or laptop before leaving; with venue equipment, confirm tracks and mappings match expectations. None of this is negotiated while an audience waits.
A good DJ changeover has a written checklist, fixed order and one responsible person. At festivals, the DJ technician accompanies the change while the previous booth packs up so the tasks do not compete.
Keeping pace: from show schedule to execution
The phases work only when timing is watched live. Actual starts and ends reveal deviations while correctable and feed incident records explaining events afterwards. The schedule plans; execution confirms.
Synchronisation systems help when video, light and music share clocks: timecode, show-control protocols or musical network links. Explore synchronisation and show-control protocols and synchronisation with ShowKontrol and Pro DJ Link.
Once executed, close the day calmly: pack, document and back up before anyone leaves.
Next step
When plans meet reality, you need a method: handover, last-minute changes and show incidents explains handing over stages between artists, absorbing changes and recording incidents.
Frequently asked questions
What is the difference between line check and soundcheck?
Line check confirms each channel sounds in the right place; soundcheck is the musical test with the artist, stage levels and final adjustments before opening.
Who directs load-in?
Production and the stage manager allocate access, unloading order and crew, following the technical advance.
What is a cable path?
The planned cable route between stage, consoles and booths, with distances, protection and crossings defined before laying cables.
How long is a well-prepared changeover?
Between five and fifteen minutes depending on the event, provided the next artist's equipment is positioned and the patch is planned.
What is checked during DJ changeover?
Players or laptop, mixer, power, cue points, libraries, screens and booth audio, plus startup order and ready backup.
Continue learning
Start here if these concepts are new to you
Related guides
Sources
- Clear-Com — Intercom y comunicaciones de producción
Intercom documentation underpinning coordination between load-in, testing and changeover phases.
- AJA Video Systems — Soporte
Video conversion and distribution support, a reference for connections and signal testing throughout the day.
- OBS Studio — Knowledge base
OBS knowledge base for setting up and verifying broadcast systems linked to show operations.
- SMPTE — Estándares
Time standards supporting clocks and timecode for synchronising phases, cues and changes.
Last technical review: 01/10/2026. Please report any errors so they can be corrected.