Root Cause Analysis of Claims

Introduction
In construction projects, claims are almost inevitable. Delays, cost overruns, design changes, differing site conditions and unclear contract language all create friction between owners, contractors, subcontractors and designers. The PMI Construction Professional (PMI-CP) certification expects candidates to resolve claims and also to understand why they happened. That discipline is called Root Cause Analysis (RCA) of Claims. This guide explains what it is, why it matters, how it works, and how to handle exam questions on it.

1. What Is Root Cause Analysis of Claims?
Root Cause Analysis of Claims is a structured investigation into the underlying causes of a claim. It goes beyond the visible symptom, such as a schedule delay or cost overrun, to find the fundamental process, contractual, communication or management failure that produced it.

A claim is a demand by one party for more time, money or other relief under the contract. A root cause is the deepest controllable cause. If you remove it, the problem will not recur.

For example, a contractor may claim extra cost for rework on a concrete slab. The symptom is the rework. The direct cause might be wrong embedment locations. The root cause might be a weak design coordination process: MEP drawings were never clash-checked against structural drawings, and the RFI process did not flag the conflict early.

2. Why Is Root Cause Analysis of Claims Important?
a) Preventing recurrence: Construction organizations often run similar projects repeatedly. Without RCA, the same mistakes cause the same claims on the next project.

b) Fair allocation of responsibility: RCA separates causation from blame. It identifies which party's action, inaction or risk allocation produced the claim. This supports defensible entitlement decisions.

c) Supporting negotiation and settlement: Clear, evidence-based causes help parties settle at the lowest level, such as direct negotiation. This avoids costly escalation to mediation, arbitration or litigation.

d) Improving contracts and procurement: RCA often reveals poorly drafted clauses, ambiguous scopes, unbalanced risk transfer or inadequate specifications. These findings feed improvements into future contract templates.

e) Organizational learning: RCA findings become lessons learned and update the organizational process assets (OPAs). They also improve risk registers on future projects.

f) Protecting relationships: Fixing systemic issues instead of blaming individuals preserves trust among stakeholders. This is a key PMI value.

g) Financial and schedule control: Claims erode margins and delay completion. Addressing root causes reduces exposure to delay damages, disruption costs and administrative overhead.

3. Common Root Causes of Construction Claims
Exam scenarios often describe a symptom and ask you to spot the underlying cause. Know these categories:

Design and documentation: incomplete, erroneous or uncoordinated drawings and specifications.
Scope definition: vague scope statements, missing items, or gaps between trade packages.
Contract language: ambiguous clauses, conflicting documents, unclear order of precedence, or unrealistic risk transfer.
Change management: undocumented verbal instructions, slow change order approvals, or no formal change control.
Site conditions: inadequate geotechnical investigation, unforeseen subsurface conditions, or unidentified utilities.
Schedule management: unrealistic baselines, poor updating, lack of float management, or owner-caused access delays.
Communication: late RFI responses, poor coordination meetings, or missing notices.
Procurement: late material delivery, supplier failure, or poor subcontractor prequalification.
Payment and cash flow: late payments that cause slowdowns or suspension.
Stakeholder and regulatory: permit delays, authority requirements, or community objections.
Estimating and bidding: underpricing, unbalanced bids, or misread bid documents.
Force majeure and external events: weather, pandemics, or market price escalation.

4. How Root Cause Analysis of Claims Works: A Step-by-Step Process
Step 1: Define the problem. State the claim clearly: what happened, when, where, the impact (time and cost), and which parties are involved. Base the statement on facts, not opinions.

Step 2: Collect data and evidence. Gather the following:

• contract documents
• baseline and updated schedules
• daily logs
• meeting minutes
• RFIs and change orders
• correspondence and notices
• photos
• inspection reports
• cost records
• weather data

Contemporaneous records are the most credible.

Step 3: Establish the timeline and sequence of events. Build a chronology. In delay claims, techniques such as As-Planned vs As-Built analysis, Time Impact Analysis (TIA), Windows Analysis and Collapsed As-Built show how events affected the critical path.

Step 4: Identify causal factors. List all contributing factors. Then distinguish:

• direct causes from contributory causes
• excusable from non-excusable delays
• compensable from non-compensable delays
• concurrent delays, where both parties contributed

Step 5: Apply RCA tools to drill down. The most common tools are:

• 5 Whys: Ask why repeatedly until you reach a process-level cause.
• Ishikawa (Fishbone) Diagram: Groups causes into categories such as People, Process, Materials, Methods, Machines, Environment, Contract and Design.
• Pareto Analysis: Applies the 80/20 rule. A few root causes usually generate most of the claim value or frequency.
• Fault Tree Analysis: A top-down logic diagram of the combinations of events that led to the outcome.
• Cause-and-Effect Matrix / Scatter diagrams: Correlate variables, such as late RFIs against rework cost.
• Change/Barrier Analysis: Compares what was planned with what happened, and identifies which controls failed.
• Timeline/Event and Causal Factor Charting: Visual sequence of events alongside the conditions that enabled them.

Step 6: Validate the root cause. Test it: if this cause had been absent, would the claim still have occurred? Is the cause within someone's control? Is it backed by evidence?

Step 7: Determine entitlement and quantum implications. Link the root cause to contract clauses to decide responsibility (entitlement). Then quantify the impact (quantum) in time and money.

Step 8: Develop corrective and preventive actions.

• Corrective actions fix the current problem.
• Preventive actions stop it happening again. Examples: better constructability reviews, BIM clash detection, clearer contract clauses, faster RFI turnaround standards, better geotechnical surveys, formal notice procedures.

