Asana Workload Tracking for Capacity Planning
How Asana Workload Tracking Works
The Workload view aggregates every task assigned to a person across all projects in a team, with bars showing planned effort vs capacity. Overload bars turn red; capacity is configurable per person.
The view exists at the team and portfolio level. There is no workspace-wide Workload view by default — each team or portfolio sees its own slice.
- Per team — Workload tab inside the team page; lists members and bar chart per person
- Per portfolio — same view scoped to projects in the portfolio
- Capacity unit — tasks, hours, or any numeric custom field; pick one and stay consistent
- Date range — typically next 2–4 weeks; configurable
- Plan limits — Advanced, Enterprise, Enterprise+; not on Personal or Starter
If capacity isn\'t set per person, the view becomes a bar chart of task counts. That has some value, but the overload warning is the whole point.
Workload (Advanced+) shows per-person load with capacity overlay. Set capacity values — otherwise the warning doesn't fire.
Capacity Inputs and Workload Units
Capacity in Workload is measured in whatever unit the team agrees on: tasks per week, hours per week, story points per sprint. Pick the unit that matches how the team plans work.
The unit choice matters because mixing units breaks the rollup. A team using story points for software and hours for design will see two separate workload charts, not one.
- Tasks per period — simplest; assumes tasks are roughly equal size (often false)
- Hours per week — most common for time-tracking teams; pair with the time tracking field
- Story points per sprint — for agile teams; estimates calibrated through velocity
- Custom effort field — number; relative (S/M/L/XL mapped to 1/3/5/8) often works well
- Non-working days — schedule settings reduce capacity for vacation, holidays, part-time schedules
Set capacity for the same number of hours every person logs as real work — usually 30 to 35 productive hours per week, not 40. Padding the number creates a false sense of available capacity.
Pick one unit per team. Set realistic capacity (30–35h/week), not theoretical (40h/week).
Balancing Overloaded Teams
When Workload flags an overloaded teammate, three actions help: reassign work, reschedule deadlines, or descope. The right action depends on the cause of the overload.
Overload is rarely random. It usually traces to one of three causes — and the fix differs for each.
- Single overloaded teammate — reassign work; check why the team default keeps landing there
- Whole team overloaded — descope or push deadlines; hiring is the slow fix, not the immediate one
- Bottleneck on a specific stage — restructure the workflow; sometimes a single reviewer holds everything
- Spotting bottlenecks early — set capacity warnings 2–4 weeks ahead, not just for the current week
- Escalation — when capacity risk crosses 100%+ for two consecutive periods, escalate to project sponsor
If the team is overloaded every week without exception, the issue is intake, not capacity. Tighten request triage rather than asking the team to work harder.
Reassign for personal overload, descope for team-wide overload. Persistent overload = intake problem.
Dashboards and Resource Reporting
A workload dashboard pairs the Workload view with a few cards: utilisation by person, total committed hours, capacity vs allocation. Time tracking (Advanced) adds actual-hours data alongside planned hours.
Resource reporting is most useful when planned and actual data sit side by side. Planned hours show the commitment; actual hours show whether estimates were honest.
- Workload charts — bar per person, capacity overlay; the primary card
- Time tracking as capacity signal — actual hours logged per person, compared with planned
- Portfolio view — Workload across multiple projects in one chart
- Utilisation metric — actual hours ÷ available hours; useful for agencies and consultancies
- Avoid — using utilisation as a performance metric without context; it punishes deep work and rewards meeting-heavy weeks
For utilisation reporting at agency scale, a dedicated PSA tool (Mosaic, Resource Guru, Float) usually beats stitching Asana plus Harvest plus a BI tool.
Planned + actual hours side by side. Don't use utilisation as a performance metric.
Workload Tracking Limits
Subtasks behave inconsistently in Workload, private tasks don't aggregate, and manual capacity data degrades over time. Plan for these limits or accept they will distort the view.
Three known limits cause most frustration. Each has a workaround; ignoring them lets the dashboard drift away from reality.
- Subtask behaviour — subtasks may or may not roll up to the parent, depending on settings; verify before relying on the count
- Private tasks — invisible to managers and missing from team workload; document this gap to non-admins
- Data quality issues — wrong owners, missing due dates, stale estimates all distort the view; weekly hygiene matters
- Dedicated resource tools — Float, Resource Guru, Mosaic for deeper utilisation, capacity scheduling, and skill matching
- Cost — adding a PSA tool roughly doubles the per-seat cost; justify with concrete agency-scale needs
If the team has a dedicated resource manager who spends more than half their week on capacity planning, a PSA tool will pay back faster than fighting Asana.
Subtask and private-task gaps distort the view. Heavy resource management → PSA tool.
Frequently asked questions
What plan do I need for Asana Workload?
Advanced, Enterprise, or Enterprise+. Workload is not included on Personal or Starter. The Advanced plan also unlocks Goals and Portfolios, which pair naturally with Workload for resource and outcome tracking.
Can I measure workload in hours instead of tasks?
Yes. Add a numeric custom field (typically "Effort hours") and configure Workload to use it as the unit. Hours often give more honest signals than task counts because tasks vary widely in size; story points work similarly for agile teams.
Do subtasks count in Workload?
Sometimes, depending on the workspace setting. Check the subtask rollup option in workspace settings before assuming Workload counts them. The default behaviour has changed over Asana's history, so verify rather than assume.
Can Workload show capacity across multiple projects?
Yes. The team-level Workload view aggregates assignments across every project in the team. Portfolio-level Workload scopes to the projects in a portfolio. Workspace-wide Workload across all teams isn't a single view by default.
How does Asana Workload compare to dedicated resource tools?
Asana covers planning, capacity, and overload warnings — enough for most operations teams. Dedicated resource tools (Float, Resource Guru, Mosaic) add skill matching, utilisation forecasting, time-off integration, and more refined scheduling. Agencies and consultancies usually outgrow Asana on this dimension first.