Studio workload you can see as counts, not a sheet

Throughput is a count, not a savings percentage

Throughput is the number of tasks closed in a week. The horizontal axis is the week. The vertical axis is the count. If there are no stage moves, you see that there is no data, not a fake zero.

There is no savings percentage here. The numbers come from moves the board already recorded.

A week with eight closed tasks is eight, whether those tasks were a colour pass or a caption fix. The product does not invent a weight. If you need to compare kinds of work, filter by label or by project, then read the same count.

Bottleneck and load, in the same units

A bottleneck is the stage with the most open tasks at that moment. The bar is a count, and the stage name sits next to the number.

Load is how many open tasks a person has. It is counted from the board. Time tracked on a task is the hours they logged, not an estimate. A label on a task helps filter the queue; a watcher joins only the items they need to follow.

The analytics bottleneck view answers a second question with different data: the stage with the longest median time, measured from the moment tasks enter it to the moment they leave. That number is minutes in stage, not a count of cards. Both are useful. They are not the same chart.

A dashboard on the same two questions

The same two questions appear on the dashboard after you sign in: how many closed, and where the open ones sit. The public page explains the units; the dashboard shows them on your work.

A project filter on that dashboard is the same filter as on the board. You are not reading a second database. A week that looks quiet on the dashboard and busy on the board means the closed count and the open count are answering different questions, and both are still counts.

When there is no work yet, you see a no-data state with a short explanation. We do not show zero as if a measurement happened.

The weekly report the owner reads on Monday uses the same rollup. It lists the three busiest members with their load, and it does not add a savings percentage there either.

Hours logged versus minutes estimated

A person's load on the workload view is estimated open minutes against weekly capacity. The default capacity is 2,400 minutes: five days of eight hours. If they belong to two teams, capacity is the sum of both. Anyone over that line is painted red.

Hours actually spent are a different number. They are typed time entries against a work item. A project total puts those hours beside the estimates, so a producer can see both 'what we thought' and 'what we logged'.

Neither number is a timesheet product. They are the two readings a studio already argues about, taken from the board instead of from a sheet that drifted.

Several productions, one queue

When twenty projects are open, a sheet per production hides the person who is on four of them. The workload view groups by the person. The bottleneck view groups by the stage key, so Client Review on project A and Client Review on project B are one line.

If two templates use the same key for stages that mean different things, they will share a line. Keep the keys honest in the templates and the view stays honest.

A saved view can keep the person grouping and the label filter together, so Monday does not start by rebuilding the same two clicks. The count you see then is the same count the owner report will print.

A label such as waiting on the client still works across those projects. Filter to it and the open count is the work you cannot start, not a colour in a column.

What to do with a number once you can see it

A stage with the most open tasks is a place to add an owner or a wait, not a reason to rename the stage. A person over capacity is a reason to stop assigning, not a reason to ask them to log more hours.

A week with no closed tasks and a board full of cards is a process question. The Monday report will say so. The dashboard will say so. Neither will invent a percentage to soften it.

When the numbers disagree with the feeling in the room, trust the board. The counts are the moves already recorded. The feeling is often last week's sheet.