Due Dates & Deadlines

Deadlines keep things moving. Whether it’s a label submission date, a client delivery, or a self-imposed release goal, due dates in Producer Dashboard help you see what’s coming up and what’s already overdue.

Where You Can Set Due Dates

Due dates can be set at two levels:

On individual tracks — For specific deadlines on a single song
On projects — For a blanket deadline that applies to everything inside

Both work together through inheritance (covered below), so you get flexibility without having to set dates on every single track.

Setting a Due Date on a Track

Inline in the Grid

Find the track in the grid
Click the due date cell in that row (it might be empty or show an existing date)
A date picker appears
Choose a date and confirm
The date shows up immediately in the grid

From the Activity Panel

Select a track to open it in the activity panel on the right
Look for the Due Date widget
Click it to open the date picker
Select your date

Both methods do the same thing — pick whichever is more convenient based on whether you’re scanning the grid or focused on one track.

Setting a Due Date on a Project

Project-level due dates cover every track inside the project. See Project Due Dates for a detailed walkthrough, but the short version:

Right-click the project in the sidebar
Open the project settings
Set the due date

How Inheritance Works

The inheritance rule is straightforward:

If a track has its own due date, that date is used
If a track has no due date but its project does, the project’s date is inherited
If neither has a due date, no deadline is shown

Individual track dates always take priority over project dates. This lets you set a general project deadline and then override specific tracks that have different timelines.

Example

Your EP is due June 1 (set on the project). Five tracks are inside:

Track	Own Due Date	Displayed Date	Source
Lead Single	May 1	May 1	Track’s own date
Track 2	—	June 1	Inherited from project
Track 3	—	June 1	Inherited from project
Bonus Track	July 15	July 15	Track’s own date
Track 5	—	June 1	Inherited from project

The lead single has an earlier date because it’s dropping first. The bonus track has a later date because it’s a deluxe release. Everything else follows the project deadline.

Overdue Indicators

When a due date passes and the track hasn’t reached its final stage (Published or Archived), Producer Dashboard flags it as overdue:

Red date text in the grid’s due date column
Red accent on the due date widget in the activity panel
Overdue badge on the project in the sidebar
Dashboard highlight in the upcoming deadlines section

These visual cues make overdue items impossible to miss. You’ll see red and know something needs attention.

What Counts as Overdue

A track is overdue when:

Its due date (own or inherited) is in the past, AND
It hasn’t been moved to Published or Archived

Once you mark a track as Published (or Archive it), the overdue indicator clears regardless of the date.

Your dashboard includes an Upcoming Deadlines widget that gives you a consolidated view of what’s due soon:

Shows tracks and projects ordered by their due dates
Overdue items appear at the top with red indicators
Upcoming items show how many days are left
Click any item to jump to that track or project

This is the first thing to check when you open the app — it tells you what needs your attention today.

Changing and Removing Due Dates

Changing a Date

Click the due date (in the grid or activity panel) to reopen the date picker. Choose a new date, and the change applies immediately.

If you change a project’s due date, every track inheriting from that project updates automatically. Tracks with their own individual dates are not affected.

Removing a Date

To clear a due date, open the date picker and use the clear/remove option. The date disappears, and if it was a project date, any tracks that were inheriting it lose their deadline (unless they have their own).

Sorting and Filtering by Due Date

The grid lets you sort and filter using due dates to prioritise your work:

Sorting

Click the due date column header to sort by deadline:

Ascending — Soonest deadlines first (most urgent at the top)
Descending — Furthest deadlines first

Tracks with no due date typically sort to the bottom when ascending, giving you a clean view of what’s time-sensitive.

Filtering

Use the filter controls to show only:

Tracks due within a specific date range
Overdue tracks only
Tracks due this week, this month, etc.

Combine with stage filters for maximum focus: “Show me all tracks in Mixing that are due this month.”

Due Dates and Stages Together

Due dates and stages complement each other:

Stages tell you what phase a track is in (where it is in the process)
Due dates tell you when it needs to be done (the time pressure)

A track in the Mixing stage with a due date two days from now is urgent. The same track with a due date three months out is not. Use both dimensions to make good decisions about what to work on.

The Kanban view with due date indicators gives you the best of both worlds — you see the process flow and the time pressure in one view.

Tips

Set project due dates for any release with a hard deadline. It saves you from adding dates to every individual track.
Use individual track due dates only when a specific song has a different timeline from its project.
Check the dashboard deadlines widget daily. It takes two seconds and keeps you from being surprised by an approaching deadline.
Don’t set due dates on everything. If a project is exploratory with no real deadline, leave it open. Due dates lose their power if every track has one.
When a deadline changes (and it will), update the date rather than removing it. Keeping the new date visible helps you stay accountable.

Project Due Dates — Deep dive into project-level deadlines and inheritance
Understanding Stages — How stages and dates work together
Tracking Progress — Combine deadline awareness with progress tracking
Creating Projects — Set up projects where you can assign due dates