DCMA 14-Point Review of a 4,800-Activity Transit Schedule

Apply the thresholds to the facts, not to the contractor's labels. Missing logic at 8% exceeds the common 5% threshold; 22% lags exceeds the 5% threshold; 180 hard constraints is a material number for a 4,800-activity schedule and exceeds a typical 5% limit (240 would be 5%, but hard constraints should be minimal and justified); 40 activities with negative float exceed the zero-negative-float standard; 4 invalid actual dates fail; no resource loading fails an integrated schedule requirement; 12 activities over 44 working days is 0.25%, below the 5% high-duration threshold, but long-duration activities still need review. High float at 90 activities is 1.9%, below 5%, so not a fail by itself. The 35 open-ended activities are a separate logic failure and must be added to the missing-logic count. The material failures are missing logic, lags, hard constraints, negative float, invalid dates, resources, and open ends. Reject the schedule for acceptance and require correction. The 10-day review window does not justify accepting a known-defective schedule.

A separate spreadsheet is not an integrated schedule. Resource loading must be in the schedule so that the resource histogram, calendars, and activity durations can be validated together; otherwise the schedule cannot support resource leveling or progress analysis. Negative float is never 'only noncritical': negative total float means the activity is forecast to miss a constrained date or the project completion, and it indicates a logic or date conflict that must be resolved. Even if the activity is not on the longest path, negative float can signal a violated constraint or an impossible milestone. The contractor's argument also ignores the 35 open ends: open-ended activities break the logic chain and can hide the true critical path. Acceptance would let a defective schedule become the performance baseline, making future progress and delay claims unreliable.

Remediation plan: (1) correct logic by adding missing predecessors and successors and closing all 35 open ends; (2) replace lags with activities or justify each remaining lag; (3) remove or justify hard constraints, especially those not contractually required; (4) resolve negative float by fixing logic or dates, not by deleting constraints; (5) load resources into the schedule and reconcile the histogram; (6) correct invalid actual dates; (7) review long-duration activities and split where manageable; (8) re-run the DCMA 14-point assessment and submit a corrective action report. Acceptance conditions: missing logic no more than 5%, lags no more than 5%, hard constraints minimal and justified, zero negative float, zero invalid dates, resources loaded, and no open ends. The payment milestone should be released only after the corrected schedule passes the review or a signed corrective action plan with a holdback is in place. If the contractor cannot meet the conditions within the review period, escalate to the contract manager rather than accept the schedule.