What Every Band Should Send Venues Before a Gig

TLDR; Playing a gig soon? Send the venue what they need before they have to ask.

Most show-day problems come from bad communication, not bad playing. Use one repeatable packet: technical rider, stage plot, input list, contact sheet, and schedule. Keep hospitality, merch, backline, and settlement notes separate, and send them only if they matter. Send the main packet 2 to 4 weeks ahead, confirm details 1 week out, then do a short final check-in 24 to 48 hours before doors. Centralized files and a band communication app with event scheduling make rebooking more likely.

If a show is going to run smoothly, the real work usually starts long before anyone steps on stage. A lot of gig-day problems are not really music problems. More often, they come down to communication, which is frustrating for everyone. The venue did not get the latest input list. The sound engineer never saw the stage plot. No one confirmed the load-in time. Merch space was assumed instead of clearly agreed on. By the time gig day arrives, the band is left doing damage control.

That is why every serious act needs a pre-show packet they can use again and again. Keep it simple. If someone is searching for what to send venues before gig day, the answer is usually not a single file. It is a small set of clear documents, along with a few updates, so the venue, crew, and band are all working from the same plan. Good band management often means clearing up confusion before it costs time, money, or even a rebooking if things are left too loose. Still, extra admin for its own sake does not make anything better.

This guide covers what every band should send, when to send it, and how to keep everything up to date. It also looks at how a band communication app and better event scheduling can make the whole process easier. The goal is simple: help your band be easy to work with, well prepared, and ready to perform. Ready to play.

Start With the Core Venue Packet

Not every band needs a huge tour book. But every band does need a small set of core items that answer the venue’s main questions fast and reduce back-and-forth emails. Production and touring teams have been pretty consistent about the basics: a technical rider, a stage plot, an input list, clear contacts, and timing details. Those are the essentials. They’re still the standard documents venues use to plan staffing, sound, backline, and changeovers, usually before load-in and the set change.

The live music business is large, and venues are usually handling a lot at once. In 2025, the U.S. live music market was valued at $18.51 billion, and medium-sized venues made up 48.15% of that market. That same year, concerts accounted for 45.21% of the market. Those are big numbers. More specifically, they suggest venues are managing a high volume of events and need information that’s quick to scan and easy to trust, which is pretty reasonable.

So what belongs in the packet?

The must-send documents

• Technical rider: what’s coming with the act, what the venue needs to provide, and any sound or power needs involved
• Stage plot: a simple visual map showing where players, amps, drums, keys, and monitors should be on stage
• Input list: every vocal mic, instrument line, DI, or other channel the engineer needs to know about
• Advance contact sheet: who the venue should contact before the show and on the day itself, so nobody is left guessing
• Schedule or timeline: load-in, soundcheck, doors, set times, curfew, and load-out

If the show needs them, send a hospitality rider too. Backline notes, merch details, or settlement info can matter too. In most cases, it’s usually better to send those early, so the venue and the artist are not figuring things out at the last minute.

Send the Right Details, Not Just More Details

Bands sometimes think looking professional means sending a huge document, but honestly, it often works the other way. Venue teams usually need accurate info they can use fast: stage setup, input lists, and contact details. Keeping it simple helps. A short rider is often more useful than an overloaded one.

Production guides for artists and tour managers keep making the same point: out-of-date documents can cause more trouble than having no document at all, which is pretty frustrating. So files should be current, dated, and set up in a way that’s easy to scan. Clean, clear, useful, and probably easier to update too.

What each item should include

Technical rider

Keep this practical. Include your lineup, backline, monitoring needs, power requirements, and anything the venue needs to provide. If you use in-ear monitors, tracks, a click, extra DI boxes, or special mics, say that clearly, since it usually helps a lot. In this view, that is the main information. And if the drummer needs a riser, add that too.

Stage plot

This should stay clean and visual. Show where each player stands, then mark wedge monitors, amps, drums, keys, pedalboards, power drops, and vocal mic positions. It should be easy to scan at a glance. Add your band name and a version date at the top, so it is clear which version is the current one.

Input list

Match it with your stage plot. Number the channels clearly, and note whether each source is a mic or DI. Do special notes need to appear everywhere? Usually, they only help where they matter most. That tends to keep things clearer for both you and the venue.

We covered the technical side in this guide on gig tech specs, which helps bands package the info venues actually need.

Keep technical and non-technical needs separate

Hospitality should be in its own document. Food, drinks, towels, green room basics, and buyouts should not be buried in a tech rider, because that usually slows things down. Keeping those details separate often makes things easier for venue managers, the crew, and for you too.

Timing Matters More Than Most Bands Think

Even a perfect rider can still cause headaches if it arrives too late. Venue production schedules are usually planned well ahead of time, and engineers are often juggling multiple acts, staff shifts, or rental plans at the same time, which is pretty common. If your files arrive at the last minute, the venue has much less flexibility to help, especially on show day.

Once the show is confirmed, send the main packet right away. Then, closer to the date, a quick follow-up is usually enough if anything changed. And if something does change, send only the updated version. What you want to avoid is making the venue guess which file is current, because that usually slows everything down.

