The Architect as Contract Administrator

Everything in the earlier modules prepared the design; this lesson is about running it once it is being built. In most traditional building contracts the architect is named as the contract administrator (in some forms the 'architect' or the 'engineer') - the person the contract empowers to make the machinery work while construction proceeds. That role is a bundle of specific powers and duties: to issue instructions that adjust the work, to inspect and reject what does not comply, to value what has been done, to certify how much the contractor should be paid, to grant or refuse extensions of time, and to certify the great milestones of completion. Without someone performing these functions, a construction contract cannot actually run - payments could not be released, changes could not be ordered, and completion could not be recognised.

What makes the role distinctive, and difficult, is not the list of tasks but the standard the administrator must hold to. For some of these functions the architect acts as the client's agent, doing the client's bidding within the appointment. But for others - above all valuing work and certifying payment, and deciding entitlement to time - the architect must act as an independent certifier, exercising professional judgement fairly between the two parties, uninfluenced by which of them pays the fee. This is the peculiar genius and burden of the role: the same person, appointed and paid by the client, must at defined moments set that loyalty aside and hold the balance true. Understanding when you are wearing which hat is the first competence of contract administration, and the source of most of its ethical hazard.

The dual role is worth stating plainly because it is so easily misunderstood. As the client's agent, the architect advances the client's interests: advising on the brief, coordinating the design team, running the tender, recommending a contractor, and generally acting for the party who appointed them. In this capacity the architect owes the ordinary duties of an agent to a principal - loyalty, care, keeping the client informed. But the standard building contract also confers on the architect a set of decision-making functions that the courts, across common-law jurisdictions, have long held must be exercised independently and fairly as between employer and contractor. When the architect values the work for an interim certificate, decides whether the contractor is entitled to an extension of time, or certifies that the works are practically complete, the architect is not doing the client's bidding - the architect is exercising professional judgement honestly, even against the client's short-term wish.

The tension is real and constant. A client under cost pressure may lean on the architect to certify a little less than the contractor has earned, or to refuse an extension the contractor genuinely deserves; a contractor may push for a generous valuation. The certifier's integrity is precisely the refusal to bend either way. This is not merely good ethics; it is how the whole system holds together, because a contractor signs up to the contract trusting that the architect's certificates will be fair. If that trust fails - if the certifier is seen as the client's tool - the contract's dispute machinery grinds into action and everyone loses. The architect who understands and openly honours this dual role earns a professional authority that no title confers: the quiet respect of a contractor who knows the certificate will be straight.

The most visible administrative power is the instruction. A building contract gives the administrator authority to issue instructions to the contractor - to vary the work, to open up and test, to remove non-complying work, to expend provisional sums, to postpone. An instruction is a formal act with formal consequences: many of them will have cost and time implications, and how they are priced is the subject of the next lesson. The professional discipline is to issue instructions properly - in writing, numbered, clear, within the powers the contract actually grants - and never to let the informal reality of a site (a word in the ear, a mark on a drawing, a nod at a mistake) substitute for the contractual mechanism. The classic trap is the verbal instruction: the architect says 'yes, change it', the contractor does the work, and later there is no record of who ordered what, so the variation cannot be cleanly valued and a dispute is born.

The administrator must also understand the limits of the power. An instruction can only do what the contract authorises; an instruction that purports to change the contract itself, or to order work outside its scope, may be ineffective or may entitle the contractor to renegotiate. And an instruction has a cost: the wise administrator, acting also as the client's adviser, warns the client of the likely price and time effect before ordering a change, so the client is never surprised by the bill. Good instruction discipline - always in writing, always within the powers, always with the client warned of consequences - prevents more disputes than any other single habit in contract administration. Where the extent of a power is genuinely unclear, that is a question to check against the contract with legal advice, not to guess at on site.

The administrator inspects the works as they proceed, to form the professional opinion that underpins certification. But inspection is one of the most misunderstood duties in the whole role, and getting its scope right protects both the building and the architect. Inspecting is not supervising: in the traditional contract the contractor is responsible for the means, methods, sequence and safety of construction and for its quality, and the architect's periodic inspection is to check that the emerging work broadly conforms to the contract - not to stand over every trowel of mortar. An architect who behaves as if they guarantee every hidden detail assumes a burden they are neither paid nor insured to carry; one who inspects too little fails the client and may miss defects that certification then blesses. The professional stance is periodic, risk-focused inspection at the moments that matter - reinforcement before a pour, waterproofing before it is covered, the first of a repeated element - recorded honestly in site reports.

When inspection finds work that does not comply, the administrator has the power to reject it and to instruct its removal or correction, and the duty to do so rather than to look away for the sake of the programme. Toward the end of the job this becomes the discipline of snagging - listing the defects and incomplete items the contractor must put right before completion is certified. Throughout, the record matters as much as the observation: dated site reports, photographs, and clear instructions create the evidence that, if a dispute ever comes, shows the administrator acted competently. Inspection done well is quiet, methodical and well documented; done as heroics or as box-ticking, it exposes everyone. And where a defect raises a genuine question of structural safety or code compliance, that is the moment to bring in the relevant engineer, not to adjudicate it alone.

At the heart of the administrator's independent role is the certificate. Periodically - typically monthly - the contractor claims for the work done, and the administrator (often with the cost consultant's valuation) decides how much has genuinely been earned and issues an interim payment certificate for that amount. The client is then obliged to pay the certified sum within the contractual period. This is where the two hats pull hardest: the client may want the number lower, the contractor wants it higher, and the administrator must certify what is honestly due - no more to please the contractor, no less to please the client. A certificate deliberately under-valued to help the client's cashflow is not a favour; it is a breach of the certifier's duty and, in many jurisdictions, exposes the architect to liability and the client to interest and dispute.

Certification also governs the milestones. The administrator certifies practical (or substantial) completion - the point at which the works are complete enough for the client to take and use, even if minor snags remain - which starts the defects-liability period, releases part of the retention and ends the contractor's liability for liquidated damages. At the end of the defects period, once the contractor has made good the faults that emerged, the administrator issues the final certificate and the balance of retention is released. Each of these certificates has serious legal and financial consequences, which is exactly why they demand independent judgement and careful timing. The principles here are general; the precise effect of any certificate under a particular contract, and the deadlines attached to it, are matters to confirm against the contract terms and, where anything is contested, with a construction lawyer.

Running through every certifying function is a single principle: the duty to act fairly and impartially between the parties when exercising the contract's decision-making powers. This is not a vague aspiration; in common-law jurisdictions it is a well-established position that when the architect certifies, values or decides entitlement, they must do so honestly and using their own professional judgement, holding the balance even though one party pays their fee. It is the reason the whole edifice of architect-administered contracts works: the contractor accepts the architect's decisions as a fair substitute for going to law over every disagreement, precisely because the architect is expected to be straight.

Living up to this is a matter of daily discipline and quiet courage. It means resisting a client's pressure to shade a certificate or deny a fair extension; it means telling a contractor 'no' when their claim is not made out, and 'yes' when it is, regardless of which answer is convenient; it means keeping records so that a decision can be shown to be reasoned, not arbitrary. It also means being honest about the limits of the role. Where a decision turns on a contested legal question - the interpretation of an onerous clause, the validity of a termination, a serious claim for loss and expense - the fair and competent administrator does not bluff; they advise the client to take legal advice, and take advice themselves through their professional indemnity insurer, because a wrong certificate given under pressure can be very costly. The Council of Architecture's standards of professional conduct, like those of institutes worldwide, expect this integrity of the certifier; it is the ethical spine of the whole role, and the trait that, more than any design flair, marks a trusted professional.