LED Wall Preproduction Checklist: What to Confirm Before the Truck Leaves
By WireFlow Team · Published 2026-07-11 · Updated 2026-07-11 · 10 min read
Before an LED wall ships, six things have to be locked: the design (dimensions, pitch, resolution, processor capacity), the power advance, the data plan, the rigging or ground-support plan, spares and logistics, and the paperwork every other department is waiting on. This checklist walks each phase in order, what to confirm, and who has to answer. Any line that's still a guess when the truck leaves becomes a show-day problem with a show-day price tag.
How to use this checklist
Work the phases in order, because each one feeds the next: you can't advance power until the design is locked, and you can't finish the paperwork until power, data, and rigging have real answers. The six phases:
- Design lock, wall size, pitch, resolution, and processor capacity frozen against the room
- Power advance, draw, circuits, connectors, and where the power actually is
- Data plan, panels per port, backup paths, real cable-run lengths
- Rigging / structure advance, flown vs. ground-stacked, weights, and the sign-offs you collect
- Logistics, spares, cases, and the truck pack
- Paperwork, the documents every other team needs from you
The dividing line between planning documents and show-day documents matters here, the planning vs. show day guide covers which is which. Everything below is planning work: cheap to change now, expensive to change at load-in.
Phase 1, Lock the design against the room
Every downstream phase re-opens if the wall changes size. Lock the design first, in writing, and treat any later change as a change order, not a tweak.
- Confirm wall dimensions against venue sightlines. Overlay the wall on the venue section drawing: seating rake, balcony overhangs, header heights, and anything (truss, tabs, columns) that clips the view from paid seats.
- Check pixel pitch against the closest viewer. The closest paying eyeball drives the pitch decision, not the average seat, the front row sees pixels the back row never will.
- Compare content resolution to wall resolution. The wall's pixel count is exact math from panel resolution and cabinet count. Content rendered at anything else gets scaled, and scaling is where crisp graphics go soft.
- Confirm processor pixel capacity and port count. The processor has to carry the full wall's pixel count, with enough ports to feed every string, verify against the final wall size, not the size from two revisions ago.
A common industry rule of thumb, treat it as a rough starting point, not a spec, puts minimum comfortable viewing distance in meters at roughly the pixel pitch in millimeters, so a 3.9 mm wall starts to look clean from around 4 m back. Content type and lens choices move that number in both directions; the pixel pitch and resolution guide covers the real trade-offs.
Phase 2, Advance the power before anything ships
Power is the advance item most likely to be answered with "yeah, we have power." That is not an answer. Get specifics:
- Total maximum draw for the final wall size. Size to max draw (full-white worst case), not average, bright content on an average-sized feed is how breakers trip mid-show. The LED wall power math walks the calculation line by line.
- Circuit count and breaker sizes. How many circuits the wall needs at what rating, versus what the venue actually has where you need it.
- Connector types at the tie-in. Camlock, PowerCON, twist-lock, confirm exactly what's on the venue end, so adapters get built in the shop instead of improvised on site.
- Where the power physically is. Distance from tie-in to wall position drives feeder lengths and voltage-drop questions. "Stage left" can mean 15 m or 60 m.
- Generator vs. house power. If it's a generator: who supplies it, who supplies distro, when it's energized, and fuel/runtime for the full show day, not just the show.
Phase 3, Plan the data before the cable is cut
- Panels per port, inside the processor's limit. Every processor port carries a finite pixel count, and that ceiling, not the physical connector count, decides how many panels each string can hold. The full math is in how many panels can be daisy-chained.
- Backup data paths. If the processor and panels support redundant or loop data, decide now which strings get it. Many crews pull a spare data line with every main run as standard practice, it's cheap on the ground and miserable to add at trim height.
- Real cable-run lengths. Measure along the actual route, up the truss, around the proscenium, through the cable pick, not the straight line on the plot. Short cables discovered at load-in cost hours.
- Where the processor lives. FOH, dimmer beach, or backstage changes run lengths, who can reach it during the show, and how long the failure-to-fix walk is.
Phase 4, Advance rigging and structure with the people who own it
This is the phase where the checklist's job is to collect sign-offs from qualified people, not to generate them. Confirm:
- Flown or ground-stacked, decided with the venue and rigger, not assumed from last year's file photo.
- Total flown weight, including frames, bumpers, motors, and cable, broken out as per-point loads on a rigging plot, matched against the venue's rated points.
- Ground stacks: floor or stage loading, ballast or outrigger requirements, and whether the deck under the wall was ever rated for it.
- Outdoor walls: the wind plan, monitoring, thresholds, and who makes the call to bring it down, agreed before the wall goes up.
Phase 5, Spares, cases, and the truck
- Panel spares. Many touring vendors carry roughly 5–10% of the panel count as spares, ideally from the same production batch so color matches under camera. Confirm what your shop or rental partner actually sends, and where in the pack it rides.
- The small stuff that kills walls: spare receiving cards, spare data and power jumpers, and any field-swappable modules or supplies for your panel type. A wall is more often down for a $30 card than a broken cabinet.
- Dolly and case count vs. truck space. Count cases against the pack list, and make the case labels match the paperwork, "LED 7 of 22" beats "the black one."
- Pack order. First-needed comes off first: rigging hardware and motors before panels, panels before processors, spares case somewhere you can reach without unloading the show.
Phase 6, Paperwork: what every other team needs from you
The wall touches four other departments before it shows a single pixel. Each one needs a document, and every document should come from the same locked design, not from four separately maintained spreadsheets:
| Document | What it contains | Who needs it |
|---|---|---|
| Pixel map | Exact wall resolution, origin, panel offsets | Media server / content team |
| Power plot | Circuits, draw per feed, connector types, tie-in location | Venue electrician / power vendor |
| Data map | Processor ports → panel strings, entry points, redundancy | LED techs on site |
| Rigging plot | Points, per-point weights, trim heights | Rigger / venue |
| Contact sheet | Names and numbers for every department lead | Everyone, taped inside the workbox lid |
Bundle the set into one packet so nobody works from a stale revision, the AV tech pack guide covers assembling diagram, gear list, and cable schedule into a single crew-ready document. If the wall design lives in WireFlow, the pixel map, power load, and data paths export from the same wall spec you locked in Phase 1.
What we'd check on site, day-of
The advance is done; this is the short list we actually run on the morning of load-in:
- Verify the tie-in is where the advance said it is, before the feeder comes off the truck.
- The electrician meters the feed before distro energizes. No meter, no power-up.
- Find the spares case and stage it at the wall, not in the truck.
- Bring the wall up on the full pixel map with a test pattern before content rehearsal, mapping errors found during rehearsal cost everyone's time, not just yours.
- Walk the wall after trim: dead panels, receiving-card dropouts, seams that don't sit flush.
- If you fitted data redundancy, pull a main line on purpose and watch it fail over. Untested redundancy is decoration.
Frequently asked questions
- What should an LED wall site survey cover?
- Four things at minimum: sightlines (where the closest and worst seats actually are), power (tie-in location, capacity, connector types), structure (rig points or floor capacity, with the venue's numbers), and access (dock, ramps, elevators, and the path the dollies actually roll). Photograph everything, the survey photo of the tie-in settles a lot of advance-call arguments.
- How far in advance should the LED wall advance happen?
- Start as soon as the wall size is roughly known, and have power, rigging, and data answers locked before the gear is prepped, changes are nearly free while the wall is still a drawing and get expensive the day the truck is packed. Venue-dependent items like tie-in details and rig-point ratings often take the longest to get answered, so ask for those first.
- How many spare LED panels should I bring?
- There's no universal number, but many touring vendors carry roughly 5–10% of the panel count as spares, plus spare receiving cards and data/power jumpers, the small components fail more often than cabinets. Confirm the actual spares kit with your vendor during the advance rather than assuming.
- Who signs off on rigging and floor loading for an LED wall?
- A qualified rigger or structural engineer, working with the venue's own load data. The video crew provides accurate weights and the rigging plot; the sign-off itself comes from the people qualified and authorized to give it. If nobody on the call can say who that person is, that's the first problem to solve.
- What does the media server team need from the LED team?
- The pixel map: the wall's exact resolution, its origin point, and any offsets or irregular regions, plus the processor's input format expectations. Send it as soon as the design locks, content is built to the map, and a late map change means re-rendering content, not just re-patching cable.
Calculate your LED wall in WireFlow
Pick a panel, set the wall size, and get cabinet counts, pixel map, power load, and data paths, before anything ships to site.