A DJ contract that prevents the most common booking disputes covers six clauses: set duration with explicit extension billing, equipment list, song-request handling with do-not-play list, overtime rate with written-confirm requirement, load-in/load-out windows, and cancellation policy with notice window. Skipping any of them leads to the dispute pattern they’re each designed to prevent.
1. Set duration with explicit extension billing
The contract should name the contracted hours and the extension billing rate (per-hour, prorated in 15-minute increments). Without this, the “just play one more song” moment becomes a billing argument the next morning. With it, the bride knows the rate before she asks.
2. Equipment list locked in writing
The contract should list every piece of equipment included: digital mixing console, primary speaker pair sized to the venue, two wireless microphones, dance-floor lighting package, DJ booth. Specialty equipment (uplighting, additional outdoor-ceremony speakers, atmospheric effects) should be itemized as add-ons.
Without an explicit list, the “wait, where’s the second speaker?” conversation derails the load-in. With it, expectations match reality.
3. Song-request handling with do-not-play list
Song requests during the event get honored at the DJ’s reasonable discretion. The contract should allow the client to provide a do-not-play list of up to 20 songs that the DJ honors absolutely — this is the line item that prevents the awkward family-friction songs (the ex-husband’s favorite, the dad’s patriotic anthem, the cousin’s drunk-uncle anthem) from playing.
4. Overtime rate with written-confirm requirement
Extension beyond the contracted set requires written confirmation (text or email is sufficient) from the client before continuation. Without this, the verbal request becomes a billing dispute. With it, there’s an audit trail.
5. Load-in and load-out windows
Standard load-in is 90 minutes before set start; load-out completes within 60 minutes of set end. These windows match venue access expectations and prevent the “you said you’d be done by midnight” argument.
6. Cancellation policy with notice window
Cancellations more than 30 days before the wedding date owe nothing beyond the non-refundable deposit. Cancellations 30 days or fewer trigger the full balance. Without this, late cancellations eat your peak-season date with no compensation; with it, you’re protected.
The BookNox auto-generated DJ template
The clauses above are the exact ones BookNox ships in its DJ contract template (see them on /templates). When a vendor sends a proposal, the template auto-fills with the actual booking data — client name, wedding date, set hours, equipment add-ons, overtime rate, travel terms — and the couple signs it inside the same flow as picking the quote. See /djs for how it ships.