"A bad reference schedule? That's what international standards say."

PMBOK, PRINCE2, AACE, DCMA, SCL... All the major reference systems agree: "A poorly designed reference schedule can jeopardize an entire project."

In project management, the reference planning (or Baseline planning) is supposed to represent the formal commitment to deadlines. But when it is poorly structured, unrealistic or obsolete, it becomes a major risk factor.

However, in the real world, we still see too many baselines:

poorly sequenced,
unrealistic,
not validated,
or never updated.

The result? Unanticipated drift, unclear decisions, and sometimes... lost claims.

What the standards say:

PMBOK (PMI) - The baseline is the measuring instrument

«The reference schedule is used to measure deviations. Without initial reliability, there's no steering.»

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's an evolving guide to the project.»

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

Updated at every stage of the project
Connected to operational reality

DCMA 14-Point Assessment - Technical planning control

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

Examples:

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

If not? Planning considered invalid.

AACE (RP 29R-03 & 37R-06) - Basis for a serious delay analysis

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

Recommendations:

Logically and contractually consistent planning
Version traceability
Full documentation of assumptions

SCL Protocol (Delay & Disruption) - The baseline, the key to any claim

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

In litigation, weak planning is weak evidence. SCL recommends :

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

In plain English:

Poor reference planning means :

A loss of control
Downgraded anticipation
A fragile legal framework

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 players
Formally validate with project management
Update regularly (and track baselines)
Document all changes
Ensure technical quality (logic, constraints, margins, etc.)

What about you?

Have you ever had to deal with a poorly structured reference schedule? How did you rectify the situation? What standards or practices do you follow?