Construction Contracts Explained

Strip away the legal language and a construction contract is a written bargain: one party promises to carry out defined building work, and another promises to pay for it, and both agree the rules that will govern them while the work goes on and after it is done. It does four things at once. It describes the work - through drawings, specifications and a schedule or bill of quantities that together say what 'complete' means. It fixes the commercial terms - the price or the way the price will be calculated, when payments fall due, and how much is held back. It sets the timeline - a start, a completion date, and what happens if that date slips. And it allocates risk - the great, invisible subject of every contract, deciding in advance who bears the cost when the ground turns out to be worse than expected, when a design changes, when the monsoon arrives early, or when a supplier fails.

The contract matters most precisely when things go wrong. On a smooth project the document sits in a drawer; on a troubled one it is read line by line. That is why a professional treats contract-making not as paperwork but as risk design - the moment when the parties, still friendly, decide how they will behave when they are not. This lesson explains the principles every architect and project lead must grasp. It does not, and cannot, give legal advice: the exact words of any clause, and their effect in your jurisdiction, are a matter for a qualified construction lawyer, and the honest professional knows exactly where their competence ends and a lawyer's begins.

Every building contract has two principal parties. The employer (also called the client, owner or, in Indian public works, the 'department') is the party who wants the building and pays for it. The contractor is the party who agrees to build it. The whole document hangs between these two promises: to build, and to pay. Around them stand others named or implied by the contract. The architect or engineer is very often written into the contract not as a party but as a named third person with defined powers - to issue instructions, to inspect, to value work, to certify payment and completion, and, crucially, to decide certain matters fairly between employer and contractor. That dual position - agent of the client, yet impartial certifier - is the whole subject of the next lesson.

Beneath the main contract sits a second tier the head contract barely mentions but depends on entirely: the subcontractors and suppliers the contractor engages to do the trades and provide the materials. Their contracts are separate, but a wise employer's contract will require that they be back-to-back with the main terms, so risk does not fall into a gap. On larger and public projects there may also be a project management consultant, a resident engineer, third-party inspectors and sureties standing behind guarantees. Understanding who is a party (and therefore who can sue and be sued under the contract) versus who is merely named in it is a distinction students routinely miss and lawyers never do. The architect, in most traditional forms, is emphatically not a party - a protection worth understanding before you accept the certifier's role.

Rather than draft a contract from scratch each time - expensive, error-prone and untested in court - most of the world reaches for a standard form: a pre-drafted, industry-negotiated set of conditions that has been refined over decades and interpreted by courts, so both sides broadly know what the words mean. Four families dominate international practice. The FIDIC suite, published by the International Federation of Consulting Engineers, is the global lingua franca of large infrastructure and cross-border projects, colour-coded by procurement type (the Red Book for employer-designed works, the Yellow Book for plant and design-build, the Silver Book for turnkey). The JCT family, the Joint Contracts Tribunal, is the workhorse of UK building projects, with forms tuned to different procurement routes. NEC, the New Engineering Contract, takes a deliberately different philosophy - plain English, active project management, and an emphasis on collaboration and early warning rather than adversarial claims. And in the United States, the AIA contract documents provide the standard owner-architect and owner-contractor agreements.

What unites them is that each is really a menu of balanced positions: a body has already thought hard about how to share every common risk, and offers you a defensible default plus options to adjust. The professional value of a standard form is not that it is perfect for your job, but that it is coherent, tested and mutually understood, so you spend your negotiation on the few risks that are genuinely particular to your project rather than reinventing the wheel. Choosing which form, and which options within it, is a decision to take with a lawyer and a cost consultant - but knowing this landscape exists is the mark of someone who can hold their own in the room.

India's construction contracting has its own strong tradition, and a student who only learns FIDIC and JCT will be lost on their first real project. The public sector - the Central Public Works Department (CPWD), the state Public Works Departments (PWDs), and a host of government bodies - works largely to its own long-established forms and general conditions of contract, most famously the CPWD's standard documents and its detailed schedules of rates. These are overwhelmingly item-rate (measured) contracts: the contractor is paid for the actual quantity of each item of work done, at rates tendered against a detailed bill of quantities, with the department's schedule of rates as a reference. The philosophy is public accountability - every metre of brickwork measured and paid for transparently - and it has shaped how the whole Indian industry thinks about pricing.

