Fly-Date Tech Rider: Backline, Travel, and Show Advance

TL;DR — A fly-date tech rider adapts the normal show requirements to what the touring party can actually carry by air. Separate carry-on, checked, freighted, locally rented, and venue-provided items; define usable backline specifications and substitutions; confirm transport, setup, patching, power, and spares; and name an approval owner. Issue one date-specific, current Rider after every handoff is confirmed.

Table of contents

1. Define the fly-date version
2. Separate carried and local equipment
3. Write actionable backline requirements
4. Advance the complete handoff
5. Verify equipment on arrival
6. FAQ

Define the fly-date version

A fly date is a show reached primarily by air travel rather than by the normal touring vehicle and equipment package. The performance may be identical, but the production method changes because instruments, backline, cases, liquids, batteries, tools, wireless equipment, and spares cannot all be assumed to travel with the artist.

The fly-date rider should not be a vague note added to the full touring rider. It should state the exact operating version for that date:

• touring-party and crew count;
• performance lineup and show format;
• equipment the party will carry;
• equipment traveling as checked baggage or freight;
• local rental and venue-provided requirements;
• artist and local staffing;
• stage plot, input list, and monitor configuration;
• approved substitutions and fallbacks;
• delivery, inspection, setup, soundcheck, and return plan.

Keep the full touring rider as a reference only when it is clearly labeled. Production should not have to guess which requirement survives the flight.

Separate carried and local equipment

Build one equipment-responsibility table before requesting brands or models.

This is an example structure. The actual travel method must follow the carrier, airport, security, customs, dangerous-goods, battery, and destination rules that apply to that journey. Confirm those rules directly rather than copying a universal allowance into the rider.

Use five clear categories

Classify every operational item as:

1. Carry-on — essential equipment kept with the touring party when permitted.
2. Checked baggage — protected equipment traveling in the aircraft hold.
3. Freight or cargo — separately booked shipment with its own timing and paperwork.
4. Local rental — supplied by an approved backline, audio, lighting, or production vendor.
5. Venue-provided — confirmed from the venue’s real inventory for that show.

Do not use artist supplies when the equipment might be split across three flights or arrive by freight. State where it is and when production can expect it.

Prioritize the show-critical kit

Ask of every carried item:

• Is it essential to the performance?
• Can it be rented reliably at the destination?
• Does it contain show files, presets, media, or custom configuration?
• Is there a working backup?
• Can the backup travel separately from the primary item?
• What cables, power supplies, adapters, mounts, and control devices make it usable?

A modeler without its power supply or a playback interface without the correct output loom is not a complete carried system.

Write actionable backline requirements

The Backline Rider Requirements guide covers full specification structure. For a fly date, add explicit approval and delivery details because the local package replaces equipment the artist normally knows.

Specify function before preference

For each item, state:

• required function and configuration;
• size or range that affects performance;
• quantity;
• essential hardware and accessories;
• power and connection requirements;
• acceptable preferred models where helpful;
• unacceptable substitutions with a practical reason;
• acceptable alternatives;
• who may approve a change;
• setup and delivery condition.

Avoid lists that name one scarce model with no explanation or fallback. Also avoid professional quality, industry standard, or similar without defining what must remain similar.

Example backline rows

Use actual dimensions, models, and formats in the real rider. Do not treat the table above as a completed request.

Record substitutions as decisions

When the requested item is unavailable:

1. vendor sends the exact proposed replacement;
2. artist-side owner checks configuration and compatibility;
3. any additional adapters, hardware, or setup time are identified;
4. the owner accepts, rejects, or proposes another option;
5. the approved change is written into the current advance;
6. affected plot, input, power, transport, and schedule fields are updated.

A phone call can resolve the issue, but the final decision should be visible to everyone who prepares or receives the equipment.

Advance the complete handoff

A fly-date advance is more than a rental order. It connects travel, local transport, equipment, crew, stage, and schedule.

Travel and local transport

Confirm:

• arrival airport, terminal, flight, and current arrival time through the approved private coordination channel;
• touring-party and baggage/case count;
• instrument, oversized-item, and freight pickup process;
• vehicle quantity, internal capacity, and secure loading;
• driver and meeting-point process;
• border, carnet, customs, work, or equipment documentation handled by the responsible professionals;
• delay escalation and the last workable arrival threshold.

Do not put private flight, passport, phone, or identity information on a public rider link. Use a restricted contact sheet or travel document for sensitive data.

Venue and vendor delivery

Agree:

• vendor contact and order reference;
• delivery entrance, access window, and collection time;
• who receives and signs for equipment;
• whether cases remain onsite;
• build, tuning, testing, and changeover responsibilities;
• missing or damaged item escalation;
• return condition and pack-down owner.

The Concert Production Contact Sheet provides a structure for ownership without exposing personal data unnecessarily.

Stage and audio

