ISO 19650 for Small Teams: The Minimum to Know

The standard everyone cites and nobody explains

“This will be managed per ISO 19650.” The sentence appears in tenders, in slide decks, and in conversations where nobody interrupts to ask the obvious: what does that mean for me? If you’re a BIM manager, there are whole courses. If you’re a site manager, a building engineer or you run a small contracting firm, you’ve been left out of the explanation — even though the standard will reach you anyway, via contract.

Here is ISO 19650 in human words: what it actually standardizes, when it lands on you, and the 20% that matters in the field. Educational, no snake oil — nobody here is selling compliance.

What ISO 19650 standardizes (and what it doesn’t)

First surprise: ISO 19650 is not about 3D modelling. It’s a family of standards about information management: how a project’s information is organised, named, shared and approved across its life. Concretely, it standardizes — among other things:

• Who is responsible for which information and when (the roles of the party asking and the party delivering).
• Information states: work in progress → shared → published. A “shared” drawing is not a “published” drawing — and that difference prevents work executed from working versions.
• Naming and containers: what files are called and where they live, so information can be found (the CDE is the infrastructure for this).
• Information requirements: what must be delivered, when, at what detail — agreed at the start, not improvised at the end.

What it does not do: mandate any specific software, force everything to be modelled in BIM, or make anyone “ISO 19650 certified” for using a tool. Distrust anyone implying otherwise.

When a small team runs into it

Three typical doors:

• Public tenders with BIM requirements. The tender cites the standard and asks for an information management plan. buildingSMART maintains serious educational resources on the series (buildingsmart.org) — the place to go deeper.
• Working under a large contractor. The big player is bound by its client; you inherit the proportional part: naming, states, deliveries through their platform.
• A mature client. Private developers increasingly copy the public-sector requirements, because the result — findable information — is worth money in operating the asset.

If none of the three applies today, the standard demands nothing of you. But the 20% below pays anyway.

The 20% that matters in the field

Strip away the document-management layer and the standard asks for three habits any team — two people or two hundred — can have today:

1. Traceable information. Every relevant piece of data with an author, a date and a place. An anonymous photo in a camera roll isn’t traceable; a pin with photo, transcribed voice, author and position on the plan is.
2. Agreed states. Knowing what’s “in progress”, what’s “resolved” and what’s “approved” — without asking in the chat. A Kanban board that reflects the real state of findings is exactly that habit, at field scale.
3. One source of truth. The current plan, the current model and the findings in one place the whole team opens — not scattered across camera rolls, inboxes and decisions dying in WhatsApp.

Notice what these are: the everyday version of the standard’s principles. That’s why we call them habits aligned with 19650 — they take you halfway to formal compliance without buying any platform.

How to be “19650-friendly” without an enterprise stack

The honest recipe for a small team: structured field capture (place + evidence + owner + status, from day one), simple but consistent naming for what you publish, and the contractual document always identifiable. With that, the day a tender demands the formal version, the jump is process — not culture. PinMy covers the capture-and-status part; the normative document management, when it arrives, belongs to whatever platform the contract requires. PinMy claims no ISO 19650 compliance — it claims habits that point in its direction, and that difference matters.

FAQ

What is ISO 19650 in one sentence? The international family of standards for information management on construction projects: responsibilities, states, naming and delivery requirements — “how information is organised”, not “how to model”.

Is a small team obliged to comply? Only if a contract requires it (public work with BIM requirements, or working under an obligated contractor). Otherwise it’s voluntary — but its basic principles are free good habits.

Can an app “comply with ISO 19650” for me? No. The standard describes organisational processes and responsibilities, not software features. Tools can support the habits (traceability, states, one source of truth); compliance belongs to the project, not the app.

What PinMy is NOT

PinMy is the field-capture layer: pins with voice, photo, video and text on plans, photos and 3D IFC models, with assignment and Kanban. It is not a CDE or a document-management platform, claims no ISO 19650 compliance or certification, and doesn’t replace the information-management processes a contract may require. The web PDF report is useful today and still maturing.

Next time it’s cited in a meeting

You can now be the person who asks the good question: “what information requirements does the tender specify, and in which states?” And send this guide to the colleague who nods silently every time “19650” comes up.

• Start free: pinmy.co
• Book a 15-minute walkthrough: tidycal.com/pinmy