“Free To-Do List Template for Notion (Download + Guide)”

What is inside the template?

to-do list template for Notion is a key topic in modern project management and teamwork. Two databases and four views. The temptation is to add a third database for areas, a fourth for goals, and a fifth for notes; that structure is correct for a full life operating system and wrong for someone who just wants to finish the week.

If you only build one thing, build the relation. A flat task list with a text field called “Project” looks identical on day one and fails on day thirty, because text fields cannot roll up, cannot be renamed in one place, and drift into “website”, “Website”, and “web site”.

The second structural choice is where new tasks land. Use a single Tasks database and one inbox view, not a separate page per project. Pages feel tidy and force you to decide where a task belongs before you have thought about it, which is exactly the moment capture should be frictionless.

Which properties does the task database need?

Eight properties, each with a job. Notion lets you add twenty; every extra property makes the table wider and the weekly review slower.

Two of these deserve explanation. The “This week” checkbox is manual on purpose: commitment is a decision, not a calculation, and a checkbox you tick during the weekly review is more honest than a filter pretending to know your capacity. The “Days left” formula converts a date into a number so you can sort by urgency without scanning a calendar column.

Avoid a free-text “Notes” property on the task itself. Notes belong in the task page body, where they can hold headings, checklists, and links. A long text property truncates at a glance and encourages people to paste meeting transcripts into a table cell.

How do you connect the two databases?

Build the Projects database first, then the Tasks database, then the relation. Order matters because the relation needs both sides to exist before the rollup can reference anything.

1. Create Projects as a full-page database with three properties: name, status, and deadline.
2. Create Tasks as a full-page database with the eight properties above.
3. Add the relation. In Tasks, add a Relation property pointing at Projects. Enable “Show on Projects” so the reverse relation appears automatically.
4. Add the rollups on the Projects side: one for total tasks, one for completed tasks, one for percent checked if you use a checkbox instead of a status.
5. Add a formula on Projects for progress: completed divided by total, formatted as a percentage, wrapped in `if` so an empty project shows nothing instead of an error.
6. Create the views on the Tasks database, not on Projects. Views are per database, and a view created in the wrong place is the most common source of confusion in shared workspaces.

The rollup settings are where people get stuck. A rollup needs a relation, a property on the related database, and a calculation. “Count all” counts every related row whether or not it has a value; “Count values” skips empty cells. For a task count, use Count all. For a “completed” count, filter the rollup by the Status property and choose the option that counts rows matching a condition.

Percent checked only works with a checkbox property. If you use a Status property with four values, build two rollups (total and done) and divide them in a formula. It is one extra step and it keeps the status model flexible.

Which views should you actually keep?

Four views, each answering one question. Every additional view is a decision you will re-make every time you open the database.

The Today view should be a List, not a Table. On a phone, a list shows the title and the three properties you choose, with no horizontal scrolling. The This week view should be a Table grouped by project, because that is the view where you notice one project has nine tasks and another has one.

The Archive view matters more than it seems. A to-do list that never hides finished work grows into a wall of strikethrough text, and the eye stops trusting it. Filter completed items out of the working views and keep one archive for the “what did I actually do last month?” question that arrives before every performance review.

Keep views on the database, pin the Today view to your sidebar or favorites, and stop opening the raw database. The raw table is a maintenance surface, not a working surface.

How do recurring tasks and quick capture work?

Recurring tasks belong in database templates, not in duplicated rows. Create a template inside the Tasks database, set the properties (including the project relation), then set the template to repeat on the schedule you need. Each repeat creates a fresh row with the correct defaults, which is exactly what a weekly review task or a monthly invoice task needs.

Quick capture is the difference between a system you use and a system you admire. Three options work in practice:

• The mobile widget or app for a task typed in ten seconds while standing in a queue.
• A single “Inbox” view that opens by default, with no filters except Status is To-do and Project is empty.
• A shortcut or automation that appends a line to the database from another tool, if you already live in one.

Whatever you choose, the capture path must not require choosing a project. Triage is a separate step with a separate mindset, and forcing the decision at capture time is how inboxes fill with half-finished rows that nobody trusts.

What does a real week look like in this template?

