PERT Calculator

The Program Evaluation and Review Technique (PERT) turns three time estimates for each activity — optimistic, most likely and pessimistic — into a single expected duration and a measure of its uncertainty, then rolls those up to tell you how long a project will probably take and how likely it is to finish by any target date. This PERT calculator takes your activities, computes the expected time, standard deviation and variance of each, sums them along the path, and returns the project’s expected duration, its spread, and the probability of finishing on time. Enter your estimates above, add a target date, and read the risk the way a scheduler does.

What the PERT calculator computes

PERT is a probabilistic scheduling method. Where the Critical Path Method treats each activity duration as a single fixed number, PERT admits that estimates are uncertain and models that uncertainty with three points per activity. The optimistic estimate is the duration if everything goes well, the pessimistic estimate is the duration if things go badly, and the most likely estimate is the realistic middle. From those three numbers PERT derives a weighted expected time, a standard deviation that quantifies the uncertainty, and a variance used to combine activities.

This tool reports, for each activity, the expected time, the standard deviation and the variance. It then sums the expected times along the path to give the project’s expected duration, sums the variances to give the path variance, and takes the square root to give the path standard deviation. If you supply a target completion time, it computes a Z-score and the probability of finishing by that target, along with the 68%, 95% and 99.7% confidence ranges. Those outputs are exactly what a project manager needs to move from a single-point schedule to an honest statement of schedule risk.

The three-point estimate and the beta distribution

The heart of PERT is the assumption that an activity’s duration follows a beta distribution — a flexible, bounded distribution that can be skewed toward the optimistic or pessimistic end. The beta distribution is attractive here because real activity durations are bounded (they cannot be shorter than the optimistic case or longer than the pessimistic case) and are usually skewed rather than symmetric: things tend to go wrong in more ways than they go right, so the pessimistic tail is longer. Rather than ask an estimator to specify a full distribution, PERT asks only for three points and approximates the distribution’s mean and standard deviation from them.

The optimistic time, often written as O or a, is the best case with roughly a one-in-a-hundred chance of being beaten. The pessimistic time, P or b, is the worst realistic case, again with about a one-in-a-hundred chance of being exceeded. The most likely time, M or m, is the mode — the single duration you would bet on if forced to choose one. Eliciting these three well is most of the skill in using PERT; the arithmetic that follows is simple.

The expected time formula and why the mode is weighted four times

PERT computes the expected time of an activity as a weighted average that leans heavily on the most likely value:

Expected time TE = (O + 4M + P) / 6

The most likely estimate is weighted four times as heavily as either extreme, and the whole is divided by six because the weights sum to six. This particular weighting is the classical approximation to the mean of a beta distribution, and it has a sensible interpretation: the realistic middle should dominate the estimate, while the two extremes pull it a little in their direction. When the optimistic and pessimistic estimates are symmetric about the most likely value, the expected time equals the most likely value. When the pessimistic tail is longer — the common case — the expected time is pulled above the most likely value, which is exactly the conservative nudge good scheduling wants.

Consider an activity estimated at three days optimistic, five days most likely and thirteen days pessimistic. The expected time is (3 + 20 + 13) / 6 = 6 days, a full day longer than the most likely estimate, because the long pessimistic tail drags the mean upward. This is the single most useful thing PERT does at the activity level: it stops planners from scheduling to the optimistic or even the most likely case and quietly builds realistic slack into every estimate.

Standard deviation and variance

PERT measures the uncertainty of an activity with a standard deviation derived from the range between the extremes:

Standard deviation σ = (P − O) / 6    Variance σ² = ((P − O) / 6)²

The logic is that a beta distribution’s range spans roughly six standard deviations, so dividing the optimistic-to-pessimistic spread by six approximates one standard deviation. A wide gap between optimistic and pessimistic means a large standard deviation and an uncertain activity; a narrow gap means a confident estimate. The variance is simply the square of the standard deviation, and although it is less intuitive than the standard deviation, it is the quantity that lets uncertainty be combined across activities, which is why PERT tracks it.

