Lessons Learned and Historical Claims Data

Introduction
In the PMI Construction Professional (PMI-CP) framework, claims and disputes are treated as foreseeable risks that can be managed. They are not seen as random misfortunes. One of the strongest tools for managing them is the systematic capture and reuse of lessons learned and historical claims data. This guide explains what these concepts are, why they matter, how they work in practice, and how to answer exam questions on them.

1. What Are Lessons Learned and Historical Claims Data?

Lessons learned is the knowledge gained while performing a project. It covers what went well, what went poorly, and what should be done differently next time. In a claims context, it covers:
• the root causes of claims and disputes
• how they were handled
• what they cost
• how they could have been prevented or resolved earlier

Historical claims data is the structured, recorded information about past claims. Typical fields include:
• claim type (delay, disruption, differing site conditions, scope change, payment, acceleration, defective design)
• the contract clause involved and the notice timing
• amounts claimed versus amounts settled
• time to resolution
• the resolution method used (negotiation, mediation, dispute review board, adjudication, arbitration, litigation)
• the parties involved
• the supporting documents and the outcome

Together, these sit within the organizational process assets (OPAs), specifically the organization's lessons learned repository and historical information. On a live project, they are recorded in the lessons learned register. At closure, they are transferred into the organizational knowledge base.

2. Why Is It Important?

• Claims are costly and repetitive. In construction, the same claim types recur across projects: ambiguous specifications, late design information, unforeseen ground conditions, poor change control. Historical data reveals these patterns so they can be addressed before they recur.
• Prevention is cheaper than resolution. The PMI-CP philosophy favors claim avoidance first, then early resolution at the lowest possible level. Lessons learned feed claim avoidance directly.
• Better contracts and risk allocation. Data on which clauses generated disputes helps legal and procurement teams draft clearer scope, notice, change, and dispute resolution provisions.
• Better estimating and contingency. Historical claim frequency and value help set realistic contingency reserves and inform quantitative risk analysis.
• Stronger negotiation position. Knowing how similar claims were valued and settled supports fair, evidence-based negotiation and realistic settlement ranges.
• Better selection of dispute resolution methods. Data on the time, cost, and relationship impact of mediation versus arbitration versus litigation guides future choices.
• Organizational maturity and continuous improvement. Capturing knowledge stops the organization from repeating mistakes. It also supports governance, PMO standards, and stakeholder confidence.
• Relationship preservation. Learning which behaviors escalated disputes helps teams collaborate better with owners, contractors, designers, and subcontractors.

3. How It Works: The Lessons Learned Lifecycle for Claims

Step 1: Identify and capture continuously. Lessons should be captured throughout the project, not only at closure. Capture is triggered by:
• the occurrence of a claim
• a phase gate
• a resolution milestone
• a significant change event
The project manager owns the lessons learned register. All stakeholders contribute, including site teams, contract administrators, schedulers, cost engineers, designers, and subcontractors.

Step 2: Document in a structured format. Typical fields include:
• claim ID, date, and type
• contract clause
• description of the event
• root cause
• whether notice was timely
• quantum claimed and awarded
• schedule impact
• resolution method, duration, and cost
• what worked and what did not
• recommendations
• owner of the follow-up action
Consistent categorization (taxonomy) is essential so the data can be analyzed across projects.

Step 3: Analyze root causes. Use these tools to move beyond symptoms to causes:
• fishbone (Ishikawa) diagrams
• the 5 Whys
• Pareto analysis, to find the few claim categories causing most of the cost
• trend analysis
For example, "delay claim" is a symptom. "Late approval of shop drawings due to an undefined review period in the contract" is a root cause.

Step 4: Validate and share. Hold lessons learned sessions (retrospectives, post-claim reviews, close-out workshops) in a blame-free environment. Share results through:
• the PMO
• knowledge management systems
• communities of practice
• updated templates and training

Step 5: Archive into organizational process assets. At project or phase closure, the lessons learned register and the claims log are finalized and archived in the organizational repository. This is an explicit output of closing processes.

Step 6: Apply to future projects. This is the most important step, because a lesson is only learned when behavior changes. Historical claims data is used during:
• Initiation and planning: reviewing past lessons is one of the first activities on a new project. It informs the business case, procurement strategy, and the risk register.
• Risk identification: past claims serve as a checklist of potential risks.
• Contract drafting and procurement: clarifying the clauses that caused past disputes, and choosing the contract type and dispute resolution ladder.
• Estimating: setting contingency and management reserves.
• Change management: strengthening change control and notice procedures.
• Claims preparation and defense: benchmarking claim values and the documentation needed.

4. Key Relationships to Remember

