Handling song requests live

Two songs into the second set, a guest is at the stage with a phone screen held up: "Can you do this one? It's her favourite." You have never played it, the bride is watching, and you have 4 seconds to answer. Requests are part of the job; handling them badly is optional.

A request policy is not about being rigid. It is about deciding in advance so the decision on the night takes no effort.

Three kinds of request

Not all requests are the same, and the answer depends on which kind you are getting.

1. Pre-agreed requests: the client's must-play list, the first dance, the birthday song. These are not requests, they are the contract. They go on the setlist before you arrive.
2. Requests from the client on the night: the person paying asks for something. High priority, but still subject to "can we play it well?"
3. Requests from guests: the most common, the least binding. Some are gold (the song that will fill the floor), most are noise, and a few are traps ("play Free Bird" at a wedding).

Set expectations for type 1 and 2 before the gig, in the booking conversation, and type 3 mostly takes care of itself.

Say yes when

• It is in your repertoire and fits the moment. Obvious, but bands turn down songs they know because the singer is not in the mood. If you know it, play it.
• The client asked. If the client wants a song you know and it is not a floor-killer, play it in the next 3 songs and tell them you are doing so.
• A guest asks for something you know that also suits the current energy. Slot it in when the tempo curve allows, not immediately if you are mid-build. See setlist pacing.
• The request repeats. Three different people asking for the same song is data. Play it.

Say no (or not now) when

• You do not know it. A half-known song played badly costs you more than a polite no. "We don't have that one tonight, but here's one they'll love" and go straight into a banger.
• It would empty the floor. A 7-minute ballad at 11.15 pm on a full floor is a mistake even if the groom's mother asked. Offer to play it later, during a slower moment, or as a set opener.
• It is inappropriate for the room. Explicit lyrics at a corporate, the breakup song at a wedding. You are hired to read the room, not to obey it.
• The requester is drunk and insistent. Be friendly, do not engage, let the singer or the leader handle it and keep the set moving. Security exists for a reason; it is rarely needed.

The line that works for almost all of these: "We'll see what we can do" followed by an immediate, confident next song. Nobody remembers a no if the next song is great.

Request policies that working bands use

Pick one, write it into the booking information and the gig contract where it matters:

• Wedding/private: client sends up to 10 must-plays and up to 5 do-not-plays at least 4 weeks before the date; songs outside the repertoire may be learned for a fee (typically 50–150 EUR per song, varies by country) or not at all. Guest requests on the night: at the band's discretion.
• Corporate: client brief covers genre and volume; no live requests unless from the organiser.
• Bar/pub: requests welcome from the repertoire list; a printed or QR-code list at the front of the stage saves 100 conversations.
• Function/jazz: requests taken between sets, played if in the book.

The "learn a song for a fee" clause is worth more than the money. It filters out casual requests and makes the ones that remain serious. Most clients pick from your list once they see it.

The request list

A visible list of what you play changes the whole dynamic. The requester picks from things you can do instead of things they heard on the radio this week. Options:

• A laminated A4 at the stage front with 60–100 titles grouped by decade or style.
• A QR code linking to a web page with the repertoire (keep it current).
• For weddings, a link sent to the client in advance to build their must-play list from.

Keep the printed list to songs you can play tonight with tonight's line-up. A list that includes songs your former singer used to do is a list that generates disappointment.

Handling the moment on stage

• One person handles requests. Usually the singer or the leader. Other members point to that person with a smile and keep playing.
• Write it down. A small pad on the keyboard or a phone note. "We'll try to fit it in" is only honest if you remember the request.
• Batch them. Play requests in the set gaps or as a block: "We've had a few requests, here's three of them." Then back to the plan.
• Name the requester when you play it. "This one's for Sophie." It costs nothing and creates 5 new fans at Sophie's table.
• Never stop the set to discuss. A 40-second conversation at the stage edge kills the floor. Take the request, nod, play.

Requests you have not rehearsed

A band with a strong shared vocabulary can sometimes pull off an unrehearsed song: 4-chord pop with a known form, a 12-bar blues, a standard from the jazz book. The conditions: the singer knows the words, someone calls the key and form out loud, and you keep it short. Do this at most once a night, and never for the first dance. If you want a bigger safety net, keep a "can fake it" column in your repertoire; songs the band has never rehearsed but 3 or more members know well. See how many songs a cover band needs for how that column fits into your growth plan.

Do this today

1. Write your request policy in 3 sentences and add it to your booking info and quotes.
2. Make a printable list of 80 songs you can play tonight. Date it.
3. Decide who handles requests on stage and how they write them down.
4. Agree the "polite no" line the whole band uses.

Where expert.band helps

Keep the client's must-play and do-not-play lists in the gig notes on expert.band, and build the setlist from a repertoire that reflects what the current line-up actually plays. Song ratings from rating rounds tell you which requests are worth saying yes to: the songs that score high for audience appeal are the ones to slot in when a guest asks.