How to organize your DISCO with Channel folders, tags, and color indicators

A well-organized DISCO makes it easier to find the right music, understand what you are looking at, and keep moving without second-guessing where things belong. The key is not to over-organize. Instead of building a perfect filing system for every possible situation, it helps to use a few different layers for different jobs - Channels and folders for broad structure, Playlists for the actual packages of work, tags to describe and connect, and color indicators to make key information visible at a glance.

CONTENTS

build a simple, effective Channel and folder structure
use Playlists to hold the real work
use track tags to describe the music itself
use playlist tags to connect related playlists across your DISCO
use color indicators to make key information easy to see
apply these principles across different industry workflows

Start with a simple structure

A common mistake is creating too many top-level Channels too early. It is usually cleaner to create one main Channel - something like Catalog, Artists, or Composers - then add folders inside for each artist, composer, or project. The same principle applies to project work. A small number of broad Channels that reflect major areas of work is usually better than many specific ones:

Catalog
Active projects
Pitch log
New releases
Archive

Inside those Channels, use folders and subfolders to create more detail only where you need it.

Use Channels and folders for broad organization

Channels are best for organizing bigger areas of work that contain many playlists over time. A few strong examples:

a catalog Channel organized into artist folders
a production projects Channel with a folder for each artist or client
a current projects Channel with folders for each film, show, campaign, or album rollout
a releases-by-month Channel with weekly folders inside
an archive Channel for older work you still want to keep accessible

Think of Channels as the broad shelf, folders as the labeled sections on that shelf, and playlists as the actual packages of work you open, share, and act on.

Keep the real work inside playlists

Playlists are where most of the real organization should happen - an album playlist for a release, a shortlist for a project, a delivery playlist for a client, a weekly releases playlist, or a promo asset playlist containing music, images, documents, and videos. Once you have good playlists, Channels and folders simply help you place them into a larger structure.

Use track tags to describe the music itself

Track tags are best for describing or filtering the actual tracks - genre, mood or feel, instrumentation, energy, lyrical themes, internal notes like "do not pitch", approval status, or quick creative context. They help with search and internal understanding, telling you something about the music itself or about how your team relates to that track.

Some track tags should stay private. If a tag is only meant for your team, you can control its visibility so it does not travel into client-facing areas.

If you use the Discovery Suite, DISCO's auto-tagging can add descriptive track tags quickly - a significant time-saver when working with large catalogs.

Use playlist tags to connect related playlists

Playlist tags are different from track tags. Track tags describe tracks. Playlist tags describe the context around playlists and are useful when you want to connect playlists across different folders, Channels, or projects - client or company names, project names, media types, seasons and episodes, territory, internal workflow flags, or reporting context.

For example, you may have several playlists created for one advertising project, some in an active project Channel, others in a pitch log, and others in a delivery area. Rather than forcing all of them into one folder structure, apply the same playlist tag to each one. A search or report can then pull them together instantly.

When to use folders vs tags

A simple rule helps here. Use folders when you want to show where something belongs in your overall structure. Use tags when you want to describe, connect, or filter across that structure. Folders show placement. Tags add context. If you find yourself wanting to place the same playlist in many different conceptual buckets, that is usually a sign that tags will be more useful than creating more folders.

Use color indicators to make information visible fast

Color indicators are one of the easiest ways to make a busy DISCO more readable - marking team favorites, highlighting tracks linked to a specific client or project, showing approval or clearance status, signaling "do not pitch", or helping people scan search results more quickly.

The best color systems are simple. Too many colors make the interface harder to read. A small, consistent visual language works better than trying to color-code everything.

Example organization setups

Rights holders, labels, publishers, and managers

Create a main Channel for your catalog with folders for each artist, composer, or producer. Store album playlists, asset playlists, and pitch playlists inside those folders. Create separate Channels for active production projects and a Pitch Log so day-to-day work stays separate from the core catalog.

Artists, producers, and composers

One Channel for your owned music and another for current collaborative projects keeps your core catalog separate from works in progress.

Music supervisors

A Current Projects Channel with folders for each film, campaign, show, or season works well. Seasonal TV work can be broken into season and episode folders. A separate New Releases Channel organized by month and week helps keep incoming music from cluttering active project areas.

Broadcasters and radio programmers

A Releases by Month Channel with weekly folders is simple and effective. Incoming release playlists can be reviewed, tagged, and stored by week or month so they remain easy to revisit.

Practical habits that help

Good organization usually comes from a few repeated habits, not from one perfect setup at the start - name playlists clearly, use a small number of top-level Channels, store tracks in playlists rather than leaving them loose in Channels, use tags to create cross-connections instead of building overly complex folder trees, keep your color system simple and consistent, and archive older work instead of leaving everything mixed together in active areas.

Wrap up

A clean DISCO comes from giving each tool a clear job. Channels and folders create your broad structure. Playlists hold the actual packages of work. Track tags describe the music itself. Playlist tags connect related playlists across your DISCO. Color indicators make key information easier to see. When these layers work together, your DISCO becomes easier to search, easier to share, and much easier for your team to navigate at a glance.

‍

Questions answered

How should I organize my DISCO so it stays easy to manage?
Should I use folders or tags?
What’s the best way to group playlists and tracks without making a mess?
How do I structure DISCO for artists, catalogs, projects, or incoming releases?
How can my team quickly see favorites, internal notes, or project links?
What’s the difference between track tags and playlist tags in real-world use?
How do I avoid creating too many Channels?
What’s the best way to keep related playlists connected across different folders?

How do I organize my DISCO with Channels and folders?
When should I use track tags in DISCO?
When should I use playlist tags in DISCO?
What is the difference between track tags and playlist tags in DISCO?
How do color indicators work in DISCO?
How do I use tags instead of folders in DISCO?
How do I organize playlists across multiple projects in DISCO?
How do I build a clean folder structure in DISCO?

‍