Schedule control

Project Scheduling and Critical Path Basics

Learn to build a dependency-based schedule, find the critical path, and manage float so deadline risk becomes visible early.

How this page is maintained

Written for learners, checked against the sources below, and reviewed every year. Last reviewed July 22, 2026.

Short answer

The critical path is the longest sequence of dependent activities that determines project finish date. In a standard CPM baseline, activities on that path typically have zero total float, so delays there delay the project unless scope, resources, or sequence changes.

  • Dependency quality matters more than tool choice.
  • Critical path can change as progress and estimates change.
  • Float is a planning buffer, not free time to ignore.

Build a dependency-first schedule

Start from work packages, then define activity sequence and dependency type. Confirm that predecessor logic reflects real technical and business constraints.

Estimate durations with team input and document assumptions. Unstated assumptions make schedule variance harder to explain.

Use critical path for decisions

Track critical activities weekly. If one slips, decide quickly whether to add capacity, resequence work, or narrow scope.

Monitor near-critical paths too. A path with low float can become critical after one moderate delay.

  • Recalculate path after major estimate or dependency changes
  • Separate reporting milestones from work activities
  • Log approved schedule baseline changes

Critical path for pilot launch

Harbor Health must launch a clinic pilot by October 1.

  1. Sequence key activities: security review, integration testing, user training, and pilot readiness sign-off.
  2. Calculate earliest and latest dates and identify zero-float chain.
  3. Detect delay risk in integration testing and add a second test engineer to protect the date.
  4. Recalculate schedule and confirm pilot milestone still meets October 1.
Result: The team sees which activities truly control launch date and acts before slippage becomes irreversible.

Common mistakes

  • Treating all tasks as equally schedule-critical.
  • Using finish dates without explicit dependency logic.
  • Ignoring near-critical paths with very low float.
  • Updating percent complete without recalculating remaining duration.

Try one

What happens if a zero-float activity slips by three days?

The project finish date slips by three days unless corrective action changes path timing.

Sources

Learn this with a tutor

Tell LearnLive what you already know and what you need to do with schedule and critical path.

Build this course