Claims Prevention Through Front End Planning

5 minutes 5 Questions

In the PMI Construction Professional (PMI-CP) framework, claims prevention through Front End Planning (FEP) means that the most effective way to manage claims and disputes is to stop them from arising, by investing effort before contract award and construction begin. FEP, also called pre-project planning, is the early phase where owners and project teams define scope, assess risk, choose delivery methods, and set up governance. Research such as the Construction Industry Institute's work on the Project Definition Rating Index (PDRI) shows that well-defined projects have fewer changes, less cost growth, and fewer disputes. Key FEP practices that prevent claims include: 1. Clear scope definition: Ambiguous or incomplete scope is a leading cause of claims. A thorough scope, a basis of design, and an agreed level of design completeness reduce later arguments over what was included. 2. Risk identification and fair allocation: Early risk workshops identify threats such as unforeseen site conditions, permitting delays, and supply chain issues. Each risk should go to the party best able to control it, which avoids adversarial disputes later. 3. Site investigation: Geotechnical surveys, utility mapping, and existing-condition assessments reduce differing site condition claims. 4. Contract strategy and clarity: Choosing the right delivery method, such as design-bid-build, design-build, or IPD, and writing clear clauses on change orders, notice requirements, delays, and payment prevents misunderstandings. 5. Constructability and design reviews: Involving contractors early finds design errors, conflicts, and impractical sequences before they become costly changes. 6. Realistic baselines: Achievable schedules and estimates with appropriate contingencies reduce delay and acceleration claims. 7. Governance and documentation: Defined change management, document control, and communication protocols create the records needed to resolve issues quickly. 8. Dispute resolution planning: Setting up escalation ladders, partnering, or Dispute Review Boards from the start encourages early, low-cost resolution. For PMI-CP practitioners, FEP turns claims management from a reactive, costly process into a proactive strategy that protects relationships, budgets, and schedules.

Claims Prevention Through Front End Planning (PMI-CP: Claims and Dispute Resolution)

Introduction
In the PMI Construction Professional (PMI-CP) framework, claims and disputes are treated as some of the most costly and damaging risks to any construction project. The most effective way to manage a claim is to prevent it from ever arising. Claims Prevention Through Front End Planning (FEP) is the disciplined practice of finding, analysing and resolving the root causes of future claims during the earliest phases of a project. This happens before design is frozen, before contracts are signed and before construction starts.

Why It Is Important
1. Influence versus cost curve: The ability to influence project outcomes is highest at the start of a project, and the cost of making changes is lowest. A scope ambiguity fixed during planning costs very little. The same ambiguity found during construction can trigger change orders, delays, acceleration claims and litigation.
2. Root causes of claims are planning failures: Industry studies (for example, CII research on Front End Planning and Project Definition Rating Index, PDRI) show that most construction claims come from a small set of causes:
• incomplete or ambiguous scope
• poor or late design
• unrealistic schedules
• inadequate site investigation, which leads to differing site conditions
• unclear risk allocation
• weak contract documents
• poor stakeholder alignment
All of these can be addressed during front end planning.
3. Cost and schedule predictability: Projects with high-quality FEP consistently show better cost performance, schedule performance, fewer change orders and fewer disputes.
4. Relationship preservation: Disputes damage trust between owner, contractor, designer and other parties. Clear expectations set at the start support collaborative delivery.
5. Legal and financial exposure: Litigation and arbitration consume management time, legal fees and expert costs, and they disrupt cash flow. Prevention is far cheaper than resolution.

What It Is
Front End Planning, also called pre-project planning, front end loading (FEL) or project definition, is the process of developing enough strategic information for owners to address risk and decide whether to commit resources. Claims prevention through FEP means deliberately using this phase to remove the conditions that create claims. Its key elements are:
• Clear business case and project objectives: stakeholders agree on what success looks like.
• Well-defined scope: a complete scope statement, a work breakdown structure (WBS) and documented deliverables, exclusions, assumptions and constraints.
• Adequate design maturity before contract award: appropriate to the chosen delivery method.
• Thorough site investigation: geotechnical, environmental, utility and existing-condition surveys. These reduce differing site condition claims.
• Appropriate project delivery method and contract type: for example, design-bid-build, design-build, CM at Risk, IPD, lump sum, cost-plus, GMP or unit price. Each is matched to the level of scope certainty.
• Fair and clear risk allocation: each risk is assigned to the party best able to control it.
• Realistic schedule and budget: estimates and contingencies are based on validated quantities and productivity.
• Constructability reviews: experienced builders are involved early to find buildability problems.
• Contract document quality reviews: drawings, specifications and contract terms are checked for conflicts, gaps and ambiguities.
• Stakeholder engagement: permitting authorities, utilities, community groups and end users are consulted early.
• Defined change management, notice and dispute resolution procedures: these are written into the contract before work starts.

