Loading
Because everything ends up on them. Deliverables sit beside reminders, the order reflects typing rather than sequence, and people quietly keep a private list of what actually matters.
A task is a unit of work with an owner, an estimate, a status and a position in the project plan.
Every task belongs to a phase and a project, so its estimate feeds capacity, its hours feed margin and its status feeds the plan. There is one task, shown in whichever view suits the person looking.
A task cannot start because a client decision is outstanding. It is marked blocked by that dependency, drops out of the assignee's queue, and appears in the client portal as waiting on them.
They will not prioritise themselves. Dependencies say what is possible; what is important is a decision, and Loop keeps the two separate on purpose.
The plan takes its dates, capacity takes its estimate, timesheets log against it, and margin counts its hours. A task escalated from Desk keeps its ticket attached.
No. It has one home, and cross-project work is linked rather than duplicated.
Not to exist, but an unestimated task cannot be counted in capacity or a sprint.
Only phases and deliverables you expose. Internal tasks stay internal.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.