Baselining a 25%-Design Schedule Under an Audit Mandate
A 14-month, $48M wastewater treatment upgrade is at 25% design. The owner's PMO mandates a fully resource-loaded CPM baseline with every activity detailed to 8-hour increments before notice to proceed, citing audit requirements. The PM knows MEP design will not be complete for four months, and the three-person planning team estimates the full build-out at 2,300 activities. The contract requires a baseline within 30 days of NTP and monthly updates. The contractor proposes a rolling-wave approach, but the owner calls it 'a lack of rigor.' Commissioning is fixed by a regulatory permit date.
1. How should the project manager respond to the mandate, and what scheduling approach should be adopted?
Read the worked answer
The PM should not frame this as rigor versus no rigor. Propose a written schedule development plan that defines the level of detail by design gate. At 25% design, a defensible baseline is a Level 3 schedule (roughly 600–800 activities) covering civil, structural, and procurement, with MEP represented by summary activities and milestones. Commit to adding MEP detail at 60% and 90% design under baseline change control. This satisfies the audit requirement because the plan states when detail will be added, who approves it, and how the baseline is updated. Explain that 2,300 activities built on 25% design would be largely assumed logic and would require wholesale rework within four months, destroying trendability. Offer a monthly schedule quality report to demonstrate control. A fixed commissioning permit date argues for a milestone-driven long-lead plan now, not false detail.
2. What planning artifacts should exist at baseline to protect schedule integrity?
Read the worked answer
Baseline artifacts should include: (1) a WBS and coding dictionary so activities roll up consistently; (2) calendar definitions for office, field, and 24-hour work, with a rule for float reporting; (3) a schedule basis memorandum recording assumptions, exclusions, and open scope; (4) an activity dictionary for driving and long-lead activities; (5) baseline change control procedures and re-baseline triggers; (6) progress measurement rules such as physical percent complete or units installed; (7) resource-loading assumptions if the schedule is to be resource-loaded; and (8) a milestone-level plan plus a detail-development register for undefined MEP scope. These artifacts make future detail additions predictable, controlled changes rather than unexplained rework, and they give the owner an audit trail tying the level of detail to design maturity.
3. What are the main risks of the owner's mandated approach, and how would you mitigate them?
Read the worked answer
Risks: a baseline built on assumed MEP logic will produce fictitious float and a critical path that migrates at every update; the team will spend update cycles fixing logic instead of analyzing performance; the owner will see repeated re-baselines and lose confidence; audit will find changes without documentation. Mitigations: define baseline by phase gate in the contract or a side letter; use a schedule quality checklist covering open ends, lags, constraints, and calendars each month; require change control for logic revisions; publish a trend log showing why float moved; and reserve full re-baseline only for scope changes. Also assign a dedicated scheduler to MEP detail development at 60% design so the transition is planned rather than reactive.