The Roadmap
The Task, week and milestone header stays above the task scroll area. The vertical scrollbar starts below that header; task rows and dependency lines stay within the area beneath it. Horizontal scrolling keeps the week header, task grid and Team utilization columns aligned. Row backgrounds and separators extend across the available width to the scrollbar. The task-name column is 372px wide, with the same width used for names in Team utilization so their weekly columns line up. Every visible week has the same width, including the first and last. Narrow columns on either side separate the visible weeks from tasks that extend beyond the window.
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 labeled unplanned — 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.
Backlog tasks are hidden, even if they have planned dates. Done tasks appear only when their planned period overlaps the current visible window: ending in its first week or starting in its last week counts as overlap. An unplanned Done task is hidden. To Do, In Progress and In Review tasks remain available outside the window through the edge badges described below, or as unplanned rows when they have no dates. Filters can narrow these tasks further, but cannot bring hidden Backlog or out-of-window Done tasks back. The same rules apply to the phone's landscape timeline and Task schedule; the latter uses the same current roadmap window.
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. 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 are compact buttons centered in the narrow columns before the first week and after the last, with space around them to keep the week boundaries clear. 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.
The narrow columns also explain where a task's planned period goes beyond the window:
- A colored badge joined to a bar shows only its direction arrow. It marks planned work continuing before or after the visible window; a task spanning both ends has a badge at each end.
- A detached badge also shows only its direction arrow for a planned period entirely before or after the window. It is filled when the task ends in the week immediately before the first visible week, or starts in the week immediately after the last visible week. It is outlined when at least one complete week separates the task from the window. Hover or keyboard-focus any badge for its endpoint week, then click it to bring that endpoint into view.
For tasks shown on the roadmap, an edge badge describes the planned period: “ended before” does not mean the task is Done. Hover or keyboard-focus a badge for its endpoint week: Started W37 or Ends W45 on a connected badge, Ended W37 or Starts W45 on a detached one. Click it to bring that endpoint into view, keeping the same number of visible weeks; the task's name still opens its details. Connected and adjacent filled badges match their bar: green for completed work, blue for other ordinary work, and yellow or red when the project's delay tracking calls for it (§7). More distant outlined badges remain neutral unless delay tracking calls for yellow or red. When a bar is outlined (its owner picked in Team, the task being planned on the roadmap, or a dependency conflict), the outline wraps the bar and any connected badge as one shape, and stays whole for a bar in the first or last visible week.
✦ 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 on a bar or the task's name in the left column opens the task. Task, project and sub-project names use the same subtle hover background as names in Team utilization, without underlining. Project and sub-project expand/collapse arrows remain separate controls. The highlight includes the cell's left indentation while keeping the text aligned. Click the assignee portrait beside that name to change or clear the assignment when you have edit access; an unassigned task shows the same picker through its placeholder portrait. A task waiting In Review with a reviewer shows the reviewer's portrait there, and its picker changes the reviewer. Task and parent bars are filled across their entire planned span; the filled length does not show a completion percentage. Done bars are green, including a parent whose descendant work is all Done. Other ordinary bars are blue. Where delay tracking is enabled, unfinished work turns yellow when slipping past the planned end and red for a missed or projected-to-miss due date. Completed bars stay green with delay tracking on or off, on both desktop and the phone's landscape timeline. A paused task's bar keeps its color and outline but is filled with diagonal lines, so a paused task that is slipping still reads yellow; its connected and adjacent edge badges are hatched the same way, and its hover help adds paused. 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 open the Milestones window on it (§4), or the toolbar's Milestone button to open the window on a new one. Their header names wrap to at most two lines within the week's width and truncate when longer. Hover to read the full name.
Undo this Roadmap visit's changes#
Undo reverses your latest planning change. Press it again to work back through the changes you have made since entering Roadmap. Changes save as you make them; undo saves the restored values too. One Auto-move action is one undo step, including the tasks it moves together.
The history covers task dates, parent dates widened by rescheduling a subtask, milestone additions, edits and deletions, and remaining-hour edits made in Estimates. Restoring an estimate also restores its original measurement time. Filters, the visible date window and other display preferences stay as you set them.
You can switch projects within Roadmap, change filters or pan the timeline without losing the history. On a phone, Undo sits below Timeline & team, and switching between the agenda and the timeline keeps the history.
Opening a task just to read it keeps undo available. Saving a change in the task window or changing an assignee through a roadmap portrait clears the history and stops recording for the rest of that Roadmap visit. Leave Roadmap and return to start a fresh history. Leaving Roadmap or reloading also clears it; saved changes remain in place. History expires after 24 hours and supports up to 1,000 steps per visit.
Undo checks that the affected data still matches your changes. If another change conflicts with the restoration, the operation is refused without partly reverting the plan, and the history clears until your next visit.
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. Arrows cross project and sub-project headings farther down the timeline. Once a heading pins at the top, its solid background covers only the line segments beneath it; the rest of each line stays visible, including when one connected task scrolls out of view. Scrolling back reveals those segments again. Arrows never run across task names in the left rail. The Auto-move 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.
Estimates — 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 Estimates button for the weekly ritual: the Update Estimate window 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 owner, including ones whose Remaining is still unset ("—") — those are the most worth filling in. A task is listed under its owner: the assignee, or the reviewer while it waits In Review with one (§2). Tasks with subtasks aren't listed (their Σ rollup updates by itself as the subtasks are updated, §9), and tasks with nobody to own them 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 review 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.
For the team's regular meeting, Team sync (§8) walks the same way with more on each row: status and owner changes, the delay verdict and other marks, what each person finished since their last sync, and a team opening. The Estimates walk stays the lean weekly version.
✦ 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.