Forty-seven open tasks across five projects, a Monday review, and a Friday cleanup. On Monday the This week view shows 14 tasks committed, distributed as 6 for the client website, 4 for the internal migration, 2 for hiring, 1 for finance, and 1 personal.

The rollups tell the story before any meeting. The client website shows 18 total tasks, 11 done, so 61% complete. The migration shows 22 total, 4 done, 18%. Hiring shows 3 total, 0 done, and a deadline nine days away. That last line is the one that changes the week: a project at 0% with a near deadline is a decision, not a task.

By Friday, 11 of the 14 committed tasks are done. The three that moved are visible in the Archive filter and get re-committed on Monday with a note about why. No guilt, no lost items, no rebuilding the list.

Now the time math. If the alternative is a paper list plus a notes app plus a calendar, most people spend 12 to 15 minutes a day reconciling them. At 12 minutes a day, five days a week, that is 60 minutes a week, roughly 52 hours a year. A Notion setup that takes 40 minutes to build and 10 minutes a week to review returns that time within two months, provided you do not keep rebuilding the structure.

How do you stop the list from becoming a graveyard?

Cap work in progress, review weekly, and delete without ceremony. Those three habits matter more than any property.

A practical cap is five items in progress per person. The Board view makes the violation visible: a column with eleven cards is not productivity, it is a queue with better branding. When the column is full, the next task waits in To-do, which is exactly what a to-do list is for.

The weekly review is fifteen minutes: clear the inbox, tick This week for what you will actually do, uncheck what you will not, and archive anything that has been carried for three weeks without progress. That last rule is the one people resist and the one that keeps the system honest. A task carried for three weeks is usually a project that needs breaking down or a commitment you should decline.

Deletion is a feature. Notion keeps deleted rows in the trash for thirty days, so removing a stale task is reversible and cheap. A list of 200 items where 60 are dead is worse than a list of 40 live ones, because the dead ones teach you to skim.

How does Notion compare with a dedicated task app?

Notion wins on context and loses on interruption. A task can hold a document, a table, and a discussion, which no lightweight to-do app can match. A lightweight app wins on notifications, widgets, and speed of capture.

The honest recommendation: use Notion when the work needs context, and keep a phone-level reminder for the three things that must not be missed. Splitting those jobs is not a failure of the system; it is using each tool for what it does well.

What mistakes should you avoid?

• Using checkboxes as the only status. A checkbox cannot express blocked or in progress, and the board view becomes useless.
• Creating a database per project. Ten databases mean ten sets of views and no portfolio answer.
• Filtering by “not done” without a date filter. The list grows until it is unreadable.
• Letting the Today view show 30 items. A daily list you cannot finish trains you to ignore it.
• Skipping the weekly review. The template is a structure; the review is the system.
• Over-engineering the dashboard. A progress bar per project is enough; a life dashboard takes a weekend and dies in a month.
• Storing tasks in page bodies. They cannot be filtered, counted, or found again.

Where does Doitify fit?

Notion is a document tool that learned to hold tasks. When the work needs dependencies, workload, deadlines that cascade, and a team view of who is overloaded, a database of rows starts asking you to build a project management system inside it.

Doitify is built for that layer: goals turned into projects, multi-level tasks and sub-tasks with checklists, owners and due dates, WBS dependencies, sprints, calendar and Gantt views, workload reports, and a Copilot that can turn a goal statement into a first draft of the plan. It keeps the document layer too, with project notes, meeting notes, and risks attached to the work they describe.

Transparency: Doitify is our product. For a personal to-do list, the Notion template in this guide is cheaper, more flexible, and probably better suited to how you already write. The switch pays off when several people share the list and dates must react to each other.

Conclusion

A to-do list template for Notion works when the list is a database and the database has a job. Two databases, eight properties, four views, and a fifteen-minute weekly review will outperform any elaborate dashboard, because the structure answers questions instead of decorating them.

Build the relation first, then the Today view, then the rollups. Use it for a week before adding anything else, and delete the views you never open. The point is not a beautiful workspace; it is finishing the right five things before Friday.

If this post on to-do list template for Notion was helpful, you might also enjoy A Day in the Life of a Project Manager (Realistic Walkthrough) and How to Visualize Project Progress.