Song Request Form Template

For DJs, bands, and radio hosts — title, artist, the moment it should play, and the story behind it, collected before the dance floor fills.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

What should we play? Drop your request — and if there's a story behind the song, tell it. Stories get songs played.

press Enter ↵

Song requests used to mean a stranger shouting over a monitor speaker mid-mix. A request form moves that conversation to where it works: guests submit from their phones whenever the impulse strikes, and the person behind the decks reads a tidy queue between transitions instead of lip-reading over bass. But the deeper win is programming intelligence — a night's requests, read together, tell you exactly what this crowd wants before you commit to it.

Why these fields. Title and artist are both required because half of all shouted requests are ambiguous — there are a dozen songs called "Stay", and the artist field settles which one without a follow-up conversation nobody can hear. The name field is optional and deliberately casual, because requests should feel like passing a note, not filling paperwork. The play-moment question is the professional's field: guests think in songs, DJs think in arcs, and knowing a track is meant for dinner versus peak floor versus the last dance lets you place it where it lands — the same song is magic at midnight and a floor-killer at nine. The dedication field is where the mic material lives. "For my grandmother, who taught me this one" turns a track into a moment, and the intro line's promise — stories get songs played — is real request-form psychology: it coaches guests toward the requests you actually want to honor.

What we left out. Genre checklists and rating scales — nobody at a party wants to taxonomize their request — and any promise of guaranteed play, because the set belongs to the person reading the room. The ending says so with a wink.

Who uses this. Wedding DJs collecting requests weeks ahead via the invitation website, party and event DJs with a QR code taped to the booth, cover bands taking shouts digitally, campus and community radio hosts, and bars running theme nights.

Make it yours. For weddings, share the link with the invitations and watch the couple's people build the setlist for you — then export the CSV and prep the crate before the night. For live events, print the QR code and set the form to Focus mode (it already is) so it feels like a chat on a phone held in one hand. If requests should stop at midnight, set a close time in Settings and write a friendly closed message. And when one enthusiast starts flooding the queue, turn on duplicate prevention so each device submits once — the polite version of "I heard you the first time."

Read the room, on paper. A request queue is the only honest polling data a party produces. The form collects it; the set you build from it is still yours.

Frequently asked questions

How do guests find the form at an event?

Share the link as a QR code on tables or the booth — anyone can submit from their phone, no app or account, and requests appear in your responses view instantly.

Can we stop taking requests after a certain time?

Yes — set a closing time in the form Settings and it stops accepting at that moment, showing your own closed message ("The crate is locked for tonight!").

What stops one person requesting twenty songs?

Turn on duplicate prevention in Settings — one submission per device or IP reins in the enthusiast without confronting anyone at the booth.

Do requesters see what others asked for?

No — the queue is private to you. Guests see only their own confirmation, so the night keeps its surprises and you keep editorial control of the set.