Issue a fly-date stage plot showing the local backline configuration rather than the normal touring cases or racks. Reconcile:

• usable stage dimensions;
• performer and rented-backline positions;
• microphone and DI requirements;
• input list and source names;
• monitor mixes and locally supplied outputs;
• carried playback, modeler, or IEM handoffs;
• stage power locations and voltage/frequency compatibility;
• split, console, show-file, and operator boundaries;
• spare equipment that is locally available.

If the show uses a festival stage, also apply the Festival Stage Plot and Changeover Guide.

Schedule around dependencies

Build backward from the confirmed performance and doors times:

1. equipment delivered and accessible;
2. local backline assembled and checked;
3. carried equipment arrives at the venue;
4. stage setup completed;
5. audio and power connections verified;
6. line check;
7. soundcheck or changeover rehearsal;
8. final corrections and show-ready approval.

Do not assume the normal touring setup duration when unfamiliar rental equipment must be inspected or configured. Put the dependencies into the concert production schedule.

Build a date-specific confirmation

Use a simple status table during the advance:

Use clear statuses such as requested, proposed, approved, confirmed, and unavailable. Do not mark an item confirmed merely because an email was sent.

Fly-date pre-send checklist

• The fly-date version is separate from the full touring package.
• Every item is assigned to carry-on, checked, freight, rental, or venue.
• Carried systems include cables, power, mounts, and backups.
• Local backline has functional specifications and an approval owner.
• Every substitution is recorded.
• Vendor delivery, receipt, setup, and collection are assigned.
• Transport fits the touring party and real baggage/case count.
• Sensitive travel and identity data stay out of public links.
• Plot, input list, monitors, power, and local backline agree.
• The schedule includes equipment inspection and setup dependencies.
• One current revision is shared with the working production team.

Verify equipment on arrival

The receiving owner should inspect locally supplied equipment before it becomes difficult to replace.

Backline inspection

Check:

• requested item and approved model/configuration;
• quantity and condition;
• stands, pedals, clamps, cables, keys, stools, rugs, and accessories;
• power supply, voltage, connector, and approved adapters;
• drum heads, hardware, tuning access, and spare consumables where agreed;
• instrument setup or keyboard operation where specified;
• safe placement and required stage footprint.

Photograph or record problems only through the agreed production channel and avoid publishing vendor or personal information unnecessarily.

Technical verification

1. Power equipment through the venue-approved distribution.
2. Load and verify show files or presets from controlled copies.
3. Test primary and backup signal paths.
4. Confirm each source against the input list.
5. Check monitor destinations and talkback.
6. Complete line check before musical soundcheck.
7. Record the final approved configuration.

If a substitution changes the stage footprint, source count, connector, or monitor need, update the current Rider instead of leaving the change in chat history.

Common fly-date mistakes

Sending the full touring rider with backline locally added. Production still cannot tell which items travel and which must be sourced.

Naming equipment without accessories. A drum shell pack, keyboard, or amplifier may be unusable without the required stands, pedals, hardware, cables, or controls.

Approving a substitution without updating other sections. Different equipment can change power, footprint, connectors, input count, or setup time.

Treating booked as confirmed. Confirm the exact order, delivery, condition, and on-site owner.

Putting private travel data in a public technical document. Separate production requirements from restricted personal and travel details.

Carrying one copy of the show-critical data. Keep controlled backups in an allowed, accessible form and avoid placing primary and backup on the same device or bag when practical.

FAQ

What is a fly date in touring?

A fly date is a performance reached mainly by air travel instead of the normal touring vehicle and equipment package. The artist may carry essential instruments and show systems while backline, audio, or other production equipment is rented or supplied locally.

What should a fly-date tech rider include?

Include the exact lineup, carried and checked items, freight, local rental and venue responsibilities, backline specifications, substitution rules, stage plot, input list, monitors, power, staffing, transport, delivery, inspection, schedule, fallbacks, contacts, and revision date.

Who provides backline for a fly date?

It may be supplied by a local backline vendor, audio provider, promoter, venue, or a combination. The rider and advance should name the provider, exact configuration, approval owner, delivery and setup responsibility, and fallback for each item.

How do you advance a fly-in show?

Start from the performance requirements, classify every item by travel/provider method, source local equipment, approve substitutions, confirm transport and delivery, reconcile the stage and audio documents, schedule inspection and setup, and issue one date-specific confirmation.

How do you approve backline substitutions?

The vendor proposes an exact replacement with configuration details. The named artist-side owner checks function, compatibility, accessories, footprint, power, and setup implications, then records the accepted option and updates every affected production document.

Make the fly-date version unambiguous

Create the fly-date stage plot and input list in Techrider.live, invite the tour or production manager to edit and save the same Rider, inspect history after changes, and share the confirmed version with the venue.

---

Last updated: 2026-07-31 · Reviewed for fly-date equipment responsibilities, local backline, substitutions, travel handoffs, production advance, and arrival verification.