Skip to main content
Back to path

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 29

Task Database Fundamentals

Recommended resources

Welcome back! In our last lesson, we built the high-level foundation of our project management system by designing the 'Projects' database. You now have a clean, gallery-style view of your major initiatives.

Today, we're diving into the engine of our system. We will design the 'Tasks' database, which will hold all the individual, actionable steps needed to bring your projects to life. Mastering this is crucial, as a well-designed tasks database is the core of most productivity templates you might want to create and sell.

This lesson focuses specifically on adding and configuring the three most essential properties for any task manager: Status, Priority, and Due Date.

1. Creating the 'Tasks' Database

Just as we did with 'Projects', we'll create our 'Tasks' database directly on the Project & Task Manager page you set up previously. This co-location is a key principle of good template design, as it keeps related systems together for easy access. We'll use an inline table, which is the most common and flexible format for a master task list.

Notion Databases: The Ultimate Beginner's Guide

To start, let's quickly review how to create an inline database. This guide from Thomas Frank provides a clear, simple explanation.

Read the section titled 'How to Create a Notion Database'. Focus on the first few paragraphs explaining how to use the /database command and select 'Database – Inline'.

2. Designing the Core Task Properties

A task is more than just a name; it has metadata that tells you its state, importance, and deadline. Choosing the right property types for this metadata is what transforms a simple list into a dynamic system.

Notion To-Do Task Database Example
This is an example of what a well-structured 'Tasks' database looks like. Our goal is to build the core properties shown here: Status, Priority, and Due Date.

Let's watch a detailed walkthrough of how to build out these properties. The following video is packed with valuable techniques that are standard in professional Notion builds.

The Notion task manager you'll actually use (full build)

This video from Thomas Frank Explains demonstrates not just how to add the properties we need, but also how to use specific Notion features to make them more powerful. It's a masterclass in effective task database design.

Watch from 05:48 to 10:11. Pay close attention to these key steps: Turning it into a 'Tasks' database (05:48 - 07:20): This neat trick automatically adds the essential Status and Due Date properties for you. Customizing the Status Property (07:28 - 08:30): Learn how to change the names and colors of the status options to fit your workflow. Creating a 'Priority' Property (08:30 - 10:11): This is a fantastic pro-tip. The video shows how to use the Status property type—not the more obvious Select type—to create your priority tags. The key benefit is that it allows you to set a default value, ensuring every new task automatically gets a 'Medium' priority.

Let's break down the "why" behind those choices.

Status

You could use a Select property, but the dedicated Status property is superior for two reasons:

  • Built-in Categories: It has predefined groups for To-do, In progress, and Complete. This structure is essential for features like Kanban boards and progress tracking, which we'll explore later.
  • Default Option: You can set a default status (e.g., "To-do") for every new task created, which saves time and ensures consistency.

Priority

As shown in the video, using the Status property type for 'Priority' is a clever workaround. While a simple Select property with "High," "Medium," and "Low" options works, using the Status type allows you to set "Medium" as a default. This is a small detail that makes a template feel more professional and user-friendly, as it reduces manual data entry.

Adding New Properties to a Notion Task Database
When designing your database, you'll use this menu to select the most appropriate property type for the data you want to track, such as choosing `Status` for both progress and priority.
Test your understanding!

You've created a 'Priority' property using the Status type. A team member suggests it's confusing and that it should be a Select property instead. What's the main functional advantage you would lose by switching from a Status property to a Select property for your priority tags?

Show answer

The main functional advantage you would lose is the ability to set a default value. With a Status property, you can ensure every new task is automatically assigned a 'Medium' priority. A Select property does not have this capability, meaning the priority field would be empty for every new task until manually filled in.

✍️ Exercise: Build Your 'Tasks' Database

It's time to build the second pillar of our system. Follow these steps on your Project & Task Manager page.

Your Tasks:

  • 1. Create the 'Tasks' Database:

    • Below your 'Projects' gallery, type /table and select Table view.
    • In the menu that appears, click the + New database button.
    • Name your new database Tasks.

  • 2. Add and Configure Properties:

    • Delete the default Tags property that Notion adds.
    • Status Property:
      • Click the + to add a new property.
      • Name it "Status" and select the Status property type.
      • Customize the options to your liking (e.g., rename "Not started" to "To Do," "In progress" to "Doing").
    • Due Date Property:
      • Add a new property named "Due Date" and select the Date property type.
    • Priority Property (using the Status trick):
      • Add a new property named "Priority" and select the Status property type.
      • Click on the property, select Edit property.
      • Delete the "In progress" and "Complete" groups so you only have one group.
      • Add three options within the remaining group: High, Medium, and Low.
      • Assign colors you like (e.g., Red for High, Green for Medium, Blue for Low).
      • Click the ... next to Medium and select Set as default.

  • 3. Add Sample Tasks:

    • Create 3-4 sample tasks to see your new properties in action. Examples:
      • Draft proposal for Template X
      • Design cover image for portfolio
      • Schedule content for next week
    • Fill in the Status, Due Date, and Priority for each task. Notice how new tasks automatically get a Medium priority.

You now have a functional 'Tasks' database that is structured for efficiency and ready to be integrated with your projects.

Conclusion

Great job! You have now designed and built the operational core of our project management system. By creating a 'Tasks' database and thoughtfully configuring its properties, you've laid the groundwork for a powerful and organized workflow.

Key Takeaways:

  • An inline table is the standard for a master 'Tasks' database.
  • The Status property type is purpose-built for tracking progress and is superior to a Select property for this use case.
  • Using the Status property type for 'Priority' is a pro-level technique that enables default values, improving user experience.
  • The three essential properties for any task are Status, Priority, and Due Date.

Preview of the Next Lesson:
Our system currently has two powerful but separate databases: 'Projects' and 'Tasks'. The real magic of Notion begins when you connect them. In the next lesson, you will learn how to create relations between databases to link your tasks directly to their parent projects. This will allow you to see all tasks for a specific project, calculate project completion, and build truly integrated dashboards.