Sample data — this is a ScheduleLens demonstration report on a synthetic schedule, not a real construction project. Back to schedulelens.com · All sample reports · Download PDF · Download Excel appendix
ScheduleLens Schedule Comparison

Project

SL-DEMO

2026-03-09

Completion movement

+21 calendar days

+15 working days on the project's default calendar.

Critical-path activities

73

0 joined · 0 left vs baseline.

Scope changes

1

1 added · 0 removed between baseline and update.

DCMA score

B · 9 of 11 assessed

Checks passed on the update (3 not assessed).

Baseline finish

2028-06-12

SL-DEMO (data date 2026-01-05).

Update finish

2028-07-03

SL-DEMO: +21 calendar days vs baseline.

Contract finish

2028-07-03

Practical Completion · 0 wd float.

Update data date

2026-03-06

3 calendar days ago.

Contents

Schedule Comparison

  1. — Disclosures
  2. Brief
  3. 01 Executive Summary
  4. 02 Signals
  5. 03 What happened · Why · Where to investigate
  6. 04 Key Milestones
  7. 05 What to do next
  8. Narrative
  9. 06 Period hit rate (CEI)
  10. 07 Float-path risk
  11. 08 Float consumption
  12. 09 Completion forecast (Earned Schedule)
  13. 10 Critical path
  14. 11 Schedule comparison
  15. 12 Critical path — supporting views
  16. 13 Key Milestones — full comparison table
  17. 14 Float paths — detail
  18. 15 Progress curve
  19. 16 DCMA 14-Point compliance — full scorecard
  20. 17 SCL Appendix B explanatory records
  21. 18 Delay by work package
  22. 19 Scope changes
  23. 20 What to do next: further questions and recommendations
  24. Appendix
  25. 21 Scheduling options
  26. 22 Delay and change register
  27. 23 Concurrent delay
  28. 24 DCMA detail — offending activities
  29. 25 Float consumption detail
  30. 26 Delay timeline
  31. 27 Methodology

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.

02

Signals

Forecast finishes that happened 10 of 10 finished 60-day period; 3 of 3 flagged critical → §06
Near-critical paths 8 sub-critical or parallel-critical, within 20 working days of the controlling path. → §07
Float consumed 3 wd median 9 activities eroding float since the baseline → §08
Earned Schedule finish 2028-06-06 Earned Schedule at the pace to date (SPIt 1.01), measured against SL-DEMO. Programme finish: 2028-07-03. → §09
DCMA 14-Point compliance 9 of 11 assessed — 2 fails, 3 not assessed → §16
03

What happened · Why · Where to investigate

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)
CategoryEventsWorking days
Duration changes 4 18 working days
Added scope (upper bound) 1 14 working days
Top 1 WBS packages for topology edits
WBS packageEventsLogicConstraintCalendar
Superstructure 1 1 0 0
04

Key Milestones

Milestones compared: 4 Baseline vs current forecast finish for every milestone on both schedules; variance in calendar days.

Contract finish (your answer): 2028-07-03, Practical Completion · 0 wd float.

Key milestones — 4 of 4 slipped
MilestoneBaseline forecast finishCurrent forecast finishVarianceBaseline floatCurrent floatOn critical path
Substructure complete 2026-10-05 2026-10-26 +21 days 0 wd 0 wd Yes
Envelope watertight 2027-08-03 2027-08-24 +21 days 0 wd 0 wd Yes
Fit-out complete 2028-03-31 2028-04-21 +21 days 0 wd 0 wd Yes

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.

Critical questions

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 finished 60-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: 8 sub-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
#FloatActivitiesEnvelopeDriving activityBranches 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 median 9 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 nowFloat lost (typical)Activities erodingDriving activity
3 7 wd 3 wd 8/35 MEP-110 — Main intake and switchgear
09

Completion forecast (Earned Schedule)

Earned Schedule finish: 2028-06-06 Earned 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
BasisFinishvs 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

image/svg+xml schedule-analyser Jul 26 Oct 26 Jan 27 Apr 27 Jul 27 Oct 27 Showing 15 of 73 activities critical on either schedule; the full list is in the Excel workbook. SUB-240 Pile integrity testing SUB-250 Pile trimming SUB-310 Pile cap excavation SUB-320 Pile cap reinforcement SUB-330 Pile cap concrete pour SUB-340 Ground beam install SUB-410 Basement slab formwork SUB-420 Basement slab reinforcement SUP-360 Slab L2 pour SUP-410 Slab L3 formwork SUP-520 Roof slab reinforcement SUP-530 Roof slab pour ENV-140 Curtain wall install North elevation FIT-110 Stud partition L1 FIT-120 Stud partition L2 Baseline Persisted on critical path Finish-date shift
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

