Due Date Widget
The due date widget lets you assign deadlines to individual tracks. Whether you have a client expecting a mix by Friday or a personal goal to finish a beat this week, setting a due date keeps you accountable and makes overdue items visible at a glance.
Setting a Due Date
Section titled “Setting a Due Date”- Select a track in the grid and open the activity panel.
- Find the Due Date widget.
- Click the date field or the calendar icon.
- A date picker opens. Select the date you want.
- The due date is set immediately and appears in the widget and the grid.
There is no save button. The date applies as soon as you select it and syncs in the background.
The Calendar Picker
Section titled “The Calendar Picker”The date picker is a standard calendar view. Navigate between months using the arrow buttons. Click a date to select it. The selected date highlights so you can confirm your choice at a glance.
Today’s date is always marked for reference, making it easy to count how many days remain before a deadline.
Changing a Due Date
Section titled “Changing a Due Date”To move a deadline, click the date field in the widget and select a new date from the picker. The old date is replaced with the new one instantly. There is no separate edit mode — just click and pick.
Clearing a Due Date
Section titled “Clearing a Due Date”If a deadline is no longer relevant, click the clear button (an X icon) next to the current date. The field returns to its empty state and the track no longer shows as having a deadline.
You might clear a due date when a project is put on hold, when a client extends a deadline indefinitely, or when the track has been delivered and the date no longer applies.
Project Deadline Inheritance
Section titled “Project Deadline Inheritance”If the track belongs to a bucket (project) that has its own deadline, the widget shows that project deadline as an inherited date. This gives you context on the overall timeline even when you have not set a track-level due date.
The inherited date is displayed with a label like “Project deadline” so you can distinguish it from a date you set manually on the track itself.
| Scenario | What Displays |
|---|---|
| Track has its own due date | Track date shown as primary |
| Track has no date but project does | Project date shown as inherited |
| Neither has a date | Empty state |
If you set a track-level due date, it takes precedence and displays as the primary deadline. The project deadline still appears for reference so you always have both in view.
Overdue Indicators
Section titled “Overdue Indicators”When a due date passes without the track being moved to a completed stage (like Published or Archived), an overdue indicator appears. You will see this in:
- The due date widget itself — the date turns red
- The tracks grid — an overdue badge on the row
- The dashboard — in the upcoming deadlines section
Overdue indicators clear automatically when you either update the due date to a future date or advance the track to a completed workflow stage. There is no manual dismiss — fixing the underlying situation removes the warning.
Due Dates in the Grid
Section titled “Due Dates in the Grid”The due date column in the track grid shows the assigned date (or inherited project date) for each track. Overdue dates are highlighted so they stand out when you are scanning rows.
You can sort the grid by due date to see your most urgent tracks first. Combined with stage filtering, this gives you a focused view like “all tracks in Editing stage, sorted by deadline” — a natural workflow for tackling revision lists in priority order.
Multi-Select Behaviour
Section titled “Multi-Select Behaviour”When you select multiple tracks, the due date widget lets you set the same deadline on all of them at once. This is handy when:
- An entire EP has the same delivery deadline
- A batch of tracks for a client all need to be done by the same date
- You want to set a personal target date for a group of works in progress
If the selected tracks have different due dates, the widget shows a mixed indicator. Setting a new date applies it to all selected tracks simultaneously.
- Set due dates early. Even a rough deadline helps you prioritise when your library grows. You can always adjust it later.
- Use project-level deadlines for albums. Set the deadline on the bucket and let it inherit to all tracks. Override individual tracks only when they have their own specific deadline.
- Sort by due date regularly. Make it a habit to sort the grid by due date at the start of your session. It immediately shows you what needs attention first.
- Clear dates you no longer need. Stale deadlines add visual noise. If a project was shelved, clear the dates so they do not trigger overdue warnings.
- Combine with stage filters. Filter to “Editing” and sort by due date to see your revision priorities in order.
Related
Section titled “Related”- Using the Activity Panel — how the full panel works
- Todos Widget — task-level deadlines within a track
- Creating Projects — setting up buckets with project deadlines
- The Tracks Grid — sorting and filtering by due date
- Overview Widget — quick summary including deadline status