Commercial & Planning

Planning

Milestones, baseline against actual and the critical path — feeding straight into delay analysis.

Overview

Milestones, baseline vs actual, EOT

Planning tracks milestones, compares baseline against actual and maintains the critical path as the project moves.

It integrates with delay analysis so that extension of time submissions are substantiated from live project records rather than reconstructed months later from whatever anyone happened to keep.

Most EOT claims fail on evidence rather than merit. The delay was real, the entitlement was arguable, but the contemporaneous record does not support it because nobody was building that record while the delay was happening. A platform where the registers, correspondence and progress data are already linked changes what is possible when the claim is eventually prepared.

  • Milestones
  • Baseline vs actual
  • Critical path
  • EOT substantiation
MilestonesBaseline vs actualCritical pathEOT substantiation
Planning
PlanningMilestones, baseline vs actual, EOT

How it works

How delay is substantiated

Baseline captured

The accepted programme is held as the reference point, with revisions tracked.

Actual progress recorded

Progress comes from site records — installation dates, manhours, inspections — rather than from an estimate typed into a cell.

Variance surfaced continuously

Slippage against baseline is visible as it emerges, not at the next formal update.

Events linked to entitlement

Instructions, variations, late information and correspondence link to the activities they affected.

Why it matters

On a live project

EOT built from live records

Substantiation comes from the registers as they were maintained, not from a retrospective exercise.

Slippage visible early

Variance against baseline is continuous, so the programme conversation happens before the delay is locked in.

Critical path stays current

Changes flow through to the path rather than waiting for the next formal update.

Use cases

Where it is used

Extension of time claims

Substantiation built from the contemporaneous record.

Programme review

Weekly variance by area rather than a monthly percentage for the whole project.

Forecasting

Completion forecasts grounded in actual productivity rather than optimism.

Questions

Frequently asked about Planning

No. It works alongside your planning tool, holding the baseline and actual data and linking events to activities. Integration with P6 and Project is scoped during implementation.

The platform holds the contemporaneous record needed for the common methods, including as-planned versus as-built and time impact analysis. The analysis itself remains the planner's judgement.

Yes, events link to activities so their programme consequence is visible rather than argued.

Planners and commercial teams primarily, with project directors using the variance view.

See Planning on your project

Take the next step and empower your projects with Fortis Sync.