How to Manage Your Band's Gig Requests: From First Contact to Confirmed Date
The full path of a gig request for a band: centralize requests from every channel, qualify them, acknowledge fast, track each offer with a status, confirm in writing and follow four simple metrics.
A promoter reaches out on Instagram about a date in June. You ask for a few details, and they reply on Messenger. You check availability in the band group chat: the drummer answers right away, the guitarist needs to check, the singer is traveling.
Meanwhile, a second promoter emails you about the same weekend.
A week later, nobody knows exactly who's waiting for an answer, which date is still free or what fee was mentioned to whom.
Finding gigs is one thing. Handling requests when they come in is another, and it's often where a band loses dates it had actually landed.
This guide walks through the full path of a gig request, from first contact to confirmation, with a method that fits in one spreadsheet and a few rules. Each step links to a more detailed guide when you want to go further.
Why requests end up slipping through the cracks
At two or three gigs a year, a few conversations are enough. Once offers start multiplying, you're juggling several exchanges at once, each with its own unknowns: a vague date, an unannounced budget, musicians to check with, terms that shift before they're agreed.
And requests come in through every channel: Instagram, Facebook, WhatsApp, email, phone, a chat at the bar after a show.
The problem is almost never the number of requests. It's the lack of a system that tells you, at any moment, where each one stands.
Log everything in one place, whatever the channel
You won't stop a promoter from texting your singer. But you can set one simple rule: every serious request gets logged in one place, the same day, even if it's incomplete.
A minimal record is enough:
- The promoter and the channel they used to contact you
- The requested date or period
- The venue and type of event
- The request's status
- The next action, who does it and when
In practice, your tracker looks like this:
The Central Bar
June 12 · Lille
To qualify
→ Ask for the budget
Riverside Festival
June 27 · Douai
Availability to check
→ Drummer's answer
Private event
July 4 · Arras
Offer sent
→ Follow up on May 20
Town festival
July 18 · Lens
Confirmed
→ Send the rider
A shared spreadsheet, a project tool or a booking platform: it doesn't matter, as long as the tracker takes two minutes to update after each exchange. If it turns into admin work, nobody will keep it up.
The test: at any time, whoever handles booking should be able to answer three questions without opening a single chat app. Which requests are in progress? Who is waiting for an answer from us? What's the next action?
Qualify the request before involving the whole band
"Are you free in July?" isn't an offer yet. Before checking with five musicians, get the information that tells you whether the request fits your band.
- The date: a specific day or a flexible period?
- The location: which city, and is the travel reasonable for your lineup?
- The type of event: bar, festival, wedding, corporate event, town festival, each with very different expectations.
- Times and duration: one 90-minute set, two 45-minute sets, music for the whole evening?
- Tech: is a PA provided or do you bring your own, and is there enough space to play?
- The budget: is there one, and does it allow for a suitable set format?
No need to turn the first exchange into an interrogation. Two or three well-chosen questions are often enough:
"Thanks for your message, we're interested in the date. To send you a suitable offer, could you tell me the type of event, how long you'd like us to play, whether there's a PA on site and what budget you have in mind?"
If the budget leaves you unsure about your own fee, Setting the price for a gig helps you define a range before replying.
Acknowledge right away, answer in substance later
A promoter doesn't necessarily expect an instant confirmation. Above all, they want to know their request was received and is being handled. A short message is enough, even if nothing has been checked yet:
"Hi, thanks for the offer! We're interested in the date. I'm checking the band's availability and will get back to you by Thursday with an answer."
This message doesn't commit you to anything, but it shows a serious band. Then set yourself an internal rule, for example:
- Acknowledge the request the same day whenever possible.
- Check with the musicians involved right away, with a deadline.
- Aim to answer on availability within 48 hours.
- Let the promoter know if a check takes longer.
These timeframes aren't a standard: adapt them to your band. But reliability matters as much as speed: if you promise an answer by Thursday, answer on Thursday.
The availability check itself (date statuses, unavailability collected in advance, a template message for your bandmates) is covered in Shared Calendar for Bands.
Give every request a status
A request moves forward in stages. Giving it an explicit status keeps you from confusing "everyone's free" with "the gig is signed."
- To qualify: the request is logged, but key information is missing.
- Availability to check: the offer makes sense, the band needs to confirm it can play.
- Offer sent: the band is available, the terms (fee, set format, times) are being discussed.
- Confirmed: the deal is agreed and formalized on both sides.
- Closed: declined, canceled or no follow-up. Keep the record and note the reason.
These statuses match the ones in your calendar: a request in "availability to check" is a date "to check," an "offer sent" is a date "on hold." One shared vocabulary for the whole band means fewer misunderstandings.
Keep a record of every offer
A promoter offers €400 when your lineup can't travel for that fee. You suggest a shorter acoustic set. They need to run it by their team. Three weeks later, they come back to you, and without a record, you have to piece everything together from fifteen messages.
For every serious request, note at least:
- The fee mentioned at the start and any counter-offers.
- The set format or configuration offered.
- Any travel costs.
- Specific technical conditions.
- What each side has committed to.
The method for discussing fees without a power struggle is in Negotiating with a Venue.
Never leave an offer without a next action
An offer sent without a follow-up date ends up forgotten on both sides. The promoter is often waiting for budget approval or a group decision: a short follow-up at the right time beats waiting in silence. Write the follow-up date in the record the moment you send the offer.
Timing, format and mistakes to avoid: see How to follow up with a promoter without being annoying.
Confirm in writing before counting the date as booked
"Sounds good to us!" can mean the date works, not that the terms are agreed. That gap is behind most misunderstandings on the day of the show.
Before moving a request to "confirmed," make sure both sides have agreed in writing on:
- The date, venue and set times
- The promoter's identity and contact details
- The lineup booked and the performance expected
- The fee and payment terms
- Who provides what for tech and logistics
- What happens if the gig is canceled
Depending on the type of engagement, this can be a contract, an accepted quote or a recap email validated by the promoter. What matters is that it exists.
Once the date is confirmed
Booking ends and concert planning begins. Update the status and the calendar, then gather everything about the date (arrival time, tech contact, parking, rider, stage plot) in one record the musicians can access. The logistics checklist for a successful concert lists what to include.
Cut the work down from the very first contact
So far, everything happens inside the band. But much of the qualifying work comes from one simple fact: when a promoter contacts you, they don't know your set formats, your tech needs, your availability or the information you need from them. So you rebuild every request message by message.
A Booking Page flips that around. The promoter discovers the band, watches your videos, sees your set formats and availability indications, then sends you an already structured request: event, venue, requested date. Part of step 2 is done before the first exchange.
That's Yelinka's approach. You share one link on Instagram, Facebook, WhatsApp or in your emails, and requests arrive in one place. On the band's side, you ask the members involved, track their availability and build the lineup for the date, then the confirmed gig moves into your planning. All with no commission on your gigs: the relationship with the promoter stays yours.
Yelinka doesn't make decisions for you. It structures how requests come in and how you follow them up.
Examples of Booking Pages showing set formats and availability:
Track four metrics to improve your booking
No dashboard needed. Once a quarter, four numbers from your tracker are enough to see what's working.
Requests received How many serious requests this month, and through which channel? You'll see where people really discover you.
Time to first reply How long between the request and your acknowledgment? Requests left sitting stand out immediately.
Conversion rate Out of ten qualified requests, how many become confirmed gigs?
Reasons for declines Budget too low, unavailability, distance, wrong set format: the most frequent reason tells you what to fix.
Lots of requests but few confirmed dates? Look at the decline reasons. If it's almost always the budget, your presentation may be attracting events that don't match your fee. If it's unavailability, the problem is internal organization, not booking.
The process to set up this week
Every request follows the same path, with a clear owner and a next action at each stage:
- Intake: log the request the same day, so none gets forgotten.
- Qualification: get the date, location, event type, times, tech and budget.
- Availability: check with the musicians involved, with a deadline.
- Offer: send your fee and set format, and note the follow-up date.
- Confirmation: get the key terms validated in writing.
- Preparation: gather the gig information in a single record.
- Review: close the request, note the outcome and the reason if declined.
That discipline, much more than sophisticated tools, is what separates a band that receives requests from a band that turns them into dates.
Frequently Asked Questions
Appoint one person to handle requests, log every serious request in one place with a status and a next action, and keep the band's availability up to date. Before confirming a date, get the key terms validated in writing: date, times, set format, fee and technical responsibilities.
A shared spreadsheet is enough to track a few requests a month. Beyond that, the most useful option is a tool that connects the page where the promoter discovers your band, the request they send and the follow-up through to confirmation, so you don't have to copy information from one tool to another.
Log it in your tracker as soon as it arrives, even if it's incomplete: promoter, channel, requested date and next action. Then point the promoter to your booking link so they complete the request in one place rather than in a chat app.
There's no universal deadline. A good practice is to acknowledge the request the same day, even if availability still needs checking, then give a realistic timeframe for your final answer. Meeting that timeframe matters as much as speed.
A "sounds good to us" isn't enough. The date is confirmed when the musicians involved have validated it and the key terms (date, times, set format, fee, technical setup) have been accepted in writing by both sides: a contract, an accepted quote or a recap email, depending on the type of engagement.
Not necessarily. In most independent bands, one musician coordinates booking. What matters is that the role is clearly assigned and that information about requests stays accessible to the rest of the band.
Conclusion
When a band wants to play more, it thinks about visibility first: more videos, more venues contacted. That helps, but it's wasted if the requests you receive go unanswered or get lost across three messaging apps.
Start small: one person in charge, a tracker with statuses and next actions, a reply rule and written confirmation. From the next request on, you'll know exactly where it stands.
Ready to launch your Booking Page?



