Variation Claim Entitlement Analysis

A variation claim is not entitled because it was instructed, priced, or paid as an extra on site. Entitlement is a contract question: does the executed variation machinery cover this event, were the conditions precedent met, and does the contemporaneous record support the facts the claimant asserts? The useful output of this close-out task is a draft entitlement note that cites the clause and the records that exist. It is not a determination, not a certificate, and not a quantum figure that commercial can paste into a final account.

The note should state, for each claimed item, three things: the clause relied on (with the executed wording, not a paraphrase from memory), the facts the claimant needs to prove, and the documents that do or do not prove them. Where the file is silent, the corresponding field stays empty. Inventing a missing notice, backdating an instruction, or filling a gap from what usually happens on this form of contract turns a review into advocacy. Commercial and counsel still own the decision to concede, reject, or reserve.

This work sits late in close-out, after drawings, instructions, and site diaries have largely stopped moving. It is the counterpart to contract redline deviation analysis on the executed text, and it often runs beside delay claim chronology assembly when time and money are claimed from the same event.

Open the executed contract first. Variation regimes change between tender and signature: valuation rules, notice periods, deemed-variation language, and the treatment of oral instructions are frequent redlines. Running the claim against the tender form, or against a standard unamended clause, is a common failure mode. If the executed Particular Conditions deleted oral confirmation of an instruction and replaced it with a written-instruction-only rule, a claim that cites the tender wording will look entitled on a checklist and fail on the documents.

Pull the variation clause, any defined terms it uses (Variation, Instruction, Change, Employer's Representative), the notice or conditions-precedent clause, and the valuation or adjustment-of-sum clause. Record the clause numbers and the exact sentences you will cite. If the executed set is incomplete, say so in the note; do not substitute the tender pack. Tender clause risk classification is useful context for why a clause was flagged at bid, but it is not the instrument you apply at close.

Where the parties executed a deed of variation or a side letter that changed the variation machinery mid-project, that later instrument governs the later events. Date the event, then pick the clause that was in force on that date.

Walk the claim item by item against the file, not against the narrative in the claim letter.

For instruction: is there a written instruction, a drawing revision issued as an instruction, or only a meeting-minute request to proceed? Cite the document identifier and date. Do not upgrade a request for information into an instruction unless the executed clause treats it that way.

For notice: if the clause requires notice of the event or of the intention to claim within a stated period, look for a notice that meets that form and timing. If none exists, write that the record does not contain a notice. Do not invent one from an email that mentions the extra work in passing unless counsel has already treated that email as notice. Inventing a notice is the second failure mode. It poisons the draft and is hard to unwind once it has circulated.

For causation and scope: match the claimed extra work to what the contract documents already required. A variation that restates the original specification is not a variation. Cite the original drawing or spec clause and the later instruction or revision that is said to change it.

For quantum inputs (hours, quantities, rates): extract what the records show, labelled as extracted figures, not as certified amounts. Timesheets, delivery notes, measure sheets, and daywork sheets from the site system are evidence of what was recorded, not proof of entitlement or of the correct valuation method.

Site and commercial records often live in project platforms such as Autodesk and Procore alongside email and the hard-copy instruction book. Treat those platforms as a class of record stores. Search them for the same identifiers (instruction number, drawing revision, RFI, diary date). Do not assume that a workflow status in the platform (approved, closed) is a contractual determination.

When the same event also supports a delay claim, keep the entitlement note on variation limbs and point the time narrative to the chronology work rather than duplicating dates in two inconsistent lists.

Structure the note so a QS or counsel can verify every sentence without hunting.

For each claim item use a short block: item description as claimed; clause cited (number and quoted words); instruction cite; notice cite; scope and causation cites; record extracts relevant to quantum; gaps. Quote the clause words you rely on. Identify records by type, date, and unique reference. If a field has no supporting document, leave it blank or write "not on file". Do not write "notice presumed" or "instruction likely given orally".

Illustrative path, not a case study. A subcontractor claims extra reinforcement around a redesigned lift pit, priced as a variation at the rates in the contract bills. The executed variation clause requires a written instruction from the contract administrator and notice of the likely effect within 14 days of the instruction. The drawing revision is on file with a transmittal dated 3 March and marked for construction. There is no separate instruction form. The claim letter asserts that the transmittal was the instruction and that a 20 March progress meeting mentioned the extra steel. The diary for 20 March records a discussion of pit waterproofing, not reinforcement. There is no notice letter in the correspondence register.

The draft should cite the executed written-instruction wording, cite the 3 March transmittal as a drawing issue (not recast it as an instruction unless the clause equates the two), record that no notice document is on file, and extract any delivery notes for the extra bar as quantum inputs only. It should not conclude entitled or not entitled. It should not turn the extracted tonnage into a certified addition. Treating the draft as certified quantum is the third failure mode: a working paper becomes an admission if it is issued without the QS's valuation method and counsel's conditions-precedent view.

Where the claim is a subcontractor's, the same discipline applies at the downstream account. Do not let a main-contract concession leak into subcontractor final payment verification until entitlement and valuation have actually been decided on that subcontract.

The draft lines up clause text and record cites. It cannot decide whether a transmittal is an instruction under this form, whether a late notice is waived, whether prevention or an estoppel argument is available, or which valuation rule applies (contract rates, analogous rates, fair valuation, or cost plus). Those are commercial and legal judgements.

The QS owns measure, rate selection, and the arithmetic of the proposed adjustment. Counsel owns conditions precedent, construction of the clause, and any reservation of rights. Issue the note as a draft for review, with the gaps listed at the top so nobody mistakes silence for proof. Empty stays empty. Do not invent entitlement. Do not certify quantum.