A well-organized DISCO should make 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 trying to build a perfect filing system for every possible situation, it helps to use a few different layers for different jobs.

In most workflows, the simplest way to think about DISCO organization is this:

• ‍Channels and folders create your broad structure.‍
• Playlists hold the actual packages of tracks and files you want to group together.‍
• Track tags describe the tracks themselves.‍
• Playlist tags connect related playlists across different areas of your DISCO.‍
• Color indicators help your team understand important context at a glance.

Once you understand what each of these tools is best at, it becomes much easier to keep DISCO clean as your catalog, projects, and team activity grow. This article builds on the core DISCO concepts covered elsewhere and focuses on the practical question: how should you actually organize your day-to-day work?

Start with a simple structure

A common mistake is creating too many top-level Channels too early.

For example, if you manage a catalog, it is usually cleaner to create one main Channel called something like Catalog, Artists, or Composers, then add folders inside for each artist, composer, or project. That keeps the sidebar easier to scan and avoids clutter from having one Channel per artist.

The same principle applies to project work. If you are a music supervisor, manager, producer, radio programmer, or rights holder, it is usually better to create a small number of broad Channels that reflect major areas of work, such as:

• Catalog
• Active projects
• Pitch log
• New releases
• Archive

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

This gives you a structure that is easy to grow without becoming overwhelming.

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 are:

• 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

Folders are what make Channels flexible. They let you keep related playlists together without filling the sidebar with too many top-level areas.

That said, Channels do have a few quirks worth understanding.

A playlist can be added to more than one Channel or folder. This can be useful, but it also means you should stay intentional about where things go. In most cases, it is better to store your tracks inside playlists rather than leaving tracks loose in Channels. Channels work best as the container around playlists, not as a dumping ground for individual files.

A good habit is to 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.

Channels and folders are also not only useful for internal organization. They can support sharing workflows too, since Channels, folders, and subfolders can be shared as links, and some DISCO plans can share Channels directly into another DISCO. Even if your focus is purely internal organization, a clean Channel structure makes those workflows much easier later on.

Keep the real work inside playlists

Playlists are where most of the real organization should happen.

That might mean:

• an album playlist for a release
• a shortlist playlist for a project
• a delivery playlist for a client
• a weekly releases playlist
• a project playlist that stores multiple work-in-progress versions
• a promo asset playlist containing music, images, documents, and videos

Once you have good playlists, Channels and folders simply help you place those playlists into a larger structure.

This is one of the reasons overbuilding a folder hierarchy can backfire. If your playlists are already well named, well tagged, and saved in the right broad area, you usually do not need an extremely deep set of folders.

Use track tags to describe the music itself

Track tags are best when you want to describe or filter the actual tracks.

They are useful for things like:

• genre
• mood or feel
• instrumentation
• energy
• lyrical themes
• internal notes like “do not pitch”
• team favorites
• approval status
• quick creative context

Track tags help with search and internal understanding. They tell you something about the music itself or about how your team relates to that track.

For example, a supervisor team might use track tags to show which tracks certain team members like. A rights holder might use internal tags to highlight tracks that are one-stop, tracks that are not cleared yet, or tracks that should stay internal only. Track tags are especially useful because they can include color indicators, making important information easier to spot in playlists and search results.

Some track tags should stay private. If a tag is only meant for your team, such as “Do Not Pitch,” you can control its visibility so it does not travel into client-facing areas. That helps you build an internal language for your team without exposing every piece of workflow context to outside recipients.

If you use Discovery Suite, DISCO’s auto-tagging can also add descriptive track tags quickly, which can save a huge amount of time when working with large catalogs. Manual tags still matter, though, especially when you want to add business context, internal flags, or more precise descriptions that are specific to your workflow.

Use playlist tags to connect related playlists

Playlist tags are different.

Track tags describe tracks. Playlist tags describe the context around playlists.

They are useful when you want to connect playlists across different folders, Channels, or projects. Instead of moving everything into one folder just because it relates to the same job, you can use playlist tags to link those playlists together while still storing them where they naturally belong.

This is especially useful for things like:

• client or company names
• project names
• media type
• seasons and episodes
• territory
• team favorites
• internal workflow flags
• reporting context

For example, you may have several playlists created for one advertising project. Some might live 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, you can apply the same playlist tag to each one. Later, a search or report can pull them together instantly.

This is one of the biggest benefits of playlist tags: they create connections across your DISCO without forcing everything into one physical location.

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.

For example:

A folder might tell you that a playlist belongs inside Active Projects > Brand Campaigns > Bank Ad.

A playlist tag might tell you that the playlist is connected to:

• Bank Name
• Advertising
• New Zealand
• Client Sent

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.

They are not a replacement for naming things properly, and they are not a substitute for a solid folder structure. What they do well is help your team spot useful information immediately.

Some good uses for color indicators include:

• marking team member favorites
• highlighting tracks linked to a specific client or project
• showing approval or clearance status
• signaling “do not pitch”
• visually connecting a playlist tag and a track tag that belong to the same project
• helping people scan search results or playlists more quickly

For example, a team might give each staff member a custom track tag with its own color, making it easy to see who responded well to a track. Or a project might use the same color on both playlist tags and track tags so that anything related to that campaign is immediately recognizable across the system.

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

Example organization setups

The right structure depends on your role, but here are a few practical models.

Rights holders, labels, publishers, and managers

Create a main Channel for your catalog, then add 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

A good setup is often one Channel for your owned music and another for current collaborative projects. This makes it easier to separate your core catalog from works in progress. For mix review, you may also want project playlists that gather versions in one place while still living in a project folder.

Music supervisors

Many supervisors benefit from a Current Projects Channel with folders for each film, campaign, show, or season. Seasonal TV work can be broken into season folders and then episode folders inside those. A separate New Releases Channel, organized by month and week, can help keep incoming music from cluttering active project areas. A Pitch Log Channel also helps track what has already been sent out or reviewed.

Broadcasters and radio programmers

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

Radio promoters and teams sending regular updates

A Channel for client promo assets or weekly releases makes it easier to keep ongoing deliveries organized. Instead of sending disconnected links every week, you can maintain a repeatable structure that receivers learn how to navigate.

A few 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.
• Archive older work instead of leaving everything mixed together in active areas.
• Think about how your team searches, not just how things look when you first save them.

If multiple people upload regularly, it can also help to have one person or a small number of people responsible for keeping the overall structure consistent. Even a good system becomes messy if everyone uses different naming and filing habits.

Wrap up

A clean DISCO does not come from using every organizational feature at once. It comes from giving each tool a clear job.

Use Channels and folders to create your broad structure.
Use playlists to hold the actual packages of 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 easier to see.

When these layers work together, your DISCO becomes easier to search, easier to share, and much easier for your team to understand at a glance.