By the tiswa editorial team, from the official sources listed at the end of this guide. How we write our guides
Four students agree to split a course project and one of them posts the list in the WhatsApp group. Two weeks later someone asks who was writing the introduction, and another thought a teammate was collecting the references. The split existed, but it was buried under two hundred messages. A task board fixes exactly this: one place where every pair of eyes goes.
How do you start Notion project management for a group project?
The core idea in Notion is that tasks are not separate pages but rows in a database. Notion’s introduction describes a database as a collection of items that each carry properties, and you can display it in different views such as a table or a board.3 So you build the database once and change how it looks as needed, without re-entering anything.
If you do not have an account yet, set it up before the first team meeting, and read Notion for students to see what the education plan offers and how to activate it. Then invite your teammates to the same page so that everyone works on one board.
How do you build a Notion task board step by step?
- Create a new page named after the project
Use the course or project name so it does not get mixed up with your personal semester dashboard.
- Add a database in board view
Pick Board under the “Get started with” options, or type /Board view inside the page.1
- Add an owner property
The Person property tags people from your workspace and is designed for assigning tasks.2
- Add a status property
Status sorts tasks into three groups: To-do, In Progress and Complete.2 Rename the labels to words your team understands.
- Add a date property
The Date property stores a single date or a range, which suits deadlines.2
- Write tasks as verbs
“Write the literature review” is clearer than “Literature.” Each task gets one owner, never two.
How do you move tasks around the board?
A board shows items as cards in columns, grouped by default on the Status property. Dragging a card into another column changes its status straight away, and you can reorder the columns by dragging their headings.1 That small movement is what makes the board useful in a meeting: each member drags their own cards in front of everyone and says one sentence.
| Column | Put a task here when | Who moves it |
|---|---|---|
| To do | It is written, has an owner and a date, and has not started | Whoever created it |
| In progress | Work has started and is not finished | The owner |
| In review | The owner is done and wants a second pair of eyes | The owner |
| Complete | A teammate has checked it and agreed | The reviewer |
The third column is one you add yourself by editing the status labels. It is the difference between a team that hands in consistent work and one that finds mistakes the night before submission. For teams writing a shared text, group writing project version control covers splitting sections and freezing the draft.
What weekly check-in does the board need?
A board nobody opens is worthless. Agree a fixed five-minute slot each week, in front of the board and not the chat. Each member runs through their cards: what is done, what will be done this week, and what is blocking them. If one card sits in “In progress” for more than two weeks, redistribute it before it becomes a crisis.
If your team meets on a call, keep the board open in the same window and write decisions in meeting minutes. For fitting the check-in around crowded timetables, group study helps with scheduling.
When should you add more properties and relations?
When you need them. The Select property lets you pick one tag from a list, which suits task types such as “writing,” “data” and “presentation.”2 The Relation property links items to pages in other databases, so if you keep a separate database for references or meetings, you can connect it to the tasks.2 But add neither until the team has finished its first week and everyone is updating their status.
Also check that every member has edit access, not view-only. For comparison, Drive separates a viewer who changes nothing, a commenter who suggests, and an editor who edits, deletes and moves files.4 Take a lesson from that: give each member the least access that covers their job. And keep tasks apart from files: the board says who is doing what, the team folder holds the documents, and its permissions are explained in Drive permissions for a capstone.
How long does setup take and what ruins it?
One hour is enough to build the board and enter the first tasks with your team. Three things ruin it: a task with no owner, a task with no date, and a member who reports progress in the chat but never in the board. Agree from the start that whatever is not on the board did not happen.
What makes a team stick to the board?
Before anyone creates a card, sit down for ten minutes and settle three things. Who owns the board and keeps it tidy? What is the real submission date on the university platform? And what counts as “complete”? The last answer prevents a recurring argument: is a task complete when I have written it, or when a teammate has reviewed it? Put the answer on the top of the page in one line.
Then work backwards from the submission date to today. If six weeks remain, give each week a headline card: gather sources, first draft, review, presentation. Split those into smaller tasks of no more than three working days each. A task that needs two weeks is hiding four tasks nobody has written down.
If the project overlaps with midterms, pull the dates forward instead of leaving them to the end. A team that discovers in the last week that two members have back-to-back exams pays the full price. The board shows this early because everyone’s dates sit in one place.
