These features are available exclusively on the Advanced Engine. These features are intended for use during CSV or API Task import. To understand how to populate the column headers in the CSV, you can check our data import documentation.
Assignment, Sequencing, and Task Splitting - basic terms
Task/Job splitting consists of several separate segments that serve different purposes, and these segments can be combined to achieve the desired splitting behavior.
There are a few key categories to consider:
Optimization configuration - This section refers to Task pre-assignment. Here, it is specified if a specific batch of Tasks should be assigned to the same driver, same vehicle, and the exact order of the Tasks in the route is also specified here.
Sequence - This setting defines a group of Tasks that must be performed a specified number of times. It also allows you to define the allowed time range (in days) between two consecutive instances of Tasks that belong to the same sequence group.
In other words, it controls both how many times the Tasks should be completed and the maximum number of days that can pass between each occurrence.
Synchronization - This section defines the parameters that determine whether specific Tasks must be performed in sync with one another.
Users can specify if a job requires multiple people, which will generate multiple instances of the same Task based on the number of required team members. Additionally, an arrival time buffer can be defined to allow a permitted difference in arrival times between the assigned personnel.
All elements within this section can be combined and used together seamlessly.
For example, you can define a sequence and specify the number of required instances, while also determining how many assignees are needed for each job and whether those jobs must be completed simultaneously.
Optimization configuration
The following Optimization configuration information can be specified:
Same Assignee Key - Value provided by users in case they want a specific Task in a sequence to be handled by the same worker, but want to leave it up to the system to determine which worker would be best suited to do the job.
Same Route Key - Value provided by users in case they want a specific Task in a sequence to be tied to the same Vehicle, regardless of which worker will be driving that vehicle.
Route Pickup Order - Determines the order in which the pickup needs to be made (in case of a pickup/delivery workflow, and for field service businesses, this field is usually ignored).
Route Order - Determines the Task's order in the route, i.e., in which order the Task needs to be executed.
Sequence
The following Sequence information can be specified:
Sequence Key - This field is used only if there is already a sequence in the data you are uploading to eLogii, and the system should not perform a split. It indicates whether Tasks belong to the same sequence (i.e., they are instances), so all the Tasks that are a part of the same sequence must have the same sequence key to be recognized as such.
In case users want eLogii to assign a sequence key and perform a split based on set criteria, this field should be left empty.
Sequence Index - This field is used only if there is already a sequence in the data you are uploading to eLogii, and the system should not perform a split. Once the Sequence Key (field above) has been specified for the Tasks that belong to the same sequence, the index value needs to be specified. The Index indicates the instance's place in the sequence. It's an integer field, and the index numbers start from 0. This means that the first Task(instance) in the sequence will have 0 as the index value, the second one will have 1, and so on.
Number of Instances - Indicates the number of instances that should be created from the specific Task if it needs to be split.
For example, if a user wants to import jobs where a single entry indicates something that needs to span two days, they would need to provide the number of instances and set it to 2. They do not need to provide the sequence key and index because the system would automatically generate those.
Min Days Between - Indicates the minimum number of days that should be between each sequence for the specific Task. e.g., if 2 is set as the number of days between each instance, there will be at least 2 days between each instance.
Max Days Between - Indicates the maximum number of days that should be between each sequence for the specific Task. e.g., if 5 is set as the number of days between each instance, there will be no more than 5 days between each instance.
Min Days Between and Max Days Between values take into account the Driver's workday availability, rather than flat day values. For example, if the maximum number of days between 2 instances is set to 2, one instance is scheduled on Friday, but the Driver does not work during the weekend, the next instance will be scheduled for Tuesday (or Monday, depending on whether the Min Days was set to 1), instead of Sunday.
Sequences and Allowed Week Days
Sequences and Allowed Week Days can function in tandem. Though it works differently than it does with Driver workday availability. In the case of Allowed Week Days, the days between buffer dows not adjust to them, the date range is treated as a flat range value, and the vailable days are only viewed as an additional constzraont.
For example, you might allow a Task to run between Monday and Wednesday, but only on specific weekdays, say Monday and Wednesday.
If the Driver is scheduled across the entire date range and the configuration specifies two instances with a two-day gap between them, the Task will be assigned on the first available day (e.g., Monday) and then again on the next allowed day that satisfies the gap (e.g., Wednesday). However, if the gap is set to one day and that next day is not an allowed weekday, the Task becomes unviable.
The idea is that you define a continuous date range and apply a rule such as “every third day” to generate Task instances in sequence. When allowed weekdays are also configured, they determine which specific dates within that range are actually eligible for scheduling.
Using the same Monday–Wednesday example, if the Task is set to occur every third day starting from Monday, the next calculated date would be Thursday. Since Thursday is not an allowed weekday in the example, that instance cannot be scheduled, making the Task unviable for that date.
Handling Driver Availability and Allowed Weekdays ensures that minimum and maximum spacing between Tasks is respected, while also accounting for Driver schedules and permitted working days.
The system evaluates Driver availability and allows weekdays to determine which assignment dates are actually feasible. This prevents unviable scheduling and ensures compliance with business rules governing task timing. Minimum and maximum day constraints provide flexibility to model preferred scheduling intervals while still adapting to real-world availability.
Synchronization
The following Synchronization options can be set up:
Synchronization Key - For multi-man jobs, this value indicates that Tasks must be synchronized and performed simultaneously.
If multiple Tasks share the same synchronization key, this tells eLogii that several people are required for the same job and must be assigned to the same Task, at the same location, and at the same time.
Synchronization Index - This index specifies the order of a Task in a synchronization group. For example, if there are three Tasks in a synchronization group, this field determines whether a Task is done first, second, or third.
Number of Assignees Required - Determines the number of workers required to do the job in synchronization.
Arrival Tolerance - This field defines the arrival tolerance for multi-man jobs (jobs where multiple people are required to be at the same location simultaneously.
For example, if the arrival tolerance is set to 15 minutes, the scheduled arrival times of the assigned team members may differ by up to 15 minutes. This means each person can arrive within a 15-minute window relative to the others assigned to the same job.
All these elements can be set per Task, meaning that each Task's sequence can be set up on an individual level.
Task/Job Splitting and Skills
By default, if no further instruction is given to eLogii, when splitting jobs with specific skills associated with them, the Task instances will have both skills listed in the requirements.
This can be overridden by instructing the system to split the jobs, where instance one will have one skill, while instance two will have the other skill. Or, if, for instance, one instance needs to have 2 specific skills, but the second one needs to have 1 skill, that can still be specified in the override fields.
Service Duration Splitting and Assignment Configuration
Service Duration Splitting and Global assignment configuration settings can be found in Configuration ⇒ Optimization ⇒ Service/Setup duration under the Enable service duration splitting configuration option. Once configured, the criteria will be applied to only imports done after the changes were saved.
The Enable service duration splitting option must be enabled to get the different Service Duration Splitting options, as well as split mode selection.
Service Duration Split
The Service Duration Splitting options are:
Minimum duration to split - Tasks whose service duration exceeds the defined threshold (in minutes) will be automatically divided into multiple instances. For example, if the service duration exceeds 240 minutes, the Task
Maximum duration per instance - The maximum allowed service duration (in minutes) for each split instance. All Tasks created from the split will not exceed the defined value. For example, if you set 120 minutes as the maximum duration per instance, no Task instance created by the service duration splitting will be longer than 120 minutes.
Remainder distribution - This field instructs eLogii how it should allocate the remaining minutes when the total duration cannot be evenly divided between split instances. The remainder can be either added to the last instance, added to the first instance, distributed evenly across all instances, or split between the first and the last instance.
Split modes
Instructs the system how Tasks should be split. Users can choose between splitting Tasks across multiple days (Multi-day jobs), multiple drivers on the same day (same-day), or both (combined). Different options will appear based on the selected split mode. Split Modes will appear once the Enable service duration splitting configuration option is enabled in Configuration ⇒ Optimization ⇒ Service/Setup duration.
If Days is set as the preferred splitting option, two additional options are unlocked:
Maximum days - Maximum number of days to spread the Task across for sequence instances.
Expand date range automatically - If this option is enabled, when a Task with a single scheduled date is split across multiple days, the system will automatically convert the single date into a date range covering all affected days.
Users can also define a range buffer that determines how the date range is calculated when a single-date Task is split across multiple days.
If Drivers is set as the option, users unlock the following option:
Maximum drivers - This field determines the maximum number of drivers that can work on the task simultaneously (for synchronized instances).
If Combined is set as the preferred splitting option, users get both the options for Drivers and Days.
Use cases
These sets of assignment configuration options are ideal for field service businesses that need to split their jobs and schedule them according to specific rule sets.
The most common scenarios that can be supported are as follows:
Task Sequencing for Multi-Day Jobs
Many use cases require splitting a single real-life job into multiple sequential Tasks.
Task Sequencing for Multi-Day Jobs enables users to divide one job across multiple days, with the Sequence feature defining the number of required instances and (optionally) the number of days allowed between them.
For example, a two-day job requiring two people will result in four Tasks in total. Each Task will have a sequence key and sequence index to ensure proper linkage and execution order.
eLogii supports flexible input methods:
If a single CSV entry indicates a multi-day job, the system automatically generates the necessary sequence keys and indexes.
Alternatively, customers can provide multiple CSV entries with explicitly defined sequence keys and indexes to indicate the relationship between Tasks. (When the dataset already contains predefined splits, this signals to the optimization engine that no additional splitting is required and that the imported jobs belong to the same sequence.)
This flexibility allows different input formats while preserving task linkage for accurate optimization and scheduling.
Synchronization for Multi-Person Jobs
Synchronization for Multi-Person Jobs ensures that multiple assignees work simultaneously at the same location and time, coordinated through synchronization keys.
Tasks that require different skills or multiple people for the same job share the same synchronization key while maintaining individual indexes.
eLogii aligns arrival times within a defined tolerance window, ensuring synchronized start times for all assignees involved in a multi-person job.
By combining sequence keys and synchronization keys, users can configure complex multi-day, multi-person jobs, with all related Tasks properly linked and assigned for optimized scheduling.
Same Assignee Enforcement
Same Assignee Enforcement ensures that all instances of a multi-day job are assigned to the same person by using a shared assignee key.
This applies regardless of whether the Tasks are part of a sequence, supporting use cases such as weekly tutoring sessions with the same instructor or recurring visits by the same nurse.
By default, this setting prevents different people from being assigned to different days of the same job. However, eLogii’s flexibility allows users to override this behavior in special cases when necessary.
Splitting Jobs Based on Allocated On-field Time
Automatic Service Duration Splitting allows long service durations to be automatically divided into smaller task segments based on a configured maximum chunk size.
This makes it easy to assign work across multiple days or multiple team members without manually creating separate tasks.
For example, users can define a maximum task duration (e.g., 8 hours, 4 hours, etc.). Any service that exceeds that limit is automatically split into multiple Tasks. A 16-hour job can be split into two 8-hour Tasks, or four 4-hour tasks (depending on your configuration).
If the total duration doesn’t divide evenly, eLogii automatically distributes the leftover time, and the remainder can be assigned to either the first or last task, depending on settings
This feature is especially useful for handling services that exceed a standard workday while maintaining clean and structured scheduling.
Combining Service Duration Splitting with Multi-Person Assignments
This feature combination allows long jobs to be divided across multiple days and/or assigned to multiple people to shorten the overall completion time.
Customers can define thresholds that determine:
When a job should be split across multiple days
When should additional people be assigned to work simultaneously on the same day
If multiple people are assigned on the same day, the system creates synchronization groups to ensure they’re scheduled together. At the same time, it can sequence the split Tasks across multiple days if needed.
This makes it possible to handle more advanced scheduling scenarios. For example:
A 16-hour job can be split into two 8-hour Tasks
Those 8-hour Tasks can be completed by two people working simultaneously
This approach supports complex scheduling needs while keeping assignments coordinated and efficient.