Non-Working Days & Days Off

Non-Working Days and Days Off are managed using calendars.

Click Working Days to access resource calendars.
Each person (resource) has a calendar. In this example, Mary edits her Calendar's Properties to manage her Non-Working Days and Days Off.
The standard values for Availability, Capacity, and Workweek are inherited by each resource from the Group or Custom calendar which is managed by the Playbook Administrator. These should only be modified if they are different from the inherited values, otherwise, they should remain inherited. See this article for details on how to administer Group calendars. (update link in Whatfix)
Mary does not work on Fridays. To account for this on her tasks, she clicks the Basic tab, deselects the checkmark next to Workweek, and then deselects Friday. This is called a Non-Working Day.
Mary's calendar is now colored gray every Friday. Hovering over any Friday, the tooltip indicates this is a Non-Working Day. Note: the other gray vertical bars indicate weekends.
Mary's Non-Working Days are also colored gray in the Game Plan. Her tasks will automatically adjust around her Non-Working Days (explained below in detail).
Mary will also be on vacation on January 16 and she wants to make it visible to her teammates that she will not be in the office and ensure her tasks will adjust around her day off.
In the Days Off/On tab, she clicks Add, enters Vacation for the Name, and then selects January 16 for the From and To dates. If she were on vacation for more than one day, she would enter the appropriate From and To dates respectfully.
Each person manages their personal time off. Company holidays, listed below Mary’s Days Off, on the other hand are inherited from either a Group or Custom calendar (R&D in this example) and are managed by the Playbook Administrator.
Mary's calendar is colored blue on her Day Off. When you hover over the Day Off, the tooltip shows the name of the Day Off, Vacation in this example.
Mary's Days Off, inherited and not inherited, are colored blue in the Game Plan. Her tasks will automatically adjust around her Days Off (explained below in detail).
Non-Working Days (gray) and Days Off (blue) are also colored on the calendar in the Huddle and My Playbook views.

There are two options for a task's duration: Working Days and Weekdays.

Duration Option	Description	Typical Use Cases
Working Days	A task's duration only considers working days. Non-Working Days and Days Off are not considered. For example, if a task's duration is 3 days but it intersects a Non-Working Day or Day Off, it will look like a 4-day task.	Work tasks Meeting tasks
Weekdays	A task's duration considers all weekdays, including Non-Working Days and Days Off. Using the same 3-day task example above, the duration of this task is not affected by Non-Working Days or Days Off.	Monitor tasks

Work and Meeting tasks use Working Days by default, causing them to adjust automatically around Non-Working Days and Days Off.
Monitor tasks use Weekdays by default. The start date of a Monitor task adjusts automatically around Non-Working Days and Days Off because it is assumed that the assigned resource will need to do some work before the Monitor task can start. The end date of a Monitor task, however, will not adjust around Non-Working Days or Day Offs because it is assumed that the assigned resource will not need to do any work.
The task duration option can be modified as needed in Task Properties by either selecting from the Duration drop-down menu or by changing from one calendar to another using the Calendar drop-down menu, typically either the Resource or Default calendar. The Resource calendar uses a mix of Working Days and Weekdays while the Default calendar uses Weekdays for all tasks.
As a best practice, each person should create their Days Off and Non-Working Days up to date in a timely manner to keep the timeline accurate.
Need a hand? Contact a Customer Success Engineer today! 😀