Capability
Critical Path Analysis
Show what is actually driving completion this period, what has float, and which near-critical paths are about to take over.
C02 — The problem
The technical problem
Teams often treat the red bar on last month’s print as ‘the critical path’. Constraints, out-of-sequence progress, and unstatused logic make that print a poor guide to what will actually move completion.
Critical Path Analysis is a period assignment: recalculate from current remaining duration, explain the driving path in delivery language, and show near-critical work that will take over if a few days are lost. It is not recovery scheduling and not a delay-analysis opinion for a claim.
C03 — Engagement
When this capability is needed
-
01
Period update
Leadership needs to know what is driving completion now.
-
02
Steering review
Dates moved and the pack does not say why.
-
03
Before recovery
You cannot recover a path you have not identified.
-
04
Interface pressure
Several packages claim to be critical and only one can be.
C04 — Scope / method
How the work is approached
Analysis of the current programme: driving path, total and free float, near-critical paths, and the effect of out-of-sequence or constrained logic. Does not produce a delay opinion or a recovered programme unless separately scoped.
-
01
Take the live file
Data date, remaining duration, and actuals as they stand.
-
02
Clean calculation issues
Identify constraints and out-of-sequence progress that distort the path.
-
03
Extract driving and near-critical paths
Completion and intermediate contractual dates.
-
04
Write the narrative
What is driving, what has float, what changed since last period.
-
05
Flag control actions
Activities that need management attention this cycle — not a recovery optioneering study.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Critical-path narrative | Driving logic in delivery language. |
| Driving-activity set | The activities currently on the path to the dates that matter. |
| Near-critical watchlist | Paths within a defined float threshold. |
| Calculation notes | Constraints and out-of-sequence items that affect the result. |
C06 — Decision value
What this work is used to decide
Where to apply management attention this period, and whether the reported completion date is being driven by real remaining work or by modelling artefacts. It does not decide a recovery scheme.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
This is not Time Impact Analysis or an extension-of-time opinion. Those are claims assignments that may use this period’s path as a starting fact.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.