Front End Planning and Project Definition
In the PMI Construction Professional (PMI-CP) framework, Front End Planning (FEP) is the early phase in which owners and project teams develop enough strategic information to address risk and decide whether to commit resources to a capital project. It is also called pre-project planning, Front End Loading (FEL), or Front End Engineering Design (FEED). Research by the Construction Industry Institute (CII) shows that thorough FEP improves cost, schedule, and operational performance and reduces costly changes. This is because the ability to influence project outcomes is highest, and the cost of change lowest, at the start of a project. FEP usually runs in three stage-gated phases. FEL-1 (Feasibility) confirms the business need, compares options, and sets an order-of-magnitude estimate. FEL-2 (Concept) chooses the preferred alternative, defines key parameters, and refines cost and schedule. FEL-3 (Detailed Scope) produces the basis of design, execution plan, procurement and contracting strategy, and a control-quality estimate for final investment decision. At each gate, decision-makers decide to proceed, recycle, or cancel. Project Definition is the main output of FEP: a documented, well-understood scope covering business objectives, site conditions, design criteria, permits, stakeholder requirements, and execution approach. The Project Definition Rating Index (PDRI) is a widely used weighted checklist for scoring how complete the scope definition is and for revealing gaps before authorization. Lower PDRI scores correlate with better project outcomes. From a construction risk management perspective, FEP is the first and most effective line of defense. Poor definition causes scope creep, change orders, claims, disputes, and overruns. During FEP, teams identify and analyze risks, assign them through contract strategy, set contingency, include constructability reviews, align stakeholders, and set baselines for monitoring. Effective FEP therefore turns uncertainty into informed decisions. It aligns owner, designer, and contractor expectations and builds a defensible foundation for successful delivery, safety, and long-term asset value.
Front End Planning and Project Definition: Reducing Construction Risk Before It Starts (PMI-CP)
Front End Planning (FEP) is the work done early in a construction project's life cycle to define the project well enough that the owner can make a confident decision to fund and proceed. It goes by several names: Front End Loading (FEL), pre-project planning, feasibility and definition, or programming and schematic design. In the PMI Construction Professional (PMI-CP) context, FEP is one of the strongest risk management tools available. Most of a project's cost, schedule and quality outcome is decided before construction begins, so poor definition at the front end is one of the main root causes of claims, disputes, rework, cost overruns and failed projects.
Why Front End Planning Is Important
1. The Influence Curve. The ability to influence project outcomes is highest at the start, when the cost of making changes is lowest. As design and construction progress, influence drops and the cost of change rises steeply. A change that costs very little on paper during concept development can cost a great deal once concrete is poured. This idea, often called the influence or cost-of-change curve, is central to FEP questions.
2. Proven performance benefits. Research by the Construction Industry Institute (CII) and others shows that projects with well-executed FEP usually achieve:
- Better cost and schedule predictability, with smaller overruns
- Fewer scope changes and change orders
- Better operational performance after handover
- Fewer safety incidents and less rework
- Better alignment among stakeholders
3. Risk identification at the cheapest point. FEP exposes the major uncertainties early, while they can still be designed out, transferred or priced instead of being discovered in the field. Typical examples are site conditions, permitting, utilities, community concerns, technology choices and contracting strategy.
4. Foundation for contracts. A clear scope definition is the basis for choosing a delivery method (Design-Bid-Build, Design-Build, CM at Risk, IPD, EPC). It also supports writing contract scope, allocating risk and preventing disputes. Vague scope leads to claims.
What Front End Planning Is
FEP is the process of developing enough strategic information for owners to address risk and decide whether to commit resources to maximize the chance of success. It covers the period from the initial business idea up to the decision to proceed with detailed design and construction, often called Final Investment Decision (FID) or project sanction.
Typical FEP phases (stage-gated):
Phase 1 / FEL-1: Feasibility (Appraise).
- Confirm the business need and define project objectives
- Screen alternatives
- Prepare an order-of-magnitude estimate (roughly AACE Class 5, around -50% to +100%)
- Gate 1 decision: is the opportunity worth pursuing?
Phase 2 / FEL-2: Concept (Select).
- Evaluate alternative sites, technologies and configurations
- Select the preferred option
- Prepare a conceptual estimate (Class 4)
- Develop an initial risk register and execution strategy
- Gate 2 decision: which option?
Phase 3 / FEL-3: Detailed Scope (Define).
- Develop the basis of design and preliminary engineering
- Prepare the Project Execution Plan, a Class 3 budget-quality estimate (around -20% to +30%) and an integrated schedule
- Finalize contracting strategy and permitting plan
- Gate 3 decision: authorize full funding (FID)
Key deliverables of FEP
- Business case and project charter with clear objectives and success criteria
- Owner's Project Requirements (OPR) and Basis of Design (BOD)
- Scope definition package: site information, design criteria, process or functional requirements, equipment lists, building program
- Project Execution Plan (PEP), covering organization, delivery method, contracting and procurement strategy
- Cost estimate with contingency based on risk analysis
- Integrated master schedule with milestones and long-lead items
- Risk register and risk management plan
- Stakeholder register and engagement plan, including permitting and community relations
- Constructability review findings
- Safety, environmental and quality requirements
How It Works
1. Stage-gate governance. Each FEP phase ends with a formal gate review. Decision-makers, usually the owner or sponsor, review the deliverables and decide go, recycle (rework) or kill. Gates stop projects from moving forward on weak definition and stop unviable projects from consuming capital.
2. Measuring definition with the PDRI. CII's Project Definition Rating Index (PDRI) is a weighted checklist that scores how completely the scope is defined. Versions exist for industrial, building, infrastructure and small projects. Each element is rated from complete to incomplete, and the scores roll up to a total out of 1000.
- Lower scores mean better definition. A threshold of roughly 200 or below is commonly associated with better performance.
- The PDRI is used at gates to find gaps, focus effort and support the decision to proceed.
- High-scoring elements become risk items or action items.
3. Alignment. FEP brings together owner business units, operations and maintenance, designers, key contractors and regulators so that everyone agrees on objectives and priorities, such as the trade-off between cost, schedule and quality. Misalignment is a leading cause of scope creep.
4. Early contractor and constructability input. Bringing construction expertise in early lets the team assess sequencing, site logistics, modularization or prefabrication, access, laydown and safety. This is the purpose of early contractor involvement through CM at Risk, Design-Build or IPD.
5. Risk-based estimating and contingency. Estimate accuracy improves as definition matures. Contingency is set using quantitative risk analysis (for example Monte Carlo) or expected monetary value, tied to the identified risks rather than a flat percentage.
6. Scope freeze and change control. At the end of FEP the scope is baselined, or frozen. Later changes go through formal integrated change control, with impacts assessed against the baseline.
7. Handover to execution. The approved FEP package becomes the basis for detailed design, procurement and construction contracts. Lessons learned are recorded for future projects.
Common FEP Failures (Risk Sources)
- Rushing to construction to meet an arbitrary date, which skips definition
- Unclear or conflicting objectives among stakeholders
- Inadequate site investigation (geotechnical work, hazardous materials, existing utilities)
- Underestimating permitting and regulatory timelines
- Leaving operations and maintenance out of requirements
- Too much reliance on optimistic early estimates (anchoring)
- No formal gate reviews, or gates treated as rubber stamps
- Poor contracting strategy that misallocates risk
Exam Tips: Answering Questions on Front End Planning and Project Definition
Tip 1: Favor early, proactive definition. When a scenario describes scope uncertainty, unclear requirements or pressure to start, the best answer usually invests in better definition before committing. Examples include completing the scope package, holding a gate review, running a PDRI assessment or doing a site investigation. Rushing to mobilize is rarely correct.
Tip 2: Remember the influence curve. If asked when stakeholders have the greatest ability to affect cost or outcome at the lowest cost, the answer is early, during planning or front end planning. The cost of change is highest during construction and closeout.
Tip 3: Know the stage-gate logic. Gates exist to make go, recycle or kill decisions. If deliverables are incomplete at a gate, the correct action is to recycle and complete them, or escalate. Do not proceed and fix it later.
Tip 4: Connect estimate class to definition level. Early estimates have wide ranges, and accuracy improves as the scope matures. If a sponsor demands a firm number at the concept stage, the best response is to explain the estimate's accuracy range and its assumptions, and to set contingency based on risk.
Tip 5: Identify the PDRI. Questions about a tool to measure the completeness of scope definition point to the PDRI. Lower scores mean better definition.
Tip 6: Involve the right stakeholders early. Operations and maintenance staff, end users, regulators, community groups and constructors should give input during FEP. If a scenario reveals missed requirements late, the root cause is usually poor stakeholder engagement or alignment at the front end.
Tip 7: Link FEP to risk management. FEP is when the initial risk register is built, risk responses are chosen and risk is allocated through the contract. For a newly identified major uncertainty in early phases, look for answers that analyze it and either design it out, transfer it contractually or price it into contingency.
Tip 8: Link FEP to delivery method selection. Well-defined scope supports Design-Bid-Build and lump-sum contracts. Poorly defined or fast-track scope favors Design-Build, CM at Risk, cost-plus or IPD, which allow collaboration and flexibility. Know which delivery method fits which level of definition.
Tip 9: Treat scope freeze as a control point. After the FEP baseline is approved, changes must follow formal change control. Never answer with 'just incorporate the change' without assessing its impact and getting approval.
Tip 10: Watch for distractors. Answers that sound efficient, such as 'begin construction to save time,' 'let the contractor figure it out' or 'add a flat 10% contingency,' are usually traps. Choose structured, documented, stakeholder-aligned, risk-based options.
Tip 11: Pick the best answer from the owner or PM perspective. PMI questions reward the response that addresses the root cause and follows process. For FEP that means definition, alignment, gating and risk analysis.
Sample Question
An owner wants to award a lump-sum construction contract next month to meet a board deadline, but the geotechnical investigation is incomplete and operations staff have not reviewed the layout. What should the project manager do first?
Best answer: Inform the sponsor of the risks posed by incomplete definition, and recommend completing the critical FEP deliverables (the geotechnical investigation and the operations review) before the gate decision. Alternatively, recommend changing the contracting approach to fit the current level of definition. Awarding the lump-sum contract now would invite claims and change orders.
Key Takeaways
- FEP is the most cost-effective point to manage construction risk.
- It follows stage-gated phases: Feasibility, then Concept, then Detailed Scope, then FID.
- The PDRI measures how complete the scope definition is.
- Estimate accuracy and confidence in contingency improve as definition matures.
- Alignment, constructability input and early stakeholder involvement are essential.
- In exams, choose answers that complete definition, respect gates, engage stakeholders and apply risk-based thinking before committing to construction.
PMI-CP - Front End Planning and Project Definition Example Questions
Test your knowledge of Front End Planning and Project Definition
Question 1
During Front End Planning for a distribution centre, the owner's team has screened three concept alternatives. The business case targets a stated throughput and the lowest 20-year ownership cost. On current estimates, Alternative B meets both targets, but the utility has not yet confirmed it can supply B's required capacity. Alternative A has a lower capital cost and meets throughput, but carries a higher operating cost. The sponsor asks which alternative to advance into scope definition. Which recommendation BEST fits the situation?
Question 2
During Front End Planning for a coastal wastewater outfall, the owner's team has approved the concept and plans to issue a lump-sum design-build tender next month. The environmental authority has not yet indicated its permit conditions. On similar works, it has imposed seasonal in-water work windows and turbidity monitoring that reshaped construction methods and durations. Which action BEST manages this risk at the current stage?
Question 3
During Front End Planning for a data centre, the sponsor wants all major equipment ordered now to protect the in-service date. The approved basis of design fixes the electrical load and generator capacity. The cooling strategy is still being compared between two options with different plant. Transformers and generators carry 60-week lead times. Cooling plant lead times are shorter. Which approach should the project manager take?