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 inside a project. Every task lives under exactly one project.
- A subtask is a child task — its own status, priority, owner, and due date. Use subtasks when a step is big enough to track separately.
- 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? → subtask.
- 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 projects + tasks. They don't create subtasks or checklist items.
- Tasks views show tasks across every project, not subtasks or checklist items. Promote work to a task or subtask when you want it on someone's "mine" list.