Variations, Claims & Payments

A construction contract is a bet about the future made with incomplete information, and reality always negotiates. Change arrives from every direction. The client revises the brief - a bigger kitchen, a moved wall, a finish upgraded halfway through. The site springs surprises - rock where soft ground was expected, an old drain, a neighbour's foundation encroaching. The design develops - a detail that looked fine on paper cannot be built as drawn, or a coordination clash surfaces only when the ducts and beams meet in real space. The market intervenes - a specified tile is discontinued, a steel price jumps, a supplier fails. And sometimes the authorities require change - a condition imposed at sanction, a fire officer's demand.

Because change is certain, a mature contract does not pretend it away; it provides an orderly mechanism to absorb it. That mechanism is the subject of this lesson: the variation (the ordered change and its valuation), the payment rhythm that keeps money flowing as work proceeds, and the claim (the contractor's request for more time or more money when something outside their control affects them). Handled well, this machinery lets a project bend without breaking. Handled badly - changes ordered verbally, never priced, records never kept - it produces the single most common cause of construction disputes: a pile of unresolved change at the end of the job, argued over in a final account that satisfies no one. The professional's task is to keep change flowing through the proper channels, priced and recorded as it happens, so that nothing festers.

A variation is a change to the contract works - an addition, an omission, a substitution, a change in quality, quantity, sequence or timing - ordered under the contract's variation clause. The crucial word is 'ordered': a variation properly exists only when the administrator issues an instruction for it under the powers the contract grants. This is why the instruction discipline of the previous lesson matters so much here. A change the contractor makes on a verbal nod, or on their own initiative, is a swamp of later argument; a change captured in a numbered, written variation instruction is a clean transaction that can be valued and paid. The professional rule is simple and absolute: if it changes the contract works, it is instructed in writing before or as it happens, never reconstructed afterwards from memory.

Good variation practice also means seeing the change coming and managing its consequences. Before ordering a variation, the administrator - acting as the client's adviser - should estimate its likely cost and time effect and warn the client, so the client authorises the change knowing the price rather than discovering it in the next certificate. Some changes carry hidden knock-on effects far larger than the change itself: moving a wall may be cheap in itself but expensive in the services, finishes and programme it disturbs. And the administrator must know the limits of the variation power - a contract's variation clause allows change within the scope of the works, but an instruction that tries to order something wholly outside that scope may be ineffective or may entitle the contractor to renegotiate. Where the extent of the power is genuinely in doubt, that is a point to check against the contract, with legal advice if it is contentious.

Once a variation is ordered, it must be valued - and standard contracts set out a hierarchy of valuation precisely so the parties do not argue from scratch each time. The first resort is the contract rates: if the varied work is the same character and conditions as work already priced in the bill of quantities, it is valued at those agreed rates - the fairest basis, because both sides accepted them at tender. If the work is similar but not identical - the same item but in different quantity or conditions - the contract rates are used as a basis but adjusted (a 'pro-rata' or adapted rate) to reflect the difference. If the work is of a character not contemplated by the contract at all, a fair valuation (a new or 'star' rate) is built up from first principles - labour, plant, materials and a reasonable margin. And where work genuinely cannot be measured - small, incidental or emergency work - it may be valued as daywork, at recorded time and materials plus percentages, which is why daywork sheets must be signed as the work is done.

This hierarchy is a model of how professionals turn a potential fight into a procedure. In Indian item-rate practice the same logic appears as the handling of deviations and extra items against the tendered schedule, with rates derived from the contract or the department's schedule of rates and, for genuinely new items, negotiated or analysed. Two disciplines make valuation work: valuing at the right point in the hierarchy rather than reaching for a convenient number, and doing it promptly while the facts are fresh, not hoarding variations to the final account. The administrator, as impartial certifier, values honestly - not inflated to please the contractor, not shaved to please the client - and where a valuation raises a contested question of entitlement, distinguishes the sum it can fairly certify from the wider claim that may need legal input.

Construction would be impossible if contractors had to fund an entire building and wait until the end to be paid, so contracts pay in rhythm. At agreed intervals - usually monthly - the contractor is paid an interim (progress) payment for the value of work properly done and, often, materials delivered, less the amounts already paid and certain deductions. The administrator (with the cost consultant) values the work and certifies the sum, and the client must pay it within the contractual period. This keeps the contractor's cashflow alive and ties payment to genuine progress. Getting the valuation and the timing right is not a clerical matter: late or short payment can breach the contract, sour the relationship and, in some jurisdictions, trigger the contractor's right to suspend or claim interest.

Two mechanisms sit inside the payment rhythm. Retention is a percentage of each certified amount held back by the client as security - a cushion that gives the contractor an incentive to finish properly and to return and fix defects. A portion of retention is typically released at practical completion and the balance after the defects-liability period, once faults have been made good. The other is the handling of materials on site and advance payments, which must be secured so the client is not paying for goods that could vanish. Across the whole job the cumulative certified payments trace the familiar S-curve of construction spend - slow at first, steep through the main works, tapering at the end - and understanding that curve helps the administrator and client anticipate cashflow. The precise percentages, timings and release conditions vary by contract and are matters to read from the specific document, not to assume.

When something delays or disrupts the contractor through no fault of their own, the contract provides two distinct remedies that students constantly confuse. An extension of time (EOT) adjusts the completion date, protecting the contractor from liquidated damages for delay caused by a 'relevant event' the contract recognises - variations, exceptional weather, late information, and so on. Crucially, an EOT is about time, not money: granting more time stops the damages clock but does not, by itself, put a rupee in the contractor's pocket. The separate remedy for money is a loss-and-expense (or 'prolongation and disruption') claim - the contractor's request to recover the actual additional cost they incurred because of a delaying or disrupting event for which the client is responsible, such as extended site overheads, idle plant or lost productivity.

The two remedies travel together but are decided separately, and each turns on the contract's own list of qualifying events and, above all, on notice. Most contracts require the contractor to give notice of a delay or a claim within a defined period, and to keep and submit records; a genuine entitlement can be lost simply because the notice was late or the records absent. That is why the administrator's and contractor's record-keeping - programmes, progress records, correspondence, delay logs - is the true currency of claims. Assessing an EOT also requires delay analysis - relating the delaying event to its effect on the critical path - which is the subject of the next lesson. For the administrator, the guiding principles are to assess EOT and loss-and-expense on their own merits and evidence, to distinguish clearly between time and money, and, where a claim raises a serious or contested question of entitlement or quantum, to advise that legal and specialist advice be taken rather than deciding a large contested claim alone.

If there is one habit that separates projects that settle cleanly from projects that end in bitter dispute, it is the keeping of contemporaneous records. Almost every question in variations, payments and claims - what was ordered, when, why, what it cost, what delayed the work, who caused it - is ultimately answered by the records made at the time. A dated site diary, minutes of every site meeting, numbered instructions, signed daywork sheets, the marked-up programme showing planned against actual progress, photographs of concealed work, letters and emails confirming decisions: these are not bureaucracy, they are the evidence that turns a contestable memory into a provable fact. The old construction adage holds - a claim is only as good as its records - and it cuts both ways: good records protect the contractor's genuine entitlement and equally protect the client and the certifier against inflated or invented ones.

The discipline is to record as you go, not to reconstruct at the end. When a variation is ordered, price it and log it then; when a delay event happens, note it, notify it and record its effect then; when work is about to be covered up, photograph it then. The administrator sets the tone: insisting that instructions be written, that meetings be minuted, that claims be supported by records rather than assertions, and that the monthly certificate reflects a genuine assessment. In Indian practice the same logic lives in the measurement book, the deviation and extra-item statements, and the running account bill - the contemporaneous record of what was actually done and measured. Whatever the form, the principle is universal: the project that documents change as it happens rarely ends in a serious dispute, and the one that leaves it all for the final account almost always does.