A touring band sends their technical rider. It specifies a 48-channel digital console, specific microphone models, particular monitor systems, detailed stage plot, power requirements, and dressing room specifications.

You’re a 400-capacity regional venue with a 32-channel analog console, a standard mic collection, whatever monitors you’ve accumulated over the years, and dressing rooms that are basically converted storage rooms.

This gap between rider requests and venue reality plays out constantly in Australian live music. How it gets handled determines whether the show goes well or becomes a disaster.

The Unrealistic Rider Problem

Some riders are written for arena tours and never get updated for smaller venues. The band’s management sends the same 10-page technical spec to every venue regardless of capacity or capability.

I’ve seen 200-capacity pub venues receive riders specifying arena-grade production that would cost more than the entire show budget. Nobody seriously expected the venue to provide it, but the rider created confusion and unnecessary stress.

The question becomes: what’s actually required versus what’s aspirational? Most riders don’t clearly distinguish between must-have and nice-to-have.

The Console Mismatch

This is the most common technical gap. Rider specifies a specific digital console model. Venue has a different console or an analog board.

For experienced sound engineers, console differences are manageable. The fundamental work is the same - you’re mixing channels, applying EQ and dynamics, routing to outputs. A good engineer adapts.

But some touring acts bring engineers with limited experience who’ve only used one specific console. Putting them on unfamiliar gear creates problems.

The solution that works is communication before load-in. If there’s a console mismatch, discuss it early. Sometimes the band’s engineer can adapt. Sometimes the venue can rent appropriate gear. Sometimes the band needs to use a local engineer familiar with the venue system.

What doesn’t work is discovering the mismatch at soundcheck when there’s no time to solve it.

Microphone Specifications

Riders often specify exact microphone models for each source. Vintage mics, specialized instrument mics, particular vocal mics that the artist is comfortable with.

Many venues have standard mic packages - SM58s for vocals, SM57s and similar dynamics for instruments, maybe a few condensers for overheads and acoustic sources.

The gap here is usually manageable. Most of the time, similar mics in the same category work fine. An SM58 versus a Beta58 on vocals isn’t going to make or break a show. Using an SM57 instead of a specialized snare mic is workable.

The exception is when an artist has genuinely specific requirements - a vocalist who can only perform well on a particular mic model, or a unique instrument that needs specialized miking. These need to be flagged as critical rather than just listed in the rider.

Monitor Systems

Rider specifies 6 discrete monitor mixes with particular wedge models or in-ear systems. Venue has 4 monitor mixes and whatever wedges they own.

This creates real problems because monitor requirements directly affect artist performance. Guitarists need to hear themselves clearly. Singers need the right vocal level. Drummers need specific mix content.

The compromise that works is prioritizing. Which band members absolutely need separate monitor mixes versus who can share? Can some members use the house PA fold-back instead of dedicated monitors?

These conversations need to happen during advance, not during soundcheck when everyone’s stressed and time is limited.

Power Requirements

Some riders specify power distribution and capacity that exceeds what venues have available. This is especially problematic for regional venues in older buildings with limited electrical service.

Running arena-grade lighting and sound production requires significant power. If the venue’s service can’t handle it, something has to give.

The solution is usually scaling back production - fewer lights, less bass amplification, simplified effects. But this needs to be planned, not discovered when you’re trying to power up and tripping breakers.

I’ve seen shows delayed by two hours while trying to work out power distribution that should have been addressed a week earlier.

Load-In and Stage Space

Riders sometimes assume stage dimensions and load-in access that don’t match reality. The rider shows a stage plot requiring 10 meters width. The venue stage is 7 meters.

Or the rider specifies load-in directly to stage via large dock doors. The venue has a narrow side door and stairs.

These are solvable problems if addressed early. The band can adjust their stage plot, use less gear, work with the space available. But springing it on them at load-in creates frustration and rushed compromises.

Dressing Room Expectations

This is where riders get most detached from reality in smaller venues. Requests for separate dressing rooms for band and crew, specific catering, furniture, privacy, climate control.

Most regional venues have one or two small rooms that serve as storage most of the time and get cleared out for dressing rooms when needed. They’re functional but not luxurious.

Managing expectations here is mostly about communication. Bands touring regional circuits understand that dressing facilities won’t match metro venues. But they need to know what to expect.

The friction comes when riders create assumptions that don’t match reality, and the venue doesn’t clarify until the band arrives.

The Advance Process That Works

The venues handling rider mismatches well have an advance process where technical requirements get discussed 1-2 weeks before the show.

The venue technical contact reviews the rider, identifies gaps between request and what’s available, and reaches out to the band’s tour manager or production contact.

This conversation covers:

• Console and major equipment differences
• Monitor system capabilities and limitations
• Stage size and load-in constraints
• Power availability
• Critical versus flexible technical needs

Most of these discussions result in workable compromises. The band adjusts expectations or brings specific critical gear. The venue rents certain items if budget allows. A plan gets made.

When to Say No

Sometimes the gap between rider and reality is too large. A venue that can’t safely or adequately support a show shouldn’t take the booking.

If the band requires production capability that’s genuinely beyond what the venue can provide or rent, and won’t adjust their requirements, the professional response is declining the booking.

This is rare if the advance process works properly. Usually, gaps are bridgeable. But occasionally, the show isn’t a good fit for the venue, and forcing it creates problems for everyone.

The Regional Touring Reality

Bands touring regional Australia need to understand that venue capabilities vary significantly. The same rider that works fine in metro venues might be unrealistic for regional venues with different infrastructure.

The bands that tour successfully in regional areas either:

• Scale their production to be flexible across different venue types
• Carry critical gear themselves rather than depending on venue provision
• Have advance teams that work through technical requirements properly before arrival

What Venues Can Do

Invest in advance communication. The hour spent discussing technical requirements before the show prevents hours of problems on show day.

Be honest about capabilities. Don’t agree to provide things you can’t deliver. It’s better to address limitations upfront than surprise the band at load-in.

And where possible, invest in core technical infrastructure that reduces common gaps - decent console options, reliable monitor system, proper power distribution, standard mic package.

You don’t need arena-grade gear, but having functional, well-maintained equipment that covers most standard requirements reduces friction significantly.

The Bottom Line

The gap between band riders and venue reality is normal, especially in regional touring. It becomes a problem only when it’s not addressed through proper advance communication.

Most technical mismatches are solvable through compromise, adaptation, and planning. The unsolvable problems are the ones nobody talks about until load-in.

Good advance work, honest communication, and realistic expectations from both sides make the difference between smooth shows and technical disasters.