How to Advance an Artist Technical Rider

Start With the Show You Are Actually Preparing

A rider arrives. Sending it to suppliers is a useful first action, but it does not establish that the requirements are understood, achievable or allocated.

Advancing the rider means working through those questions with the relevant artist, venue and production contacts.

The result should be a plan that the receiving teams can prepare from, not simply a folder containing the original document.

A circulated rider is not an agreed production plan.

For the wider artist-facing process, see What Is an Artist Advance?.

1. Confirm the Current Documents and Performance

Establish which artist, lineup and performance the rider describes.

Ask for the current rider and relevant companion documents, including the stage plot and input list.

Check revision information where available. Confirm whether changes to the lineup, performance format or carried equipment affect the documents.

If versions conflict, identify which information is current rather than choosing the most convenient version.

Keep the received documents identifiable. Later clarifications should not make it impossible to understand what was originally requested.

2. Establish the Contacts and Approval Roles

Identify the artist’s technical contact and the person coordinating the receiving production.

Then establish who needs to review each relevant part and who can approve changes.

The person forwarding the rider may not be authorised to approve a substitution. A supplier may be able to confirm availability without being able to confirm artist acceptance.

Approval roles can vary by decision. An artist-side approval does not replace a required venue or specialist approval.

Record the appropriate contacts and route questions to the people who can answer them.

3. Review the Requirement Across Departments

Read the complete rider before separating the departmental work.

Sound, backline, staging, lighting and video requirements can affect one another. Access, power, content and communications may create further interfaces.

A stage position can affect an audio connection. Artist-carried playback can affect local inputs, monitoring and rehearsal. A lighting requirement may depend on what the venue permits.

Distribute the relevant sections for specialist review, while retaining a shared view of the unresolved interfaces.

For detailed backline interpretation, use How to Read Backline Requirements in a Technical Rider.

4. Compare the Requirement With the Actual Production

Review the rider against the venue, event format, working schedule and proposed supplier scopes.

Establish what the artist carries and what must be supplied locally.

Check whether the proposed supply covers the complete requirement, including supporting items and the work needed to make the setup usable.

Where information depends on a venue survey, specialist assessment or another department, record that dependency. Do not replace missing information with an unmarked assumption.

“Available” describes supply. It does not establish suitability, approval or responsibility.

5. Build One Clear Clarification Record

Collect the missing, conflicting and ambiguous information into a usable record.

For each item, identify:

• the requirement or document reference;
• the question or discrepancy;
• who needs to answer;
• what depends on the answer;
• when the decision is needed;
• the current status.

Consolidating questions helps the artist contact understand the production picture. It also helps the receiving teams see which answers affect their preparation.

Avoid sending several departments’ questions through separate conversations without bringing the resulting decisions back into the shared plan.

A Small Advance Record

The following is an illustrative working record, not an artist specification or mandatory template.

6. Resolve Interfaces, Not Only Equipment Items

A requirement can involve several teams even when it appears under one heading in the rider.

For example, artist-carried equipment may need local connections, a suitable position and time for checks. Those tasks may sit with different people.

Establish who provides each part, who connects or prepares it, who checks it and who communicates readiness.

Do not assume that listing an item in one supplier’s scope resolves every interface around it.

Separate responsibilities without separating the production.

7. Propose Alternatives Explicitly

If the requested arrangement cannot be supplied as written, establish what the requirement is intended to achieve and how exact it is.

Describe the proposed alternative and the relevant differences. Include the information the appropriate artist representative needs to make a decision.

Do not describe two items as equivalent merely because they belong to the same equipment category.

Some requirements may permit alternatives. Others may be essential to the performance. Confirm the distinction rather than assuming flexibility.

Keep the proposed arrangement separate from the approved arrangement.

Finding an alternative does not complete the approval.

8. Record the Decision and Its Scope

When a decision is made, record what was agreed, who approved it and which requirement it addresses.

If approval is conditional, retain the condition.

Check whether the change affects other documents or departments. A revised stage arrangement may require an updated plot. A different source arrangement may affect the input list and audio preparation.

Silence should not be treated as approval.

The decision needs to reach the people whose work depends on it, not remain only in the coordinator’s messages.

9. Check the Schedule Against the Agreed Work

Confirm the time and access needed to receive, prepare, connect and check the performance setup.

Distinguish artist arrival, equipment arrival, system readiness and readiness for soundcheck.

Where several acts share a stage, review the changeover requirements rather than assuming that shared equipment removes the work.

The production schedule should reflect those dependencies.

Time is part of the production requirement.

If the available window does not fit the agreed work, raise that conflict while the requirement, sequence or programme can still be reviewed.

10. Issue a Current Preparation Handover

Give the delivery teams the information they need to prepare their agreed part of the show.

Depending on the production, that may include:

• the current rider and companion documents;
• confirmed local and artist-carried provision;
• approved alternatives and their conditions;
• relevant preparation and connection responsibilities;
• the working schedule;
• current contacts;
• outstanding items and their owners.

The handover should distinguish confirmed information from open questions.

A team should not have to reconstruct the supplied arrangement from an old rider and several disconnected messages.

11. Manage Revisions After the Handover

A later change may affect an arrangement that was already agreed.

Identify what changed, which teams are affected and whether further approval is required. Update the working documents and communicate the revision.

An approval for an earlier arrangement should not automatically be treated as approval for a different one.

Keep unresolved changes visible. Do not mark the advance complete while a preparation-critical decision has quietly become uncertain again.

Advance Supports Verification

An approved plan still needs appropriate preparation and checks.

A line check verifies a different part of the workflow from a soundcheck. Specialist work and venue requirements still need the responsible people’s assessment.

The advance reduces avoidable uncertainty before the teams reach the stage. It does not guarantee that nothing will change or replace show-day verification.

Prepare from the current agreed requirement, and keep the remaining questions visible.