Reminders and due dates

Time-based prompts attached to nodes for tracking deadlines and follow-ups.

Due dates attach a target completion time to a node. Reminders are notifications fired at or before the due date. Both are time-based prompts that help the team track deadlines and follow-ups.

Due dates

A due date is a single date (and optionally a time) by which a node is expected to be complete. Due dates are descriptive metadata, not enforcement: Tree does not prevent work from continuing past a due date, but it does flag the node visually and surface it in date-based filters.

Due dates support:

  • Absolute scheduling: specific dates like "2026-06-15"
  • Relative scheduling: "due in 2 weeks from creation"
  • Recurring patterns: due on the same date each month or quarter (see Recurring nodes)

Due dates are queryable via Advanced date queries.

Reminders

A reminder is a notification that fires at or before a node's due date. Reminders can be:

  • A single notification at the due date
  • A series of notifications in the lead-up (one week before, one day before, on the day)
  • Custom intervals set per node

Notifications are delivered via the configured channel: in-app notification, Slack (see Slack notifications), email, or webhook (see Webhooks).

What happens past the due date

A node past its due date is flagged visually but otherwise unchanged. The team can:

  • Reschedule by updating the due date
  • Complete the node late without any penalty in the data model
  • Filter for overdue nodes to see what's slipping

Tree does not auto-fail or auto-escalate overdue nodes. The graph carries the information; the team decides what to do with it.

Reminders and due dates surface in the Tree of your day view automatically. A reminder firing today appears as a time-anchored entry on the day. Past-due items appear as carryover at the top of the next day's view.

Tier availability

Reminders and due dates are part of the core feature set, available on Free, Paid, and Team.

LAST UPDATED · 2026-05-12