Plan Schedule Management Before Building the Schedule
By month four, most schedule disputes have stopped being about dates. Somebody reports an activity at ninety per cent and somebody else says it has not started, because one of them means the build is written and the other means the service has been accepted. A supplier's plan and a client's plan disagree by nine days and both are correct, because they are counting different working weeks. A milestone moves and nobody can say who authorised it. Each of those is the consequence of a rule that was never settled before anyone opened the planning tool.
Planning how the schedule will be managed is a short piece of work that happens once. Section 2.3.2 of the PMBOK® Guide Eighth Edition describes it as a process in its own right, and the practical reason is that every one of these decisions is cheap while the plan is still blank and expensive once numbers depend on it.
Rules that have to exist before the first date
Five decisions carry most of the weight, and each of them is the subject of an argument somewhere on a project right now.
The units and the calendars. Whether duration is expressed in working days, elapsed days or hours, whose working week applies, which public holidays the plan observes, and what happens where a supplier works five days and the site runs seven. On international delivery this extends to time zones, which sound trivial until a cutover window straddles midnight in one of them.
The level of detail. How far the schedule decomposes, and how far ahead it is detailed. A plan that details month eighteen to the half-day is describing work nobody has thought about properly, and the detail will be wrong in a way that looks authoritative.
What complete means for an activity. Pick the definition and apply it everywhere: an activity is done when its deliverable has been accepted by a named party, or when the work has been performed, or when a gate has been passed. Mixed definitions inside one plan make the roll-up meaningless, and the mixing is almost never deliberate.
How progress is measured. Whether an activity in flight reports an estimate of percentage, a fixed rule such as nothing until it is finished, or physical measures such as rooms commissioned or records migrated. Physical measures are harder to argue with, which is exactly why they meet resistance.
Who owns the dates and who may change them. A named owner per section of the plan, a threshold above which a change goes to change control, and a rule about what may be reflowed quietly. Without this, the plan drifts through small adjustments nobody decided on, and the baseline stops meaning anything.
Why the writing down matters
The cost asymmetry is the whole argument. Settling these in planning costs an hour with the people who care, and the discussion is abstract, which makes it easy. Settling the same questions in month four means agreeing a rule while one party is already disadvantaged by it, which makes it a negotiation with a commercial edge.
There is also a credibility effect that is easy to underestimate. A project manager who can say what the reporting rule is, and point at where it was agreed, holds a different position in a steering group than one improvising a definition under pressure. The second is how a schedule stops being believed.
Nine days that nobody had lost
A managed service provider took over the infrastructure support for a manufacturer during a factory expansion. The transition plan showed the migration completing on a Friday, thirty working days after the start. The manufacturer's programme showed it completing the following Wednesday and had the production trial booked accordingly.
Both plans were right. The provider's scheduling tool ran a five-day calendar with English public holidays. The site ran a continental shift pattern across six days with a different holiday set, and the manufacturer's planner had built the dependent activities on that basis. Nobody had asked which calendar governed the joint plan, because a calendar is a setting rather than a decision, and settings do not get raised at a kick-off meeting.
The gap surfaced when the trial date was confirmed to the customer. Reconciling the two plans took most of a week and cost a booked engineering window that could not be moved. The rule that would have prevented it fits in a sentence: the joint plan runs on the site calendar, and the provider converts its own durations into it. Working out which of these decisions a particular delivery genuinely needs, and which are overhead, is schedule planning of the kind Omega's PMP® Exam Preparation works through.
How much of this to write down
On a small internal project the answer is a page, or half of one. The definition of complete, the reporting rhythm, the owner of the plan and the threshold for change control will cover almost everything that later goes wrong. Anything longer will not be read by the people whose behaviour it is meant to govern.
On multi-party or contracted delivery the answer is longer, because the rules have to survive disagreement between organisations that are not on the same side. Calendars, units, the measurement of progress and the change route all belong in writing, agreed by name, before the first joint plan is issued. The document is doing the same job a specification does: it removes the space in which two reasonable parties can both be right.
For a PMP® candidate, a schedule complaint in a scenario is best treated as a question about rules. Where a description mentions conflicting progress reports, a milestone that moved without a decision, or two plans that disagree, the missing element is usually an agreement made at planning, and the response that addresses the cause is not a faster replan.
In practice this is one meeting. Take the five decisions above to whoever will be reporting against the plan, agree each one out loud, write the answers on a single page and attach it to the schedule. The next dispute about a date will be settled in ten minutes by pointing at it.
Interested in going further?
Knowing which scheduling rules a delivery genuinely needs, and being able to defend them in a room where two organisations want different answers, is a practical skill with commercial consequences. Omega's PMP® Exam Preparation works through schedule planning, development and control as a connected sequence.
The PMBOK® Guide Eighth Edition sets out how schedule planning connects to the development and control that follow it.
Ad · Amazon affiliate link.
References
A110: The PMBOK 8 Schedule Performance Domain: What It Really Covers
A111: Dates Are Not a Schedule
A112: Critical Path Explained Without the Mystique
A113: Float Explained: How Much Delay Can You Really Absorb?
A114: Milestones vs Activities: Stop Treating Them as the Same Thing
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
