Can we talk about ISO 19650 in plain language? Most explanations miss the practical side.
I've been working in BIM coordination for a while and ISO 19650 comes up constantly — in tender documents, client briefs,
and job descriptions. But whenever I see it explained online it either reads like the standard itself (dense and clause-heavy) or
it's so simplified it loses the practical meaning.
Here's what I think matters most for working BIM teams:
● The EIR and BEP are not admin formalities — they're the information management contract for your project. If
they're not agreed before work starts, you'll spend the rest of the project arguing about naming conventions.
● The CDE has actual workflow states, not just folders. WIP, Shared, Published, Archived. Using them properly is
what prevents teams from clashing against out-of-date models.
● ISO 19650 doesn't specify which software to use. It specifies what outcomes are required. You can comply using
Autodesk Construction Cloud, BIM 360, Asite, or others — as long as the workflow states are respected.
● The standard applies to the whole team, not just the BIM manager. Architects, structural engineers, MEP consultants
all have delivery responsibilities defined in the MIDP.
● Level of Information Need (replacing what was called LOD in PAS 1192) needs to be defined per milestone — not
globally across the whole project.
I've seen projects where the BEP was a 40-page document nobody read after week two, and projects where a 12-page BEP
was genuinely followed and made coordination much smoother. The difference was whether the project lead treated it as a
reference document or a filing exercise.
Curious what others have experienced — do your projects actually follow the CDE workflow states, or is it more of a
checkbox requirement in the brief?