Constraint-based task assignment

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

Description

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).

Key Takeaways

  1. Filter first — Constraints define the eligible pool. Other allocation patterns then choose within that pool.
  2. Typical constraints — Separation and binding of duties, authorisation levels, certifications, legal rules and availability or working-time limits.
  3. Hard versus soft — Keep hard constraints that come from regulation or risk. Question soft ones that only shrink the pool.
  4. Protects people too — Working-time and qualification constraints protect employees from inappropriate assignments.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

Quality ▲: enforcing separation of duties, authorisation limits and qualification requirements prevents compliance violations, fraud and errors made by unqualified staff, which supports both internal and external quality. Flexibility ▼: every constraint shrinks the pool of eligible people, so it becomes harder to reroute work during peaks or absences, and the process reacts less well to change. Time is neutral or mixed. Cases may wait for an eligible person, but you avoid the delays caused by rework and audit findings. Cost is also neutral: maintaining and checking constraint rules takes effort, which is balanced by avoided violations and corrections.

Example

For example, a bank could enforce that the employee who records a change to a supplier’s bank details may not release the next payment to that supplier. It could also route credit approvals above a certain amount only to staff who hold the corresponding credit authority. When one of these people is on leave, the system offers the task to the next eligible colleague instead of the usual one, which keeps the control in place without waiting for a specific person.

Spotting the opportunity in event data

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.

Sources & references

  1. 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). Summary on this site Publisher page DOI 10.1007/978-3-031-41620-0_22

Share this pattern

Enjoy these

Foundational free Patterns

Apply Integral technology

Elevate physical constraints by applying new technology

Apply triage

Consider the division of a general activity into two or more alternative activities

Appoint case managers

Assign a responsible individual for handling each case type

Assign cases

Let workers perform as many steps as possible for single cases

Automate activities

Consider automating activities

Automate for environmental impact

Implement automation in a sustainable way

Buffer information

Buffer external information and subscribe to updates

Combine activities

Combine small activities into composite activities

Consolidate Work

Collect similar work items and work in batches

← Back

Connected to

Workload-based task assignment

Allocate tasks based on individuals' incomplete workload

What's Happening?

Dec 2023
New Pattern

Consolidate Work

Nov 2023
Oct 2023
Oct 2023
New Cheat sheet

Redesign Essentials

Sep 2023
Sep 2023
Aug 2023
New Pattern

Task delegation

Aug 2023
Aug 2023
New Pattern

Green Feature

Aug 2023