For the activity estimated at three, five and thirteen days, the standard deviation is (13 − 3) / 6 = 1.67 days and the variance is about 2.78. A tightly estimated activity at four, five and six days would have a standard deviation of just 0.33 days. Reporting both makes the difference in confidence between two activities with the same expected time immediately visible.

Why variances add and standard deviations do not

To find the uncertainty of a whole path, PERT sums the variances of the activities on it and then takes the square root to get the path standard deviation. It does not add the standard deviations directly. This is the single most misunderstood point in PERT, and it follows from a basic result in statistics: when independent random variables are added, their variances add, but their standard deviations do not. If two sequential activities each have a standard deviation of one day, the path does not have a standard deviation of two days; it has a variance of 1 + 1 = 2 and therefore a standard deviation of about 1.41 days.

Path variance = ∑ activity variances    Path σ = √(path variance)

The practical consequence is that uncertainty grows more slowly than a naive sum would suggest, because the independent ups and downs of different activities partly cancel. A project with many activities is proportionally less uncertain, per unit of duration, than any single activity, which is a reassuring and non-obvious result that only the variance arithmetic reveals. This calculator does the summing for you and reports the path variance and path standard deviation directly.

The probability of finishing on time

Once the path has an expected duration and a standard deviation, PERT invokes the central limit theorem: the sum of many independent activity durations is approximately normally distributed, whatever the shape of the individual beta distributions. That lets the method answer the question managers actually care about — what is the chance of finishing by a given date — using the standard normal distribution. The tool computes a Z-score:

Z = (target duration − expected duration) / path standard deviation

The Z-score is the number of standard deviations the target lies above or below the expected duration. Feeding it into the normal cumulative distribution gives the probability of finishing by the target. A target equal to the expected duration gives Z = 0 and a probability of exactly 50%, which surprises people the first time they see it: scheduling to the expected duration means a coin-flip chance of being late. To reach 90% confidence you must add roughly 1.28 standard deviations of buffer to the expected duration; for 95%, about 1.65. This calculator reports the probability for whatever target you enter, so you can find the date that meets your desired confidence.

Confidence ranges around the expected duration

Because the project duration is approximately normal, the familiar empirical rule applies. About 68% of the probability lies within one standard deviation of the expected duration, about 95% within two, and about 99.7% within three. The calculator prints all three ranges, which is the fastest way to communicate schedule risk to a stakeholder: rather than a single date, you can say the project will almost certainly finish within the three-sigma band, is very likely to finish within the two-sigma band, and is more likely than not to finish within the one-sigma band. These ranges are also what the PMP and CAPM examinations expect candidates to compute from the path standard deviation.

Worked examples

Example 1 — a three-activity path. Suppose a critical path has activities A (optimistic 2, most likely 4, pessimistic 6), B (3, 5, 13) and C (1, 2, 3). Their expected times are 4, 6 and 2, summing to a project expected duration of 12. Their variances are 0.44, 2.78 and 0.11, summing to a path variance of 3.33, so the path standard deviation is about 1.83. Scheduling to 12 gives only a 50% chance of success. To be 95% confident you would need about 12 + 1.65 × 1.83 ≈ 15 time units. Load this example with the button above to see the table, the ranges and the distribution curve.

Example 2 — the effect of one uncertain activity. Notice that activity B dominates the path uncertainty: its variance of 2.78 is most of the path variance of 3.33, because its optimistic-to-pessimistic range of ten is far wider than the others. If you could tighten B’s estimate — by resolving whatever makes it uncertain — to, say, 4, 5, 6, its variance would fall to 0.11 and the path variance to about 0.66, cutting the path standard deviation from 1.83 to 0.81. The expected duration would barely change, but the schedule would become far more predictable. PERT’s variance column is what points you to the activity worth de-risking.

