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.
The tool does not perform a full critical-path method recalculation and 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.
For the project director
Brief
Severity-coded status headlines, top risks, what to act on.
01
Executive Summary
The schedule quality is rated as acceptable with minor concerns, though 16 near-critical activities and a DCMA score of 8 out of 14 indicate moderate risk to timely completion. The presence of 58 activities with float exceeding 44 working days and 12 activities with dangling logic affects the reliability of the critical path, which may distort delay analysis and resource planning. These issues matter because they increase the likelihood of undetected delays and reduce confidence in milestone forecasting, particularly as the near-critical tasks are within one reporting cycle of impacting the finish date. For verification, review the detailed logic and float anomalies in the schedule structure analysis.
02
Where to focus first
Priority packages:5Top 5 WBS packages by impact score (8 total buckets carry at least one signal).
The MEP Rough-In and Building Envelope packages carry the highest impact scores, driven primarily by a high number of affected activities and the presence of warning findings. Both exhibit widespread instances of excessive float and dangling logic, indicating potential planning or execution gaps. Reviewers may wish to examine these packages first to understand the extent and context of the reported conditions.
Priority WBS packages
Package
Critical
Warning
Affected
Near-crit.
Top issues
MEP Rough-In
0
2
16
9
Activities with float over 44 days (7 of 58); Activities with dangling logic (1 of 12)
Superstructure
0
2
14
3
Activities with float over 44 days (11 of 58); Activities with dangling logic (6 of 12)
Pre-Construction
0
2
5
4
Activities with float over 44 days (1 of 58); Activities with dangling logic (1 of 12)
Building Envelope
0
2
17
0
Activities with float over 44 days (17 of 58); Activities with dangling logic (2 of 12)
Interior Fit-Out
0
2
4
0
Activities with float over 44 days (4 of 58); Activities with dangling logic (2 of 12)
03
Key Milestones
Key milestones:3Auto-detected from the contractual-milestone dictionary, plus critical-path finish milestones as a fallback for custom names.
The milestones below are the contractual and progress dates the report has identified as deserving prominent review — Practical Completion, sectional handovers, commissioning, and similar dates that projects are typically managed and assessed against.
Detection is deterministic: contractual keywords (Practical / Sectional / Substantial Completion, Handover Certificate, Commissioning Completion, and similar) take precedence; zero-duration finish milestones on the critical path are included as a fallback for schedules whose contractual dates use project-specific names. The rationale column shows which rule matched each row.
To add or remove keywords, re-upload the schedule with the Advanced options filled in.
Key milestones — planned and actual dates
Milestone
Planned start
Planned finish
Actual start
Actual finish
Progress
Total float
On critical path
Detection
Substructure complete
2026-09-29
2026-09-29
—
—
0%
0 wd
Yes
finish milestone on critical path (terminal in WBS package)
Fit-out complete
2028-03-07
2028-03-07
—
—
0%
0 wd
Yes
finish milestone on critical path (terminal in WBS package)
Reading this chart. Two cumulative curves over time: where the schedule should be (Planned Value, solid blue) and where it actually is (Earned Value, solid red). The vertical dotted line is the data date; the gap between the two curves at that line is the current schedule performance.
Acronyms. PV = Planned Value — the share of total scheduled work that should have been consumed by a given date under the baseline plan. EV = Earned Value — the share actually completed, computed as Σ(original_duration × percent_complete) ÷ Σ(original_duration). SV = Schedule Variance = EV − PV, expressed in working-day equivalents under the duration-weighting. SPI = Schedule Performance Index = EV ÷ PV. SPI < 1.00 ⇒ behind plan; SPI > 1.00 ⇒ ahead.
Why duration-weighted. P6 / MS Project exports routinely strip resource and cost data, so a cost-weighted EV (the classic EVM formulation from AACE RP 27R-03) is not always available. Duration-weighting is the industry-standard fallback: each activity contributes in proportion to its original working-day duration rather than its budget. Full formula and caveats in METHODOLOGY §5d.
Duration-weighted progress S-curve
Current plan PV (solid blue) vs actual EV (solid red). Vertical dotted line marks the data date where SPI is read.
05
Float-path risk
Near-critical paths:3sub-critical or parallel-critical, within 20 working days of the controlling path (primary driving path shown separately as rank 1; full list in the Excel appendix).
What this section answers: where else forward risk is concentrated besides the controlling chain. Each row is an alternative chain to the project endpoint that's within 20 working days of the critical path; any of them could become controlling with a small slip.
Three float paths fall within 20 working days of the controlling path, indicating a moderate cluster of near-critical risk. The group includes one zero-float path already on the critical threshold and two near-critical paths with positive float, showing the forward risk is split between current criticality and potential future impact. Multiple sub-critical paths matter because any one of them could become controlling with a delay of just a few working days, potentially altering the project’s overall schedule outcome.
Top 4 float paths
#
Float
Activities
Envelope
Driving activity
Branches from
1
0 wd
68
2026-01-05 → 2028-06-08
MS-START — Project Start
—
2
7 wd
67 (4 unique)
2026-02-09 → 2028-06-08
PRE-210 — Site mobilisation
Path 1 at SUB-110
3
10 wd
37 (4 unique)
2026-11-06 → 2028-06-08
SUP-340 — Slab L2 formwork
Path 1 at MEP-130
4
20 wd
30 (8 unique)
2027-02-10 → 2028-06-08
MEP-210 — Plant room frame and pads
Path 1 at FIT-160
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. Background shading marks the critical-path envelope. Reads at a glance: are the alternatives spread across the programme or crowded into one window?
Project finish target date:2028-06-08 — zero days of slackAny slip on the activities below pushes the project finish date unless recovered elsewhere on the chain. 885 calendar days from today.
What this section answers: what controls the project finish date. The activities below are the ones whose slip directly delays the entire project — the controlling chain.
The 68 activities listed are flagged as critical by the source scheduling tool's own calendar-aware CPM and are ordered by planned start date. Any slip on any of them delays the project finish unless offset by acceleration elsewhere on the same path.
The ``critical_path`` finding in the analysis section reports any material disagreement between this stored set and ScheduleLens' own independent trace.
Critical path rollup — WBS summary bars
One bar per WBS cluster that contains at least one critical or near-critical activity. Bar span is the cluster's envelope (earliest start to latest finish); the count at the right is the number of stored-critical activities in the cluster.
Node = WBS cluster containing stored-critical activities. Arrow = at least one activity in the source cluster is a predecessor of an activity in the target cluster. Layout is topological left-to-right; columns are depth levels from project start.
Critical path — stored is_critical activities (part 1 of 3)
Activities flagged ``is_critical`` by the source scheduling tool, plotted on the project calendar. Bar length is the planned duration.
Critical path — stored is_critical activities (part 2 of 3)
Activities flagged ``is_critical`` by the source scheduling tool, plotted on the project calendar. Bar length is the planned duration.
Critical path — stored is_critical activities (part 3 of 3)
Activities flagged ``is_critical`` by the source scheduling tool, plotted on the project calendar. Bar length is the planned duration.
Activities on the critical path
ID
Name
WBS
Duration (wd)
Float (wd)
Planned start
Planned finish
MS-START
Project Start
Pre-Construction
0
0
2026-01-05
2026-01-05
PRE-110
Submit planning permission application
Permits & Approvals
5
0
2026-01-05
2026-01-12
PRE-120
Planning permission approval
Permits & Approvals
25
0
2026-01-12
2026-02-16
PRE-130
Building control submission
Permits & Approvals
10
0
2026-02-16
2026-03-02
PRE-140
Building control approval
Permits & Approvals
15
0
2026-03-02
2026-03-23
SUB-110
Bulk excavation Zone A
Excavation
12
0
2026-03-23
2026-04-10
SUB-210
Piling rig mobilisation
Foundation Piling
4
0
2026-04-10
2026-04-16
SUB-220
CFA piling Zone A
Foundation Piling
18
0
2026-04-16
2026-05-13
SUB-230
CFA piling Zone B
Foundation Piling
18
0
2026-05-13
2026-06-08
SUB-240
Pile integrity testing
Foundation Piling
6
0
2026-06-08
2026-06-16
SUB-250
Pile trimming
Foundation Piling
8
0
2026-06-16
2026-06-26
SUB-310
Pile cap excavation
Pile Caps & Ground Beams
8
0
2026-06-26
2026-07-08
SUB-320
Pile cap reinforcement
Pile Caps & Ground Beams
10
0
2026-07-08
2026-07-22
SUB-330
Pile cap concrete pour
Pile Caps & Ground Beams
6
0
2026-07-22
2026-07-30
SUB-340
Ground beam install
Pile Caps & Ground Beams
12
0
2026-07-30
2026-08-17
SUB-410
Basement slab formwork
Basement Slab
8
0
2026-08-17
2026-08-27
SUB-420
Basement slab reinforcement
Basement Slab
12
0
2026-08-27
2026-09-15
SUB-430
Basement slab waterproofing
Basement Slab
6
0
2026-09-09
2026-09-17
SUB-440
Basement slab pour
Basement Slab
8
0
2026-09-17
2026-09-29
MS-SUB-END
Substructure complete
Substructure
0
0
2026-09-29
2026-09-29
SUP-110
Column starter bars L1
RC Columns L1-L3
4
0
2026-09-29
2026-10-05
SUP-120
Column formwork L1
RC Columns L1-L3
6
0
2026-10-05
2026-10-13
SUP-130
Column pour L1
RC Columns L1-L3
4
0
2026-10-13
2026-10-19
SUP-140
Column starter bars L2
RC Columns L1-L3
4
0
2026-10-19
2026-10-23
SUP-150
Column formwork L2
RC Columns L1-L3
6
0
2026-10-23
2026-11-02
SUP-160
Column pour L2
RC Columns L1-L3
4
0
2026-11-02
2026-11-06
SUP-210
Column starter bars L3
RC Columns L1-L3
4
0
2026-11-10
2026-11-16
SUP-220
Column formwork L3
RC Columns L1-L3
6
0
2026-11-16
2026-11-24
SUP-230
Column pour L3
RC Columns L1-L3
4
0
2026-11-24
2026-11-30
SUP-240
Column starter bars L4
RC Columns L4-L6
4
0
2026-12-02
2026-12-08
SUP-250
Column formwork L4
RC Columns L4-L6
6
0
2026-12-08
2026-12-16
SUP-260
Column pour L4
RC Columns L4-L6
4
0
2026-12-16
2026-12-22
SUP-440
Slab L4 formwork
Slab Pours L4-L6
8
0
2027-01-04
2027-01-14
SUP-450
Slab L4 reinforcement
Slab Pours L4-L6
8
0
2027-01-14
2027-01-26
SUP-460
Slab L4 pour
Slab Pours L4-L6
6
0
2027-01-26
2027-02-03
MEP-130
Electrical containment L4-L6
Electrical Rough-In
18
0
2027-04-09
2027-05-06
MEP-140
Cable pulling L1-L3
Electrical Rough-In
20
0
2027-05-06
2027-06-03
MEP-150
Cable pulling L4-L6
Electrical Rough-In
20
0
2027-06-03
2027-07-01
MEP-160
Distribution boards
Electrical Rough-In
12
0
2027-07-01
2027-07-19
MEP-170
Lighting wiring rough-in
Electrical Rough-In
18
0
2027-07-19
2027-08-12
MEP-180
Power outlet rough-in
Electrical Rough-In
18
0
2027-08-12
2027-09-08
FIT-110
Stud partition L1
Partitions & Ceilings
12
0
2027-08-16
2027-09-02
FIT-120
Stud partition L2
Partitions & Ceilings
12
0
2027-08-24
2027-09-10
FIT-130
Stud partition L3
Partitions & Ceilings
12
0
2027-09-02
2027-09-20
FIT-140
Stud partition L4
Partitions & Ceilings
12
0
2027-09-10
2027-09-28
FIT-150
Stud partition L5-L6
Partitions & Ceilings
18
0
2027-09-20
2027-10-14
FIT-160
Suspended ceilings L1-L3
Partitions & Ceilings
25
0
2027-09-20
2027-10-25
FIT-210
Plastering L1-L3
Finishes & Decoration
20
0
2027-10-06
2027-11-03
FIT-170
Suspended ceilings L4-L6
Partitions & Ceilings
25
0
2027-10-14
2027-11-18
FIT-180
Ceiling integration MEP
Partitions & Ceilings
12
0
2027-10-25
2027-11-10
FIT-220
Plastering L4-L6
Finishes & Decoration
20
0
2027-11-03
2027-12-01
FIT-240
Painting L4-L6
Finishes & Decoration
18
0
2027-12-01
2027-12-29
FIT-260
Floor finishes L4-L6
Finishes & Decoration
22
0
2027-12-29
2028-01-28
FIT-310
Reception joinery
Joinery & Fixtures
15
0
2028-01-06
2028-01-27
FIT-320
Toilet vanity install
Joinery & Fixtures
18
0
2028-01-06
2028-02-01
FIT-330
Tea-point joinery
Joinery & Fixtures
12
0
2028-01-13
2028-01-31
FIT-340
Meeting room joinery
Joinery & Fixtures
18
0
2028-01-20
2028-02-15
FIT-350
Built-in storage and fittings
Joinery & Fixtures
15
0
2028-02-03
2028-02-24
FIT-360
Final joinery snagging
Joinery & Fixtures
8
0
2028-02-24
2028-03-07
MS-FIT-END
Fit-out complete
Interior Fit-Out
0
0
2028-03-07
2028-03-07
CMS-210
Client walkthrough and snag list
Snagging & Punchlist
5
0
2028-04-18
2028-04-25
CMS-220
Major snags rectification
Snagging & Punchlist
15
0
2028-04-25
2028-05-16
CMS-230
Minor snags rectification
Snagging & Punchlist
12
0
2028-05-04
2028-05-22
CMS-240
Final inspection
Snagging & Punchlist
4
0
2028-05-16
2028-05-22
CMS-310
Building handover documentation
Practical Completion
8
0
2028-05-18
2028-05-30
CMS-320
O&M manuals issued
Practical Completion
4
0
2028-05-30
2028-06-05
CMS-330
Soft landings start
Practical Completion
3
0
2028-06-05
2028-06-08
MS-PC
Practical Completion
Practical Completion
0
0
2028-06-08
2028-06-08
08
Float analysis
Float analysis measures how much delay each activity can absorb before it pushes the project finish. Activities with zero or near-zero float drive the completion date.
Float distribution
Distribution of total float across incomplete activities. Too many activities with very high float (DCMA §6: > 44 days) often indicates missing successor logic; any negative float means the schedule cannot meet an imposed date (DCMA §7).
Chart colour key (DCMA §6/§7 bands):
Red — activities at immediate risk (negative or zero total float)
Orange — activities with 1–10 working days of float (DCMA's near-critical band)
Blue — activities with comfortable float margins
Grey — excessively high float (over 44 working days), usually signalling missing logic
Note: the cover-page Near-critical activities headline counts activities within the schedule's status cycle rather than the strict 1–10 wd band, so it can include activities that fall in the orange and blue regions of the chart. See METHODOLOGY §5c.2.
Float distribution (counts)
Bucket
Activities
negative
0
0
68
1-10
8
11-44
14
>44
58
09
Recommendations
Actions identified:1Findings-driven go-forward actions. Each recommendation traces to a specific finding, warning, or metric in this report.
Concrete next actions derived from this analysis. Every recommendation below references a specific number, finding, or warning elsewhere in the report — nothing speculative.
Industry precedent (AACE RP 29R-03 §4.3; CIOB Guide §5.5) treats this section as a required deliverable element of any forensic report.
Close the open ends: 1 missing predecessor(s) and 6 missing successor(s) — see DCMA §1 (Logic) in the DCMA 14-Point scorecard above and the Findings table for the affected-activity list. Every incomplete activity should have at least one predecessor and one successor so the critical path is fully driven by logic.
Full forensic record
Forensic appendix
Full evidence, registers, methodology, standards citations.
10
Findings
Findings:15
The analysis identifies fifteen findings, predominantly of informational nature, with three classified as warnings, indicating areas where schedule integrity may be compromised. A central theme across the findings is the maintenance of logical and temporal fidelity within the schedule model, particularly in adherence to established network principles such as those defining the critical path as "the longest sequence of activities from commencement to completion" per the CIOB Guide's §4.29.1. The presence of twelve activities with dangling logic and six without successors raises concerns about network continuity, echoing the CIOB Guide's §4.23.1 caution that open ends should be avoided to ensure reliable float calculations and critical path identification. Multiple findings relate to schedule logic, including nine relationships with positive lag, which the DCMA 14-Point §3 flags as potentially masking discrete work effort that should be explicitly modelled. The warning-level finding regarding fifty-eight activities exhibiting float exceeding 44 working days aligns with DCMA 14-Point §6, where such high float may indicate incomplete logic or an unstable network. No findings are rated as CRITICAL, though the warning-level items collectively warrant reviewer attention to ensure the schedule remains a reliable forecasting and analytical tool.
All findings by severity
Severity
Check
Title
Affected activities
Reference
warning
Float analysis
58 activities with float over 44 days
PRE-230, SUP-310, SUP-320, SUP-330, SUP-410 (full list in Excel appendix)
Logic quality checks assess whether the network is fully driven by sequential dependencies. Gaps, excessive non-FS links, and dangling chains all undermine the critical path calculation.
Relationship type distribution
Type
Count
FS
160
SS
7
FF
0
SF
0
Total
167
FS ratio
95.8%
Open ends
Finding
Count
1 activities with no predecessor
1
6 activities with no successor
6
Other logic-quality findings
Check
Count
Redundant relationships
4
Dangling logic
12
12
Open ends
Activities with missing logic — either no predecessor (nothing must happen before them) or no successor (nothing depends on their completion).
DCMA 14-Point §1 expects fewer than 5% of incomplete activities to have open logic.
Missing predecessors allow an activity to start on the project start date regardless of its true sequencing.
Missing successors mean delay to the activity never flows through to the completion date.
Review each row and confirm with the planner whether the logic gap is intentional.
Activities with open logic
ID
Name
WBS
Issue
Duration (wd)
Float (wd)
ENV-310
External doors install
Windows & Doors
No successor
10
317
EXT-310
Boundary fencing
Boundary Treatments
No predecessor
12
653
FIT-250
Floor finishes L1-L3
Finishes & Decoration
No successor
22
157
MEP-310
Below-slab drainage
Plumbing & Fire
No successor
15
544
PRE-230
Welfare cabins and offices
Site Setup
No successor
7
648
SUP-330
Slab L1 pour
Slab Pours L1-L3
No successor
6
461
SUP-430
Slab L3 pour
Slab Pours L4-L6
No successor
6
425
13
Schedule metadata
Source and calculation
Field
Value
Source format
xer
Data date
2026-01-05
Project start
2026-01-05
Project finish
2028-06-08
Activities
148
Relationships
167
Calendars
1
Scheduling options from the source file. These govern how P6 calculates float and the critical path.
Two options in particular (Progress Override and the 'Include all activities meeting CP definition' flag) can change the reported critical path materially without changing a single activity or relationship.
Any setting that warrants a warning is listed separately in the Findings table above.
Scheduling options
Option
Value
Retained Logic
Yes (ON)
Progress Override
No (OFF)
Include all activities meeting CP definition
No (recommended)
Float type
Finish Float
External-project dependency handling
Apply external dates to both start and finish
Source file
Field
Value
P6 version
22.12
Export date
2026-01-05
14
Excel appendix guide
The accompanying ``.xlsx`` workbook is the audit companion to this PDF. Wherever the PDF says ``full list in Excel appendix``, the matching tab below carries the unabridged data.
The workbook is laid out in two tiers. The first tier (presentation tabs) gives audit-ready tables of milestones, the critical path, ranked float paths, and the full activity register. The second tier (findings-register tabs) drills into each individual finding with affected activities — one tab per finding.
Tier 1 — presentation tabs
Tab
Contents
Summary
Schedule metadata (project dates, activity count) plus every finding with severity, count, and reference. The row to start at when triaging the report.
Key Milestones
The full set of detected key milestones with the detection rationale spelled out (contractual keyword, user-supplied keyword, or critical-path WBS-tail fallback). The PDF body is capped at 15; this tab is uncapped.
Critical Path
Every activity flagged critical by the source scheduling tool, complete and incomplete. The PDF Critical-path section filters to incomplete-only for clarity; this tab is the unfiltered companion.
Float Paths
Every ranked near-critical chain — the full list behind the PDF Float-path risk section's top-5 table. Includes the activity sequence comma-separated for search.
Activities
Every activity in the schedule with predecessors and successors inline. The audit substrate — whatever the PDF Findings table references, look up the activity row here to see its surrounding logic.
Tier 2 — findings-register tabs
Tab
Contents
CP stored vs traced
Activities where the source file's stored critical flag disagrees with ScheduleLens' independent longest-path trace.
CP summary or LOE
Critical activities flagged as summary or level-of-effort — they should not appear on the path since they roll up other activities.
Near-critical activities
Activities within the schedule's status-cycle float band.
Float over threshold
Activities with total float above DCMA §6's 44-day threshold — usually a sign of missing successor logic.
Negative-float activities
Activities with negative total float — the schedule cannot meet its imposed dates without acceleration.
Long-duration activities
Activities with planned duration above DCMA §8's 44-day threshold — candidates to break down further.
Open ends - no predecessor
Incomplete activities with no predecessor — they will start on the project start date regardless of true sequencing.
Open ends - no successor
Incomplete activities with no successor — slip never flows through to the completion date.
Constrained activities
Activities with date constraints applied — these can override logic-driven dates and mask schedule risk.
Out-of-sequence activities
Activities making progress before their predecessors are complete. The Predecessor IDs column lists the specific predecessors that haven't completed yet.
A tab in this tier is created only when the underlying finding has at least one affected activity, so the actual workbook may carry a subset of the rows above.
15
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 §10) 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 §10.4 test asks whether two delays were both critical during their overlap. The engine evaluates this as the union of baseline-side and update-side 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 is outside V1 scope. 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. A V1.1 release will add a cross-period as-built CP synthesis section to the series report Brief layer.
Engine-attributed-vs-observed divergence — the engine's net-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.
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
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.
16
Appendix A — Reference Standards
Each abbreviation used in the Reference column of the findings table maps to the full title below.
These are bibliographic citations indicating the analytical basis for each check. ScheduleLens is not affiliated with, endorsed by, or certified by AACE International, PMI, DCMA, CIOB, or the Society of Construction Law.
Cited standards
Abbrev.
Full title
AACE
AACE International Recommended Practice 29R-03: Forensic Schedule Analysis
CIOB
CIOB Guide to Good Practice in the Management of Time in Major Projects
PMBOK
Project Management Institute — A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 8th Edition, 2025
PMI
Project Management Institute — Practice Standard for Scheduling, 2nd Edition, 2011
DCMA
US Defense Contract Management Agency 14-Point Schedule Assessment
SCL
Society of Construction Law Delay and Disruption Protocol, 2nd Edition