How to Create an AV Signal-Flow Diagram

What is an AV signal-flow diagram?

A signal-flow diagram shows how signal moves through a system: every device, every connection between devices, and the direction the signal travels. Unlike a floor plan, it ignores where gear physically sits. Unlike a rack elevation, it ignores what the gear looks like. It answers exactly one question, what feeds what, and answering that question precisely is what makes every other show document possible.

The test of a good diagram is brutal and simple: a competent tech who has never seen the system should be able to build it, or trace a dead path through it, using the drawing alone. If they'd need to call you, the diagram isn't done.

Step 1, Inventory the system before you draw anything

Every wasted hour in diagramming comes from drawing while discovering. Separate the two. First, list every device that touches signal, sources, processing, destinations, and the infrastructure between them:

• Sources, cameras, playback machines, laptops, media servers, microphones, wireless receivers
• Processing, switchers, mixers, DSPs, scalers, matrices, LED processors, encoders
• Destinations, displays, LED walls, projectors, speakers, recorders, streaming endpoints
• Infrastructure, DAs, converters, extenders, network switches, patch panels, stage boxes

For each device, note its relevant inputs and outputs and their connector/signal types, the specific ports you'll actually use, plus spares worth showing. This is exactly the information a port-aware tool stores in its device library; in WireFlow each device template carries its real ports so you define them once, not per drawing.

Step 2, Lay out left to right, source to destination

Signal flow reads like a sentence: sources on the left, processing in the middle, destinations on the right, so signal travels left-to-right and anyone can scan the story of the system. Group related devices into visual lanes, video path, audio path, network/control, and keep each lane roughly horizontal.

1. Place your primary switcher or mixer at center, it's the heart the rest of the system organizes around.
2. Add sources in a left column, roughly ordered by importance (Cam 1 at top, guest laptop lower).
3. Add destinations in a right column, program displays, records, streams, monitors.
4. Slot infrastructure (converters, DAs, extenders) between the devices they actually sit between.
5. Leave more whitespace than feels necessary, wire routes need room, and systems only grow.

Step 3, Draw connections port-to-port, never box-to-box

This is the step that separates documentation from decoration. A line from "Camera 1" to "Switcher" records an intention. A line from Camera 1 · SDI OUT 1 to Switcher · SDI IN 3 records a buildable fact, and exposes the problems while they're still cheap:

• Format mismatches surface immediately, the laptop's HDMI output aimed at an SDI input now visibly needs a converter, which means the converter makes the gear list.
• Input counts become real, five sources drawn into a four-input switcher fails on the page instead of at load-in.
• Every drawn connection becomes a row in the cable schedule with real endpoints, see How to build a cable schedule.

This is also where connection-aware software earns its place over generic drawing tools: WireFlow knows an SDI output can't legally land on a Dante port and blocks the patch, while a generic tool will happily draw any line between any two rectangles. The diagram stops being a picture of your plan and starts being a check on it.

Step 4, Label cables and signals so the diagram survives contact with the crew

Every connection needs two pieces of text: a cable ID (unique, permanent, matching the physical label heat-shrunk on the cable) and a signal name (what's on the wire, "PGM A", "Cam 2 ISO", "Lectern Mic 1"). The ID is how you find the cable; the signal name is how you reason about the system.

Keep IDs dumb and stable, the ID names the cable, not the patch. If V007 gets repurposed mid-tour from a camera feed to a teleprompter feed, its ID doesn't change; its signal-name entry in the documentation does. Naming schemes that encode the destination into the ID die the first time anything gets re-patched.

Step 5, Walk every path before you call it done

A diagram is verified the same way a system is: trace each signal from its source to its final destination and confirm every hop is possible. For each major path ask:

1. Does every connection land on a port that actually exists and is actually free?
2. Is every format transition handled, HDMI→SDI, analog→Dante, resolution/frame-rate changes?
3. Do the record and stream paths work if the program path dies? Where are the single points of failure?
4. Does anything on the drawing exceed a real-world limit, input counts, cable-length limits for the format, switch port counts?
5. Could a stranger build this? Every device named, every port labeled, every cable ID assigned?

In WireFlow, signal tracing is built in, select a device and walk its upstream and downstream paths, and the same verified diagram then exports the gear list and cable schedule, so documentation stays consistent because it's derived, not retyped.

Keep it alive: proposed vs. as-built

The drawing you plan from is the proposed diagram. What actually got built, after the venue's house patch turned out different and Cam 3 moved to a longer lens position, is the as-built. Update the diagram during or immediately after load-in while the changes are fresh, and version it: the as-built is what you hand the client, and it's the drawing that makes the *next* show at that venue start from truth instead of memory.

Frequently asked questions

What's the difference between a signal-flow diagram and a wiring diagram?

In AV practice the terms overlap heavily. "Signal flow" emphasizes the logical path, what feeds what, in what order. "Wiring diagram" emphasizes the physical connections, ports, cables, and IDs. A good port-to-port diagram is both at once, which is why one drawing can drive the cable schedule and the troubleshooting session.

What software should I use for AV signal-flow diagrams?

Any tool beats no tool, and generic diagramming apps (Visio, Lucidchart, draw.io) can produce box-and-line drawings. Purpose-built AV tools add the things generic tools can't: port-level device models, connection validation, and cable schedules/gear lists derived from the drawing. See our honest comparison in Best AV wiring-diagram software.

Should audio and video be on the same diagram?

Same project, and usually the same drawing organized into lanes. Splitting systems across disconnected files hides exactly the cross-trade links, embedders, de-embedders, streaming audio feeds, where shows actually break. Split into multiple pages only when a single view stops being readable.

How detailed should the diagram be?

Port-level for every connection you expect a human to build or troubleshoot. Summarize only what is genuinely atomic from the system's point of view (you don't draw the inside of a stagebox). If someone will plug it, patch it, or trace it, it's on the diagram.

Build this diagram in WireFlow

Port-aware devices, validated connections, and exports your crew can read on site. Free plan includes three editable diagrams, no credit card.

Start a free diagram · Explore the sample show first