🔥 BLACK FRIDAY SALE | Get 50% OFF all templates & courses with code BF2026. Ends November 30!
How to Get Started with Notion: A Simple First Setup
Learn Notion's four core concepts, build a simple checklist, and add task statuses, due dates, and filtered views only when you need them.
7 min read


The simplest way to get started with Notion is to build one thing you already need. Create a page, add a few tasks, and use that list before exploring the rest of the app. You do not need a dashboard, formulas, or a complete life-management system on your first day.
This tutorial starts with a basic checklist. If you need deadlines and a way to separate finished work from unfinished work, you can turn the same idea into a small task database. Along the way, you will learn four concepts: pages, blocks, databases, and views.

Table of Contents
Understand the four concepts without learning every feature
Think of Notion as a set of building pieces rather than a finished notebook with a fixed layout. A handful of pieces is enough to make something useful.
Pages are places to keep information. A page can contain notes, a checklist, and other pages. A page inside another page is a subpage.
Blocks are the pieces inside a page: paragraphs, headings, checkboxes, images, and more. You can move a block or change its type.
Databases organize collections of pages with shared properties. In a task database, each task is a page, and properties describe its status or deadline.
Views show that database in different ways. A table can show everything, while a filtered list shows only unfinished tasks.
These are not four separate apps. A database entry is still a page, and its notes are still blocks. Views let you change what you see without creating another copy of every task.
For a fuller explanation of the first two pieces, read the guide to Notion blocks versus pages. If you are still deciding what the app is for, the Notion overview covers that broader question. Here, the goal is to get something working.
Create a page and add your first checklist
These instructions are easiest to follow in Notion's desktop app or web version. The exact onboarding screen can vary, so start from a new empty page rather than trying to match every item in the sidebar.
Use the sidebar's new-page control to create a page.
Name it Tasks.
Click in the empty page body and type
/to-do.
Choose the To-do list block.
Add one real task, then press Enter to add another checkbox.
Start with three tasks such as Send the project update, Book the appointment, and Review the meeting notes. Click a checkbox to mark a task complete. Click again to uncheck it.
Add a short text block above the list if you need context, such as “Things to finish this week.” Select text to make it bold, or use the six-dot block handle to open its menu and turn it into a heading. You can also drag that handle to move the block.
If one task needs a smaller step beneath it, drag another to-do block underneath it and slightly to the right to nest it. For example, Draft three bullet points can sit beneath Send the project update.


That is already a usable task manager. Stop here if a short checklist solves the problem. Adding a database is useful when you need structure, not because a checklist is somehow less legitimate.
Add a task database when a checklist stops being enough
A database becomes helpful when you need to answer questions like “What is due next?” or “Which tasks are still in progress?” A plain checklist does not give you properties to filter and sort.
Create a new page for the database. Under the page's starting options, choose a database or table database, then create an empty database. Alternatively, type /database inside an existing page. Name the database Tasks.
Choose a database, not the simple Table block. A simple table holds rows and columns, but it does not provide database views, filters, or task pages. Notion's database creation guide explains the current creation options.
Add the tasks from your checklist as entries in the first column. For this small exercise, entering them again is the clearest way to see how database rows work. Once you have checked the database, stop maintaining the old checklist so you do not have two competing task lists.
Open one task from its row. You will see a page where you can add notes, links, or a small checklist of steps. The database is not limited to the information visible in the table.
Keep the task properties simple: Status and Due date
The first column contains each task's title. Add two more properties using Add property or the plus control beside the existing columns:
Status, using the Status property type. Start with Not started, In progress, and Done, or the equivalent labels already in your database.
Due date, using the Date property type. Use it for the actual deadline or day you intend to finish the task.
Click a cell to change its value. Set one task to In progress, mark another Done, and give at least two unfinished tasks different due dates. These sample values make the next steps easier to understand.
You can also add Cancelled as a status option. That is useful if you want to keep a record of work you decided not to do. Add it through the Status property's editing menu if that situation matters to you. Place Cancelled in the Complete status group if you want it treated as closed work.




Do not add Priority, Project, Owner, and half a dozen other properties just because they exist. A property earns its place when you use it to make a decision. Status and Due date are enough for this first setup.
Create an active view and a completed view
Keep the original table as All tasks, with no status filter. It gives you a place to inspect the entire collection if something seems missing.
Add a new view using the plus beside the current view, or the view-name menu if the tabs are collapsed. Choose List and name it Active tasks.
Open the view's Filter settings and show only tasks with the active statuses you use, such as Not started or In progress. If you use exclusion rules instead, exclude both Done and Cancelled with AND: the task must be neither Done nor Cancelled.
Next, create another List view called Completed tasks. Filter it to show Done. If Cancelled belongs in the same review list, include it with OR, and consider renaming the view Closed tasks so its name matches its contents.


A filter hides entries from that view; it does not delete them. Change a task to Done in Active tasks and it should disappear there, while remaining visible in All tasks and appearing in Completed tasks.
Each view has its own settings. Editing a task's status changes the task itself across views, but changing a view's layout or filter does not automatically change every other view. This distinction is more important than learning every layout.
Show deadlines and put the earliest tasks first
In Active tasks, open Property visibility and show Due date. Then add a sort for Due date → Ascending. Among dated tasks, earlier dates come before later ones. Descending does the opposite.
Check the result using your two unfinished tasks. If the later deadline appears first, change the direction to Ascending. For earliest deadlines first, the setting you want is Ascending.

An undated task has no deadline to compare. Review those entries in All tasks and either assign a meaningful date or leave them undated deliberately. Do not invent deadlines just to fill every cell.
If seeing tasks on a calendar would be more useful than reading a list, the guide to creating a task calendar in Notion is a natural next step. You do not need a calendar to finish this setup.
Use the setup for a week before expanding it
A useful first system should make it easier to capture a task, find it again, and know whether it is finished. Test those actions with your real work before changing the design.
Avoid these four beginner mistakes:
Building a dream workspace immediately. Start with one problem, not every area of your life.
Decorating before the system works. Icons and covers can wait until you can use the page without thinking about its layout.
Creating too many databases. Different views of one task collection are usually a better starting point than separate databases for every task list.
Watching tutorials instead of building. Try a feature, use the result, and return to a guide when a specific question comes up.
At the end of the week, notice the friction. If you keep searching for unfinished tasks, improve the active view. If you never use a property, remove it. If the checklist was enough all along, keep the checklist.
For a guided next step after this first build, the free 5-Day Notion Mastery Challenge offers one actionable email per day to help you build your own workspace.
Conclusion
You now have a clear starting point: a page with a checklist, or a small task database with statuses, deadlines, and views. Keep the version that helps you do the work. Learn the next feature when you encounter a real need, rather than trying to master Notion before using it.
Join The Movement
Follow Notionbase on social media to stay up to date with Notion... and more!
Links
Master Notion in 5 days.
© 2026 Notionbase. Website by William Coste.
Products
