IMS critical path analysis identifies the sequence of remaining activities that drives a program completion date or another key milestone. To perform it correctly, update the Integrated Master Schedule (IMS) through a common status date, recalculate the network, trace the driving logic to the target milestone, and validate the resulting path against constraints, calendars, float, resources, and technical reality.
Do not stop after applying a software filter labeled “Critical.” That filter may show low-float activities without proving which sequence actually drives the milestone. A professional analysis explains the path, confirms why each activity drives its successor, identifies emerging threats, and gives management a decision-ready forecast.
What the Critical Path Means in an IMS
The critical path is the logically connected sequence of activities that determines the earliest calculated completion of the project or selected milestone. If remaining duration increases on a driving activity, and no offsetting recovery occurs, the driven completion date moves later.
However, several related terms require careful distinction:
- Critical path: The controlling sequence through the schedule network, commonly associated with the least total float.
- Longest path: The continuous sequence of driving activities from the current status point to the selected completion milestone.
- Lowest-float path: Activities or chains with the smallest total float values. Constraints can cause this path to differ from the true driving path.
- Near-critical path: A secondary path with limited float that could become controlling after a modest delay.
- Driving predecessor: The predecessor that directly controls the calculated start or finish of its successor.
The GAO Schedule Assessment Guide recommends examining the longest path and activity drivers rather than relying only on activities marked critical by scheduling software. Constraints and incomplete logic can distort float, so the lowest-float activities may not drive the program finish.
Prepare the IMS Before Analyzing the Critical Path
Critical path analysis is only as credible as the schedule network. Therefore, first confirm that the IMS represents the current execution plan.
Establish a valid status date
All progress must reflect the same data date or status date. Actual starts, actual finishes, remaining durations, and forecast dates should be current through that point. Future work should remain on or after the status date unless the scheduling method and approved procedures explicitly permit another treatment.
If the data date is unclear, review what the IMS status date controls. Then follow a disciplined process to status the Integrated Master Schedule before calculating the path.
Check the network fundamentals
Before trusting the result, review the following conditions:
- The IMS includes the remaining contractual and program scope.
- Activities have valid predecessors and successors, except for legitimate start and finish points.
- Durations reflect the current execution estimate.
- Relationship types and lags represent real dependencies.
- Calendars reflect actual working periods and planned availability.
- Hard constraints do not override logic without a documented need.
- Completed work has accurate actual dates.
- In-progress activities have realistic remaining durations and forecast finishes.
- External dependencies connect to appropriate interface milestones.
- The selected completion milestone has a complete path back to the status date.
A path cannot reveal missing work. It can only calculate through the activities and relationships present in the file. A well-organized IMS aligned with the Work Breakdown Structure also makes path ownership and scope validation easier.
How to Perform IMS Critical Path Analysis
1. Define the milestone being analyzed
Start with a specific endpoint. The overall contract completion milestone may be the primary target, but management often needs separate analysis for first article delivery, Critical Design Review, qualification completion, software release, test readiness, or another major event.
Record the milestone identifier, current forecast date, baseline date, and any contractual or management date. This prevents analysts from discussing “the critical path” while tracing different endpoints.
2. Recalculate the schedule network
Run the scheduling engine after status entry and approved forecast changes. Confirm that the correct data date, calendars, calculation options, and project settings are active.
The forward pass calculates early dates. The backward pass calculates late dates and float against the schedule’s finish conditions. However, target dates and constraints may affect those calculations. Therefore, review the configuration before interpreting total float.
3. Identify the driving sequence
Begin at the target milestone and trace its controlling predecessor backward. Continue through each driving relationship until the path reaches the status date, an in-progress activity, or a valid external starting point.
Next, inspect the path forward. Confirm that every relationship transmits schedule movement toward the target. A collection of red bars or zero-float activities is not necessarily a continuous path.
For each activity, capture at least:
- Activity ID and description
- Responsible control account or organization
- Current start and finish
- Remaining duration
- Total float
- Driving predecessor and successor
- Relationship type and lag
- Calendar
- Constraint or deadline, if present
4. Test the path for continuity and credibility
Read the path as an execution story. The sequence should make technical sense to the Control Account Managers (CAMs), Integrated Product Team leads, and program manager.
Ask practical questions. Can environmental testing begin immediately after hardware assembly? Does the test procedure require approval first? Is customer-furnished equipment available before integration? Does software need to reach a defined maturity before system test?
If the schedule says “yes” but the team says “no,” the network may omit scope or logic. Correct the model through normal schedule change control rather than accepting a mathematically valid but operationally false path.
5. Examine constraints, lags, and calendars
Constraints can create negative or zero float without identifying the sequence that drives completion. They can also interrupt the backward pass. Review each constraint on or near the path and determine whether it represents a real external restriction, an approved planning assumption, or an unnecessary date override.
Also inspect long lags. A lag may represent curing, transport, or another legitimate waiting period. However, an activity often provides better visibility when work or accountable elapsed time must be monitored.
Finally, compare calendars across the path. A five-day engineering calendar, seven-day test calendar, and limited-shift supplier calendar can produce unexpected date behavior. Calendar differences may also explain why activities with similar durations do not move together.
6. Analyze float and secondary paths
Total float indicates how much an activity or path may move before it delays the applicable completion condition. Negative float indicates that the calculated network cannot meet a constraint or target under the current plan.
Do not interpret float as owned contingency. Multiple activities on the same path may share the same float. Consuming five days on one activity does not leave every other activity with an independent five-day allowance.
Next, review near-critical paths. Use a program-defined threshold based on schedule duration, update frequency, risk, and management needs. For example, a team may review all paths within 20 working days of the controlling path. That threshold is a management practice, not a universal regulatory value.
7. Compare the path with the prior update
A current snapshot shows where the program stands. Period-over-period analysis explains how it got there.
Compare the current and prior paths to determine:
- Whether the driving sequence changed
- Which activities gained or lost float
- Which remaining durations increased
- Whether late status or logic changes caused the movement
- Whether a secondary path became controlling
- How much the target milestone moved
- Whether approved recovery actions produced the expected result
Preserve the prior-period file or an approved schedule extract. Otherwise, the team may struggle to distinguish performance-driven movement from modeling changes.
8. Convert the analysis into management action
A useful critical path narrative should state:
- The target milestone and its forecast date.
- The major work sequence currently driving that date.
- The change since the prior reporting period.
- The cause of any delay or float erosion.
- The responsible organization or CAM.
- The planned corrective action.
- The date when management will know whether the action worked.
Avoid statements such as “testing remains critical.” Instead, explain which test, what predecessor controls its start, how much duration remains, and which decision could improve the forecast.
Practical Example: Falcon Ridge Sensor Upgrade
Consider a fictional defense electronics program developing an upgraded airborne sensor. The IMS shows an October 30 qualification-complete milestone.
The scheduler traces the following driving sequence:
- Complete receiver redesign
- Release production drawings
- Fabricate prototype receiver
- Integrate prototype sensor
- Complete environmental qualification
- Close qualification discrepancies
- Achieve qualification-complete milestone
During the August update, receiver redesign gains ten working days of remaining duration because of an unresolved thermal issue. The qualification milestone moves ten days, indicating that no downstream float absorbs the delay.
However, the scheduler also finds a software verification path with only three working days more float than the hardware path. Compressing receiver fabrication by five days would not automatically improve the final milestone by five days. The software path could become controlling after three days of hardware recovery.
The management recommendation is therefore specific: resolve the thermal decision by August 28, evaluate a second prototype fabrication shift, and accelerate two software verification procedures in parallel. The analysis addresses both the current driver and the path most likely to replace it.
Using Microsoft Project and Deltek Open Plan
Microsoft Project
In Microsoft Project, display critical tasks in the Gantt Chart and add fields such as Total Slack, Start, Finish, Remaining Duration, Constraint Type, and Deadline. Microsoft’s guidance for showing the critical path in Project also explains that the critical-task threshold can include tasks with a defined amount of slack.
That threshold changes which activities Project labels critical. It does not repair missing logic or prove that every displayed activity belongs to one continuous driving path. Therefore, trace task drivers to the target milestone and inspect the dependency chain.
Deltek Open Plan
In Open Plan, run Time Analysis to calculate early dates, late dates, and float. Then use Schedule Driver Analysis to identify the activities driving a selected target and other potentially controlling chains.
Open Plan can distinguish critical, most critical, and controlling critical conditions. Even so, the scheduler must still validate calendars, target dates, constraints, progress, and the technical sequence.
Critical Path Analysis and EVMS Requirements
Critical path analysis supports reliable schedule forecasting, Integrated Baseline Reviews, risk discussions, and corrective-action planning. It also helps CAMs understand whether control account issues threaten contractual events.
However, do not describe every analysis convention as a contractual requirement. When included in a DoD contract, DFARS 252.234-7002 requires an Earned Value Management System (EVMS) and management procedures that generate timely, reliable, and verifiable information for applicable performance and IMS data items. The contract, Contract Data Requirements List, data item description, agency direction, and approved system description determine the specific deliverables and processes.
Likewise, the NASA schedule management overview describes a logic-network schedule developed with the Critical Path Method as a foundation for planning and management decisions. NASA guidance does not automatically become a requirement on a DoD contract.
For broader context on schedule and EVMS integration, see the complete guide to the DoD Integrated Master Schedule and the process for building an Integrated Master Schedule.
Common Critical Path Analysis Failures
- Filtering only on zero float: The resulting list may contain disconnected activities or constraint-driven dates.
- Analyzing stale status: Incorrect actuals and remaining durations produce an obsolete path.
- Ignoring near-critical paths: Recovery on the current path may simply expose another driver.
- Accepting unexplained constraints: Hard constraints can distort float and hide the natural network result.
- Reporting only activity names: Management needs causes, effects, ownership, and decisions.
- Treating float as contingency: Shared path float is not an independent allowance for every activity.
- Ignoring resources: A logic-driven forecast may remain infeasible if critical resources are unavailable.
- Failing to preserve prior files: Without change history, analysts cannot explain why the path moved.
IMS Critical Path Analysis Checklist
- Confirm the target milestone.
- Validate the status date and progress.
- Recalculate the IMS with approved settings.
- Trace the driving path backward and forward.
- Verify path continuity.
- Review constraints, lags, calendars, and external links.
- Validate the sequence with CAMs and technical leads.
- Assess total float and negative float.
- Review near-critical and secondary paths.
- Compare the path with the prior update.
- Document milestone impact, root cause, owner, and recovery action.
Frequently Asked Questions
Can an IMS have more than one critical path?
A schedule can contain multiple zero-float or near-critical chains. However, one sequence generally controls a selected completion milestone at a given calculation point. Analyze secondary milestone paths as well as the overall program completion path.
Is the critical path always the path with zero total float?
No. Zero or lowest float often identifies critical work, but constraints, deadlines, calendars, and incomplete logic can separate the lowest-float path from the true driving path. Trace activity drivers to confirm the continuous sequence.
How often should the critical path be analyzed?
Analyze it during every formal status cycle and whenever a major technical, scope, logic, or forecast change occurs. High-risk programs may also monitor selected driving paths between reporting periods.