Not a quality flag. A risk indicator. John Jackson explains why too many activities on the critical path mean too much exposure to delay, and shares the range worth aiming for: somewhere between 15% and 35%. Anything higher, and it is time for a review.

Sometimes the logic is right. Sometimes it is hiding missing relationships in plain sight. John Jackson explains how Schedule Validator defines high float, why activities carrying too much float deserve a second look, and how skipping that review is exactly how logic gaps get missed.

A hard constraint pins the date, forces the path, and quietly distorts the entire calculation downstream. John Jackson explains how they affect your critical path, why soft constraints are almost always the better choice, and how to spot when a hard constraint is dragging your schedule score down.

A constraint is not a scheduling tool. It is an override. John Jackson explains what constraints actually do to your critical path, why your dates should come from scope, time, and logic, and when (if ever) constraints belong in your schedule.

A duration with no scope assigned to it. That is the problem. John Jackson explains how lag fits into CPM, why it must be used with discipline, and the rule to follow: lag duration should not exceed half of the predecessor’s duration. Use it where it belongs, and manage it consistently.