Set Up Workload View in Asana
Use workload to inspect assigned, scheduled work and compare capacity with an agreed effort measure. A quiet workload view may mean missing data rather than available people.
Step-by-step guide
Check access and scope
Project and portfolio workload require eligible plans. Confirm access to relevant tasks, assignees and dates before using the view for staffing decisions.
Choose workload scope
Choose project or portfolio workload according to the planning scope. A project can add a Workload tab from its header; a portfolio exposes its own Workload tab for cross-project scope.
Audit scheduling data
Inspect tasks for assignees, due dates and useful start dates.
- Worked example: A five-day migration task and a copy change should not both consume one undifferentiated unit when planning a specialist week. Use agreed hours or points with explicit scope assumptions.
Pick an effort measure
Choose task count or a consistent effort unit.
Agree owner capacity
Set capacity with team members and check time-off constraints.
Rebalance specific commitments
Rebalance a small set of tasks and confirm the revised schedule.
Verify the result
Each owner recognizes their visible commitments and overloaded periods have a documented scheduling decision.
Common mistakes
Check the handoff edge case
A task-count view treats differently sized tasks alike. Choose an effort measure appropriate to the decision rather than implying exact capacity.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.