ISO 19650 in East Africa — what actually applies

If you've worked on a UK-funded project in East Africa in the last five years, you've been asked for ISO 19650 compliance. If you've worked on a donor-funded project — World Bank, AfDB, EIB, USAID, DFI portfolio — the chances are even higher.

The standard is good. But it was written with UK practice in mind: the Building Regulations 2010 framework, the UK BIM Framework's interpretation, NHS Estates' adoption pattern, even the language ("appointing party" / "lead appointed party") was tuned to UK procurement law. Most of it transposes cleanly to East African work. Some of it doesn't. And a few of the "best practice" extensions that float around (UK BIM Framework Information Protocol, BS 8536, the PAS series remnants) will get you in awkward conversations with local authorities.

This is our running guide — what we tell our team and what we tell new clients. It's opinionated. We're happy to be argued out of any of it.

The core that always applies

These bits of ISO 19650 are universal. Adopt without modification:

• The information management lifecycle (Part 1). Concept → delivery → operation. The diagram in §5.1 of ISO 19650-1 is correct regardless of jurisdiction.
• The roles (Part 2 §5.1). Appointing party / lead appointed party / appointed party / task team. The vocabulary maps cleanly to your client / lead consultant / sub-consultant structure in any jurisdiction.
• The CDE state machine. WIP → Shared → Published → Archived. Universal — this isn't even a UK concept; it's an information-management invariant.
• The file-naming convention (Part 2 Annex A). Project–Originator–Volume–Level–Type–Role–Number is sensible everywhere. The codes aren't sacred — but the structure is.
• The suitability codes (S0–S7). Universal.
• The revision schema (P / C / A). Universal.
• The audit-trail requirement (§5.6). Universal — and in our experience, the bit that earns its keep faster than any other when disputes arise.

The UK-specific bits to adapt

These need translation for local practice:

UK BIM Framework Information Protocol

Annex A of the protocol assumes UK procurement: NEC contracts, JCT terms, references to UK CDM Regulations. The information requirements model is fine; the contract-clause integration won't survive a Ugandan or Kenyan procurement context. Use the IR structure, draft the contract clauses yourself with local counsel.

The "OIR / AIR / EIR" cascade

UK clients (especially NHS Estates) have well-developed OIRs and AIRs. Most East African clients don't. Telling a Ministry of Health that they need to issue an OIR before you can proceed will produce blank looks. Either draft the OIR/AIR yourself in consultation with the client team, or adopt a "presumed information needs" approach where you specify what you'll deliver and they sign it off.

BS 1192:2007 references

The earlier BS 1192 was the precursor to ISO 19650. Several UK guides still reference it. Where your project documents reference BS 1192 specifically, either swap the reference to ISO 19650-2 (which supersedes it) or, where the BS detail is more specific than ISO 19650, retain BS 1192 alongside.

The bits that don't apply — and don't try to make them

BS 8536-1 / -2 ("Briefing for design and construction")

UK-specific framework for the briefing process. Useful conceptual reading; not contractually applicable here. Don't pretend it is.

UK government Soft Landings

The handover-and-aftercare framework is UK-specific. The Soft Landings concept (better commissioning, better handover, post-occupancy evaluation) is universally good — but the formal framework references UK Government Construction Strategy 2025, BSRIA's specific guidance, and assumes a UK FM market structure. Borrow the ideas; don't try to formally adopt the framework.

NEC4 BIM-specific clauses

If your contract isn't NEC4 (and most East African public-sector contracts aren't), don't import the NEC4 BIM clauses verbatim. The intent is fine; the wording assumes NEC4 procedural language.

What East African delivery adds

Things ISO 19650 doesn't cover that you'll need:

Donor-funded reporting requirements

World Bank, AfDB, IFC, EIB — each has its own information reporting templates and frequencies. Your BIM Execution Plan should reference them explicitly. Most have an "environmental and social management framework" that requires geo-tagged photographic evidence of progress — fit naturally into the audit trail you've built for ISO 19650 anyway.

Local building authority approvals

Kampala City Authority, Nairobi County, Lagos State Physical Planning Permit Authority — each has its own drawing submission requirements. They typically want stamped PDFs, not IFC. Plan a workflow that produces both: your BIM-native deliverables for the design team, and authority-stamped PDFs from the same source.

Multi-currency cost reporting

Most large projects mix local-currency contracts with USD-denominated equipment imports. Your information requirements should call out which costs are reported in which currency, and what FX rate fix point applies. ISO 19650 is currency-agnostic; your BEP shouldn't be.

French-language deliverables (for francophone West Africa)

If you're working in francophone West Africa, you need bilingual document sets — French for the client, English for international consultants. ISO 19650 has French versions of the standard; the vocabulary table is in NF EN ISO 19650-1:2019.

Compliance evidence — what we recommend

When a donor auditor or sceptical client asks "show us your ISO 19650 compliance," these are the artefacts that pass without fuss:

1. Signed BEP with version history.
2. MIDP with status against each deliverable.
3. CDE state log — every file's transition history from WIP to Published.
4. Suitability-coded deliverable register — S2 / S4 / S6 visible per file.
5. Hash-chained audit log — proves no tampering. Run the chain-verify command live for the auditor; takes 5 seconds.
6. Transmittal log — every Published deliverable, who it went to, when.

If you can produce these six in a single export, you'll pass any ISO 19650 audit we've ever seen. Planscape does it as a one-click bundle — but the principle applies regardless of tool.

Things we wish the standard said more clearly

• Naming for federation files. ISO 19650-2 Annex A is great for individual file naming but unclear about how to name the federation that combines them. We use <Project>-<Originator>-ZZ-ZZ-FD-<Discipline>-<Number> where FD = federation. Borrowed pragmatically from a UK firm's house style.
• Phase-handover vs project-handover. Multi-phase projects (e.g. four hospital wings delivered over three years) need clearer handover guidance than the standard gives. Plan it in the BEP.
• Sub-consultant TIDP relationships. When you have three layers of sub-consultancy (lead → primary sub → sub-sub-sub), the TIDP roll-up gets ambiguous. We map every actor explicitly in the BEP.

Closing

ISO 19650 is the right baseline. It's worth the investment to learn it. But it isn't a tick-box and it isn't a UK-only thing — it's a structured way to manage information across the lifecycle, and most of it works fine for East African delivery.

The bits you adapt (OIR/AIR, contract clauses), the bits you replace (procurement-law references), and the bits you add (donor reporting, multi-currency, local authority workflows) all sit comfortably alongside the standard's core.

If you'd like to talk about ISO 19650 adoption on your project — happy to. Drop us a line at hello@planscape.co.