A near critical path schedule review identifies sequences of work that could soon control a program completion date or key milestone. These paths have more total float than the current critical path, but not enough flexibility for the program team to ignore them.
Schedulers should monitor more than the current float value. They should also trend float consumption, verify path logic, assess forecast movement, examine resource and risk exposure, and watch for changes in the path that controls each major milestone. Otherwise, a secondary path can become critical before management has time to respond.
Near-critical analysis is a recommended schedule management practice, not a universal contractual rule with one government-wide threshold. The contract, statement of work, Contract Data Requirements List (CDRL), applicable Data Item Description (DID), agency guidance, or approved schedule management plan may establish specific reporting expectations.
What Is a Near-Critical Path?
A near-critical path is a connected sequence of activities with total float close to the float on the current critical path. The NASA Program Planning and Control glossary defines a near-critical activity as one whose total float falls within a narrow range of the critical path.
The critical path usually represents the longest or least-float path that controls program completion. Near-critical paths are the next most time-sensitive sequences. If work on one of those paths slips, consumes float, or encounters a risk, it can overtake the current critical path.
However, a list of low-float activities is not automatically a near-critical path. A path must follow valid network logic through related activities. Therefore, the scheduler must trace the predecessor and successor chain to the applicable completion milestone.
Near-critical paths versus driving paths
A near-critical path generally refers to a path approaching criticality for program or project completion. A driving path controls an interim event, such as a Critical Design Review, test readiness milestone, subcontract delivery, or production start.
The distinction matters because a path can drive an important interim milestone without appearing near the top of a project-wide total-float sort. For that reason, a sound critical path analysis in an Integrated Master Schedule should examine both the program finish and selected contractual or management milestones.
How to Define a Near Critical Path Schedule Threshold
There is no universal rule that defines a near-critical path as five, ten, or twenty working days of total float. The NASA Schedule Management Handbook recommends identifying near-critical and driving paths using a minimum total-float threshold determined by program management. It also notes that programs commonly track several leading paths.
The threshold should reflect the program rather than scheduler preference alone. Consider:
- Status frequency: A monthly update cycle provides less reaction time than a weekly cycle.
- Management response time: Some recovery actions require authorization, engineering analysis, procurement lead time, or customer coordination.
- Remaining program duration: Ten days of float has a different meaning on a four-month effort than on a five-year development program.
- Milestone importance: A contractual delivery or major test event may justify a wider monitoring band.
- Duration uncertainty: Paths containing immature design, supplier, integration, or test work may need attention even when they have more float.
- Calendar structure: Float values based on different activity calendars may not represent equivalent elapsed time.
A practical approach is to establish monitoring bands. For example, the team might classify the least-float path as critical, paths within an approved low-float range as near-critical, and other paths as watch paths when risk or resource exposure warrants attention. Document the threshold and use it consistently.
Do not change the threshold each month merely to produce a convenient report. Instead, revise it only when program conditions justify the change, and record the rationale in the schedule basis or schedule management plan.
What Schedulers Should Monitor on Near-Critical Paths
1. Total float and float trend
Total float shows how long an activity can move before it affects the applicable completion date, subject to the schedule model’s logic, constraints, calendars, and calculation settings. More importantly, the direction of travel shows whether the path is becoming more or less threatening.
The GAO Schedule Assessment Guide recommends comparing near-critical paths and total float with prior schedule updates. Decreasing float indicates that the path may soon become critical.
Report the current total float, prior-period total float, and change during the period. Also explain the cause. A loss of five days due to verified supplier performance differs from a five-day change caused by revised logic or a calendar correction.
2. Forecast movement at the target milestone
Float alone does not tell the full story. Review the current forecast, baseline date, contractual date, and any approved forecast target for the milestone that the path supports.
A near-critical path may retain positive float while its target milestone continues to move later. Conversely, a path may lose float because another path improved rather than because its own work slipped. The scheduler should explain both the absolute forecast movement and the relative float position.
3. The activity currently driving each handoff
Identify the activity that directly controls the next key handoff on each monitored path. Then confirm that the predecessor chain reaches completed work or the current Integrated Master Schedule status date.
Management usually needs to know the next actionable driver, not every activity that will occur over the next two years. Highlight near-term engineering releases, material deliveries, decisions, test assets, approvals, and resource-constrained tasks that control the next transition.
4. Path continuity and logic quality
A low float value has little analytical value if the path contains missing logic, inappropriate constraints, unexplained lags, or incorrect status. Trace the path from its target milestone backward through valid relationships.
Check for:
- Open-ended activities or milestones
- Dangling starts or finishes
- Constraints that override network logic
- Long or undocumented lags
- Level of effort activities driving discrete work
- Links that cross work breakdown structure or organizational boundaries without a real technical dependency
- Unexpected gaps between logically connected activities
These conditions can create misleading float or break a path into fragments. Therefore, resolve schedule integrity issues before presenting the path as a reliable management forecast.
5. Status quality and remaining duration
Near-critical path analysis depends on accurate progress. Verify actual starts and finishes, remaining durations, expected completion dates, and out-of-sequence conditions before calculating the path.
Activities should reflect realistic forecasts as of the status date. Do not retain an obsolete remaining duration simply because the Control Account Manager (CAM) did not submit a new estimate. Instead, reconcile the forecast with the responsible technical team and document significant changes through the program’s normal status process.
The practices described in how to status an Integrated Master Schedule help prevent invalid actual dates and incomplete updates from distorting float.
6. Constraints, deadlines, and calendars
Constraints and target dates can change how scheduling software calculates float. Multiple calendars can also make equal-looking float values difficult to compare.
For example, ten working days on a five-day engineering calendar does not equal ten working days on a seven-day test calendar in elapsed time. A deadline or imposed finish date may also create low or negative float that reflects the target rather than an uninterrupted longest path.
Consequently, each path report should identify significant constraints, deadlines, and calendar transitions. The scheduler should also determine whether the displayed path represents the true network driver or merely the effect of a date restriction.
7. Shared resources and cross-path convergence
Two paths may appear independent in the logic network while competing for the same engineer, test chamber, integration facility, supplier, or review board. This exposure often remains invisible in an unresourced schedule.
Look for points where critical and near-critical paths converge. Also examine scarce resources assigned across several low-float paths. A recovery action that protects one path can unintentionally consume float on another.
Before recommending added resources, confirm that the work can actually be accelerated. Some activities depend on fixed test durations, material cure times, sequential technical decisions, or unavailable specialized staff.
8. Risks, opportunities, and duration uncertainty
Deterministic total float reflects one set of durations and logic. It does not show how often an uncertain path could become critical.
A Schedule Risk Analysis (SRA) can identify activities that appear on the simulated critical path across many iterations. GAO calls this measure risk criticality. A path with moderate deterministic float may deserve more attention than the current critical path if it contains substantial uncertainty or mapped schedule risks.
Therefore, compare near-critical paths with the risk register and SRA results. The analysis should identify the responsible risk owner, potential schedule effect, mitigation activity, trigger date, and decision deadline. For broader context, see proactive program risk management.
Fictional Program Example
Consider Falcon Ridge, a fictional communications payload development program. Its current critical path runs through flight software integration and system qualification testing. The path has zero working days of total float to the contractual delivery milestone.
A second path runs through antenna fabrication, environmental testing, and payload-level integration. At the previous monthly update, that path had 18 working days of total float. It now has nine days.
A simple low-float report shows that the antenna path remains noncritical. However, a useful analysis finds several warning signs:
- The supplier moved the antenna delivery forecast five working days later.
- Environmental testing retained its original remaining duration despite an unresolved fixture problem.
- The antenna and software paths require the same integration team when they converge.
- The next status cycle will occur after the latest date for reserving a backup test slot.
- The SRA shows frequent criticality on the antenna test sequence.
The scheduler should not wait for the path to reach zero float. Instead, the team could confirm the supplier recovery plan, update the test forecast, protect the backup slot, and resolve the integration resource conflict. The program manager can then compare the cost and technical consequences of each option.
This example also shows why float thresholds alone are insufficient. Nine days of float may appear acceptable, but the program has less than nine days to make a key management decision.
Microsoft Project and Deltek Open Plan Practices
Microsoft Project
Microsoft Project calls float “slack.” Its critical path guidance explains that Project normally treats tasks with no slack as critical. Users can change the threshold so tasks with limited slack also receive the Critical flag.
However, changing the software threshold can blur the distinction between the mathematical critical path and management-defined near-critical work. An alternative is to retain the normal critical setting and create a separate filter, group, or custom indicator based on Total Slack, incomplete status, and the selected milestone.
If the team changes the critical-task threshold, disclose the setting in reports. Also remember that a task-level low-float filter does not prove path continuity. Trace the logic before assigning a path number or presenting the sequence to management.
Deltek Open Plan
Deltek Open Plan calculates total and free float during time analysis. Its Schedule Driver Analysis can identify activities driving a selected target and recognize multiple potential controlling chains grouped by total float.
This supports milestone-focused analysis because the scheduler can select a program completion milestone, test event, delivery, or other target. Still, the tool output requires professional review. Validate logic, status, calendars, target dates, and activity types before relying on the reported paths.
Common Near-Critical Path Failure Modes
- Monitoring only zero-float tasks: This gives management little warning before another path becomes critical.
- Reporting a low-float activity list as a path: Activities with similar float may belong to separate logic chains.
- Using one threshold for every program: The appropriate range depends on update frequency, risk, duration, and response time.
- Ignoring prior-period values: A current snapshot does not show the rate of float consumption.
- Accepting tool output without validation: Constraints, missing logic, calendars, and poor status can produce misleading results.
- Focusing only on project completion: Near-driving paths to interim contractual and technical milestones may require earlier action.
- Confusing float with contingency or schedule margin: Float results from network calculations and is shared along a path. It is not automatically management-controlled reserve time.
- Adding resources without checking feasibility: More people do not always shorten technically sequential work.
Near-Critical Paths in EVMS and Program Controls
Near-critical analysis complements Earned Value Management System (EVMS) data. Earned value indicators show cost and schedule performance against the Performance Measurement Baseline (PMB), while network analysis forecasts how remaining work may affect future milestones.
A Control Account Manager can have an unfavorable schedule variance without controlling program completion. Likewise, a near-critical activity may have little current earned value variance but still threaten a delivery because of limited float, future uncertainty, or a shared resource.
For that reason, program reviews should connect schedule paths with control accounts, work packages, risks, corrective actions, and Estimates to Complete. This integration supports a more credible Performance Measurement Baseline.
FAR Part 34 addresses EVMS and Integrated Baseline Reviews for applicable acquisitions, but it does not establish a universal near-critical float threshold. Any binding contractor requirement must come from the applicable contract and incorporated requirements. Agency handbooks and schedule assessment guides provide valuable practices, but teams should not present them as contract clauses unless the contract makes them applicable.
A Practical Monthly Review
For each major completion or delivery milestone, the scheduler should provide a concise view of the current critical path and selected near-critical paths. At a minimum, include:
- The target milestone and current forecast date
- Current and prior-period total float
- Float gained or consumed during the period
- The current driving activity near the status date
- Major logic, calendar, constraint, or status concerns
- Mapped risks and resource conflicts
- Required management action and decision date
- The CAM or organization responsible for the next action
Finally, retain prior-period path reports. Path movement often provides more insight than the current critical path alone. A well-maintained Integrated Master Schedule should give management enough warning to act while real schedule flexibility still exists.
Frequently Asked Questions
How much float makes a path near-critical?
No universal value applies to every schedule. Program management should define and document a threshold based on the update cycle, remaining duration, milestone importance, uncertainty, and time required to implement corrective action.
Can a near-critical path have negative float?
Yes, depending on the schedule’s target dates, constraints, and calculation settings. The critical path may be the path with the lowest float rather than a path with exactly zero float. The scheduler must understand how the software calculated the value.
Should completed activities appear in a near-critical path report?
Completed activities may help explain path history, but management attention should focus on incomplete work and the current driver near the status date. Actual dates must still support a continuous and credible logic trace.