"Will it be ready in time?" — the delay status

This is Qivo's headline answer to the question every status meeting circles around. For every task that isn't done, Qivo projects the week the work will actually finish and marks the task with the verdict — color only where the plan is under pressure:

On track — the projected finish lands within the plan and before the due date. Carries no color: on track is the ordinary state, and the ordinary state is drawn as nothing.
🟡 Currently delayed — projected to finish after the planned end: the plan is slipping, but the due date is still reachable.
🔴 Delayed — projected to finish after the due date — or the due date has already passed. The deadline is lost unless something changes.
No verdict — done, or nothing to project from: a task needs a plan, or an assignee with remaining hours, to earn one (a due-date-only task earns none until the date actually passes). Unmarked, exactly like On track — the difference is in the task window's chip, not on the board or the roadmap.

How the projection works#

A remaining time is a measurement: every save of the Remaining field is stamped with when it was made, and the projection reads the two together. If the task has an assignee and remaining hours, Qivo walks that person's free capacity forward from the moment the estimate was saved — or from the planned start, whichever is later, since no work happens before the task begins: their own plannable hours per week (§10) minus everything else they're committed to — across the entire organization, hidden projects included (anonymously, see §12). Between the estimate and today, work is assumed to have progressed as planned — so a status doesn't slowly turn red just because the estimate aged; it degrades only when the numbers genuinely stop fitting. Saving a new remaining value re-anchors the projection at that moment (the weekly Update Estimate walk, §6, is exactly this). The projected finish is never earlier than today — a task that's still open past its planned end shows Currently delayed rather than sitting quietly on track. A busy person's task genuinely takes more calendar weeks — and the colors say so before the deadline does. Without an assignee or remaining hours, the planned end itself (pushed to today once it has passed) is the estimate. An agent has no weekly capacity to walk (§10), so there is nothing for its hours to spread over: its work is never projected to take more calendar weeks than the plan gives it, and what can still turn it yellow or red is the plan and the due date themselves, never a full week. A remaining of 0 is an answer, not a blank: the task projects as finishing now, so work with nothing left is never colored against a plan it has outrun.

Where you see it#

Roadmap — bars, unscheduled-row pills, out-of-view edge pills and due-date triangles are painted by status. The due triangle additionally warns "tight — projected to finish in the due week" in yellow.
Board — a card that is off plan wears a banner across its top edge: Slipping (running past the planned end) or Delayed (the due date projected to be missed, or already passed), with how far — "over plan", "projected", or "12d late". An on-track card carries no mark at all. The due-date chip carries the same warning in its tooltip ("Due <date> — projected to be missed") already when the projection says the deadline will be missed, not only after; where a banner is drawn above it the chip stays plain, so one fact is marked once.
Task window — a chip next to the due date: "On track", "Currently delayed" or "Delayed", with the projected finish week in its tooltip.
Overview — the "Overdue & at risk" list includes tasks projected to miss their due date (marked "projected to miss") alongside the already overdue, and the health table counts the two verdicts in its Delayed and Slipping columns — one row per sub-project, or per project.

Turning it on and off#

Delay tracking is a per-project setting (Project settings → "Delay tracking"). Projects that track delays color tasks by status; projects that don't stay unmarked and keep the older due-vs-planned-end due-tick heuristic. The team setting ("Delay tracking — New projects") only sets the default copied onto newly created projects. Both default to on.

✦ What sets this apart — Mainstream tools tell you a date was missed; Qivo forecasts that it will be, from remaining work vs. one person's real free capacity across everything they're assigned to, org-wide, and paints that verdict on the roadmap, the board, the task window and the Overview dashboard. It replaces decorative project colors with the one thing a glance should tell you: is this on track?