Logic Review: How to Find and Fix Missing Predecessors in P6

Logic errors are among the most damaging problems in a construction schedule — and missing predecessors and successors are the most common logic error of all. An activity with no predecessor can start at any time, regardless of what should come before it. An activity with no successor has no modeled impact on anything downstream.

Both conditions break the CPM network. They inflate float values artificially, make the critical path analysis unreliable, and produce a schedule that looks complete but does not behave like one.

This post explains what missing logic means, how to find it in P6, and how to fix it.

What the DCMA Says About Missing Logic

The DCMA 14-point assessment's first check — Check 1 — is missing logic. The standard threshold is fewer than 5% of activities having a missing predecessor or missing successor.

That threshold is intentionally not zero, because some activities legitimately have limited connections: a project start milestone may have no predecessor, a project completion milestone may have no successor, and a few procurement or administrative activities may have unusual sequencing. The 5% threshold allows for these exceptions while flagging schedules where missing logic is pervasive.

Start and finish milestones are excluded from the missing logic check in Change Inspector's health check, following DCMA guidance — because these milestone types often intentionally anchor the start or end of the schedule with no predecessor or successor respectively.

How Missing Logic Damages Your Schedule

Consider what happens when an activity has no predecessor.

In P6's CPM calculation, an activity with no predecessor is treated as if it can start on the project start date (or the data date, depending on settings). Its float is calculated relative to that unconstrained start. The result is typically very high total float — the activity appears to have enormous schedule flexibility because the CPM engine has no reason to think it needs to finish by any particular date.

This high float is false. In reality, the activity probably has a real predecessor that was simply not entered. The schedule is telling you the activity is not critical when it very likely is.

The reverse problem applies to missing successors. An activity with no successor has no downstream consequence in the CPM model. Delaying it does not delay anything. But in reality, work that has no downstream consequence is rare — there is almost always something that depends on it completing.

Missing logic is therefore not just a data quality problem. It is a schedule reliability problem. A schedule with many activities that have no predecessors or successors cannot be trusted to accurately model project completion risk.

How to Find Missing Logic in P6

Method 1: Run a DCMA Health Check in Change Inspector

The fastest way to identify activities with missing logic is to run a DCMA health check in Change Inspector. The Health Check module's Check 1 card shows the count and percentage of activities with missing predecessors or successors. Clicking the card expands a drill-down table listing every flagged activity — with Activity ID, name, WBS, status, and a detail column indicating whether it is missing a predecessor, a successor, or both.

Export the results to Excel for a complete list you can work from in P6.

Method 2: Use P6 Reports

In P6 directly, you can create a report or layout filter to identify activities with no predecessors or successors:

1. Go to Project > Activities
2. Create a new filter: Activity Predecessor Count = 0 (or Successor Count = 0)
3. P6 does not natively expose predecessor/successor counts as filterable fields in all versions, but you can use a global change or report to identify them
4. Alternatively, use the Check Schedule function under Tools > Schedule in P6 — it flags scheduling issues including open ends

Method 3: Visual Network Review

For smaller schedules (under 300 activities), a visual review of the network diagram in P6 or Change Inspector's Network module can reveal isolated activity nodes with no incoming or outgoing arrows. This is less efficient for large schedules but useful for targeted review of specific WBS areas.

How to Fix Missing Logic

Finding the missing logic is only the first step. The harder work is determining what the correct logic should be.

For Activities with No Predecessor

Ask: what must happen before this activity can start? The answer may be:

• A preceding construction activity in the same WBS area
• A submittal approval or procurement delivery
• A mobilization or access prerequisite
• A project start milestone (for activities that genuinely can start on day one)

If the activity truly has no real-world predecessor other than the project start date, connect it to the project start milestone with a Finish-to-Start relationship. This makes the intent explicit and keeps the activity anchored in the network.

For Activities with No Successor

Ask: what activity depends on this finishing before it can start? The answer may be:

• The next phase of work in sequence
• An inspection or testing activity that cannot occur until the work is complete
• A project completion milestone
• A handover or turnover activity

If the activity genuinely has no downstream dependent — rare for actual construction work — connect it to the project completion milestone. This ensures the CPM engine understands it must finish before the project can close.

Watch for Cascading Float Changes

When you add missing logic, float values throughout the affected part of the network will change. An activity that showed 150 days of float because it had no successor may now show 10 days once its successor is connected. This is the correct behavior — the schedule is now telling you the truth about the constraint.

Run a new schedule comparison after adding the missing logic to see the full effect of the changes across the network.

Preventing Missing Logic in Future Updates

Missing logic tends to accumulate when new activities are added to the schedule mid-project without the discipline of fully connecting them to the existing network. A few practices help:

• Review the DCMA health check at every update. If the missing logic count is growing, new activities are being added without complete connections.
• Add a schedule QA step before each submission. Have the scheduler or a reviewer specifically check that all newly added activities have both predecessors and successors before submitting.
• Use Change Inspector's Relationships tab. When reviewing a schedule update comparison, check for newly added activities (Added badge on the Activities tab) and then verify they appear in the Relationships tab with appropriate connections.