How to Make a Weekly Planner in Notion with One Task Database

← All Notion guides · See the example

A useful weekly planner answers one question: what will I work on this week? Start with one task database and a view of the work you have scheduled. You can add projects and automation later.

Separate a work date from a deadline

Planned Date is when you intend to work on the task. Due Date is when the result must be delivered. You might plan to draft a proposal on Tuesday even though its deadline is Friday.

Moving the planned work to Wednesday should not silently move Friday’s deadline. Two Date properties keep those decisions separate. If your tasks do not have external deadlines, leave Due Date empty rather than inventing one.

1. Set up one task database

Use your existing task database if you have one. For a fresh practice area, create a database with these properties:

• Name: the task title.
• Planned Date: Date, using single dates without times for this exercise.
• Due Date: Date, optional.
• Done: Checkbox.

Keep an unfiltered table view named All tasks. Your weekly view will hide work outside its rules; All tasks gives you a place to find and reschedule it. The views show the same records, so you do not need a new database every Monday.

2. Choose which week you are planning

For the first build, use explicit start and end dates. This makes it easy to check which tasks should appear. The worked example uses Monday 5 October to Sunday 11 October 2026. Choose the corresponding dates for your own week.

Create a table view called This week. In the view settings, choose Filter and combine these conditions with AND:

Add a sort on Planned Date, ascending. With single dates without times, both boundary days are included. Do not apply this recipe unchanged to time-specific appointments or date ranges.

This is a manually selected week. Naming the view This week does not make fixed dates advance automatically. At your next weekly review, change both boundary dates. If you later use a relative week filter, test which days it includes in your workspace before replacing the fixed-date version.

Notion supports multiple views, property filters and sorts. The controls used here follow Notion’s official database-view documentation.

What your week should contain

These six fictional tasks illustrate the week of 5–11 October 2026. Enter the actual dates in Date properties; the table is a practice example, not a screenshot from a Notion workspace.

Which three tasks appear in This week?

Draft proposal, Send feedback summary and Plan the following week, in that order. Each has a Planned Date inside the selected week and is unfinished. The call is completed, project notes are unscheduled and the next project is planned for 12 October.

This week · unfinished

6 Oct — Draft proposal

9 Oct — Send feedback summary

11 Oct — Plan following week

Unscheduled · unfinished

Collect project notes

Planned Date: empty
Due Date: 8 Oct

Illustrative result, not a Notion screenshot. The deadline does not place Collect project notes in the weekly view: its Planned Date is empty.

3. Keep unscheduled work visible

Using a calendar view? Check why a task is missing from your Notion calendar before making another copy.

Create an Unscheduled view with Planned Date empty AND Done unchecked. Collect project notes belongs here even though its Due Date is 8 October. A deadline is not automatically a plan for when to do the work.

Review this view when planning your week. Decide when you can realistically work on each task, then set its Planned Date. Do not give every task Monday’s date just to empty the list.

4. Check the planner with one change

1. In your practice records, give Collect project notes a Planned Date of 7 October. It should enter This week and leave Unscheduled.
2. Tick Done on Draft proposal. It should leave This week while remaining in All tasks.
3. Find it in All tasks, untick Done and move its Planned Date to 12 October. It should stay outside the selected week.
4. Restore the practice values when you finish.

When a task disappears from a filtered view, it has not been deleted. Look in All tasks and check the date and completion properties.

A short weekly review

Repeating the same review each week? Create a recurring task with a repeating database template, then give each new occurrence a Planned Date.

Open All tasks and review unfinished work, including tasks planned before the selected week. Decide what to finish, move or drop. Check deadlines separately: a task scheduled for next week may already have a missed deadline.

Then review Unscheduled, choose work that fits your week and update both date boundaries. Start with a table; add a calendar view on Planned Date only if seeing work across days helps you make those decisions.

If you share the weekly view, use Save for everyone when appropriate. Filters organise what a view displays; they do not restrict access to the underlying database.

A five-minute weekly reset

Review All tasks before choosing the next week’s work. Keep unfinished records; moving them to a new planned date is clearer than creating another copy and leaving the original behind.

First inspect overdue deadlines. Then inspect tasks with no Planned Date. Choose the work you can realistically schedule, keeping Due Date as the actual deadline rather than changing it to make the week look tidy.

Finally, check the weekly view’s date range and completion rule. The fixed practice week in this guide is a test dataset, so its results stay reproducible. When using a different week, update the practice dates and expected results together.

Common mistake: an empty weekly view can look like a finished workload while unscheduled tasks still exist. Keep the unscheduled queue beside your plan and review it deliberately. A filtered view is one perspective on your database, not a complete list of everything you owe.

Add a calendar without creating another task list

Add a Calendar view of the same source database. Under Layout → Show calendar by, choose Planned Date. Use the same fixed-week and Done filters as This week, then navigate to the practice month. The calendar and table should agree about which tasks qualify.

For the existing 5–11 October practice data, the work belongs on 6, 9 and 11 October. Keep the table available to inspect the properties. If you use another week, update the records and both filter boundaries together.

Check capacity before filling dates. Choose a next action you can realistically do. An unscheduled task with a deadline still needs review; assigning every task to Monday simply hides the scheduling decision.

For a closer look at the two date fields, see Planned Date versus Due Date. For shared work, also review unfinished tasks without an owner before committing to the week.

Frequently asked questions

Do I need a new task database every week?

No. Keep one task database and change the weekly view’s date boundaries. Unfinished and completed tasks remain in the same source.

What is the difference between Planned Date and Due Date?

Planned Date records when you intend to work on a task. Due Date records its deadline. Rescheduling work does not automatically change the deadline.

Why is a task missing from my weekly planner?

Check its Planned Date, the selected date range and its Done checkbox. An undated, completed or out-of-week task is excluded by this recipe. Find the original record in All tasks.

Does the practice view automatically advance to next week?

No. It uses fixed dates so you can reproduce the expected results. Update both date boundaries when planning another week.

Can I use Status instead of a Done checkbox?

Yes, but adapt the completion filter to your actual Status options. Replace the Done condition with a rule that excludes your completed status, then test a finished task and an unfinished task.