SOP: Review Critical Path the Right Way in Microsoft Project

Words: ...
↓ Quick Down

SOP: Review Critical Path the Right Way in Microsoft Project

🎯 Purpose

To identify the tasks that directly control the project finish date so you can focus on the work that matters most.

Important Rule:

If a Critical Task is delayed by 1 day, the entire project may be delayed by 1 day.


Step 1: Complete Your Schedule First

Before reviewing the Critical Path, make sure you have:

✅ Created all tasks

✅ Assigned durations

✅ Linked task relationships (FS, SS, FF, SF)

✅ Assigned resources

✅ Set project start date

Without a complete schedule, the Critical Path will not be accurate.


Step 2: Switch to Gantt Chart View

  1. Open Microsoft Project.

  2. Go to View tab.

  3. Select Gantt Chart.

This is the easiest place to review Critical Tasks.


Step 3: Display the Critical Path

Method 1 (Recommended)

  1. Go to Format tab.

  2. Check Critical Tasks.

Microsoft Project will automatically highlight critical tasks.

Typical result:

  • Red bars = Critical Tasks

  • Blue bars = Non-Critical Tasks


Step 4: Check Total Slack

Critical tasks normally have:

Total Slack = 0 Days

To display it:

  1. Right-click any column header.

  2. Choose Insert Column.

  3. Select Total Slack.

Example:

TaskTotal Slack
Excavation0d
Foundation0d
Column Work0d
Painting5d

Interpretation:

  • 0d = Critical

  • Greater than 0d = Non-Critical


Step 5: Apply Critical Filter

To see only critical tasks:

  1. Go to View

  2. Select Filter

  3. Choose Critical

Now Microsoft Project shows only the tasks affecting project completion.

This is useful for weekly review meetings.


Step 6: Trace the Critical Chain

Review the critical tasks from start to finish.

Example:

Site Preparation
      ↓
Excavation
      ↓
Foundation
      ↓
Columns
      ↓
Beams
      ↓
Roof
      ↓
Finishing
      ↓
Project Completion

Ask:

  • Which task can delay the next task?

  • Which task has no float?

  • Which task is currently behind schedule?


Step 7: Review Progress Weekly

Every week:

  1. Update Actual Start.

  2. Update Actual Finish.

  3. Update % Complete.

  4. Recalculate schedule.

Then review:

  • Has the Critical Path changed?

  • Are new tasks becoming critical?

  • Is the project finish date moving?

Critical Path can change throughout the project.


Step 8: Focus Management Attention on Critical Tasks

For every Critical Task:

Check Resources

  • Enough workers?

  • Enough equipment?

  • Enough materials?

Check Risks

  • Weather risk?

  • Supplier delay?

  • Design approval delay?

Check Productivity

  • On schedule?

  • Behind schedule?

  • Need additional crew?


Common Mistakes

❌ Reviewing Critical Path before linking tasks

❌ Reviewing Critical Path before assigning durations

❌ Looking only at red bars without checking Total Slack

❌ Ignoring resource constraints

❌ Not updating progress regularly

❌ Assuming the Critical Path never changes


Construction Example

Suppose your house project has:

TaskDuration
Excavation3d
Foundation5d
Columns4d
Roof5d
Painting6d

After calculation:

  • Excavation = Critical

  • Foundation = Critical

  • Columns = Critical

  • Roof = Critical

  • Painting = Non-Critical (3 days slack)

If Painting is delayed by 2 days:

✅ Project finish date stays the same.

If Foundation is delayed by 2 days:

❌ Project finish date moves 2 days later.


Best Practice for a General Contractor (GC)

For your 8AM construction projects:

Daily

  • Review today's critical tasks.

Weekly

  • Apply the Critical filter.

  • Review all critical activities with the team.

Monthly

  • Compare current Critical Path against the baseline schedule.

Always Remember

"The Critical Path is the fastest route to project completion. Protect it every day."

When managing a construction project, spend 80% of your attention on Critical Tasks and 20% on Non-Critical Tasks because critical tasks determine whether the project finishes on time.

Previous Post Next Post
🕒
Color
Font
19
Content
Outline Data
Outline Level
```html ```