Wedding Song Checklist: The 8 Moments That Need One
A wedding song checklist runs to eight moments, not three - and six need a song the couple actually picks, not whatever the DJ has already queued.
Most wedding song checklists stop at three lines: first dance, a parent dance, last song. A real wedding song checklist runs to eight moments, and five of them happen before the reception even starts. Two of the eight run on whatever the DJ or band already has queued - the couple never actually picks a track for them.
Half of the eight moments happen before the reception starts: three during the ceremony, one through cocktail hour.
The full checklist, in order
Copy this table as a starting point, then drop whatever does not apply - a short ceremony with no processional walk, for instance, or a reception with no formal cake cutting. The order below follows the day itself: ceremony first, then the gap before the reception opens, then the reception's own run of fixed moments.
| Moment | When it runs | Who picks it |
|---|---|---|
| Prelude | Guests arrive and take their seats | Background - DJ or musician's own set |
| Processional | The wedding party and the couple enter | Couple, one dedicated song |
| Recessional | The couple exits, newly married | Couple, one dedicated song |
| Cocktail hour | Between the ceremony and the reception | Background - DJ or musician's own set |
| Reception entrance | The couple is introduced into the room | Couple, one dedicated song |
| Cake cutting | A short pause mid-reception | Couple, one dedicated song |
| First dance | The couple's first dance as married partners | Couple, one dedicated song |
| Last song | The final track before the night ends | Couple, or the DJ's call if left open |
Eight rows, not forty micro-decisions. Most checklists elsewhere pad this list by splitting the reception into first dance, father-daughter dance and mother-son dance as three separate entries - real moments, but the same one decision repeated: does this dance get its own song, or does it share the first dance's track.
Six get a song, two run on autopilot
Of the eight moments, six get a song the couple actually chose. Two - the prelude and cocktail hour - run on whatever the DJ or band already has queued.
The prelude and cocktail hour are the two moments most couples never think to plan, because nothing about them feels like a decision. Guests are seated, or guests are holding a drink, and background music plays underneath either way. Leaving those two moments unplanned is not a mistake - most Australian receptions run them exactly that way, and 68% of couples engage a professional for the music in the first place, which means someone qualified is already choosing what plays.1
The other six are different. Each one has a fixed point in the day where the room's attention turns to a single song, and a DJ picking on instinct for one of those six is a DJ guessing at a decision that belongs to the couple.
The one that gets skipped by accident
Cake cutting is the row most likely to go unplanned, because it rarely gets its own line on a run sheet the way the first dance does. It is a five-minute pause with everyone's eyes on the couple, and no music playing under it reads as an oversight rather than a choice. A short, deliberately chosen thirty seconds under the cutting itself does more work than a full song left to run on - most of the room stops listening once the knife goes in and the photos start.
What the reception's music actually costs
Professional wedding music in Australia averages $2,142, up 5% on the year before.2 That figure covers DJs, live bands, soloists, acoustic duos and classical strings together as one category, so it is a starting budget line, not a rate for any one format. Sixty-nine percent of couples are planning a first dance specifically, which is the one moment on this checklist almost everyone treats as non-negotiable even before the rest of the list gets built out.1
One Australian wedding DJ's own rule of thumb allows at least 90 to 120 minutes for open dancing at the end of the night, on top of 30 to 45 minutes for dinner service.3 That window is what the last song closes - not the venue's official finish time, but the end of the dance bracket the DJ has been running the whole night.
Where the checklist meets the run sheet
Four of the six couple-picked songs anchor to fixed times in the classic PlannedBy reception day: entrance at 6:00 PM, cake cutting at 8:30, first dance at 8:45, last song at 11:00.
In the classic PlannedBy reception template, four of these moments land at fixed points: the couple is introduced at 6:00 PM, cake cutting runs at 8:30, first dance follows at 8:45, and the send-off is set for 11:00. Those times are not guesses - they come from the same 62-row day used across the ceremony and reception, and they move together if the ceremony start time changes.
Set the ceremony time once, not four times The run sheet generator derives cake cutting, first dance and the last song off a single ceremony time input. Move the ceremony by twenty minutes and all three shift with it, instead of four separate corrections sent to four different people.
The song list itself still sits outside the run sheet - it is a decision the couple makes, not a time the software calculates - but the when for each of the six couple-picked moments comes straight off the same schedule as everything else in the day. DIY access to build that schedule is a single payment for the whole wedding, not a monthly charge.
Common questions
How many songs do you actually need for a wedding? Six dedicated songs across the eight moments in this checklist, plus background playlists for the prelude and cocktail hour that the DJ or band typically supplies without a request.
Do parent dances need their own song? Not on this checklist by default - they are a variation on the first dance row, not a ninth moment. Couples who want a separate father-daughter or mother-son dance add it as its own line with its own song; couples who skip it fold both into the one first-dance slot.
What happens to the reception's song times if the ceremony runs late? On PlannedBy's run sheet generator, cake cutting, first dance and the last song all shift by the same amount the ceremony did, because they are derived from the ceremony time rather than set as fixed clock times. On a static PDF, someone has to manually correct four separate times.
Who picks the last song? The couple, if they want to. Left unspecified, it becomes the DJ's call - usually whatever closes the dance bracket cleanly at the agreed finish time.
Does the processional need a different song from the recessional? Most ceremonies use two different tracks - one for the entrance, one for the exit - because the mood each moment is going for is different: anticipation walking in, celebration walking out. Using the same song for both is not wrong, just less common.
Do you need to tell the DJ the songs in advance, or just on the day? In advance. A DJ working from a run sheet with cues but no song titles still has to guess in the moment, which is the exact gap a short song list next to the schedule closes.
The next decision
Pick the six songs first - prelude and cocktail hour can wait, since those two run on the DJ or band's own set regardless. Once the six are chosen, get their moments into the wedding run sheet template alongside everything else in the day, so the DJ or band is reading times off the same document as the caterer and the celebrant. For the rows that belong to the DJ or band specifically, the DJ and band run sheet template covers what else that column needs beyond the six songs. The rest of PlannedBy covers the rest of the day.