Full activity listings and the complete delay register are in
the accompanying Excel appendix.
Disclosures
Analytical tool output — not expert determination
This report is automatically generated from the uploaded schedule file(s). It is an analytical aid — not an expert determination, legal advice, or a certified forensic delay analysis.
Float and criticality are the source scheduling tool's own, as recorded in the file. The tool runs its own calendar-aware critical-path pass to fill a gap where the source recorded no float on incomplete work, and to measure change between two schedules. That pass is an analytical recompute, not a substitute for re-scheduling in P6 or MS Project: it does not level resources, force Expected Finish or imposed-finish dates, or work at sub-day precision. It cannot determine contractual excusability.
Figures should be reviewed by a qualified delay analyst before being relied upon in formal contract correspondence or dispute proceedings. Nothing in this report should be construed as a legal opinion or expert witness statement.
No concurrent delay detected (Society of Construction Law Delay and Disruption Protocol, 2nd Edition (2017) methodology)
No concurrent delay periods were detected in this comparison, so the concurrency methodology did not affect the engine-attributed delay figure. The Society of Construction Law Delay and Disruption Protocol, 2nd Edition (2017) methodology would have governed how any overlapping critical delays net. An alternative methodology (Malmaison 'first in time' approach (Henry Boot v Malmaison [1999] 70 ConLR 32)) is available; with no concurrent periods here it would give the same figure, but the choice can matter on updates where critical delays overlap.
Brief
For the project directorSeverity-coded status headlines, top risks, what to act on.
01
Executive Summary
The programme finish moved 21 calendar days (15 working days) later, driven by duration increases to piling rig mobilisation, bulk excavation, and pile integrity testing, alongside a logic change to slab formwork. These critical events are concentrated within the early substructure and piling phases, indicating that the delay is not spread across the entire project but is anchored in specific foundational activities. The schedule quality remains acceptable with a DCMA score of B, although the presence of 13 relationships with positive lag warrants review to ensure the logic accurately reflects construction sequencing. The detailed breakdown of these critical events and their individual impacts is provided in the decomposition panel below.
Completion movement:+21 calendar days+15 working days on the project's default calendar. The only delay figure is the completion movement; the panel below splits it into activity-level drivers and topology signals — diagnostics, not competing delay totals.
The programme finish moved 21 calendar days later, representing a completion movement of 15 working days. The "Why" section presents a per-category breakdown of activity-level drivers, including duration changes and added scope, which serve as a churn and structural signal of where movement arose rather than a summed project delay total. Each activity is measured on its own, meaning parallel paths and float-absorbed slip are recorded here without adding to the finish movement. The "Where to investigate" section identifies topology edits, such as logic changes in the Superstructure package, as direction-of-travel signals indicating where the schedule was rewired between baseline and update. These edits are not sized in isolated working days, as that would require a calendar-aware CPM pass per event, but they indicate where pressure built up for further review.
The drivers and topology signals below are diagnostics, each measured on its own: they are not expected to sum to the completion movement. See Methodology (§27).
Quantified drivers (working days by category)
Category
Events
Working days
Duration changes
4
18 working days
Added scope (upper bound)
1
14 working days
Top 1 WBS packages for topology edits
WBS package
Events
Logic
Constraint
Calendar
Superstructure
1
1
0
0
04
Key Milestones
Milestones compared:4Baseline vs current forecast finish for every milestone on both schedules; variance in calendar days.
Showing 3 of 4 compared milestones, largest slip first; all are in “Key Milestones — full comparison table”.
05
What to do next
7 questions for the programme's author, 4 critical. In §20: 3 to clarify.
Check your own records first. Each may already answer a question below.
Your progress records, NCRs and resourcing for the activities named (Critical 1, Critical 2, Critical 3)
The update's report of revisions and their reasons (SCL Protocol §1.59), if one was supplied (Critical 4)
Critical questions
Critical 1. SUB-210 Piling rig mobilisation has grown from 4 to 10 working days on the critical path, adding 6 working days to completion on its own. What caused it, and how will the time be recovered? (§22)
Critical 2. SUB-110 Bulk excavation Zone A has grown from 12 to 17 working days on the critical path, adding 5 working days to completion on its own. What caused it, and how will the time be recovered? (§22)
Critical 3. SUB-240 Pile integrity testing has grown from 6 to 10 working days on the critical path, adding 4 working days to completion on its own. What caused it, and how will the time be recovered? (§22)
Critical 4. None of these 3 changes names a cause outside your control. Is any of this time attributed to such a cause? If so, which event, and when was it notified? (§22)
Narrative
For the planner or delay analystSupporting analysis, schedule comparison, driving-path detail.
06
Period hit rate (CEI)
Forecast finishes that happened:10 of 10 finished60-day period; 3 of 3 flagged critical
Of the 10 activities the baseline (data date 5 Jan 2026) forecast to finish before 6 Mar 2026, 10 had finished by the update, over 60 days; 3 of the 3 it flagged critical did. Shown as a count: fewer than 30 activities were forecast in this period.
Starts: of the 12 activities it forecast to start in the period, 12 had started.
07
Float-path risk
Near-critical paths:8sub-critical or parallel-critical, within 20 working days of the controlling path.
Where else forward risk sits: alternative chains to the project end within 20 working days of the critical path. See Methodology (§27).
8 sub-critical paths within 20 working days of critical — a delay on any of them could shift the controlling path. Rank 1 in the table below is the primary critical path for reference.
Top 3 float paths
#
Float
Activities
Envelope
Driving activity
Branches from
1
0 wd
69
2026-03-02 → 2028-07-03
PRE-140 — Building control approval
—
2
7 wd
69 (1 unique)
2026-03-06 → 2028-07-03
PRE-250 — Site security and CCTV
Path 1 at SUB-110
3
7 wd
35 (8 unique)
2026-10-26 → 2028-07-03
MEP-110 — Main intake and switchgear
Path 1 at FIT-110
Top 3 of 9 paths shown (the primary driving path plus 8 near-critical) — the full 5-path table and the float-path overlay chart are in Float paths — detail; every path is in the Excel appendix.
08
Float consumption
Float consumed:3 wd median9 activities eroding float since the baseline
Which near-critical chains are burning float: an early warning before a path goes critical. Float lost is the median drop, not the sum. See Methodology (§27).
9 activities eroded float since the baseline, a median of 3 working days each (27 working days in aggregate). The median is the typical per-activity erosion; the aggregate runs far larger on a broad schedule and shouldn't be read as the delay to completion. The most-eroded near-critical path is rank 3 (driving activity MEP-110 — Main intake and switchgear), down 3 wd and now at 7 working days of float.
Most-eroded near-critical paths (top 1)
#
Float now
Float lost (typical)
Activities eroding
Driving activity
3
7 wd
3 wd
8/35
MEP-110 — Main intake and switchgear
09
Completion forecast (Earned Schedule)
Earned Schedule finish:2028-06-06Earned Schedule at the pace to date (SPIt 1.01), measured against SL-DEMO. Programme finish: 2028-07-03.
Measured against your approved baseline (SL-DEMO, finishing 2028-06-12), the work done by the data date (2026-03-06) was planned to be done by 2026-03-06: on the baseline. That is a schedule performance index (SPIt) of 1.01. At that pace the baseline's planned duration (889 days from 2026-01-05) runs to 2028-06-06. Earned Schedule measures the rate of work (PMI Standard for EVM, 2019, §4.4); it is not a reschedule. The programme's own finish is 2028-07-03. Work is weighted by the baseline's original durations.
Completion forecast
Basis
Finish
vs programme
Programme finish
your programme
2028-07-03
—
Earned Schedule, pace to date
SPIt 1.01
2028-06-06
-27 days vs programme
To finish by the programme's own date (2028-07-03), the remaining 829 days of baseline work must be done in 850 days: a required pace (TSPIed) of 0.97 days of baseline work per day, against 1.01 achieved so far (SPIt). The required pace is within 0.10 of the pace achieved, which NDIA reads as in line with performance to date (NDIA Predictive Measures Guide, 2025, §2.6.2).
10
Critical path
Activities driving the completion date in each schedule version, as flagged critical in the source programme for each schedule.
Where the critical path has shifted between the baseline and the update, the shift itself is often the single most important finding — it signals that delay or acceleration in one area has re-routed the critical chain through previously non-critical work.
Critical-path activities with largest baseline-vs-update variance
A diagnostic view, not the full critical path. The 15 critical-in-either activities with the largest finish variance are plotted here — the chart surfaces what moved between baseline and update, selected by a priority rule (see Methodology (§27)): persisted by float severity, then variance, then joined, then left. For the end-to-end critical chain from data date to project finish see Critical path — supporting views (WBS rollup, network diagram, timeline) and the Schedule comparison table.
Each activity appears as two bars: dashed outline for the baseline plan, filled bar for the update. Fill colour encodes membership change — red for persisted on the critical path, teal for joined, grey for left.
11
Schedule comparison
Side-by-side comparison of the baseline and the update (SL-DEMO (data date 2026-03-06)) activity dates.
“Baseline” here means SL-DEMO (data date 2026-01-05), selected as your approved baseline. All dates are each schedule’s current forecast finish (see Methodology (§27), Date basis).
Start and finish variances are shown in calendar days — positive values mean the update is later than the baseline.
The delay register and concurrent-delay analysis in the sections below derive from these variances.
Baseline vs update Gantt overlay
Each activity appears twice: a dashed outline bar for the baseline plan above a filled bar for the update plan. Critical-path activities are shown in red. Rows are sorted by criticality and finish variance — the activities whose dates moved most appear first.
Baseline vs update (critical path)
ID
Name
Baseline start
Baseline finish
Update start
Update finish
Start Δ
Finish Δ
Status
Critical (baseline)
Critical (update)
SUB-250
Pile trimming
2026-06-16
2026-06-25
2026-07-07
2026-07-16
+21d
+21d
not started
✓
✓
SUB-310
Pile cap excavation
2026-06-26
2026-07-07
2026-07-17
2026-07-28
+21d
+21d
not started
✓
✓
SUB-320
Pile cap reinforcement
2026-07-08
2026-07-21
2026-07-29
2026-08-11
+21d
+21d
not started
✓
✓
SUB-330
Pile cap concrete pour
2026-07-22
2026-07-29
2026-08-12
2026-08-19
+21d
+21d
not started
✓
✓
SUB-340
Ground beam install
2026-07-30
2026-08-14
2026-08-20
2026-09-07
+21d
+24d
not started
✓
✓
SUB-410
Basement slab formwork
2026-08-17
2026-08-26
2026-09-08
2026-09-17
+22d
+22d
not started
✓
✓
SUB-420
Basement slab reinforcement
2026-08-27
2026-09-14
2026-09-18
2026-10-05
+22d
+21d
not started
✓
✓
SUB-430
Basement slab waterproofing
2026-09-15
2026-09-22
2026-10-06
2026-10-13
+21d
+21d
not started
✓
✓
SUB-440
Basement slab pour
2026-09-23
2026-10-02
2026-10-14
2026-10-23
+21d
+21d
not started
✓
✓
MS-SUB-END
Substructure complete
2026-10-05
2026-10-05
2026-10-26
2026-10-26
+21d
+21d
not started
✓
✓
SUP-360
Slab L2 pour
2026-12-04
2026-12-11
2026-12-29
2027-01-06
+25d
+26d
not started
✓
✓
SUP-410
Slab L3 formwork
2026-12-14
2026-12-23
2027-01-07
2027-01-18
+24d
+26d
not started
✓
✓
SUP-420
Slab L3 reinforcement
2026-12-24
2027-01-07
2027-01-19
2027-01-28
+26d
+21d
not started
✓
✓
SUP-520
Roof slab reinforcement
2027-03-03
2027-03-12
2027-03-24
2027-04-06
+21d
+25d
not started
✓
✓
SUP-530
Roof slab pour
2027-03-15
2027-03-22
2027-04-07
2027-04-14
+23d
+23d
not started
✓
✓
ENV-140
Curtain wall install North elevation
2027-03-23
2027-04-14
2027-04-15
2027-05-06
+23d
+22d
not started
✓
✓
ENV-150
Curtain wall install East elevation
2027-04-15
2027-05-06
2027-05-07
2027-05-27
+22d
+21d
not started
✓
✓
ENV-160
Curtain wall install South elevation
2027-05-07
2027-05-27
2027-05-28
2027-06-17
+21d
+21d
not started
✓
✓
ENV-170
Curtain wall install West elevation
2027-05-28
2027-06-17
2027-06-18
2027-07-08
+21d
+21d
not started
✓
✓
ENV-320
Window install upper floors
2027-06-18
2027-07-05
2027-07-09
2027-07-26
+21d
+21d
not started
✓
✓
ENV-330
Window install lower floors
2027-07-06
2027-07-21
2027-07-27
2027-08-11
+21d
+21d
not started
✓
✓
ENV-340
Glazing and seals
2027-07-22
2027-08-02
2027-08-12
2027-08-23
+21d
+21d
not started
✓
✓
MS-ENV-END
Envelope watertight
2027-08-03
2027-08-03
2027-08-24
2027-08-24
+21d
+21d
not started
✓
✓
FIT-110
Stud partition L1
2027-08-03
2027-08-18
2027-08-24
2027-09-09
+21d
+22d
not started
✓
✓
FIT-120
Stud partition L2
2027-08-09
2027-08-24
2027-08-31
2027-09-15
+22d
+22d
not started
✓
✓
FIT-130
Stud partition L3
2027-08-13
2027-08-31
2027-09-06
2027-09-21
+24d
+21d
not started
✓
✓
FIT-140
Stud partition L4
2027-08-19
2027-09-06
2027-09-10
2027-09-27
+22d
+21d
not started
✓
✓
FIT-150
Stud partition L5-L6
2027-08-25
2027-09-20
2027-09-16
2027-10-11
+22d
+21d
not started
✓
✓
FIT-160
Suspended ceilings L1-L3
2027-08-25
2027-09-29
2027-09-16
2027-10-20
+22d
+21d
not started
✓
✓
FIT-170
Suspended ceilings L4-L6
2027-09-30
2027-11-03
2027-10-21
2027-11-24
+21d
+21d
not started
✓
✓
FIT-180
Ceiling integration MEP
2027-10-11
2027-10-26
2027-11-01
2027-11-16
+21d
+21d
not started
✓
✓
FIT-210
Plastering L1-L3
2027-10-11
2027-11-05
2027-11-01
2027-11-26
+21d
+21d
not started
✓
✓
FIT-220
Plastering L4-L6
2027-11-08
2027-12-03
2027-11-29
2027-12-24
+21d
+21d
not started
✓
✓
FIT-240
Painting L4-L6
2027-12-06
2027-12-31
2027-12-29
2028-01-21
+23d
+21d
not started
✓
✓
FIT-260
Floor finishes L4-L6
2028-01-03
2028-02-01
2028-01-24
2028-02-22
+21d
+21d
not started
✓
✓
FIT-310
Reception joinery
2028-01-11
2028-01-31
2028-02-01
2028-02-21
+21d
+21d
not started
✓
✓
FIT-320
Toilet vanity install
2028-01-11
2028-02-03
2028-02-01
2028-02-24
+21d
+21d
not started
✓
✓
FIT-330
Tea-point joinery
2028-01-18
2028-02-02
2028-02-08
2028-02-23
+21d
+21d
not started
✓
✓
FIT-340
Meeting room joinery
2028-02-03
2028-02-28
2028-02-24
2028-03-20
+21d
+21d
not started
✓
✓
FIT-350
Built-in storage and fittings
2028-02-29
2028-03-20
2028-03-21
2028-04-10
+21d
+21d
not started
✓
✓
FIT-360
Final joinery snagging
2028-03-21
2028-03-30
2028-04-11
2028-04-20
+21d
+21d
not started
✓
✓
MS-FIT-END
Fit-out complete
2028-03-31
2028-03-31
2028-04-21
2028-04-21
+21d
+21d
not started
✓
✓
CMS-210
Client walkthrough and snag list
2028-03-31
2028-04-06
2028-04-21
2028-04-27
+21d
+21d
not started
✓
✓
CMS-220
Major snags rectification
2028-04-07
2028-04-27
2028-04-28
2028-05-18
+21d
+21d
not started
✓
✓
CMS-230
Minor snags rectification
2028-04-28
2028-05-15
2028-05-19
2028-06-05
+21d
+21d
not started
✓
✓
CMS-240
Final inspection
2028-05-16
2028-05-19
2028-06-06
2028-06-09
+21d
+21d
not started
✓
✓
CMS-310
Building handover documentation
2028-05-22
2028-05-31
2028-06-12
2028-06-21
+21d
+21d
not started
✓
✓
CMS-320
O&M manuals issued
2028-06-01
2028-06-06
2028-06-22
2028-06-27
+21d
+21d
not started
✓
✓
CMS-330
Soft landings start
2028-06-07
2028-06-09
2028-06-28
2028-06-30
+21d
+21d
not started
✓
✓
MS-PC
Practical Completion
2028-06-12
2028-06-12
2028-07-03
2028-07-03
+21d
+21d
not started
✓
✓
Showing the top 50 most-moved critical-path activities of 73 critical and 148 total matched. Selected by absolute start+finish variance, then re-sorted chronologically. Full matched-activity list in the Matched Activities sheet of the Excel appendix.
12
Critical path — supporting views
Structural views behind the Brief-layer critical-path overlay: the update's critical chain rolled up to WBS level, the dependencies between critical clusters, and the update timeline on the project calendar.
Critical path rollup — WBS summary bars
Summary-bar view of the update's critical path — one bar per WBS cluster that contains stored-critical activities. Near-critical clusters (1–20 wd float, the schedule's status-cycle threshold) are shown alongside in amber so the reader can see which clusters are one slip from the critical path.
Critical path sequence — the driving chain in order
The update's driving path to the project endpoint, read in the direction the arrows point, row by row. Each box is a run of consecutive activities on that path sharing a WBS parent (or a single activity on short chains), labelled with how many activities it covers and its date envelope; shading is stage duration. Every activity on the chain is inside exactly one box — nothing is sampled or dropped.
Update critical path timeline
Stored-critical activities on the post-update schedule plotted on the project calendar. Use alongside the schedule-comparison table to see which activities drive the current completion date. Showing 40 of 69 critical activities; the full list is in the Excel workbook.
13
Key Milestones — full comparison table
Milestones compared:4Baseline vs current forecast finish for every milestone on both schedules; variance in calendar days.
The full set of near-critical chains behind the Brief-layer float-path callout, with the overlay chart showing when each chain lands on the calendar. The Excel appendix carries the complete per-activity list per path.
Top 5 float paths
#
Float
Activities
Envelope
Driving activity
Branches from
1
0 wd
69
2026-03-02 → 2028-07-03
PRE-140 — Building control approval
—
2
7 wd
69 (1 unique)
2026-03-06 → 2028-07-03
PRE-250 — Site security and CCTV
Path 1 at SUB-110
3
7 wd
35 (8 unique)
2026-10-26 → 2028-07-03
MEP-110 — Main intake and switchgear
Path 1 at FIT-110
4
8 wd
47 (3 unique)
2026-12-03 → 2028-07-03
SUP-210 — Column starter bars L3
Path 1 at SUP-410
5
14 wd
47 (3 unique)
2026-11-13 → 2028-07-03
SUP-310 — Slab L1 formwork
Path 1 at SUP-410
Float-path overlay — when each near-critical chain lands
One bar per top-5 float path showing its divergent window — the activities unique to this path before it merges into a higher-priority chain, with the float window, data date and contractual milestones marked. Reads at a glance: are the alternatives spread across the programme or crowded into one window?
15
Progress curve
Reading this chart. Three cumulative curves over time: the baseline's planned value (dashed grey), the current plan's planned value (solid navy), and the actual earned value on the update (solid teal). Gap between the dashed grey and solid navy lines shows re-planning (work pushed into future periods, independent of actual progress). Gap between solid navy and solid teal at the data date shows the current execution gap.
Acronyms.
PV (Planned Value): share of total scheduled work due by a date.
EV (Earned Value): share actually achieved.
SV (Schedule Variance): EV − PV, in working-day equivalents.
Progress ratio: EV ÷ PV; below 1.00 ⇒ behind plan. Printed in the chart title at the data date. It is not the earned-value SPI (Schedule Performance Index), which is cost-based.
Why duration-weighted. Cost-based EVM (AC / CV / CPI) is not computed because P6 exports routinely strip resource and cost tables. Duration-weighting — each activity contributes in proportion to its original working-day duration — is used instead. Full formula: see Methodology (§27).
Duration-weighted progress S-curve
Baseline PV (dashed grey), current plan PV (solid navy), actual EV (solid teal). Vertical dotted line marks the data date where the progress ratio is computed.
16
DCMA 14-Point compliance — full scorecard
DCMA 14-Point compliance:9 of 11 assessed — 2 fails, 3 not assessed
DCMA 14-Point Assessment: 9 pass, 2 fail, 3 not assessed.
DCMA 14-Point items
Item
Measured
Threshold
Status
Notes
§1 Logic
0.8%
≤5% of incomplete activities
Pass
1 of 131 activities assessed
§2 Leads
0
0 (none allowed)
Pass
0 negative lag(s)
§3 Lags
7.8%
≤5% of relationships
Fail
12 of 154 relationships
§4 Relationship Types
90.9%
≥90% Finish-Start
Pass
140 of 154 are Finish-Start
§5 Hard Constraints
0.0%
≤5% of incomplete activities
Pass
0 hard constraint(s)
§6 High Float
21.4%
≤5% of incomplete activities
Fail
28 activities with > 44 wd float
§7 Negative Float
0
0 (none allowed)
Pass
0 activities with negative float
§8 High Duration
0.8%
≤5% of incomplete activities
Pass
1 activity longer than 44 wd
§9 Invalid Dates
0
0 (none allowed)
Pass
0 activities with dates inconsistent with data date 2026-03-06
§10 Resources
—
Not assessed
PAM 200.1 §4.10: the IMS DID does not require resource loading, so DCMA publishes no canonical threshold for this item
§11 Missed Tasks
—
≤5% of activities with baseline finish on or before status date
Not assessed
schedule has no baseline finish dates
§12 Critical Path Test
Pass
Pass / Fail
Pass
critical activities identified — note this item tests for their presence, not for an unbroken chain to the project finish; see the Open ends section
10 of 10 due activities completed by data date, measured vs SL-DEMO — no approved baseline embedded in the file, so this is informational and not scored toward the 14-point total
PAM 200.1 companion metrics
Item
Measured
Threshold
Status
Notes
Cumulative Hit Task Percentage (PAM 200.1 §3.1.2.4 — BEI companion)
—
≥0.95 (informational; PAM publishes no formal threshold)
Not assessed
no activities have baseline finish dates on or before the status date
17
SCL Appendix B explanatory records
SCL Protocol Appendix B §1.4 gives examples of explanatory records a contractor keeps. Of the items this report can stand in for: 5 present, 0 partial, 0 not assessed.
App B §1.4(d) — Milestone dates: scheduled, forecast and actual. 8 milestone(s) tracked with planned, forecast, and actual dates.
App B §1.4(b) — The critical path. Critical activities are the schedule's own stored critical flags; driving paths to contractual milestones are traced through the driving relationships in the programme's own dates; near-critical paths use the schedule's own float.
App B §1.4(c) — Progress against the earlier programme. 148 activities matched between the two schedules.
App B §1.4(b) — Key changes since the earlier programme. Changes are summarised by WBS package and accompanied by recommended next actions.
App B §1.4(b) — Delay or disruption events impacting progress. 6 event(s) itemised; 4 carry both a quantified impact and a preliminary entitlement classification. The rest are topology events (logic, constraint or calendar changes) that need a calendar-aware CPM pass to size, or events the rule-based classifier could not place from the description alone.
18
Delay by work package
Work packages with delay:4Top 5 by critical-path movement shown below; full rollup is in the Excel appendix.
Delay events aggregated by the work breakdown structure node of each affected activity.
Top 5 work packages by critical-path movement (negative = pulled in):
Foundation Piling — +10 working days net · +10 working days on the critical path · 2 events (2 critical)
Excavation — +5 working days net · +5 working days on the critical path · 1 events (1 critical)
Plumbing & Fire — +14 working days net · 0 working days on the critical path · 1 events (0 critical)
Electrical Rough-In — +3 working days net · 0 working days on the critical path · 1 events (0 critical)
The full rollup — every WBS node with a recorded event — is in the Excel appendix under the Delay Register sheet (filter by WBS column).
Activities that exist in one schedule but not the other. Added activities represent new scope; removed activities represent scope deletion.
Added activities: 1 (total planned duration 14 working days)
Removed activities: 0
The activity matching process uses four cascading strategies before an activity falls into these pools:
Exact ID
Normalised ID
Name plus WBS path
Name-only fallback
Surviving entries are genuine scope changes, not renumbering or WBS-restructuring artefacts.
Full per-activity lists (every added and removed activity) are in the Excel appendix under the Scope Changes tab.
20
What to do next: further questions and recommendations
Check your own records first. Each may already answer a question below.
Your variation register (Clarify 2)
Questions to clarify
Clarify 1. This link carries a lag: MEP-280 to FIT-160, 15 days into critical work. What does the gap represent? If it is real work, please show it as an activity.
Clarify 2. 1 activity is new in this update (MEP-355 Additional fire-water tank install). Is it a variation we instructed, or initiated by you? Please reference the instruction. (§19)
Clarify 3. The logic into 1 activity changed and its dates moved (SUP-440 Slab L4 formwork). What does the new or changed logic represent? (§22)
Forensic appendix
Full forensic recordFull evidence, registers, methodology, standards citations.
21
Scheduling options
Schedule calculated under Retained Logic
Retained Logic preserves the original network sequence through out-of-sequence progress — a partially-complete activity still waits for its predecessors to finish before continuing. This is the conservative, forensic-friendly default.
Total float calculated using finish float
Total float can be computed relative to the earliest start, the latest finish, or the lower of the two — P6 stores the project's choice here for disclosure on any report that quotes float values.
22
Delay and change register
Identified changes:6
The delay register lists each change identified between the baseline schedule dated 2026-01-05 and the update dated 2026-03-06. Each row represents a single modification to activity durations, logic, or scope, along with its individual impact on the project finish date.
Each row carries an Impact basis tag (matching the chart that follows) so the reader can immediately see whether its delay-days value is a directly-measured figure or a placeholder:
Activity-level (measured) — Duration change and Progress shortfall events. The delay-days value is a directly-measured working-day figure (update duration minus baseline duration for duration changes, or days-behind-current-plan for progress events).
Scope — upper bound — Added scope and Removed scope events. The activity's own planned duration is shown as an upper bound; the real delay contribution depends on whether the activity sits serially on the critical path, which this engine does not verify per event.
Topology (engine-unresolved) — Logic change, Constraint change, and Calendar change events. These carry a 0 delay-days value because the engine cannot size each event's isolated contribution without a calendar-aware CPM pass per event (see Methodology (§27)).
Positive delay values indicate delay to the project finish; negative values indicate acceleration. The Isolated contribution (wd) column gives, for each critical event, the working-day movement of the project finish when that event's change alone is reverted out of the update. It is a screening measure for triage, not an entitlement figure: it is subtractive, so it is not a time impact analysis, which is additive (AACE MIP 3.6/3.7; CIOB §5.8.36) and, as the CIOB Guide uses the term, prospective (CIOB §5.8.40). The figures are isolated from one another and must not be summed (see Methodology (§27)). Events off the critical path show "—"; events whose category is not resolvable by the calendar- and constraint-agnostic trace (constraint / calendar changes) show "see note" — see Methodology (§27) for the limitation. The Entitlement (prelim.) column carries a rule-based first-pass classification: Employer risk or Contractor risk (the SCL Protocol's two event types), or Neutral / Concurrent / Not assessed. The first-pass reads activity descriptions for cause-of-delay keywords and falls back to category-default rules where no keyword fires. Verify every classification against the contract, the variation register, NCRs, and documentary evidence before relying on it in any formal correspondence — the final call is a legal / contractual determination this tool does not make.
Composition by category:
Duration change: 4
Logic change: 1
Added scope: 1
Register composition
Register split by the three Impact basis buckets defined above — Activity-level (measured), Scope (upper bound), and Topology (0 without CPM). Bar width shows the event count in each bucket; percentages sum to 100 across the register.
Delay events (summary)
Ref
Category
Activity
Delay
Impact basis
Isolated contribution (wd)
Critical
Period
Entitlement (prelim.)
DE-001
Duration change
SUB-110
+5 working days
Activity-level
+5 working days
✓
2026-03-23 → 2026-04-16
Contractor risk
DE-002
Duration change
SUB-210
+6 working days
Activity-level
+6 working days
✓
2026-04-17 → 2026-04-30
Contractor risk
DE-003
Duration change
SUB-240
+4 working days
Activity-level
+4 working days
✓
2026-06-23 → 2026-07-06
Contractor risk
DE-004
Logic change
SUP-330, SUP-440
0 working days
Topology
0 working days
✓
2027-01-18 → 2027-01-27
Neutral
DE-005
Added scope
MEP-355
+14 working days
Scope — upper bound
—
2027-03-08 → 2027-03-25
Not assessed
DE-006
Duration change
MEP-130
+3 working days
Activity-level
—
2027-03-10 → 2027-04-09
Contractor risk
Delay events (detail)
Ref
Internal id
Description
DE-001
dur:SUB-110
Activity SUB-110 (Bulk excavation Zone A): duration increased from 12 to 17 working days (+5).
Review note. Activity duration extended by 5 working day(s). Classification reason: Duration increase with no external-cause keyword in the description — default Contractor risk. Check NCRs, resource-histogram variance and subcontractor correspondence for contributory cause.
DE-002
dur:SUB-210
Activity SUB-210 (Piling rig mobilisation): duration increased from 4 to 10 working days (+6).
Review note. Activity duration extended by 6 working day(s). Classification reason: Duration increase with no external-cause keyword in the description — default Contractor risk. Check NCRs, resource-histogram variance and subcontractor correspondence for contributory cause.
DE-003
dur:SUB-240
Activity SUB-240 (Pile integrity testing): duration increased from 6 to 10 working days (+4).
Review note. Activity duration extended by 4 working day(s). Classification reason: Duration increase with no external-cause keyword in the description — default Contractor risk. Check NCRs, resource-histogram variance and subcontractor correspondence for contributory cause.
DE-004
log:SUP-330->SUP-440:added
Relationship SUP-330 (Slab L1 pour) → SUP-440 (Slab L4 formwork) added (SS with lag +2).
Review note. Logic change — the network re-wiring affects critical-path sequencing. A calendar- and constraint-aware CPM pass on this specific edit is required to quantify its effect on completion. Classification reason: Topology change — entitlement depends on who made the change and why. Manual review required; treat as NEUTRAL pending that review.
DE-005
add:MEP-355
Activity MEP-355 (Additional fire-water tank install) added — new scope of 14 working day(s). Delay contribution shown is an upper bound; the true impact depends on whether the activity lies serially on the driving path.
DE-006
dur:MEP-130
Activity MEP-130 (Electrical containment L4-L6): duration increased from 18 to 21 working days (+3).
Full description for each event. The internal id links events back to the engine output and is useful when reconciling figures against the underlying analysis data.
All 15 working days of critical delay come from one category (Duration change), so there is no breakdown to chart.
23
Concurrent delay
This section lists time windows where two or more independent critical delay events overlap. The "net impact" column shows the delay days that flow through to the project completion date under the methodology named in the disclosure at the top of the report; the "absorbed" column shows delay days that would otherwise have been counted twice and are removed from the total.
The delay register contains 3 measurable critical events. None met this engine's test for concurrency — the events are either causally linked in the schedule network (one activity is upstream of the other in either the baseline or the update) or their time windows do not overlap. This is a defensible zero, not an absence of analysis: under the SCL Protocol (§10.5) delays are concurrent only if each causes Delay to Completion, which on a network means two or more independent critical chains contending for the finish during the same period. Where a schedule shows a single dominant delay chain — for example a vendor procurement sequence or a commissioning chain — the events on that chain are causally linked and correctly excluded. Where two or more independent chains exist, this section will populate with the windows during which they overlap. Review the delay register and the schedule logic to confirm the chain structure is expected.
24
DCMA detail — offending activities
The activities and relationships behind each failing DCMA item, most severe first. Tables are capped at 20 rows; the Excel appendix's “DCMA detail” sheet carries the full lists.
§3 Lags — 12 of 154 relationships
Ref
Name
Value
MEP-280 → FIT-160
Insulation and labelling → Suspended ceilings L1-L3
Cladding survey and setting-out → Cladding North elevation
SS lag +5 wd
FIT-320 → FIT-330
Toilet vanity install → Tea-point joinery
SS lag +5 wd
FIT-110 → FIT-120
Stud partition L1 → Stud partition L2
SS lag +4 wd
FIT-120 → FIT-130
Stud partition L2 → Stud partition L3
SS lag +4 wd
FIT-130 → FIT-140
Stud partition L3 → Stud partition L4
SS lag +4 wd
FIT-140 → FIT-150
Stud partition L4 → Stud partition L5-L6
SS lag +4 wd
SUP-330 → SUP-440
Slab L1 pour → Slab L4 formwork
SS lag +2 wd
§6 High Float — 28 activities with > 44 wd float (showing 20 of 28 — full list in the Excel appendix)
Ref
Name
Value
EXT-110
External drainage
123 wd float
EXT-120
Sub-base preparation
123 wd float
EXT-130
Tarmac surfacing
123 wd float
EXT-140
Line marking and signage
123 wd float
EXT-210
Soft landscape preparation
123 wd float
EXT-220
Planting and turf
123 wd float
EXT-230
Hard landscape features
123 wd float
EXT-310
Boundary fencing
122 wd float
EXT-320
Gates and access controls
122 wd float
MEP-355
Additional fire-water tank install
120 wd float
MEP-320
Riser plumbing
109 wd float
MEP-330
Floor plumbing L1-L3
109 wd float
MEP-340
Floor plumbing L4-L6
109 wd float
MEP-350
Sprinkler mains
109 wd float
MEP-360
Sprinkler floor distribution
109 wd float
SUP-610
Roof waterproofing membrane
78 wd float
SUP-620
Roof finishes and parapet
78 wd float
MEP-110
Main intake and switchgear
71 wd float
FIT-230
Painting L1-L3
62 wd float
FIT-250
Floor finishes L1-L3
62 wd float
25
Float consumption detail
Float lost by WBS package
WBS
Float lost (typical)
Activities eroding
Electrical Rough-In
3 wd
8
MEP Rough-In
3 wd
1
How float consumption is measured
Float consumed is the reduction in CPM-recomputed total float on activities matched between the baseline and this update. 148 of 148 matched float-bearing activities were compared on a like-for-like basis; 0 were excluded because their constraint changed or they moved to a different calendar, which shifts float wholesale and would otherwise read as erosion.
26
Delay timeline
Timeline visualisation of delay events plotted against the project schedule. Events are coloured by category; concurrent-delay windows are shaded.
Delay events and concurrent periods
27
Methodology
This report assesses the uploaded schedule against the published industry standards listed below. Each finding traces to a specific rule in one or more of those standards. The analysis is automated and deterministic — the same schedule file will always produce the same findings.
Scope of this analysis. This report is based solely on the schedule file(s) you uploaded. Determinations that — under AACE RP 29R-03, the SCL Delay & Disruption Protocol, or other cited standards — require evidence outside the schedule file have been flagged as candidates rather than concluded. Specifically, the following determinations and analyses require manual verification by a qualified delay analyst before being relied on for contractual purposes:
Pacing vs concurrency — distinguishing contractor pacing (AACE §4.2.F / SCL §15.2) from independent concurrent delay requires contemporaneous notice, correspondence, and resource records that are outside the scope of schedule-only analysis.
Constructive acceleration — identifying directed or constructive acceleration (AACE §4.4) requires correspondence and contract notices not available to the engine.
Contractual classification — categorising delay events as excusable, compensable, or non-excusable depends on contract terms outside the schedule file.
Concurrency during the overlap window — the SCL Protocol (§10.5) treats delays as concurrent only if each causes Delay to Completion. The engine tests whether both were critical during their overlap, and evaluates this as the union of the two schedules' critical-path membership, which is a snapshot-level approximation of the window-level test. A precise test would require a CPM walk per overlap interval, which the engine does not run. The approximation will under-detect concurrency where an activity was on the critical path only during a sub-window of the overlap and not at either snapshot date.
As-built critical path — the report does not produce a stitched as-built critical path across multiple updates. On comparison reports the per-update critical path is shown for each schedule in the comparison (Driving Path section); on series reports an interim methodology paragraph describes the per-period substitute.
Date basis. Every start and finish date in this report is each schedule's *current forecast* — the date work is now expected to occur, or its recorded actual date where the work is complete. In Primavera P6 that is the Remaining Early date; in Microsoft Project and Asta Powerproject it is the scheduled Start/Finish. The report does not use a tool's frozen Planned/target dates, which stop updating once an activity is in progress and so understate movement on a progressed schedule. Baseline dates stored inside a file (e.g. a P6 baseline) are read as recorded, and every variance compares the current forecast on each side.
Float and criticality — the source tool's — every total-float and critical-path figure in this report (including the DCMA float checks, float paths, near-critical detection and milestone deliverability) is the value recorded by the scheduling tool that produced the file. ScheduleLens does not overwrite it. Where the source recorded no float and the activity is incomplete, ScheduleLens's own calendar-aware pass supplies one; completed activities are left unfloated rather than given an invented value. That gap-filling pass applies Retained Logic/Progress Override per the file's scheduling options but does not model Start/Finish-No-Later-Than or As-Late-As-Possible constraints, Expected Finish forcing, or an imposed must-finish date. ScheduleLens's own critical-path pass is used for change between two schedules — critical-path churn, bounded what-if, retained-logic versus progress-override, between-snapshot slip — where both sides run through the same engine; those figures are labelled as ScheduleLens's. Where the independent pass disagrees with the file's own critical flags, the disagreement is reported by the critical-path staleness check rather than resolved.
Engine-attributed-vs-observed divergence — the engine-attributed delay figure is an attribution of observed completion movement to specific activity-level events. It can diverge from the observed figure in either direction. Undercount divergence (engine attributes less than observed) typically reflects unquantified topology changes, scope absorption, or parallel-path absorption the activity-level formula cannot capture without a CPM recalculation. Overstate divergence (engine attributes more than observed) typically reflects double-counting along a critical chain, scope-add events whose full duration is being counted, or concurrency absorption gaps. In both directions the observed figure is authoritative for the headline; the engine-attributed figure is a subordinate diagnostic surfacing what specific events contributed.
Where the engine raises a candidate flag for any of these determinations, the relevant section explicitly says so. The engine does produce a rule-based first-pass entitlement classification on each delay-register row (Employer risk, Contractor risk, Neutral, Concurrent, or Not Assessed) — this is a preliminary tagging based on activity-description keywords and category defaults, not a contractual determination. The classification is presented as '(prelim.)' in the column header and every row carries a review-note prompt to verify against the contract, the variation register, NCRs, and documentary evidence before relying on it.
Units. Day figures in this report are calendar days unless they are marked as working days. Two different quantities are being measured and the distinction is deliberate.
Movement between two dates — how far completion, a milestone or the schedule end has moved between submissions — is reported in calendar days. Elapsed time is the same quantity for every activity on a programme, so figures measured this way can be compared with each other, and they do not change when a calendar's holidays are edited. AACE RP 29R-03 directs that as-built comparison be carried out in calendar days for this reason, and cautions that float expressed in workday units differs between activities on different calendars; SCL Protocol §8.8 gives the same caution where multiple work-day calendars are in use.
Schedule properties — float, activity durations, the delay quantum recorded against each event, and the DCMA thresholds — are reported in working days, and are marked as such wherever they appear. These are not spans between two dates and have no calendar-day equivalent: an activity whose duration grows from 10 to 20 working days has no single elapsed-day value, because that depends on where in the calendar the work falls. The DCMA 14-point checks define their thresholds in working days, so restating them would change what is being tested.
A working-day figure is counted on the calendar assigned to the activity it describes, not on the project default — on a programme running five-day and seven-day calendars together, the same elapsed period is a different number of working days for different activities.
Isolated contribution per critical event. For each critical event in the delay register, the update is re-run with that one change reverted, using the independent longest-path trace described below, and the movement of the project finish is the event's isolated contribution in working days (a progress shortfall uses its measured days behind plan instead). It is a screening measure, not a time impact analysis. Each figure is measured on its own, so the figures must not be summed and are not expected to add up to the movement in completion: concurrent events on parallel paths each show their own figure, but completion moves only by the longest. Constraint and calendar changes cannot be sized this way, because the trace models neither; they carry 0 delay days or "see note" and are reported as direction-of-travel signals. The Contribution note column of the Excel register gives the reason for each "see note" row.
Logic-change grouping. One re-sequencing usually edits several dependency links at once. The register shows one row per activity whose incoming logic changed, stated as "N link changes affecting M activities", and that row's isolated contribution reverts the whole group together. Grouping by the receiving activity is a mechanical rule, not a record of what the planner intended. Every individual link change is listed in the Excel Delay Register tab.
Key milestone comparison. A comparison report lists only the milestones present on both schedules. One that exists on one side only is a scope change (added or removed), and including it would put a variance against nothing; those are counted under the table and listed in Scope Changes and the Excel Key Milestones sheet. Variance is in calendar days, the unit an extension-of-time claim is usually stated in, so the figure reads the way the contract will assess it. The two float columns are each file's total float in working days, read from the scheduling tool wherever it recorded one. A milestone is paired across the files the way every other activity in the comparison is.
Independent longest-path trace. A forward pass over the activity network using durations and relationship types only. It is a cross-check, not a CPM recalculation: it does not model calendars, constraints or resource levelling, so where those drive the dates its answer can differ from the source scheduling tool's. Float and critical flags in this report come from the source tool wherever it recorded them.
Near-critical threshold. Float paths and the near-critical count use a threshold set by the schedule's status cycle, not its length: the question is whether an activity could become controlling, with a small slip, before the next status update. The default is 20 working days, a monthly cycle; it can be set for each project at upload. No published standard prescribes a value. The float distribution chart keeps the DCMA bands (1–10, 11–44 and over 44 working days) so its shape compares across reports, which is why the near-critical count can include activities in the 11–44 band.
Duration-weighted progress. Exported schedules rarely carry cost or resource loading, so the progress curve weights each activity by its original duration. Planned value (PV) at a date is the share of that weighted work the schedule's own planned dates put before it. Earned value (EV) is each activity's original duration multiplied by its percent complete, summed, and divided by the sum of original durations. Summary, level-of-effort and milestone activities are excluded. The progress ratio (EV ÷ PV) is measured against the file's planned dates, not an approved baseline, so it is not the earned-value SPI.
Critical-path overlay rows. The overlay chart shows at most 15 activities. It takes those critical in both versions first (negative float, then zero, then positive, each by largest finish movement), then those that joined the critical path, then those that left it, keeping at least two rows each for joined and left where they exist.
Float erosion. Each period compares an activity's total float with the previous update like for like, leaving out activities whose constraint or calendar changed (a holiday edit to the same calendar is netted out instead). The float lost on a chain is the median drop across its eroding activities, not the sum: every activity on a float path shares that path's float, so adding their drops would count one loss many times. A period with a re-baseline (a wholesale constraint or calendar change) or a re-sequence (float released about as fast as it is consumed) is flagged rather than reported, because its float changes come from re-planning, not erosion.
Use of AI. The ScheduleLens analysis engine computed every finding, figure, score and chart in this report. At the requester's election, a language model (qwen3-6-27b, via Venice) then wrote the explanatory prose in the sections “Executive Summary”, “What happened · Why · Where to investigate” and “Delay and change register”. It worked only from those computed results. It did not see the schedule file and did no analysis of its own. Where prose and a table or chart differ, the table or chart governs.
Standards referenced
Short name
Full title
Edition
Sections cited
DCMA 14-Point
DCMA EVMS Program Analysis Pamphlet (PAM) — §4 14 Point Schedule Metrics for IMS Analysis
AACE Recommended Practice 29R-03 — Forensic Schedule Analysis
§4.2.F, §4.4, MIP 3.6/3.7
CIOB Guide
CIOB Guide to Good Practice in the Management of Time
2nd Edition
§5.8.36, §5.8.40
PMI Standard for EVM
PMI — The Standard for Earned Value Management
2019
§4.4
NDIA Predictive Measures Guide
NDIA IPMD — Predictive Measures Guide
Revision 4 (2025)
§2.6.2
ScheduleLens is not affiliated with, endorsed by, or certified by AACE International, the Project Management Institute, the Defense Contract Management Agency, the Chartered Institute of Building, the Society of Construction Law, or the Government Accountability Office. Citations to these standards in this report are bibliographic, indicating the analytical basis for each check.