Definition Claims management is the systematic process of identifying, documenting, substantiating, submitting, negotiating, and resolving contractual claims arising from capital project execution. A claim is a formal request for additional payment, time extension, or other relief under a contract, submitted when the claimant believes they are entitled to compensation beyond what has been agreed through normal variation processes. In capital projects, claims management addresses several categories of disputed entitlement: Variation claims: Disputed valuation of instructed changes Extension of time claims: Requests for schedule relief due to delay events Prolongation claims: Cost recovery for extended project duration Disruption claims: Compensation for productivity loss caused by employer or third-party actions Acceleration claims: Recovery of costs incurred to mitigate delays Unforeseen conditions claims: Entitlement arising from physical conditions differing from contract assumptions Change in law claims: Compensation for regulatory changes affecting project cost or duration Termination claims: Entitlement arising from contract termination Effective claims management requires: Contemporaneous records: Documentation created at the time events occur, not reconstructed later Real-time capture: Recording of events, instructions, and impacts as they happen on site or in the yard Digital approval workflows: Systematic processes for obtaining and documenting stakeholder acknowledgment Contractual compliance: Adherence to notice requirements, time limits, and procedural obligations Causation analysis: Clear demonstration of cause-and-effect between events and claimed impact Quantum substantiation: Detailed calculation of claimed amounts with supporting evidence Professional presentation: Clear, well-organised claim documents that facilitate assessment Claims management is distinct from variation management in that claims address disputed matters where normal agreement processes have not succeeded. However, the foundation for successful claims is laid through effective variation and change management—particularly the real-time capture of events and systematic documentation that begins when changes first occur. Stakeholder Risk Exposure Claims management affects all project stakeholders, with exposure depending on contract type, project complexity, and the effectiveness of contemporaneous documentation systems. Risk Exposure by Industry Stakeholder Construction Marine & Offshore Shipbuilding Mining Project-Based Manufacturing Client / Owner 6 7 5 8 5 Contractor / Builder 7 8 8 7 7 Consultant / Supervisor 4 5 4 5 4 Designers 5 6 6 5 6 Laboratories / QC 2 3 3 3 3 QA and HSE 4 6 5 7 4 Lenders / Banks 5 7 6 8 4 Insurers 5 7 6 7 5 Rating Scale: 1 = Lowest risk exposure, 10 = Highest risk exposure Stakeholder Roles in Claims Management Stakeholder Role in Claims Management Key Concerns Owner / Developer / E&P Operator Receives and assesses claims; defends against unjustified claims; settles valid claims Cost exposure, project budget, dispute avoidance Contractor / Shipbuilder / Mining Contractor Prepares and submits claims; substantiates entitlement; negotiates settlement Entitlement recovery, margin protection, cash flow Consultant / Independent Engineer / Employer’s Representative Assesses claims on behalf of owner; certifies valid entitlements; provides expert opinion Fair assessment, professional liability, contractual compliance Designer / Architect / Naval Architect Provides technical information; may be subject to claims for design errors Liability exposure, PI insurance, documentation QA and HSE Provides records supporting or defending claims Documentation accuracy, compliance evidence Lenders / Project Finance Banks Monitors claims exposure; assesses impact on project cost and viability Budget impact, completion risk, covenant compliance Insurers / Sureties May provide coverage for certain claims; assesses claims impact on project risk Coverage determination, subrogation rights The Critical Role of Real-Time Capture The foundation of successful claims management is contemporaneous documentation—records created at the time events occur, not reconstructed weeks or months later. Modern project delivery demands real-time capture systems that operate at the point of work. Why Contemporaneous Records Matter Record Type Created in Real-Time Reconstructed Later Credibility High—records created when events fresh Low—records questioned as self-serving Accuracy High—details captured immediately Low—memory fades, details lost Completeness High—systematic capture ensures coverage Low—gaps where events not recalled Audit trail Clear—timestamps, locations, authors verified Unclear—authenticity questioned Dispute outcome Favourable—evidence supports narrative Unfavourable—lack of evidence undermines position The Cost of Poor Documentation Claims fail not because they lack merit but because they lack evidence: Documentation Failure Consequence No contemporaneous notice Contractual time bar; claim rejected procedurally No site records of event Cannot prove event occurred as described No record of instruction Disputed whether instruction was given No productivity records Cannot quantify disruption impact No approval documentation Disputed whether work was authorised Reconstructed records Credibility challenged; records discounted Real-Time Capture at Point of Work Effective claims management requires capturing information where work happens: Site and yard capture requirements: Information Type Capture Method Timing Daily conditions Digital daily report with photos End of each shift Instructions received Logged with date, time, source, content Immediately upon receipt Events and incidents Incident report with witnesses, photos Within hours of occurrence Resource deployment Labour, equipment, material records Daily Progress achieved Quantity surveys, progress photos Daily or as work completes Delays encountered Delay notice with cause and impact Same day Changed conditions Condition report with documentation Upon discovery Mobile and field capture technology: Modern claims protection requires technology that enables capture at the point of work: Mobile applications for site personnel to record events Photo and video capture with automatic timestamps and geolocation Voice-to-text for rapid narrative recording Offline capability for remote sites without connectivity Automatic synchronisation when connectivity restored Integration with project control systems Digital Approval Workflows and Portal-Based Documentation The second critical element of claims protection is systematic approval workflows—obtaining and documenting stakeholder acknowledgment of events, instructions, and impacts through digital systems that create auditable records. Why Portal-Based Approval Matters Traditional paper-based or email-based approval processes create vulnerabilities: Traditional Approach Vulnerability Paper site instructions Lost, damaged, disputed authenticity Email chains Buried in inboxes, incomplete threads, version confusion Verbal instructions No record; disputed whether given Manual sign-off Delayed, incomplete, disputed signatures Scattered documentation Cannot locate records when needed Digital portal-based systems address these vulnerabilities: Portal Capability Claims Protection Benefit Centralised repository All records in one searchable location Automatic timestamps Indisputable record of when documents created/submitted User authentication Clear identification of who created/approved records Workflow enforcement Cannot bypass required approvals Audit trail Complete history of all actions and changes Version control Clear record of document evolution Notification and escalation Ensures timely response to submissions Access control Appropriate visibility for all stakeholders Portal-Based Approval Workflow Event Occurs on Site/Yard │ ▼ ┌─────────────────────────────┐ │ Site/Yard Personnel │ │ Captures Event via Mobile │ │ App with Photos/Details │ │ (Timestamped, Geolocated) │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ Automatic Upload to │ │ Project Portal │ │ (Even from Remote Sites) │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ Contractor PM Reviews │ │ and Submits Formal Notice │ │ via Portal │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ Automatic Notification to │ │ Client/Consultant via │ │ Portal │ └──────────────┬──────────────┘ │ ▼ ┌─────────────────────────────┐ │ Client/Consultant Reviews │ │ in Portal with Full │ │ Supporting Documentation │ └──────────────┬──────────────┘ │ ┌─────┴─────┬──────────────┐ │ │ │ APPROVE REQUEST INFO REJECT │ │ │ ▼ ▼ ▼ ┌──────────────┐ ┌──────────┐ ┌──────────────┐ │ Approval │ │ Query │ │ Rejection │ │ Recorded │ │ Logged │ │ Recorded │ │ with │ │ Response │ │ with │ │ Timestamp │ │ Required │ │ Reasons │ │ and User ID │ │ │ │ (Preserved │ │ │ │ │ │ for Claim) │ └──────────────┘ └──────────┘ └──────────────┘ │ │ ▼ ▼ ┌─────────────────────────────────────────────┐ │ Complete Audit Trail Available for │ │ Claims Substantiation or Defence │ └─────────────────────────────────────────────┘ Stakeholder Portal Access Different stakeholders require different portal access for claims-related documentation: Stakeholder Portal Access Typical Actions Contractor Site Team Event capture, daily reports, photo upload Record events as they occur Contractor PM Review, submit notices, variation requests Formalise claims-relevant submissions Contractor Commercial Claims preparation, quantum documentation Compile and substantiate claims Client/Owner PM Review submissions, approve/reject/query Respond to contractor submissions Consultant/Engineer Review, certify, provide determinations Assess and certify entitlements Subcontractors Event capture, submit claims upstream Document sub-level events Lenders (view only) Monitor claims status and exposure Assess project risk Approval Documentation Requirements For claims protection, portal approval workflows must capture: Element Requirement Claims Value Instruction acknowledgment Client/consultant confirms receipt of notice Proves notice was given Event acknowledgment Client/consultant acknowledges event occurred Establishes factual basis Impact acknowledgment Agreement on principle of impact (even if quantum disputed) Establishes causation Direction to proceed Instruction to execute work despite dispute Protects entitlement Rejection with reasons Documented basis for rejection Preserved for claim/dispute Time-stamped responses When responses provided Proves compliance with time limits Context in Project-Based Industries Claims management operates across all project-based industries, with practices reflecting industry-specific contractual frameworks, typical disputes, and documentation requirements. Construction In construction, claims commonly arise from: Claim Type Typical Causes Documentation Requirements Extension of time Weather, late information, variations, third parties Delay analysis, programme updates, notices Prolongation costs Extended site presence due to excusable delay Resource records, cost substantiation Disruption Out-of-sequence work, acceleration, congestion Productivity records, measured mile analysis Variations Disputed scope, valuation methodology, rates Instructions, measurements, cost build-ups Unforeseen ground Differing site conditions from contract basis Site investigation, condition reports, expert opinion Key characteristics: Standard forms (FIDIC, NEC, JCT) have specific claims procedures Time bars for notice are strictly enforced Quantity surveyor role in claims assessment Adjudication commonly used for interim resolution Site capture priorities: Daily diaries with weather, resources, progress, events Photographic records of conditions and progress Instruction logs with immediate capture Delay notices submitted same-day via portal Marine and Offshore In marine and offshore projects, claims reflect high-value operations: Claim Type Typical Causes Documentation Requirements Vessel standby Weather delays, client readiness, access Vessel logs, weather records, standby notices Weight growth Design development beyond tolerance Weight reports, design change records Offshore delays Installation issues, hook-up complexity Daily offshore reports, progress records Change orders Scope evolution, interface changes Change documentation, impact assessments Key characteristics: High daily rates magnify delay impacts Weather records critical for delay claims Multiple contractor interfaces create complexity Lender scrutiny of claims exposure Yard and offshore capture priorities: Vessel daily reports with automatic upload Weather station data integration Weight tracking with variance alerts Offshore progress with photo/video documentation Shipbuilding In shipbuilding, claims address long production cycles: Claim Type Typical Causes Documentation Requirements Owner changes Specification modifications Change request documentation, impact assessments OFE delays Owner-furnished equipment late delivery Delivery schedules, delay notices, mitigation records Classification changes Rule changes, surveyor requirements Classification correspondence, compliance costs Currency claims Exchange rate movements (if contractual) Rate records, contract provisions Key characteristics: Long build cycles create change accumulation Currency provisions vary by contract Owner-furnished equipment creates interface claims Milestone payment disputes common Yard capture priorities: Production records by block and zone OFE delivery tracking with automatic alerts Classification survey records Change instruction logs with owner approval Mining In mining projects, claims reflect geological and remote execution challenges: Claim Type Typical Causes Documentation Requirements Geotechnical Ground conditions differing from baseline Geological records, condition reports, expert opinion Scope changes Resource updates, process modifications Change documentation, cost impact Regulatory Permit conditions, compliance requirements Regulatory correspondence, compliance costs Remote site Logistics, weather, access constraints Site records, delay documentation Key characteristics: Geological uncertainty creates significant claims exposure Multiple contractor interfaces in EPCM delivery Remote sites challenge documentation systems Community and regulatory claims increasing Site capture priorities: Geological logging with digital capture Daily site reports even in remote conditions Weather and access records Regulatory correspondence tracking Project-Based Manufacturing In project-based manufacturing, claims address specification and delivery disputes: Claim Type Typical Causes Documentation Requirements Specification changes Client modifications, design development Change orders, impact assessments Delivery delays Site not ready, sequence changes Delivery notices, storage costs Inspection delays Client inspection not timely Inspection schedules, delay records Rejection disputes Disputed non-conformance Inspection records, technical substantiation Key characteristics: BIM/design integration enables rapid change identification Delivery coordination claims common Quality documentation critical for rejection disputes Clear specification baseline essential Factory capture priorities: Production records by element and project Inspection and test documentation Delivery scheduling with client confirmation Change instruction capture with approval workflow Why This Concept Exists Claims management exists because capital projects involve complex contractual relationships where disagreements are inevitable and significant sums are at stake. Contracts cannot anticipate every situation Even well-drafted contracts cannot address every circumstance: Events occur that were not contemplated Contract language is subject to interpretation Parties have different understandings of obligations Changed circumstances alter the balance of the agreement Claims provide the mechanism for resolving disputes within the contractual framework. Variation processes have limits Normal variation management assumes parties can agree: On what constitutes a variation On the appropriate valuation On entitlement to time relief On responsibility and liability When agreement fails, claims provide the escalation path. Financial stakes justify formal process Capital project claims involve significant sums: Prolongation claims may represent months of site costs Disruption claims may represent substantial productivity loss Delay damages may be measured in millions Disputed variations may accumulate to major exposure These stakes justify the investment in formal claims management. Contemporaneous records are the only reliable evidence When disputes arise months or years after events: Memories fade and differ between parties Documents may be lost or incomplete Personnel may have left the project Self-serving reconstruction is challenged Contemporaneous records—created in real-time at the point of work—provide the only reliable evidence for claims resolution. Digital systems create the required audit trail Traditional documentation methods cannot provide the audit trail that claims require: Paper records are lost, damaged, or disputed Email chains are incomplete and scattered Verbal communications leave no trace Manual processes have gaps and delays Digital portal systems create the complete, timestamped, authenticated records that claims substantiation demands. How It Works Conceptually Claims management operates through a lifecycle from identification through resolution, supported by real-time capture and digital approval workflows. Claims Lifecycle Potential Claim Event │ ▼ ┌────────────────────┐ │ REAL-TIME CAPTURE │ │ Site/yard records │ │ event with photos, │ │ details, witnesses │ └─────────┬──────────┘ │ ▼ ┌────────────────────┐ │ NOTICE │ │ Formal notice via │ │ portal within │ │ contract time │ │ limits │ └─────────┬──────────┘ │ ▼ ┌────────────────────┐ │ PORTAL APPROVAL │ │ WORKFLOW │ │ Client/consultant │ │ acknowledges or │ │ responds │ └─────────┬──────────┘ │ ▼ ┌────────────────────┐ │ SUBSTANTIATION │ │ Compile detailed │ │ claim with full │ │ supporting │ │ evidence │ └─────────┬──────────┘ │ ▼ ┌────────────────────┐ │ SUBMISSION │ │ Formal claim │ │ submitted via │ │ portal with all │ │ documentation │ └─────────┬──────────┘ │ ▼ ┌────────────────────┐ │ ASSESSMENT │ │ Claim reviewed │ │ and determined │ └─────────┬──────────┘ │ ┌─────┴─────┐ │ │ AGREED DISPUTED │ │ ▼ ▼ ┌────────┐ ┌────────────┐ │SETTLE- │ │ DISPUTE │ │MENT │ │ RESOLUTION │ └────────┘ └────────────┘ Notice Requirements Most contracts impose strict notice requirements: Requirement Typical Provision Consequence of Non-Compliance Initial notice Within 7–28 days of event Time bar—claim rejected Particulars Within 28–84 days of event Claim limited to noticed amount Final claim Within defined period after event Entitlement lost Continuing events Regular updates required Ongoing entitlement lost Portal-based notice compliance: System Capability Compliance Benefit Automatic event timestamping Proves when event occurred Notice templates Ensures required content included Deadline tracking Alerts before time limits expire Submission confirmation Proves notice was submitted Receipt acknowledgment Proves notice was received Audit trail Complete record for disputes Claims Substantiation A well-substantiated claim contains: Section Content Evidence Source Executive summary Overview of claim and relief sought — Factual narrative Chronological description of events Site records, daily reports, correspondence Contractual basis Contract provisions establishing entitlement Contract documents, specifications Causation Link between events and claimed impact Programme analysis, expert opinion Quantum Detailed calculation of claimed amount Cost records, resource data, invoices Supporting documents Evidence supporting all assertions Portal-stored documentation Evidence hierarchy for claims: Evidence Type Weight Source Contemporaneous records Highest Real-time capture at point of work Portal-documented approvals High Digital workflow with timestamps Correspondence Medium-High Emails, letters (preferably in portal) Expert analysis Medium Delay analysis, quantum assessment Witness statements Medium Statements from project personnel Reconstructed records Low Documents created after the fact Delay Claims and Programme Analysis Delay claims require programme-based analysis: Analysis Method Description Application As-planned vs. as-built Compare planned schedule to actual Simple delay demonstration Impacted as-planned Insert delay events into baseline Prospective entitlement assessment Collapsed as-built Remove delays from as-built Retrospective analysis Time impact analysis Contemporaneous impact at each event Industry-preferred method Windows analysis Period-by-period delay assessment Complex multi-cause delays Disruption Claims and Productivity Analysis Disruption claims require productivity evidence: Analysis Method Description Evidence Required Measured mile Compare disrupted to undisrupted productivity Detailed productivity records by period Earned value Compare earned to planned productivity Progress and resource records Industry studies Apply published productivity factors Recognised study data Total cost Claim all overrun as disruption (least preferred) Elimination of other causes Claims Negotiation and Resolution Claims resolution follows escalating steps: Step Process Typical Outcome Project level PM-to-PM negotiation Settlement of straightforward claims Commercial level Commercial manager negotiation Settlement of moderate claims Executive level Senior management negotiation Settlement of significant claims Mediation Facilitated negotiation Non-binding resolution attempt Adjudication Binding interim decision Rapid resolution (common in construction) Arbitration Binding final decision Formal dispute resolution Litigation Court proceedings Last resort Risk Exposure by Contract Type Claims exposure varies significantly by contract type: Stakeholder Fixed-Price Design-Build EPC EPCM Cost-Plus PPP/BOT Client / Owner 5 4 3 7 8 7 Contractor / Builder 8 8 9 5 4 7 Consultant / Supervisor 4 5 4 7 5 5 Designers 5 8 8 5 4 6 Laboratories / QC 2 3 3 3 2 3 QA and HSE 3 4 4 4 3 5 Lenders / Banks 5 6 6 7 5 8 Insurers 5 6 7 5 4 7 Rating Scale: 1 = Lowest claims exposure, 10 = Highest claims exposure Key observations: EPC and Fixed-Price create highest contractor claims exposure—scope disputes and valuation disagreements concentrate risk EPCM and Cost-Plus shift claims risk toward owners—contractor claims are fewer but owner exposure to cost growth is higher Design-Build and EPC create designer claims exposure through design responsibility PPP/BOT creates complex claims dynamics across construction, operation, and concession terms Lenders face claims exposure through project cost and completion impact Why Generic Approaches Fail Generic enterprise systems fail to support effective claims management because they lack the real-time capture capability, approval workflows, and documentation structures that claims require. No real-time site/yard capture Claims depend on contemporaneous records created at the point of work. Generic systems: Have no mobile capture capability for site personnel Cannot capture photos with automatic timestamps and geolocation Lack offline capability for remote locations Cannot integrate field data with project control systems No portal-based approval workflow Claims protection requires documented approvals through systematic workflows. Generic systems: Have no project-specific portal capability Cannot enforce approval workflows for instructions and notices Lack audit trails for stakeholder responses Cannot track notice compliance and time limits No integration with project control Claims substantiation requires data from across project systems. Generic systems: Cannot link claims to affected WBS and cost codes Cannot extract resource and productivity data for quantum Cannot integrate with schedule for delay analysis Cannot connect variation registers with claims registers No claims register capability Claims management requires structured tracking: Claim status and progression Notice compliance monitoring Settlement tracking Dispute status Generic systems lack claims-specific data structures and workflows. Spreadsheet and email-based documentation creates fatal gaps Many organisations manage claims documentation through spreadsheets and email: No single source of truth Version control problems Incomplete audit trails Documents scattered across inboxes Cannot demonstrate contemporaneous capture Vulnerable to challenge in disputes Where it Applies Project Execution. Ongoing identification and documentation of potential claims throughout construction. Commercial Management. Claims preparation, submission, and negotiation as part of commercial function. Variation Management. Escalation of disputed variations to formal claims. Final Account. Claims resolution as part of project closeout and final account settlement. Dispute Resolution. Claims documentation supporting adjudication, arbitration, or litigation. Lessons Learned. Claims analysis for contract improvement and risk allocation refinement. Common Misconceptions Misconception: Claims are adversarial and should be avoided. Reality: Claims are a legitimate contractual mechanism for resolving disputes about entitlement. Avoiding justified claims means accepting losses that the contract does not require. Professional claims management protects commercial position without unnecessary conflict. Misconception: Good relationships eliminate the need for claims documentation. Reality: Relationships change, personnel leave, and memories differ. Good relationships should make claims resolution easier, not claims documentation unnecessary. Contemporaneous records protect both parties regardless of relationship quality. Misconception: Claims can be prepared after the project from available records. Reality: Claims prepared after the fact from incomplete records are vulnerable to challenge. The credibility and completeness of contemporaneous documentation—created in real-time through systematic capture—determines claims outcomes. Misconception: Notice requirements are formalities that can be addressed later. Reality: Notice requirements are strictly enforced by tribunals and courts. Time-barred claims are rejected regardless of merit. Portal-based systems with automatic tracking prevent notice compliance failures. Misconception: Small potential claims are not worth documenting. Reality: Small claims accumulate; today’s minor issue may be part of tomorrow’s major claim. Systematic capture of all events through real-time systems costs little and protects against cumulative exposure. Misconception: Digital systems are not accepted as evidence. Reality: Properly implemented digital systems with audit trails, timestamps, and authentication are increasingly preferred over paper records. The key is demonstrating system integrity and contemporaneous capture. Related Topics What Is Risk Management in Capital Projects? — Claims often arise from risk events; risk management informs claims exposure. What Is Change and Variation Management? — Disputed variations escalate to claims; change documentation supports claims. What Is a Risk Register? — Claims exposure should be tracked as project risk. What Is Contingency Management? — Claims affect contingency through both exposure and recovery. What Is Contractual Risk Allocation? — Contract terms determine claims entitlement. What Is Project Cost Control? — Claims values must integrate with cost management. RELATED ASSETS Related Industries Construction Project-based Manufacturing Marine and Offshore Construction Mining and Quarrying Shipbuilding and Repairs RELATED ASSETS Related Stakeholders Owner/Developer E&P Owners Mine & Quarry Owner Consultants General Contractors Marine Contractor Shipbuilders Mining Contractor RELATED ASSETS Related Roles C-level Executives Project Manager Bidding Manager Cost Estimator Cost Controller Go to Previous Topic Previous Topic Return to What is? Go to Hub Go to Next Topic Next Topic