• Lessons learned register (project level, living document) versus lessons learned repository (organizational level, an OPA).
• Claims log/register: tracks active claims. Its closed entries become historical claims data.
• Risk register: fed by historical claims data. Recurrent claim causes become identified risks with responses.
• Documentation and records management: good contemporaneous records are needed both to win claims and to produce reliable historical data.
• Contract administration: lessons often lead to revised notice periods, clearer scope, better change order procedures, and well-designed dispute resolution steps (negotiation, then mediation, then dispute board, then arbitration or litigation).

5. Practical Example
A contractor reviews five years of historical claims data. It finds that 40% of claim value came from differing site conditions on urban projects, mostly because geotechnical investigation was inadequate. It also finds that claims resolved through a dispute board settled in an average of 3 months, versus 18 months in arbitration.

Lessons applied to the next project:
• fund a more thorough geotechnical survey
• include a clear differing site conditions clause with baseline reports
• add a specific risk response and contingency
• propose a standing dispute board in the contract
The result is fewer claims, faster resolution, and preserved relationships.

6. Common Pitfalls
• Capturing lessons only at the end, when people have left and memories have faded.
• Recording lessons but never retrieving or applying them ("lessons documented" is not the same as "lessons learned").
• A blame culture, which suppresses honest input.
• Inconsistent data categories, which prevent analysis.
• Recording only failures and ignoring successful practices.
• Ignoring confidentiality and legal privilege. Sensitive dispute information may need controlled access, sanitization, or legal review before it is shared.

Exam Tips: Answering Questions on Lessons Learned and Historical Claims Data

Tip 1: Prevention and early action win. When a question asks what the project manager should do first or best on a new project, an answer about reviewing historical claims data or lessons learned from similar projects is usually correct. This applies especially during planning, risk identification, or contract preparation.

Tip 2: Lessons learned are continuous. Avoid answers implying lessons are captured only at project closure. PMI expects capture throughout the lifecycle: after each claim, at phase ends, and after resolution.

Tip 3: Know where the information lives.
• Lessons learned register: project document, updated throughout.
• Lessons learned repository and historical information: organizational process assets.
• Archiving into OPAs: an output of closing the project or phase.

Tip 4: Root cause over symptoms. If an option addresses the underlying cause of recurring claims, it beats an option that only resolves the current claim. Examples of underlying-cause fixes include revising contract language, improving change control, and strengthening document control.

Tip 5: Collaborative, blame-free language. Choose answers that involve stakeholders, encourage open sharing, and focus on improvement. Avoid answers that assign blame or hide information.

Tip 6: Link to risk management. Historical claims data is a key input to risk identification and quantitative analysis. If a question asks how to determine contingency or identify likely claim risks, historical data is a strong answer.

Tip 7: Link to negotiation and valuation. When a question involves evaluating or negotiating a claim, using historical data on similar claims to benchmark a fair value is a sound, objective approach.

Tip 8: Lowest-level, fastest resolution. When the data shows that certain dispute resolution methods were faster or cheaper, the correct answer usually recommends using that evidence to select appropriate methods. This favors negotiation and alternative dispute resolution over litigation.

Tip 9: Applying is the point. An option that ensures lessons are actually used is better than one that merely files a report. Examples include updating templates, contract clauses, training, and the risk register.

Tip 10: Watch for confidentiality traps. If the scenario involves sensitive or ongoing litigation, the best answer may involve consulting legal counsel or sanitizing data before broad sharing. It should not involve withholding the lesson entirely.

Tip 11: Read scenario keywords. Phrases such as "recurring disputes," "similar project last year," "same issue happened before," or "to prevent future claims" signal that the expected answer involves lessons learned or historical data.

Tip 12: Eliminate reactive or punitive options. These are rarely correct:
• immediately escalating to litigation
• ignoring past data
• waiting until closure to document
• terminating a contractor without analysis

Sample Question
A project manager is starting a hospital construction project. The organization's previous two hospital projects experienced major delay claims related to late design approvals. What should the project manager do FIRST?
A. Increase the schedule buffer by 20%.
B. Review lessons learned and historical claims data from the previous hospital projects to identify root causes and incorporate responses into the risk register and contract terms.
C. Hire a claims consultant to prepare defenses.
D. Include a clause preventing the contractor from filing delay claims.

Answer: B. B is proactive, uses organizational process assets, addresses root causes, and feeds both risk management and contract design.
• A may follow later, but it is not data-driven as a first step.
• C is reactive.
• D is unfair risk shifting that likely increases disputes.

Summary
Lessons learned and historical claims data turn past pain into future protection. Capture them continuously, analyze them for root causes, share them openly, archive them as organizational process assets, and above all apply them to planning, risk, contracting, estimating, and dispute resolution. On the exam, favor answers that are proactive, collaborative, evidence-based, and focused on prevention and continuous improvement.