Input list template
The input list is what the sound engineer patches from. Get the numbering and the detail right and the console is ready before you open a case.
What an input list contains
An input list is a numbered table, one row per channel, in the order the engineer will patch it. Conventionally it runs drums first, then bass, guitars, keys, other instruments, and vocals last — because that order is what most engineers expect to see.
Channel
The number on the stage box. Keep it stable between shows so everyone learns it.
Source
What makes the sound: kick, snare top, bass DI, guitar left, lead vocal.
Microphone or DI
Your preference, and whether you bring it or the venue supplies it.
Stand
Tall boom, short boom, none, clip. Small detail, common delay.
Phantom power
Mark the channels that need 48V so nothing arrives silent.
Notes
Anything the engineer cannot guess: shared stand, backing track channel, spare vocal.
A short worked example
- 1 — Kick in — dynamic kick mic — no stand — bring our own
- 2 — Snare top — dynamic — short boom — venue supplies
- 3 — Overhead L — condenser — tall boom — 48V
- 4 — Bass — DI — none — post-pedalboard
- 5 — Guitar L — dynamic — short boom — amp mic
- 6 — Keys L/R — stereo DI — none — 48V, two channels
- 7 — Lead vocal — dynamic — tall boom — bring our own
How the input list relates to the technical rider
The input list is a section of the technical rider, not a separate document. It has to agree with the stage plot: every source drawn on stage should appear as a channel, and every channel should be findable on the drawing. When the two disagree, the crew trusts neither.
How ArtistRider manages it
- Channels derive from the instruments and sources you placed on the stage plot
- Per-channel microphone, DI, stand, phantom power and note fields
- Reorder or renumber the list without breaking the rest of the document
- Choose the columns your engineer wants to see, then export to PDF