How WireFlow fits into preproduction
Where documentation lives between sales handoff and load-in — and why doing it early prevents show-day fires.
When to use this
Read this when planning how WireFlow slots into your shop's prep timeline — sales → design → bench → site.
The preproduction gap
After the quote is signed, most teams still jump straight to packing cases. The gap — documented signal path, rack faceplates, LED processor maps — is where mistakes compound.
WireFlow is meant to close that gap: one living document set that updates when the client adds a playback machine or the wall grows by four cabinets.
Suggested prep phases
- Phase 1 — Scope: rough diagram with major devices (switcher, cameras, LED processor, audio console)
- Phase 2 — Detail: port-level connections, rack elevations, wall layout with cabinet count
- Phase 3 — Validate: walk power and network paths; confirm processor port limits and cable labels
- Phase 4 — Freeze: export tech pack, share view-only links, print rack pages for the road case
- Phase 5 — As-built: note on-site changes; update project after strike if the rig repeats
Why it matters on show day
Venue techs, freelancers, and client reps work from whatever you send them. A clear diagram reduces "which HDMI is program?" on comms.
When the LED tech knows data path and power circuit before the wall is on the ground, you lose fewer hours to re-patching.
Tip: Freeze documentation 24–48 hours before load-in when possible — then only push critical changes through the same share link.
Common mistakes
- Building the diagram only after gear is on the truck
- Keeping rack patching in someone's head instead of in Rack Builder
- Sending a screenshot instead of a share link — crew sees stale revs
- Skipping wiring plans because "everyone knows the rig" — they don't on a new venue