What is task management and how does it differ from projects? RACI roles, priorities, statuses, kanban, Gantt and calendar views, subtasks and watch lists.
Much of a team's daily work disappears into email threads, meeting notes and people's memories. "Who has this?", "When is it due?", "Who signs it off?" get asked again every week. Task management is the discipline of moving those answers into one place that everyone sees the same way.
This guide covers the core concepts of task management as of 2026: the difference between tasks and projects, role assignment, priorities and statuses, what each view is good for, and how to build a sensible subtask hierarchy.
Tasks vs. projects
A task is a unit of work with an owner, start and due dates and a status, which can be completed on its own: "Send the supplier contract to legal." A project is a set of tasks serving a shared goal, with its own budget, purpose, members, risks and success criteria.
A simple test helps: if one person can finish it in a few days, it is a task. If it involves several people, several deliverables and several weeks, open a project and link tasks under it. For short, repeating work cycles, sprints are the better fit.
RACI: who does what on a task?
The feeling that "nobody owns this" usually comes from undefined roles. The RACI model removes that ambiguity. In HibritİK, each task can have these roles assigned separately:
- Assignee: the person doing the work. With several assignees, each one's allocation percentage can be set.
- Manager: accountable for the outcome and approves the task when it is completed.
- Tester: checks the output and records a Passed or Failed result.
- Consulted: the expert whose input is needed.
- Informed: the stakeholder who should be kept up to date.
Defining roles up front ends the debate about who signs off when the work is done. For details of the approval and test flow, see our task approval guide.
Priorities and statuses: a shared language
Priority levels
Keep priorities simple. HibritİK uses four levels: Low, Normal, High, Urgent. In a team where everything is marked urgent, priority stops meaning anything, so reserve "Urgent" for work that genuinely needs attention the same day.
Statuses
The task lifecycle is tracked with five statuses: New, In Progress, On Hold, Testing, Completed. Tasks with a manager also carry a separate approval state, so work that is "done but not yet approved" stays visible.
Five views, five questions
The same task data answers different questions in different views:
| View | Question it answers |
|---|---|
| List | What is on today, and which tasks match my filter? |
| Tree | Which parent does this belong to, and how is it broken down? |
| Kanban | At which stage is work piling up? |
| Gantt | Are the timeline and dependencies consistent? |
| Calendar | What is due this week and this month? |
The kanban board shines for daily follow-up, the Gantt chart for longer-term planning. The tabs in the list view (Active, Pending my approval, Pending my test, Overdue, Recent activity, My watch list, All) let each person pull up their own agenda in seconds.
Subtask hierarchy and automatic roll-up
Breaking big work into pieces makes both estimating and tracking easier. In HibritİK, tasks can be split into subtasks up to five levels deep. The parent's status, completion percentage, workload and approval state roll up automatically from its children, so managers never have to update each level by hand.
The catch is not to go deeper than you need. Two or three levels are enough for most teams; keep five levels for large, multi-team efforts.
Watch list: work you follow but don't own
Managers and team leads often want to know how work they are not directly responsible for is going. The watch list is the lightest way to add a task to your own agenda: you get notified when it changes, without altering the role assignments.
Activities: the task's memory
A title and a due date don't tell the story of the work. What was tried, why a decision was made and where things got stuck live in the activity log. In HibritİK, each activity is a rich-text comment; the same entry can update the completion percentage, change the status and record the effort spent in minutes. You can also drag and drop attachments, group work with tags and keep private notes that only you can see.
Logging activities consistently pays off twice: whoever takes over a task doesn't have to start by asking questions, and managers see progress without calling a status meeting. And because the task history keeps events in order, "when did this date change?" always has an answer.
Checklist for adopting task management
- Agree on the task vs. project distinction as a team.
- Require at least an assignee and a manager on every task.
- Write down what each priority level means.
- Decide which work needs approval and which needs testing.
- Run team meetings from the kanban or Gantt view.
- Review the "Overdue" tab every week.
Common mistakes
- Cramming everything into one task: work that spans weeks shows no progress unless it is split into subtasks.
- Tasks without roles: work with no manager is accountable to nobody when it is done.
- Stale statuses: views are only useful when data is current, so make logging activities a habit.
Get started with HibritİK
HibritİK's task and project management module brings the roles, statuses and views described here together on web, iOS and Android. Start your 14-day free trial with your team, or compare plans on the pricing page.