When planning multiday itineraries (e.g. a technician traveling to a distant location for several days), the current workaround is to model a single long shift with hotel breaks. This leads to wrong cost calculations.

We'd like a way to link individual daily shifts together, so that costs are calculated per working day rather than across the full multiday span. This would produce accurate cost reporting and prevent the optimizer from generating solutions where visits are clustered on a single day while costs are counted for the entire week.