Setting up task distribution through Bitrix24 streams

Configuring Task Distribution through Bitrix24 Flows

A manager spends an hour a day deciding who to assign the next task to. One employee is overloaded, another sits idle, a third is already on vacation—but the task is assigned to them. Bitrix24 flows automate distribution: a task enters the flow, the system itself selects the executor by set rules.

Distribution Methods

Bitrix24 offers three basic task distribution methods in flows:

Round-robin (in order). Tasks are assigned to flow participants in sequence. The system remembers who received the previous task and assigns the next one to the next person in the list. If an employee is absent (vacation, sick leave)—skip them.

Suitable for: uniform tasks with equal complexity. Example—processing incoming requests, where each request takes approximately the same time.

By workload. The system counts the number of active (open) tasks each flow participant has. A new task is assigned to whoever has the fewest open tasks. If several participants have equal workload—the first in the list is chosen.

Suitable for: tasks of varying duration. Example—design tasks: one mockup takes an hour, another takes three days. Round-robin doesn't work here because task count doesn't reflect actual workload.

Manual assignment by manager. The task enters the flow queue, the flow manager sees it in the backlog and assigns it to a specific employee. The system doesn't intervene.

Suitable for: tasks requiring expert assessment. Example—legal requests, where lawyer specialization must be considered.

Assignment Rules

Beyond the basic method, additional rules are configured:

• Exclude absent. Employees on vacation or sick leave (marked in Bitrix24) are automatically excluded from distribution.
• Task limit. Maximum number of active tasks per participant. When the limit is reached, tasks are assigned to others.
• Participant priority. Some employees get tasks first—e.g., interns get only simple tasks, complex ones go to senior specialists.
• Competency filter. If a task is tagged "1C"—it's assigned only to participants with corresponding competency.

Reassignment

Situations requiring task reassignment:

• Executor rejected the task—task returns to the queue.
• Executor didn't start work within N hours—automatic reassignment.
• Flow manager manually reassigned the task.

In automatic reassignment, the system excludes the current executor and applies the standard distribution algorithm to remaining participants.

Typical Configurations

What We Configure

• Select distribution method for each flow
• Rules for excluding absent employees
• Task limits per participant
• Competency and priority filters
• Automatic reassignment rules
• Testing: running tasks through the flow, checking load balancing