There is a need to model an entity that can show the current schedules of an organization. The schedules are to show customer support agents, dispatchers, and managers what work requests with what skills, time, and location have been received, what employees or pools are reserved for the requests, and what employees are assigned to do the work tasks. Besides the Pools of available capacity, the schedules support CSR, Workforce managers, and dispatchers, allowing them to have an overall view of current assignments, to make decisions about further reservations and assignments, or the planning of future capacity.<br/>For this purpose we introduce WorkSchedule, which can hold Reservation (booking) and Assignment. An example of WorkSchedule is when a contractor team responsible for the New York market has been receiving 100 appointment requests for fiber installation during July and currently reserves employees to perform 80 of them in particular timeslots.<br/>The explicit modeling of WorkSchedule and its association with other entities like Pools, Reservation, and Assignment is a subject of a future revision of this Workforce Management addendum. In this version, following the model of ProjectSchedule, we propose that WorkSchedule is also to be a type of SimpleCalendar, defined in Common guide book section Calendar ABE.<br/>The following Figure represents the WorkSchedule entity.<br/>Being an extension of Simple Calendar, WorkSchedule inherently contains CalendarEntry (start–end time, or time slot). We can use CalendarEntry to associate it with the Appointment, Reservation, and Assignment records.<br/>An organization can have more than one WorkSchedule for various purposes (e.g. for a time period, some work types, or serving areas).<br/>