Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

Primavera P6 calendars explained: global, project and resource calendars and how they affect float

P6 has three calendar types, and each activity is assigned one global or project calendar. Here is how the hierarchy works and why mixed calendars make float behave unexpectedly.

In short

Primavera P6 has three calendar types: global, project and resource. Each activity is assigned one global or project calendar, which sets its working time, its dates and its total float; resource calendars only drive dates on Resource Dependent activities. Because float is calculated on each activity's own calendar, paths that mix calendars show varying float, so check calendars, lag settings and the longest path before judging criticality.

Primavera P6 has three types of calendar: global, project and resource. Each activity is assigned one global or project calendar, which sets when it can be worked and so how P6 converts durations into dates and calculates float. Resource calendars set when resources are available, and they drive the dates on Resource Dependent activities.

There is no separate "activity calendar" type. The activity calendar is simply the global or project calendar assigned to that activity. Getting this hierarchy right avoids most unexpected date shifts and float values.

What do calendars do in Primavera P6?

A calendar defines the working week, the working hours each day, and holidays and other exceptions. Without calendars, work would be scheduled around the clock, which is unrealistic for most projects.

When an activity has a duration of 10 days, P6 counts only the working time on that activity's calendar to calculate the finish. For example, on a standard five-day calendar a 5-day activity starting on Monday finishes on Friday. If Wednesday is a holiday, the finish moves to the following Monday.

What is the difference between global, project and resource calendars in P6?

Calendar typeWhere it livesWhat can use itTypical use
GlobalThe whole P6 databaseActivities and resources in any projectStandard company work weeks and national holidays
ProjectOne projectActivities in that project onlySite shifts, project-specific holidays, 24-hour working
ResourceResources (shared or personal resource calendars)Resource assignmentsRosters, leave and equipment availability

New activities take the project's default calendar, set on the Defaults tab of the Projects window, unless you assign another. Project and resource calendars can inherit holidays and exceptions from a global calendar, which keeps public holidays consistent across a portfolio.

Which calendar sets an activity's dates?

The activity type decides:

  • Task Dependent: the activity and all its resource assignments are scheduled on the activity's own calendar. Resource calendars do not move the dates.
  • Resource Dependent: each resource assignment is scheduled on that resource's calendar, and the activity's dates span its assignments. A resource holiday can therefore extend the activity.
  • Level of Effort and WBS Summary: dates come from the activities they span, not from their own work.

How do calendars affect durations in P6?

P6 stores durations in hours and displays them in days, weeks or months by dividing by a set number of hours per period. If that conversion does not match the calendar, durations look wrong. For example, on a 10-hour-day calendar with an 8 hours per day display setting, one working day shows as 1.25d. In Admin Preferences (Time Periods), the option to use the assigned calendar to specify the number of work hours for each time period makes the display follow each activity's calendar.

How do calendars affect float in P6?

Total float is the time an activity can slip without delaying the project finish or its constraining date. P6 calculates each activity's float in the working time of that activity's own calendar, not the project's default calendar. On a path that mixes calendars, float therefore changes from one activity to the next even when nothing else differs.

For example, a 7-day calendar activity finishes on Friday and drives a 5-day calendar activity that can only start on Monday. The successor has zero float, but the predecessor shows two days of float, because Saturday and Sunday are working time on its calendar and it could finish on Sunday without delaying anything. A filter of "total float less than or equal to zero" then misses it from the critical path, which is why the longest path is a better test of criticality in mixed-calendar schedules. The total float and negative float article covers float behaviour in more depth.

Two schedule options are worth checking:

  • Calendar for scheduling relationship lag: lags can be counted on the predecessor's calendar, the successor's calendar, a 24-hour calendar or the project default calendar. The same 2-day lag gives different dates under each.
  • Compute total float as: start float, finish float, or the smallest of the two. Mixed calendars make the difference between these more visible.

What are the common calendar mistakes in P6?

  • Assuming resource calendars drive every activity: on Task Dependent activities, a resource's leave or extra Saturday shift has no effect on dates. If resource availability should drive the work, the activity must be Resource Dependent.
  • Reading float across mixed calendars as if they were one: float values on 7-day, 6-day and 5-day activities are not directly comparable. Check the calendar before calling an activity near-critical or not.
  • Inconsistent holidays: updating holidays on one calendar but not the others leaves some activities or resources working on public holidays. Inherit holidays from one global calendar where possible.
  • Hours per day mismatch: durations display as fractions of days because the display setting does not match the calendar's working hours.
  • Misused 24-hour calendars: 24-hour calendars suit curing or continuous plant, not normal site work. Using them for ordinary activities overstates progress capacity and distorts float.
  • Adjusting dates manually instead of using calendars: shift work, weather windows and special working patterns should be modelled with calendars, not with constraints or hand-moved dates, so updates stay consistent.

Practical tips for managing calendars in P6

  • Set up the project's main calendar, working week and known holidays before adding activities.
  • Keep the number of calendars small and give each a clear name that says what it is for, for example "5d x 10h site" or "7d x 24h curing".
  • Create resource calendars only for genuinely different availability patterns, and make sure the activity types match the intent.
  • Show the Calendar column in activity layouts so the assigned calendar is visible, and audit it for critical activities.
  • Record each calendar's purpose, working pattern and holiday source in the basis of schedule.
  • Check calendars as part of every schedule review: activities on 24-hour calendars, calendars without holidays, unused or duplicate calendars, and float jumps along the critical path.

Calendars control when work happens, how durations become dates and how float is calculated. Understanding the three calendar types and the activity type rules turns unexplained date and float behaviour into something you can predict. Calendar setup is part of building a sound programme in project planning, and calendar checks are a standard part of an independent schedule review.

FAQ

Common questions

What is the difference between global, project and resource calendars in Primavera P6?
Global calendars live in the P6 database and can be used by activities and resources in any project. Project calendars belong to one project and can only be used by its activities. Resource calendars define when resources are available and are used by resource assignments.
Is there a separate activity calendar type in P6?
No. P6 has global, project and resource calendars. Each activity is assigned one global or project calendar, and that assigned calendar is what people mean by the activity calendar.
How do resource calendars affect activity durations in P6?
It depends on the activity type. On Task Dependent activities the activity calendar sets the dates and resource calendars have no effect, while on Resource Dependent activities each assignment follows its resource's calendar, so resource holidays can extend the activity.
Why does float look wrong when activities use different calendars?
P6 calculates each activity's total float in the working time of its own calendar. On a path that mixes 7-day and 5-day calendars, an activity can show float over a weekend that its successor cannot use, so float varies along the same path and the longest path is a better test of criticality.
Which calendar does P6 use for relationship lags?
It depends on the schedule option for the lag calendar, which can be the predecessor's calendar, the successor's calendar, a 24-hour calendar or the project default calendar. The same lag can give different dates under each, so check and record the setting.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.