Delivery Requirements

In-Depth Explanation

Delivery requirements are the technical and legal specifications a record label imposes on an artist for finished recordings. They include file format, sample rate, bit depth, metadata standards, and delivery deadlines. These requirements trigger payment obligations and determine whether the label accepts the recordings as contractually complete.

How Delivery Requirements Works

Every record deal includes a delivery clause. This clause defines what counts as a finished, acceptable recording. Without meeting delivery requirements, the artist has not fulfilled their contractual obligation. The label does not pay advances or release the music until delivery is complete.

Technical requirements specify the exact file format. Most labels require 24-bit WAV files at 96 kHz sample rate for masters. Some accept 24-bit/48 kHz. The label may also require stems (separated instrument tracks) for remixing and sync licensing. Files must be properly named using a convention like "ArtistName_AlbumName_TrackNumber_SongTitle.wav."

Metadata requirements are equally strict. Each file must include ISRC codes, ISWC codes (for compositions), songwriter splits, publisher information, and explicit content flags. Labels that use DDEX standards require specific XML metadata files alongside the audio. Missing metadata means the delivery is incomplete.

Legal requirements often include a warranty that the recordings are original. The artist must confirm they own or have cleared all samples. The label may require a sample clearance log listing every third-party sound used.

Delivery deadlines are the most contentious part. A contract might require delivery of an album by March 1, 2025. If the artist misses the deadline, the label can extend options, reduce the advance, or reject the project entirely. Some contracts include cure periods (extra time to fix issues) of 14 to 30 days.

Quality standards also apply. The label's A&R team reviews delivered recordings for commercial viability. If the recordings do not meet the label's quality bar, they can reject the delivery and request revisions. This is subjective and often becomes a point of negotiation.

Real-World Example

An independent artist signs a deal with an indie label. The contract requires delivery of 10 songs in 24-bit/96 kHz WAV format with complete DDEX metadata. The delivery deadline is June 1. The artist submits the files on May 28 but forgets to include ISRC codes in the metadata.

The label rejects the delivery as incomplete. The artist has 14 days to fix the metadata under the cure period. The artist adds the ISRC codes and resubmits on June 5. The label accepts the delivery on June 10. The $15,000 advance payment triggers on June 11 because the contract states payment within 30 days of accepted delivery.

If the artist had missed the cure period deadline, the label could have invoked a breach clause. The artist would have lost the advance and potentially the deal. This is why metadata accuracy matters as much as the music itself.

Another example involves sample clearance. A producer delivers an album containing a sample from a 1970s funk record. The delivery requirements include a sample clearance log. The producer has not cleared the sample. The label rejects the delivery and withholds $8,000 of the advance until clearance is obtained. The clearance costs $3,500, which the producer pays out of pocket.

Why It Matters for Independent Artists

Independent artists who self-release do not face label delivery requirements. But if you sign any deal, you will. Understanding delivery requirements before signing prevents costly mistakes.

Create a delivery checklist before you start recording. Include file format, sample rate, bit depth, metadata fields, and ISRC codes. Treat this checklist as a contract with yourself. When you finish the album, verify every item.

If you work with a mixing engineer or mastering engineer, communicate the delivery requirements upfront. Give them the exact specifications from your label contract. A mastering engineer who delivers 16-bit/44.1 kHz files when the label wants 24-bit/96 kHz creates a delivery failure that costs you time.

Register your ISRC codes before delivery. You can get them through your distributor or directly from your national ISRC agency. Each track needs its own unique ISRC. Without these codes, no digital distributor will accept your music.

Keep a sample clearance log from day one. Every time you use a loop, a sample, or a royalty-free sound, document the source and license terms. This log protects you when the label asks for clearance proof.

Related Terms

• DDEX
• ISRC
• Metadata
• Mastering