Projects vs tasks
How projects, tasks, subtasks, and checklist items relate — and which level to use when.
Reviewed OperatorVertiqa 1.54+
Vertiqa's project management module has four levels of work, from biggest to smallest:
- A project is a body of work with its own start, end, and status.
- A task is one piece of work, usually inside a project. A task can stand on its own too, for example one created by accepting an intake request, until you put it in a project.
- A subtask is a child task with its own status, priority, owner and due date. A task's page lists its subtasks when it has any.
- A checklist item is a tick-box step inside a task. Lightweight, no metadata of its own.
Which level should I use?
- New body of work with multiple discrete steps and a delivery date? → project (often from a template).
- One unit of work with a clear "done"? → task.
- A step inside a task that has its own owner or due date? → a separate task (or a subtask, if your workspace creates them).
- A step inside a task that's just "did I do this?" → checklist item.
Why the distinction matters
- Reporting rolls up at the project level. Tasks contribute to a project's progress; checklist items don't.
- Assignment happens at the task and subtask level. Checklist items aren't assigned.
- Templates are project-shaped and create a project with its tasks. They don't create subtasks or checklist items.
- Tasks views show tasks across every project, not checklist items. Make a step its own task when you want it on someone's My Tasks list.
Organizing layers on top
Two optional layers group tasks without changing the hierarchy above:
- Cycles are time-boxed iterations (sprints). A cycle's tasks drive its burndown.
- Modules are a project's sections viewed as goal-grouped chunks with their own lead and dates.
Both are organizing views over the same tasks — they don't add a new level of work.