image/svg+xml schedule-analyser Oct 26 Jan 27 Apr 27 Jul 27 Oct 27 Jan 28 Showing 15 of 140 matched activities, critical first, then by size of date change. SUB-340 Ground beam install SUB-410 Basement slab formwork SUP-360 Slab L2 pour SUP-410 Slab L3 formwork SUP-420 Slab L3 reinforcement SUP-520 Roof slab reinforcement SUP-530 Roof slab pour ENV-140 Curtain wall install North elevation ENV-150 Curtain wall install East elevation FIT-110 Stud partition L1 FIT-120 Stud partition L2 FIT-130 Stud partition L3 FIT-140 Stud partition L4 FIT-150 Stud partition L5-L6 FIT-240 Painting L4-L6 Baseline Update (critical) Update (non-critical)
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)
IDNameBaseline startBaseline finishUpdate startUpdate finishStart ΔFinish ΔStatusCritical (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

image/svg+xml schedule-analyser May 26 Sep 26 Jan 27 May 27 Sep 27 Jan 28 Showing 15 of 28 WBS clusters. Permits & Approvals Excavation Foundation Piling Pile Caps & Ground Beams Basement Slab Substructure RC Columns L1-L3 Slab Pours L1-L3 Slab Pours L4-L6 Roof Slab Curtain Wall Windows & Doors Building Envelope Partitions & Ceilings Finishes & Decoration 1 act. 1 act. 5 act. 4 act. 4 act. 1 act. 6 act. 3 act. 6 act. 3 act. 4 act. 3 act. 1 act. 8 act. 4 act. Critical (flagged in the source programme)
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

image/svg+xml schedule-analyser Permits & Approvals to Excavation 2 act. 02 Mar 26 – 16 Apr 26 Foundation Piling 5 act. 17 Apr 26 – 16 Jul 26 Pile Caps & Ground Beams 4 act. 17 Jul 26 – 07 Sep 26 Basement Slab 4 act. 08 Sep 26 – 23 Oct 26 Substructure 1 act. 26 Oct 26 RC Columns L1-L3 6 act. 26 Oct 26 – 02 Dec 26 Slab Pours L1-L3 3 act. 03 Dec 26 – 06 Jan 27 Slab Pours L4-L6 6 act. 07 Jan 27 – 09 Mar 27 Roof Slab 3 act. 10 Mar 27 – 14 Apr 27 Curtain Wall 4 act. 15 Apr 27 – 08 Jul 27 Windows & Doors 3 act. 09 Jul 27 – 23 Aug 27 Building Envelope 1 act. 24 Aug 27 Partitions & Ceilings 8 act. 24 Aug 27 – 24 Nov 27 Finishes & Decoration 4 act. 01 Nov 27 – 22 Feb 28 Joinery & Fixtures 6 act. 01 Feb 28 – 20 Apr 28 Interior Fit-Out 1 act. 21 Apr 28 Snagging & Punchlist 4 act. 21 Apr 28 – 09 Jun 28 Practical Completion 4 act. 12 Jun 28 – 03 Jul 28 69 activities to Practical Completion. Follow the arrows: each row reads in the direction the arrows point, then drops to the row below. Box = consecutive activities on the driving path sharing a WBS parent. Shade: darker = longer stage. 1 box span more than one WBS parent (named first to last) so the whole chain fits; no activity is omitted.
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

image/svg+xml schedule-analyser Jul 26 Jan 27 Jul 27 Jan 28 Jul 28 PRE-140 Building control approval SUB-110 Bulk excavation Zone A SUB-210 Piling rig mobilisation SUB-220 CFA piling Zone A SUB-230 CFA piling Zone B SUB-240 Pile integrity testing SUB-250 Pile trimming SUB-310 Pile cap excavation SUB-320 Pile cap reinforcement SUB-330 Pile cap concrete pour SUB-340 Ground beam install SUB-410 Basement slab formwork SUB-420 Basement slab reinforcement SUB-430 Basement slab waterproofing SUB-440 Basement slab pour MS-SUB-END Substructure complete SUP-110 Column starter bars L1 SUP-120 Column formwork L1 SUP-130 Column pour L1 SUP-140 Column starter bars L2 … 29 more not shown FIT-180 Ceiling integration MEP FIT-210 Plastering L1-L3 FIT-220 Plastering L4-L6 FIT-240 Painting L4-L6 FIT-260 Floor finishes L4-L6 FIT-310 Reception joinery FIT-320 Toilet vanity install FIT-330 Tea-point joinery FIT-340 Meeting room joinery FIT-350 Built-in storage and fittings FIT-360 Final joinery snagging CMS-210 Client walkthrough and snag list MS-FIT-END Fit-out complete CMS-220 Major snags rectification CMS-230 Minor snags rectification CMS-240 Final inspection CMS-310 Building handover documentation CMS-320 O&M manuals issued CMS-330 Soft landings start MS-PC Practical Completion
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: 4 Baseline vs current forecast finish for every milestone on both schedules; variance in calendar days.

Contract finish (your answer): 2028-07-03, Practical Completion · 0 wd float.

Key milestones — baseline vs current
MilestoneBaseline forecast finishCurrent forecast finishVarianceBaseline floatCurrent floatOn critical path
Substructure complete 2026-10-05 2026-10-26 +21 days 0 wd 0 wd Yes
Envelope watertight 2027-08-03 2027-08-24 +21 days 0 wd 0 wd Yes
Fit-out complete 2028-03-31 2028-04-21 +21 days 0 wd 0 wd Yes
Practical Completion 2028-06-12 2028-07-03 +21 days 0 wd 0 wd Yes
14

Float paths — detail

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
#FloatActivitiesEnvelopeDriving activityBranches 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

image/svg+xml schedule-analyser Jul 26 Jan 27 Jul 27 Jan 28 Jul 28 Jan 29 Path 1 (critical) · 0 wd · 69 act. Path 2 · 7 wd · 1 act. Path 3 · 7 wd · 8 act. Path 4 · 8 wd · 3 act. Path 5 · 14 wd · 3 act. PRE-140 — Building control approval PRE-250 — Site security and CCTV MEP-110 — Main intake and switchgear SUP-210 — Column starter bars L3 SUP-310 — Slab L1 formwork M1 M2 M3 M4 Critical path (Path 1) Alternative chain (divergent window) Float window (total float, approx. calendar) Data date M1 — Substructure complete M2 — Envelope watertight M3 — Fit-out complete M4 — Practical Completion
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.

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

image/svg+xml schedule-analyser Jan 26 May 26 Sep 26 Jan 27 May 27 Sep 27 Jan 28 May 28 Progress ratio 0.92 at the data date · EV 5.4% · PV 5.9% · SV -0.5pp 0 20 40 60 80 100 Cumulative % complete (duration-weighted) Data date 6 Mar 2026 Planned band (early to late dates) Planned value (current plan) Earned value (actual progress) Planned value (baseline)
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
ItemMeasuredThresholdStatusNotes
§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
§13 Critical Path Length Index 1.00 ≥0.95 Pass CP length 593 wd to Practical Completion, finish float 0 wd
§14 Baseline Execution Index 1.00 ≥0.95 Not assessed 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
ItemMeasuredThresholdStatusNotes
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.

SCL Appendix B §1.4 explanatory records
ItemDescriptionAddressed inStatus
App B §1.4(d) Milestone dates: scheduled, forecast and actual Key Milestones (Brief) Present
App B §1.4(b) The critical path Driving path (Brief), Float paths (Brief) Present
App B §1.4(c) Progress against the earlier programme Schedule comparison (Narrative), Progress curve Present
App B §1.4(b) Key changes since the earlier programme WBS roll-up (Narrative), Recommendations (Narrative) Present
App B §1.4(b) Delay or disruption events impacting progress Delay register (Appendix) Present

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: 4 Top 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):

