Skip to content

Project Due Dates

When you’re working toward a release date, sync deadline, or client delivery, setting a due date on the project keeps everything on track. Producer Dashboard lets you set a single deadline at the project level, and that date cascades down to every song inside it.

  1. Right-click the project name in the sidebar
  2. Select Edit or open the project’s settings
  3. Find the Due Date field
  4. Click it to open the date picker
  5. Choose your deadline and confirm

The due date appears next to the project name in the sidebar, giving you a quick visual reminder of when things are due.

This is the key concept: when you set a due date on a project, every track inside that project inherits the deadline — unless the track already has its own individual due date.

Here’s the logic:

Track has own due date?Project has due date?What the track shows
YesYesThe track’s own due date (takes priority)
YesNoThe track’s own due date
NoYesThe project’s due date (inherited)
NoNoNo due date shown

So the cascade is simple: project due dates fill the gap for tracks that don’t have their own deadline. If you set a specific date on an individual track, that always wins.

Say you’re working on a five-track EP due on March 15. Instead of setting March 15 on each song individually, you set it once on the project. All five tracks now show March 15 as their deadline. If one track needs to be done earlier — maybe it’s the lead single dropping February 28 — you give that track its own date, and it overrides the project date.

When a due date passes and the work isn’t done, Producer Dashboard flags it:

  • Red text appears on the due date in the grid and activity panel
  • Overdue badges show up on the project in the sidebar
  • The dashboard highlights overdue items in its upcoming deadlines section

These indicators apply to both individual track due dates and inherited project due dates. If your project deadline has passed and a track inside it has no individual date, that track shows as overdue.

When deadlines shift (and they always do), updating the project due date automatically updates the inherited date for every track inside:

  1. Right-click the project in the sidebar
  2. Update the due date to the new deadline
  3. Every track inheriting from the project immediately reflects the new date

Tracks with their own individual due dates aren’t affected — they keep their specific deadlines.

To clear a project’s due date:

  1. Open the project’s date picker
  2. Clear the date field
  3. Tracks that were inheriting this deadline now show no due date (unless they have their own)

The dashboard gives you a consolidated view of upcoming and overdue deadlines across all your projects. This is useful when you’re juggling multiple releases or client projects and need to see what’s coming up next.

You can also use the grid’s sort and filter options to see tracks ordered by due date, or filter to only show tracks due within a specific timeframe.

You’re releasing an album on June 1. Set June 1 as the project due date. All 12 tracks inherit that deadline. Your lead single needs to go out May 1 for pre-release, so you give it an individual due date of May 1. Now you can see at a glance that one track is due sooner than the rest.

A client needs stems by Friday. Set Friday as the project due date. If they need a rough mix even sooner — say Wednesday — put Wednesday on that specific track. The rest keep Friday.

Some projects don’t have a hard deadline. That’s fine — don’t set a due date. You can always add one later when a deadline emerges.

  • Set project due dates as soon as you know the deadline. It’s easier to move a date than to remember to set one later.
  • Use individual track due dates sparingly — only when a specific track has a different timeline than the rest of the project.
  • Check your dashboard regularly to catch overdue items before they become problems.