Dangling Activities

What it is:
These are activities missing a logical predecessor (SS or FS) or successor (FS or FF). They “float” without being tied into the schedule network.

Why it’s a Problem:
Dangling logic weakens the schedule’s analytical power. Critical path calculations become unreliable, gaps appear in sequencing, and delays can hide because activities aren’t fully connected to downstream work.

Best Practice:
Every activity should have at least one predecessor and one successor, except true start/finish points. Fully connect your logic so the schedule behaves as a real network, not a loose list of tasks.