The Risk Framework as Claims Reduction

Overview
In construction, most claims are not random events. They are usually risks that were never identified, never clearly allocated, or never actively managed until they became disputes. The PMI Construction Professional (PMI-CP) body of knowledge treats the risk management framework as one of the strongest tools for preventing claims. This guide explains what the concept means, why it matters, how it works in practice, and how to handle exam questions on it.

Why It Is Important
1. Claims are costly and destructive. They consume management time, legal fees, and expert costs. They delay projects, damage relationships, and erode profit margins for every party.
2. Most claims trace back to risk. Typical sources include unforeseen ground conditions, design errors, scope ambiguity, late information, weather, supply chain disruption, regulatory change, and owner-directed changes. Each of these is a foreseeable risk category.
3. Prevention is cheaper than resolution. Under the dispute resolution hierarchy, the best outcome is avoiding a dispute altogether. Next comes resolving it early through negotiation. Arbitration and litigation come last. A sound risk framework works at the very top of this hierarchy.
4. It supports collaborative delivery. Modern contract models such as NEC, IPD, alliancing, and partnering rely on shared risk visibility. This replaces adversarial claim-making with joint problem-solving.
5. It protects entitlement. When a claim is legitimate, a well-run risk process produces the records, notices, and baselines needed to substantiate it quickly and fairly.

What It Is
The Risk Framework as Claims Reduction is the principle that systematic, proactive risk management across the project life cycle reduces both the frequency and the severity of claims. It does this by:
- Identifying risks early, starting in planning and procurement.
- Allocating each risk clearly to the party best able to control or bear it.
- Pricing and funding risks through contingency, allowances, and management reserve.
- Monitoring risks continuously and triggering early warnings.
- Responding through agreed mitigation before impacts crystallize.
- Documenting everything, so that any residual claim is resolved on facts rather than opinion.
In short, a claim is often a risk event whose ownership and consequences were not agreed in advance. The risk framework makes that agreement explicit.

How It Works
1. Risk identification during planning and procurement
Use techniques such as workshops, expert judgment, checklists, lessons learned, site investigations, constructability reviews, and design reviews. Identify risks before the contract is signed so they can be addressed in the contract documents. For example, geotechnical surveys reduce differing site condition claims.

2. Clear contractual risk allocation
The contract is the primary risk allocation tool. Key principles:
- Allocate each risk to the party best able to control, manage, or absorb it.
- Use clear clauses on differing site conditions, force majeure, changes, delays, price escalation, and liquidated damages.
- Avoid ambiguous or one-sided transfers. Pushing uncontrollable risk onto a contractor usually produces inflated bids, contractor failure, or aggressive claims.
- Choose a contract type that suits the risk profile. Under fixed price, the contractor bears cost risk. Under cost reimbursable, the owner bears more. Unit price and GMP models share risk.
- Use a baseline reports approach, such as a Geotechnical Baseline Report, to set objective thresholds for entitlement.

3. Risk register linked to contract clauses
Each risk in the register should record its owner, probability, impact, response strategy, trigger, and the contract clause that governs it. This lets everyone see who bears what before an event occurs.

4. Contingency and reserves
Contingency reserve covers known risks (known-unknowns). Management reserve covers unknown-unknowns. When funded risks occur, they are drawn from contingency rather than becoming contested claims. Some contracts use shared risk pools or pain/gain mechanisms.

5. Early warning and notification processes
Contracts such as NEC require parties to issue early warnings of anything that could affect cost, time, or quality. Risk reduction meetings follow. Timely notice requirements, including time-bar clauses, ensure issues surface while they can still be mitigated cheaply.

6. Integrated change control
Many claims are really unapproved or disputed changes. A disciplined change management process works as follows: identify the change, assess its impact, agree on price and time, approve it, and update the baselines. This converts potential claims into agreed variations.

7. Monitoring, schedule, and cost control
Several tools let teams detect deviations early, before they escalate:
- An agreed baseline schedule (CPM)
- Regular schedule updates
- Earned value analysis
- Progress reporting
Agreed schedules also make delay analysis more objective if a claim does arise.

8. Documentation and records management
Keep daily logs, RFIs, meeting minutes, photographs, correspondence, and notices. Good records reduce disputes about facts. They also allow quick, fair settlement of valid claims and rebuttal of weak ones.

9. Stakeholder communication and partnering
Regular risk reviews, open-book approaches, and partnering charters build trust. Dispute review boards or standing neutrals can also be used. These mechanisms resolve issues at the lowest level and earliest stage.

10. Lessons learned
Feed claims and risk outcomes back into the organizational process assets. This improves future identification and allocation.

The Claims Avoidance Chain
Identify risk, then allocate it in the contract, then price or fund it, then monitor triggers, then give early warning, then mitigate jointly, then process it through change control, then document the outcome. Each link that breaks increases the chance of a claim.

Illustrative Example
A highway project team commissions extra soil borings during design. They then include a geotechnical baseline report in the contract. Rock is later encountered beyond the baseline. Because the baseline exists, entitlement is clear and the change is priced through the agreed mechanism. No dispute arises. Without the baseline, the same event would likely become a contested differing site conditions claim.

Exam Tips: Answering Questions on The Risk Framework as Claims Reduction
1. Prefer proactive over reactive answers. If the options include identifying or mitigating the risk early versus filing, defending, or litigating a claim, the proactive option is usually correct.
2. Think 'best able to control'. For risk allocation questions, choose the answer that assigns the risk to the party with the most control or capacity. Avoid answers that transfer all risk to one party regardless of control.
3. The contract is the main allocation tool. When asked how to prevent disputes over responsibility, look for clear contract clauses, baseline reports, or defined change and notice procedures.
4. Early warning beats late notice. Answers involving prompt notification, risk reduction meetings, and collaborative mitigation are strongly favored.
5. Follow the dispute resolution hierarchy. The order is avoidance, then negotiation, then mediation or DRB, then adjudication, then arbitration, then litigation. Pick the least adversarial step that fits the scenario.
6. Change control is claims prevention. If a scenario describes an informal instruction or undocumented scope change, the best answer usually routes it through formal change control.
7. Documentation is always relevant. Answers that strengthen records, baselines, and the risk register are often the best next step.
8. Distinguish reserves. Contingency is for identified risks and is usually controlled by the project manager. Management reserve is for unknown risks and usually requires sponsor or management approval.
9. Watch for 'first' or 'best next' wording. The first step is usually to assess the situation or review the risk register and contract. Escalation is rarely the first step.
10. Recognize poor practice traps. Common wrong options include:
- Ignoring a risk because it is the other party's problem
- Withholding information
- Hiding contingency
- Imposing onerous clauses
- Skipping notice requirements
11. Link risk to contract type. Expect questions on which party bears more risk under fixed price, cost plus, unit price, GMP, or design-build. Expect questions on how that choice affects claim likelihood.
12. Use collaborative delivery cues. Words such as partnering, alliancing, IPD, and shared savings point toward joint risk management answers.

Sample Question Approach
Scenario: During excavation, the contractor notices groundwater levels higher than shown in site data. What should the project manager do first?
Reasoning: Do not jump to rejecting or approving a claim. First, ensure prompt notification and an early warning or risk review. Next, check the risk register and the contract clauses, such as differing site conditions. Then agree on mitigation and document the conditions. The best answer is the one that triggers the agreed risk and notice process collaboratively.

Key Takeaways
- Most claims are unmanaged or poorly allocated risks.
- Clear allocation, adequate funding, early warning, change control, and good records are the core claims reduction tools.
- In the exam, favor proactive, collaborative, contract-based, and well-documented actions over adversarial or reactive ones.