What Is Driving Logic?
Driving logic refers to the specific predecessor relationships that actually control (drive) an activity's calculated dates. In a CPM schedule, an activity may have multiple predecessors, but only one predecessor relationship determines its early start date — this is the driving relationship. The other predecessors are non-driving; they are satisfied before the driving relationship allows the activity to begin.
Understanding driving logic is essential for effective schedule management because it reveals the true chain of dependencies that controls project timing. When you need to accelerate an activity, you must address its driving predecessor — accelerating non-driving predecessors has no effect on the activity's dates. Similarly, when tracing the cause of a delay, you must follow the driving logic path to find the root cause.
Driving logic analysis is closely related to critical path analysis but provides more granular insight. The critical path tells you which activities have zero float; driving logic tells you exactly which relationships connect those activities and control their dates. This distinction matters when schedules have complex logic with multiple relationship types and lags.
How Driving Logic Works
Consider an activity with three Finish-to-Start predecessors: Activity A finishes on day 10, Activity B finishes on day 15, and Activity C finishes on day 12. The successor activity's early start is day 15 (the latest of the three predecessor finish dates, assuming no lags). Activity B is the driving predecessor because it is the one that actually controls the successor's start date.
If Activity A is delayed by 3 days (finishing on day 13), the successor's start date does not change — Activity B is still the driver. But if Activity B is delayed by even 1 day (finishing on day 16), the successor's start immediately moves to day 16. This illustrates why identifying driving relationships is critical for understanding schedule sensitivity.
Driving logic becomes more complex with Start-to-Start and Finish-to-Finish relationships, lags, and calendars. An activity might have its start driven by one predecessor (through an SS relationship) and its finish driven by a different predecessor (through an FF relationship). Both driving relationships must be understood to fully comprehend what controls the activity's dates.
Tracing Driving Logic Paths
A driving logic path is the continuous chain of driving relationships from any activity back to the project start (or forward to the project finish). Tracing this path reveals the complete sequence of activities and relationships that control a specific activity's timing.
To trace a driving logic path forward from an activity: identify the activity's driving successor (the successor whose dates would change if this activity were delayed), then identify that successor's driving successor, and continue until reaching the project finish milestone. This forward trace shows how a delay to the starting activity would propagate through the schedule.
To trace backward: identify the activity's driving predecessor, then that predecessor's driving predecessor, continuing back to the project start. This backward trace reveals the chain of dependencies that determines when the activity can begin — essential for understanding what must happen before the activity can start.
Float Master's driving logic feature automates this tracing process, visually highlighting the driving path for any selected activity. This makes it easy to understand schedule dependencies without manually tracing through complex logic networks.
Driving Logic and the Critical Path
The critical path is the driving logic path with zero total float — the longest path through the schedule that determines the project completion date. Every relationship on the critical path is a driving relationship, and every activity on the critical path is driven by its critical predecessor.
However, driving logic extends beyond the critical path. Every activity in the schedule has a driving logic path, regardless of its float value. Understanding driving logic for non-critical activities is valuable for resource planning, subcontractor coordination, and understanding what would happen if near-critical paths become critical.
When the critical path shifts (due to delays, acceleration, or logic changes), the driving logic paths for many activities may change simultaneously. Regular driving logic analysis helps teams understand these shifts and adjust their management focus accordingly.
Visualize Driving Logic Instantly
Float Master traces and visualizes driving logic paths for any activity in your schedule. Understand what truly controls your dates.
View Pricing →Applications of Driving Logic Analysis
Delay Analysis
In delay analysis, driving logic is essential for determining causation. A delay only impacts the project completion date if it occurs on the driving logic path to the project finish. By tracing the driving path at the time of the delay, analysts can determine whether a specific delay event actually impacted the critical path or was absorbed by float on a non-driving path.
Schedule Acceleration
When schedule recovery is needed, driving logic analysis identifies where acceleration efforts will be effective. Only activities on the driving path to the project finish can be accelerated to recover time. Accelerating non-driving activities wastes resources without improving the completion date.
What-If Analysis
Before making schedule changes, trace the driving logic to understand potential impacts. If you are considering delaying an activity, check whether it is on the driving path to any critical milestone. If you are considering accelerating an activity, verify that it is actually driving its successors — otherwise the acceleration provides no schedule benefit.
Subcontractor Coordination
Driving logic analysis helps subcontractors understand what truly controls their start dates. Rather than looking at a list of predecessors (which may include many non-driving relationships), they can focus on the specific driving predecessor that must complete before they can begin. This clarity improves coordination and reduces scheduling conflicts.
Driving Logic in Complex Schedules
In large construction schedules with thousands of activities and complex relationship networks, manually tracing driving logic is impractical. Multiple relationship types (FS, SS, FF), lags, calendars, and constraints all affect which relationships are driving at any given time.
Furthermore, driving logic can change as the schedule progresses. A relationship that was non-driving at the start of the project may become driving as predecessor activities complete at different rates. This dynamic nature means driving logic analysis should be performed regularly, not just once at project start.
Float Master handles this complexity automatically, calculating and displaying driving relationships for any activity in the schedule regardless of network complexity. Combined with forward path and backward path analysis, it provides complete visibility into schedule logic behavior.
Key Takeaways
Driving logic analysis reveals the true dependencies that control activity dates in a construction schedule. By identifying which relationships are driving and tracing driving paths through the network, project teams can make informed decisions about acceleration, delay mitigation, and resource allocation.
Understanding driving logic is essential for anyone involved in schedule management, delay analysis, or project controls. It transforms schedule data from a static display of dates into a dynamic model of cause and effect that supports proactive project management.