The private sector is more varied. Large developers and international clients increasingly use FIDIC or heavily bespoke lump-sum contracts drafted by law firms; but a vast amount of Indian building still runs on bespoke or informal agreements - a negotiated item-rate or lump-sum arrangement, sometimes a simple letter of intent, sometimes little more than an approved estimate and a handshake. This is where risk lives untamed, and where architects most often get drawn into disputes they are not equipped for. The professional lesson is not to romanticise the standard forms nor to disparage Indian practice, but to insist - gently, early, and in the client's own interest - that even a modest project deserves a written contract that names the parties, defines the work, fixes the price basis, sets a completion date and says what happens if things change. Getting that in place, and getting a lawyer to check it, is often the single most valuable thing an architect does for a client before construction starts.

The single most consequential choice in any construction contract is how the price is structured, because it decides who carries the risk of the work costing more than expected. Three families cover almost everything. In a lump-sum (or fixed-price) contract, the contractor agrees one price for the whole defined scope; if the work costs them more than they estimated, that is their problem, and if less, their gain. It gives the client price certainty and pushes cost risk onto the contractor - but only if the scope is genuinely well defined, because every gap becomes a variation and a claim. In an item-rate (measured) contract, the client pays for the actual measured quantity of each item at agreed unit rates; the client carries the quantity risk while the contractor carries the rate risk. This suits works where quantities cannot be precisely known in advance - earthworks, refurbishment, much of Indian public building - and it is transparent, but the final cost is not known until the last measurement.

In a cost-plus (or cost-reimbursable) contract, the client reimburses the contractor's actual costs plus an agreed fee or percentage for overhead and profit. It suits urgent starts, ill-defined scope or highly bespoke work where no sensible price could be fixed up front - but it flips the risk almost entirely onto the client and offers the contractor little incentive to be economical, which is why it is usually hedged with a guaranteed maximum price, target cost or open-book auditing. Real contracts often blend these: a lump sum for the defined shell with item-rate provisional sums for the uncertain bits, or a target-cost arrangement that shares overruns. Choosing well means matching the pricing model to how much the scope is really known - and being honest with the client that certainty of price and flexibility of scope pull in opposite directions.

Beneath the pricing model, a handful of clauses do most of the heavy lifting, and a professional learns to find and read them first. The time clauses fix the completion date, define what counts as an extension of time, and set liquidated damages - a pre-agreed sum the contractor pays for each week of culpable delay, which the parties fix in advance precisely to avoid arguing about actual loss later. The payment clauses set the rhythm of money: interim (progress) payments as work proceeds, the amount of retention held back as security against defects, and the timing of the final account. The quality clauses define the standard of workmanship and materials, the tests and inspections, and the defects-liability (or maintenance) period during which the contractor must return to fix faults that emerge.

Then come the risk clauses that decide who pays when the unexpected happens: variations (how changes are ordered and valued), unforeseen ground conditions, force majeure and excusable events, insurance and indemnity (who insures the works, third parties and professional liability), suspension and termination, and the dispute resolution ladder that governs how disagreements are settled - the subject of Lesson 8.4. Together these clauses are a carefully balanced machine for sharing risk, and changing one shifts the load onto another. That is why you never edit a standard form casually, and why the wording of any specific clause - its exact triggers, notices and time bars - is a matter for a construction lawyer, not for an architect improvising on site. The architect's job is to understand the principles well enough to administer the contract intelligently and to know when to pick up the phone to a lawyer.

When a contract lands on your desk - to administer, or to advise a client on - approach it the way a surgeon approaches a chart, not the way most people approach terms and conditions. First, identify the skeleton: which standard form (if any) is the base, what has been amended, and which documents are incorporated by reference - the drawings, specifications, bills, general and special conditions - and in what order of precedence they rank when they contradict each other, because they will. Second, find the five vital signs: the price basis, the completion date and damages, the payment and retention terms, the variation mechanism, and the dispute ladder. If you can state those five for any contract, you understand the deal.

Third, note the traps: onerous amendments to a standard form that quietly shift risk (a widened liquidated-damages exposure, a stripped-out extension-of-time entitlement, a pay-when-paid clause, a shortened defects notice period), and any obligation with a strict time bar, because in construction a right unexercised within its notice period is often a right lost. And fourth, know your limits: the architect reads the contract to administer it competently and to spot what needs advice, but the interpretation of a disputed clause, the drafting of an amendment, and any question of legal liability belong to a qualified lawyer. Advising a client to have a lawyer review their contract before signing is never a sign of weakness - it is the single most valuable professional instinct in this whole module, and the one that keeps both your client and your practice out of trouble.