In Primavera P6, missing logic, also called open ends, means an activity has no predecessor, no successor, or neither. Apart from the project start and finish milestones, every activity should have at least one predecessor and one successor, and the DCMA 14-point assessment fails a schedule when more than 5% of its incomplete activities have missing logic.
Open ends are fixed by adding the right relationships, not by adding constraints. This guide covers what counts as an open end or a dangling activity, how to find them in P6, and how to fix and verify them.
What are open ends in Primavera P6?
Open ends come in two forms:
- Open start (missing predecessor): nothing drives the activity's start, so P6 schedules it as soon as the data date or a constraint allows.
- Open end (missing successor): the activity's completion drives no later work, so it can slip without moving anything.
Both produce activities that sit loose in the network and undermine the critical path.
What is a dangling activity?
An activity can have a predecessor and a successor and still dangle. A dangling start has no Finish-to-Start or Start-to-Start predecessor driving its start. A dangling finish has no Finish-to-Start or Finish-to-Finish successor driven by its finish. For example, an activity whose only successor is a Start-to-Start link has a finish that drives nothing: extend its duration and no later date moves. The basic DCMA count does not catch these, but a thorough schedule review treats them as logic defects.
What is the DCMA missing logic threshold?
The DCMA logic check counts incomplete activities that are missing a predecessor, a successor or both, normally excluding summary and level of effort activities and the project start and finish milestones. The schedule passes if the result is under 5%. The logic check sits with related relationship checks in the DCMA 14-point assessment:
| DCMA check | Threshold |
|---|---|
| Logic (missing predecessors or successors) | Less than 5% of incomplete activities |
| Leads (negative lags) | 0 |
| Lags | Less than 5% of relationships |
| Relationship types | At least 90% Finish-to-Start |
| Hard constraints | Less than 5% of incomplete activities |
Why do dangling activities break a schedule?
- False float: an activity with no successor takes its float from the project finish, so it shows high total float and hides its real criticality.
- Wrong critical path: without the links, the critical path can skip key work and the forecast completion date is unreliable.
- Poor credibility: reviewers and clients lose confidence in a programme whose activities are not connected.
- Weak resource levelling: resources on unlinked activities can be levelled into the wrong periods, causing overallocation or gaps.
- Unusable for delay analysis: a network that does not represent the planned sequence of work cannot show how a delay event affected completion.
How do you find open ends in P6?
1. Read the scheduling log
In P6 Professional, open Tools > Schedule (F9), tick Log to file and schedule the project, then click View Log. The log lists activities without predecessors, activities without successors, out-of-sequence activities and activities with constraints. It is the fastest built-in check.
2. Add Predecessors and Successors columns
Add the Predecessors and Successors columns to the activity table, then sort or group so blank entries come together. The Relationships tab in Activity Details confirms the links and their types for any single activity.
3. Use Check Schedule in P6 EPPM
The web version of P6 has a Check Schedule function that reports schedule quality measures, including activities missing predecessors or successors, against set thresholds.
4. Trace Logic and the Activity Network
Show Trace Logic in the bottom layout and step through an activity's predecessors and successors. A trace that stops unexpectedly points to an open end. In the Activity Network view, isolated nodes and chains that do not reach the project start or finish are easy to spot.
A schedule-checking tool or a P6 report built on the exported XER can run the same count across the whole programme and also flag dangling starts and finishes.
How do you fix missing logic correctly?
The correct fix is to add logical relationships. Constraints such as Start On or Finish On fix a date but do not connect the activity to the network, and they often create new problems.
- Identify the intended sequence. For each open activity, ask what must happen before it can start and what cannot start until it finishes. Ask the project team where the answer is not obvious.
- Add predecessors. Use Finish-to-Start by default. If a concrete pour must follow rebar installation, the rebar activity is the pour's predecessor.
- Add successors. Every activity except the final milestone needs at least one successor. If an activity is the last in its path, link it to the project finish milestone or the relevant contract milestone.
- Close dangling ends. Where an activity has only a Start-to-Start successor, add a Finish-to-Finish or Finish-to-Start link so its finish drives something. Where it has only a Finish-to-Finish predecessor, add a link that drives its start.
- Use start and finish milestones. Have one project start milestone with no predecessor and one project finish milestone with no successor, and tie the first and last activities of each path to them.
- Keep constraints for genuine dates. Use them only for real contractual or external dates, and record why in the basis of schedule.
Common mistakes to avoid
- Constraints instead of logic: a Finish On constraint on a dangling activity fixes its date but it still drives nothing.
- Overusing Start-to-Start and Finish-to-Finish: they have their place, but DCMA expects at least 90% Finish-to-Start, so use other types only where the work genuinely overlaps.
- Linking everything to the finish milestone: it clears the count but hides the real sequence. Link each activity to the work it actually drives.
- Fixing only one end: both the start and the finish must be tied into the network.
How do you verify the fix?
Reschedule and re-run the log or check to confirm open ends are below 5% of incomplete activities, and ideally close to zero. Then review the critical path and the high float list: activities that showed high float only because they lacked successors should now sit on realistic paths. If the critical path flows through the work you expect, the fix has worked.
Missing logic is more than a DCMA metric. It is a basic flaw that makes the dates, float and critical path unreliable. Building complete logic from the start is part of sound project planning, and it is one of the first things an independent schedule review checks.
