Remote Ops

Show Project Progress from Related Tasks in Notion with a Rollup

How do I show the percent of tasks done for each project in Notion using a relation and rollup?

Connect Tasks to Projects with a two-way relation. On Projects, count all related tasks, count the ones whose Status is Done, and divide. Keep the two counts as their own properties, because a total across projects must be summed done over summed total, not an average of the project percentages.

What you need

  • A Notion Projects database and a Tasks database in the same workspace
  • A Status property on Tasks with an option named Done
  • Permission to add properties to both databases

To show progress on each project in Notion, connect a Tasks database to a Projects database with a two-way relation, then count the related tasks on the project side: all of them, and the ones marked Done. Divide the second count by the first and you have the percent complete. Keep both counts visible. They are what lets you report an honest total across several projects later, which an average of the percentages cannot do.

How the two databases fit together

Each task belongs to one project, and each project lists its tasks. Notion handles that link with a relation property.

Database Property Type Holds
Tasks Name Title The task
Tasks Status Status Not started, In progress, Done
Tasks Project Relation to Projects The project this task belongs to
Projects Name Title The project
Projects Tasks Relation (the other side of Project) Every task linked to this project
Projects Total tasks Formula Count of related tasks
Projects Done tasks Formula Count of related tasks with Status Done
Projects Progress Formula Percent done, or “No tasks”

The Tasks property on Projects is not something you create by hand. It appears when you make the relation two-way. Notion’s relations and rollups article says relations are one-way by default and that turning on the toggle labelled “Show on” followed by the related database’s name adds the matching property on the other side.

Building the relation and the progress properties

Start with the relation, then add the three formulas on Projects.

  1. Add the relation on Tasks. In the Tasks database, add a new property, name it Project, and choose the Relation type. Select the Projects database.
  2. Make it two-way. Turn on “Show on Projects” and name the related property Tasks. Review the preview, then select Add relation.
  3. Link some tasks. Open a few tasks and pick their project in the Project property. Each project’s Tasks property fills in to match.
  4. Add the counts on Projects. Add three formula properties to Projects with the formulas below. Name them exactly Total tasks, Done tasks, and Progress, because Progress refers to the other two by name.
// Total tasks
prop("Tasks").length()

// Done tasks
prop("Tasks").filter(current.prop("Status") == "Done").length()

// Progress
if(
  prop("Total tasks") == 0,
  "No tasks",
  format(round(prop("Done tasks") / prop("Total tasks") * 100)) + "% (" +
    format(prop("Done tasks")) + " of " + format(prop("Total tasks")) + ")"
)

These formulas read the related tasks directly. Notion’s Formulas 2.0 guide says formulas can now reach properties in a related database without first creating a rollup, and the formula syntax reference lists prop("Tasks").length() and prop("Tasks").filter(current.prop("Status") ...) as relation examples. Inside filter, current stands for each related task in turn, so the filter keeps only tasks whose Status reads Done. length() counts what is left.

Progress returns text, so the empty case can say “No tasks” instead of showing 0%. A project with no tasks has not made zero progress; it has nothing to measure. Change "Done" in the second formula if your finished option has a different name.

If you prefer a rollup property

The relations help article documents rollups with these calculations for any property: Show original, Show unique values, Count all, Count values, Count unique values, Count empty, Count not empty, Percent empty, and Percent not empty. Number properties add Sum, Average, Median, Min, Max, and Range.

That list is enough to rebuild the counts without the relation formulas:

  • Total tasks: a rollup on the Tasks relation, property Name, calculation Count all.
  • Done tasks: first add a formula on Tasks called Done (1/0) with if(prop("Status") == "Done", 1, 0). Then add a rollup on Projects over the Tasks relation, property Done (1/0), calculation Sum.

Divide one rollup by the other in a formula, as in Progress above. Third-party tutorials mention other percentage options for Status and checkbox properties. The help article does not list them, so check what your own rollup menu offers before building on one, and keep the underlying counts visible either way.

Rollups and formulas give the same numbers here. The formula route needs fewer properties; the rollup route may feel more familiar if your team already uses rollups elsewhere.

Worked sample: three projects and one empty one

The sample has four projects and fifteen linked tasks. The tasks for the first two projects are listed in full:

Task Owner Project Status
Measure the new office Avery Example Office move Done
Book the movers Riley Placeholder Office move Done
Order desks Morgan Sample Office move Done
Set up the guest Wi-Fi Avery Example Office move In progress
Move payroll to the new provider Morgan Sample Payroll switch Done

Website refresh has ten tasks, two of them Done. Hiring plan has no tasks yet. The formulas give:

Project Total tasks Done tasks Progress
Office move 4 3 75% (3 of 4)
Payroll switch 1 1 100% (1 of 1)
Website refresh 10 2 20% (2 of 10)
Hiring plan 0 0 No tasks

Office move: 3 / 4 * 100 = 75. Payroll switch: 1 / 1 * 100 = 100. Website refresh: 2 / 10 * 100 = 20. Hiring plan hits the Total tasks == 0 check and never divides.

Why averaging the project percentages overstates progress

Suppose someone wants one number for all active work. The tempting move is to average the Progress column: (75 + 100 + 20) / 3 = 65%.

That figure treats the one-task payroll switch as equal in weight to the ten-task website refresh. Count the tasks instead: 3 + 1 + 2 = 6 done out of 4 + 1 + 10 = 15 total, which is 40%. Sixty percent of the work across these projects is still open, and the average hides that because the small finished project pulls the number up.

The fix is to add up the counts, then divide once. In a Notion table view, the relations help article describes clicking a property, hovering over Calculate, choosing More options, and picking Sum. Do that for Done tasks and Total tasks, then divide the two totals. Do not take the average of Progress; it is text in this template partly so that nobody can.

The same rule applies on any dashboard. This guide to calculating a completion rate without averaging percentages walks through the arithmetic in SQL, including how to keep a group with no tasks undefined rather than at 0%.

Hiring plan also stays out of the total. It has nothing to count, so it adds 0 to both sums and does not change the result. If empty projects are a problem in their own right, look for them separately; finding projects with no tasks using a SQL LEFT JOIN shows the same check on exported data.

When task counts are the wrong measure of progress

Counting Done tasks treats a ten-minute task the same as a two-week one. For a project where one task dominates the effort, 3 of 4 done can still mean most of the work is ahead. If that matters, add a number property such as Estimate to Tasks, sum the estimate of Done tasks and of all tasks, and divide those instead. The structure is identical; only the thing being counted changes.

Two other cases need care. If a task can belong to more than one project, it counts once in each, so the portfolio totals overstate the number of distinct tasks. And if tasks move between projects, the percentages change without anyone finishing anything. Keep Project to a single choice where you can, and add a note to the project page when tasks are moved.

If you report progress to a remote team on a schedule, a weekly snapshot avoids arguments about numbers that changed mid-meeting; this guide to automating a weekly report page in Notion shows one way to publish one. More guides on running projects across time zones are on the remote operations topic page.

Sources

Esc