A tidy Gantt can conceal a weak schedule. Check whether activities have the predecessors and successors their work requires. Look for unexplained leads, long lags, date constraints, very long activities and unusually high float. These are prompts to investigate, not proof that a schedule is unusable. An approved start or finish milestone naturally has an open end.
Schedule assessment checklists, including the DCMA approach, help you ask the same questions consistently. Their thresholds need context. This editor calculates network dates and float without hard date constraints, so it cannot generate negative float against an imposed deadline. The external audit record supplies that case explicitly. Test a copy of the plan by extending a critical activity, then see whether the computed project finish responds as expected.
A missing-logic measure followed by a review of the actual dependencies.