Universal Containers (UC) has 140 service resources who handle 2,400Service appointments per day.

Service Territories sized to fewer than about 50 resources is the appropriate Field Service design. Scheduling and optimization quality improves when territories are kept within practical resource and appointment volumes. Splitting 140 resources into three territories yields roughly 46–47 resources per territory and approximately 800 appointments per day if demand is balanced.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Two territories would leave about 70 resources in each, while polygons inside one very large territory do not reduce the number of resources the scheduling engine must consider.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Service Territory design; optimization scalability; dispatcher performance.