Planning against real capacity

Plan on roadmap#

From any task, "Plan on roadmap" jumps to the timeline with that task spotlit (unscheduled tasks get a starter bar to drag). A PlanCard docks in the corner with:

"Auto-fit end to workload" (on by default): every drag release sets the start, and the end computes itself from the assignee's free weekly capacity — "End follows Anna's free time on drop."
The assignee's committed hours in the planned window, broken down per project — with work in projects you can't see folded into one anonymous "Other projects" bucket (hours, no names), and a "~Xh/wk free of Anna's Yh plannable" summary — the name is in it because the plannable week being divided is hers, not her team's. Plan an agent and there is no such division to write: the line reads "Atlas has no weekly capacity — work is never stretched to fit", and auto-fit leaves the end where the start is (§10).
Confirm keeps the dates; Cancel restores exactly what was there before, including "unscheduled".

The Team strip#

Always docked under the roadmap, same window and week grid. One row per person visible on the roadmap; every week they have work planned in gets a load box that writes the load out as a percentage of that person's own plannable hours (weeks with nothing planned stay empty). Plannable hours belong to the person, not to their team (§10) — a new person starts on whatever the organization's default is (32 out of the box) — and they are deliberately less than a full work week, because time lost to meetings, email and other overhead was never available for planning in the first place.

Every row is measured against its own week. The denominator is written under the person's name — "27 h/wk" — and the strip's header says the same thing once: "% of each person's plannable week". So 100% means exactly the same thing on every row — this person's week is full — even though it stands for a different number of hours on each. A part-timer and a manager whose week is mostly meetings are no longer planned as if they had the same week, and no box has to be footnoted as measured against somebody else's scale.

Every box writes its percentage, and colour marks only the weeks worth looking at: an ordinary week under 90% carries no fill at all, yellow at 90–100% (nearly booked), red over 100% (overbooked — more work than that person's plannable time holds, with a warning ring). Nothing beside the person's name repeats those figures: the week you would have read there is already on screen, in its own box.

An agent's row is measured differently, because there is nothing to measure it against. An agent has no plannable week at all (§10), so its row has no denominator: where a person's name carries "27 h/wk", an agent's says "no weekly limit", and each box writes the hours it is committed to that week instead of a percentage — never a warning colour, whatever the number. "0%" would have been true and useless: an agent isn't idle, it simply can't be over capacity. Toggle All work / This project only (absent in All projects and My view — there, all work already is the scope); ▲/▼ steps the strip between header-only, normal, and full-screen. Click a person to ring their bars on the roadmap and fade everyone else.

The strip's numbers are derived from the tasks themselves — each task's remaining hours spread evenly from the week its estimate was last saved (or from the planned start, if that's later) through its planned end: hours measured mid-task land on the weeks still ahead of that measurement, not on weeks the estimate already accounted for, and hours re-measured after the planned end has passed land in the save week itself rather than vanishing. There is no separate allocation grid to maintain, and the strip animates live while you drag a bar above it.

✦ What sets this apart — Capacity is a pure derivative of the plan: drag a task and watch the person's week-by-week load recolor in real time. Where other tools sell resource management as a separately-maintained add-on, Qivo has one source of truth — the tasks — so the workload view can't disagree with the plan. And the auto-fit planner respects privacy: you see that a person is busy without learning what they're busy on.