The full rollup — every WBS node with a recorded event — is in the Excel appendix under the Delay Register sheet (filter by WBS column).

19

Scope changes

Added · Removed: 1 · 0 Net scope delta: +1 activities.

Activities that exist in one schedule but not the other. Added activities represent new scope; removed activities represent scope deletion.

The activity matching process uses four cascading strategies before an activity falls into these pools:

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.

Questions to clarify

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:

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:

Register composition

image/svg+xml schedule-analyser 0 1 2 3 4 Events in register (6 in total) Activity-level (measured) Scope — upper bound Topology (0 days without CPM) 4 (67%) 1 (17%) 1 (17%)
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)
RefCategoryActivityDelayImpact basisIsolated contribution (wd)CriticalPeriodEntitlement (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)
RefInternal idDescription
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
RefNameValue
MEP-280 → FIT-160 Insulation and labelling → Suspended ceilings L1-L3 FS lag +15 wd
CMS-110 → CMS-120 Mechanical commissioning → Electrical commissioning SS lag +8 wd
FIT-170 → FIT-180 Suspended ceilings L4-L6 → Ceiling integration MEP SS lag +7 wd
FIT-260 → FIT-310 Floor finishes L4-L6 → Reception joinery SS lag +6 wd
SUB-110 → SUB-120 Bulk excavation Zone A → Bulk excavation Zone B SS lag +5 wd
ENV-210 → ENV-220 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)
RefNameValue
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
WBSFloat 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

image/svg+xml schedule-analyser May 26 Jul 26 Sep 26 Nov 26 Jan 27 Mar 27 SUB-110 · Bulk excavation Zone A (+5wd) SUB-210 · Piling rig mobilisation (+6wd) SUB-240 · Pile integrity testing (+4wd) SUP-330 · Slab L1 pour MEP-355 · …nal fire-water tank install (+14wd) MEP-130 · Electrical containment L4-L6 (+3wd) Duration change Logic change Added scope
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:

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 nameFull titleEditionSections cited
DCMA 14-Point DCMA EVMS Program Analysis Pamphlet (PAM) — §4 14 Point Schedule Metrics for IMS Analysis DCMA-EA PAM 200.1, October 2012 §1, §2, §3, §4, §5, §6, §7, §8, §9, §10, §11, §12, §13, §14
SCL Protocol SCL Delay & Disruption Protocol, 2nd Edition 2nd Edition (2017) §8.8, §15.2, Appendix B §1.4, §1.59
AACE RP 29R-03 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.

Produced by ScheduleLens 0.1.0.