Construction Stage & Handover

When construction begins, the architect's role shifts decisively. Through design and documentation you were the author; now you become an administrator, inspector and impartial certifier. In RIBA terms this is the Construction stage; in AIA terms it is Construction Administration; in Indian practice it is the construction-stage service. The building is now the contractor's to build - it is their means, methods, sequence and safety - while the architect's job is to see that what is built accords with the contract documents, to answer the questions the drawings could not anticipate, to instruct changes properly, and to certify honestly.

A crucial and often misunderstood point is the limit of the architect's site role. On most appointments the architect makes periodic inspections, not continuous supervision: you visit to observe quality and progress and to catch non-compliance, but you are not standing over every pour and every joint, and you do not take over the contractor's responsibility for their own work or for site safety. Where genuinely continuous supervision is needed, that is a separate, resourced service - a resident engineer or clerk of works - and must be appointed and paid for as such. Being clear about this distinction in the appointment protects you from liability for things you were never engaged to control.

Underpinning all of it, when the architect acts as the contract administrator, is a duty to hold the balance fairly between client and contractor on matters the contract asks you to decide - valuations, extensions of time, certificates. You are paid by the client but, in that certifying role, you must act impartially and professionally. This dual character - the client's designer and the contract's fair administrator - is one of the subtlest and most important things to understand about practice, and Module 8 treats it in depth.

The daily texture of the construction stage is inspection and instruction. Inspections are your eyes on quality and progress: periodic site visits, ideally to a rhythm, where you check that the work conforms to the drawings and specification, look hard at the things that will be hidden forever once covered - waterproofing, reinforcement, service routes before they are cast or clad - and record what you find. A site visit that produces no written record barely happened; a dated inspection note or site-visit report, with photographs and a list of items to correct, is both a management tool and your evidence.

Instructions are how change and clarification enter the works lawfully. When something must change - a detail resolved differently, a client-requested alteration, an unforeseen ground condition - it is issued as a written architect's instruction, not a casual word to the foreman, because a verbal instruction that later costs money and is denied is a dispute in waiting. Similarly, the contractor's questions arrive as requests for information, and your written responses become part of the record. Discipline here is everything: everything that changes the works, or that could later be argued about, goes in writing, dated, numbered and copied to the right people.

The architect also typically certifies payment. As the work proceeds, the contractor claims for what has been done; the architect (with the quantity surveyor where there is one) values the work actually completed against the contract and issues a payment certificate for that amount, so the contractor is paid fairly for genuine progress and the client does not overpay. Certifying honestly - neither starving a performing contractor nor over-certifying work not really done - is a core professional duty and a matter the contract, and the law, take seriously.

Beyond the individual visit and instruction sits the larger management task of keeping the project on quality, cost and programme through the long months of construction. Regular site meetings - with the contractor, the client's representative and the consultants - are where progress is reviewed against the programme, problems are surfaced early, and decisions are minuted. Minuted is the operative word: the site-meeting minutes become the running history of the job and settle a remarkable number of would-be disputes simply by recording what was agreed.

Change must be managed rather than merely suffered. Every variation - whether client-driven, design-driven or forced by site conditions - should be evaluated for its effect on cost and on time before it is instructed, priced against the contract rates or agreed separately, and recorded. Uncontrolled change is how projects quietly haemorrhage budget and slip their programme; controlled change keeps the client informed and consenting and keeps the contractor fairly paid. When delays occur, they must be assessed against the contract's mechanisms for extensions of time and any associated cost, a subject Module 8 develops.

Throughout, the architect must also watch the things that are easy to lose in the noise: that the specified materials are actually the ones being installed, that samples and mock-ups are approved before bulk work proceeds, that the difficult junctions are being built as detailed, and that quality is being held even as the programme presses. In India, where site labour is often skilled in traditional trades but works from drawings unevenly, the value of clear communication, good mock-ups and vigilant inspection of the hidden and the critical is especially high. The building you get is the building you inspected for.

As the works near their end, the project approaches practical completion - the point at which the building is complete enough to be used for its intended purpose, even if minor items remain. Reaching it well requires snagging: a careful, systematic inspection to identify the defects and incomplete items - the door that binds, the chipped tile, the missed coat of paint, the tap that drips - compiled into a snagging or defects list for the contractor to put right. Good snagging is unglamorous and forensic; a building handed over with a thin, careless snag list is a building whose faults become the occupant's problem.

Practical completion is a significant contractual moment, not just a milestone. It typically marks the point at which the client takes possession and responsibility for the building, when the defects-liability period begins, and when a portion of the retention money held back from the contractor may be released. Because so much hangs on it, certifying practical completion is a judgement to make carefully: certify too early, under pressure to occupy, and you may release the contractor and the retention while real work remains; certify honestly against a proper inspection and the moment protects everyone.

In India this contractual completion runs alongside the statutory completion and occupancy process - the building must be certified complete by the architect in the terms the local authority requires and, where applicable, an occupancy or completion certificate obtained before lawful occupation. These statutory steps have their own requirements and vary by authority, so explain the principle to the client and defer the specifics to the local authority and the current regulations. Contractual completion and statutory occupancy are related but distinct, and both matter.

Handover is more than passing over the keys; it is the deliberate transfer of everything the client needs to own and operate the building well. A proper handover package includes the as-built or record drawings - the drawings updated to show what was actually built, which invariably differs in places from the tender set - so that future maintenance, alteration and repair have an accurate basis. Without as-builts, the next person to open a wall is drilling blind.

It includes the operation and maintenance manuals: the assembled information on the installed systems and equipment - the pumps, the lifts, the electrical and HVAC plant, the waterproofing - with their specifications, warranties, guarantees, servicing requirements and the details of who installed them. A building is a machine that must be maintained, and the O&M manual is its owner's handbook; a handover without it leaves the client unable to service what they have bought. Commissioning records, test certificates and any statutory approvals and completion documents belong in the package too.

Handover is also a human moment. The client is taking possession of something they have waited years and paid heavily for, and a considered handover - walking them through the building, explaining how the systems work, setting expectations about the settling-in and the defects period - turns an anxious client into a satisfied one, and a satisfied client into the referrals and repeat work of Module 3. The practices that treat handover as an afterthought and vanish at the keys forfeit both a reputational asset and, often, their final fee; the ones that close out generously are remembered.

The project is not truly finished at handover. Two tails run on. The first is the defects-liability period (also called the rectification or maintenance period) - a defined span, commonly of the order of a year, during which the contractor remains responsible for putting right defects that appear in the completed building. During this period the architect typically inspects, particularly toward its end, schedules the defects that have emerged, and requires the contractor to make them good. Only when the defects are rectified is the final portion of the retention money released and a final certificate issued. This period is the client's protection against latent faults and the contractor's incentive to build well; managing it properly is part of a complete service.

The second tail is the final account - the settling of the true, final cost of the project. Through construction the sum has moved with variations, remeasurement, provisional sums resolved into actual work, and adjustments for delay or claims. The final account reconciles all of it into an agreed final figure, prepared by the quantity surveyor and certified by the architect, so that both parties know the job is financially closed. An unsettled final account is a project that never really ends and a common source of lingering dispute; a properly agreed one lets everyone move on.

Closing out well is a professional discipline that too many practices neglect, exhausted by the time the building stands. Yet the last ten percent - the honest snagging, the complete handover package, the defects period conscientiously run, the final account fairly settled - is what separates a service that merely produced a building from one that delivered a project. It is also, quietly, where reputations are made: the client remembers how the job ended at least as vividly as how it began.