Task bundling reduces unnecessary site visits by automatically grouping related work orders when certain criteria are met, such as the same site, contractor, task type, and scheduled time frame.

When tasks are bundled, the system creates a parent task that acts as an umbrella for the individual child tasks. This gives management, site, and contractor/supplier users a single place to manage work while preserving the details and completion records for each individual task.

Terms

• Task Bundling is the feature that automatically groups related tasks/work orders together.
  • Tasks may also be grouped together manually.
• Parent/Child Tasks are grouped tasks/work orders that are managed together. 
  • The parent task provides an overall view of the bundled work.
  • Each child task retains its own information, history, and completion status, but can be managed in bulk for convenience.
• Related Tasks are grouped tasks/work orders that are loosely associated, but do not operate together in a dependent relationship.

Bundling Rules

Assigning Tasks to Bundles 

• If a scheduled task shares the same site, same contractor, same task type, and falls within the same bundle group of selected templates and configured time window — it is eligible to bundle.
• If a reactive task shares the same site, same contractor, and same task type within the configured time window — it is eligible to bundle.
• A bundle can only include reactive or scheduled tasks; not both. 
• If a task matches the criteria for more than one bundle, it goes into whichever bundle is evaluated first.
• If a task is manually unlinked from a bundle, it cannot be automatically added to a future bundle. It can still be manually re-bundled, and if necessary, Titan Support can re-enable the task for automatic bundling.

Parent Task Behavior

• When tasks that meet eligibility criteria are identified and grouped, the system automatically creates a parent task and assigns the qualifying tasks as children.
• Parent tasks inherit the workflow of the first child task added to the bundle.
• The SLA for the parent task is set to the earliest SLA date across all child tasks. 
• The parent task automatically closes when all child tasks are closed. 
• If a parent task is manually closed or re-opened, the action will cascade to all child tasks. 
  • Users may choose to close the parent task without closing all child tasks. In this case, open child tasks will become unlinked.

Child Task Behavior

• If a child task is created from a parent task, the child's supplier/contractor must be in the same hierarchy as the parent, and share the same workflow as the parent.
• If a child task's contractor is changed after bundling, the child is automatically unlinked from the parent.
• Child tasks can only exist in one bundle. Users will need to confirm if they are reassigning a child to a different parent.  

Related Tasks

• Users may choose to manually associate tasks as related tasks. Related tasks are not created or linked manually.
• Related tasks do not have dependent relationships. Closing one related task does not impact associated tasks.