Skip to content

Smart Notifications

Producer Dashboard does not wait for you to go looking for problems. Smart notifications proactively surface things that need your attention so you can stay on top of your production workflow.

PD monitors your library and alerts you about situations that typically require action. Here is what triggers a notification:

When a track or project has a due date approaching, you get a notification. The closer the deadline, the more prominent the alert becomes. This ensures time-sensitive work does not sneak up on you.

  • 3 days before — a gentle heads-up that a deadline is approaching.
  • 1 day before — a more prominent alert that tomorrow is the day.
  • Due today — highlighted as urgent.

If a due date has passed and the track is still not at a completed stage, PD flags it. Overdue notifications are the most urgent type and are highlighted in red wherever they appear. They persist until you either complete the work, update the due date, or remove the deadline.

When a track has not been updated in 30 or more days (and is not in the Published or Archived stage), PD considers it abandoned and includes it in your notifications. This is a softer alert — more of a nudge than an alarm — designed to help you remember work you might have forgotten about.

If a collaborator has sent you a track or you have an unresolved collaboration request, PD notifies you so it does not get lost in the shuffle.

PD flags tracks that are missing commonly useful metadata:

  • No BPM — the track has not had its tempo detected or entered.
  • No key — the musical key is unknown.
  • No tags — the track has no tags applied.

These are not urgent, but filling in metadata makes your library more searchable and useful over time. The notifications are gentle reminders to keep your data clean.

Songs that are not assigned to any project (bucket) get flagged. This helps you keep your library organised. Unassigned tracks are harder to find later and do not appear in project-based views.

Not all notifications are equally important. PD prioritises them so the most urgent items get your attention first:

PriorityTypeWhy
HighOverdue tracksYou already missed a deadline
HighDue todayAction needed now
MediumDue within 3 daysAction needed soon
MediumPending collaborationSomeone is waiting for you
LowAbandoned tracksWorth reviewing but not urgent
LowMissing metadataHousekeeping, not time-sensitive
LowUnassigned tracksOrganisational, not urgent

High-priority notifications are always shown first and with the strongest visual treatment. Low-priority notifications are still visible but do not compete for attention with urgent items.

Smart notifications are entirely automatic. You do not need to set up rules, configure triggers, or create alerts. PD generates notifications based on the state of your data.

The logic is simple and transparent:

  • Has a due date and it is approaching? Notification.
  • Has a due date and it has passed? Notification.
  • Has not been touched in 30+ days? Notification.
  • Is missing BPM, key, or tags? Notification.
  • Is not in any project? Notification.

There is no machine learning or complex prediction. The rules are straightforward so you always understand why a notification appeared.

Some notifications can be dismissed, and some resolve themselves:

  • Deadline notifications resolve when you complete the work, update the due date, or remove the deadline.
  • Abandoned track notifications resolve when you make any change to the track.
  • Missing metadata notifications resolve when you add the missing data.
  • Unassigned track notifications resolve when you assign the track to a project.

You do not need to manually dismiss most notifications. Take the action, and the notification goes away.

PD does not bombard you. Each notification appears once and stays visible until resolved. You will not get repeated alerts for the same issue. If a track is overdue, you see one overdue notification for it — not a new one every day.

This keeps the notification list manageable even if you have a large library with many items needing attention.

  • Address high-priority notifications first. They are sorted that way for a reason.
  • Use missing metadata notifications as a prompt to run audio analysis on tracks that do not have BPM/key data yet.
  • If you have many abandoned tracks, consider setting aside 15 minutes for a triage session. Archive what you do not need and update what you want to keep.
  • Pending collaboration notifications should be acted on quickly — someone is waiting for a response.
  • If notifications feel overwhelming, focus on the red (high-priority) items first and work your way down.