Front-end planning is the work an owner does before committing full funding to a capital project. This guide explains how the process is structured, how two Construction Industry Institute (CII) tools are used to test readiness, and where planning most often breaks down, including on projects built abroad.
What front-end planning is
A 2018 US Department of Energy (DOE) workshop presentation by DOE’s Matthew West and Arizona State University professor G. Edward Gibson Jr. defines the practice as “the process of developing sufficient strategic information” with which owners can “address risk and make decisions to commit resources.” The presentation reduces its aims to three ideas: build the right project, scope the right things and set the stage for successful execution.
CII reports that assessments of projects with effective front-end planning have shown cost differences of six to 25 percent and schedule differences of six to 39 percent. Its research teams studied 1,081 projects worth $96.5 billion and engaged more than 800 professionals from 279 organizations. The DOE presentation puts the average cost of effective planning at 1.5% to 5%, depending on project type and complexity.
Step 1: Work through the gates
The CII model shown in the DOE presentation moves through three planning phases before design and construction: feasibility, concept and detailed scope. The phases are separated by decision gates numbered 0 to 3. By Gate 3, the point CII links to funding decisions, about 30% of the design effort is generally complete.
Step 2: Score the scope with PDRI
CII’s Project Definition Rating Index (PDRI) is a score sheet that “identifies and precisely describes each critical element in a scope definition package.” Versions exist for building, industrial and infrastructure projects, with further editions for small industrial and small infrastructure work, mining, and manufacturing and life sciences. For hybrid projects, CII suggests the building version when architects are the primary designers and the industrial version when process or mechanical engineers are.
Higher scores indicate weaker definition and more risk. CII says the original tool was meant to support funding decisions at Gate 3, but that experience shows it should be used more than once before that point, depending on size and complexity. DOE’s environmental management program has described using PDRI to identify gaps and risks “more so than a numerical score,” so the resulting gap list can matter more than the total.
Step 3: Add the international layer
Standard scope checks do not cover the hazards of working in another jurisdiction. CII commissioned its International Project Risk Assessment (IPRA) because US firms pursuing work abroad faced “risks unique to projects in foreign jurisdictions.” The tool “focuses on the international aspects and does not address issues considered basic to the project,” so it complements scope tools such as PDRI rather than replacing them.
The original IPRA lists 82 risk elements, each assessed for likelihood of occurrence and relative impact. It is written for both owners and contractors and covers risks across the project’s entire life cycle.
A similar argument appears in investment commentary. An article on the website of Egemen Mustafa Sener says that local regulation, market opportunities, existing infrastructure and financial risk should be weighed together before a step abroad is taken. IPRA gives project teams a structured way to do that on a specific job.
Step 4: Close the gaps before setting the baseline
An assessment only helps if it leads to action. On a $1 billion Strategic Petroleum Reserve life-extension project described in the DOE presentation, government and contractor staff carried out front-end planning jointly as an integrated project team, ran the assessment before and after the Critical Decision 1 approval, and used the gap list to generate actions.
Common problems
- Baselines set too early. A 2008 DOE root cause analysis, cited in the presentation, ranked incomplete front-end planning before project baselines as the top issue of 143 identified.
- Too few people or too little time. The same analysis listed insufficient personnel, missing skills, inadequate time and insufficient planning budgets among the causes.
- Missing stakeholders. The presentation describes a privately owned $135 million refinery upgrade that ran 26% over its baseline budget and 20% behind schedule. Reported problems included key stakeholders left out of planning, team turnover and poor leadership.
- Incomplete technical definition. On the same refinery project, the reported gaps included client specifications, fire protection studies and pipe stress analysis.
- Using a home-market checklist abroad. CII’s international research exists because foreign jurisdictions add risks that a standard scope review does not address.
The caveats
The performance ranges above are CII’s reported findings from its own research program, not guaranteed savings, and the DOE figures come from a workshop presentation. These tools support, but do not replace, applicable standards, contract requirements, local legal advice and qualified engineering judgment.


