Introduction:
Every construction or engineering project, regardless of scale, faces the same fundamental challenge: too many tasks, too little time, and real consequences when the plan breaks down. The Critical Path Method (CPM) exists precisely to address that challenge. It gives project managers a systematic, logical framework for identifying which sequence of activities determines the earliest possible project completion, and it provides the quantitative basis for every scheduling decision that follows.
Oracle Primavera P6 is the industry standard for implementing CPM on complex projects. Across federal construction contracts, heavy civil work, commercial development, and infrastructure programs, Primavera P6 CPM scheduling is the tool owners and contractors rely on to plan, track, and defend their timelines. Understanding how to identify and manage the critical path within P6 is not optional knowledge for anyone responsible for delivering a project on time.
This guide walks through the full process: how CPM works conceptually, how P6 calculates and displays the critical path, how activity relationships drive schedule logic, how float is computed through forward and backward pass, and how near-critical paths can be surfaced for proactive risk management. Whether you are preparing a baseline schedule for a USACE or NAVFAC submission, managing a commercial development timeline, or defending a delay claim, this knowledge applies directly to the work.
The concepts here are also the foundation of Leopard Project Controls’ approach to construction scheduling services. From baseline schedule development to time impact analysis and recovery scheduling, the critical path is the central organizing principle. Getting it right from the start protects the project, protects cash flow, and protects the contractor’s credibility with owners and agencies alike.
What is the Critical Path Method?
The Critical Path Method (CPM) is the most widely used planning technique in project management, often referred to as critical path planning. It is used to plan and manage a project, calculating the minimum lead time for completion along with the possible start and end times for all project activities.
CPM remains a cornerstone of project planning today. How long a project lasts often depends on its longest chain of dependent tasks. There must be no delay in the activities on the critical path. Any delay to a single activity on that path results in an equivalent delay to the overall project completion date. A fundamental concept to understand is that critical path activities carry zero float. Float is the amount of scheduling flexibility available to an activity such that a delay within that tolerance does not push the project end date. Activities on the critical path have no such tolerance.
In practice, understanding the critical path also means understanding which activities have flexibility and which ones demand tight attention. A well-managed schedule uses that distinction to focus resources, prioritize supervision, and make informed decisions when changes arise.
1. Identification of critical path in Primavera P6
When you have completed the basic planning for a project in Primavera P6, as described in the article on creating a new project in Oracle Primavera P6, follow the steps below to identify the critical path.
First, press F9 and then click the Options button. Find the option “Define Critical Activities as” and choose either “Longest Path” or “Total Float less than or equal to 0.” Then click the Schedule button.
After scheduling, look at the Gantt window. You should now see a red critical path displayed automatically across the bar chart.
The filter function is also a fast and practical way to isolate the critical path on screen. Click the Filters button to enable the critical path filter. There is also a separate filter for the longest path. Applying it shows only the critical activities, hiding everything else. Follow the sequence: Filter > Critical > Apply > OK.
The image below shows the resulting critical path view after the filter has been applied.
One important consideration at this stage is the difference between the two display options. Defining critical activities by total float (equal to or less than zero) can sometimes show activities as critical when they have retained a small amount of positive float due to constraints or out-of-sequence progress. The Longest Path option, by contrast, traces the true driving path from project start to finish regardless of float values. For government contract submissions and forensic schedule analysis, the Longest Path setting is generally the more defensible choice.
2. Activity relationships
The logic of a CPM schedule is built entirely on activity relationships. These relationships define the order in which work must occur and determine how the schedule network flows from start to finish. In Primavera P6, relationships are assigned by navigating to Detail > Relationships > selecting the activity > Predecessor.
To assign proportions to the sample activities (A, B, C, D, E, F, G, H, and J), follow the steps shown in the diagram below.
Highlight the existing activity you want to connect, then select the Relationship tab. To add a successor relationship, click the icon to add a sequel as shown in the following images.
Select the appropriate relationship type from the Relations drop-down based on the actual sequencing logic of the work. P6 offers four relationship types, each representing a different real-world dependency.
Finish-to-Start (FS)
This is the most common relationship type. The successor activity cannot start until the predecessor finishes. A straightforward example: plastering a wall cannot begin until brick masonry on that wall is complete.
Finish-to-Finish (FF)
This relationship links the finish of two activities. The successor activity finishes at the same time as, or after, the predecessor finishes. It is typically used when two parallel work streams must both be complete before the project can advance to the next phase.
Start-to-Finish (SF)
In this relationship, the predecessor activity can finish once the successor starts. It is the least common type and is used for situations such as a design approval activity that can be closed out when material procurement begins.
Start-to-Start (SS)
The successor activity can start as soon as the predecessor starts. This reflects parallel work that can proceed simultaneously. An example: excavation of Building B can begin as soon as excavation of Building A starts.
Lag values can also be applied to any of these relationships to introduce a required waiting period between activities. A positive lag delays the successor; a negative lag, also called lead time, allows the successor to start or finish before the predecessor’s milestone is fully reached. Appropriate use of lags and leads makes the schedule logic more accurate and reduces artificial float throughout the network.
What is float?
In Primavera P6, there are two main float values that project teams monitor: Total Float and Free Float.
Total Float is the amount of time an activity can be delayed without pushing back the project completion date. Free Float is the amount of time an activity can be delayed without delaying the early start of any of its successor activities. The distinction matters when managing near-critical work, because an activity may have significant total float but very little free float, meaning any delay to it will immediately affect downstream activities even if the project finish date is not yet threatened.
Monitoring both float values as a schedule progresses is an important part of proactive project controls. When total float on a path drops below a defined threshold, usually two to four weeks, depending on the project, it signals that the path has become near-critical and warrants closer oversight.
3. Forward pass and backward pass
The critical path is calculated through a two-pass process that traces the network in both directions. The chart below summarizes the differences between the forward pass and the backward pass.
The following two sub-sections explain how each pass works and how P6 applies these calculations within the schedule.
4. Forward pass
The forward pass calculates Early Start (ES) and Early Finish (EF) for every activity in the network. Starting from the first activity, P6 moves forward through each relationship, determining the earliest possible date each subsequent activity can begin and end given its dependencies. The Early Start of a successor is driven by the Early Finish of its predecessor, adjusted for any lag.
The forward pass produces the earliest possible schedule and establishes the minimum project duration. The following diagram shows how this calculation proceeds through the pilot project network.
When an activity has multiple predecessors, its Early Start is set to the latest Early Finish among all of them. This ensures that no activity begins before all of its driving dependencies are satisfied.
5. Backward pass
The backward pass calculates Late Start (LS) and Late Finish (LF) for every activity, working from the project end date back through the network. It determines the latest each activity can start and finish without extending the project beyond its target completion date.
The backward pass results shown in the diagram below illustrate how the Late Start of a successor activity drives the Late Finish of its predecessor. For example, the Late Start of successor activity A1040 sets the Late Finish for predecessor activities A1020 and A1030. Float is then calculated by subtracting Early dates from Late dates: Total Float = Late Start minus Early Start (or equivalently, Late Finish minus Early Finish). Activities where both values are equal carry zero float and are therefore on the critical path.
Understanding both passes is essential for anyone reviewing a schedule or building one for agency submission. Errors in relationship logic, missing predecessors, or open-ended activities will corrupt the backward pass results, produce artificially inflated float values, and make the critical path unreliable.
Longest path and critical path
It is widely accepted across construction, infrastructure, and engineering industries that identifying and following the longest path of a project is the most reliable way to keep the completion deadline in view. CPM scheduling keeps the most important sequence of tasks visible and accountable throughout the project lifecycle.
Primavera P6 gives you two options when displaying the critical path on the Gantt chart. You can display the path of activities with zero total float, or you can display the longest path. These two options are accessed through the scheduling options dialog: F9 > Schedule > Options > Define critical activity.
The zero-float option is intuitive and widely used, but the Longest Path option is generally more accurate on projects with constrained milestone dates or multiple calendars. When a project has date constraints applied to intermediate milestones, some activities may carry negative total float yet not actually drive the project end date. The Longest Path algorithm avoids this ambiguity by tracing only the continuous chain of activities that drives the last activity in the network.
For federal contract submissions, including those reviewed by USACE, NAVFAC, and state DOT agencies, the Longest Path setting is often the preferred approach because it produces a more defensible and logically consistent critical path analysis.
6. Multiple paths in Primavera P6
When filtering a critical path in Primavera P6, the standard view shows only one critical path. On a complicated project with many parallel work sequences, it is often valuable to surface near-critical paths as well, so the project team can monitor activities that are approaching criticality before they become a problem.
The Multiple Float Paths feature in P6 addresses this need. Using the same pilot project, follow these steps:
Press F9 on the keyboard, then click Options.
In the “Display multiple float paths ending with activity” field, select the last activity in the network (in this example, activity J). Click the Advanced tab and check the box for “Calculate multiple float paths.” Choose the number of paths to display. For this demonstration, two paths are selected.
Click Close and then Schedule.
Right-click on the activity table and select Group and Sort.
In the Group and Sort dialog, set Group By to “Float Path” and click OK.
Primavera P6 will then display two separate float paths as follows:
Path 1: A > B > C > E > F > G > J
Path 2: A > B > D > E > F > G > J
This multi-path view is particularly useful for risk management. When the schedule is updated monthly, the scheduler can quickly see whether any previously near-critical paths have converged with the primary critical path due to actual performance or scope changes. Tracking float trends across all near-critical paths is a standard practice in robust construction schedule management.
How Leopard Project Controls applies critical path methodology
Understanding critical path analysis in Primavera P6 is one thing. Applying it correctly under the pressure of real contract requirements, agency review timelines, and active construction is another. That gap between theory and reliable execution is where Leopard Project Controls provides direct value to contractors, owners, and project managers.
Leopard Project Controls is a registered engineering firm and certified general contractor offering Primavera P6 CPM scheduling services across federal, state, and commercial construction projects. The firm’s core services are built around the same principles covered in this guide, applied with construction-first experience and a thorough understanding of what agencies and owners actually require from a submitted schedule.
Baseline schedule development is the starting point. Leopard builds field-informed, specification-compliant CPM schedules that satisfy the submission requirements of USACE, NAVFAC, and state DOT programs, and are delivered within seven business days with unlimited revisions until approved. Every baseline is structured around a valid critical path, with logic-tied activities, properly assigned relationships, and a longest path that accurately reflects the project’s true driving sequence.
Monthly progress updates and reporting keep the schedule current and maintain the integrity of the critical path analysis over time. Each update includes logic-driven schedule recalculation, narrative reporting, and owner-ready submittals. Tracking float trends as the project advances is central to this work, giving the project team early warning when activities approach criticality before they become a schedule problem.
Time Impact Analysis (TIA) and delay analysis services draw directly on the forward pass, backward pass, and float calculations explained earlier in this article. When a delay event occurs and a contractor needs to demonstrate schedule impact and pursue entitlement, the forensic-level P6 analysis Leopard provides relies on the same CPM logic. A defensible TIA requires a credible baseline, accurate as-built data, and a clear narrative connecting the delay event to the critical path. Leopard’s team builds that case with documented P6 methodology.
Recovery scheduling is another area where critical path analysis drives the solution. When a project falls behind, the recovery plan must be built around the current critical path, not the baseline one. Leopard identifies which activities have shifted to near-critical or critical status, develops realistic catch-up strategies, and produces an updated schedule that is both executable in the field and acceptable to the reviewing agency.
For owners and developers, Leopard also provides owner’s representative scheduling support and owner’s scheduling consultant services, offering an independent review of contractor-submitted schedules, verifying that the critical path logic is sound, and flagging risks before they become disputes. This layer of independent oversight is particularly valuable on public sector projects where schedule compliance carries contractual and financial consequences.
Whether the need is a first-time baseline submission for a federal contract, ongoing schedule management through construction, or forensic analysis after a project dispute, Leopard Project Controls brings the technical depth in Primavera P6 and the construction knowledge to make CPM scheduling work as intended.
Conclusion
The critical path is the backbone of every well-managed construction schedule. It defines the minimum project duration, identifies the activities where delay has the greatest consequence, and provides the analytical foundation for everything from baseline development to delay claims. Understanding how to identify, calculate, and monitor it in Oracle Primavera P6 is a core competency for anyone serious about project controls.
This article has covered the full scope of that knowledge: the conceptual basis of CPM scheduling, the step-by-step process of identifying the critical path in P6 using filters and scheduling options, the four relationship types that govern schedule logic, the distinction between total float and free float, the forward and backward pass calculations that produce early and late dates, the difference between the zero-float and longest-path display options, and the multi-path functionality that surfaces near-critical sequences for proactive risk management.
A few key principles deserve emphasis as takeaways. First, the higher the number of critical and near-critical paths in a schedule, the greater the schedule risk. When multiple paths converge on the same milestone, any one of them can become the new critical path if its activities slip. Second, float is a risk indicator that must be monitored across the entire network, not just on the critical path itself. Third, the choice between the zero-float definition and the Longest Path definition of criticality matters significantly on complex projects with constrained milestones, and the Longest Path setting is generally the more defensible standard for agency submissions.
For contractors working on federal and state contracts, schedule compliance is directly tied to payment, claims resolution, and long-term reputation with agencies. A properly structured CPM schedule in Primavera P6 is a project management asset that enables better decisions, earlier identification of problems, and a stronger position in any dispute.
For project owners and developers, an independently verified critical path gives confidence that the contractor’s submitted schedule reflects real construction logic and that the project team has a credible plan for meeting milestones. The value of that confidence is difficult to overstate when a project is under financial pressure or subject to liquidated damages.
The Critical Path Method, applied correctly in Primavera P6, is one of the most powerful tools available to the construction industry. Mastering it, or partnering with a firm that has already done so, is a practical advantage on every project where schedule performance matters.
Q&A
What is the difference between the critical path and the longest path in Primavera P6?
The critical path, when defined by zero total float, includes all activities that cannot be delayed without extending the project. The longest path is the continuous chain of activities that drives the project’s last completion date, regardless of float values. On projects with date constraints applied to intermediate milestones, some activities may show negative float without actually driving the end date, which can make the zero-float definition misleading. The longest path algorithm avoids this issue and is generally the preferred setting for government contract submissions and forensic schedule analysis.
How does float affect the critical path, and why does it matter for construction scheduling?
Float quantifies the scheduling flexibility of an activity. Total float measures how long an activity can slip before it pushes the project completion date. Free float measures how long it can slip before it delays a successor. Activities with zero total float are on the critical path; any delay to them directly delays the project. Float erosion across near-critical paths is one of the most important early-warning signals in construction schedule management. Monitoring float trends during monthly updates is a standard part of professional project controls practice, and it is central to how Leopard Project Controls manages ongoing schedule update support for its clients.
Why do federal agencies like USACE and NAVFAC have specific Primavera P6 schedule requirements?
Federal agencies rely on CPM schedules as a contractual management tool, not just a planning document. A properly developed Primavera P6 baseline schedule allows the agency to verify that the contractor’s plan is realistic, that the critical path is logical, and that the schedule supports the payment milestones outlined in the contract. Deficiencies in schedule logic, missing predecessor relationships, or unsupported activity durations can result in rejection and delay the contractor’s ability to bill. Agencies like USACE, NAVFAC, and state DOT programs have developed specific submission standards over decades of managing complex capital programs, and compliance with those standards is a prerequisite for keeping the project moving forward.
When should a contractor use multiple float paths in Primavera P6?
Multiple float paths are most valuable on projects with complex network logic, many parallel work sequences, or aggressive schedules where several paths are competing for criticality. Displaying two to four float paths allows the scheduling team to monitor which sequences are approaching zero float before they become critical, enabling proactive intervention rather than reactive recovery. It is also useful when preparing a time impact analysis, as surfacing near-critical paths can demonstrate that a delay event affected not just the primary critical path but also compressed the available float on secondary paths, which may strengthen the contractor’s entitlement argument.
How does Leopard Project Controls help contractors manage the critical path on active construction projects?
Leopard Project Controls supports contractors through every phase of schedule management. From building the initial baseline schedule in Primavera P6 to conducting monthly progress updates, preparing time impact analyses, and developing recovery schedules when projects fall behind, the firm’s services are structured around maintaining a credible, defensible critical path throughout the project lifecycle. Schedules are built to meet USACE, NAVFAC, and DOT specifications and are delivered within seven business days with unlimited revisions. For contractors who do not have in-house Primavera P6 expertise, partnering with Leopard provides the scheduling capability needed to meet agency requirements, protect cash flow, and manage delay risk effectively.
Contact Leopard Project Controls for your next construction scheduling project.
Email: info@consultleopard.com | Phone: (833) 777-6276 | Website: consultleopard.com
