DSIV Cue Sheet Starter

Use this starter when a film, TV, broadcast, festival, client, game, app, installation, or long-form project needs music reporting. It keeps PRO and cue details available with the project files without making metadata the main shopping detail.

Project

Project title:
Episode, campaign, client, or version:
Production company, artist, creator, or brand:
Contact email:
Release/platform:
Territory:
Publish or air date:
Order, invoice, or license reference:

When to use this

Use a cue row when the project is broadcast, film, TV, game, app, festival, branded content, supervised client work, or any project where a distributor, network, client, PRO, or music supervisor asks how the music should be reported.

You do not need cue metadata on every main product card. Keep it available in:
- License docs or license packet.
- Final production cue sheet.
- Invoice, receipt, or project folder.
- Post-purchase delivery files.
- DSIV support reply for custom approval-needed uses.

Cue row

Scene or placement:
Track title:
Track version or edit:
Artist:
Writer/composer:
Publisher:
PRO:
Master owner/contact:
Usage type:
Foreground, background, theme, bumper, trailer, ad, social cutdown, live visual, or other:
Usage duration:
Timestamp in:
Timestamp out:
Notes:

Cue row detail

Use type examples:
- Foreground vocal or instrumental feature.
- Background underscore.
- Theme, bumper, ident, intro, or outro.
- Trailer, teaser, recap, or social cutdown.
- Paid ad, sponsored content, live visual, game/app loop, or installation.

Duration format:
- Use minutes:seconds, for example 00:18.
- If the cue repeats, make one row per placement unless the client asks for a single combined row.
- Keep timestamps in the final edit timeline, not the rough cut.

Reporting metadata

Keep the final cue row with the project, license paperwork, order receipt, invoice, post-purchase files, or client delivery folder. If the distributor, client, broadcaster, supervisor, or platform asks for more detail, include the order/license reference when contacting DSIV.

Where metadata should live

- License docs or license packet.
- Cue sheet starter or final production cue sheet.
- Invoice, receipt, or order-status notes.
- Post-purchase delivery files when the project needs reporting.
- Direct DSIV support reply for custom or approval-needed uses.

Simple cue sheet table

Copy this into a spreadsheet when needed:

Project title | Scene/placement | Track title | Version/edit | Artist | Writer/composer | Publisher | PRO | Master owner/contact | Usage type | Duration | Time in | Time out | License/order reference | Notes

Row 1:
Row 2:
Row 3:

Companion CSV template

Use dsiv-cue-sheet-template.csv when the customer, client, distributor, supervisor, broadcaster, or project manager wants a spreadsheet-ready cue sheet. The CSV keeps the same reporting fields in a format that can be opened in Numbers, Excel, Google Sheets, Airtable, or a production tracker.

The CSV columns are:
- project_title
- scene_or_placement
- track_title
- track_version_or_edit
- artist
- writer_composer
- publisher
- pro
- master_owner_contact
- usage_type
- duration
- time_in
- time_out
- territory
- platform_or_network
- license_order_reference
- notes

Companion metadata JSON

Use dsiv-track-metadata-template.json when the project needs structured metadata for a license packet, client handoff folder, or delivery notes. This JSON keeps the same cue and PRO details available without making metadata the main shopping detail.

The JSON is organized into:
- project: title, client or artist, platform, territory, publish or air date, and license/order reference.
- track: title, version/edit, artist, writer/composer, publisher, PRO, master owner/contact, duration used, and usage type.
- placement: scene or placement, time in, time out, and notes.
- recordkeeping: where the customer should keep the cue sheet, license docs, invoice, and post-purchase delivery files.

Approval notes

Client/distributor asking for cue info:
Deadline:
Required format:
Need writer/publisher confirmation:
Need DSIV reply attached:
Need invoice/order note:
Open issue:

Open questions

1.
2.
3.

Copy/paste cue row

Project title:
Scene or placement:
Track title:
Track version/edit:
Artist:
Writer/composer:
Publisher:
PRO:
Master owner/contact:
Usage duration:
Timestamp in/out:
License/order reference:
Reporting notes:

Cue decision

Use a cue sheet when any of these are true:
- A broadcaster, distributor, client, supervisor, festival, game studio, app team, or network asks for music reporting.
- The project has multiple placements, cutdowns, edits, versions, or territories.
- The project needs writer, publisher, master owner, PRO, or license/order references attached to production files.
- The project may later be sold, distributed, broadcast, screened, syndicated, licensed, or submitted to a platform that requests reporting.

You may not need a formal cue sheet when the use is a simple creator post, personal artist promo, informal social edit, or private draft that does not require reporting. Still keep the product title, order receipt, license notes, and final URL with the project folder.

Metadata handoff

Who is requesting metadata:
Format requested:
Deadline:
Final edit available: yes / no
Cue timing source:
Order or invoice reference:
DSIV reply needed:
Client-facing note needed:

Post-purchase file placement

Store cue and PRO metadata in:
- Project folder.
- License documents or order receipt folder.
- Cue sheet spreadsheet.
- Invoice or client handoff folder.
- Post-purchase delivery notes when reporting is expected.

You do not need to make PRO/cue metadata the main product feature unless the project needs it. Keep it available, searchable, and attached to the license/project record.