This article applies to firms using Aiwyn Practice.
Work Pools gives staff a self-service way to pull unclaimed work instead of waiting for a manager to assign it. This article explains what a pool is, how Aiwyn decides which items show in it, why claiming behaves the way it does, and where the feature's boundaries are.
The problem work pools solve
During a busy season, large volumes of similar work arrive at once. Traditionally a manager hands each item to a person, which means the manager is a bottleneck and nobody notices when someone runs out of work until later. Many firms have built their own workarounds for this, such as shared boards or route sheets, that sit outside the practice management system and don't know who is already assigned to what.
Work Pools brings that queue inside Aiwyn. Administrators define the queues, work flows into them from projects, and staff take the next item themselves. Because the claim is recorded on the task, stage or project, the rest of Aiwyn (Action Items, project pages, reports) sees the assignment immediately.
A pool is a filter, not a container
Nothing is ever moved into a work pool. A pool is a saved set of criteria: which roles can see it, what kinds of items it shows, and optionally which offices, service lines, work codes and deliverables it covers. When a staff member opens the Work Pool tab, Aiwyn looks across the firm's work and shows whatever matches a pool that person can see.
Three consequences follow. The same item can appear in several pools at once if it matches all of them. Deleting a pool changes nothing about the work; claimed items keep their assignee and unclaimed items keep their eligibility. And a pool's item count is always live, because it is computed from the work rather than stored.
Desks and shelves
It helps to think of two ways work can reach a person. A desk is a personal list: a manager assigns an item to someone and it appears in their Action Items. A shelf is shared: eligible work sits where anyone with the right role can see it, and whoever has capacity takes the next item. Work Pools is the shelf. Both models coexist; an item that a manager assigns directly never appears on a shelf, because it already has an owner.
How work becomes eligible
Work opts in. Each task, stage and project carries a checkbox that marks it as eligible for pools. Project templates carry the same checkboxes so that projects created from the template arrive already marked. The flags are copied onto the project at creation, which is why a task added to a project later needs its own tick.
Stage and task flags are independent. Marking a stage eligible makes the stage itself claimable as a unit; it does not mark the tasks inside it. This lets a firm pool whole review stages for senior staff while pooling individual preparation tasks for junior staff.
The five conditions
An item appears on a staff member's Work Pool tab only when all of these hold at once:
- It is marked eligible.
- Its type (task, stage or project) is one the pool contains, and it passes the pool's office, service line, work code and deliverable filters.
- Nobody owns it. A task with an assignee, a stage with an owner, or a project with an owner is held work, not pooled work.
- It is ready. If the pool's readiness options are on, the item's target start date must have arrived and, for tasks, every dependency must be done.
- The staff member's role is on the pool's Roles list, and if the pool names offices, the staff member belongs to one of them.
The filter rule is the same everywhere: an empty field means all, several values in one field means any of them, and different fields must all match.
Why readiness gates exist
A queue is only useful if everything in it can be worked right now. Without gates, a pool would show tasks whose predecessor isn't finished or whose project hasn't started, and staff would claim work they can't begin. The two readiness options hold those items back until they are actually doable. Both are on for new pools. Pools created before the options existed have them off, so an administrator chooses when to turn them on.
Why the list isn't sortable
The Work Pool tab orders items by nearest due date, then by how long each has waited, and offers no other sort. This is deliberate. Allowing staff to sort or filter by hours or client would let them cherry-pick easy work and leave the hard or urgent items to sit. Pool chips are the only filter, so a firm shapes what staff see by how it defines pools rather than by what staff choose to look at.
Why claiming is first-click-wins
When two people claim the same item at nearly the same moment, Aiwyn lets exactly one succeed and tells the other that the item was already selected. The claim writes the assignee or owner on the item itself and records it in the activity history. This replaces the race that happens with a shared spreadsheet or board, where two people can both believe they own the same return.
Undo is simply the unassign action offered in place while the row is still on screen. There is no time limit; once the row is gone, the item is unassigned from the project like any other.
What claiming does and doesn't do
Claiming a task sets its assignee. Claiming a stage sets its owner. Claiming a project sets its owner. In every case the item leaves every pool, because it is now held, and appears in the claimer's Action Items.
Claiming a project or stage does not assign the tasks inside it. Those tasks stay unassigned and remain in whatever pools they match. This keeps the two levels independent: a reviewer can own a stage while preparers still pull its tasks.
Building a prep-to-review flow
Work Pools does not route work automatically from one pool to another. Firms achieve a handoff by defining two pools with different work codes, for example a preparation code and a review code, and by using task dependencies. With the dependency gate on, a review task that depends on its preparation task appears in the review pool only after the preparation task is done.
Boundaries
- Pools require projects, stages or tasks. A firm that doesn't use tasks has little to pool.
- There is no complexity or skill rating on items, no team-level scope, and no built-in pool metrics such as average age or throughput.
- Stages have no due date, so that column shows
--for them. - A project owner can be replaced but not cleared from the project edit dialog, and duplicating a project does not carry the owner across.
Related
- Set up a work pool and claim your first item
- Create and manage work pools
- Add projects, stages and tasks to work pools
- Claim work from a work pool
- Work pool settings and permissions reference