Workload

A 14-day heatmap of committed work per assignee against their configured weekday capacity. Over-allocated days light up red so PMs can rebalance before someone misses.

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

• Set each user's capacity in Settings > Workload first. Without a row, Atlas uses a 40-hour Mon-Fri default.
• Timezone is carried through but the math is done in UTC. A future iteration will honor the user's timezone for day boundaries.

1. 1Go to Settings > Workload and set hoursPerWeekday for each assignee.
2. 2Open /workload to see the 14-day heatmap.
3. 3Drag tasks off an over-allocated (red) day using the board or the week view.

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 in Settings, then Workload. Without a row for somebody, 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?

Timezone is carried through, but the arithmetic is currently done in UTC, so a day boundary can fall in the wrong place for somebody far from it. Honouring each person's timezone is a later iteration.