Event Organisers: Why You're Always Waiting on Artist Tech Riders
You've confirmed the artist. The contract is signed. The fee is agreed. And then — for weeks — silence on the tech rider.
The stage manager needs it to finalise the stage plot. The audio crew needs the input list to confirm the console. The lighting designer is waiting on the fixture requirements before they can spec the rig. Every day that rider doesn't arrive, three departments are either working on assumptions or standing idle.
Then it arrives — on the Wednesday before a Friday show. Incomplete. Missing the monitor mix preferences. With a drum riser specification that the venue physically cannot accommodate.
This guide is for event managers, production coordinators, and artist liaison teams who want to stop building shows on late, incorrect, or missing technical data.
Why Tech Rider Collection Goes Wrong — The Real Reasons
Artists and their management treat riders as late-stage admin
From an artist's perspective, the rider is often something their manager handles "when we get close to the show." The artist's team is managing multiple bookings simultaneously, and your specific event's rider request doesn't feel urgent until the show is imminent — meanwhile, you needed it six weeks ago to lock down equipment hire and crew scheduling.
The request goes to the wrong person
Your booking email went to the agent. The tech rider lives with the tour manager — who isn't on that email. The agent passes along a vague "they'll send it soon" but doesn't have the authority to extract it from the production team. Weeks pass while the message travels slowly through the artist's ecosystem.
The rider that arrives is wrong, outdated, or generic
Festival Pro's analysis of common production failures notes that if technical requirements are incorrectly specified, it can lead to muffled, distorted, or unbalanced sound — and in certain cases an artist may refuse to perform entirely. Many riders on file with artist management are generic or outdated — sometimes by years. A band's touring rig changes from tour to tour. If nobody checks currency, you can find yourself ordering equipment that no longer reflects what the act actually uses.
"If technical issues are identified early enough in the sound check, the organiser may have the opportunity to source the correct equipment — but this will incur additional costs and probably cause delays." — Festival Pro, 2024
Nobody set a deadline with consequences
"Please send your tech rider when you get a chance" is not a deadline. Without a specific date, a clear statement of what happens if the rider doesn't arrive, and a named person responsible for sending it, the request drifts.
The rider arrives as a PDF and everyone loses it
A rider arrives as an email attachment. The production coordinator saves it somewhere. The audio engineer asks for it separately and gets a different version. The stage manager works from what they remember from a phone call. By show day, multiple people are working from different versions of the technical requirements.
The Event Industry Council reports that 89% of event professionals said staffing shortages directly impacted their events in 2024–2025. When rider information arrives late or incomplete, there's far less capacity to recover.
How to Collect Artist Tech Rider & Production Requirements: Step by Step
Send the tech rider request at the point of contract confirmation — not later
The moment a booking is confirmed, send the tech rider request. Don't wait for a follow-up call, don't wait for the contract to be fully counter-signed, don't wait until "closer to the time." The earlier you send, the earlier it becomes an action item on the artist's management team's list. Your confirmation should include a link to your structured collection form — not just a request to "send your tech rider."
Address the request to the tour manager directly, not just the agent
Artists' booking agents manage fees and scheduling. Tour managers and production managers handle technical requirements. These are often different people. When you send the rider request, cc the agent and address the substance of it to the tour manager or production contact. Ask the agent to confirm who the correct technical contact is if you don't already have this information.
Specify every requirement category with a deadline for each
A vague rider request produces a vague response. Your structured collection form should cover:
- Stage plot (full diagram or annotated file)
- Input list with channel count, direct inputs, and mic requirements
- Monitor requirements (number of mixes, any in-ear monitor systems)
- Backline requirements (amplifier models, drum kit specification, keyboard equipment)
- Lighting requirements (fixture types, colour wash, special effects)
- Power requirements (amperage, three-phase if relevant, distribution preferences)
- AV and screen requirements if applicable
- Stage dimensions required (minimum width, depth, and height)
- Load-in time requirements and crew head count from organiser
- Soundcheck duration and scheduling requirements
Assign a deadline to the full submission — not a soft request. State explicitly what happens if the rider isn't received by that date: "If we do not receive your complete technical requirements by 2026, we will proceed on the basis of our venue's standard provision, and any supplementary equipment costs incurred as a result will be invoiced to the artist."
Use a version-controlled, central collection point
When riders arrive as email attachments, version control breaks immediately. One team member receives an updated rider and doesn't forward it. The production coordinator works from the original. A structured collection form — with a versioned submission record — means everyone on your production team can see the current, confirmed rider in one place. Any update from the artist's management replaces the previous submission cleanly.
Confirm feasibility before accepting the submission as final
When the rider arrives, your production manager needs to review it against what the venue can actually provide — before you mark it as "received and confirmed." Confirm: Can the stage accommodate the minimum dimensions specified? Is the power draw within the venue's capacity? Are there equipment items that need to be sourced externally, and is there time to arrange this?
Technical riders enable organisers to avoid last-minute purchases or rentals that go over budget due to miscommunication — but only if they're reviewed against venue capability before show day.
Any gaps or conflicts should be communicated back to the artist's production contact with a specific resolution request — not left to be discovered during load-in.
Lock and distribute the confirmed rider to all departments
Once the rider has been reviewed and confirmed, lock it and distribute a single master copy to every relevant department: stage management, audio, lighting, AV, backline, catering, and your event operations lead. One document, one version, one timestamp. If any amendment comes in after this point, issue a numbered revision to all the same recipients.
Artist Tech Rider & Production Requirements Checklist
Use this checklist for every booking:
- Stage plot — diagram showing instrument and monitor positions, drum riser placement, fly points if applicable
- Input list — numbered channels, instrument/source for each, DI or microphone preference
- Monitor mix count and type (wedge or in-ear, and IEM system brand preference if any)
- Backline specification — amplifier makes and models, drum kit brand and configuration, keyboard stands
- Power requirements — amperage, distribution board preferences, three-phase if applicable
- Stage dimensions — minimum stage width, depth, and height requirements
- Lighting specification — fixture count and type, colour wash preferences, special effects (haze, CO₂, strobes, UV)
- Pyrotechnics or special effects documentation and applicable permits
- Screen/projection requirements — size, resolution, content delivery method
- Load-in time — earliest arrival time, crew head count required from organiser
- Soundcheck duration and scheduling preference (afternoon/pre-doors)
- Set length and curfew acknowledgement
- Catering and hospitality rider (if combined document)
- Emergency contact for production queries on show day
- Rider version date confirmed as current
What a Well-Run Tech Rider Collection Process Looks Like
Scenario: The production coordinator at a mid-sized music festival, "Greenfield Sound," books fifteen artists across two stages. In previous years, riders would arrive at different times from different contacts, some incomplete, some outdated — typically within two weeks of the event. The audio supplier would estimate requirements and order equipment speculatively, often incurring change fees when actual riders finally came through.
After restructuring their collection process, Greenfield now sends a structured tech rider form within 24 hours of each booking being confirmed. The form goes directly to the tour manager's email address — provided by the agent at the point of booking. A submission deadline is set at six weeks before the event.
In 2025, twelve of fifteen riders were submitted before the deadline. Two came through after a single automated reminder at the five-week mark. One arrived late because the act's tour manager had changed — a problem caught at week five rather than the week of the event. The audio supplier received a consolidated rider pack at seven weeks out, significantly ahead of previous years. Equipment change fees dropped materially.
Common Mistakes in Tech Rider Collection
Requesting the rider too late
Asking for a tech rider four weeks before show day, when equipment hire timelines often require six to eight weeks' notice for specialist items, puts your production at risk. The rider request should go out the day the booking is confirmed.
Sending the request only to the agent
Agents facilitate bookings — they don't manage technical specifications. Always get the tour manager or production manager's contact at the point of booking, and address the technical request directly to them.
Accepting a generic or undated rider
Before filing a rider as current, confirm with the artist's production contact that it reflects their current touring setup. Ask for the date of the most recent update.
Not cross-referencing the rider against venue capability
A rider that lists a 52-channel console when your venue has a 32-channel input limit needs to be resolved before show day — not discovered during soundcheck.
Distributing riders by forwarding email attachments
Forward chains get broken, cc lists get missed, and multiple versions proliferate. Distribute one confirmed master rider to all departments simultaneously from a central source.
Use the Ready-Made Template to Collect Every Rider Requirement Upfront
GatherMonk's artist tech rider and production requirements template includes fields for every category above — stage plot upload, input list, backline spec, power requirements, and more — with automated reminders that go to the artist's management team if a submission is overdue. Every submission is version-controlled and accessible to your full production team from a single location.
→ See the artist tech rider collection template
Frequently Asked Questions
When should I send the tech rider request after confirming an artist booking?
The same day the booking is confirmed. The further you are from the event, the easier it is for the artist's management to locate and send the rider without time pressure. A request sent on booking day is also less likely to be lost in the volume of correspondence that builds up as the event approaches.
What if an artist's management says the rider will be sent soon?
Soon is not a date. Acknowledge the response, provide a specific deadline, and state what the fallback position is if the rider does not arrive in time. If equipment costs are material, put the consequence in writing: any costs from speculative equipment orders due to a late rider will be addressed per the contract terms.
How do I handle a rider that exceeds what the venue can provide?
Address the shortfall immediately. Contact the tour manager with a specific list of items you cannot accommodate as specified and ask for acceptable alternatives or whether additional equipment needs to be sourced. Never leave a venue capability gap to be discovered during load-in.
Should hospitality riders and technical riders be collected in the same form?
They can be collected together but should be routed separately on receipt. Technical rider information goes to production and audio teams. Hospitality information goes to catering and venue management. A combined form is fine for collection as long as each section is clearly routed to the right department.
How does collecting tech riders through a form differ from email in practice?
Email produces scattered attachments, multiple versions, and no visibility into what is outstanding. A structured collection form gives you a submission status view — showing which artists have submitted, which are overdue, and which have outstanding items — without searching through an inbox.
For event organisations managing artist onboarding, supplier coordination, and production documentation at scale, see GatherMonk for Event Organizers, Speaker Onboarding, and the Event Manager resource hub.