An open-ended activity is missing logic at one end. With no predecessor, nothing but a constraint or the data date fixes its start. With no successor, nothing downstream depends on its finish, so it can slip without moving any later date. Its float is then measured to the project finish and is usually overstated.
Worked example
Illustrative: Install signage has a predecessor but no successor and shows 40 days of total float, because it’s measured against the project finish. In reality it has to be done before the occupancy inspection. Adding that finish-to-start tie brings its float down to 3 days. If P6’s Make open-ended activities critical option is on instead, the untied activity’s late finish is pulled back to its own early finish. Its float becomes zero and it shows on the critical path until someone adds the missing logic.
Why it matters
Open ends hide risk. The DCMA 14-point assessment counts activities with missing predecessors or successors and expects very few. Reviewers treat them as a sign that the network can’t be trusted to show the effect of a delay.
Common mistakes
- Turning on open-ended activities critical to make a report look tighter, instead of adding the missing logic.
- Tying an activity to the finish milestone only to clear the check, when its real successor is a specific piece of work.
- Counting an activity with only a start-to-start or finish-to-finish successor as open-ended. Any relationship type counts as a successor.
How os.construction handles it
The engine’s Make open-ended activities critical follows P6 23.12 as measured on probe projects: an unfinished activity with no successor of any type takes its own early finish as its late finish, and the work driving it follows through the backward pass. Every calculation’s schedule log lists open ends. See P6 compatibility.
FAQ
Why are open-ended activities a problem?
An activity with no successor can slip without moving any later date, so its float is overstated and a real delay stays invisible. The DCMA missing-logic check counts them for that reason.
What does Make open-ended activities critical do in P6?
It gives an unfinished activity with no successor a late finish no later than its own early finish, so its total float is zero or negative and the work driving it shows as critical too. Activities with no predecessor are not affected.
Are the project's first and last activities open ends?
Yes, by definition, and that's expected. A sound network has one start and one finish milestone, and every other activity has at least one predecessor and one successor.