To display the Microsoft Project critical path, open the Gantt Chart view, select the Gantt Chart Format tab and check Critical Tasks. Microsoft Project formats critical task bars in red. You can also apply the Critical filter when you need a list containing only critical tasks.
That procedure answers the immediate software question. However, a professional schedule review should go further. Red bars show which tasks Microsoft Project has classified as critical. They do not, by themselves, prove that the schedule contains complete logic or that the displayed chain drives the contractual completion milestone you intend to analyze.
How to Display the Microsoft Project Critical Path
- Open the project schedule.
- Select View and apply the Gantt Chart view.
- Select the contextual Gantt Chart Format tab above the ribbon.
- In the Bar Styles group, check Critical Tasks.
Microsoft Project will display critical task bars in red. Noncritical task bars retain the formatting defined for the current Gantt view. Microsoft documents these steps in its guidance on how to show the critical path in Project.
If the Critical Tasks option appears to have no effect, first confirm that you are working in a Gantt Chart view. Also remember that formatting changes apply to the active view. Formatting one custom Gantt view does not automatically change another view.
Three Useful Ways to Review Critical Tasks
The best display method depends on whether you want to brief the path, inspect its float or troubleshoot the logic.
1. Format critical bars in the Gantt Chart
The red-bar display provides the clearest overview. It lets a scheduler see critical work beside the rest of the schedule while preserving the Work Breakdown Structure (WBS), task dates and surrounding activities.
This view works well for routine status reviews. However, expand the applicable summary tasks before drawing conclusions. A collapsed outline can hide the detailed activities that make up the path.
2. Filter the schedule for critical tasks
To isolate the critical tasks, select View > Filter > Critical. Depending on the ribbon configuration, the filter may appear in the Data group or in a filter drop-down list.
The filter removes noncritical rows from the current display. Therefore, it creates a concise list for review or export. To restore the full schedule, apply the No Filter option.
Use this filtered list carefully. A list of critical tasks may include separate branches, tasks made critical by deadlines or constraints, and tasks associated with different schedule endpoints. The filter identifies tasks with a Critical field value of Yes. It does not arrange them into a verified logic sequence.
3. Use the Detail Gantt and Schedule table
For a more analytical view, select View > Other Views > More Views > Detail Gantt. Then apply the Schedule table from the Tables menu.
The Detail Gantt displays critical tasks and available slack graphically. Meanwhile, the Schedule table provides fields such as Early Start, Early Finish, Late Start, Late Finish, Free Slack and Total Slack. Microsoft provides the detailed procedure in its guidance for showing slack in Project desktop.
For most schedule diagnostics, add these columns to the working view:
- Critical
- Total Slack
- Free Slack
- Predecessors
- Successors
- Constraint Type
- Constraint Date
- Deadline
Together, these fields explain more than bar color alone.
How Microsoft Project Determines Which Tasks Are Critical
The critical path is the sequence of work that controls the calculated project finish. Microsoft Project generally classifies tasks as critical when they have no available slack. The program calculates slack from the early and late dates produced by task durations, relationships, calendars, constraints, deadlines and other scheduling factors.
In simple terms, total slack shows how long a task can slip before it affects the applicable finish date. Microsoft explains the underlying behavior in its overview of how to manage a project’s critical path.
However, several settings and conditions affect the Critical field:
- The critical-task threshold may include tasks with more than zero days of slack.
- A deadline can reduce total slack and cause a task to become critical.
- Inflexible constraints can affect late dates and create critical or negative-slack tasks.
- Completed tasks generally stop appearing as critical because they can no longer delay their successors.
- Multiple-critical-path calculation can classify local paths within independent task networks.
Therefore, do not assume that every red task belongs to one clean, continuous chain from project start to project finish.
Check the Critical-Task Slack Threshold
Microsoft Project lets you control how much slack a task can have while still being classified as critical.
- Select File > Options.
- Select Advanced.
- Scroll to Calculation options for this project.
- Review Tasks are critical if slack is less than or equal to.
A threshold of zero days focuses the display on tasks with zero or negative slack. If you enter five days, Project can also flag tasks with one through five days of slack as critical.
A larger threshold may help managers monitor near-critical work. However, it also changes the meaning of every red bar and every Yes value in the Critical field. For formal analysis, document the setting and review the actual Total Slack values. You can then monitor low-float work without confusing it with the path that currently controls the finish date.
For a broader discussion of low-float chains, see Near-Critical Paths: What Schedulers Should Monitor.
Display Multiple Critical Paths Only When You Need Them
By default, Microsoft Project displays the overall path that affects the project finish. You can also calculate a critical path for each independent task network.
- Select File > Options > Advanced.
- Scroll to the calculation options for the project.
- Check Calculate multiple critical paths.
- Return to the Gantt Chart and enable Critical Tasks.
This option can support a master schedule containing several subprojects or a schedule with distinct phases and delivery milestones. However, it can also produce many red paths in a fragmented schedule. Open-ended activities and weak logic often create independent networks that Project then evaluates separately.
As a result, multiple-critical-path calculation should not replace sound network logic. If the purpose of the analysis is to find the chain driving one specific delivery, trace backward from that milestone instead.
Displaying Critical Tasks Is Not the Same as Tracing a Path
The red-bar option answers, “Which tasks does Project classify as critical?” A path trace answers a more focused question: “Which predecessor sequence drives this milestone?”
To inspect a selected task, use Gantt Chart Format > Task Path > Driving Predecessors. The Task Path feature highlights the predecessors that drive the selected activity. You can continue selecting predecessor tasks to examine the chain in more detail.
Microsoft Project also provides the Task Inspector. Select an activity and choose Task > Inspect Task. The inspector can identify predecessors, constraints, calendars, actual dates, leveling delay and other factors that affect the selected task. Microsoft describes these capabilities in its guidance on how to view and track scheduling factors.
For a detailed workflow, see How to Trace a Critical Path in Microsoft Project. The related critical path analysis process for an Integrated Master Schedule explains how to interpret the resulting chain at the program level.
Practical Example: A Software Qualification Milestone
Assume the fictional Falcon Ridge program has a contractual software qualification milestone on November 20. Two activity chains feed the milestone:
- Code integration, regression testing and qualification testing have zero days of total slack.
- Training material development and instructor review have three days of total slack.
With the critical threshold set to zero days, Microsoft Project displays the integration and test chain in red. That chain currently controls the qualification milestone. The training chain remains noncritical, although it has little schedule flexibility.
If the scheduler changes the threshold to five days, both chains appear critical. That display may help the program manager monitor risk. However, it no longer distinguishes the zero-float driving path from the three-day near-critical path without reviewing the Total Slack column.
Now assume the qualification milestone has a deadline earlier than the calculated project finish. The deadline can change total slack for the tasks feeding that milestone. Consequently, the red path may reflect performance against the deadline rather than only the final task in the project file. The scheduler should confirm which endpoint Project is using before briefing management.
Common Reasons the Critical Path Display Looks Wrong
Missing or incomplete logic
Activities without appropriate predecessors or successors can form disconnected networks. Microsoft Project can calculate dates for those activities, but the resulting red bars may not represent an end-to-end program path. Review open ends and confirm that the logic reflects how the work will execute.
Excessive constraints
Must Start On and Must Finish On constraints can override normal network flexibility. Other constraints can also affect late dates. Review the Constraint Type and Constraint Date fields before treating a constrained chain as a logic-driven critical path.
Deadlines are affecting total slack
A deadline does not normally force a task to occur on a specific date. However, it can reduce total slack. This behavior is often useful, but the schedule analyst must understand which deadline drives the calculation.
The critical threshold is too high
If dozens of tasks appear red, review the critical-task threshold. Someone may have increased it to capture near-critical work. Restore the intended value or use the Total Slack field to separate the driving and near-driving tasks.
Summary tasks obscure the detailed path
A summary task rolls up the dates of its subtasks. It does not replace the detailed network. Expand the outline and review the lowest practical activity level before evaluating path continuity.
The status update changed the path
The critical path can shift after actual progress, forecast changes or revised logic. That movement is not automatically an error. Compare the current schedule with the approved baseline and investigate the reason for the change. If a baseline has not yet been saved, follow the steps in How to Create a Baseline in Microsoft Project.
What to Review Before Briefing the Critical Path
- Confirm the intended completion or delivery milestone.
- Verify the critical-task slack threshold.
- Review Total Slack instead of relying only on red formatting.
- Trace driving predecessors from the selected milestone.
- Check for missing logic, constraints, deadlines and calendar effects.
- Review negative and near-critical paths.
- Compare current and baseline dates when a baseline exists.
- Explain any change from the prior reporting period.
For a customer-facing Integrated Master Schedule (IMS), also perform a broader quality review. The IMS customer-delivery review checklist covers the surrounding checks that a red-bar display cannot address.
Why the Critical Path Display Matters
Displaying the critical path helps planners focus status collection, recovery planning and management attention on the work with the least schedule flexibility. It also gives Control Account Managers (CAMs) a clearer view of activities that can affect key milestones.
However, the critical path is a calculated schedule result, not a permanent label. It can move when actual performance, remaining durations, relationships, calendars or constraints change. Therefore, schedulers should review it after each status cycle and before major schedule deliveries.
For Department of Defense or Earned Value Management System (EVMS) work, no universal rule says every program must use one particular Microsoft Project display setting. Contractual requirements depend on the contract, agency direction and program tailoring. Still, sound critical path analysis supports credible forecast dates and helps the IMS perform its management function. See Microsoft Project for Integrated Master Scheduling for the broader application.
Frequently Asked Questions
Why are all my Microsoft Project tasks critical?
The schedule may contain disconnected activity chains, date constraints or a critical-task threshold above zero. Apply the Schedule table and inspect Total Slack, predecessors, successors, constraints and deadlines.
Why did completed tasks disappear from the critical path?
Completed activities can no longer delay remaining successor work, so Microsoft Project generally stops classifying them as critical. Use baseline and tracking views when you need to show historical performance.
Can Microsoft Project show near-critical tasks?
Yes. You can raise the critical-task slack threshold, but that changes the Critical field and red-bar display. A clearer analytical method often uses Total Slack filters or groups to identify low-float tasks separately.
Does a red bar prove that a task drives my delivery milestone?
No. It proves that the task meets Microsoft Project’s current critical-task criteria. Trace driving predecessors from the delivery milestone and review the logic, total slack, constraints and deadlines before confirming the path.