01
Gather the musical guardrails
Collect the client-control rules, audience restrictions, cultural details, request cutoff, and event-day authority before drafting policy language.
Made for DJs
Set a Song Request Policy Without Killing the Vibe
Also useful for: people in Creative
30 min
Intermediate
Boundaries
Set a Boundary
Setting a Boundary
Turn scattered music preferences into a clear policy for requests, explicit tracks, cultural selections, protected songs, and late changes.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Set firm musical boundaries without making the celebration feel rigid.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Build the request hierarchy
Decide whose instructions win when a client, planner, guest, venue representative, or member of the wedding party asks for something different.
03
Draft the policy in two voices
Create a complete internal standard alongside a warmer client-facing version that welcomes requests without promising every selection.
04
Pressure-test the live rules
Test the policy against realistic booth-side conflicts so the final version still works when the room is loud and decisions need to be quick.
Make Your Play
Set a Song Request Policy Without Killing the Vibe
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
List the event types this policy should cover.
Describe how much control clients receive and how much room you keep for reading the crowd.
0/10000
Explain how many must-plays you'll accept and whether each one needs a specific moment.
0/10000
State whether do-not-plays are absolute and who, if anyone, may approve an exception.
0/10000
Choose the closest match for how guest requests should be handled.
Choose the default rule for explicit lyrics.
Describe any traditions, communities, languages, pronunciations, or specific musical moments the policy must respect.
0/10000
Set the normal request cutoff and identify who may approve changes after it.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the musical guardrails
Collect the client-control rules, audience restrictions, cultural details, request cutoff, and event-day authority before drafting policy language.
02
Build the request hierarchy
Decide whose instructions win when a client, planner, guest, venue representative, or member of the wedding party asks for something different.
03
Draft the policy in two voices
Create a complete internal standard alongside a warmer client-facing version that welcomes requests without promising every selection.
04
Pressure-test the live rules
Test the policy against realistic booth-side conflicts so the final version still works when the room is loud and decisions need to be quick.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with the rules that are already clear, even if the rest are still undecided. Use the AI assistant’s suggested defaults as a draft, then adjust anything that doesn’t match how you work. Pay special attention to who may approve changes during the event.
Advanced instructions
Create separate policy variations for weddings, corporate events, school events, and nightlife bookings. Add a request hierarchy to the event brief, then turn the live decision guide into a short booth-side reference.
Use this when
A client wants to discuss song requests, guests may approach the booth, cultural music matters to the event, or last-minute playlist changes could cause confusion.
You'll need
- Event types
- Music and crowd approach
- Must-play approach
- Do-not-play approach
- Guest request approach
- Explicit music standard
- Cultural music considerations
- Last-minute change standard
You'll get
- Must-play and do-not-play rules defined
- Guest request authority established
- Explicit-track standard documented
- Cultural music process documented
- Late-change cutoff and event-day decision-maker named
- Client-facing policy ready to send
By the end of this playbook
You will have:
- Must-play and do-not-play rules defined
- Guest request authority established
- Explicit-track standard documented
- Cultural music process documented
- Late-change cutoff and event-day decision-maker named
- Client-facing policy ready to send
Examples
Progress 1 of 4