6-lesson course · about 2 hours
Getting Missing Release Information to Its Owner Early
For Artists, producers, managers and music teams responsible for creative decisions, release preparation and the details that connect them
Everything for Music teamsDesigned for release managers and music team leads to build a delivery-requirements checklist and a supervised AI agent routine that detects and routes missing assets to their owners well before deadlines.
What you’ll be able to do
By the end, you can…
How it works
A tutor that meets you where you are
- Adaptive lessonsThe course material is not static. Lessons adapt to your specific experience level, ensuring you spend time on new concepts without repeating what you already know.
- One-on-one AI tutoringYou have a dedicated AI tutor available at all times. You can ask for clarification, request examples, or dive deeper into a topic using either typed text or voice commands.
- Integrated reinforcementEvery lesson is paired with targeted quizzes and digital flashcards. These tools help you lock in technical configurations and workflow logic before moving to the next module.
- Progress trackingMonitor your journey through the curriculum with a real-time progress dashboard. Once you complete all modules and requirements, you will receive a certificate of completion.
Curriculum
The curriculum
This 2-hour course is divided into two modules: establishing your requirements and implementing the AI agents to enforce them.
Module 1Building the Requirements Foundation2 lessons
1Creating the Distributor Specification Checklist
- Create a delivery-requirements checklist based on distributor specifications
- Identify mandatory assets like ISRCs and clean versions
2Designing the Owner-Based Track Sheet
- Design a track sheet that separates composition and recording credits
- Assign named owners to unsupported or missing metadata fields
Module 2Implementing Supervised AI Agents4 lessons
3Configuring the Proactive Intake Agent
- Configure a proactive intake agent using Dots or Claude Duet
- Set up rules to log versions and isolate duplicates
4Building the Credits and Metadata Agent
- Build a credits agent routine that detects missing metadata
- Configure the agent to freeze conflicting publisher splits for human resolution
5Setting Up the Packaging Audit Agent
- Set up a packaging agent to audit manifests for missing files
- Spot missing clean or instrumental versions before submission
6Establishing the Automated Routing System
- Establish a routing system that sends specific gaps to named owners
- Configure agent stop-points for human resolution
Who it’s for
Made for you if…
Made for: Artists, producers, managers and music teams responsible for creative decisions, release preparation and the details that connect them
Release Managers
You are tired of discovering that an ISRC or a clean version is missing only days before delivery. This course helps you build a system that spots these gaps early so they are resolved before they become a release problem.
Music Team Leads
You coordinate audio versions and contributor credits across multiple people. You need a way to separate composition and recording credits and ensure every missing field has a named owner responsible for the data.
Music Coordinators
You spend too much time manually checking manifests and chasing people in general team channels. You can use supervised AI agents to audit files and route specific requests directly to the person who owns the asset.
Independent Label Operators
You handle the roles of both the manager and the coordinator. You need a proactive intake routine that logs new versions and isolates duplicates automatically, allowing you to focus on human resolutions rather than admin.
Questions
Good to know
Which AI tools do I need to use for this course?
The course focuses on configuring proactive agents using either Dots (OpenAI) or Claude Duet (Anthropic). These tools are used to automate the intake, auditing, and routing of release assets.
What exactly does the 'routing system' do for my team?
Instead of posting a general alert to a team channel, the system identifies a specific gap—such as a missing ISRC or publisher split—and sends the request directly to the named owner of that asset. This ensures the right person is notified well before the delivery deadline.
Can the AI agent handle publisher splits and credits automatically?
The credits agent can detect missing metadata and identify conflicts in publisher splits. However, rather than making a decision, it freezes the conflicting data and notifies a manager for human resolution to ensure accuracy.
Does the packaging agent actually submit my music to the distributor?
No, the packaging agent does not handle final submission. Its role is to audit the manifests for missing files, such as clean or instrumental versions, and flag those gaps so they can be fixed before you submit.
How does the track sheet differ from a standard credit list?
You will design a track sheet that explicitly separates composition credits from recording credits. Most importantly, it includes assigned owners for any unsupported or missing fields, so there is always a point of contact for gaps.
How does the intake agent handle duplicate files or new versions?
The proactive intake agent is configured with specific rules to log new audio versions while keeping approved ones intact. It is also designed to isolate duplicate assets so they do not create redundant work or overwrite approved files.
What is the primary goal of the delivery-requirements checklist?
The checklist is based on distributor specifications to ensure all mandatory assets are identified early. This prevents the common problem of discovering a missing clean version or ISRC only days before the release date.