How to Create an Input List for Live Sound

An input list (also called a channel list) is the document that tells the sound engineer exactly what is plugged into every channel of the mixing console. It is the backbone of a smooth soundcheck — paired with your stage plot, it gives the production team everything they need to patch your band before you even arrive.

This guide walks through building a clean, professional input list from scratch, whether you are a solo performer with a vocal and a guitar or a full band running playback and in-ear monitors.

What Is an Input List?

An input list is a numbered table. Each row is one console channel, and each channel maps to a single source on stage — a microphone, a direct box (DI), or a line from a playback rig. A typical row contains the channel number, the source (e.g. "Lead Vocal" or "Kick"), the microphone or DI, whether it needs phantom power, and the stand type.

The engineer reads your input list from top to bottom and patches the stage box accordingly. A clear list means faster line checks, fewer surprises, and more time for an actual soundcheck.

Input List vs. Stage Plot

These two documents work together but answer different questions:

Both are usually included in your tech rider. Send them together.

Step-by-Step: Building Your Input List

Step 1 — List Every Source

Start by writing down every sound that needs its own channel. Walk the stage in your head: drums (kick, snare, hats, toms, overheads), bass, each guitar, keyboards, every vocal mic, plus any click, playback, or backing tracks. Do not forget utility channels like a talkback mic or an ambient room mic if you use them.

Step 2 — Put Channels in a Logical Order

Engineers expect a conventional channel order. The most common layout is:

  1. Drums — kick, snare top, snare bottom, hi-hat, toms, overheads
  2. Percussion
  3. Bass — DI and/or mic
  4. Guitars
  5. Keys and synths (often stereo)
  6. Lead and backing vocals
  7. Playback, click, and tracks

Numbering in this order makes your list instantly readable to any engineer who opens it.

Tip: Group stereo sources — keyboards, playback, and tracks — into left/right pairs and keep them on adjacent channels. It keeps the patch tidy and prevents an accidental mono fold-down.

Step 3 — Choose a Mic or DI for Each Channel

Assign a capture method to every source. Dynamic mics (like an SM57 or SM58) suit loud sources and vocals; condensers suit overheads and acoustic instruments; DI boxes suit bass, keys, acoustic-electric guitars, and laptop playback. Note your preferences, but stay flexible — most house engineers will substitute a comparable mic from their locker if needed.

Step 4 — Mark Phantom Power and Stereo Pairs

Flag every channel that needs 48V phantom power (condenser mics and most active DIs). Getting this right on paper avoids a confusing line check where a channel appears dead. Confirm which sources are stereo so the engineer can link the pair on the console.

Step 5 — Add Stands, Notes, and Network Patching

Specify stand types (tall boom, short boom, round-base) so the stage crew sets the right hardware. Add notes for anything unusual — a specific reverb, a hard-panned source, or an instrument that switches mid-set. If the venue runs a digital, networked console, include your Dante, AES67, AVB, MADI, or AES/EBU patch so the system tech can subscribe the right flows.

Step 6 — Export and Share

Export your finished input list as a PDF for printing, an XLSX or CSV for editing, or JSON for handing to another system. Send it with your stage plot at least a week before the show.

Common Input List Mistakes

Build Your Input List Now

The Hive Mind's Input List Creator builds clean, numbered channel lists in your browser — with mic and DI suggestions, stereo pairing, phantom-power flags, full network-audio patching, and export to PDF, XLSX, CSV, and JSON.

Open the Input List Creator →