The Roadmap

A week-grid timeline: one track per sub-project — or, in All projects and My view, one per project, banded inside into its sub-projects — scheduled tasks as draggable bars, undated tasks as rows of their own after the scheduled ones (the title in the left rail like any other task, a dashed pill with the task key — and its due date, when one is set — in the timeline; click it to open and schedule), and the team strip docked underneath (§8). Every header — track or sub-project band — shows how much work is left inside: the summed remaining hours of its not-done tasks ("120h"), so a collapsed one still tells you what it would cost to finish. Both also stay on screen while their own rows scroll — the track pinned under the week header, a sub-project band a step below it — so a long track never leaves you reading nameless bars; the next track (or band) pushes the previous one out. Both collapse the same way, so in All projects you can fold a whole project or just one discipline inside it — and the double chevron in the rail's Task column head does the whole rail at once: fold everything down to the project rows for a one-screen overview, then unfold it all again. It folds what you can't see too, so opening a single project back up shows its sub-projects still folded, ready to open one at a time.

The filters (§3) reach the rail itself: a project or sub-project with no matching task drops off the timeline entirely, so a search leaves you with the tracks that answered it instead of a screen of empty headings to scroll past. Focus is the exception — because it stays on until you turn it off, it only thins the rows, never the rail. Clearing the filter brings everything back, folded exactly as you left it.

A window you control#

The visible range starts at −2…+6 weeks around today — though that is yours to change, see Your own default below — and every control for it is on the timeline rather than in the toolbar above it.

Where you are looking: the ◀ and ▶ arrows standing at the two ends of the week ruler, one in the margin before the first column and one after the last, so neither ever covers a week. Each press moves the view by 20% of what it shows. They stay put when a wide window scrolls sideways.

How much you are looking at: the calendar glyph in the top-right corner of the TASK column heading. It opens a short menu — a month, two months, a quarter, half a year, a year — and the span you are on is marked. The same menu holds Default window, Save this as my default and Custom range… — the last opens both ends at once and is where a range stops being a number of weeks: each end is separately either Relative weeks ("−2 weeks from today" — slides forward as time passes) or an Exact date (pinned).

Getting back: a ⟲ appears beside the calendar glyph as soon as the view is off its default, and goes away again when you press it. While it is missing, there is nothing to undo.

Your own default: −2w … +6w is where everyone starts, not what everyone has to keep. Set the view to the range you actually work in and press Save this as my default in the same menu — from then on that is what ⟲ and Default window come back to, and what the Roadmap opens on. The Default window row always names the range it would go to, so you can see what yours is without leaving the menu. It is yours alone: your colleagues go on seeing their own.

Once you are standing on a default you chose, that row becomes Forget my default and hands you back the standard −2w … +6w — so the row is never a dead one, and the choice is never a one-way door.

A task scheduled entirely outside the window doesn't vanish: a dashed edge pill with a chevron and its start date marks it at the row's edge — click to open. The pill takes the delay color — yellow or red (§7) — where the project tracks delays and the plan is off, and a neutral gray otherwise, so on a delay-tracking project, a red arrow at the edge means trouble even when the bar itself is out of sight.

✦ What sets this apart — Each end of the window is separately either calendar-following or pinned — "from two weeks ago until the release date" is a first-class view.

Weeks that match your calendar#

The header shows calendar week numbers ("W29") over each week's first-workday date; the week that opens a month brightens its date and carries a solid gridline where the other weeks carry dashed ones, and narrow columns drop the date, then the "W". Which day starts a week and what "week 1" means follow your organization's settings (§10) — so a Sunday-start retail org and an ISO-8601 engineering org both see their week numbers.

Qivo deliberately plans in whole weeks, not days: bars snap to weeks, due dates stay day-precise as markers. At roadmap horizons, day-level bar precision is fiction — weeks keep the plan honest.

Scheduling by hand#

Drag a bar to move it, drag either edge to resize; release to commit — where you can write; a read-only role's bars don't move or resize, they only open. A simple click opens the task. Bars show status progress fill. A parent's bar can never be dragged inside the span of its scheduled children — parents always cover their subtasks (the "date envelope", enforced everywhere, even against API writes). Milestones are draggable violet diamonds with a dashed line down the timeline; click one to edit, or the toolbar's Milestone button to add one.

Dependencies you can see — and safely fix#

"Blocks" links draw as finish-to-start arrows: green when satisfied, red when in conflict (the blocker ends on or after the blocked task's start) — updating live while you drag. An arrow between two different tracks draws over the heading rows it crosses, pinned ones included, so it stays one unbroken curve from the dot on its blocker to the head on the blocked task. It still never runs across the task names in the left rail. The Auto-correct button (with a live count badge) pushes every blocked task to start after its blocker, cascading through chains, moving parent/child families as one unit — and deliberately leaves mathematically unsolvable tangles (cycles) alone, red arrows on, for you to untangle by hand.

✦ What sets this apart — One-click cascade rescheduling that knows which conflicts are unsolvable and refuses to "fix" them into far-future nonsense. Most tools warn about dependencies; few dare to move them safely.

Update Estimate — refresh the numbers before you plan#

The load boxes, the delay projection and the auto-fit are only as good as the remaining hours behind them. So the roadmap toolbar has an Update Estimate button for the weekly ritual: a window that walks the team's open work one person at a time, for the sole purpose of updating each task's Remaining — refresh the numbers first, then plan the week on trustworthy data. It covers every project you can see (wider than the roadmap's own project scope you're looking at): every To Do, In Progress or In Review task that has an assignee, including ones whose Remaining is still unset ("—") — those are the most worth filling in. Tasks with subtasks aren't listed (their Σ rollup updates by itself as the subtasks are updated, §9), and unassigned tasks stay out of the walk entirely.

Each person's list reads in "this week first" order — scheduled tasks by planned start week, then unscheduled by due date — and every row carries the context for judging the number: project, status, plan weeks or due date, and the Remaining input itself (rows deliberately don't open the task — this window has one job). Edits commit immediately on blur/Enter, exactly like the task window's field, and closing flushes whatever is still in the focused box — so no way out of the walk loses a number you typed. The load boxes and the track-header sums follow instantly; the delay projection catches up a moment later, once the refreshed workload lands. Each saved number also re-anchors that task's projection at this moment (§7) — which is the walk's real payoff: fresh estimates make the colors sharp. An edited task also stops counting as stale. A subtle ✓ marks each row you've edited — or confirmed unchanged with its "ok as is" tick — so you can see you've looked at every line; the footer counts "N of M tasks reviewed" and a person whose rows are all ✓ gets a check on their avatar in the rail. Previous / Next (or clicking an avatar in the rail) moves between people; the last step's button becomes Done. The checkmarks live only while the window is open — nothing is stored on the tasks, and reopening the walk starts a fresh pass.

✦ What sets this apart — Estimates rot because updating them means opening thirty tasks one by one. A purpose-built walk — per person, open work only, one number per row — turns it into a five-minute Monday habit.