How It Works
Step 1: Phase-gated planning. FEP is usually run as a series of stage gates, for example:
• FEL-1 (Feasibility)
• FEL-2 (Concept)
• FEL-3 (Detailed scope or basis of design)
At each gate, the project's definition is assessed, often with tools such as the PDRI. The project moves forward only when the level of definition is good enough.

Step 2: Claims risk identification. The team runs risk workshops focused on likely claim triggers, such as:
• differing site conditions
• owner-caused delays
• design errors
• late approvals
• access restrictions
• weather
• supply chain disruption
• regulatory changes
Lessons learned and historical claims data from similar projects feed this analysis.

Step 3: Scope and design definition. The team develops the scope baseline, WBS, WBS dictionary and basis of design. Interfaces between packages are clarified, because interface gaps are a common source of claims.

Step 4: Contract strategy and drafting. The team selects the delivery method and contract form, for example AIA, ConsensusDocs, FIDIC or NEC. The contract should clearly address:
• scope
• specifications and order of precedence
• notice requirements and time bars
• change order procedures
• differing site conditions clauses
• force majeure
• liquidated damages
• payment terms
• schedule requirements
• dispute resolution tiers (negotiation, then dispute review board, then mediation, then arbitration or litigation)

Step 5: Constructability and bid-document reviews. Independent reviews (biddability, constructability, operability and sustainability) are carried out. Pre-bid conferences and formal clarification processes (RFIs and addenda) remove ambiguity before pricing.

Step 6: Baseline documentation and record-keeping plan. The team sets up a schedule baseline, cost baseline, document control, daily reporting and photo documentation protocols. Good records discourage weak claims and support quick resolution of valid ones.

Step 7: Partnering and alignment. Partnering sessions, team charters and early dispute avoidance mechanisms (for example, a Dispute Avoidance Board or Dispute Review Board) create a culture of raising issues early.

Step 8: Handover to execution. All planning outputs flow into the project management plan, the risk register and the change control process. This ensures continuity into construction.

Key Concepts to Remember
• Prevention is better than resolution: PMI-CP strongly favours proactive approaches.
• Risk is allocated to the party best able to manage it. Unfair risk transfer leads to inflated bids or claims.
• Ambiguity causes claims. Courts often interpret ambiguity against the drafter (contra proferentem), so owners have a strong reason to draft clearly.
• Early contractor involvement (ECI) through CM at Risk, design-build or IPD improves constructability and reduces disputes.
• Site investigation reduces differing site condition claims, which are among the most common claim types.
• Notice provisions and documentation protocols must be set before construction starts.
• Lessons learned registers from previous projects are critical inputs.

Exam Tips: Answering Questions on Claims Prevention Through Front End Planning
1. Choose the proactive answer. When a question asks for the BEST way to reduce claims, pick the option that acts earliest. Examples include clarifying scope before award, running a constructability review or doing a site investigation. Reacting after a claim is filed is rarely the best answer.
2. Look for root causes. If a scenario describes recurring change orders or disputes, the correct answer usually fixes the source, such as incomplete scope definition or poor design. Answers that only treat the symptom are weaker.
3. Match contract type to scope certainty. • Well-defined scope suits lump sum or fixed price.
• Uncertain scope suits cost-plus, GMP with contingency or unit price.
A mismatch is a classic claim generator. Expect questions on this.
4. Risk allocation logic. Pick answers that assign each risk to the party best able to control it. Be careful with options that push every risk onto the contractor. This often leads to higher bids and more claims.
5. Differing site conditions. If the scenario mentions unknown subsurface conditions, the best preventive action is a thorough geotechnical investigation shared with bidders, plus a clear differing site conditions clause.
6. Stakeholder alignment. Questions about conflicting expectations usually point to early stakeholder engagement, an agreed project charter or partnering workshops.
7. Document quality. If a scenario mentions conflicting drawings and specifications, the answer often involves:
• bid-document reviews
• an order-of-precedence clause
• pre-bid clarification through addenda
8. Know the sequence. Follow PMI logic: plan first, then execute. Prefer answers that review, analyse or consult the plan or contract before escalating. Never jump straight to arbitration or litigation when earlier steps are available.
9. Recognise FEP tools. Know these by name:
• PDRI
• stage gates (FEL-1/2/3)
• constructability reviews
• value engineering
• risk registers
• lessons learned
• partnering
• Dispute Review Boards
• early contractor involvement
10. Watch for keywords. Words such as before contract award, during planning, prevent, minimise future claims and most effective signal that the answer should come from front end planning activities.
11. Eliminate distractors. Rule out answers that are:
• adversarial (for example, threatening liquidated damages)
• too late (for example, hiring a claims consultant after a dispute)
• outside the project manager's authority
12. Remember the cost of change curve. Any question about when changes are cheapest or most influential should be answered with the earliest project phase.

