You do not create a resource calendar directly. You configure the records that feed it, and Field Service assembles the calendar from them. Here is the path to give a service resource accurate availability.
- Confirm the service resource exists
In the Service Resources list, open or create the record for the worker. Make sure it is active and linked to the right user so the calendar and mobile app resolve to the correct person.
- Define the working window
For fixed schedules, build an Operating Hours record with one or more time slots and the correct time zone. For variable schedules, enable and create Shifts on real dates instead. You can combine both.
- Assign availability through territory membership
Add the resource to a service territory for the relevant date range, and attach the operating hours. Set membership start and end times in the member's own time zone, 24 hours or longer.
- Log absences as they come up
Record vacation, training, and other time off as Resource Absences, on the resource record or directly on the Gantt, so the engine treats that time as unavailable.
- Review on the Gantt and optimize
Open the Dispatch Console Gantt, confirm the calendar reflects hours, shifts, and absences, then run scheduling or single-resource optimization to assign appointments.
A record of working time built from time slots per day of week, with a time zone, attachable to a service territory, service resource, or account.
Date-specific working blocks for a named resource, used when hours change often or extend beyond territory operating hours.
A period when a resource cannot take appointments; blocks time on the calendar and can be created on the Gantt.
The link between a resource and a territory for a date range, where membership times are read in the member's time zone.
- The calendar is derived, not editable. To change availability you edit the underlying appointments, hours, shifts, or absences, never the calendar itself.
- Set territory membership start and end times in the member's own time zone, not the territory's, or scheduling can place work at the wrong hours.
- Log absences before optimization runs. An unlogged day off lets the engine book appointments the resource will never reach.
- Use shifts, not operating hours, for workers whose hours change week to week; fixed operating hours will not flex day by day.