Specifications and methods of measurement in Kenya

Drawings show geometry; specifications describe materials, workmanship, testing, and execution standards. Contractors price from both. A BOQ without a spec invites the contractor to assume the cheapest compliant interpretation — or their favourite supplier.

Architects typically lead architectural specifications; QSs align BOQ descriptions with method of measurement rules.

Kenyan practice references standard methods of measurement so quantities are comparable between projects and tenders. BOQ items must be describable, measurable, and linked to drawing references.

When items are vague (“supply and fix tiles”), expect tender spread. When items reference standards and finishes schedules, spreads tighten.

Specify corrosion protection, moisture-resistant substrates, ventilation rates, and external finishes for marine exposure. Interior specs should cross-reference room data sheets once interior design is appointed.

Copy-pasting specs from inland projects is a common source of early maintenance failure on the coast.

Treat spec upgrades as cost decisions: involve the QS for delta cost plans before issuing to tender. Post-tender spec upgrades are variations — priced late and expensive.

Issue spec and BOQ together at tender. Hold a pre-tender query period. Archive the issued set on REDM with revision numbers matching drawings.

Create a finishes schedule keyed to plan areas — kitchens, wet rooms, facades, common parts. Reference sample boards or mock-up panels in the spec so tenderers price what you will approve on site.

Methods of measurement training for quantity surveyors emphasises consistent item descriptions. Align architect spec clause numbers with BOQ items to reduce claims that “item 4.2 was not in the drawings.”

For coastal facades, specify fixing systems, DPC continuity, and maintenance access. Inland spec clauses copied verbatim are a common source of premature staining and efflorescence.

Cross-check BOQ items against spec clause numbers and drawing schedules before issue. Hold a contractor Q&A and publish answers to all bidders.

For each provisional sum, state who measures, when, and how price is agreed. Ambiguous provisional sums become disputes.

Archive the issued spec/BOQ set on REDM with the same revision tag as planning drawings.

Run a spec workshop with architect, QS, and MEP so services sections reference architectural zones and risers.

Reject contractor substitutions that downgrade durability on coast projects unless equivalency is documented.

During construction, treat spec breaches as defects, not courtesy — quality drift starts with unpunished first fixes.

Performance specifications (U-values, acoustic ratings) need testable standards — reference Kenya or accepted international standards explicitly.

Nominated suppliers can speed procurement but reduce tender competition — state substitution rules.

Protect proprietary systems with maintenance clauses so handover manuals are not empty marketing PDFs.

Photograph mock-ups and benchmark panels; attach to project file as approved quality evidence.

Split specifications by trade packages if phased tendering — but keep cross-references so MEP and architecture interfaces stay aligned.

During site visits, carry the issued spec PDF with clause numbers — inspectors reference clauses, not memories.

At final account, unresolved spec interpretations should be settled against issued documents, not verbal site practice.

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.

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.