Example 3 — a single-activity estimate. For a quick exam-style question you can enter just one activity. Given optimistic 8, most likely 10 and pessimistic 18, the expected time is (8 + 40 + 18) / 6 = 11, the standard deviation is (18 − 8) / 6 = 1.67, and the probability of finishing within 13 is the normal probability at Z = (13 − 11) / 1.67 = 1.2, about 88%. The calculator handles the single-activity case exactly like a one-item path.

How to read the results

The headline shows either the expected project duration, or — when you enter a target — the probability of finishing by that target. The metric grid beneath it reports the expected duration, the path standard deviation and the path variance, and, when a target is set, the probability and the Z-score.

The three confidence ranges give the one-, two- and three-sigma bands around the expected duration. The table lists every activity with its three estimates and its computed expected time, standard deviation and variance, so you can see which activities are the largest and the most uncertain.

The chart draws the approximately normal distribution of the project duration, whose peak sits at the expected duration and whose width reflects the path standard deviation.

Read the variance column to find where uncertainty concentrates, read the expected-duration figure to set a realistic baseline, and read the probability to judge whether a promised date is a safe commitment or a gamble. Export the table to CSV to attach to a schedule review, or save the page as a PDF for a risk report.

PERT versus the Critical Path Method

PERT and the Critical Path Method are companions, not competitors. CPM is deterministic: it takes single durations and computes the critical path, the float and the project duration exactly. PERT is probabilistic: it takes three-point estimates and computes the expected duration and its uncertainty. In practice the two are layered.

You first identify the critical path with CPM using the expected times, then apply PERT’s variance arithmetic to that path to state the probability of finishing on time. The expected times this calculator produces are exactly the durations you would feed into a critical-path analysis, and the path whose variance you sum here is normally the critical path found there.

Using the two together gives both the schedule and its risk, which is why they were developed in the same era and are taught side by side.

A subtlety worth knowing is that PERT’s focus on the single critical path can understate risk when a project has several near-critical paths, because a non-critical path with high variance can become the binding constraint on a bad day. Sophisticated practice supplements PERT with Monte Carlo simulation, which samples every activity’s distribution and re-finds the critical path thousands of times. PERT remains the right first tool because it is transparent, hand-computable and exam-standard, and because it captures the great majority of the insight for a fraction of the effort.

PERT, triangular estimates and simple averages

PERT is not the only three-point method. A triangular distribution uses the same three estimates but computes the expected time as a plain average, (O + M + P) / 3, and a different standard deviation. The triangular mean weights the extremes more heavily than PERT’s beta mean does, so it produces a slightly more conservative expected time.

Some organisations prefer it for its simplicity and its lack of a hidden distributional assumption. The beta-based PERT formula, with its four-times weighting of the mode, remains the dominant convention in project management and the one the certifications teach, which is why this calculator uses it.

The key point is that any three-point method is dramatically better than a single-point estimate, because it forces the estimator to think about the range of outcomes rather than a single hopeful number.

Eliciting good optimistic, most likely and pessimistic estimates

PERT’s output is only as good as its three inputs, and eliciting them well is a discipline in itself. The most common failure is anchoring: an estimator picks a most likely value and then sets the optimistic and pessimistic only slightly to either side, producing an artificially narrow range and a falsely confident schedule.

Guard against it by eliciting the extremes first and independently — ask for the best case imaginable and the worst case that could realistically happen before asking for the most likely — so the range is not anchored to the middle. Define the extremes as roughly percentile values rather than absolute limits: the optimistic time is one you would beat only about one time in a hundred, and the pessimistic likewise.

Draw on historical data for similar activities where it exists, and involve the people who will do the work rather than only the planner. A well-elicited three-point estimate captures real knowledge about risk; a poorly elicited one merely dresses a guess in statistical clothing.

Common mistakes when using PERT

The most frequent error, already noted, is adding standard deviations instead of variances when combining activities; always sum the variances and take the square root at the end. A second is scheduling to the expected duration and being surprised by a 50% on-time rate; commitments should be made at the expected duration plus a buffer sized to the confidence you need.

A third is treating PERT’s probability as exact: it rests on the assumptions that activities are independent, that the path is the binding one, and that the beta and normal approximations hold, none of which is perfectly true, so the probability is a well-founded estimate rather than a guarantee.

