How hour allocation works
Every hour on a schedule lane has one of three sources. By default, the item’s estimate is spread evenly over the working days in the item’s span. When someone types hours into the item’s cells, those hours replace the spread for that person.
Reserved hours, such as a support rotation, add to the day on top of both.
The strip above each lane adds all three into one number per column. On a person’s or a team’s lane, that number is what the view compares with the lane’s capacity.
Automatic hours follow the estimate
Section titled “Automatic hours follow the estimate”- The estimate is spread over the person’s working days between the start date and the end date. A working day is a day on which the person has capacity. If no day in the span has capacity, the hours are spread over every calendar day in it.
- An item with several assignees appears in each assignee’s lane, and the hours are split evenly between them.
- When a person takes a day off, automatic hours move to that person’s other working days inside the span by themselves.
- An item with no estimate draws a ghost bar, a dashed outline that holds no hours until someone types hours into its cells.
Typing hours sets them by hand
Section titled “Typing hours sets them by hand”Each item row has one cell for every column the item’s span covers, for a viewer who may edit the item and create allocations. A number typed into a cell states how many hours that day or period holds. One cell edit does all of this:
- That person’s hours for the item become hand-set. They stop following the estimate, time off and the item’s dates by themselves.
- The edited day or period becomes a set day. The person’s other days stay open: they share what the set days leave of the person’s hours, evenly over the open days the person works inside the span. The person’s total stays the same.
- Every other assignee whose hours were still automatic gets them fixed at their current values, with all their days open. An assignee whose hours are already hand-set keeps them as they are.
- The item’s estimate is rewritten to the sum of the hours on all its lanes, when the view maps an estimate field.
- One undo reverses all of it.
A bar of 4 hours a day over four days with the third day set to 1 becomes 5, 5, 1, 5. Setting the first day to 2 next gives 2, 6.5, 1, 6.5, because the third day is already set.
Raising a day takes hours from the open days. Once the set days add up to more than the person’s total, the open days hold 0 and the total grows. They take hours back if a set day is lowered again. Dragging a cell up or down at day zoom works the same way, and the open days move while you drag.
The open days are the days the bar held hours on when it was first edited. A day it never held, such as a weekend, stays empty until you type into it. An open day the person does not work, or one past the item’s end, holds 0. If no open day is left that the person works inside the span, the open days keep what they hold and the total changes with the edit.
Bars shaped with a curve preset, by Move hours to working days when it moves hours, through the public API, or before open days existed have no open days. On those bars a cell edit changes only the day you edit.
Week and month cells
Section titled “Week and month cells”A total typed into a week or month cell keeps the pattern inside that period. Typing 0 clears that cell’s whole period.
Clearing every day is refused, because that is the job of Reset to estimate. Only columns inside the item’s span have cells, so to add hours outside the span, make the bar longer.
How a hand-set bar behaves
Section titled “How a hand-set bar behaves”A thin line along the top edge of the bar marks hours set by hand. Hand-set hours are never split between assignees.
Moving the bar moves the hours with it, each day keeping its place from the bar’s start. Resizing the bar changes only the item’s dates, and the hours keep their place counted from the bar’s start. A shorter bar can therefore leave hours past its end, where no cell shows them. Reset to estimate or a curve preset puts them back inside the span.
For a bar that has hours, the right-click menu holds curve presets such as Front-loaded and Ramp up. Reset to estimate returns the bar to the automatic spread.
Time off never deletes hand-set hours
Section titled “Time off never deletes hand-set hours”When time off lands on a day with hand-set hours, set or open, the hours stay and a warning marker appears on that segment. Move hours to working days, in the bar’s right-click menu, moves those hours onto the person’s available days between the first and last segment. Each available day takes a share in proportion to what it already carries. The reflow never runs by itself. The next cell edit on the bar also moves an open day’s hours to the other open days.
Reserved hours
Section titled “Reserved hours”A reservation holds a person’s time for work that is not a task. Examples are a support rotation, or capacity promised to a project before its tasks exist. Reservations sit in one extra row under the lane’s items, have their own dates, and are already inside the strip and the totals.
Team roll-up lanes
Section titled “Team roll-up lanes”With Group lanes set to Teams (roll-up), each lane is one team and no lane is a person. The counting follows these rules:
- A team lane holds an item once, even when the item reaches the lane through several assignees.
- The item’s hours in that lane are the sum of the shares of the assignees that reach it. The team itself reaches its lane, and so does each member.
- A subteam, and each member of it, also reaches every team above the subteam.
- A person in no team has a share in a No team lane. An item with nobody assigned stays in the Unassigned lane.
- Hours set by hand for a person still count in the totals of every team lane that person reaches.
- A person in two teams appears in both team lanes with the same share. The lanes show the share twice. The footer counts it once, and so does a section total when the view has sections.
- The hours are spread over the days the team’s own capacity can supply, which is the sum of its members’ capacity.
Reservations reach the team lanes the same way:
- A team lane holds the team’s own reservations and the reservations of each person and subteam that reaches the lane.
- A person in two teams has the reservation in both team lanes. The footer counts it once.
- With two Group by levels, a reservation shows only in the first section that has a lane for one of its teams.
- The reservations of a person in no team do not show.
- In a team lane, only the team’s own reservations can be changed. A new reservation made in a team lane belongs to the team.
Hours cannot be set on a roll-up lane, because the lane sums the shares of several people.
A roll-up example
Section titled “A roll-up example”Ana is a member of Structural. Ben is a member of Structural and Mechanical.
- Item A is estimated at 10 hours and assigned to the Structural team and to Ana. Each assignee has a share of 5 hours, and both reach the Structural lane. The lane shows 10 hours for Item A.
- Item B is estimated at 10 hours and assigned to Ben. Ben belongs to both teams, so Structural and Mechanical each show 10 hours for Item B.
- The lane totals add up to 30 hours: 20 in Structural and 10 in Mechanical. The footer shows 20 hours, because Ben’s share of Item B is counted once.
What the totals count
Section titled “What the totals count”- A strip cell counts every hour in that lane for that column: automatic, hand-set and reserved.
- The lane header shows the lane’s total for the page on screen.
- The footer row adds up, per column, everything the filter and search leave visible, reserved hours included. Under team sections a person is counted once, so section totals need not add up to the footer. Its left cell shows the page total and a count of unscheduled items.
- Items with no dates add nothing and wait in the Unscheduled subsection. An item with no estimate adds nothing until hours are typed into its cells.
Hovering a strip cell lists what makes up its number, largest first.
A worked example
Section titled “A worked example”An item estimated at 12 hours runs from Monday to Wednesday. It is assigned to Ana and Ben, who both work all three days.
The estimate spreads to 4 hours per day, so each lane shows 2 hours per day. Ana types 5 into her Monday cell. Her Tuesday and Wednesday share the 1 hour her 6 leaves, so she still has 6, Ben keeps his 6, and the estimate stays 12.
| Lane | Monday | Tuesday | Wednesday | Total |
|---|---|---|---|---|
| Ana, before | 2 | 2 | 2 | 6 |
| Ana, after | 5 | 0.5 | 0.5 | 6 |
| Ben, after | 2 | 2 | 2 | 6 |
Had Ana typed 8 instead, her Tuesday and Wednesday would drop to 0, her total would be 8, and the estimate would become 14.
Behaviours that surprise people
Section titled “Behaviours that surprise people”- Editing the estimate does not reach a hand-set bar, not even its open days. They re-share only on the next cell edit on that bar, and they share the hours the bar already held, not the new estimate. The estimate disagrees with the bars until that edit rewrites it.
- Open days do not follow new time off by themselves. The next cell edit on the bar leaves a day off at 0 and shares its hours with the other open days.
- A failed save can leave the estimate too high. The next cell edit recomputes it from the hours that exist.
- The warning marker is not drawn at month zoom, because a month column cannot point at one day.
- Cells appear only on the lane of a person or a team, and never on a team roll-up lane. Hours assigned to a team stay on the team’s lane and are never spread over its members.
- On a phone or in very narrow columns, hours are edited in the item’s detail panel instead of the cell.
- A view can be set to spread the remaining hours instead, the estimate minus tracked time, from today onward. An overdue item’s remaining hours then land on today.