The real problem: understanding ≠ proving

A project can be delayed for dozens of reasons:

• late modifications
• Poorly managed interfaces
• Customer decisions
• External constraints

But within a contractual framework, that is not enough.

For a delay to legally “exist”, it must be demonstrated:

• the cause
• Responsibility
• the impact on the schedule

This is precisely the role of the Delay analysis :

Identify, quantify and assign delays with a structured methodology

Without this, the delay is invisible... even if it is real.

2. All delays are not equal

This is a major error on the projects.

A delay is only valuable if it impacts the critical path.

Simple example:

• Delay on a non-critical activity no contractual impact
• delay on the critical path Extension of time + potential cost

In practice:

• There are many delays.
• few are contractually valid

Delays are classified (critical, excusable, compensable, etc.), and each type has different consequences for claims.

Key conclusion:

80%: some delays are “unaccountable” because they are incorrectly scheduled.

3. The decisive factor: documentation

This is where it all comes down to it.

An undocumented delay is a non-existent delay.

Projects produce massive data:

• emails
• Reports
• Radio Frequency Interference
• amended plans
• site diaries

But without structure:

 impossible to:

• rebuild the timeline
• To prove causality
• demonstrate the impact

Or

solid documentation allows for the identification of events, quantification of their impact, and attribution of responsibilities

4. Delays are rarely an execution problem

It's counter-intuitive but fundamental.

In major projects:

• The teams are performing correctly overall
• schedules are drifting due to systemic factors

The common real causes:

• late client decisions
• Insufficient design maturity
• Vague contractual interfaces
• poorly integrated changes
• Poor float management

And above all:

Delays become a problem when they are not structured into the schedule.

5. The real issue: turning time into a contractual lever

A well-analysed delay allows:

• one Extension of Time (EOT)
• one penalty protection
• one Financial claim (extension, disruption, etc.)

The expert's role is clear:

To analyse events, assign responsibilities and quantify the impact to enable financial valuation.

6. Why 80% delays are “lost”

Because the projects:

❌ Do not structure their schedule
do not follow the critical path
❌ do not document correctly
❌ don't think “contractual”
Do not anticipate claims

Result:

• Delays exist
• but they are not neither proven nor defensible

7. ALVID positioning (high value)

That's exactly where the difference lies between:

❌ A classic planner

who follows progress

A strategic approach (ALVID)

→ which turns the schedule into a contractual asset

Conclusion — Time is a contractual capital

Projects do not waste time.
They are losing the ability to prove it.

The real gap is not operational.
It is analytical, contractual and strategic.