"A poor reference planning? That's what the international standards say."

PMBOK, PRINCE2, AACE, DCMA, SCL… All major frameworks are unanimous: "A poorly designed baseline schedule can jeopardise an entire project."

In project management, the Master plan (or Baseline planning) is supposed to represent the formal commitment to deadlines. However, when it is poorly structured, unrealistic, or outdated, it becomes a Major risk factor.

And yet, in the reality on the ground, we still see too many baselines:

badly sequenced,
unrealistic,
unvalidated,
never updated.

The result? Unforeseen drifts, vague decisions, and sometimes... lost claims.

What the standards say

PMBOK (PMI) – The baseline is the measurement instrument

«The baseline schedule is used to measure deviations. Without initial reliability, no management is sustainable.»

It must be:

Realistic
Collaborative
Based on documented assumptions
Formally validated

PRINCE2 – The plan is a living product

«A schedule is not a static document; it is an evolving guide for the project.»

A fixed or theoretical plan quickly becomes an illusion. It must be:

Updated at each project stage
Connected to operational reality

DCMA 14-Point Assessment – Schedule Technical Review

«A reference schedule must meet strict criteria to be credible.»

Examples:

< 5% of illogical activities
No abuse of constraints or lags
Consistent margins
Clear critical path

Otherwise? Planning considered invalid.

AACE (RP 29R-03 & 37R-06) – Foundation of a serious schedule analysis

«Without a valid plan, no delay analysis can be considered reliable.»

Recommendations

Logically and contractually coherent planning
Version traceability
Full documentation of assumptions

SCL Protocol (Delay & Disruption) – The baseline, key to all claims

«An unrealistic or unmet baseline invalidates the legitimacy of a claim.»

In litigation, a weak plan becomes weak evidence. SCL recommends:

Logically linked, validated and updated schedules
Formally rebaselined baselines
A rigorous archive of versions

To put it plainly:

Poor reference planning is:

A loss of control
A diminished expectation
A legal vulnerability

And this, even if the rest of the project is well managed.

Best practices (common to all standards):

Co-construct the schedule with the business stakeholders
Formally validate with project management.
Regularly update (and track baselines)
Document all changes
Ensure technical quality (logic, constraints, margins…)

And you?

Have you ever encountered a poorly structured baseline schedule? How did you rectify the situation? What standards or practices do you follow?

Do you have any more questions?