DCMA 14-Point Schedule Assessment: What the Checks Mean and What They Do Not
The DCMA 14-point assessment is widely used as a structured way to screen schedule quality. It is useful because it forces attention onto common schedule weaknesses, but it should not be treated as a substitute for project-specific planning judgment or forensic delay analysis.
What the assessment is trying to reveal
The checks look for schedule characteristics that can reduce reliability, such as missing logic, leads, excessive lags, hard constraints, high float, negative float, long durations, invalid dates and progress-related anomalies. Together they provide a repeatable health screen.
Why context still matters
A metric can fail for a legitimate project reason, and a schedule can pass several checks while still representing the work poorly. Calendar structure, contractual milestones, access restrictions, engineering and procurement interfaces, commissioning logic and update rules all need project-specific interpretation.
Baseline-dependent measures need baseline evidence
Some performance-oriented checks require approved baseline information. A single current XER cannot create evidence that is not present. Good schedule assurance should clearly mark a metric as unavailable rather than invent a result from incomplete data.
Use the results to improve the network
The most useful outcome is a prioritized correction list: repair broken logic, review constraints, investigate negative float, split unrealistic long activities and reconcile progress. ORQIV's public DCMA 14 Lite tool is intentionally a screening layer; deeper planning control belongs inside the governed PCS workflow.
Move from guidance to governed workflow.
ORQIV publishes practical project-control guidance publicly while keeping customer data, proprietary algorithms and private implementation details inside the governed product boundary. Review methodology is documented in the Editorial Policy.