Schedule
The critical path schedule, built and run in the platform. Durations are workdays on the project calendar. Every change re-runs the schedule; publishing an update keeps a snapshot so any finish that moved goes to the delay log. P6 files still import on the upload page and export from here.
Data date
2026-10-21
Source: project
Project finish calc
2026-10-07
early finish of the last activity
Source: activity
Against baseline calc
1 d late
baseline 2026-10-06, set 2025-12-17 by Jordan Pike, PM
Source: baseline_activity
Critical activities
0
total float 0 or less
Source: activity
Working over each other calc
stacked crews or lifts over a crew
Source: activity, overhead_clearance
Last run
2026-10-22 13:35
by Jordan Pike, PM
Source: schedule_run
Schedule check: 9 of 11 pass
Quality checks in the spirit of the DCMA 14-point assessment, over 165 activities and 317 relationships. Percent is of unfinished activities (of relationships for the finish-to-start check).
| Check | Count | % | Limit | Result | Activities |
|---|---|---|---|---|---|
| Missing logic (no predecessor or no successor) Every activity needs a predecessor and a successor so delays flow through the schedule. | 0 | 0.0 | 5% | PASS | |
| Leads (negative lags) Leads hide overlap; break the work into activities instead. | 0 | 0.0 | 0% | PASS | |
| Lags Lags are waiting time nobody manages. | 3 | 300.0 | 5% | FAIL | EN020, EN070, EN080 |
| Relationships that are not finish-to-start Keep most logic finish-to-start. | 14 | 4.4 | 10% | FAIL | EN030, EN060, EN070, EN080, FB110, FB110, FB110, FB110, FB110, FB110, FB110, PR080, SY030, SY040 |
| Hard constraints Hard constraints stop the logic from moving dates. | 0 | 0.0 | 5% | PASS | |
| High float (over 44 workdays) High float usually means missing logic. | 0 | 0.0 | 5% | PASS | |
| Negative float The schedule cannot meet a constraint date. | 0 | 0.0 | 0% | PASS | |
| Long durations (over 44 workdays) Long activities are hard to manage; split them. | 0 | 0.0 | 5% | PASS | |
| Actual dates after the data date Progress is only reported up to the data date. | 0 | 0.0 | 0% | PASS | |
| Out of sequence (started before a finish-to-start predecessor finished) Fix the logic or the progress so the schedule shows what really happened. | 0 | 0.0 | 0% | PASS | |
| Should have started before the data date Run the schedule after updating progress. | 0 | 0.0 | 0% | PASS |
Source: activity, activity_rel