Allocate tasks based on individuals' incomplete workload
Goel, K., Fehrer, T., Röglinger, M., & Wynn, M. T. (2023). Not Here, But There: Human Resource Allocation Patterns. In Lecture Notes in Computer Science (pp. 377–394). All sources
Workload-based task assignment belongs to the utilisation category of the HRAPs (Goel et al., 2023). It assigns tasks to people according to their workload, defined as the number of task instances a person has started but not yet completed. The allocation rule is usually to give the next work item to the eligible person with the lowest workload. This corresponds to the “shortest queue” distribution known from the workflow resource patterns. Workload can be reconstructed from start and complete events in an event log at any point in time. Simple counts treat all tasks as equal, so in practice you may weight work items by their expected effort.
In the study, experts named it among the most pervasive patterns. It pairs naturally with Constraint-based task assignment, the other utilisation pattern: constraints define who may do the task, and workload chooses among those people. It is also the main counterweight to the productivity patterns. Performance-based task assignment and Experience-based task assignment tend to pile work on the best people, and a workload cap keeps that in check.
For employees, the pattern is the most direct protection against chronic overload. It spreads work fairly, and that matters for well-being and for how fair the allocation feels. One side effect needs attention: people who finish quickly receive more work, so speed is “rewarded” with more load. Caps, effort weighting and transparency about how the rule works reduce this effect.
■ This pattern ■ Baseline
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: processes with start and complete timestamps per resource and a pool of interchangeable people. Location: activities and roles where open work is spread unevenly across resources, and cases waiting in front of particular people while others are free. Attributes: work in progress per resource over time (started but not completed), the spread of workload within a role, waiting time by assigned resource, and availability or working time. Constraints: without start events, workload can’t be measured as defined. Adjust for part-time work and absences, and combine with constraint and skill rules so that balancing doesn’t send work to unsuitable people.
Foundational free Patterns
Elevate physical constraints by applying new technology
Consider the division of a general activity into two or more alternative activities
Assign a responsible individual for handling each case type
Let workers perform as many steps as possible for single cases
Consider automating activities
Automate for environmental impact
Implement automation in a sustainable way
Buffer external information and subscribe to updates
Combine small activities into composite activities
Collect similar work items and work in batches
Constraint-based task assignment
Allocate tasks considering business process execution constraints
Constraint-based task assignment
Allocate tasks considering business process execution constraints