How a Workload View Shows Who Has Too Much Work

A workload view answers a planning question the board hides: who already has a pile of work due, and who does not. You look at it before you assign the next task, not after someone misses a date.

The catch is the unit. Some screens count tasks. Some add up hours. Some price the work. Those are different questions. A view that counts tasks due per day can show a crowded Thursday. It cannot show that Thursday is a two-hour task for one person and an eight-hour task for another. Read the screen you have, not the word “workload” in the menu.

What you should see

Open the view for the people on the work, not for an abstract team chart.

A useful workload picture has:

• A person.
• The tasks assigned to that person.
• When those tasks are due.
• A way to see that one person has many dues on the same days and another has none.

You then decide. Move a due date, reassign, or cut scope. The view does not make that decision. It stops you from handing the next task to the person who is already the busiest on the board you forgot to scroll.

People with no tasks in the set may not appear. That is a feature if you are looking for load, and a gap if you are looking for who is free. Check whether an empty person is hidden. “Not listed” is not the same as “available” until you know the view’s rule.

Tasks due are not hours booked

What you might assume	What a task-count view actually says
Maya is at 120% capacity	Maya has more tasks due on those days than the others
The project is over budget	Nothing about money
Friday is a full day	Friday has several due dates, of unknown size
Someone with no row is free	They may simply have no task in this project, or no due date this month

If the view is “tasks due per day, this month,” a task with no due date will not land on a day. It can still be assigned. Expand the person and read the list, including rows that say there is no due date. Undated work is invisible on a day count and still has to be done.

A task due on the 3rd counts on the 3rd. It does not smear across the days before it. A two-week build that is due on the 18th looks like a single mark on the 18th, not a bar of effort. That is why this view is a due-date load, not a schedule of effort. The Gantt chart is where duration lives, if you filled in start and end.

Do not convert the count into a utilization percentage in a slide. Six tasks due is not 60% of a week. It might be six small reviews or six launches. Open the tasks before you tell someone they are overloaded.

When to look

Look before a planning meeting, not only after a miss.

A small agency is about to accept a new brochure. The board looks fine because the new work is not on it yet. The workload view for this month shows the designer with dues on six different days and the writer with one. The new brochure should not land entirely on the designer unless those six dues are tiny and you have checked. That check is the planning step. You do not need a second article or a second tool for it.

Also look when several projects share people. A board is usually one project. A person can be assigned on more than one. If the workload view is scoped to the tasks you loaded, it will not show assignments that sit outside that set. Know the scope before you declare someone free.

What not to expect

A workload view of due dates will not:

• Store skills or a role catalog (“only senior designers”).
• Book someone for a percentage of a week.
• Subtract leave, unless leave is represented as tasks in the same set. Employee leave usually lives in an HR system, not on the project board.
• Price the work or warn you about margin.
• Forecast next quarter from a capacity model.

If you need hours, use time estimates and time tracked on the tasks, and accept that you are doing a different comparison. If you need invoices, that is a finance tool. A currency field on a task is not a workload cost.

An example you can check by hand

Four people share a project in March. The view counts tasks with a due date in March.

• Priya: due counts on the 2nd, 4th, 9th, 11th, and 18th.
• Owen: one count on the 18th.
• Lena: no row, because nothing in this set is assigned to her.
• Chris: a row, and the expanded list shows two tasks with no due date plus one due on the 3rd.

Priya looks busiest. Open her five tasks before you move the new landing page to her. Two of them may be ten-minute approvals. Owen’s single due date may be the full build. Lena is not proven free. She may be loaded on another project the view did not include. Chris’s undated tasks will not show on a day until you give them a due date.

After you reassign one of Priya’s approvals to Owen, the 11th count on Priya should drop and Owen should gain that day. If the screen does not change, you are looking at a different set of tasks than the one you edited.

How to act on what you see

1. Filter your attention to the month you are assigning into.
2. Find the person with marks on the most days, and open their tasks.
3. Separate small dues (a review, an approval) from large ones (a build).
4. Reassign or move a date only after that look. Do not rebalance from the count alone.
5. Put a due date on important undated work or it will stay off the day count.
6. Check again after the new assignment. The view should change because the task changed, not because you edited a separate plan.

If everyone looks equally busy and the work is still late, the problem may be the estimate of the tasks, not the distribution. A workload view cannot fix unclear tasks.

How this works in Dayzen

In Dayzen, the workload view is titled around team workload and labeled as tasks due per day for the current month. It lists workspace members who are assigned at least one of the tasks in the view. For each person it shows a count on the days this month where their tasks are due. You can expand the row and see the task titles, including tasks with no due date.

It does not add up hours, compare estimates with a capacity number, or show cost. It will not, by itself, include leave stored on the HR side. Use it to see a crowded set of due dates before you assign more. Use task time entries if the question is hours. Use the HR attendance and leave tools if the question is whether someone is working that day.