Step 9: Document and share lessons learned. Update the lessons learned register, risk register, OPAs, contract templates and procurement strategies. Communicate findings to stakeholders.

Step 10: Monitor effectiveness. Track claim frequency and value on later projects to confirm the actions worked.

5. Worked Example
Scenario: A contractor claims 45 days of delay and extra cost for foundation work.

The 5 Whys drill-down:

• Why 1: Excavation stopped. Because rock was encountered unexpectedly.
• Why 2: Rock was unexpected. Because the geotechnical report showed only soil.
• Why 3: The report missed the rock. Because only two boreholes were drilled on a large site.
• Why 4: Only two boreholes were drilled. Because the owner cut the site investigation budget to save cost.
• Why 5: The budget was cut. Because there was no risk-based policy for minimum site investigation.

Root cause: No risk-based site investigation policy at the owner organization.
Entitlement: Likely excusable and compensable under a differing site conditions clause, if the contractor gave timely notice.
Preventive action: Set minimum geotechnical investigation standards and include contingency for subsurface risk.

6. Relationship to Other PMI-CP Concepts

• Risk Management: RCA findings update risk registers and improve risk identification.
• Change Management: Many claims trace back to poor change control. RCA strengthens change procedures.
• Contract Administration: RCA reveals clause weaknesses and notice failures.
• Dispute Resolution Hierarchy: Accurate root cause identification enables early settlement through negotiation or a Dispute Avoidance/Adjudication Board (DAAB) before arbitration or litigation.
• Quality Management: RCA tools come from quality management, such as Deming's Plan-Do-Check-Act (PDCA) cycle.
• Lessons Learned and Knowledge Management: RCA is a primary source of organizational learning.

7. Common Pitfalls in Claims RCA

• Stopping at the symptom or the first cause.
• Blaming individuals instead of fixing processes.
• Relying on memory instead of contemporaneous records.
• Ignoring concurrent delay or shared responsibility.
• Letting commercial bias shape the analysis. Each party wants a favorable conclusion, so objectivity is essential.
• Not converting findings into preventive actions.
• Doing RCA only after the project ends, when evidence is lost and people have moved on.

Exam Tips: Answering Questions on Root Cause Analysis of Claims
Tip 1: Look past the symptom. Many questions describe a visible problem, such as delay, cost overrun or rework. The correct answer usually targets the underlying process or system issue, not the surface event.

Tip 2: Prefer process fixes over blame. PMI favors systemic, collaborative solutions. Options that fire, blame or penalize individuals are usually wrong. Choose options that improve processes, procedures or contracts.

Tip 3: Gather facts first. When asked what the project manager should do FIRST, the answer is often to collect and review the facts: contract documents, records, schedules and correspondence. Do not jump to conclusions or immediate settlement.

Tip 4: Know which tool fits which situation.

• Many possible causes across categories: Fishbone/Ishikawa diagram.
• Drilling down a single chain of causation: 5 Whys.
• Prioritizing the causes that produce most claims: Pareto chart.
• Showing how combinations of events led to failure: Fault Tree Analysis.
• Delay causation on the critical path: Time Impact Analysis or Windows Analysis.

Tip 5: Link root cause to contract entitlement. Expect questions on whether a cause makes a delay excusable or non-excusable, and compensable or non-compensable. Always check the contract clauses, such as differing site conditions, force majeure, changes and notice requirements.

Tip 6: Remember notice and documentation. A frequent root cause of rejected claims is failure to give timely written notice. If a scenario mentions verbal instructions or missing notice, poor documentation is likely the root issue.

Tip 7: Always close the loop. The best answers include corrective AND preventive action, plus updating lessons learned and the risk register. If an option mentions capturing lessons learned or updating OPAs after RCA, it is often correct.

Tip 8: Watch for concurrent delay. If both parties contributed, the answer usually involves apportioning responsibility, not assigning all of it to one side.

Tip 9: Favor early, low-level resolution. RCA supports negotiation and dispute avoidance. When choosing between escalating to arbitration and analyzing causes then negotiating, PMI generally prefers the collaborative path first.

Tip 10: Separate the key terms.

• Root cause = fundamental, controllable cause.
• Contributing cause = factor that made the problem worse.
• Direct cause = immediate trigger.

Exam distractors often present a direct cause as if it were the root cause.

Tip 11: Read for keywords. Words like recurring, repeated, systemic, across multiple projects or prevent in future signal that the answer is RCA and preventive improvement, not a one-off fix.

Tip 12: Stay objective and ethical. RCA must be impartial. Avoid options that manipulate data, hide records or pre-decide the outcome. This aligns with the PMI Code of Ethics: honesty, fairness and responsibility.

Sample Exam-Style Question
A construction company has experienced repeated claims from subcontractors over late payments on three consecutive projects. What should the project manager do FIRST?
A) Replace the accounts payable staff
B) Settle all outstanding claims immediately
C) Perform a root cause analysis of the payment process using claim records
D) Add stricter penalty clauses for subcontractors

Correct answer: C. The recurring pattern signals a systemic issue. Analyzing the process with factual data identifies the true cause, such as approval bottlenecks or invoicing requirements. Option A blames individuals. Option B treats the symptom. Option D shifts risk without fixing the problem.

Summary
Root Cause Analysis of Claims turns claims from costly disputes into learning opportunities. Remember the sequence: define the problem, collect evidence, build the timeline, identify causal factors, apply RCA tools, validate, link to entitlement, implement corrective and preventive actions, and share lessons learned. On the PMI-CP exam, choose answers that are fact-based, process-focused, collaborative, contract-aware and forward-looking.