Construction scheduling is one of the most consequential disciplines in project controls, and the foundation of every credible schedule is time. Not just the raw count of calendar days from start to finish, but a precise, structured accounting of when work can actually happen: which days are productive, which are not, how many hours a crew works in a shift, when holidays interrupt flow, and how those variables interact across different trades, contracts, and regulatory environments. In Primavera P6, the mechanism that captures all of this is the calendar.
Yet despite its central role in CPM scheduling, the Primavera P6 calendar is one of the most frequently misconfigured elements on real projects. Schedulers who are otherwise proficient in building logic networks, assigning resources, or running time impact analyses often treat calendar setup as a formality rather than a discipline. The result is schedules that calculate incorrect durations, misrepresent float, and fail agency review for entirely avoidable reasons.
This article provides a thorough grounding in how Primavera P6 calendars work, covering the three calendar types built into the application, the step-by-step process for creating and configuring them, and the practical decisions that determine whether a schedule reflects project reality or only approximates it. Whether you are preparing a baseline schedule for USACE or NAVFAC submission, managing a multi-phase commercial build, or simply trying to ensure your schedule logic holds up under scrutiny, understanding the calendar system is non-negotiable. Proper calendar configuration is not a back-office detail; it is a direct input into every date the schedule produces.
Primavera P6 calendars
Calendars in Primavera P6 define the working time available for a project, activity, or resource. At their most basic level, they specify which days of the week are workdays and how many hours are available within each workday. Beyond that standard structure, they accommodate holidays, planned shutdowns, weather windows, owner-mandated non-work periods, and any other exception to the regular work pattern. An unlimited number of calendars can be configured within a single P6 database, making it possible to model the precise work schedules of every participant on a complex project without forcing them into a single, ill-fitting template.
When a calendar is assigned to an activity, P6 uses it to calculate the activity’s finish date based on its duration and start date. If a five-day activity starts on a Thursday and the calendar defines Saturday and Sunday as non-work days, P6 correctly calculates the finish as the following Wednesday. If that same activity uses a six-day calendar instead, the finish shifts earlier. The calendar, therefore, is not cosmetic. It is a direct driver of every computed date in the schedule, and by extension, of every float value and every critical path determination.
There are three distinct calendar types integrated into the Primavera P6 application: global calendars, project calendars, and resource calendars. Each has a defined scope and a set of rules governing how it interacts with the other two.
Global calendar
A global calendar is built into the P6 database itself rather than belonging to any particular project. Because it lives at the database level, it can be assigned to any project, any work activity, or any resource within the entire Enterprise Project Structure. It can be created, copied, and modified freely, and a single global calendar can be assigned simultaneously to multiple projects. That flexibility is precisely what makes the global calendar powerful and, if mishandled, potentially disruptive. Any modification to a global calendar propagates immediately to every project and activity it is assigned to. On a portfolio with dozens of active schedules, a carelessly edited global calendar can alter calculated dates across every one of them. Access controls and careful naming conventions are therefore essential when managing global calendars in a shared P6 environment.
Project calendar
A project calendar is scoped to a single project within the Enterprise Project Structure. It can be assigned to activities within that project but cannot be applied to resources or to activities in other projects. This scoping makes it the preferred choice for most baseline schedule development work: it keeps the calendar logic contained within the project it describes, eliminates the risk of cross-project contamination, and gives the project scheduler full control over its configuration without requiring database-level access.
Project calendars can be linked to a global calendar as a parent. When this relationship is established, changes to the global parent cascade down to the project calendar, but edits to the project calendar have no effect on the global parent. This one-way inheritance is useful in organizations that want to enforce a common standard (such as a company-wide holiday schedule) while allowing individual projects to layer on their own exceptions. For most construction scheduling applications, the project calendar is the right starting point.
Resource calendar
Resource calendars govern the availability of specific resources: labor, equipment, materials, or any other input whose schedule differs from the activity calendar. They are appropriate when a particular subcontractor works a different shift than the general contractor’s crew, when a piece of specialized equipment is available only on certain days, or when a material delivery window is constrained by supplier logistics. Resource calendars should not be attached to projects or activities directly; their purpose is narrowly focused on resource availability.
Like project calendars, resource calendars can inherit from a global parent, with changes flowing downward but not upward. When P6 encounters a conflict between an activity’s calendar and a resource calendar, the more restrictive schedule governs resource availability. Used correctly, resource calendars are indispensable for accurate resource leveling, realistic schedule compression analysis, and meaningful tracking of resource utilization against plan.
The interaction between all three calendar types gives P6 its scheduling flexibility. A project operating on a five-day, eight-hour calendar can incorporate a concrete crew working six days, a crane available only four days a week, and a federal holiday shutdown that affects everyone, all within a single coherent schedule, provided the calendars are configured deliberately and consistently.
Setup the global calendar
Creating a new calendar
In the main menu bar in Primavera P6, click on Enterprise, and click on Calendars from the main top drop-down menu, as per the following figure.
Now in the “Calendars” section, next select the + Add button, as per the below figure.
Now you can copy a default calendar of P6 and modify it. In the “Select Calendar to Copy From” window, select the 7 Days calendar as an example, according to the following figure.
Now rename the new calendar as 5 Days x10 Hrs, as an example in the figure below.
Modification of calendar
Select “Modify” and open the “Global Calendar: 5 Day x10 Hrs” window, as shown in the figure below.
Note that the “Total work hours/day” option is set to 10 work hours per day, according to the below figure.
This setting is important beyond its face value. When P6 converts durations from hours to days or days to hours internally, it relies on the hours-per-day value defined in the calendar. If the calendar says eight hours but the field actually runs ten-hour shifts, any duration entered in days will be misinterpreted. This mismatch is a common source of schedule errors that are difficult to detect once a baseline has been approved. Setting the hours-per-day value accurately at the outset eliminates the discrepancy entirely.
Now select “Workweek” to mark the non-work days. For example, Saturday and Sunday are non-work days. Type “0” work hours for Saturday and Sunday, as shown in the figure below.
The result is a five-day workweek calendar, as shown in the following two figures.
It is worth pausing here to consider the broader implications of workweek configuration on schedule quality. A project operating on a six-day workweek has roughly 17 percent more productive time per month than one running five days. That difference compounds over a multi-year project and can substantially affect milestone dates, cash flow curves, and contract compliance. Schedulers who default to a five-day calendar without verifying the actual site work pattern may be building in a systematic inaccuracy from day one. Consulting the contract documents, the project execution plan, and where relevant the labor agreements before finalizing the workweek configuration is standard practice in rigorous project controls work.
Allocation of holidays
To mark holidays, highlight the relevant dates in the calendar grid and select the “Non-work” button. In this example, June 17, 2020 and July 1, 2020 are designated as holidays, as shown in the two figures below.
Holiday configuration deserves more care than it typically receives. On federal and state public works projects, certain holidays are contractually mandated non-work days, and their omission from the project calendar can make the schedule non-compliant. On private commercial projects, the holiday schedule may be negotiated or may follow an industry convention. In either case, applying holidays to a global calendar when multiple projects share the same database carries the risk described earlier: a change intended for one project inadvertently alters the schedule of another. Using project-level holidays in a project calendar, rather than global-level exceptions, is a safer approach in multi-project environments.
It is also common practice on longer projects to pre-load anticipated holidays for the full project duration during baseline development, rather than adding them retroactively during monthly updates. Proactively scheduling known shutdowns, seasonal work stoppages, and recurring holidays at baseline gives the schedule a more accurate picture of available working time and reduces the likelihood of float miscalculations that surface only when a date has already been missed.
Time periods
The Hours/Day cell must be set to 10.0 to match the five-day, ten-hour-per-day work week configured above, as shown in the two-step figure below.
The time periods settings determine how P6 converts between duration units. When a scheduler enters a duration in days, P6 multiplies by the hours-per-day value to compute the equivalent in hours. When outputting reports that display durations in weeks or months, P6 uses the hours-per-week and hours-per-month settings to perform the conversion. If these values are inconsistent with the actual calendar configuration, duration displays in reports will be misleading even if the underlying hour-based calculations are correct. Ensuring that the time periods settings match the calendar configuration is part of a complete and accurate schedule setup.
Set default calendar
Finally, set the newly created five-day, ten-hour-per-day calendar as the project default. Select Enterprise, then Projects from the main menu, select the sample project, and assign the new workweek calendar as shown in the two images below.
The default project calendar is the calendar P6 assigned automatically to any new activity created within the project. While individual activities can be reassigned to a different calendar at any time, getting the default right from the outset reduces the risk of inconsistencies accumulating silently across a large activity list. On a schedule with several hundred or several thousand activities, manually auditing calendar assignments after the fact is tedious and error-prone. A correct default is a form of quality control built into the setup process itself.
Setup the project calendar and resource calendar
To create a project calendar or resource calendar, repeat the steps described in sections 3.1 through 3.5 above, selecting the appropriate calendar type as shown in the image below.
When setting up a project calendar, the primary considerations are the project’s contractual work schedule, any owner-mandated restrictions, and the site conditions that govern productive time. When setting up resource calendars, the relevant inputs are the specific availability constraints of each resource type: shift patterns for labor, maintenance windows and mobilization requirements for equipment, and lead time and delivery schedules for materials.
A well-structured P6 schedule typically uses a project calendar as the primary driver for activity scheduling, with resource calendars layered on top only where a resource’s availability genuinely differs from the project baseline. Using resource calendars indiscriminately on every activity adds complexity without adding analytical value and can make the schedule harder to update and audit. The principle is to use the right calendar at the right level of the hierarchy, no more and no less.
How Leopard Project Controls approaches calendar configuration
Calendar configuration looks straightforward on paper, but in practice it is one of the areas where schedule quality diverges most sharply between practitioners. The decisions made during setup, including which calendar type to use, how to structure inheritance, how to handle holidays, how to align hours-per-day with actual site conditions, and how to coordinate calendars across multiple subcontractor work patterns, directly affect the accuracy and defensibility of the entire schedule. A single misconfigured calendar can undermine an otherwise well-built CPM schedule.
Leopard Project Controls brings a construction-first approach to Primavera P6 scheduling services. The firm’s scheduling consultants are not simply software users; they are construction professionals with field-informed understanding of how work actually gets done on site, which makes their calendar configurations reflect the project’s real productive time rather than a generic template. Every baseline schedule Leopard delivers is built with calendars that match the contractual work schedule, account for all known holidays and shutdowns, and align duration entries with the hours-per-day values defined in the time periods settings. This internal consistency is part of what allows Leopard’s schedules to pass agency review, whether the reviewing authority is USACE, NAVFAC, a state DOT, or a private owner with exacting submittal requirements.
Beyond initial baseline schedule development, Leopard supports clients through monthly progress updates, time impact analyses, recovery scheduling, and delay analysis. Calendar accuracy is equally important in these downstream deliverables: a schedule update that inadvertently inherits the wrong holiday configuration or time period settings can generate misleading float values and distort the critical path in ways that are consequential for claims, negotiations, and project decision-making. Leopard’s project controls services maintain calendar integrity across the full project lifecycle, from Notice to Proceed through final completion.
For general contractors, project managers, and owners who are working through complex scheduling requirements or navigating a dispute where schedule accuracy is at issue, Leopard offers a flat-fee proposal within 24 hours and delivers draft schedules within seven days, with unlimited revisions until the document is approved. The firm serves federal, state, and private sector clients nationwide, with particular depth in government construction scheduling and the compliance requirements of major contracting agencies.
Summary
The Primavera P6 calendar system is the temporal foundation of every CPM schedule. Getting it right is not an optional refinement; it is a prerequisite for any schedule that aspires to be both accurate and defensible. The three calendar types, global, project, and resource, each serve a distinct purpose and operate within a hierarchy of inheritance rules that, once understood, give schedulers substantial flexibility to model complex, multi-resource project environments with precision.
Global calendars provide database-wide reach but require careful governance because changes propagate across every assigned project. Project calendars are the right default for most construction scheduling work, keeping the calendar logic scoped to the project it serves. Resource calendars address the availability constraints of specific inputs and, when used selectively, add a level of analytical fidelity that generic activity calendars cannot provide.
The configuration steps covered in this article, creating a new calendar, setting work hours per day, defining the workweek, allocating holidays, aligning time period settings, and assigning the calendar as the project default, form a coherent workflow that applies regardless of the specific schedule requirements. Each step builds on the last, and an error or omission at any point carries forward into every calculated date the schedule produces.
For construction professionals who need schedules that satisfy rigorous agency and owner requirements, understanding these mechanics is the starting point. Applying them consistently, project after project, with the discipline to verify every configuration decision against the actual project conditions, is what separates a compliant, trusted schedule from one that creates more problems than it solves. The calendar is where that discipline begins.
Leopard Project Controls specializes in precisely this kind of meticulous, construction-informed Primavera P6 scheduling. Whether the need is a first-time baseline submission, a time impact analysis to support a delay claim, or ongoing monthly update support through project closeout, Leopard delivers project controls services built on the same foundational rigor described throughout this article.
Questions and Answers
What is the difference between a global calendar and a project calendar in Primavera P6?
A global calendar is stored at the P6 database level and can be assigned to any project, activity, or resource across the entire Enterprise Project Structure. A project calendar is scoped to a single project and can only be assigned to activities within that project. The practical consequence is that editing a global calendar affects every schedule it is tied to, while editing a project calendar affects only that project. For most construction scheduling work, especially when multiple projects share a database, using project calendars reduces the risk of unintended cross-project impacts and gives the individual scheduler tighter control over the schedule’s working time definition.
Why does the hours-per-day setting matter so much in a P6 calendar?
When a scheduler enters activity durations in days, P6 uses the hours-per-day value defined in the calendar to convert those durations into hours internally. If the calendar says eight hours per day but the site actually runs ten-hour shifts, every day-based duration entry is being interpreted incorrectly. The finish dates P6 calculates will be later than the actual productive schedule warrants, and any resource loading built on those durations will be similarly distorted. Setting the hours-per-day value to match the real work shift is one of the simplest and most important accuracy checks in calendar setup.
Should holidays be entered in the global calendar or the project calendar?
In a single-project database, either approach works. In a shared database where multiple projects are active simultaneously, entering holidays at the project calendar level is generally safer. Marking a date as non-work in a global calendar applies that exception to every project assigned to that calendar, which may not be appropriate if different projects have different holiday obligations. For government contracts in particular, where specific holidays are contractually mandated, verifying that the holiday list matches the contract requirements and applying it at the right calendar level is a standard step in compliant schedule development.
When is it appropriate to use a resource calendar instead of relying on the activity calendar?
Resource calendars are appropriate when a specific resource has an availability pattern that genuinely differs from the project’s standard work schedule. Common examples include a subcontractor who works a different shift, a piece of equipment available only on certain days due to maintenance or shared-use agreements, or a material delivery constrained by supplier hours. When there is no meaningful difference between a resource’s availability and the activity calendar, adding a resource calendar introduces complexity without adding analytical value. The guiding principle is to use resource calendars selectively, only where the deviation from the project calendar is real and material to the schedule outcome.
How does proper calendar setup affect schedule submittals to agencies like USACE or NAVFAC?
Agency reviewers evaluating a Primavera P6 schedule under USACE or NAVFAC specifications look at calendar configuration as part of the overall schedule quality assessment. A schedule whose calendars do not reflect the contract work schedule, that omits required holidays, that has hours-per-day settings inconsistent with the time periods configuration, or that applies the wrong calendar type to resources or activities will typically generate review comments or outright rejection. Correcting these deficiencies after initial submission delays the approval process and can hold up Notice to Proceed or early payment milestones. Building the calendar correctly at baseline is the most efficient path to first-submission approval and the uninterrupted cash flow that follows.
