Team workload & assignment
A staff roster with live-computed workload — clients handled and open tasks per accountant — for assignment decisions made on numbers.
Team workload & assignment
Workload computed, not reported
Open tasks, clients handled and overdue counts come from the task records themselves.
Capacity in the same view
Each member carries a weekly capacity, so load reads against something rather than in the abstract.
Roles that mean something
Owner, admin, member and viewer — enforced by the API, not just hidden in the UI.
Assignment is usually a guess
"Who has room?" is answered by whoever speaks first, or by whoever is least likely to say no. The firm rarely has a number in front of it at the moment the decision is made.
By the time overload is visible it is February and the person carrying it has been carrying it since December.
How the team roster works
Every staff member has a profile carrying a role, a title and a weekly capacity. Against that profile the system computes, live from the task and client records, how many clients they handle, how many tasks are open, and how many of those are overdue.
Because the numbers are computed rather than entered, they cannot drift. Reassigning a task changes both people's counts immediately.
- Roles: owner, admin, member, viewer — enforced server-side
- Weekly capacity per member
- Live counts of clients handled, open tasks and overdue tasks
- Invitations by email with an expiring token
What changes for the firm day-to-day
Assignment decisions get made against the roster instead of against the loudest voice. Overload is visible in November rather than in February.
When someone leaves or goes on leave, their book is a filter rather than a reconstruction.
What ships in the module
- A staff roster with role, title and weekly capacity per member.
- Live-computed clients handled, open tasks and overdue tasks per member.
- Four roles enforced at the API layer.
- Email invitations with expiring tokens.
Updated July 2026