Redundant logic: the invisible noise that weakens your schedule as evidence

Your schedule is, most likely, the most important piece of evidence you'll have in a delay dispute. And yet, almost every complex schedule carries a silent defect that erodes its credibility: redundant logic relationships.

A redundant relationship is a link between two activities that adds nothing, because the sequence is already defined by another path in the network. It doesn't change the dates. It isn't visible at a glance. But it pollutes the logic, distorts critical-path traceability and weakens the evidentiary value of the schedule exactly when you need it most.

What exactly is a redundant relationship

The example is simple and appears, identical, in the two most cited reference manuals in the world. If activity A precedes B, and B precedes C, then the sequence A → C is already guaranteed. Adding a direct A → C link on top adds no information: it's redundant.

That's how the NASA Schedule Management Handbook defines it, classifying redundant logic as a topological health problem of the schedule:

"A redundant link occurs when, in addition to the link in question, there is a more detailed logic link between the same two activities. (…) It also makes logic traceability, such as critical path traces, more difficult for schedule assessment and analysis." NASA — Schedule Management Handbook, "Redundant Logic" section

The GAO (the U.S. Government Accountability Office), in its Schedule Assessment Guide, elevates it to a formal best practice:

"…the network should be clear of redundant logic. Redundant logic represents unnecessary logic links between activities. For example, a sequence of activities A, B and C with finish-to-start logic has no need for an additional finish-to-start link between A and C." GAO — Schedule Assessment Guide (GAO-16-89G), Best Practice 2

And it isn't only Anglo-American doctrine. The Spanish-language technical literature states it with the same clarity:

"Redundant connections add no information to the network and only increase the calculation effort." Métodos de planificación y control de obras

Why it matters: traceability and the critical path

A redundant link "does no harm" to the dates, but it does harm something more valuable: the ability to trace and demonstrate why the project will finish when it finishes.

The GAO is categorical about the importance of sound network logic:

"Any missing or incorrect logic relationship is potentially damaging to the entire network. Complete network logic between all activities is essential if the schedule is to correctly forecast the dates." GAO — Schedule Assessment Guide (GAO-16-89G)

Traceability —being able to trace, horizontally and vertically, how each activity connects to the outcome— is one of the pillars of reliability according to the GAO. And NASA explicitly says that redundancy makes those critical-path traces harder. In other words: every redundant link is noise standing between you and a clear explanation of your schedule.

The point that changes everything: the schedule as evidence

This is where redundant logic stops being a technicality and becomes an economic risk. In an extension-of-time claim, the schedule is the time model that demonstrates the cause-and-effect relationship between an event and the delay. If that model isn't sound, it demonstrates nothing.

The CIOB (Chartered Institute of Building), in its Guide to Good Practice in the Management of Time in Complex Projects —a global reference in forensic delay analysis—, leaves no room for doubt:

"The integrity of the schedule is of paramount importance in predicting consequences (…). If the schedule does not react logically, the calculation it produces will be of little help in identifying cause and effect, or in predicting the future conduct of the work." CIOB — Guide to Good Practice in the Management of Time in Complex Projects (§3.8.66.4)

And the GAO sums it up in a sentence every project director should keep in mind:

"The reliability of the schedule determines the credibility of the forecasted dates." GAO — Schedule Assessment Guide (GAO-16-89G)

A schedule loaded with redundant logic is harder to audit, harder to explain and easier for the opposing expert to challenge. A clean schedule is a defensible schedule.

So why does almost nobody fix it?

For a very simple reason: until now it was humanly impossible.

In a schedule with thousands of activities and tens of thousands of relationships, determining which links are redundant means comparing every relationship against all possible paths in the network —a graph transitive-reduction analysis—. It's a task no planner can do by hand, which is why not even the most widely used audit standards included it in their checks. Not because it didn't matter, but because there was no way to tackle it at that scale.

What you should do now

• Assume your schedule has them. Across 67 schedules processed, 19% of relationships turned out to be redundant: nearly 1 in 4. On complex projects it's the norm, not the exception —it accumulates with every update.
• Include it in your quality control. Alongside missing logic, constraints and lags, redundancy should be part of every schedule-integrity review.
• Clean it before it becomes evidence. The best baseline is the one that's clean from day one; don't wait for the dispute to discover the noise.