Wedding DJ client workflow: inquiry, music intake, and run of show
workflowfor wedding djsAugust 26, 20267 minute read
A reliable wedding DJ workflow produces a confirmed booking, a complete music plan, and a run of show that matches the real wedding day. It moves the couple from inquiry to final review through clear stages. Each stage ends with an owner, a deadline, and one current record of the decisions made.
The process below works for a solo DJ or a multi operator company. The difference is the handoff. A solo DJ needs a record that protects attention during a busy season. A team needs a record that another DJ can open and understand without reconstructing months of email.
The wedding DJ workflow at a glance
- Capture and qualify the inquiry before offering a consultation.
- Use the consultation to define scope, then send the proposal.
- Turn the booking into an event record with clear next steps.
- Collect music choices, do-not-play decisions, and MC notes.
- Build the run of show with the venue, planner, and other vendors.
- Review the final event sheet, perform the event, and close the record.
Stage one: Capture and qualify the inquiry
The first stage should answer whether the date, location, and requested coverage fit your operation. What breaks is a long email exchange that never settles the basics. Good intake captures the wedding date, venue, ceremony sound needs, reception coverage, guest count, and the best next step before anyone starts writing a custom quote.
Standardize the fields and the response path. Keep the reply human. Everbook can feed an inquiry form into the pipeline, draft a reply for review, and send the couple to a public booking page for a consultation. The broader wedding DJ platform shows how that commercial path connects to planning work.
Stage two: Define scope in the consultation
Use the consultation to learn what the couple is asking the DJ to own. Ceremony audio, cocktail hour, reception music, MC duties, lighting, and special effects can change the operating plan. Ask who controls the master timeline and whether the venue has load-in or sound restrictions. A vague scope becomes an awkward event day request.
A good proposal reflects the agreed scope in plain line items from a maintained catalog. Standardize package language, add-on names, payment steps, and what is outside scope. Keep music direction and hosting style open for later planning. The proposal should settle what you are providing without pretending every creative decision is already final.
Stage three: Book the work and open planning
A signed contract and deposit should change the status of the job and start the planning process. The common failure is a commercial handoff with no operational handoff. The couple thinks planning has started, while the DJ still has a proposal in one tool and a blank intake form somewhere else.
In Everbook, a booked proposal automatically becomes an event record with a Music and MC section of the BEO. Contracts, invoices, payments, and the event stay on that connected record. The platform overview explains the full inquiry through execution chain. Whatever system you choose, test this handoff during evaluation instead of assuming a booking creates a usable planning record.
Stage four: Collect music and MC decisions
Music intake needs more structure than a blank request box. Capture the ceremony cues, wedding party entrance, first dance, family dances, open dancing direction, must-play choices, do-not-play choices, name pronunciations, announcements, and the person authorized to request changes. Record the preferred version or edit when that distinction matters.
What breaks is treating the first submission as final. Couples refine choices as the timeline changes. Good intake remains attached to the event and clearly shows what is decided, what is still open, and who changed it. Everbook keeps do-not-play and MC notes as fields in the Music and MC section. Couples can contribute their part through the client portal, and booked events queue for planning on the Event Sheets surface.
Stage five: Run a focused planning meeting
Hold the planning meeting after the couple has supplied enough material to review. Work from a fixed agenda: confirm names, formalities, music choices, announcements, sensitive family details, surprise moments, and open questions for other vendors. Read decisions back in operational language. A preference such as a lively entrance still needs a cue, a person giving that cue, and an approved track.
The meeting should end with changes applied to the current plan, not trapped in notes. Everbook’s meeting recorder can write notes and list requested changes for review. The operator chooses which changes to apply. Nothing should update without that review.
Stage six: Build the live run of show
The run of show turns client decisions into event day cues. For each special moment, record the timing, location, track or announcement, cue source, and responsible vendor. Include ceremony sound checks, load-in, entrances, dances, toasts, meal transitions, open dancing, and the final song only when they belong to the contracted scope.
A DJ timeline cannot be accurate in isolation. Compare it with the venue and planner timeline, then check dependencies with photo and video. If speeches move, the MC cue and photographer coverage may move too. Everbook places ceremony sound, special moments, effects approvals, and DJ cues beside the shared timeline so the Event Sheet follows the current event record.
Stage seven: Review, hand off, and perform
Before the event, review the current record from the working DJ’s point of view. Verify pronunciation, prohibited music, formalities, cue owners, venue contacts, load-in, setup location, and unresolved changes. Confirm that the playback library and equipment plan support the approved event. Do not rely on the client portal as the performance screen.
For a multi operator company, the assigned DJ should be able to explain the event back from the record. That is the handoff test. After the wedding, record any approved scope changes, complete the final invoice, and close outstanding tasks. Preserve the event history so a later question can be answered from the record rather than memory.
Choose the right amount of structure
Standardize information that creates risk when it is missing: scope, payment state, name pronunciation, do-not-play choices, cue ownership, and the current run of show. Keep artistic choices flexible: how to read the room, how tightly to follow request preferences, and how to recover when the floor changes. Too little structure causes missed cues. Too much structure turns the DJ into a playlist operator.
| Workflow decision | Standardize | Keep flexible |
|---|---|---|
| Music intake | Use named fields for formalities, must-play choices, do-not-play choices, and MC notes. | Let the couple describe energy, taste, and the feeling they want without forcing every song in advance. |
| Run of show | Give each planned moment a cue source, owner, location, and current timing. | Allow the working DJ to adapt transitions when the room or service timing changes. |
| Team handoff | Require the assigned DJ to review the same event record and acknowledge open decisions. | Let each performer prepare music and hosting notes in a way that supports their craft. |
A checklist to use this week
- List the facts every inquiry must contain before a consultation is offered.
- Write a consultation agenda that separates contracted scope from later creative decisions.
- Check that a booking creates a planning record and an owner for the next client action.
- Replace blank music request boxes with fields for formalities, must-play choices, do-not-play choices, and MC notes.
- Add cue source and responsible vendor to every planned special moment.
- Give an upcoming event record to another DJ and ask them to identify every open decision.
- Use the criteria in the wedding DJ software guide when a tool cannot support this process without duplicate entry.
What should a wedding DJ client workflow include?
It should include inquiry qualification, consultation, proposal, contract, deposit, music intake, a planning meeting, run of show coordination, final review, event delivery, and payment closeout. Each stage needs a clear owner and a current record of decisions.
When should couples submit wedding music?
Set the deadline early enough to review the choices in a planning meeting and resolve questions before the final run of show. Keep the intake open to controlled updates, since ceremony cues and formalities often change with the timeline.
How do wedding DJs collect song requests?
Use structured fields for formalities, must-play choices, do-not-play choices, and special moments. Add a place for broader music direction so the couple can describe the room they want without prescribing every transition.
What belongs in a wedding DJ run of show?
Include each contracted moment that needs music, sound, an announcement, or a cue. Record its current timing, location, track or instruction, cue source, and responsible vendor so the working DJ can act without searching through messages.