The resource calendar adds that Tuesday is a non-working day, and Wednesday through Saturday are 10-hour days. The task calendar adds that July 4 is a working day.įinally, the resource that will be working on the task has a different working schedule than the rest of your organization. One task in the project takes place in another country, so the July 4 holiday won't apply. The project calendar uses the base calendar as a starting point, but adds that Saturdays are now working days, and Mondays are now non-working days. The base calendar shows the Monday through Friday work week, with July 4 identified as a non-working holiday. The base calendar reflects these working days and hours, as well as company holidays, like July 4 for Independence Day, and December 25 for Christmas.Ī project manager starts a new project that runs from July 1 to July 15, and requires a Tuesday-Saturday work week. Let's say your organization is located in Seattle, and has a typical work week of 8-hour work days, Monday through Friday. These calendars all stack together to frame how work is scheduled on a project. These unique calendars are particularly helpful when accounting for things like a leave of absence, shift work, or tasks that are completed by equipment that runs throughout nights and weekends. Project, resource, and task calendars use a base calendar as a template, and then are modified to reflect the unique working days and hours for individual projects, resources, or tasks. Important: Using Project with Project Web App? If so, check with your administrator to request changes to base calendars.

How to ms project staff timeline