Describe your event and what you want guests to tell you. Makeform turns it into a song request form — song title and artist, timing, dedications, and a do-not-play list — so the DJ works from one clean, sorted queue instead of shouted names and paper slips.
Send new requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Pick a prompt, edit it above, or send it into the real Makeform builder. The structure here is an example, not a live AI result.
Audience
Guests requesting songs for a wedding reception
Format
Guest request form with must-play and do-not-play
Prompt size
395 chars
Example form structure
Guest request form with must-play and do-not-play
Guest name and table number
Song title and artist
When should we play it?
Is this a must-play?
Dedication or note for the DJ
Suggested routing tags
Must-play
If it fits
Do-not-play
Ask for the artist, not just the song title — the wedding band's "Hey Jude" and The Beatles' "Hey Jude" are two different files the DJ has to cue.
Step 1
Request
guests submit song, artist, and a dedication
Step 2
Collect
every request lands in one sortable list
Step 3
Sort
flag must-plays and do-not-plays
Step 4
Play
the DJ works from a clean, ranked queue
Why a request form
A DJ can't hear a song title over the speakers, and paper slips pile up unsorted at the booth. A song request form collects every request with the artist spelled out, in one list you can actually sort.
Free-text fields capture the exact title and artist, so the DJ cues the right track instead of guessing at a name yelled across the room.
Share one link or QR code and guests submit from where they're standing — no clipboard, no pen, no line at the booth.
A do-not-play field and an approval step keep the ex's song and the explicit track off the speakers before they ever reach the queue.
Built for your event
Start from the version closest to how you collect requests, then edit the fields in the builder.
Must-play and do-not-play fields, timing by part of the night, and dedications for the couple's big moments.
A short QR-code form guests fill in seconds, with genre tags so you can read the room fast.
Listener requests with track links, show slots, and on-air dedications, embedded right on your site.
Moderated requests with a clean-version check, routed to a coordinator before they reach the DJ.
Request workflow
Makeform turns your event into a live song request form with notifications, so requests stop getting lost between the dance floor and the booth.
Tell Makeform what you're collecting — song and artist, timing, dedications — and any rules like a do-not-play list or a clean-version requirement.
Adjust the genre options, add conditional fields — a dedication box only when it's a slow song — and mark the artist field required.
Post the link, print the QR code for the tables, or embed the form on your site so requests come in before and during the event.
Requests flow to your inbox and Google Sheets — one ranked list of must-plays, maybes, and do-not-plays the DJ works straight through.
Form vs template vs slips
A song request template gives you a printout to hand around, but paper slips still have to be read, sorted, and typed up. A generated form collects the same details already sorted and searchable.
Field guide
Looking for a song request template? These are the sections that make one work at a real event — generate them as a form, then tweak the wording to your night.
The request
The whole point is a track the DJ can actually cue. Ask for the title and the artist as separate, required fields — "that one song" is not a cue — and let requesters paste a link when they have one.
Timing & context
A ballad during cocktail hour and a banger at last dance are different asks. A timing dropdown and a genre tag let you place each request instead of shuffling blind.
Dedications & messages
Half the requests at a wedding come with a story. A dedication field turns "play our song" into "for Grandma and Grandpa's 50th" — the moment the DJ announces from the booth.
Screening & do-not-play
Every event has songs that can't play. A do-not-play field and an approval step catch the explicit track, the ex's song, or the overplayed request before it reaches the queue.
Related tools
The song requests are one piece. Build the RSVP, registration, and entry forms for the same event from one AI builder.
Collect headcounts, meal choices, and plus-ones so you know who's on the dance floor.
Open toolRSVP and gift-swap details for holiday parties, ready to share in minutes.
Open toolRoute event and booking requests to the right approver with venue and budget details.
Open toolRun a raffle or giveaway at your event and collect entries in one sortable list.
Open toolSign up DJs, caterers, and vendors for your event with the details you need up front.
Open toolTake sign-ups for sessions and classes with capacity limits and confirmations.
Open toolFAQ
Short answers for DJs, wedding hosts, and event organizers collecting requests.
It is the form a guest, listener, or student fills out to ask for a specific song — usually the song title and artist, plus who is asking and any dedication. It gives the DJ, band, or radio host one sorted list of requests instead of shouted names, paper slips, or messages scattered across texts.
A template is a printable slip or a Word or PDF layout you hand around and read back by hand. A form is the online version guests submit from a phone, and every request lands sorted and searchable. Makeform generates the form; if you want the printed look, you can still style it, but you skip retyping every slip.
The core set: the song title and artist as separate required fields, the requester's name, an optional link to the track, when to play it, and an optional dedication. Add a genre or vibe tag, a must-play versus do-not-play choice, and a clean-version check for school and family events.
Describe your reception to Makeform — guest name and table, song and artist, timing across cocktail hour, dinner, and dancing, plus a dedication and a do-not-play list. Generate it, edit the timing options to match your night, then share the link or a QR code on the tables so guests request during the reception.
Yes. Publish the form as a public link and turn it into a QR code you print on table cards or a booth sign. Guests scan, submit a song and artist in seconds, and their request drops straight into your list — no app and no account needed.
Yes. Add a do-not-play field the host fills in up front, and a per-request flag so a guest can mark a song to avoid. Combined with an approval step, that keeps the explicit track, the ex's song, or the overplayed request off the speakers.
An RSVP form confirms who is coming and details like meal choice and plus-ones. A song request form collects what guests want to hear once they are there. They pair well — many hosts share the RSVP first, then send the song request form closer to the event. Start from the event RSVP generator if you need headcounts.
Yes. Embed the form on your station's site or link it in your stream. Listeners submit the song, artist, a link if they have one, and which show they are requesting for, and you can collect an email so you can tell them when it airs.
Yes. Route new submissions to a coordinator or student council for approval, so someone screens for clean versions, duplicates, and do-not-play songs before the DJ sees the queue. Approved requests can flow on to your inbox, Slack, or a Google Sheet.
Yes. You can generate the form, edit it, and share it for free. Paid plans add higher submission volumes and advanced workflow features, but collecting song requests works on the free plan.
Requests land in your Makeform inbox and can flow to Google Sheets, Slack, or thousands of apps through Zapier — so the DJ works from one live, sortable list of songs, artists, and dedications instead of chasing slips.
Yes. Share the form as a public link, embed it on your website, or hand out a QR code — anyone with the link can request a song, no login required. Only you need a Makeform account to build the form and see the requests.
Stop losing requests on the dance floor.
