Allocate tasks considering business process execution constraints
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
category: Human Resource Utilisation class: Allocation Rules frameworkAspect: Organizational Population perspective: organizational/resource
Constraint-based task assignment belongs to the utilisation category of the HRAPs (Goel et al., 2023). Before any other criterion is applied, it limits who may perform a task according to the constraints attached to its execution in the process. The resource attribute is eligibility under those constraints. Typical constraints are separation of duties (the person who requests a payment may not approve it), binding of duties (the person who started a case also performs a later step), authorisation levels and certifications, legal or regulatory requirements, conflict-of-interest rules, and availability restrictions such as location, shift and working-time limits.
The allocation rule acts as a filter. Constraints decide who may do a task, and the other HRAPs decide who should do it. It pairs most naturally with Workload-based task assignment, the other utilisation pattern: the eligible candidate with the lowest open workload gets the task. Many of these rules correspond to the workflow resource patterns on authorisation, separation of duties and case handling in the BPM literature, and they are often embedded in ERP and workflow systems.
Constraints also protect employees. Rest-period, overtime and qualification rules keep people from being assigned work they shouldn’t or can’t do safely, and transparent rules make allocation feel less arbitrary. Over-constraining, however, takes away discretion and the opportunity to learn new tasks. In the ability–motivation–opportunity view behind employee-aware BPI, that weakens motivation. You should therefore distinguish hard constraints (law, risk) from soft ones (habit, preference).
■ This pattern ■ Baseline
Framed along the FLAC rule types — fitness, location, attribute, constraint.
Fitness: compliance-critical processes such as purchase-to-pay, lending, claims or healthcare. Measure the current rate of constraint violations; if it is near zero, the pattern is already applied. Location: activity pairs that are subject to segregation-of-duties rules (create and approve a purchase order, change vendor bank data and pay), and approvals with value thresholds. Attributes: share of cases where the same resource performs both sides of a duty pair, approvals by users below the required authority level, and executions outside working time. Constraints: count the eligible resources per activity so that flexibility does not collapse, and don’t add rules without a regulatory or risk rationale.
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
Workload-based task assignment
Allocate tasks based on individuals' incomplete workload