Playback Tracks Tech Rider: Outputs, Cues, and Backup

TL;DR — A playback tracks tech rider should show the rig location, every audio output, connector and signal type, the destination of tracks, click, and spoken cues, required DIs or isolation, monitor routing, power, operator position, and the backup plan. Pair the stage plot with a numbered input list. Describe the system you will actually tour, and agree on substitutions during the advance instead of assuming every venue supports the same playback workflow.

Table of contents

1. Define the playback system before drawing it
2. Build the playback section in six steps
3. Example playback input lists
4. Plan failure and recovery
5. Advance the playback rig with the venue
6. FAQ

Define the playback system before drawing it

“Backing tracks” can mean one stereo music file, separate stems, a click track for performers, spoken count-ins, timecode, or a combination of those signals. The production team cannot infer the routing from the phrase alone. Write down the exact outputs used in the current show.

Start with five decisions:

• who starts, stops, and monitors playback;
• where the computer, player, or rack sits on stage;
• which outputs go to FOH and which are monitor-only;
• whether the outputs are analog audio, digital audio, or timecode;
• what happens if the primary playback path stops working.

Keep audio, control, and synchronization signals separate in the documentation. A click track is an audio source. MIDI is control data. Timecode is a synchronization signal. They may originate from the same rig, but they do not share the same destination or cabling by default.

Build the playback section in six steps

1. Place and label the operator and rig

Show the playback rig in its real stage position. Label the operator by role or name, such as Playback — stage right, and mark the approximate footprint of the computer stand, rack, interface, or hardware player.

If a drummer operates the rig, show the playback hardware beside the drum position without hiding it under a generic drum-kit symbol. If a dedicated technician operates from offstage, mark that location and the cable route to the stage box. The drawing should help the stage team place equipment during changeover.

2. List every physical output

Create one input-list row for each output delivered to the venue. State the connector at the point of handoff and whether the source is balanced or unbalanced. Useful descriptions include:

• interface output 1 on balanced 1/4-inch TRS;
• interface output 2 on XLR;
• headphone output on stereo 1/4-inch TRS, requiring a suitable breakout;
• artist-provided transformer-isolated XLR output.

Avoid writing only “laptop L/R.” The venue needs to know what it can plug into, whether two channels are required, and who provides adapters, DIs, or isolation.

3. Name the content and destination of each output

Use stable labels across the playback session, interface, stage plot, input list, and console. For a four-output rig, the handoff might be:

The exact layout is a show decision, not a universal standard. Some productions combine click and cues; others use mono tracks to reduce channel count; larger shows may deliver multiple stems. Document the chosen arrangement rather than presenting an optional routing idea as a requirement.

4. Keep click and cues out of the audience mix

Mark click and spoken cues clearly as monitor-only when that is the intended workflow. The channels may still pass through the monitor console or a shared console, but they should not be assigned to the audience mix.

Also state who needs each signal. “Click to drummer IEM only” is more useful than “click in monitors.” If the musical director needs cues but the other performers do not, show that distinction in the monitor notes. For more detail on destinations and mix labels, read Configuring Monitor Mixes & IEMs.

5. Document DIs, isolation, and gain responsibility

Computers and interfaces can produce different connector formats and output levels. The rider should identify the real device outputs, then state who provides the interface, DIs, transformer isolation, and adapters. Do not prescribe phantom power unless a specific artist-provided device requires it and its documentation confirms that requirement.

When the artist carries a playback rack with labeled XLR tails, write artist provides playback rack and XLR outputs. When the venue must accept unbalanced outputs, request the exact number and type of appropriate DIs during the advance. This avoids a last-minute collection of improvised adapters.

6. Add power, network, and changeover notes

Mark power beside the rig and list the required outlet quantity and location. If the rig uses a local network for control, identify artist-carried switches, routers, and cables; do not assume access to a venue production network or public Wi-Fi.

Add a concise changeover note:

• hardware arrives prewired in one rack or separate pieces;
• loom length from rig to stage box;
• expected line-check method;
• whether the operator needs a talkback path;
• whether playback remains on stage between sets.

The venue's qualified production staff decide safe power distribution. The rider communicates the load locations and artist equipment, while the advance resolves the final connection plan. See How to Document Stage Power Requirements for the broader power workflow.

Example playback input lists

Two-channel stereo playback

This arrangement does not provide a separate click or cue channel. It suits a show where playback contains only audience-facing program material or where performers do not require a routed click.

