YouTube Music gives a delivered track three affirmative AI disclosure answers: fully generative AI, partly generative AI, or not generative AI. Its other rule is just as consequential for catalogue work: an empty field means unknown. A label deciding how a recording was made must answer that question separately from whether a platform may later let someone remix it.
Make the disclosure an answer
“Unknown” is a distinct state, not a quiet version of “not generative AI.” If a label leaves the field empty because it has not checked a track, the delivery carries uncertainty. If the label has checked and concluded that the track is not generative AI, it has an affirmative answer available. Those are different catalogue records, even when the audio file is the same.
The distinction matters most when several people have handled a recording before delivery. The person sending it to a platform may not be the person who knows how it was produced. A delivery choice made without that knowledge can turn a missing production record into a platform-facing answer. YouTube’s disclosure decision travels through DDEX and CSV delivery, so the practical control belongs before delivery: obtain the production account, choose the value it supports, and retain the account behind that choice.
For an independent label, the useful unit of work is the track. Record who supplied the production information, what they said about generative AI, which answer the label selected, and when the answer was sent. If the information has not arrived, mark the decision for follow-up instead of treating a blank as a completed review. This gives the next person handling the catalogue a way to distinguish a deliberate answer from an unfinished task.
Keep permission separate from production
Spotify is testing an AI-powered remix feature, and an AI cover and remix tool could reach Premium subscribers in early 2027. The participating artists have not been identified. That makes a rights decision different from YouTube’s production disclosure: one describes the source track; the other would determine whether a new use of it is permitted and on what terms.
A track marked “not generative AI” could still be proposed for a remix. A track marked “partly generative AI” still has a separate rights history to examine. Neither disclosure answer identifies who can authorize a cover or remix, what use an agreement covers, or who receives money from it. Treating the disclosure field as a permission switch would skip the contract question that controls the use.
The money question is therefore concrete. If a remix uses a right controlled by an artist or label, their share depends on whether the relevant agreement recognizes that use and provides an accounting route for it. A term that permits use without payment to the controlling rightsholder would move the value of that use away from them. Before agreeing to participate, a rightsholder should ask what is being authorized, how the resulting use will be measured, and where any payment will appear. The unidentified participant list makes those questions preparation for a possible offer, not a claim that a particular catalogue has already joined.
Review the catalogue in two passes
A single “AI reviewed” flag is too broad to guide either delivery or negotiation. Use two passes with different outcomes:
- Production pass: For each track, settle the fully, partly, or not generative AI answer from a retained production record. Leave an unresolved answer visibly unresolved.
- Rights pass: Identify who must approve a proposed cover or remix of that track, then check the proposed permission and payment terms against the applicable agreements before accepting them.
This division also tells a distributor what to request from a label. A delivery deadline calls for a production answer. A remix proposal calls for authority and terms. Sending the same questionnaire for both can collect plenty of information while leaving the decision that moves money unanswered.
Start with tracks whose production history is least clear and tracks the rightsholder would consider making available for new uses. Close the first pass with a supported delivery value. Close the second only when the party granting permission and the route for accounting are clear. YouTube’s empty-field rule supplies an immediate test for the first pass: a blank is still unknown. Spotify’s possible Premium tool supplies the reason to prepare the second before an offer arrives. A catalogue can be ready to answer one question while still needing work on the other.
