Asana team workload board for your Monday capacity check

Build me a team workload board that I open every Monday morning to see who on my team is buried and fix it on the spot. It reads everything from Asana and sends handover notifications through Slack. Nothing runs on a schedule; I open the board when I want to review capacity.

The main screen starts with a team picker. Load the teams I can see with Get Teams in a Workspace, and load people with Get Users in a Workspace so every team member resolves to a name, an email, and an Asana user id. Remember the last team I picked so the board comes straight back to it next Monday.

Once a team is picked, show one lane per team member. Each lane holds every incomplete task assigned to that person across every project in the workspace, not just one project. Fetch each person's work with Get Multiple Tasks using the assignee plus workspace filter, one call per member, and page through the results so a heavily loaded person is never silently truncated. Completed tasks are always excluded, everywhere, with no toggle to bring them back.

Inside each lane, bucket the tasks into four groups: overdue, due this week, due next week, and no due date at all. Put a headline count at the top of the lane and an overload flag on anyone past their threshold, so I can scan the board and see the problem before I read a single card.

Treat the no due date bucket as the important one. Tasks with no due date are the hidden load nobody sees in a normal task list, because they never surface in a due soon filter. Give that bucket the same visual weight as overdue, and include it in the lane headline count.

Each task card shows the task name, which project it belongs to, and its due date. Resolve project names with Get Multiple Projects and cache that lookup for the session, since many tasks share the same handful of projects. A task that sits in more than one project should show all of them.

Clicking a card opens the full detail with Get a Task: description, project memberships, due date, current assignee, and whatever else the record carries.

From that detail view I can do two things without leaving the board. I can reassign the task to another member of the team, and the person picker should show each candidate's current bucket counts so I pick someone with room instead of moving the problem sideways. I can also change the due date. Both changes go through Update a Task.

Every change also writes a Create a Comment on a Task entry recording what changed, who it moved from and to, the old and new due date, and the reason I typed, so the audit trail stays inside Asana where the team already works. Refresh the affected lanes after each change so counts and overload flags are immediately correct.

When a task is reassigned, the new owner gets a Slack direct message telling them what landed on their plate and why. Resolve them from their Asana email with the Slack Bot Look Up User by Email operation, open the direct message with Open a Conversation, and send it with Send a Message. The message names the task, its project, its due date, who moved it, and the reason given. If no Slack user matches that email, still complete the Asana change and show me clearly on the board that the notification could not be delivered.

Make the overload threshold configurable per user and persist it. Default to more than eight tasks due this week, or three or more overdue. Let me edit both numbers in a settings area, and recompute the flags immediately when I do.

Do not build a time off, holiday, or availability column. There is no out of office read operation available here, so any availability signal would be invented. On this board, capacity means assigned open work and nothing else.