Predecessors Later than Milestones

What it is:
This occurs when a predecessor activity is scheduled to finish after the milestone it’s supposed to support. In other words, your milestone says “we’re done,” but a predecessor is still working in the background.

Why it’s a Problem:
This breaks the logic of the schedule. It sends mixed signals about what’s required to hit a milestone, making it harder for teams to understand what drives key dates. It can also distort your critical path and create reporting inconsistencies.

Best Practice:
Make sure every milestone is anchored by predecessors that finish before it begins. A milestone should represent a genuine “moment of completion,” not a placeholder that ignores remaining work. Consistent sequencing keeps the schedule believable and defensible.