Contract administration in Kenya: what developers should enforce

A building contract is an agreement enforceable by law — promises exchanged for consideration. On site, what matters is whether instructions, variations, delays, and payments are administered under the contract form with auditable records.

Developers who manage by informal chat inherit the contractor’s version of events when disputes arise.

Variations should be instructed in writing, priced or agreed provisional, and reflected in certificates. Extensions of time need causation linked to contract clauses — not generous gestures without precedent.

Architects (as CA) and QSs have distinct duties: the architect certifies compliance and issues instructions within scope; the QS measures value and recommends payment subject to contract terms.

Interim certificates follow defined cycles with retention and release rules. Developers should verify work on site against certified amounts, not pay ahead of measurable progress except where contractually allowed (mobilisation, materials on site with vesting certs).

Lien and performance bond provisions should be understood before first payment.

Site instructions register, meeting minutes with actions, drawing revision log, RFIs, inspection reports, photographs, and delivery notes. Store them against the REDM project ID — not only on individual phones.

When claims appear, the party with chronology wins more often than the party with rhetoric.

Hold regular cost and programme meetings aligned to the QS report. Challenge unsigned variations before work proceeds. Close out defects and retention with documented lists — especially on coastal handovers where humidity exposes unfinished snagging.

Define defect liability period and retention release in the contract, then track defects with photos and dates. On humid coastlines, condensation and waterproofing defects emerge early — schedule inspections before retention release, not years later.

Final account needs agreed measurements, settled variations, and released retention. QSs prepare statements; developers verify against site and bond status. Disputes often trace to unsigned dayworks — prohibit unpriced daywork except emergencies with next-day pricing rules.

Link handover documentation to the asset stage: O&M manuals, as-built drawings, test certificates, and warranty contacts stored on the REDM project file help operators after sales.

Insist on a single instruction channel and variation register from week one on site. Photograph progress aligned to certificate periods.

Review QS recommendations against your own site walks — certificates are recommendations, not automatic payments.

Plan retention release with a defects list and moisture-focused snagging on coast projects; link closed items to REDM handover artefacts.

Agree meeting cadence with architect CA and QS — weekly during structure, fortnightly during finishes. No decisions without minuted actions.

Train your site team not to direct trades outside the contract chain. Friendly site help creates unpriced work.

When disputes arise, assemble chronology from instructions, drawings, and certificates before lawyers — many disputes narrow once records are sorted.

Liquidated damages and extension-of-time clauses need calendar baselines agreed at contract signing. Without baselines, delay claims become opinion battles.

Insurance certificates (CAR, PI, public liability) should be collected before mobilisation payment. Missing insurance is a solvency red flag.

Employer-supplied materials or free-issue items need vesting and storage clauses. Theft and damage disputes are common on congested coastal sites.

Practical completion is not final completion — agree snagging periods and who funds remedial access.

Set a variation cost threshold above which board approval is required — prevents site teams committing spend informally.

Use measured work photos for hidden works (foundations, ducts) before cover-up — disputes after tiling are expensive.

On Kenyan coastal projects, document every decision that affects cost, approvals, or programme in the REDM project file so consultants, lenders, and your own board see the same timeline. Informal agreements scattered across email are where disputes start.

Before the next fee milestone, confirm who signs, who certifies, and who records — then hold one coordination meeting with minutes. Developers who skip that step usually pay twice: once for rework and once for dispute advice.

Pair this guide with the design-stage and statutory approvals articles so by-law, environmental, and tender assumptions stay consistent from predesign through handover.

On Kenyan coastal projects, document every decision that affects cost, approvals, or programme in the REDM project file so consultants, lenders, and your own board see the same timeline. Informal agreements scattered across email are where disputes start.

Before the next fee milestone, confirm who signs, who certifies, and who records — then hold one coordination meeting with minutes. Developers who skip that step usually pay twice: once for rework and once for dispute advice.