Match a Mobile DJ Request to the Audio Version Before It Enters the Set

A mobile DJ request sheet should preserve the requested music, identify the exact proposed audio version, and keep the decision to include it separate from a record that it was played. A title written on a list doesn't resolve a version question. Leave missing information visible until the responsible person can confirm the intended file and event use.
The example below is invented. “Window Light” and “Harbour Steps” are fictional working titles for a planning exercise, not identified recordings. Fovza hasn't inspected audio, played a set, attended an event or verified a customer's request. The sheet doesn't supply copyright permission, venue approval, a content-rating check or a technical playback test.
Keep the request in the words that arrived
The hypothetical organizer writes, “Please include the short version of Window Light.” That is a request with an unresolved reference. The phrase “short version” could refer to a particular supplied edit, a remembered recording or a desired length. The person receiving the message shouldn't choose an interpretation merely to fill the next column.
Record the request and where its meaning needs clarification. Ask which reference the organizer intends and whether there is an agreed, authorized way to identify it. Don't collect account passwords or bypass a platform's access controls to find a file. This planning sheet doesn't decide where music may lawfully be obtained or used.
Keep the request separate from event instructions. A person may want to hear a piece, while the organizer has a different decision about including it in the event. Record who is responsible for that decision without assuming that every request is an instruction to play.
The music practice excerpt guide connects a teacher-selected passage to a learner's task. This sheet addresses a different problem: identifying an event request, the proposed recording version and the current inclusion decision. It doesn't give lesson instructions or define a practice passage.
Resolve the version before assigning a place
For the fictional Window Light request, give the proposed reference a distinct identifier such as “organizer-supplied reference A.” Attach the identifier to the actual reference only when one exists in a real assignment. In the exercise it remains a placeholder, with no file supplied or checked.
Use separate fields for the requester’s description and the version description that has been confirmed. If the message says “clean edit,” that phrase records what was requested. It doesn't prove anything about an audio file's contents. A filename containing similar words cannot substitute for an appropriate check of the actual material.
When the reference changes, identify what changed. A different supplied edit may have a different opening, ending or other characteristics relevant to the intended event. This guide doesn't measure those differences or tell the reader how to judge suitability. It keeps the dependency visible so a responsible person can make the necessary checks.
Don't choose a running-order position while the reference is ambiguous. A proposed slot can remain conditional. For the fictional Harbour Steps entry, the sheet might say that no version has been identified, so the next action is clarification rather than assignment to the final set.
Distinguish an annotation from the recording
Audacity's label-track documentation distinguishes a point label from a region label and describes labels as annotations rather than audio. Those concepts help explain a narrow boundary: a cue note can mark an intended point or passage without being the sound that will play.
If a real assignment uses a cue annotation, attach it to the identified reference and the relevant time origin. A note about “the first chorus” can become ambiguous after a version change. This article supplies no sample timestamps, menu steps, software compatibility claim or demonstration of a working cue.
Treat “cue noted” and “playback checked” as different observations. The fictional sheet can propose a cue question, but cannot report that a file loads, sounds correct, or begins where expected. Those statements would need an actual check in the intended authorized workflow.
The same distinction applies to a region annotation. Highlighting a desired passage doesn't establish that an excerpt was created, that an edit sounds acceptable, or that the intended use is permitted. Keep such questions with the appropriate person instead of allowing a colored marker to look like completed preparation.
Record the inclusion decision and its limits
Use plain status descriptions with a stated meaning. “Requested” records that a request exists. “Proposed for inclusion” records the DJ's current plan. “Organizer confirmed for this plan” records a bounded decision when it actually occurs. None of those descriptions means “played.”
In the invented exercise, Window Light remains a clarification item because its reference is unresolved. Harbour Steps remains unassigned. The example deliberately contains no approved tracks or completed performance. That prevents a practice sheet from being mistaken for a genuine playlist or event report.
If someone withdraws a request, preserve the change without leaving the item in a supposedly final set. If a new request conflicts with an existing instruction, record the conflict and the next question. Don't interpret the most recent message as authority to override every earlier agreement.
The event run-sheet guide helps coordinate transitions and owners. It can refer to a confirmed music decision, but it cannot resolve an unidentified audio version merely by giving the moment a place in the programme. Close the version question before treating the reference as stable.
Keep the working set tied to a reviewed copy
Google Docs' version-history guidance describes named versions and access to earlier document changes. A named stage can identify the request sheet behind a proposed set. It doesn't prove that audio files are available, suitable, licensed or tested.
For the fictional exercise, a useful stage name is “requests awaiting version confirmation.” In an actual authorized assignment, a later reviewed copy should state which entries changed and which conditions remain open. An older sheet can stay in the history without being treated as the current performance instruction.
Avoid including unnecessary personal information in a copy used during the event. The person acting on the music decision may need an entry identifier and the confirmed reference, not a requester's private correspondence. Agree how the recipient will identify the right entry without spreading details that don't help the task.
If a reference becomes unavailable, reopen the dependency. Don't silently substitute another version because its title matches. The planned copy and the reference it points to need to remain connected for the decision to be understandable.
Separate the plan from any later account of playback
A set plan describes intended actions. A later event note describes what someone can actually establish happened. Copying every planned entry into a “played” list would manufacture a performance record. Leave the latter empty unless the relevant observation exists in an actual assignment.
An omitted entry and an unconfirmed observation deserve different descriptions. If a real observer cannot confirm whether a version was played, the note should preserve that uncertainty. Don't fill the gap from the running order or from what the organizer had requested.
Before handing over the sheet, check an entry from request through version identification to its current decision. If another person must guess which file or which approval the note means, the handoff isn't ready for that action. Return the specific missing detail for clarification.
This exercise ends with a proposed request sheet, not a successful set. Its value is that requests, version references and observed playback don't collapse into one reassuring tick. The next person can see exactly which question still needs an answer before relying on the plan.