Tower C — Commercial Tower & Podium

Contents

01 Delay summary

Completion has moved from 1 November 2027 to 19 November 2027 — a net critical slip of 18 days against the approved baseline. Three distinct delay events lie on or join the critical path this period.

Float is no longer available to absorb the next event

Holding the position at +18 days consumed effectively all of the remaining path float. Seventeen activities now sit in negative float where the baseline had none. The practical consequence is that the next disruption of any size lands directly on the completion date, because there is nothing left between it and completion.

02 How the finish date moved

The bridge from the baseline finish to the current forecast, in critical-path calendar days. Each bar is a movement that reached the completion date; movements absorbed by float do not appear here and are listed in Appendix A.

Figure 1 — Baseline finish to current forecast

Why the arithmetic does not simply add up

+18 and +12 against −18 would give +12, not the +18 observed. The residual six days arise where the two delay events overlap: during the concurrency the recovery cannot be applied twice, so acceleration bought back calendar time on only one of the two paths. This is the normal behaviour of a network under concurrent delay and it is why the movement must be taken from the recalculated critical path rather than from a sum of event durations.

03 What changed in the critical path

The driving path to completion is not the same chain it was at baseline. One activity has entered it and the sequence beyond that point has re-ordered.

R10 baseline path

R12 current path

The re-ordering matters for management as much as for measurement: mitigation aimed at the baseline critical path would now be aimed at the wrong activities. Any acceleration proposed from here should be tested against the R12 path, not the approved one.

04 Basis, matching and limitations

This report compares two Primavera P6 files activity by activity. Everything in it derives from that comparison; nothing is asserted from outside the two files.

What was compared

• Baseline. R10, approved 30 November 2025, forecast finish 1 November 2027.
• Update. R12, data date 28 February 2026, forecast finish 19 November 2027.
• Matching. By activity ID. 2,970 of 3,842 activities matched; the remainder are additions, deletions or re-identified activities and are listed in Appendix C.
• Movement is measured on the recalculated driving path, not as a sum of activity variances.

Limitations

• An activity that was renumbered between revisions cannot be matched and appears as one deletion plus one addition. Appendix C flags likely renumbering by name similarity, but the pairing is not asserted.
• Cause attribution reflects what the programme shows and what was declared in the submission. Where nothing was declared, the register says so rather than inferring intent.
• Risk allocation shown here is the factual position — whose scope the activity sits in. It is not a contractual determination; the Claim Brief performs that analysis.

A Variance register — activities that moved

Every matched activity whose dates changed by more than two days, ordered by impact on completion. “Critical” indicates the activity lies on the R12 driving path.

Activity	Description	Baseline finish	Current finish	Var	Float	Crit
A1422	Erect columns Grid G, L4–6	14 Jul 27	1 Aug 27	+18d	−18d	Yes
A1733	Level 3 pre-pour inspection	02 Aug 27	14 Aug 27	+12d	−12d	Yes
A1801	MEP rough-in Zone A	18 Aug 27	24 Aug 27	+6d	−6d	Yes
A1560	Metal deck & concrete L4–6	28 Jul 27	30 Jul 27	+2d	4d	No
A2110	Curtain wall North — accelerated	22 Sep 27	10 Sep 27	−12d	0d	Yes
A1390	Steel delivery release 2 — extra shift	28 Jun 27	22 Jun 27	−6d	0d	Yes
A2240	Core handover	01 Nov 27	19 Nov 27	+18d	−18d	Yes
Net movement of the driving path to completion				+18d

Movements absorbed by float

Fourteen further activities moved by more than two days without affecting completion. Together they account for the difference between 36 days of gross event duration and 18 days of net movement.

Range	Activities	Total movement	Effect on completion
Moved, float remaining	11	+31d	None — absorbed
Moved, float exhausted	3	+9d	Partial — see Appendix B

B Critical-path change, activity by activity

The driving path in each revision, in sequence. Activities present in one path only are the structural change; activities present in both may still have moved.

Seq	R10 baseline path	R12 current path	Change
1	A1390 Steel delivery	A1390 Steel delivery	−6d
2	A1422 Grid G columns	A1422 Grid G columns	+18d
3	A1560 Deck L4–6	A1733 Pre-pour hold	Replaced
4	A1801 MEP rough-in	A1801 MEP rough-in	+6d
5	A2240 Core handover	A2240 Core handover	Shifted

Float profile, baseline versus current

Float band	R10 baseline	R12 current	Change
Negative float	0	17	+17
Zero float (critical)	42	58	+16
1 – 20 days	311	402	+91
Over 20 days	2,617	2,493	−124

The whole distribution has shifted left. This is the numeric form of the finding in section 1: the programme has less room than it had, everywhere, not only on the driving path.

C Matching basis, unmatched activities and provenance

Comparison is by activity ID. An activity present in one revision only cannot be varianced, and is reported here rather than silently excluded.

Category	Count	Treatment in this report
Matched on activity ID	2,970	Varianced — Appendix A
Added in R12	604	No baseline to compare; listed below where critical
Removed since R10	211	Reported as scope change, not as variance
Likely renumbered	57	Flagged by name similarity; pairing not asserted
Total activities in R12	3,842

Added activities on or near the driving path

Activity	Description	Duration	Float
A1733	Level 3 pre-pour inspection — added R11	12d	−12d
A2115	Curtain wall acceleration works — added R12	18d	0d

Both additions are consequences of events described in section 2 rather than scope growth. A1733 formalises a hold that was previously untracked; A2115 is the declared acceleration.