Project Due Dates

Projects have an optional deadline, and tracks can have their own due dates. When a project deadline changes, The Library automatically cascades that deadline only to tracks in the project that do not already have an individual due date.

Setting a Project Deadline

When you set a deadline on a project, you’re establishing a target date for everything in that folder. This is useful for aligning with release dates, sync deadlines, or client deliverables.

Update the project’s deadline through its project controls. The update requires project ownership and uses the project’s validated mutable fields.

Setting Individual Track Due Dates

Sometimes a single track needs a different deadline than the rest of its project. Maybe one song requires extra mastering time, or a specific client needs an earlier version. Individual due dates let you override the project deadline for that track.

Use the Due Date widget for one or more selected tracks. It supports optimistic updates and rolls all selected values back if any persistence request fails.

When you set an individual due date, it takes precedence over any project-level deadline for that track only.

How Cascading Works

When you set a deadline on a project, The Library automatically applies that deadline to all tracks within it. This happens instantly and keeps your pipeline consistent.

However, the cascade follows a simple rule:

Tracks without an individual due date inherit the project deadline
Tracks with an individual due date keep their custom date

This means you can set a project deadline, have most tracks automatically follow it, and still give specific tracks their own timeline when needed. The system respects both levels of control without conflict.

For example, imagine your “Summer Release” project has a deadline of July 15:

Ten tracks with no individual dates show July 15 as their due date
Two tracks you manually set to June 30 keep that earlier date
One track you set to August 1 keeps its later date

This makes it easy to manage both uniformity and exceptions within the same project.

Editing and Updating Deadlines

Deadlines change as projects evolve. You can update a deadline at any time:

For projects — update the project’s deadline
For tracks — use the selected-track Due Date widget

When you update a project deadline, the cascade automatically propagates the change to all tracks that don’t have individual overrides. This keeps everything synchronized without manual effort.

Tips

Use project deadlines as your primary timeline tool, then override only the tracks that genuinely need different dates
If a track’s due date seems wrong, check whether it has an individual override before adjusting the project deadline