A fourth is applying PERT to a path other than the critical one; the probability of the project finishing on time is governed by the longest path, so run the variance arithmetic on the critical path unless you are deliberately checking a near-critical path’s risk. Avoiding these four keeps PERT honest.

Choosing a confidence target from the Z-score

The Z-score is the bridge between a confidence level and a committed date, and a handful of values are worth memorising. A Z of 0 is the expected duration at 50% confidence. A Z of about 1.28 corresponds to 90%, 1.65 to 95%, 2.00 to about 97.7%, and 2.33 to 99%. To turn any of these into a date, multiply the Z by the path standard deviation and add the result to the expected duration.

For the worked three-activity path, with an expected duration of 12 and a path standard deviation of about 1.83, a 90% commitment sits at 12 + 1.28 × 1.83 ≈ 14.3 time units and a 95% commitment at 12 + 1.65 × 1.83 ≈ 15.0. Reading it the other way, if a customer demands delivery at 13, the Z is (13 − 12) / 1.83 ≈ 0.55, giving only about 71% confidence — useful ammunition for a conversation about either extending the date or reducing the scope that drives the variance.

This calculator does the lookup for you when you enter a target, but understanding the handful of Z values lets you reason about schedule risk in your head.

PERT in agile and hybrid delivery

Three-point thinking is not confined to traditional plan-driven projects. Agile teams estimate with ranges too — story-point distributions, optimistic and pessimistic sprint velocities, and forecast cones that widen with the horizon are all expressions of the same idea that a single number hides real uncertainty.

At the release or programme level, where a body of work must be forecast against a date, the PERT arithmetic applies directly to the sequence of increments or the dependency chain between teams: estimate each stage with three points, sum the expected times and variances, and state the probability of hitting the release window.

Hybrid delivery models often keep detailed work iterative while forecasting the coarse-grained milestones probabilistically, and PERT is a natural, lightweight way to do the latter without adopting a full simulation tool. The method is a way of thinking about uncertainty first and a scheduling formalism second, which is why it survives every shift in delivery fashion.

Where PERT is used

PERT was created for research-and-development programmes where activity durations were genuinely uncertain and had never been done before — famously the US Navy’s Polaris submarine-missile programme in the late 1950s, which had tens of thousands of interdependent and unprecedented tasks.

That heritage explains its enduring home: new-product development, engineering projects, construction with novel methods, software delivery, event planning, and any endeavour where estimates carry real uncertainty and a committed date carries real consequences. Anywhere a single-point schedule would be dishonest because the work has never been done exactly this way before, PERT’s three-point estimate and probability of on-time completion earn their place.

It is also a staple of project-management education, and the expected-time, standard-deviation and probability calculations on this page are precisely what the PMP and CAPM examinations require candidates to perform.

Reading the distribution chart

The chart below the results draws the project duration as an approximately normal bell curve, centred on the expected duration with a spread set by the path standard deviation. The peak marks the single most probable region of outcomes, and the area under the curve to the left of any point is the probability of finishing by that time.

A tall, narrow curve means a predictable project whose finish date can be committed with confidence; a low, wide curve means a volatile project where the honest answer to “when will it be done” is a broad range rather than a date.

Comparing two schedule options by the width of their curves is often more persuasive to a stakeholder than any table, because it makes risk visible rather than abstract.

Because the curve is symmetric about the expected duration, exactly half its area lies on either side, which is the visual form of the fifty-percent rule: the expected date splits the outcomes in two. Sliding your target to the right moves more of the area under the curve to its left, and that growing shaded fraction is the rising probability of on-time completion that the metric grid reports numerically. Seeing the number and the area together builds an intuition for how much buffer a given confidence level really costs.

Buffers, management reserve and committed dates

PERT’s real payoff is in setting the date you commit to, as distinct from the date you plan around. The expected duration is the planning baseline, but the committed date should include a buffer sized to the confidence the situation demands.

