qivo

"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 owner 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 owner 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, paused tasks excepted — 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. The owner is the assignee, or the reviewer while the task waits In Review with one (§2), so a task handed to a reviewer is walked against the reviewer's week. Without an owner 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.

A parent group uses its planned end and due date for this comparison, not its saved workflow status or a separate estimate of its own. A saved Done status cannot hide a group's missed deadline while descendant work remains unfinished. Once all of that work is Done, the group has no delay verdict.

Where you see it#

  • Roadmap — bars, unscheduled-row pills, edge badges and due-date lines are painted by status. The due line additionally warns "tight — projected to finish in the due week" in yellow, and hovering it spells the verdict out.
  • 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), ending in a yellow or red block with a clock. 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 — beside the due date, a slipping task says Currently delayed and a lost deadline Delayed: a glyph in the pressure colour and plain words, with the projected finish week in the tooltip. A lost deadline also outlines the date box in red. On track shows nothing there: it is the ordinary state.
  • 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 unfinished tasks by delay status; projects that don't omit those delay colors and keep the older due-vs-planned-end due-tick heuristic. Completed roadmap bars stay green in either case. Both default to on.

Review time#

A task that moves into In Review gets a fresh remaining time: the project's review time, 2 hours unless the project sets another. It is saved as a new measurement even when the number is unchanged, so the projection and Team utilization re-anchor on the move, and the hours count against the reviewer when one is set (§2). Moving the task on keeps whatever remaining time is left; enter a new value if the work that follows needs more.

It is a project setting (Project settings → Review time, in hours from 0 to 999), and only someone with Lead access to the project can change it. A sub-project uses its project's time unless it sets its own; its box shows the time it follows while empty, and clearing the box follows the project again. A change applies to the next moves into Review; tasks already there keep their remaining time.

✦ 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 own, 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?