Redundant Logic Explained

In project scheduling, relationships define the flow of work. But adding too many links can backfire.

Example:

• Activity A → Activity B → Activity C. By definition, C already comes after A (through B). Adding a direct link A → C is redundant logic.

Why avoid it?

• It adds no value—C’s dates are already driven by B (and B by A).

• It complicates updates. If site conditions change (e.g., floor before ceiling due to delays), redundant links can lock you into sequences that no longer reflect reality. This causes misleading and inaccurate delays.

• Baselines should stay clean. Extra relationships make schedules harder to adjust when assumptions shift.

👉 Best practice: Keep relationships simple and necessary. Avoid redundant links in your baseline which ensures flexibility and clarity when the schedule evolves.