What Is PERT?
The Program Evaluation and Review Technique (PERT) is a project scheduling method designed for situations where task durations are uncertain. While CPM uses a single duration estimate per task, PERT uses three: optimistic, most likely, and pessimistic. These feed into a weighted average that accounts for the inherent uncertainty in complex or novel work.
PERT was developed in 1958 by the U.S. Navy Special Projects Office, working with Booz Allen Hamilton and its prime contractors, for the Polaris missile submarine program — a project with over 3,000 contractors and massive uncertainty. It helped reduce the program's expected completion time by two years.
When to Use PERT vs. CPM
Use CPM when you have reliable historical data and tasks are well understood (routine plant shutdowns, standard changeovers). Use PERT when tasks are novel, uncertain, or have never been done before (R&D projects, first-time installations, new product introductions). In practice, many teams use PERT estimates fed into a CPM network for the best of both worlds.
The Three-Point Estimate
For each task, you gather three duration estimates:
| Estimate | Symbol | Definition | Guidance |
|---|---|---|---|
| Optimistic | O (or a) | Best-case duration if everything goes right | Has about 1% chance of happening. No major problems. |
| Most Likely | M (or m) | Duration if the task runs normally | The mode of the distribution. What would happen most often if you repeated this task many times. |
| Pessimistic | P (or b) | Worst-case duration if things go wrong | Has about 1% chance of happening. Major problems, but not catastrophic (no acts of God). |
The PERT Formulas
Expected Duration (Weighted Average)
Standard Deviation (Per Task)
Project Duration Variance
Worked Example
A new production line installation with 4 critical-path tasks:
| Task | O (days) | M (days) | P (days) | te | σ | σ² |
|---|---|---|---|---|---|---|
| A: Site prep | 3 | 5 | 10 | 5.5 | 1.17 | 1.36 |
| B: Equipment install | 6 | 8 | 16 | 9.0 | 1.67 | 2.78 |
| C: Electrical & plumbing | 4 | 6 | 10 | 6.3 | 1.00 | 1.00 |
| D: Commissioning | 2 | 4 | 8 | 4.3 | 1.00 | 1.00 |
Calculating the Results
Expected project duration = 5.5 + 9.0 + 6.3 + 4.3 = 25.1 days
Project variance = 1.36 + 2.78 + 1.00 + 1.00 = 6.14
Project σ = √6.14 = 2.48 days
Probability Calculations
With the expected duration and standard deviation, you can calculate the probability of finishing by a specific date using the Z-score:
Using our example: What is the probability of finishing in 28 days?
| Calculation | Value |
|---|---|
| Z = (28 – 25.1) ÷ 2.48 | Z = 1.17 |
| P(Z ≤ 1.17) | ~88% probability of finishing in 28 days |
Common Confidence Levels
| Confidence | Z-Score | Buffer Added | Use Case |
|---|---|---|---|
| 50% | 0 | Expected duration (no buffer) | Internal planning baseline |
| 84% | 1.0 | +1σ | Reasonable internal target |
| 95% | 1.65 | +1.65σ | Customer commitments |
| 99% | 2.33 | +2.33σ | Contractual deadlines |
Both the mean and the σ are the worked example's own totals: 5.5 + 9.0 + 6.3 + 4.3 = 25.1 days, and √(1.36 + 2.78 + 1.00 + 1.00) = 2.48 days. The ladder underneath is the page's confidence table read back onto the axis, so each level's Z becomes a date rather than a multiplier — +1σ is 27.6 days, not "some buffer". The dotted rule is the page's own Z question: 28 days gives Z = 1.17 and about 88%. The curve is normal because that is what the page assumes when it sends you to a Z table; individual tasks are beta and right-skewed, but their sum is not. The page's merge-bias warning is not drawn here — it argues this whole curve sits too far left, and the page gives no figure for how far.
PERT in Manufacturing Operations
| Application | Why PERT Fits |
|---|---|
| New product introduction | Tooling, validation, ramp-up — durations are highly uncertain for first-time builds |
| Major capital projects | Construction, installation, commissioning have wide duration ranges |
| R&D / prototyping | By definition, novel work with no historical duration data |
| First-time plant shutdowns | Unfamiliar scope means high variability in task durations |
| Customer delivery commitments | Use PERT to set due dates at 90-95% confidence instead of guessing |
Limitations and Criticisms
✅ PERT Strengths
- Forces teams to think about uncertainty explicitly
- Provides probability-based schedule confidence
- Better than single-point estimates for novel work
- Identifies high-risk (high-variance) tasks
- Enables rational buffer sizing based on math, not gut feeling
❌ PERT Weaknesses
- Assumes independence between task durations (rarely true)
- Only considers the critical path variance (ignores near-critical paths)
- Beta distribution assumption may not fit all tasks
- People are bad at estimating O, M, and P — anchoring bias is real
- Ignores resource constraints entirely (same as CPM)
The Merge Bias Problem
PERT underestimates project duration when multiple parallel paths merge at the same point. If 5 parallel paths feed into one task, the merge point completes when the slowest of the 5 finishes — not the average. PERT's critical-path-only variance calculation misses this. For complex networks with many merge points, consider Monte Carlo simulation for more accurate probability estimates.
🎯 Key Takeaway
PERT transforms "I think it will take 8 days" into "there is a 90% chance it will take 12 days or less." That shift from deterministic guessing to probabilistic planning is powerful. Use three-point estimates for tasks with genuine uncertainty, calculate the variance on the critical path, and set commitments based on confidence levels — not optimism. But remember: PERT is only as good as the estimates you feed it, and it systematically underestimates projects with many parallel paths merging.
Interactive Demo
Calculate PERT estimates. Enter optimistic, likely, and pessimistic times to see expected duration and probability.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.