← All Notion guides

Notion Guide

How to Count Tasks With Missing Due Dates on a Notion Project

A project can show an earliest deadline while several related tasks have no deadline recorded. Add a separate missing-date count so the date summary does not look more complete than its inputs.

This recipe counts empty Due Date values across all tasks in a project’s selected relation. It is a data review signal, not an automatic scheduling decision.

What you will build

A Rollup property called Tasks Without Due Dates, plus a task view that shows which records contribute to that count.

1. Check the relation and the date property

Use your existing Projects and Tasks sources. Tasks needs a Project relation and a Date property called Due Date. Projects needs the relation containing its tasks.

If the project-side property is missing, follow the two-way relation guide. Do not create an unrelated second connection just to build the summary.

2. Prepare four fictional tasks

Expected missing-date count: two related tasks.
Task Due Date Done
Prepare homepage draft Recorded date Unchecked
Confirm image selection Empty Unchecked
Check copy references Empty Checked
Prepare handover Recorded date Unchecked

Connect all four to one fictional project. The expected count is 2, including the completed record with an empty deadline.

3. Add the missing-date rollup

  1. In Projects, add a Rollup property.
  2. Name it Tasks Without Due Dates.
  3. Select the relation containing the project’s tasks.
  4. Select Due Date as the related property.
  5. Choose Count empty.
  6. Compare the result with the four test records.

Notion documents Count empty as a calculation on empty values in related pages; see its rollup documentation.

4. Test one change and restore it

Give Confirm image selection a fictional deadline. The count should fall from 2 to 1. Clear that test date and confirm that the count returns to 2.

If it does not, inspect the relation’s selected pages and the rollup’s chosen property. A similarly named date field can summarize the wrong inputs.

5. Show the contributing records

On the fictional project page, create a linked Table view of Tasks. Combine Project contains this project AND Due Date is empty.

Show Task, Due Date and your completion field. The two empty-date records from the example should appear.

Keep this view aligned with the rollup’s scope. If you exclude completed tasks from the view, it will show one record while the all-task rollup still counts two. That difference is expected, but the labels must make it clear.

Use the missing due dates guide for the record-level review.

6. Decide whether a date is actually needed

An empty date might mean an overlooked deadline, a task awaiting a decision or work with no genuine deadline. Check the context before entering one.

A completed historical task may not need an invented deadline. An administrative action might need a planned work day but no delivery commitment.

The Planned Date versus Due Date guide explains that distinction. Do not improve the count by filling dates that do not mean anything.

7. Interpret zero carefully

Zero means the selected related input set has no empty Due Date values. It does not prove every task is connected, every date is correct or the project is fully planned.

Inspect the task relation too. A project with no related tasks has no task deadlines to review; do not read its summary alone as proof of complete scheduling.

Common mistakes

  • Calling the count Unscheduled tasks when it checks Due Date rather than Planned Date.
  • Expecting completed records to be excluded automatically.
  • Comparing an all-task rollup with an unfinished-only view without noting the difference.
  • Assigning arbitrary deadlines just to reach zero.

Frequently asked questions

Does this count only unfinished tasks?

No. This recipe checks all tasks in the selected relation, including completed records.

Why does my review view show fewer tasks than the rollup?

Compare their scopes. Completion or other view filters can exclude records that remain included in the rollup relation.

Should every empty date be filled?

No. Review whether the task actually needs a deadline before entering one.

Does zero prove the project is fully scheduled?

No. Check relation completeness, date meaning and the actual work plan separately.

Can I use Planned Date instead?

Yes. Select that property and rename the rollup to describe missing planned dates rather than missing deadlines.

Explore the wider workflow

This process can sit alongside your existing projects. For a broader client and project workspace, explore Freelancer CRM and compare its structure with how you work.

Explore Freelancer CRM →