{"id":73498,"date":"2026-08-31T15:15:02","date_gmt":"2026-08-31T18:15:02","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=73498"},"modified":"2026-08-31T15:24:43","modified_gmt":"2026-08-31T18:24:43","slug":"contractual-claim-engineering-how-to-structure-claim","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/contractual-claim-engineering-how-to-structure-claim\/","title":{"rendered":"Contractual Claims in Engineering: How to Technically Structure a Claim"},"content":{"rendered":"\n

A contractual claim \u2014 or claim<\/strong>, in the common terminology of engineering contracts \u2014 is a formal and substantiated assertion of a right, time, cost, or other contractual consequence arising from an event that changed the expected conditions of execution. A technically structured claim is not a generic complaint or simply a spreadsheet of amounts: it must demonstrate which obligation existed, which event occurred, which contractual right is invoked, how the event produced the impact, and how that impact was quantified<\/strong>.<\/p>\n\n\n\n

In construction, EPC, EPCM, design, supply, installation, commissioning, and engineering services, claim quality depends primarily on traceability. The document should allow a third party to reconstruct the sequence baseline \u2192 event \u2192 notice \u2192 effect \u2192 mitigation \u2192 schedule\/cost \u2192 request<\/strong> using verifiable records. When this chain is incomplete, even a real impact may be difficult to prove.<\/p>\n\n\n\n

The technical purpose of a claim is not to maximize a narrative. It is to separate facts, responsibilities, and effects in an auditable manner so that the client, contractor, Owner\u2019s Engineering, technical supervision, contract administration, and legal counsel can decide based on evidence.<\/p>\n\n\n\n

What characterizes a contractual claim in engineering<\/h2>\n\n\n\n

Not every disagreement becomes a claim. During execution there are questions, requests for information, routine adjustments, formalized changes, performance failures, and commercial negotiations. A claim arises when one party maintains that a fact produced a contractual consequence that must be recognized.<\/p>\n\n\n\n

Situation<\/td>Is it necessarily a claim?<\/td>Initial technical treatment<\/td><\/tr>
RFI or design question<\/td>no<\/td>clarify the requirement and record the response<\/td><\/tr>
formal scope change already agreed<\/td>not necessarily<\/td>process the change order\/amendment and update baselines<\/td><\/tr>
additional work performed without a defined price<\/td>potentially<\/td>preserve instruction, scope, quantities, costs, and reservation of rights<\/td><\/tr>
delay in releasing a work front<\/td>potentially<\/td>record the constraint, schedule, resources, and mitigation<\/td><\/tr>
loss of productivity due to interference<\/td>potentially<\/td>document normal and impacted conditions, causation, and production<\/td><\/tr>
ordinary increase covered by an index<\/td>as a rule, not an extraordinary claim<\/td>apply the contractual price-adjustment mechanism<\/td><\/tr>
extraordinary event with economic impact<\/td>potentially<\/td>analyze risk, causation, and rebalancing<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This distinction prevents the claims process from becoming a repository for every problem. Contracts, Scope, and Deliverables Management<\/a> should establish different channels for clarifications, changes, performance deviations, notifications, and claims.<\/p>\n\n\n\n

A claim is not the same as a contract amendment<\/h2>\n\n\n\n

An amendment is an instrument that formalizes a contractual change. A claim is a substantiated assertion that may or may not result in an amendment, agreement, rejection, compensation, extension of time, or another outcome provided by the contract.<\/p>\n\n\n\n

This distinction matters because many projects accumulate \u201cextra work\u201d without formalization and attempt to resolve everything at closeout. When additional work is performed without clear instruction, notice, or records, the issue stops being merely commercial and begins to involve proof of the origin of the obligation.<\/p>\n\n\n\n

The article on contract amendments in construction and engineering services<\/a> examines the mechanisms for formal changes. A claim, in turn, focuses on the technical construction of the assertion and its evidence<\/strong>.<\/p>\n\n\n\n

The anatomy of a technically defensible claim<\/h2>\n\n\n\n

A technically defensible claim is not supported by the event narrative alone. It must connect the clause, baseline, triggering fact, notice, causation, schedule or cost impact, contemporaneous evidence, and mitigation in a single traceable line of argument.<\/p>\n\n\n\n

\n

A claim submitted without a baseline, notice, entitlement, causation, and a traceable calculation may describe a real problem, but it will rarely support a consistent contractual decision.<\/p>\n\n\n\n

Structure or technically assess the claim before negotiation<\/a><\/p>\n<\/div>\n\n\n\n

A robust claim can be viewed as a chain. The asserted right should not appear separately from the fact; the fact should not appear separately from the impact; and the impact should not appear separately from the calculation.<\/p>\n\n\n\n

Technical structure of a contractual claim in engineering<\/title><\/path><\/marker><\/path><\/marker><\/circle><\/marker><\/circle><\/marker><\/path><\/marker><\/path><\/marker><\/g><\/path><\/path><\/path><\/path><\/path><\/path><\/path><\/path><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g><\/g><\/rect>

Contract and baseline<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Event<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Notice<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Entitlement<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Cause and effect<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Schedule and cost impact<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Mitigation<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Quantum and request<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect>

Supporting evidence<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/g><\/g><\/g><\/svg>

Technical structure of a contractual claim in engineering<\/figcaption><\/figure>\n\n\n\n

AACE International treats change management in EPC as a formal process that begins with identifying a potential change, moves through assessment, approval or rejection, and reaches contractual incorporation or dispute treatment. This discipline is valuable because it prevents a change from remaining outside the control system for months until it becomes an accumulated claim.<\/p>\n\n\n\n

Contract and baseline<\/h3>\n\n\n\n

The claim needs to begin with the reference condition: scope, price, schedule, sequence, productivity, responsibilities, access, supplies, assumptions, and risks that existed before the event. Without a baseline, there is no reliable technical comparison.<\/p>\n\n\n\n

Contractual scope definition<\/a> is particularly important. If the obligation was already included, the claim cannot simply treat it as \u201cextra work\u201d; it will be necessary to demonstrate what condition changed and why that changed execution.<\/p>\n\n\n\n

Event<\/h3>\n\n\n\n

The event should be specific: an instruction, constraint, design change, delayed information, area unavailability, regulatory change, unforeseen interference, suspension, requested acceleration, late rejection, sequence change, or another relevant occurrence.<\/p>\n\n\n\n

Dates matter. A good record states when the event began, when it was identified, when it was notified, when it stopped producing effects, and which decisions occurred in the interval.<\/p>\n\n\n\n

Entitlement: what is the basis of the asserted right?<\/h3>\n\n\n\n

In international practice, entitlement<\/strong> is commonly used to designate the contractual or legal basis that would support a right to compensation or time. The same reasoning can be treated as framing the asserted right.<\/p>\n\n\n\n

Engineering should not invent legal interpretations, but it can organize the facts needed for analysis: clauses on access, response times, risk, scope changes, client instructions, force majeure, extensions of time, or payment conditions. The legal issue becomes much clearer when the factual basis is well defined.<\/p>\n\n\n\n

Notification is part of control, not mere bureaucracy<\/h2>\n\n\n\n

Complex contracts often require certain events to be notified within defined deadlines and formats. These rules vary from contract to contract; there is no single universal deadline applicable to every engineering claim.<\/p>\n\n\n\n

Timely notification performs practical functions: it alerts the other party while the event can still be mitigated; enables inspection and joint collection of records; avoids surprise at closeout; identifies the potentially affected clause; and preserves project chronology.<\/p>\n\n\n\n

A useful notice does not need to anticipate a quantum that is not yet known. It should identify the event, the affected obligation or condition, the potential impact, immediate measures, and reservation of an update once the effect can be measured.<\/p>\n\n\n\n

Notice does not replace the complete claim<\/h3>\n\n\n\n

The notice records the occurrence and preserves the contractual position according to the applicable instrument. The complete claim presents the consolidated analysis. Mixing these two documents produces poor extremes: waiting months until all costs are known before notifying, or believing that a two-line letter is sufficient to substantiate the entire claim.<\/p>\n\n\n\n

Good contract administration creates a trail between the initial notice, interim updates, and final submission.<\/p>\n\n\n\n

Causal link: the technical core of the claim<\/h2>\n\n\n\n

The greatest improvement in quality occurs when the narrative stops saying \u201cthere was an event and there was a cost\u201d and begins to demonstrate how one caused the other<\/strong>.<\/p>\n\n\n\n

Consider a change instruction in an electrical room already under installation. To demonstrate causation, it is not enough to attach the revised drawing and the new labor spreadsheet. It is necessary to show what was designed, the stage of installation, which items had to be removed or reworked, which activities were interrupted, which additional resources were mobilized, and why those hours were not part of the original execution.<\/p>\n\n\n\n

A causal chain can be expressed as follows:<\/p>\n\n\n\n

event \u2192 affected obligation \u2192 impacted activity \u2192 additional resource\/time \u2192 resulting cost or schedule impact.<\/strong><\/p>\n\n\n\n

If one link cannot be demonstrated, the corresponding portion should be treated cautiously.<\/p>\n\n\n\n

Contemporaneous records: the raw material of a claim<\/h2>\n\n\n\n

The Society of Construction Law Delay and Disruption Protocol emphasizes the importance of contemporaneous records related to progress and execution circumstances and connected to the programme. The recommendation addresses a common problem: claims prepared months later, with retrospective narratives unable to separate simultaneous facts.<\/p>\n\n\n\n

Record<\/td>What it may demonstrate<\/td>Limitation if used alone<\/td><\/tr>
site log\/daily report<\/td>presence, activity, constraint, weather, equipment, occurrences<\/td>may not demonstrate economic impact<\/td><\/tr>
schedule and updates<\/td>logic, critical path, float, sequence, and variance<\/td>depends on update quality<\/td><\/tr>
meeting minutes<\/td>decisions, open items, and owners<\/td>summary may omit production details<\/td><\/tr>
emails\/letters<\/td>instructions, notifications, and responses<\/td>do not by themselves prove the amount of impact<\/td><\/tr>
measurements<\/td>recognized production<\/td>may not record loss of productivity<\/td><\/tr>
labor records<\/td>hours and resources<\/td>additional hours do not automatically prove entitlement<\/td><\/tr>
photos\/videos<\/td>physical condition and progress<\/td>need date, location, and context<\/td><\/tr>
invoices\/contracts<\/td>actual cost<\/td>cost does not prove contractual causation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The value lies in correlating records. A georeferenced photograph linked to the site log, revised drawing, and schedule activity is far more informative than each document in isolation.<\/p>\n\n\n\n

Schedule claims: delay, extension, and critical path<\/h2>\n\n\n\n

When the claim involves schedule, the question is not merely how many days the event lasted. It is necessary to verify whether and how the event affected the relevant contractual date.<\/p>\n\n\n\n

A ten-day blockage may not generate a ten-day extension if the activity had float or alternative work fronts existed. In another scenario, a two-day instruction may trigger replanning, material procurement, and rework that affect critical activities for a longer period.<\/p>\n\n\n\n

The analysis needs to consider the baseline schedule, updates, network logic, contemporaneous critical path, constraints, concurrent delays, and recovery measures. Delay-analysis methodology can be developed in a specific article; within the claim, the essential point is that the number of days requested must be the consequence of schedule analysis and not merely the administrative duration of the event<\/strong>.<\/p>\n\n\n\n

Delay and disruption are different phenomena<\/h3>\n\n\n\n

Disruption is a loss of efficiency or productivity. It can occur without extending the final completion date. A team may complete the work on time while consuming more hours due to interference, fragmented work fronts, frequent changes, or an inefficient sequence imposed by external conditions.<\/p>\n\n\n\n

The SCL Protocol distinguishes delay analysis from disruption analysis and recommends proof of causation and productivity records. This is particularly relevant in engineering because labor claims often confuse \u201cmore hours spent\u201d with \u201chours causally attributable to disruption.\u201d<\/p>\n\n\n\n

Cost claims: quantum must follow causation<\/h2>\n\n\n\n

Quantum is the quantification of the recognized consequence. It should not be calculated before defining the scope of the event and the affected period.<\/p>\n\n\n\n

Cost component<\/td>Main question<\/td>Typical evidence<\/td><\/tr>
additional labor<\/td>which hours were incremental and for which activity?<\/td>timesheets, site logs, production, payroll records, crew composition<\/td><\/tr>
equipment<\/td>was the resource additionally mobilized or idle because of the event?<\/td>site log, rental records, telemetry, utilization<\/td><\/tr>
material<\/td>was there an additional purchase, loss, replacement, or eligible variation?<\/td>requisition, invoice, quantity, drawing, inspection<\/td><\/tr>
subcontract<\/td>was the change passed through and substantiated?<\/td>contract, change order, invoice, subcontractor calculation<\/td><\/tr>
prolongation<\/td>which costs depend on the additional duration?<\/td>monthly structure, causal period, schedule<\/td><\/tr>
remobilization<\/td>did the interruption require actual remobilization?<\/td>logistics, transport, crew, authorization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Applying generic percentages to the total amount may be inappropriate when more direct data exist. Cost Engineering and Estimating<\/a> should help build a verifiable calculation and eliminate double counting.<\/p>\n\n\n\n

The problem with global claims<\/h2>\n\n\n\n

A global claim aggregates multiple events and presents a total impact without satisfactorily demonstrating the link between specific causes and specific consequences. In projects with hundreds of changes, this approach may seem convenient, but it reduces traceability and makes it difficult to separate responsibilities.<\/p>\n\n\n\n

The SCL Protocol discourages reliance on a global claim when cause and effect can be demonstrated with greater granularity. For engineering, the recommendation is pragmatic: segregate by event or by coherent families of events, identify periods and activities, and show the corresponding costs.<\/p>\n\n\n\n

This does not mean that every minor interference must become a separate process. Related events may be grouped when the causal logic and quantification method remain transparent.<\/p>\n\n\n\n

Mitigation: demonstrate what was done to limit the impact<\/h2>\n\n\n\n

A claim dossier should not show only the problem. It should record the decisions made to reduce the consequence: crew reassignment, replanning, temporary sequence changes, alternative purchasing, additional resources, work on another front, or a proposed technical solution.<\/p>\n\n\n\n

Mitigation has two functions. First, it reduces the actual harm to the project. Second, it helps distinguish the unavoidable impact of the event from costs produced by inaction or internal decisions.<\/p>\n\n\n\n

Documentation should record alternatives evaluated, constraints on implementation, authorization when required, and observed results. The absence of a technically feasible alternative may also be a relevant fact, provided it is demonstrated.<\/p>\n\n\n\n

Recommended structure for a claim dossier<\/h2>\n\n\n\n

A good dossier supports both executive reading and detailed audit. The structure may vary with the contract, but it should separate argument, evidence, and calculation.<\/p>\n\n\n\n

Section<\/td>Expected content<\/td>Purpose<\/td><\/tr>
Executive summary<\/td>event, asserted right, requested schedule\/cost, and main conclusions<\/td>enable an initial decision<\/td><\/tr>
Contract identification<\/td>contract, clauses, hierarchical documents, parties, and owners<\/td>define the governing instrument<\/td><\/tr>
Baseline<\/td>scope, schedule, price, method, resources, and reference risks<\/td>show the original condition<\/td><\/tr>
Chronology<\/td>events and communications in chronological order<\/td>eliminate date ambiguity<\/td><\/tr>
Entitlement<\/td>contractual and factual basis<\/td>show why the request is being made<\/td><\/tr>
Causation<\/td>relationship between event, activity, and impact<\/td>substantiate cause and effect<\/td><\/tr>
Schedule analysis<\/td>logic and number of days, when applicable<\/td>justify extension or time effect<\/td><\/tr>
Quantum<\/td>calculation and criteria<\/td>demonstrate value<\/td><\/tr>
Mitigation<\/td>measures adopted and effects<\/td>separate unavoidable impact<\/td><\/tr>
Evidence<\/td>index of attachments and cross-references<\/td>enable verification<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The dossier should not conceal unfavorable documents. A technically mature analysis recognizes concurrent facts and limitations. This increases credibility and allows substantiated portions to be assessed separately from disputed ones.<\/p>\n\n\n\n

Claim traceability matrix<\/h2>\n\n\n\n

For complex claims, a matrix helps connect each request to the minimum required body of evidence.<\/p>\n\n\n\n

ID<\/td>Event<\/td>Clause\/obligation<\/td>Affected activity<\/td>Period<\/td>Effect<\/td>Evidence<\/td>Value\/days<\/td><\/tr>
C-01<\/td>design revision<\/td>applicable contractual requirement<\/td>panel installation<\/td>recorded dates<\/td>rework<\/td>drawing, site log, timesheet<\/td>calculation C-01<\/td><\/tr>
C-02<\/td>access delay<\/td>release obligation<\/td>area B installation<\/td>recorded dates<\/td>critical-path shift<\/td>letter, schedule, site log<\/td>analysis C-02<\/td><\/tr>
C-03<\/td>interference<\/td>interface matrix<\/td>infrastructure installation<\/td>observed period<\/td>loss of productivity<\/td>photos, production, site log<\/td>study C-03<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The table above is only a conceptual model; actual data must come from the project. The benefit is the ability to audit each line without navigating hundreds of unindexed pages.<\/p>\n\n\n\n

How the client should analyze a claim received<\/h2>\n\n\n\n

The analysis should not begin by trying to \u201cnegotiate the amount down.\u201d First, admissibility and technical logic are tested.<\/p>\n\n\n\n

  1. Confirm the event and chronology<\/strong>, comparing records from both parties.<\/li>
  2. Verify the contract, notice, and framing<\/strong>, including the risk matrix and responsibilities.<\/li>
  3. Reconstruct the baseline<\/strong> to determine what was already included.<\/li>
  4. Test causation and concurrency<\/strong>, identifying contractor-caused factors or simultaneous events.<\/li>
  5. Review schedule and productivity<\/strong> using contemporaneous data.<\/li>
  6. Audit the quantum<\/strong>, eliminating unsupported items and double counting.<\/li>
  7. Record a conclusion by component<\/strong>, indicating acceptance, rejection, adjustment, or the need for additional information.<\/li><\/ol>\n\n\n\n

    Technical analysis of amendments, scope changes, and claims in engineering contracts<\/a> is precisely a decision-support activity: it transforms a volume of documents into a matrix of facts, responsibilities, and effects.<\/p>\n\n\n\n

    How the contractor should prepare the claim without waiting for closeout<\/h2>\n\n\n\n

    Preparation begins on the first day of the contract. The team needs to know notice clauses, document hierarchy, change rules, measurement criteria, base date, risk matrix, and instruction channels.<\/p>\n\n\n\n

    When an event arises, it should enter the change register or contractual event register. From there, the project tracks status, owner, notice deadline, potential impact, pending documents, and decision. If the event is resolved without impact, it is closed. If it evolves, the records are already organized.<\/p>\n\n\n\n

    ISO 21502 recommends formal change control and maintenance of coherent baselines. Applied to claims, this discipline prevents the poor practice of reconstructing the story at closeout from dispersed files.<\/p>\n\n\n\n

    Economic-financial rebalancing and claims: what is the relationship?<\/h2>\n\n\n\n

    A request for economic-financial rebalancing<\/a> may be presented as a claim, but the concepts are not identical. A claim is the structure of the assertion; rebalancing is a possible basis or economic remedy depending on the contractual regime.<\/p>\n\n\n\n

    Likewise, a claim may request an extension of time without cost, recognition of a scope change, compensation for disruption, or another consequence. Therefore, the dossier should clearly state what is being requested<\/strong>, not merely describe the problem.<\/p>\n\n\n\n

    In public contracts, Law No. 14,133\/2021 provides the legal framework for changes, risks, and restoration of the economic equation. In private contracts, the contract and applicable law define the procedure. In either case, technical proof continues to depend on the baseline, event, causation, and quantum.<\/p>\n\n\n\n

    Claim Management as a preventive process<\/h2>\n\n\n\n

    The best claims management is preventive. The objective is not to produce more claims, but to identify changes early, decide quickly, and prevent legitimate events from remaining untreated until the end of the project.<\/p>\n\n\n\n

    Mature governance integrates the change register, RFI, interface matrix, schedule, budget, risks, correspondence, and decisions. If an instruction changes scope, the system should trigger schedule and cost assessment. If a constraint threatens the critical path, the team should record the occurrence and discuss mitigation before the delay becomes consolidated.<\/p>\n\n\n\n

    Interface Management in Engineering Projects<\/a> is an important source of prevention: interfaces without a clear owner, input, output, and deadline frequently generate events that are difficult to attribute later.<\/p>\n\n\n\n

    Errors that reduce claim credibility<\/h2>\n\n\n\n
    Error<\/td>Problem created<\/td>Better practice<\/td><\/tr>
    late notice without checking contractual requirements<\/td>may compromise procedure and mitigation<\/td>understand notice requirements from kick-off<\/td><\/tr>
    claim that \u201cevery delay generates cost\u201d<\/td>confuses event duration with impact<\/td>analyze criticality, resources, and causal period<\/td><\/tr>
    attach thousands of pages without an index<\/td>transfers to the reviewer the work of building the case<\/td>create a traceability matrix<\/td><\/tr>
    use actual cost as automatic proof of entitlement<\/td>cost does not demonstrate responsibility<\/td>link quantum to entitlement and causation<\/td><\/tr>
    ignore self-caused delays<\/td>weakens objectivity<\/td>analyze concurrent causes<\/td><\/tr>
    apply generic percentages unnecessarily<\/td>reduces alignment with actual impact<\/td>prioritize contemporaneous data and verifiable methods<\/td><\/tr>
    change the narrative between letters and the final claim<\/td>creates inconsistency<\/td>maintain a single controlled chronology<\/td><\/tr>
    fail to document mitigation<\/td>makes it difficult to separate unavoidable impact<\/td>record decisions and alternatives<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    The role of Consulting Engineering and Owner\u2019s Engineering<\/h2>\n\n\n\n

    Claims combine planning, cost engineering, document management, scope, contracts, and knowledge of the execution method. A single discipline rarely sees the complete case.<\/p>\n\n\n\n

    Consulting Engineering can support the contracting party in reconstructing the event, analyzing documentation, technically validating productivity, reviewing the schedule, and quantifying impacts. For the contractor, the same capabilities can structure records, chronology, and the technical calculation. On both sides, there should be a clear separation between engineering analysis and legal opinion.<\/p>\n\n\n\n

    Engineering Technical Consulting<\/a> is particularly useful when the documentary volume is high or when the event involves multiple disciplines and interfaces.<\/p>\n\n\n\n

    Preventive claims management is more efficient when the client keeps scope, schedule, communications, measurements, decisions, and changes integrated within the same governance. Potential events are then addressed when they arise, rather than only at closeout, when reconstructing causation and records becomes more costly.<\/p>\n\n\n\n\n\n\n\n\n\n

    Final considerations<\/h2>\n\n\n\n

    A technically strong contractual claim is a chain of evidence, not a rhetorical document. It begins with the baseline, characterizes the event, preserves the notice, identifies the asserted right, demonstrates cause and effect, quantifies schedule and cost, records mitigation, and organizes documents in a traceable manner.<\/p>\n\n\n\n

    The same structure serves both the party submitting and the party analyzing the claim. The contractor can separate demonstrable impacts from perceptions; the client can accept or reject portions with technical justification.<\/p>\n\n\n\n

    Projects that implement change management and contemporaneous records from the beginning tend to reduce the need for late forensic reconstruction. When a dispute arises, the information already exists \u2014 organized by event, activity, period, and consequence \u2014 and the discussion can focus on technical and contractual merit.<\/p>\n\n\n\n

    \n

    Claims are easier to prevent and address when events, changes, communications, and decisions are recorded during execution rather than reconstructed only at contract closeout.<\/p>\n\n\n\n

    Structure contract governance and change control<\/a><\/p>\n<\/div>\n\n\n\n

    Technical references<\/summary>\n

    [1] AACE INTERNATIONAL. Recommended Practice 100R-19: Contract Change Management \u2014 As Applied in Engineering, Procurement, and Construction. 2020. Available at: [AACE International](https:\/\/web.aacei.org\/docs\/default-source\/toc\/toc_100r-19.pdf<\/a>).<\/p>\n\n\n\n

    [2] SOCIETY OF CONSTRUCTION LAW. Delay and Disruption Protocol. 2. ed. 2017. Available at: [SCL](https:\/\/www.scl.org.uk\/resources\/delay-disruption-protocol<\/a>).<\/p>\n\n\n\n

    [3] BRAZIL. Law No. 14,133, April 1, 2021. Public Procurement and Administrative Contracts Law. Available at: [Presidency of the Republic](https:\/\/www.presidencia.gov.br\/ccivil_03\/_ato2019-2022\/2021\/lei\/l14133.htm<\/a>).<\/p>\n\n\n\n

    [4] ADVOCACIA-GERAL DA UNI\u00c3O. Manual de Licita\u00e7\u00f5es e Contrata\u00e7\u00f5es Administrativas. Consultoria-Geral da Uni\u00e3o. Available at: [AGU](https:\/\/www.gov.br\/agu\/pt-br\/composicao\/cgu\/cgu\/manuais\/manualdelicitacoesecontratacoesadministrativaspdf.pdf<\/a>).<\/p>\n\n\n\n

    [5] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21502:2020 \u2014 Project, programme and portfolio management \u2014 Guidance on project management. Available at: [ISO](https:\/\/www.iso.org\/standard\/74947.html<\/a>).<\/p>\n<\/details>\n\n\n\n

    Frequently asked questions<\/summary>\n
    What is a contractual claim in engineering?<\/strong>

    It is a formal and substantiated assertion of a right, time, cost, or other contractual consequence associated with an event. A robust claim demonstrates the baseline, event, basis, causation, impact, quantum, mitigation, and evidence.<\/p><\/div>

    Are a claim and a contract amendment the same thing?<\/strong>

    No. A claim is an assertion that may be accepted, rejected, negotiated, or lead to different consequences. An amendment is an instrument that formalizes a contractual change. An accepted claim may result in an amendment, but the concepts are not equivalent.<\/p><\/div>

    Does every delay entitle a party to additional time and cost?<\/strong>

    No. Responsibility, critical path, float, concurrent causes, mitigation, and the actual effect on resources must be analyzed. Event duration is not automatically equal to an extension of time or compensable prolongation.<\/p><\/div>

    Which documents strengthen a claim?<\/strong>

    The contract, proposal, baseline schedule and updates, site logs, notices, minutes, drawings, RFIs, measurements, productivity records, timesheets, invoices, contextualized photos, and calculations are recurring examples.<\/p><\/div>

    What is the deadline for notifying a claim?<\/strong>

    There is no universal deadline for all contracts. The notice deadline and form must be checked in the contractual instrument and applicable legal regime. International contracts and specific forms may have their own procedures.<\/p><\/div>

    What is causation in an engineering claim?<\/strong>

    It is the demonstration of how the asserted event affected a specific obligation or activity and produced the requested schedule or cost consequence. The chain should connect event, activity, resource, period, and impact.<\/p><\/div>

    What is a global claim?<\/strong>

    It is an assertion that aggregates multiple events and presents a total impact without sufficiently demonstrating the link between specific causes and specific consequences. When data are available, causal segregation tends to produce a more auditable analysis.<\/p><\/div><\/div>\n<\/details>\n\n\n\n

    Complementary technical materials<\/summary>\n

    Related solutions<\/h4>\n\n