How to Find Tasks With No Predecessor or Successor in Microsoft Project

Why open-ended tasks are a problem

A task with no predecessor can start at any time, and a task with no successor has no downstream consequence in the plan. Either way, the schedule is no longer a connected model. When you change a date or a duration, the effect does not ripple through, so the finish date stops being reliable and the critical path can break. This is exactly what the DCMA logic check looks for, and it allows no more than 5% of tasks to be open-ended.

Method 1: Add the Predecessors and Successors columns

This is the simplest approach and works in every version of Microsoft Project.

1. Open the Gantt Chart view.
2. Right-click a column heading and choose Insert Column.
3. Add the Predecessors column, then repeat and add the Successors column.
4. Scroll down the task list and look for blank cells. A blank Predecessors cell means an open start; a blank Successors cell means an open end.

For a small or medium schedule, this is often all you need. Skip summary tasks and the project start and finish milestones, which are allowed to be open (more on that below).

Method 2: Build a filter for unlinked tasks

On a large schedule, scanning by eye is slow. A custom filter shows only the tasks that need attention.

1. Go to the View tab, click the Filter dropdown, and choose New Filter (or More Filters, then New).
2. Name it something like “Open ends.”
3. Set the condition to Predecessors equals (leave the value blank), then add an Or row for Successors equals (blank).
4. Apply it. Project now lists only the tasks missing a link at one end or the other.

Turn the filter off when you are done to see the full schedule again.

Method 3: Use the Network Diagram view

The Network Diagram view (View tab, Network Diagram) draws each task as a box with lines for its links. Disconnected boxes, ones with no line coming in or going out, are your open ends. This view is slower to scan on a big schedule, but it is the clearest way to see how a section of your logic actually connects, and it is handy for tracing a break in the critical path.

Which tasks are allowed to be open

Not every blank is a problem. Three cases are expected:

• The project start milestone legitimately has no predecessor.
• The project finish milestone legitimately has no successor.
• Summary tasks (the headers) should not carry logic at all; the detail tasks under them do.

Everything else should connect at both ends. A good habit is to end every chain of work at a clear project finish milestone, so nothing dangles.

How to link an open-ended task

Once you have found an open end, fixing it takes seconds:

1. Decide what the task truly depends on (its predecessor) and what depends on it (its successor).
2. Open Task Information for the task, go to the Predecessors tab, and add the predecessor with the right relationship type, usually Finish-to-Start.
3. To add a successor, open the successor task and add this task as its predecessor, or drag a link between the two bars in the Gantt chart.
4. Recalculate (press F9) and confirm the dates now make sense.

Work through the list until only the legitimate exceptions remain. The payoff is a schedule that actually responds when reality changes.

Check your whole schedule at once

Missing logic is the single biggest driver of an unreliable timeline, and it is rarely the only problem in a file. GanttScore reads your Microsoft Project schedule and scores it against the DCMA 14-point standard plus three checks of our own, seventeen in total, in about ten seconds. The free score shows you exactly which checks pass and fail, including logic, and the full report names the specific open-ended tasks and gives you the fix. See the full list of checks, or read about the common mistakes that cause most schedule problems.