Tracks, click, and cue playback

Replace every generic interface description with the connectors and provider assignments of the actual touring system. If tracks can run in mono as an agreed fallback, record that option explicitly instead of silently combining a stereo program at the venue.

Plan failure and recovery

A useful backup note explains the recovery path without promising uninterrupted playback. Identify the likely failure points and the operator's next action.

Decide what “backup” means for this show

A backup may be a second computer, a hardware player, a duplicate audio interface, a spare power supply, or a simplified stereo file on a separate device. These options do not provide the same recovery time or routing. State which equipment is carried and whether switching is manual or automated.

Keep the fallback understandable

The backup output should have labels that match the primary system. If the fallback provides only stereo tracks and no separate click, say so. If switching requires the band to stop and restart a song, the musical director and stage manager should know that plan before doors.

Rehearse a safe response

Test the recovery process during rehearsal with the same output configuration used on stage. The operator should know how to mute an unstable source, select the backup, confirm the correct song or cue, and communicate with the performers and engineer. A written backup list is not a substitute for a rehearsed decision.

Advance the playback rig with the venue

Send the playback details with the complete rider, not as a separate message on show day. During the advance, confirm:

• available console channels and stage-box inputs;
• analog handoff connectors and DI or isolation providers;
• monitor-only routing for click and cues;
• the operator's monitor, talkback, and line-of-sight needs;
• power location and artist-carried distribution;
• changeover and line-check time;
• whether timecode or other synchronization is in scope;
• the agreed fallback if the full routing cannot be supported.

Update the rider after the conversation so the final file records the agreed plan. Use the process in How to Advance a Show to keep decisions, owners, and deadlines together.

Common playback rider mistakes

Writing “backing tracks” with no channel count. List every output and destination.

Sending click to an unspecified monitor bus. Name the performers who receive it and mark it monitor-only.

Assuming the venue supplies adapters. Assign providers for DIs, isolation, breakouts, and connector conversion.

Confusing stereo audio with two independent stems. Label the content of each channel, not only L and R.

Claiming redundancy without describing recovery. State the carried backup and the operator's switching method.

Leaving playback off the stage plot. The physical rig, operator, power, and cable handoff all affect setup.

Pre-send checklist

• Rig and operator positions appear on the stage plot.
• Every playback output has a channel number and content label.
• Connector and signal type are stated at the handoff point.
• Tracks, click, cues, stems, and timecode are distinguished.
• Monitor-only channels name their destinations.
• DIs, isolation, adapters, and cables have assigned providers.
• Power and any artist-carried control network are documented.
• Primary and fallback systems have an understandable recovery plan.
• Changeover and line-check requirements are included.
• The final rider reflects agreements made during the advance.

FAQ

What should a playback tracks tech rider include?

Include the rig and operator positions, a numbered output list, connectors, signal types, content labels, FOH and monitor destinations, click and cue routing, DI or isolation providers, power, changeover needs, and the backup plan. The stage plot and input list should use the same names.

How do bands send backing tracks to front of house?

Bands commonly deliver one or more analog audio outputs from a playback interface or hardware player to the venue's input system. The exact connectors, channel count, balance, level, and need for DIs or isolation depend on the touring equipment. Confirm the physical handoff during the advance.

Should click track go to front of house?

Click is normally intended for selected performer monitors, not the audience mix. Label the channel monitor-only and identify each recipient. The console workflow may still route the channel through the monitor system, but it should not be assigned to the house mix unless the production has an unusual, explicitly agreed reason.

Does a playback rig need a DI box?

It depends on the interface output, connector, cable run, isolation needs, and venue input. A balanced professional output may connect differently from an unbalanced headphone or consumer output. Document the exact device and agree on suitable DIs or isolation rather than assuming every rig needs the same box.

How do you back up a live playback rig?

Carry a tested alternative appropriate to the show, such as a second computer, hardware player, spare interface, or simplified stereo playback device. Document what the fallback can output, how the operator switches to it, and what performers should do during recovery. Rehearse that process before the show.

Build one current playback document

Create a Rider in Techrider.live, place the playback rig on the stage plot, connect every output to the matching input-list row, and record monitor destinations and provider assignments. Share the current link during the advance and export a dated PDF for show-day reference.

---

Last updated: 2026-07-20 · Reviewed by the Techrider.live team for live playback handoffs and production advances.