Sample Question Approach
Scenario: An owner plans a hospital expansion on a brownfield site with limited records of existing utilities. What should the project manager do FIRST to minimise future claims?
Best answer: Commission a comprehensive site and utility investigation during front end planning, and include the findings in the bid documents with a clear differing site conditions clause.
Why the other options are weaker: Adding a large contingency, transferring all risk to the contractor, or planning to resolve disputes through arbitration do not prevent the root cause.

Summary
Claims Prevention Through Front End Planning is about investing effort early to define scope, investigate conditions, allocate risk fairly, draft clear contracts and align stakeholders. In the PMI-CP exam, the strongest answers are almost always the most proactive, root-cause-focused, collaborative and earliest-stage actions. Remember: a claim prevented in planning is the cheapest claim you will ever manage.
Test mode:
Start practice test

PMI-CP - Claims Prevention Through Front End Planning Example Questions

Test your knowledge of Claims Prevention Through Front End Planning

Question 1

During Front End Planning for a design-build airport terminal, the owner's project manager reviews the draft tender package. The owner's requirements state one peak-hour passenger throughput. An appendix copied from an earlier feasibility study states a higher figure. The draft contract has no order-of-precedence clause, and the tender is due to issue in two weeks. The design-build contractor will size the building systems from whichever figure governs. Which action BEST prevents a later claim over the basis of design?

Correct Answer: Reconcile the two figures and state one governing throughput in the tender set

Reconciling the conflicting figures and stating one governing peak-hour throughput removes the ambiguity at its source, so every bidder sizes building systems from the same basis of design and there is nothing left to dispute later.
An order-of-precedence clause only ranks documents. The conflicting figure stays in the set and invites interpretation arguments. Asking bidders to state their own assumed figures produces non-comparable bids and shifts the definition of scope to the contractor. Labeling the appendix for information only still leaves a contradictory number that bidders may rely on.
Key concept: Front End Planning should establish a single, unambiguous basis of design before tender to prevent scope claims.

Question 2

During Front End Planning for a lump-sum hospital wing, the deterministic schedule shows 20 months. A Monte Carlo schedule risk analysis of the same logic returns P50 = 22 months and P80 = 25 months. The sponsor's stated policy requires 80% confidence in committed dates. The sponsor proposes tendering a 20-month completion date backed by liquidated damages. Which approach BEST limits future delay and acceleration claims?

Correct Answer: Tender a 25-month completion date that matches the P80 result and the confidence policy

Committing to the P80 duration of 25 months meets the sponsor's 80% confidence policy. It sets a realistic, risk-informed completion date, so the contractor is less likely to overrun and then claim delay or acceleration costs.
A 22-month date at P50 gives only a coin-flip chance of success, and holding the gap as owner float does not change the contractual date the contractor must meet. Keeping the 20-month date with budget contingency still commits to a date with very low confidence, so acceleration and delay disputes remain likely. Relying on liquidated damages does not remove the risk; contractors price it, dispute it, or claim the date was unachievable.
Key concept: setting committed schedule dates from probabilistic schedule risk analysis confidence levels.

Question 3

During Front End Planning for a lump-sum pipeline, the owner will obtain all crossing permits and grant work-area access to the contractor. The draft contract lists fixed access dates. However, the permitting lead reports that those dates were copied from a prior project and that the authority's review durations for this corridor are unconfirmed. On earlier lump-sum projects, late access led to owner-caused delay claims. Which step BEST reduces this claim exposure before tender?

Correct Answer: Confirm review durations with the authority and base the contract access dates on them

Confirming the authority's review durations and setting contract access dates from them removes the root cause of past claims. It turns the owner's access commitments into realistic, achievable obligations before the lump-sum price is fixed.
Shifting permitting to the contractor moves an owner-controlled risk to a party less able to manage it, which invites inflated bids and still leaves dispute potential. Keeping the copied dates and reserving float for the owner keeps unrealistic commitments in place and invites float-ownership disputes. Recording the risk and raising contingency only funds claims rather than preventing them.
Key concept: validating owner-furnished obligations during Front End Planning to reduce claim exposure.

More Claims Prevention Through Front End Planning questions
15 questions (total)
Start 15 question test

Other Claims and Dispute Resolution concepts

Adjudication, Arbitration and LitigationChange Orders Versus ClaimsClaim Documentation and Contemporaneous RecordsCommunication Practices That Prevent DisputesContract Types and Claim FrequencyDelay, Disruption and Acceleration ClaimsDelivery Methods and Claim FrequencyDispute Review BoardsEarly Resolution of ClaimsLessons Learned and Historical Claims DataNegotiation and Mediation of DisputesNotice Requirements and Time BarsProblem Areas That Generate ClaimsQuantifying Claim Cost and Time ImpactsRoot Cause Analysis of ClaimsSelecting a Dispute Resolution TechniqueThe Claims Process and Key Intervention PointsThe Risk Framework as Claims Reduction
All Claims and Dispute Resolution questions · PMI-CP practice test