A schedule calendar defines working periods and nonworking periods. It can represent a five-day workweek, different shifts, holidays, or seasonal restrictions. Activity durations need a calendar before they can be translated into start and finish dates.
Calendar assignments matter as much as calendar names. A calendar named “Standard” does not tell the reviewer whether Saturday is working time or whether a holiday exception was added.
How it works
A calendar has three layers:
- A standard workweek, such as Monday to Friday, 7:00 to 15:30 with a half-hour break.
- Exceptions, such as public holidays, a site shutdown over the winter break or a working Saturday.
- Hours per period, which the software uses to convert between hours and the days, weeks and months it displays.
Each activity is assigned one calendar. The engine counts the activity’s duration through that calendar’s working time, skipping nonworking periods, to find its finish. Float is also measured in working time on a calendar, which is why it can’t be compared directly between activities on different calendars.
Typical construction schedules carry several calendars: a five-day calendar for most site work, a six-day calendar for an accelerated trade, a seven-day calendar for curing, deliveries or owner review periods, and a restricted calendar for work that can’t happen in certain months. Primavera P6 also has global, project and resource calendars, and Microsoft Project has project, resource and task calendars, so it matters which one is actually driving each activity.
Worked example
Illustrative: a task needs five eight-hour workdays and starts at the beginning of Monday. On a Monday-to-Friday calendar with no exceptions, it finishes at the end of Friday. If Wednesday is a nonworking holiday, the same 40 hours finish at the end of the following Monday. The duration did not increase; the elapsed time changed.
Now add a lag. A slab pour on the five-day calendar finishes Friday, and its successor, stripping formwork, follows with a 3-day lag for curing.
| Lag calendar | Lag counts | Formwork stripping can start |
|---|---|---|
| Seven-day (or 24-hour) | Sat, Sun, Mon | Tuesday |
| Five-day | Mon, Tue, Wed | Thursday |
The same relationship gives two different dates depending on the lag calendar. Concrete cures through the weekend, so a seven-day basis may be the more realistic model here. The point is to choose deliberately and record the choice.
Calendars vs related settings
- Calendar vs duration type. The calendar decides when working time falls. Duration type decides what happens to duration, units and resources when one of them changes.
- Calendar vs weather allowance. Weather can be modelled as nonworking calendar time or as a separate allowance. Each method shows delay differently, so the contract should drive the choice.
- Activity calendar vs resource calendar. In some tools a resource-dependent activity follows its resource’s calendar instead of its own. Check which applies before reading a date.
Why it matters
Calendars decide every date in the schedule, but they are among the least visible settings in it. A reviewer reading a Gantt chart sees bars, not the working-time rules beneath them. A holiday added in the wrong update can look like a slip of several days. A critical chain moved onto a six-day calendar can look like recovery when the real change is a commitment to Saturday work that someone has to staff and pay for. In delay analysis, calendar changes between updates are one of the first things an analyst checks, because they can move dates without any change in progress or logic. Contracts and owner specifications often say which calendars are allowed and require calendar changes to be explained in the update narrative.
What to compare between updates
Compare working hours, holidays, exception periods, and activity assignments. Record the reason for each change. Review which calendar governs relationship lag in the scheduling software; it may differ from the activity calendar.
Use working hours when comparing durations across calendars with different hours per day. A displayed “day” is not necessarily the same amount of work in every file or software configuration.
Common mistakes
- Adding nonworking time mid-project without explaining it, which can look like a delay or hide one.
- Mixed calendars on the critical path with nobody checking how float and the longest path respond.
- Holidays missing for the project’s actual location, or added for the wrong year.
- Seven-day calendars on labour activities to make a date work.
- Hours-per-day settings that differ between the calendar and the display, so a “day” is really 10 hours in one place and 8 in another.
See the construction schedule calendars guide, lags and leads, and the Schedule Forensics learning hub.
FAQ
What is a calendar in a construction schedule?
It is the set of working and nonworking time the scheduling software uses to turn a duration into start and finish dates. A calendar defines the workweek, working hours, holidays and other exceptions. Each activity is assigned a calendar, and its dates follow that calendar's working time.
Why does a 5-day activity take 7 calendar days?
Because durations count working time, not elapsed time. A five-day activity that starts on a Wednesday on a Monday-to-Friday calendar works Wednesday, Thursday and Friday, skips the weekend, and finishes on Tuesday, seven calendar days later. A holiday in that window adds another day.
How do multiple calendars affect float?
Float is measured in working time on a calendar, so activities on different calendars can show different float even when they finish on the same date. A chain on a five-day calendar feeding a milestone on a seven-day calendar can show float that isn't really usable. That's one reason the longest path can differ from the zero-float activities.
Which calendar is used for relationship lag?
It depends on the software and settings. Primavera P6 lets the scheduler choose the predecessor's calendar, the successor's calendar, a 24-hour calendar or the project default calendar for lag. A three-day cure lag on a five-day calendar can take longer in elapsed time than the same lag on a seven-day calendar.
Should weather days go in the calendar?
Contracts and owners handle it differently. Some expect anticipated bad-weather days as nonworking time in the calendar, others as a separate weather allowance or contingency activity. Follow the contract, keep the method the same across updates, and say which method the schedule uses.