Bottom-Up Estimating: Definition, Steps & Example [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on August 30, 2026
8 min read
If you want to know what a project will really cost, there is no substitute for pricing every piece of it and adding them up. That is bottom-up estimating — the slowest, most detailed, and most accurate of the estimation techniques, the one you reach for when a rough guess will not do. Its trade-off is effort: you cannot build it until the work is defined, and assembling it takes real time. This guide covers bottom-up estimating in full — what it is, how to do it step by step, how it compares with top-down methods, its trade-offs, and how it is tested on the PMP and CAPM exams.
What is bottom-up estimating?
Bottom-up estimating is a technique that builds a project's total cost or duration by estimating each of its smallest components individually and then summing them. You break the work down to the level of work packages in the work breakdown structure, estimate each one on its own, and roll the estimates up through the WBS to a total for the whole project.
Its defining trait is accuracy. Because the estimate reflects the actual work rather than a comparison or a formula, it is the most accurate of the estimation techniques — and, as cost estimation practice recognizes, the most time-consuming. You cannot produce it until the scope is defined in enough detail to list the work packages, which is why bottom-up estimating comes later in planning, once you know what the project actually involves.
How to do bottom-up estimating
Bottom-up estimating follows a clear sequence from the detail up to the total:
- Decompose the work. Break the project down through the work breakdown structure into the individual work packages that make up the whole scope.
- Estimate each work package. Estimate the cost or duration of each package on its own, using the people who will do the work or the best available data.
- Add contingency where needed. Include contingency reserves for the risks in specific packages, so each estimate reflects its real uncertainty.
- Roll the estimates up. Sum the work-package estimates through each level of the WBS to reach a total for the project.
Here is the roll-up in action for an office renovation — a predictive project with a fully decomposed scope, priced by the trades who will do the work:
| WBS element | Estimate |
|---|---|
| Demolition & site prep — labor $6,500 + disposal $1,500 | $8,000 |
| Electrical — rough-in $9,000 + fixtures $4,500 + inspection $500 | $14,000 |
| Interior finishes — drywall $7,000 + paint $3,000 + flooring $8,000 | $18,000 |
| Project total ($40,000 + $4,000 contingency on the electrical rework risk) | $44,000 |
Each work package is priced on its own, package-level contingency is attached where the risk actually lives — the building's aging wiring — rather than smeared across the whole project, and the totals roll up through the WBS levels to a $44,000 figure a sponsor can interrogate line by line. Note that this is a predictive-planning technique: it needs the full scope decomposed up front, which is exactly what agile projects do not have; agile teams size work with relative story points instead. The estimate is only as good as the decomposition, so the more completely the work is broken down, the more reliable the sum.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Bottom-up vs. top-down estimating
Bottom-up estimating is the opposite of top-down estimating, and the exam expects you to know the difference. Top-down methods start from the whole project and work down; bottom-up starts from the parts and works up:
| Bottom-up estimating | Top-down estimating | |
|---|---|---|
| Approach | Estimate each work package, then sum them | Estimate the whole project, then divide down |
| Techniques | Detailed work-package estimating | Analogous and parametric estimating |
| Accuracy | Highest | Lower, rougher |
| Effort and time | High — needs a full WBS | Low — fast to produce |
| When to use | Later, once scope is defined | Early, when detail is scarce |
The two are complementary: teams often start with a top-down estimate for an initial budget and refine it with a bottom-up estimate as the work breakdown structure takes shape.
Advantages and limitations
Advantages:
- The most accurate: it is built from the real work rather than a comparison or formula, so it best reflects what the project will actually take.
- Exposes detail: decomposing the work surfaces tasks, risks, and costs a top-down estimate would miss.
- Builds ownership: because the people doing the work estimate it, the numbers are more credible and better supported.
Limitations:
- Time-consuming and costly: estimating every package takes significant effort, which is the main reason not to use it for a quick figure.
- Requires a defined scope: you cannot do it until the WBS is complete, so it is unavailable early in a project.
- Can drift high: summing many padded package estimates can inflate the total, so watch for contingency stacked on contingency.
Bottom-up estimating on the PMP® and CAPM® Exams
On the PMP exam, bottom-up estimating is usually tested through its trade-offs. The exam expects you to know it is the most accurate but most time-consuming method, that it requires a defined WBS, and that it belongs later in planning than analogous or parametric estimating. A common scenario asks which technique fits a situation: if the scope is detailed and accuracy matters, bottom-up is the answer; if the project is early and only a rough figure is needed, it is the wrong, over-engineered choice.
The subtler test is judgment under pressure — for instance, when a detailed bottom-up estimate conflicts with an earlier, rougher top-down number and a stakeholder wants the estimate changed to fit. The exam rewards defending the more accurate estimate and reconciling the gap honestly, not making the number say what someone wants. The CAPM tests the same ideas more directly, usually by matching bottom-up estimating to its definition or identifying it as the most accurate method. Our PMP Complete Study Guide lays out all the estimating techniques side by side so the distinctions stick.
PMP Practice Question: Bottom-Up Estimating
At initiation the sponsor set the project's budget from an analogous estimate. Now that the work breakdown structure is complete, the project manager works with the team members who will perform the work to develop a bottom-up estimate — and it comes in 20% above the sponsor's figure. The project has not yet baselined its cost, and the sponsor is expecting the numbers to be confirmed at the upcoming planning review.
What should the project manager do next?
a) Meet with the sponsor to walk through the bottom-up estimate and request the additional budget needed to close the 20% gap.
b) Analyze the differences between the two estimates to determine what is driving the higher figure, then bring the findings and options to the sponsor.
c) Reconvene the team to re-check the WBS and estimating assumptions and confirm the bottom-up figure before acting on it.
d) Submit a change request so that integrated change control can update the cost baseline to the bottom-up estimate.
Correct answer: B.
Rationale: All four options are honest, legitimate actions, so the question turns on sequence. Before any conversation with the sponsor can be useful, the project manager must understand why the two estimates differ — scope the WBS revealed that the early analogous figure never saw, richer information, or a different estimating basis — because diagnosis turns "the budget is wrong" into findings and options. Going straight to the sponsor for more budget is the strong candidate's trap: it involves the right person but arrives empty-handed, unable to answer the first question the sponsor will ask, and you never take a variance to a sponsor without understanding it. Re-checking the estimate sounds diligent, but the stem says it was already built with the people who will perform the work; that is the validated figure, and re-verifying it is rework that avoids the real task. A change request has nothing to act on: no baseline exists yet, and integrated change control executes approved changes rather than reconciling estimates. Understand the variance first, then bring findings and options. To practice this kind of technique-and-judgment question under exam conditions, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is bottom-up estimating?
Bottom-up estimating is a technique that builds a project's total cost or duration by estimating each of its smallest components, the work packages in the work breakdown structure, individually and then summing them. Because it reflects the actual work, it is the most accurate estimation method, and also the most time-consuming.
What is an example of bottom-up estimating?
To estimate a software module, you price each task separately — for instance 40 hours for design, 120 for development, 50 for testing, and 20 for documentation — then add them for 230 hours. You roll every module up the same way to reach the full project total. The estimate is the sum of its detailed parts.
What is the difference between bottom-up and top-down estimating?
Bottom-up estimating sums the estimates of individual work packages for a precise total but requires a defined scope and significant effort. Top-down estimating (analogous and parametric) estimates the whole project quickly from limited information and is rougher. Teams often start top-down for an early budget and refine to bottom-up as the scope firms up.
When should you use bottom-up estimating?
Use bottom-up estimating when the scope is defined in enough detail to list the work packages and when accuracy matters, which is typically later in planning. It is the wrong choice early in a project, when the work breakdown structure does not yet exist and only a rough top-down figure is possible or needed.
Why is bottom-up estimating the most accurate?
Because it is built from the actual work rather than from a comparison to a past project or a statistical formula. Estimating each work package individually captures the specific tasks, risks, and costs of this project, and involving the people who will do the work makes the numbers more credible than a top-down approximation.
Is bottom-up estimating on the PMP exam?
Yes. Bottom-up estimating is a core PMP estimation topic. The exam tests recognizing it as the most accurate but most time-consuming method, knowing it needs a defined WBS, distinguishing it from analogous and parametric estimating, and judging when it is the right technique for a given situation.
Is bottom-up estimating on the CAPM exam?
Yes. The CAPM tests bottom-up estimating within its predictive methodologies domain, usually by asking you to match it to its definition, identify it as the most accurate method, or distinguish it from top-down techniques. The questions are more direct and carry less situational judgment than the PMP's.
Fast-Tracking vs. Crashing: Schedule Compression [2026]
Fast-tracking vs crashing, the two schedule compression techniques: what each is, how they differ, when to use which, and how both are tested on the PMP exam.
Monte Carlo Simulation in Project Management [2026]
Monte Carlo simulation in project management: how it works, reading the S-curve and P50/P80 values, when to use it, and how it is tested on the PMP exam.
Resource Leveling vs. Smoothing: Guide & Examples [2026]
Resource leveling explained: what it is, how it works, and how it differs from resource smoothing — including the effect on the critical path and the PMP exam.
