Independent Cost Review

Navigation: estimate-classification | index

An Independent Cost Review (ICR) is a structured evaluation of a project estimate by a reviewer with no prior involvement in producing that estimate. The goal is to catch errors, challenge assumptions, and verify that the estimate is fit for its intended decision — before the owner commits to a budget or the contractor commits to a GMP.

ICR is required by the U.S. Department of Energy (DOE Order 413.3B) at Critical Decision gates and recommended by CII at FEED gate for projects above a threshold cost. It is not an audit — it is a technical peer review focused on cost confidence and completeness.

---

When ICR Is Required or Recommended

Context	Trigger	Authority
U.S. DOE capital projects	All CD-2 (performance baseline) and CD-3 (start of construction) gates	DOE Order 413.3B
CII member capital projects	FEED gate (Class 3 estimate) — recommended for projects >$20M TIC	CII Research Report 268
IPA project benchmarking	Any project seeking IPA benchmarking certification	IPA standard practice
Owner internal governance	Varies — many owners require ICR at FEL-3 gate for projects >$5–10M	Owner capital project procedures
GMP negotiation	Owner may require contractor to fund/accept ICR before finalizing GMP	Contract requirement

---

Who Conducts the ICR

Reviewer Type	Use Case	Independence Level
Owner’s independent estimating group	Large owners with in-house capital project teams (e.g., CPG, pharma, energy companies)	Medium — same organization, different team
Third-party cost consultant	Projects where owner lacks in-house expertise or arm’s-length review is required	High — separate firm, no prior involvement
IPA (Independent Project Analysis)	Projects seeking formal benchmarking and FEP scoring alongside ICR	High — specialized independent firm
DOE Independent Project Review Team	DOE-funded capital projects	Highest — government-mandated reviewer

Key requirement: The ICR reviewer must not have contributed to the estimate being reviewed. A team member who built the estimate cannot independently review it.

---

ICR Scope and Process

What the Reviewer Examines

1. Estimate basis documentation (BOE)

   • Is the BOE complete? Are assumptions documented?
   • Are exclusions explicit and reasonable?
   • Is the estimate class appropriate for the project phase?

2. Methodology and technique

   • Is the estimating method appropriate for the level of design definition?
   • Are parametric benchmarks used where appropriate? Are they calibrated to comparable projects?
   • Is bottom-up takeoff performed on the appropriate portions of scope?

3. Scope completeness

   • Does the estimate capture the full program?
   • Are indirect costs (general conditions, permits, temporary facilities) included?
   • Are design fees, owner costs, and commissioning costs accounted for?

4. Quantified claims and benchmarks

   • Are unit costs sourced from credible references (RSMeans, AACE, IPA, historical data)?
   • Do $/SF or $/unit benchmarks align with comparable projects?
   • Are outlier line items explained?

5. Contingency

   • Is the contingency calculation method documented?
   • Is the contingency level appropriate for the estimate class and design maturity?
   • Is escalation separated from contingency?

6. Risk register

   • Are major risks identified?
   • Are risk costs quantified or at minimum qualitatively assessed?

Typical ICR Findings Categories

Finding Category	Description	Frequency
Scope omission	An identifiable scope element has no cost in the estimate	Common at Class 3–4
Benchmark outlier	A line item $/unit or $/SF is significantly above or below comparable project data	Common
Methodology mismatch	Estimating technique too aggressive for the design maturity (e.g., bottom-up unit costs on undefined scope)	Moderate
BOE incompleteness	Assumptions not documented; exclusions not stated	Common
Contingency understated	Contingency % is lower than AACE RP 18R-97 recommended range for the estimate class	Common
Escalation combined with contingency	Escalation not broken out as a separate line item	Moderate
Double counting	Same scope included in both a sub estimate and a GC-supplied line item	Occasional

---

CII FEP Score and ICR Correlation

CII Research ties Front End Planning (FEP) score to project outcomes — and ICR is a component of a high FEP score.

FEP score components include:

• Scope definition completeness
• Technology assessment
• Site assessment
• Project execution plan maturity
• Estimate and schedule quality (ICR outcome feeds this)

FEP Score	Avg. Cost Growth	Avg. Schedule Growth
>65 (good)	4.8%	5.7%
35–65 (fair)	10.3%	12.4%
<35 (poor)	19.6%	23.2%

A clean ICR (few findings, no major scope omissions) is one indicator of a high-FEP project. An ICR with major findings at FEED gate is a signal that the project needs more definition before entering execution — proceeding without addressing findings increases cost growth risk.

---

ICR and GMP Negotiation

In design-build, the owner may commission or accept an ICR as part of GMP validation:

• Owner uses ICR findings to challenge GMP line items where benchmark data shows the contractor is above market
• Contractor uses a clean ICR to demonstrate estimate rigor and justify the GMP number
• Significant ICR findings (major scope omissions, outlier unit costs) give the owner leverage to renegotiate before executing the GMP
• An ICR does not replace the owner’s right to negotiate — it provides an evidence base for both sides

Practical note: GMP negotiations go faster and more smoothly when the BOE is complete and the contractor can respond to each ICR finding with documentation. An undocumented estimate is a negotiating liability.

---

Deliverable: ICR Report

A standard ICR report contains:

1. Executive summary — overall confidence rating, number of findings by severity, recommendation (proceed / proceed with conditions / revise and re-review)
2. Findings log — each finding numbered, categorized, cost impact estimated, recommendation stated
3. Scope completeness matrix — program elements vs. estimate line items
4. Benchmark comparison — key unit costs vs. reference data
5. Contingency adequacy assessment — comparison of contractor contingency to AACE recommended range for the class

---

Related Pages

• Estimate Classification and BOE — AACE class definitions and BOE requirements
• BOE Template — BOE structure that supports a clean ICR
• Phase-by-Phase Workflow — where ICR fits in the gate sequence
• Delivery Methods and Contracts — GMP negotiation context

Navigation: estimate-classification | index