On this page
A duration describes work. A calendar describes when that work can happen. You need both before a finish date means anything. This distinction matters whenever a team compares schedules, adds weekend work or discusses a delay in “days.”
Follow the same activity across two calendars
Imagine a fictional installation needing 40 working hours, beginning Thursday at the start of an eight-hour shift. There are no holidays, interruptions or predecessor restrictions in this example.
| Calendar | Work happens on | Finish |
|---|---|---|
| Monday–Friday, eight hours daily | Thursday, Friday, Monday, Tuesday, Wednesday | End of Wednesday |
| Every day, eight hours daily | Thursday through Monday | End of Monday |
| Monday–Friday, Monday is a holiday | Thursday, Friday, Tuesday, Wednesday, Thursday | End of Thursday |
The work content is unchanged. The finish moves because the available working time changes. Record the start time and finish boundary when reproducing an example; counting inclusive dates can otherwise introduce an extra day.
- 01Inspect the fileDates, logic, calendars
- 02Read the contractEdition, clause, exceptions
- 03Check the fieldSequence, access, resources
- 04Record the decisionOwner, evidence, next action
Review more than the calendar name
“Standard” is a label, not evidence. Inspect the weekly pattern, shift start and finish times, holidays, shutdowns and working exceptions. Check which activities use each calendar and whether a resource assignment changes the scheduling behavior.
Keep displayed duration units distinct from working shifts. A stored duration in hours can be displayed as days using a conversion setting. A ten-hour workday and an eight-hour display conversion need careful explanation rather than a quick assumption that one is corrupted. Oracle documents the relevant time-period setting in its P6 scheduling settings help.
Treat a changed calendar as a changed plan
If an update adds Saturday work, ask who has approved the crew, access, inspection coverage and delivery support. The calendar may make a forecast mathematically earlier while the site still operates five days a week.
A useful change record says which calendar changed, which activities it affects, the reason, the approval and the date the new pattern becomes available. Recalculate a controlled copy and compare milestone movement. Check whether another path becomes controlling after the change.
Questions for the next schedule meeting
- Are durations and reported delay movements expressed in working hours, working days or elapsed calendar days?
- Which calendar governs each reported number?
- Are seasonal restrictions, shutdowns and approved overtime represented?
- Did any calendar assignment change since the previous update?
- Does the relationship-lag calendar match the intended waiting period?
Keep these answers with the schedule narrative. They make a later comparison understandable without asking the original scheduler to reconstruct the assumptions from memory.
Continue with lags and leads, recovery schedules, or the Schedule Forensics learning paths.
Share this article