The real problem: understanding ≠ proving

A project can be delayed for dozens of reasons:

• late modifications
• poorly managed interfaces
• customer decisions
• external constraints

But in a contractual setting, that's not enough.

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

• the cause
• accountability
• the impact on the schedule

This is precisely the role of the delay analysis :

Identify, quantify, and attribute delays with a structured methodology

Without that, the delay is invisible... even if it's real.

Not all delays are equal.

This is a major mistake 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 critical path Extension of deadline + 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 takeaway:

80% of delays are “unquantifiable” because they are poorly positioned in the schedule.

3. The decisive factor: documentation

This is where it all happens.

An undocumented delay is a non-existent delay.

Projects produce massive data:

• emails
• Reports
• Radio Frequency Interference
• modified plans
• Site diaries

But without structure:

 impossible to:

• reconstruct the timeline
• prove causality
• demonstrate the impact

Or

Solid documentation allows for the identification of events, quantification of their impact, and assignment of responsibility.

4. Delays are rarely an execution problem.

It's counterintuitive but fundamental.

In large projects:

• the teams are performing globally correctly
• The schedules are slipping 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:

Delay becomes a problem when it's not factored into the schedule.

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

A well-analyzed delay allows for:

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

The expert's role is clear:

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

6. Why 80% of 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”
Don't anticipate claims

Result:

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

7. ALVID's (High Value) Positioning

That's exactly where the difference lies between:

❌ A classic planner

→ who follows progress

✅ A Strategic Approach (ALVID)

which transforms the schedule into a contractual asset

Conclusion — Time is a contractual capital

Projects don't waste time.
They lose the ability to prove it.

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