Trello Workload Tracking for Capacity Planning
How Trello Workload Tracking Works
Workload visibility comes from cards-per-member, summed Estimate fields, and the Premium Dashboard. Native capacity-leveling is not in scope; the data is, the algorithm is not.
- Work by assignee — Dashboard widget for cards-per-member, optionally filtered by status.
- Capacity vs availability — convention; sum of Estimate field per member, divided by weekly capacity hours.
- Plan limits — Premium for Dashboard widgets; Free and Standard see board-level filters only.
The way most teams use Trello workload tracking: the team lead opens the Dashboard at the start of each week, sees who has too many cards, and rebalances before sprint-start. That cadence is enough for teams up to about 25 people.
Trello answers "is anyone overloaded" cleanly. Deeper leveling is convention-based or dedicated-tool territory.
Capacity Inputs and Workload Units
Pick one unit (hours, points, count) and standardise across the Workspace. Mixing units within a team breaks the dashboard math.
- Tasks count — simplest unit; useful when cards are similarly-sized.
- Hours — Estimate field in hours; pair with a time-tracking Power-Up for actuals vs estimates.
- Story points — used by engineering teams; abstract effort unit.
- Custom field — Estimate (number), required on every card via a Butler rule.
- Time estimates and due dates — both inputs to workload; due dates determine when the load is felt.
- Non-working days — manually noted on the board or in a calendar; Trello does not auto-block holidays.
The most common workload-tracking failure on Trello is mixing units. Half the team estimates in hours, half in story points; the dashboard becomes unreadable. Pick one and enforce it.
One unit across the Workspace. Mixing hours and points breaks the math.
Balancing Overloaded Teams
Rebalancing happens at the start of each week. Reassign or reschedule based on the Dashboard. Butler can flag when a member exceeds a threshold.
- Reassigning or rescheduling — drag-and-drop in the board view; member change is logged.
- Spotting bottlenecks — Dashboard widget for cards-per-member, sorted descending.
- Escalation workflows — Butler rule that messages the team lead when a member has more than N active cards or more than X estimated hours.
- Member workload bar (Power-Up) — Planyway, Hello Epics, or Burndown for Trello render a workload bar visualisation.
The signal that matters is not "who has the most cards" — it is "who is least likely to deliver this week". Pair card count with due-date density to get that.
Card count plus due-date density tells you who is at risk this week.
Dashboards and Resource Reporting
Premium Dashboard handles team-level workload. Portfolio or multi-team views require Workspace-level Dashboards (Premium) or a dedicated resource tool.
- Workload charts — cards-per-member, sum of Estimate by member.
- Time tracking as capacity signal — actual hours from a Power-Up + estimated hours from custom field = utilisation ratio.
- Portfolio views — Workspace Dashboard aggregates across boards.
- Multi-team reporting — limited on Trello\'s native model; evaluate Float, Resource Guru, or Runn for true resource planning.
For agencies with billable resource planning, the pairing that works is Trello + Float (or Trello + Resource Guru): Trello holds the work, Float holds the resource plan. They are not the same thing and should not be the same tool.
Trello holds the work; a resource tool holds the resource plan. They are different categories.
Workload Tracking Limits
Limits to verify: subtask and checklist behaviour, manual data quality, no auto-leveling, no native non-working-day handling.
- Subtasks and private task behaviour — checklist items do not carry estimates natively; only the parent card does.
- Manual data quality — Estimate field accuracy depends on member discipline.
- No auto-leveling — Trello does not suggest reassignment; the manager does.
- Dedicated resource tools to compare — Float (calendars and scheduling), Resource Guru (booking model), Runn (scenario planning), Mosaic (portfolio leveling).
The honest test: how often does the team\'s workload conversation involve a tool other than Trello? If "rarely", Trello is enough. If "weekly", a dedicated tool is worth evaluating.
If workload conversations happen weekly with another tool, that other tool is doing real work. Pay for it.
Frequently asked questions
Does Trello have a workload view?
Not as a native module. The Premium Dashboard counts cards-per-member; pair with an Estimate custom field and a Butler rule that flags overload. Power-Ups (Planyway, Hello Epics) add workload-bar visualisations.
What is the best Trello workload Power-Up?
Planyway is strong for timeline-plus-workload; Hello Epics handles epics-with-resource views; Burndown for Trello adds capacity charts. Trial each on one board for two weeks before standardising.
Can Trello plan resources across multiple teams?
Limited. Premium Workspace Dashboards aggregate across boards, but true multi-team resource planning needs a dedicated tool (Float, Resource Guru, Runn, Mosaic) alongside Trello.
How do I track a team's capacity in hours on Trello?
Add an Estimate custom field in hours. Sum the field per member via the Premium Dashboard. Compare against the team's weekly capacity (e.g. 30 productive hours/week). Butler can flag when a member exceeds threshold.
Should I use story points or hours on Trello?
Pick one and stick with it across the Workspace. Story points work for engineering teams comfortable with the abstraction. Hours work for agencies and ops teams that bill or plan against real time. Mixing the two breaks the math.