A claim versus a change in plain language: when a disagreement becomes a claim
The excavation extra has been disputed for sixty days. A final refusal arrives and the coordinator labels the folder claim. The project manager needs to know which formal process applies and whether an earlier communication already required action.
A change proposal asks the project to review altered work and its commercial effects. A claim is a formal assertion of relief under the applicable contract and law, with definitions and procedures that must be checked. An unresolved change can lead to a claim, but a renamed folder or final refusal does not automatically determine its legal status. Ask the company's advisers to identify the basis, required recipient, submission content and earliest relevant deadline.
For example, the United States federal disputes clause defines a claim as a written demand asserting a right to payment, adjusted terms or other relief, and distinguishes routine undisputed invoices. Its changes clause separately addresses changed work and adjustments. These are examples of defined contract processes, not Canadian rules or deadlines to copy into another project.
Identify the required process before changing the label
- State what remains disputed. Record the event, instruction, requested amount or time effect, and the response. Separate agreed work from unresolved scope, valuation or responsibility. A clear issue helps an adviser determine the next process without reading an unexplained collection of emails.
- Find the project's definitions. Read the change, notice, claim and dispute provisions with the commercial lead. Check incorporated terms and the parties covered. Do not assume another project's terminology, a consultant's everyday wording or an online example controls this contract.
- Trace the earliest relevant dates. Assemble the event, awareness, notice, submission and response chronology. Have the adviser identify the operative dates and required actions. Do not start the review only at final refusal; the applicable process may depend on an earlier event or communication.
- Confirm who prepares and receives it. Identify the authorized company representative, required addressee, issue method and necessary supporting material. Preserve evidence of delivery. A technical reviewer, site superintendent and formal claims recipient may have different roles; check rather than treating them as interchangeable.
- Keep project records and strategy connected. Continue gathering dated facts, cost support and relevant programme information through the agreed process. Record which commercial steps remain open and who owns them. Obtain advice about any performance or dispute obligations instead of assuming a claim alone changes work instructions.
Common mistakes
- Assuming final refusal is the first date that matters.
- Calling a routine invoice a formal claim without reviewing the definition.
- Copying another contract's recipient or procedure.
Checklist
The questions for the commercial review
- Defined unresolved issue.
- Project-specific definitions and provisions.
- Complete event and notice chronology.
- Required company authority and recipient.
- Advice on content, delivery and deadlines.
- Named owner for records and next action.
Check your understanding
The reviewer refuses the change today. Can you assume the time to make a claim starts today?
