Workload

A heatmap of committed work per assignee against their configured weekday capacity. It opens on two weeks from today, with presets for one, two, four and six weeks. Over-allocated days are marked so project managers can rebalance before someone misses a date.

• The UserCapacity model stores hours per weekday plus timezone
• Tasks with an estimate contribute to the day they are due
• Spanning tasks (startsOn to dueOn) split equally across working days only
• Completed, archived, and deleted tasks are ignored, and every other task in the window is counted

• Set a person's capacity with the pencil beside their name on the Workload screen. Without a saved capacity, Atlas uses a 40-hour week, Monday to Friday.
• Each task is placed on the UTC calendar date of its due time, and the heatmap opens on your own current day. The timezone saved with a capacity is kept for reference and does not change the arithmetic.

1. 1On the Workload screen, choose the pencil beside a person and enter their hours for each weekday.
2. 2Choose a range with the presets, and move the window with the previous and next buttons.
3. 3Select an over-allocated day to list the tasks counted on it. The list shows the first hundred and says how many there are in all. Open a task, and move its due date or assignee.

Why does a task contribute to its due-date day?

When dueOn is set but startsOn is not, we assume all the work happens on the due day. If you want multi-day work, set both startsOn and dueOn, and Atlas splits the estimate across the working days in that range.

Why does everybody appear to have the same capacity, and where do I change it?

Set each person's capacity with the pencil beside their name on the Workload screen. Without a saved capacity, Atlas assumes forty hours across Monday to Friday, which is why an unconfigured team looks uniform.

Our team is spread across timezones. Is the heatmap accurate for them?

Mostly. A task counts on the UTC date of its due time, and the heatmap opens on your own current day. The timezone saved with a capacity is kept for reference and is not used in the arithmetic, so for somebody far from UTC a task due very early or very late in their day can count on the neighbouring day.