AACE CEP Certified Estimating Professional common mistakes
AACE CEP Certified Estimating Professional · Understand the traps and how to avoid them.
Treating a Class 5 / order-of-magnitude estimate as if it were a Class 3 budget estimate and applying the same expected accuracy range and contingency assumptions to it.
Candidates memorize a single 'typical accuracy' figure (e.g., ±10%) and apply it uniformly, forgetting that accuracy range and contingency narrow as the estimate matures through AACE estimate classes.
What to do instead
Learn the estimate class table as a matrix: for each class, know the expected maturity of project definition, the typical accuracy range, and the typical contingency range, and practice mapping a described project definition to the correct class before answering.
Choosing a detailed bottom-up method for a project with almost no engineering definition, or an analogous/top-down method for a fully defined scope.
Candidates select methods by personal familiarity or by what sounds 'more accurate' rather than by the amount of project definition available, which is the governing criterion.
What to do instead
Use a decision rule: method selection follows the degree of scope definition and available data. When a question gives a definition maturity, first classify the estimate, then pick the method that classifies with it.
Confusing cost analysis with price analysis and applying the wrong technique to a bid or proposal question.
Both involve money and both appear in procurement scenarios; candidates miss that price analysis compares total prices for reasonableness while cost analysis examines the individual cost elements and their basis.
What to do instead
Before answering, ask 'am I judging the total price against the market, or am I decomposing and validating the cost buildup?' Map the question to the matching technique and its inputs.
Adding contingency and escalation together as a single lump and applying both to the same base, or applying escalation to already-escalated totals.
Both are 'add-ons' expressed as percentages, so candidates treat them as interchangeable or compound them incorrectly, and they forget escalation depends on the timing of expenditure rather than total value.
What to do instead
Keep the two as separate line items with separate bases: contingency on the estimate base excluding escalation, escalation computed on cash-flow timing by period. Practice a small worked example of each independently, then combined.
Using a single point estimate in a risk-adjusted estimate instead of expected value or a defined confidence level (e.g., P50 vs P80).
Candidates default to most-likely values and ignore that risk-adjusted estimates require probability-weighted ranges or a stated confidence target, so they pick the deterministic total.
What to do instead
When a stem mentions risk-adjusted, contingency for risk, or confidence level, look for the expected-value or percentile-based answer and reject plain deterministic totals. Know what P50 and P80 mean for contingency sizing.
Omitting or misplacing indirect costs, overheads, and owner costs when building a total installed cost, producing a direct-cost-only answer.
The stem often emphasizes material and labor quantities, so candidates stop at direct cost and forget the structure of a complete estimate (direct, indirect, overhead, owner/project costs, contingency, escalation).
What to do instead
Build a mental checklist of the full estimate structure and run every total-cost question through it before selecting an answer; verify which cost categories the stem explicitly includes or excludes.
Failing to apply a productivity or learning-curve adjustment when the scenario describes repetitive work or changed conditions (weather, congestion, overtime).
Candidates take the base labor rate or first-unit hours at face value and ignore that labor productivity factors modify quantities and hours, not just wage rates.
What to do instead
Flag keywords indicating repetition, learning, or adverse conditions and apply the appropriate factor to labor hours/quantities. Distinguish adjustments to hours from adjustments to rates.
Ignoring the estimate basis document and answering questions about deliverables as if the estimate were only a number.
Candidates focus study time on calculations and under-prepare on the qualitative deliverables (basis of estimate, reconciliation, review records), so they miss questions about what must be documented and why.
What to do instead
Study the basis of estimate as a defined deliverable: know its typical contents (scope, assumptions, exclusions, methodology, class, accuracy, contingency basis) and be able to identify missing or contradictory basis elements.
Treating change control, estimate reviews, and benchmarking as optional administrative steps rather than integral parts of the estimating management process.
These topics feel less technical, so candidates skim them and cannot answer questions about review gates, reconciliation of estimates, or how historical data feeds benchmarking and continuous improvement.
What to do instead
Map the estimating process end to end (kickoff, data gathering, review, reconciliation, approval, feedback loop) and learn where change control, benchmarking, and lessons-learned fit in that sequence.
Misreading units and time basis (per hour vs per day, currency, escalation periods) and carrying an arithmetic slip through to the final choice.
Exam items mix units and periods deliberately; candidates compute quickly under time pressure and select the first answer matching their raw number without checking the unit or period requested.
What to do instead
Write the unit of every intermediate value, convert to a single consistent time basis before computing, and sanity-check the magnitude of the result against the inputs before choosing an answer.