1. Templates
  2. Events & Weddings
  3. Entertainment
  4. Song Request & Do-Not-Play Form

Song Request & Do-Not-Play Form

An intake template for the couple’s must-play and do-not-play songs, plus dedications and announcements for the night.

Description

Every DJ and band knows the two lists that make or break a night: the songs that have to be played, and the songs that must never be. This intake form captures both cleanly, with a table for each so nothing gets lost in a rambling email. One row per song, artist beside title, as many as the couple like. The do-not-play table even has a gentle ‘why’ column — not because you need the reason, but because letting a couple explain sometimes surfaces a sensitivity worth knowing. There’s a first-dance field pinned at the top and a box for dedications and announcements, so the whole musical brief for the evening arrives in one structured place. Send it to couples once they’ve booked, a few weeks before the day. It’s free, brand-styled, and replaces a nervy back-and-forth with a single tidy list you can load straight into your set.

Form fields

Everything the Song Request & Do-Not-Play Form above collects — 7 fields, so you can see exactly what it captures before you make it your own.

Song Requests & Do-Not-Play List

  • Your name(s)

    Name Icon
    Name
  • Email address

    Email Icon
    Email
  • Your first dance song (artist & title)

    Short Answer Icon
    Short Answer
  • Must-play songs

    Table Icon
    Table
  • Do-not-play list

    Table Icon
    Table
  • Any dedications or announcements to make on the night?

    Long Answer Icon
    Long Answer
  • I'm happy to be contacted about my booking

    Consent Icon
    Consent
Use Template Arrow Right Icon

Template FAQs

Common questions about the Song Request & Do-Not-Play Form — what it captures, when to use it, and how to make it your own.

Who fills this form in — the couple or the guests?

Usually the couple, a few weeks before the event, once they’ve had time to think. It gathers their definitive must-play and do-not-play lists in one place rather than in scattered messages.

Why use tables instead of a single text box?

Because a table keeps each song separate and legible — title, artist, one per row. That’s far easier to load into a set than a wall of text where songs blur together.

What's the 'why' column on the do-not-play list for?

It’s optional, and it’s there to catch sensitivities — a song tied to a difficult memory, say. You don’t need the reason to honour the request, but it sometimes flags something worth handling gently.

Can couples add dedications and announcements?

Yes. A dedicated box lets them note shout-outs and announcements for the night, so those moments are planned rather than sprung on you mid-set.

When should I send it?

A few weeks before the event works well — late enough that the couple have firm ideas, early enough that you can prepare and source anything unusual they’ve asked for.

Is the form free?

Yes. It’s free with a Fun Forms account, fully brandable, and ready to send as a link or embed on your site.