How many songs does a cover band need?

New cover bands book their first three-set bar gig with 25 songs and discover on the night that 25 songs is 90 minutes. Established bands carry 200 in a list and play the same 45 every weekend. The right number is neither "as many as possible" nor "what we know", and it depends on what you play and how often.

The arithmetic

A song averages 3 minutes 30 seconds live, plus about 20 seconds of transition. That is roughly 15 songs an hour of playing time, or 11 to 12 in a 45-minute set.

Gig type	Music time	Songs needed for the night	Repertoire to do it well
Bar or pub, 3 x 45 min	2 h 15	34 to 38	55 to 70
Wedding, 2 x 60 min party sets	2 h	30 to 34	60 to 80
Wedding, with drinks set and ceremony	3 h 30	50 to 55	90 to 110
Corporate, 2 x 45 min	1 h 30	22 to 26	45 to 60
Festival or support slot	45 min	11 to 12	25 to 30
Residency, weekly at the same venue	2 h 15	34 to 38	100 or more

The "repertoire to do it well" column is larger than the "songs needed" column for three reasons: the room, the requests, and boredom.

Why you need more than a night's worth

The room. A setlist planned for a young crowd meets a room full of the couple's parents. You need 5 to 10 substitutions per set that go a different direction: older, slower, louder. That is 15 to 30 songs beyond the plan.

Requests and must-plays. Weddings and private parties bring a client list of 5 to 10 must-plays and a night of shouted requests. A band with 60 songs says yes to most of them; a band with 35 says "we don't do that one" all night. See handling song requests live.

Boredom. A band that plays the same 36 songs 40 times a year plays them worse by October. The extra 20 in the repertoire are what let you rotate 5 songs in and out per gig and keep the band awake.

Repeat bookings. A venue that books you monthly needs a different set each time, or its regulars stop coming. A residency is the one case where repertoire keeps growing indefinitely.

The overlap you can rely on

Most working bands have a core of 30 to 40 songs that go on every setlist, whatever the gig, and a ring of 30 to 60 around it that gets used by gig type. The core is where the quality lives; it is played every week and should be tight. The ring is where the growth happens.

A practical structure for a 70-song band:

• Core, 35 songs: the ones that work everywhere and that a dep must know.
• Wedding ring, 15: first dances, slow soul, the songs for the parents.
• Party ring, 10: the loud late-night ones for bars and 30th birthdays.
• Background ring, 10: acoustic-friendly, mid-tempo, for drinks receptions and dinners.

Label the songs that way in the repertoire and setlists build themselves by filter.

A growth plan

A new band should not book a three-set gig until it has 45 songs it can play without a chart. Before that, take shorter slots: support sets, 2 x 45 at a small venue, a private party with one long set.

From 45, grow by gig type, not by whim. The next 15 songs should be the ones that unlock the bookings you want: a wedding ring if you want weddings, a background ring if you want corporate drinks receptions. A band that has 100 songs but no slow soul is a band that cannot play a wedding.

Targets that working bands actually reach:

• Year 1: 45 by the first three-set gig, 60 by the end of the year.
• Year 2: 80, with rings for two gig types.
• Year 3 and beyond: 100 to 120, and from here it is replacement, not growth: 15 new songs in, 10 tired songs out, per year.

Beyond 120, the marginal song is rarely played and rarely tight. Big lists look impressive on a website and are a liability at rehearsal.

The learning cadence

The number that matters is not the repertoire size but the learning rate. A band that learns three songs a month has 36 new songs a year, which is a complete refresh of the core every 12 months. A band that learns one a month is standing still once you count the songs it drops.

A cadence that fits people with day jobs:

• Learn in batches of three: one easy, one medium, one hard, on the two-rehearsal cycle in learning new songs fast.
• One batch every four weeks. Homework in week 1, first rehearsal in week 2, second rehearsal in week 3, first low-stakes gig in week 4.
• Nine batches a year (skip the busiest gig months). That is 27 songs a year, enough to grow from 60 to 80 in one season while dropping 7.

Pick the batches fairly, with a proposal-and-vote process and a threshold, so the list does not become one member's playlist; the mechanics are in song proposals and voting.

Cutting songs

A repertoire is not a museum. Every quarter, rate what you have (audience reaction, how well the band plays it, how much the band enjoys it) and cut the bottom 5 to 10%. A song that scores low on all three has no reason to be there; a song that the crowd loves and the band hates stays, and the band learns to like it. The rating approach is in rating your repertoire.

Cutting feels like loss and is the opposite: 60 tight songs get more bookings than 100 rough ones, and every cut song is a rehearsal hour returned to the songs that matter.

Deps and the core

The size of the core is also the size of the dep's job. A dep for a five-piece with a 35-song core and charts can cover a gig with one rehearsal; a dep asked to learn 70 songs cannot. Keep the core list current and written down, and every dep in your region can play with you.

Do this today

1. Count the songs the band can play tonight without a chart. Not the list; the real number.
2. Compare it with the table above for the gigs you are booking. If it is short, book smaller slots until it is not.
3. Sort the repertoire into core and rings, and label them.
4. Schedule the next batch of three songs, with a four-week cycle.

Where expert.band helps

The repertoire with its labels (Core, Wedding, Background, New) makes the count per ring a filter away, and the three-scale ratings show the bottom 10% when it is time to cut. Song proposals with a vote threshold pick the next batch of three fairly, and promoting a proposal creates the song in the repertoire with the reference link attached, so the learning cycle starts from a chart-ready entry rather than a title in a chat.