A low-stakes internal milestone might be committed at the expected duration plus one standard deviation, roughly 84% confidence; a contractual delivery with penalties might warrant two standard deviations, about 98%. The gap between the expected duration and the committed date is the schedule contingency, and PERT lets you justify its size with a number rather than a hunch, which is exactly the conversation a project sponsor wants to have.

This is the scheduling analogue of the contingency reserve that risk analysis produces on the cost side, and mature project offices set both from explicit probability targets rather than from a flat percentage add-on.

It is worth distinguishing this activity-and-path contingency, which covers the ordinary variability PERT models, from management reserve, which covers the unknown-unknowns that no three-point estimate anticipated. PERT sizes the former; the latter is a separate, usually organisational, allowance held above the project baseline. Confusing the two leads either to double-counting or to projects with no cushion for genuine surprises, so keep the PERT-derived buffer and the management reserve as separate lines.

A brief history of PERT

PERT was developed in 1957 and 1958 by the US Navy’s Special Projects Office, working with the consultancy Booz Allen Hamilton and the contractor Lockheed, to manage the Polaris ballistic-missile submarine programme. That project coordinated thousands of contractors on work that had never been attempted, where durations could not be looked up in any table and had to be estimated under deep uncertainty.

The three-point estimate and the probability of meeting a deadline were the method’s answer to that uncertainty, and PERT is widely credited with helping bring Polaris in ahead of schedule. At almost the same moment DuPont and Remington Rand were developing the Critical Path Method for plant maintenance, where durations were well known and the goal was cost-time trade-off rather than uncertainty.

The two techniques were born within a year of each other, converged on the same network mathematics, and have been taught together ever since as the deterministic and probabilistic faces of project scheduling.

Assumptions and limitations to keep in mind

PERT rests on several assumptions, and knowing them tells you when to trust it and when to reach for something richer. It assumes each activity’s duration follows a beta distribution well summarised by three points, that activities are statistically independent, that the analysed path is the one that will actually determine the finish, and that the sum of activities is normal enough for the standard-normal probability to apply.

The independence assumption is the shakiest: in reality a bad week affects many activities at once, correlating their durations and making the true spread wider than PERT’s variance sum suggests. The single-path assumption is the next weakest, because a project with several near-critical paths can finish late through whichever path happens to blow out, a risk PERT on one path cannot see. None of this makes PERT wrong; it makes PERT a first, transparent approximation whose numbers should be read as informed estimates.

When the stakes justify the effort, Monte Carlo simulation relaxes every one of these assumptions by sampling all activities and re-finding the critical path many thousands of times, and it is the natural next step beyond PERT.

Three-point estimating beyond the schedule

Although PERT was born as a scheduling technique, the three-point estimate it popularised is used just as often for cost. The same optimistic, most likely and pessimistic logic applies to the price of a work package: a best case if suppliers hold their quotes and no rework is needed, a worst case if everything that can cost more does, and a realistic middle. The expected cost is the same beta-weighted average, (O + 4M + P) / 6, and the standard deviations combine by summing variances exactly as they do for time.

This is why three-point estimating appears in the cost-management as well as the schedule-management parts of the project-management body of knowledge, and why the contingency reserve on the budget is often derived the same way the schedule buffer is: from a target confidence level applied to a combined distribution.

If you are estimating cost rather than duration, this calculator’s arithmetic carries over unchanged — read “time units” as currency and the expected value, standard deviation and confidence ranges mean exactly what they did before.

The broader lesson is that any estimate made under uncertainty benefits from being stated as three numbers rather than one. The discipline of naming a best and a worst case forces an explicit conversation about what could go right and wrong, surfaces risks that a single figure would bury, and produces a spread that downstream analysis can use. Whether the quantity is a duration, a cost, a headcount or a throughput, the three-point habit is one of the highest-leverage estimating practices a team can adopt.

A short glossary of PERT terms

