Get AI summaries of any video or article — Sign up free
Notion Task Manager and Productivity Tracker (Free Template) thumbnail

Notion Task Manager and Productivity Tracker (Free Template)

Red Gregory·
5 min read

Based on Red Gregory's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Create two linked databases: “My Tasks” for task metadata and “Timetable” for scheduled work sessions.

Briefing

A free Notion setup turns task planning into a connected system: tasks feed a weekly timetable of work sessions, and those sessions roll up into hours tracked per task. The core payoff is that every scheduled work block can be tied to a specific task, automatically inherits the task’s deadline, calculates time spent, and then updates task-level totals—so productivity tracking happens as a byproduct of scheduling.

The build starts with two linked databases. The first is a “My Tasks” calendar-style database with key properties: a deadline date, a status select (Not started, Idea, In progress, Completed), a text description, and a formula that derives the weekday from the deadline. A simple “new task” template adds a consistent icon to make task creation faster. Status is also used to create a pipeline board view that groups tasks by stage, while an advanced filter prevents the “Completed” column from growing endlessly by hiding items completed more than a week ago. Those older completed tasks are redirected into an archive-style table grouped by deadline week.

The second database is a “Timetable” built as a timeline view. Each timeline card represents a work session and includes a session name, a checkbox for done, and a “result” select (underachieve, roadblock, productive). A relation property links each session back to a task in “My Tasks.” From that relation, a rollup pulls in the task’s deadline so the session can be scheduled with the right date range. The timetable also calculates session duration: a formula computes hours from the session start and end times (using a minutes-between calculation, then converting to hours and rounding). To support planning, additional formulas label sessions as belonging to “this week” or “next week,” and another formula categorizes the session start time into morning/afternoon/night using hour thresholds and emojis.

To make the system usable day-to-day, multiple filtered views are created from the same timetable: “this week,” “next week,” and “today,” plus a monthly “index” list that groups sessions by month (or by task) and can show totals. The “index” view supports deeper tracking by grouping and sorting sessions, while task pages gain a rollup called “total hours” that sums the hours from all related sessions. That creates a feedback loop: schedule sessions → mark done → automatically accumulate hours on the task.

Finally, everything is assembled into a dashboard homepage with linked views for quick actions: schedule sessions, view today’s timeline, open the task pipeline, and browse the session index. The dashboard also includes a linked tasks table for brainstorming ideas filtered to status “Idea,” letting new ideas become tasks that can later be scheduled into the timetable. The result is a single Notion workspace where planning, execution, and time tracking stay connected through relations, rollups, and carefully designed filters.

Cornell Notes

The setup builds a two-database Notion system where tasks drive a weekly timetable of work sessions. “My Tasks” stores deadline, status, and description, then feeds a pipeline view that hides completed items older than a week into an archive. “Timetable” stores session start/end times, a done checkbox, and a result; each session is related to a task, rollups the task deadline, and calculates hours worked from the time range. Filtered views (“this week,” “next week,” “today”) and a monthly index make scheduling and review fast, while a task-page rollup (“total hours”) sums hours from all linked sessions. This matters because time tracking becomes automatic once sessions are scheduled and marked done.

How does the system prevent the task pipeline from becoming cluttered as tasks accumulate?

The pipeline board groups tasks by status (Not started, Idea, In progress, Completed), but it uses an advanced filter for the “Completed” column. That filter keeps only completed tasks whose deadline is within a relative window: it sets a condition equivalent to “deadline is on or after one week ago” (implemented via a grouped advanced filter with “deadline is on or after one week ago” and the logic adjusted so older completed tasks disappear). Older completed tasks are instead routed into a separate “tasks by week/archive” table view grouped by deadline week.

What makes each timetable card a “work session” tied to a specific task?

Each timeline card in “Timetable” has a relation property named “task” that links back to “My Tasks.” Once the relation is created, the backlink is named “sessions” inside the tasks database. This connection lets the session inherit task data via rollups—most importantly, a rollup property “task deadline” that pulls the task’s deadline into the session so scheduling aligns with the task’s due date.

How are hours worked calculated for a session, and when does the formula run?

A formula property named “hours” calculates duration only when the session’s done checkbox is checked. It uses a date-difference approach: it finds the minutes between the end and start of “work time,” divides by 60 to convert to hours, then rounds to avoid messy decimals (the build nests the computation inside a round strategy using a scaling factor). The result updates after marking the session done.

How do the “this week” and “next week” views decide which sessions belong where?

A “week” formula labels each session by comparing the week number of the session’s “work time” date to the current week number. It formats the date of work time as a capital “W” (week number from Monday to Sunday), converts it to a number, and then uses an if/else structure: if the session’s week number equals the current week number, it returns “this week”; if it equals current week number + 1, it returns “next week”; otherwise it returns blank. Filtered views then show only sessions whose “week” formula matches the target label.

What role do rollups play in turning session data back into task-level metrics?

On each task page, a rollup property called “total hours” sums the “hours” values from all related timetable sessions. The rollup is configured using the sessions relation and the “hours” property, with a sum aggregation. This means marking sessions done and setting their start/end times automatically updates the task’s total time spent.

How does the dashboard enable quick scheduling and idea capture without leaving the homepage?

The homepage uses linked database views. It places quick links to “schedule sessions” (this week), “today’s timeline,” “my task pipeline,” and “session index.” For adding sessions, the linked view is configured to show a minimal set of properties (like start time and done) and uses filters such as “name contains session” and “work time is today,” so new sessions default to today and can be given an end time and task relation. For brainstorming, it links to tasks with a filter like “status is idea,” so new ideas can be added as tasks and later scheduled into the timetable.

Review Questions

  1. What specific filter logic keeps the “Completed” column from growing indefinitely in the tasks pipeline?
  2. Describe the chain of data flow from a task deadline to a timetable session (relation + rollup).
  3. How does the “hours” formula ensure accurate time tracking and avoid counting sessions that aren’t marked done?

Key Points

  1. 1

    Create two linked databases: “My Tasks” for task metadata and “Timetable” for scheduled work sessions.

  2. 2

    Use a status pipeline view for tasks, then apply an advanced filter so completed tasks older than a week move out of the main pipeline.

  3. 3

    Connect each timetable session to a task via a relation, then roll up the task deadline into the session for consistent scheduling.

  4. 4

    Calculate session duration with a formula that runs only when the done checkbox is checked, converting minutes between start/end into rounded hours.

  5. 5

    Add filtered timetable views for “this week,” “next week,” and “today” using a week-label formula based on ISO-style week numbers (Monday–Sunday).

  6. 6

    Use a task-page rollup (“total hours”) to sum hours from all related sessions, turning scheduling into automatic reporting.

  7. 7

    Assemble everything into a dashboard using linked views so sessions and ideas can be added quickly from one homepage.

Highlights

A relation + rollup connection makes each work session inherit the task deadline, so scheduling stays consistent without manual copying.
Session hours are computed from start/end times only after marking the session done, reducing accidental or premature time totals.
Filtered timetable views (“this week,” “next week,” “today”) are driven by a week-number formula based on Monday–Sunday week boundaries.
Task pages gain a “total hours” rollup that sums hours across all linked sessions, creating an automatic time-tracking loop.
The dashboard relies on linked database views with tight filters, enabling quick session scheduling and idea capture from the same page.

Topics

Mentioned