A simple timeline to follow

2 to 4 weeks before the gig

Send your rider, stage plot, input list, contact sheet, and timeline. It also helps to ask for a quick confirmation, so you know the venue got everything. It’s a small step, but it usually makes the whole process easier and is probably worth doing every time.

1 week before the gig

At this point, confirm your arrival time, parking, the load-in route, the soundcheck plan, and who the day-of-show contact will be. That gives you a better idea of where to go, where to park, and who to call if anything changes. If you’ve got a dep, a lineup change, or a different backline, update the documents now instead of leaving it until the last minute.

24 to 48 hours before the gig

A short final confirmation message is usually enough here. Don’t resend everything unless something has changed. Just check the key details again, like timing, access, and the current contact person.

A shared system is much easier than searching through a messy chat thread. A proper band communication app gives everyone one clear place for files, contact info, and timing, so nothing gets lost in old messages. It also helps with event scheduling, keeping rehearsals, travel, and gig details connected instead of spread across five different places.

If your band still runs everything through scattered messages, we covered that here: stopping band chat chaos

The Most Forgotten Items Are Often the Ones That Cause Stress

Bands usually remember the setlist and the start time. But the smaller details often get missed, and that can cause stress on the day. At first, they usually do not seem urgent. Then all of a sudden they are, and that is often the tricky part.

Common misses that should be sent early

Day-of-show contacts

Don’t rely on one old email thread from months ago. Send the phone number for the bandleader, tour manager, or whoever can actually respond fast on show day. That usually means a call or text, and it often makes things a lot easier when the schedule gets tight.

Backline split

Be very clear about who is bringing what. If the venue is providing a drum shell pack but not cymbals, say that plainly. If amps are being shared, mention exactly which ones. And if keys need a stand and power nearby, include that too. It may seem small, but it often saves real time once everyone is loading in.

Merch details

If merch will be sold, ask where the table should go, whether the house takes a cut, and who handles settlement. For independent bands especially, that usually matters more than people expect if the goal is to avoid an awkward conversation at the end of the night.

Settlement expectations

This does not need to turn into a legal document every time, but it helps to know who is paying, when payment happens, and whether parking or buyouts are part of the deal. Those details usually matter at load-out or right after the set, not hours later.

There is also a bigger business reason to take this seriously. The top 100 global tours brought in $9.1 billion in 2024 and again in 2025, with 69.7 million tickets in 2024 and 69.5 million in 2025. Even on a smaller scale, live music runs on tight operations, so professional habits often matter at club shows too, not just at the top.

Bands that stay organized also tend to build better venue memory over time. Keeping notes on staff preferences, stage limits, and details from past gigs makes advancing the next show much easier. That is likely why many artists now use centralized tools like BandMGT instead of searching through old inboxes and attachments.

Build a Repeatable System for Every Show

The smartest move usually isn’t making one perfect packet. It’s setting up a simple system the band can use for every booking. That’s when band management starts to feel actually helpful instead of just annoying, and that really does make a difference.

A good place to start is a master folder with the current rider, stage plot, input list, hospitality rider, and contact sheet. Keep it simple. Put a version date on every file, and have one person handle updates. Then connect those files to the calendar and the gig record so everyone can see which version goes with each event and nothing gets mixed up.

Cloud-based and mobile workflows are pretty common in music software now, and that matters because lineups change, venues change, and travel plans shift too. Things move fast. Real-time updates, file sharing, and remote access all help. AI is appearing in band admin tools too, but right now the biggest benefit still usually comes from basic organization done well. In most cases, that’s what saves time and reduces confusion.

A platform like BandMGT can help keep gig details, files, contacts, availability, and money in one place. That’s especially useful when shows, rehearsals, and member schedules are all happening at once. It may not be flashy, but it helps everyone stay on the same page.

Make It Easy for the Venue to Say Yes Again

Good communication before a gig does more than help a band avoid problems on the day. It also makes it much easier for a venue to book that band again later. Venue teams usually remember acts that are prepared, quick to reply, and easy to work with, and that often matters a lot. They also remember the bands that sent conflicting PDFs and then never confirmed anything.

Before each gig, it helps to check a few quick questions:

1. Did we send the core packet early?
2. Are all files up to date and clearly dated?
3. Did we separate tech info from hospitality, and did we confirm receipt?
4. Does everyone in the band have the same schedule and contact info?

That last point usually matters just as much inside the band as it does with the venue. The internal system should support the relationship with the venue, not make things harder. If band members miss updates, show up at load-in at the wrong time, or bring the wrong gear, the venue will still usually see it as the band’s mistake. In most cases, they will not separate one person’s mix-up from the rest of the group. A solid workflow for weekly gig check-ins helps stop that kind of drift before it turns into show-day confusion and lots of avoidable back-and-forth.

Venue communication does not need to be flashy. It should stay clear, up to date, and consistent. When the right documents go out early and are easy to follow, the whole process usually takes less time and causes less stress. That also helps the band come across as the kind of act a venue will want to bring back for another date.