Give each database a clear purpose
For an illustrative content team, a project is a bounded outcome such as publishing an onboarding guide. A task is a piece of work such as approving the outline or checking links. Store them in separate databases so project context does not have to be copied onto every task page.
Keep the initial properties small: project owner, project status, task assignee, task status, and any dates the team actually uses. Define what Done means for a task before building a progress dashboard. An unchecked field and an unfinished deliverable are different problems.
Connect tasks to projects with a relation
Notion relations connect items in databases, while rollups summarize properties from related items. Use a relation from tasks to projects, then add a rollup only when it answers a clear question about those linked tasks.
For the onboarding guide, link the outline, draft, design, and review tasks to one project. A task count can help check whether work is missing, but it is not automatically a measure of effort. Four completed minor tasks and one blocked legal review should not be presented as a confident launch forecast.
| Database or view | Purpose | Decision it supports |
|---|---|---|
| Projects database | Store outcomes and project context | Who owns this result? |
| Tasks database | Store actionable work linked to a project | What happens next? |
| My tasks view | Show relevant assignments from the task database | What should I work on? |
| Project review view | Show the selected project's tasks and status | What prevents completion? |
Create views of the same records
Notion supports database views with filters, sorts, and grouping. Different views can expose the same underlying records for different purposes. Its documentation also distinguishes personal view changes from saving settings for everyone, which matters when people collaborate in a shared workspace.
Create a personal task view filtered to the assignee, a board grouped by status, and a project review view filtered to the related project. Edit a sample task from each view and confirm that the same record changes everywhere. If a task exists independently in three databases, the team now has three opportunities for conflicting status.
Keep planning dates distinct from promises
Use a date property only when its meaning is explicit. The draft due date may be an internal target, while the public publication date may depend on approval. Write that distinction in the project page so a calendar view does not imply every displayed date is a commitment.
Give blocked work a reason and an owner for the next decision. A project with all tasks assigned can still lack someone who resolves an editorial disagreement. Use the project page for decisions and context, and keep the task record focused on the action that another person can understand.
Review actual sharing before inviting a guest
Notion sharing can involve inherited access and several permission levels; the broadest applicable access can determine what someone is allowed to do. Review the current sharing documentation for the workspace features you use. A filtered task view alone does not define an access policy.
For an external illustrator, write down exactly which project pages and task details they should see. Test with an appropriately restricted account, including access through parent pages and related records. Check links to internal notes before inviting the guest. Choose the supported permission arrangement that matches the requirement instead of relying on a hidden column.
Rehearse one completed project before expanding the template
Run the onboarding-guide example from project creation to completion. Check who assigns work, where a reviewer records a decision, and how the final guide is linked. Archive or close the sample project and confirm that unfinished tasks do not silently disappear from the responsible person's working view.
Notion is a candidate when connected documents and flexible work views match the team's habits. Keep the first template small enough to explain to a new collaborator. Add rollups, formulas, and more databases when a repeated operating question justifies them, with ownership for keeping those connections accurate.
Sources and editorial method
Official sources linked in this guide were checked on October 27, 2026. Features, interfaces, and commercial limits can change. The examples are proposed workflows and illustrative calculations, not customer results or a hands-on product benchmark. Confirm the current documentation before implementing the workflow.