What to capture
A cue sheet keeps the music usage easy to understand later. It should be simple, consistent, and stored with the project archive.
Starter fields
- Project title and release date.
- Track title, product URL, and order number.
- Use type, scene or section, start time, end time, and duration.
- Composer, publisher, PRO, and contact details when provided in the license packet.
- Notes for edits, cutdowns, alternates, or stems.
Where metadata should live
Private writer, publisher, and PRO metadata does not need to be a loud storefront feature. Keep it in license docs, cue sheets, invoices, or post-purchase files where production teams need it.
Core cue fields
A cue sheet starter makes DSIV track usage easy to document while keeping detailed reporting information in the right project files.
- Track title and version
- Artist, writer, publisher, and PRO details
- Scene, usage type, duration, and timestamp
- License/order reference
Cue metadata belongs with your project file
Most projects only need cue metadata in license docs, cue sheets, invoices, post-purchase files, or request replies when reporting is required.
- Film, TV, broadcast, and festival work
- Sponsored or agency campaigns
- Games, apps, installations, and long-form projects
Keep it with your order
The cue starter references the track and order so DSIV can answer rights questions quickly if a supervisor, client, or platform asks for confirmation.
Copyable cue row
Paste this into a spreadsheet, treatment, or production document when a project needs music reporting.
Keep detailed writer, publisher, and PRO metadata in cue sheets, license docs, invoices, or post-purchase files.