Optimistic time (O or a) — the best-case duration, beaten only about one time in a hundred. Most likely time (M or m) — the modal duration, the single best guess. Pessimistic time (P or b) — the worst realistic duration, exceeded only about one time in a hundred. Expected time (TE) — the beta-weighted mean, (O + 4M + P) / 6. Standard deviation (σ) — the activity’s uncertainty, (P − O) / 6. Variance (σ²) — the square of the standard deviation, the quantity that adds across activities. Path variance — the sum of the variances on a path. Path standard deviation — the square root of the path variance. Z-score — the number of standard deviations a target lies from the expected duration. Confidence range — the ±1σ, ±2σ and ±3σ bands holding about 68%, 95% and 99.7% of the probability. Keeping these straight is most of what it takes to read any PERT analysis with confidence.

How to use this calculator

List your activities one per line as ID, optimistic, most likely, pessimistic — for example B, 3, 5, 13. For a whole-project estimate, enter the activities on the critical path so their expected times and variances sum correctly; for a single estimate, enter just one line. Optionally type a target duration to get the probability of finishing by it. Press calculate, or press “Load example” to populate a worked three-activity path.

Read the expected duration and the confidence ranges first, then the probability against your target, then the per-activity table to see where the uncertainty lives. Keep your time units consistent across all activities, make sure each line satisfies optimistic ≤ most likely ≤ pessimistic, and export the result to CSV or PDF for your records.

Adjust an activity’s estimates and recalculate to see how tightening an uncertain estimate sharpens the whole schedule.

Five worked examples of PERT estimation

Example 1: the expected time

Optimistic 4, most likely 6, pessimistic 14 days. te = (o + 4m + p) ÷ 6 = (4 + 24 + 14) ÷ 6 = 7 days. The weighted average pulls toward the most likely but respects the long tail.

Example 2: the activity’s standard deviation

σ = (p − o) ÷ 6 = (14 − 4) ÷ 6 = 1.67 days; variance = σ² = 2.78. A wide optimistic-to-pessimistic spread means a more uncertain activity.

Example 3: rolling up the project

For a critical path of three activities with te 7, 5, 8, expected duration = 20 days. Project variance = sum of the critical activities’ variances, say 2.78 + 1.0 + 1.78 = 5.56, so project σ = √5.56 = 2.36 days.

Example 4: probability of finishing on time

To finish by 23 days, z = (23 − 20) ÷ 2.36 = 1.27, which maps to about 90% probability. PERT turns a deadline into a confidence level.

Example 5: a symmetric estimate

If o 5, m 8, p 11 (symmetric), te = (5 + 32 + 11) ÷ 6 = 8 — the same as the most likely. PERT only shifts the estimate when the three points are skewed.

Three expert tips for PERT

Sum variance only along the critical path

Project variance comes from the activities on the critical path, not all activities. If a near-critical path has higher variance, check it too — it can dominate the risk.

Get honest three-point estimates

The method is only as good as the optimistic and pessimistic bounds. Ask for realistic extremes from the people doing the work, not padded or wishful numbers.

Use the probability, not just the mean

The power of PERT is the confidence level around a date. Commit to a date with a stated probability (say the 80% date), not the bare expected duration.

Frequently asked questions

Sources, disclaimer and editorial transparency

This calculator applies the standard PERT formulas: expected time TE = (O + 4M + P) / 6 from the beta-distribution approximation, standard deviation σ = (P − O) / 6, variance σ², path variance as the sum of activity variances, and the probability of finishing by a target from the normal approximation with Z = (target − ∑TE) / √(∑σ²). This is consistent with standard project-management references such as the PMBOK Guide. This calculator and guide are created and reviewed by the OpsCalculators team; see our Editorial Policy for how each tool is researched, built, and tested.

Results are accurate estimates for planning and education, not certified scheduling advice, and they assume independent activities, that the analysed path is the binding one, and that the beta and normal approximations hold. For projects with several near-critical paths, supplement PERT with Monte Carlo simulation. OpsCalculators.com is operated by MAFHH INTERNATIONAL LTD. Your data is processed in your browser and never stored; see our Privacy Policy.