SLA Design for Multi-Region Assignment Groups with Different Time Zones & Reassignment Handling

[DeeshaP]

Hi, I am looking for best practice guidance on designing an SLA model for Service Catalog Tasks (SCTASK) in a multi-region environment where assignment groups have users across different time zones (e.g., Asia, Europe, Americas), and tasks may move across multiple assignment groups during their lifecycle or be reassigned within the same group to different members working in different time zones. The main challenge is determining which business schedule an SLA should follow when a single assignment group spans multiple time zones, given that SLA cannot dynamically adjust based on the assigned user’s timezone. Additionally, I need clarity on how SLAs should behave during reassignment—whether a single SLA should continue using pause/resume logic or whether it is better to stop and start new SLAs per assignment group—and specifically, if a task is reassigned to another member within the same assignment group but in a different time zone, should a new SLA be triggered or should the existing SLA continue. I also want to avoid multiple SLAs per task while still ensuring a single, clear SLA outcome for reporting and audit purposes. Further, I am trying to understand the best approach for schedule design, whether to use regional schedules, a unified global schedule (such as 24x5 or follow-the-sun), or a hybrid model, in a way that balances accurate SLA measurement, fair accountability across teams, and clean, reliable reporting. Any recommendations, proven design patterns, or real-world examples would be highly appreciated.