Song requests
Build your covers set in blocks, not a fixed running order
How to build a covers set list that has room for requests: song blocks, flex slots, a request-ready repertoire list and a plan for songs you do not know yet.
Read
Third song in, someone walks up to the mic stand mid-verse, leans in and says a title you half catch. You nod, because nodding is easier than stopping. Two songs later the same person is back, slightly less patient, and now the table they came from is watching to see whether you play it.
Every covers act knows this moment. Requests are one of the best things about playing live and one of the easiest ways to lose the thread of a night. The difference is almost never the songs. It is the system: how requests reach you, when you look at them, and how you say yes or no.
Decide what a request means before the gig
Most request trouble starts because the audience and the performer have different ideas about what a request is. Some people think it is an order. Some think it is a vote. Some think a fiver makes it a contract.
Settle it in your own head first. A request is a suggestion. You read it, you decide, and you owe nobody an explanation beyond a friendly one. That is not rudeness. The person who asked for a ballad at 11.40pm on a packed Saturday does not want the room to empty either; they just cannot see the room from where they are sitting.
Then decide three practical things:
- When requests are open. All night, second set only, or the last hour. Many residency players keep the first set their own and open requests once the room has warmed up.
- What you will play. Your list only, or anything you can busk. Be honest about your busking range.
- How you will answer. Played, maybe later, or not tonight. Having the words ready makes declining quick.
Pick a way to collect requests
There are four common methods. None is wrong, but they fail in different ways.
| Method | Works well when | Where it goes wrong |
|---|---|---|
| Walk-up to the stage | Small rooms, quiet sets, regulars who know the etiquette | Interrupts songs, you forget titles, only the confident ask |
| Paper slips and a pen | Weddings, private parties, tables within reach | Pens vanish, handwriting in the dark, slips pile up unread |
| Text or DM to your number | Friends-of-friends crowds, small private gigs | Mixes gig messages with your personal inbox, shares your number |
| QR code to a request page | Pubs, bars, residencies, anywhere with tables | Needs decent signal or Wi-Fi, needs the code where people can see it |
The walk-up is the default because it costs nothing, but it has a hidden cost: it only works for people bold enough to approach a performer, and it arrives at the worst moment. Slips and texts move the request to a better moment but create admin. A scan-to-request page removes both problems if you put the code in the right places; our guide to where to put a QR code at a gig covers mic stand, table card and poster placement in detail.
Whatever you choose, pick one and say it out loud. Two methods running at once means you check neither properly.
Tell the room how it works
People follow instructions they hear. They do not read a sign they have not been told about. A short line between songs does more than any printed card:
- "If you want to hear something, scan the code on the mic stand or the table and send it in. I check between songs."
- "Requests open after the break. I cannot promise everything, but I read all of them."
Say it early in the set you open requests, and again after the break when the room has turned over. Keep it under ten seconds. The phrase "I check between songs" does a lot of work: it tells people not to walk up mid-verse and tells them you are actually reading.
Handle requests between songs, not during them
The rule that saves most sets: you only look at requests in the gap between songs. Never mid-song, never while tuning something awkward.
A simple routine for the gap:
- Glance at what came in since the last check.
- If one fits what the room needs next, play it now.
- If one fits later, note it and keep going.
- If one does not fit tonight, let it go.
Keep the device you check on in a fixed place: on a music stand, taped to the monitor or on the amp. Turn the brightness down and the screen to a dark theme so it does not light your face from below. If you are a band, agree who reads requests. One person reads, one person calls the tune. Five people peering at one phone is worse than a heckle.
Reading the room against the list
A request is information. Three requests for early-2000s indie in half an hour tells you more about the room than any single one of them. Use the pattern, not just the title. If the room is asking for singalongs, move your singalongs forward even if nobody asked for those exact songs.
How to say no without making it awkward
You will decline more requests than you play. That is normal. What matters is that nobody feels ignored.
| Situation | What to say or do |
|---|---|
| You do not know the song | "Don't know that one, sorry. How about something close?" and play a neighbour |
| Wrong moment for the room | "Love that. Saving it for later," then play it later if it still fits |
| You would never play it | "Not one for us tonight," said warmly and left there |
| Same person, fourth request | Play one of theirs if you can, then stop checking their name for a while |
| Offensive or targeted request | Ignore it completely; do not read it out |
| Request comes with a tip | Thank them for the tip; the request still gets the same answer as any other |
That last row matters. If money moves a request up, every request becomes a bidding war and the people who just wanted to hear a song feel priced out. Keep tips and requests separate in your head and in how you talk about them. If you take tips too, our guide on taking tips without cash goes through how to mention them without it sounding like a toll.
Requests at different kinds of gigs
The same system bends to fit the booking.
- Pub and bar residencies. Regulars learn your rules fast. Open requests at a consistent point each week and the room will start saving them up. A covers set built to take requests makes this far easier than a fixed running order.
- Weddings and private parties. The client usually has a must-play and a do-not-play list. Ask for both in advance and treat guest requests inside those limits. Check with the client before you play anything that might be on the wrong side of the line.
- Restaurants and background sets. Keep requests quiet: no announcements over dinner, just a table card. Volume and tempo limits come first.
- Busking and markets. Requests draw a crowd. Say "shout one out" between songs and play the good ones fast.
After the set
Requests keep being useful once the gear is packed. Look back at what people asked for and note three things: songs you were asked for and did not know, songs asked for more than once, and songs you played that landed. That list is your rehearsal plan for next week.
Also note who asked. Someone who sent a request and heard it played is the most likely person in the room to come back. Tell them where you are next. Our guide to getting fans to your next gig covers how to do that without a mailing list.
Where GigTag fits
GigTag gives your act one QR code that opens a request page: fans pick from your list or type any song, add a first name if they like, and you mark each one played, accepted or declined between songs. No voting, no paid priority, and nothing for fans to download. You can see how it works in two minutes. Create your act