Standards· 3 min read· by TaskBider Team

ISO 19650 in practice: a working guide for MENA and African BIM teams

What ISO 19650 actually requires day to day — CDE, naming, EIR, BEP, TIDP/MIDP — explained for CAD/BIM teams in Egypt, the Gulf, the Maghreb and West Africa.

ISO 19650 in practice: a working guide for MENA and African BIM teams — cover image

ISO 19650 is the single highest-leverage credential-adjacent knowledge for CAD/BIM professionals in MENA and Africa, because it is the language large clients use to decide who is safe to hire. Most explanations of it are written for consultants selling implementation. This one is written for the person producing the models.

What the standard is really about

ISO 19650 is not a modeling standard. It says almost nothing about how to draw. It is an information management standard: who asks for what information, when it is handed over, how it is named, and where it lives.

Practical translation: it exists so that a model arriving from Cairo, Manila or Manchester can be dropped into a project without anyone guessing what the files mean.

The six terms you must use correctly

Term Plain meaning
CDE (Common Data Environment) The single agreed place files live, with states: Work in Progress, Shared, Published, Archived
EIR The client's written information requirements
BEP Your plan for meeting them (pre-appointment and post-appointment)
Information container Any named file — a model, drawing, schedule, report
TIDP / MIDP Task-level and master delivery schedules: which container, by whom, by when
LOIN Level of information need — how much detail is enough, no more

Using these terms accurately in a proposal or interview instantly separates you from the majority of applicants in this region.

The container naming convention, decoded

A typical ISO 19650 file name looks intimidating and is actually mechanical:

PRJ-ORG-ZZ-01-M3-A-0001-S3-P02
  • PRJ project code
  • ORG originator (your company)
  • ZZ volume / system
  • 01 level
  • M3 type (3D model)
  • A discipline (architectural)
  • 0001 number
  • S3 suitability / status code
  • P02 revision

Learn to read this before your first federated-model job. Getting the status code wrong — publishing something as Shared that should be WIP — is the most common junior mistake and the one clients notice.

Day-to-day workflow that satisfies an auditor

  1. Work only in the WIP area until your internal check is done.
  2. Run your own QA: model health, warnings, naming, purge, coordinates.
  3. Move to Shared with the correct suitability code and revision bump.
  4. Log the container in the TIDP so the MIDP stays truthful.
  5. Never overwrite. Revise.

That is 80 percent of compliance for a production role.

What changes when you are the freelancer, not the firm

  • You inherit the client's CDE — do not propose your own Drive folder. Ever.
  • Ask for the EIR and BEP before quoting. If neither exists, price the ambiguity in or write a lightweight BEP yourself and charge for it.
  • Confirm shared coordinates and units in writing on day one. Most delivery disputes trace back to this.
  • Agree the LOIN explicitly: LOD 300 architectural with LOD 350 at interfaces is a sentence that prevents weeks of rework.

Why this matters commercially in MENA and Africa

Gulf megaprojects, Egyptian new-city developments, Moroccan infrastructure programmes and Nigerian commercial builds are all standardising on 19650-style information management, usually via a UK or European consultant. The delivery capacity is regional; the standards are imported. Anyone in Cairo, Tunis, Casablanca, Algiers, Lagos or Nairobi who can speak the standard fluently sits at the front of the queue for the highest-paying remote work available locally.

Concretely, in TaskBider listings, roles that name ISO 19650 or an equivalent information-management requirement carry noticeably higher advertised ranges than otherwise identical modeling roles — see the role salary pages and the 2026 rate guide for the underlying benchmarks, and the live job board for openings that require it.

A 30-day self-study path

  • Week 1: Read ISO 19650-1 and -2 summaries; memorise the six terms above.
  • Week 2: Rebuild one of your own projects with compliant container naming and a WIP/Shared/Published structure.
  • Week 3: Write a two-page pre-appointment BEP for that project.
  • Week 4: Add "ISO 19650 information management" to your profile with the BEP as a downloadable sample.

That sample document does more for your rate than another software logo.

FAQ

Is ISO 19650 mandatory in the Gulf?
It is not a universal legal requirement, but it is contractually required on most large public and semi-public projects in the UAE, Saudi Arabia and Qatar, and increasingly referenced in Egyptian and Moroccan tenders. In practice, bidding for serious BIM work without it is difficult.
What is the difference between the EIR and the BEP?
The Exchange Information Requirements (EIR) are written by the appointing party and state what information they need, when and in what format. The BIM Execution Plan (BEP) is the delivery team's answer explaining how they will meet it. EIR asks, BEP answers.
Do freelancers need ISO 19650 knowledge?
Yes, at vocabulary and workflow level. You do not need certification, but you must be able to work inside a client's CDE, follow their naming convention and deliver information containers at the agreed level without creating rework.

Related articles