ISO 19650 for Small Firms: No BIM Manager Required

ISO 19650 has a reputation in small practices: enterprise machinery, written for firms with a BIM department and a compliance budget, nothing to do with a studio where the same person designs, manages, and issues. The standard's own text says otherwise. ISO 19650 for small firms is not a stretch of the standard; it is a stated design goal. The document applies to projects of all sizes, instructs that its principles be applied proportionately to scale and complexity, and adds that this matters particularly where small and medium-sized enterprises are involved. A delivery team, in its own terms, can be one person.

So the useful questions are the practical ones: what does the standard actually govern, where did the idea that it requires a dedicated hire come from, and what does proportionate application look like on a real project? This guide answers all three, and ends with the four moves worth making first.

What ISO 19650 Actually Governs (It Isn't Software)

ISO 19650 never tells you which software to buy. Its subject is information management: how the information a project produces (models, drawings, schedules, even meeting minutes) gets named, stored, shared, and trusted.

Even its definition of BIM contains no software. BIM, in the standard's terms, is the use of a shared digital representation of a built asset to facilitate design, construction, and operation decisions. The test of BIM is whether people can rely on the model to make decisions, not which platform renders it.

Why govern this at all? The standard is blunt about the cost of leaving information unmanaged: considerable resources are spent correcting unstructured information, resolving the uncoordinated efforts of delivery teams, and solving problems of information reuse. Any small firm can translate that sentence into local terms: the drawing set reconciled by hand before issue, the consultant model that has to be reinterpreted before it can be used, the hour spent finding the current version of anything.

One more thing worth knowing before going further: the standard's operative verb is "should," not "shall." ISO 19650 is a framework of recommendations to be adopted proportionately. It is a way of working, not a regulation with an inspector attached.

ISO 19650 Was Written with Small Firms in Mind

The enterprise-only assumption fails against three provisions that sit in the standard's own scope and principles:

• It applies to assets and projects of all sizes and complexity, from infrastructure networks to individual buildings, with the explicit instruction to apply the concepts proportionately, "particularly where small and medium-sized enterprises are involved."
• A delivery team can be any size, from one person carrying out all the necessary functions. The standard does not assume an org chart; it assumes information that needs managing, however many people touch it.
• Multiple functions may be performed by the same individual. In smaller businesses and projects, the standard expects information management to be carried alongside other roles: project management, design leadership, or both.

Proportionality is not a loophole added for small firms to squeeze through. It is the design. The standard also acknowledges that less experienced organisations can seek expert assistance for information requirements rather than build that expertise internally, which is a direct answer to the firm that wants the structure without becoming a standards body.

Functions, Not Job Titles: Why the Hire Is Optional

The standard draws a line most job postings blur: information management is a set of functions, and it explicitly warns against confusing functions with job titles or professional designations.

What the industry calls "the BIM manager" is, in ISO 19650 terms, mostly the project information management function: leadership in establishing the project's information standard, its production methods and procedures, and its common data environment. Read that list closely. It is a list of decisions, and most of them are decisions made once. A naming convention is established, then followed. A folder workflow is defined, then used. A parameter set is structured, then filled.

That is why the function scales down. At enterprise scale, with dozens of concurrent projects and rotating teams, those decisions need a full-time custodian. At small-firm scale, the load is front-loaded into setup: the same person leading the project can carry the function, provided the decisions are made before drawing starts, when making them is still cheap. The function is mandatory in the sense that someone has to hold it. The hire is not.

Where a Small Firm Starts: Four Proportionate Moves

Proportionate application still has to start somewhere. These four moves are the core of the standard at any scale, ordered by how quickly they pay back.

1. Name everything to one convention

ISO 19650 treats every file, model, drawing, and schedule as an information container: a named, persistent set of information that can be retrieved. Retrieved is the operative word. A container that cannot be found, or cannot be trusted to be what its name implies, fails at the only job a name has.

A single naming convention, decided once and applied to views, sheets, families, and files, is the smallest complete implementation of the concept, and the one with the longest payback: every search, every handoff, and every consultant exchange reads from it.

2. Run the CDE as a workflow, not a purchase

The standard defines the common data environment as an agreed source of information with two parts: a workflow that describes the process, and a solution that supports it. The workflow comes first, and it is the part that matters: information moves through four states, from work in progress (visible only to the team producing it), to shared (visible to the wider team, not editable), to published (authorized to be relied on), with an archive keeping the audit trail.

Nothing in that requires a platform subscription. A disciplined folder structure can carry the four states if the workflow is agreed and followed. The value is that everyone knows, from an information container's state, exactly what it may be used for. Adopt the workflow first; select technology to support it when the workflow outgrows the folders.

3. Define the minimum information needed at each milestone

The standard's framework for how much detail to produce is the level of information need, and its purpose surprises most first readers: it exists to prevent the delivery of too much information. The level should be the minimum needed to answer the requirement, and the standard states plainly that anything beyond that minimum is waste.

For a small firm this is permission to do less, deliberately. Not every element needs full data at every stage; decide per deliverable what question the information has to answer, produce that, and stop. Effort spent modelling detail that answers no requirement is effort taken from the deadline.

4. Write the information requirements down before the project starts

An information requirement, in the standard's definition, is a specification of what information is to be produced, when, how, and for whom. At enterprise scale this becomes a hierarchy of documents. At small-firm scale it is one page, written before the project starts: what the client needs at handover, what each consultant needs at each exchange, and what your own team needs to keep the model reliable.

The timing is the point. Requirements written before the project shape the setup; requirements discovered at handover become the scramble the standard exists to prevent.

What You Can Leave for Later

Proportionate cuts both ways: the standard also describes machinery a small firm does not need on day one.

• The full requirements hierarchy (OIR, AIR, PIR, EIR as separate documents) informs the one-page version in move 4. The formal document set waits until a client's appointment requires it.
• Federation strategies and container breakdown structures manage coordination between multiple task teams producing separate models. One firm, one model: the concern barely exists yet.
• Formal capability and capacity reviews matter when an appointing party evaluates prospective delivery teams. A team of three reviewing itself needs honesty, not paperwork.

Adopting ISO 19650 is not a compliance project with a completion date. Each piece earns its place when the work demands it. The four moves above are the pieces that pay for themselves on the first project; the rest can arrive with growth.

Structure Without the Hire

Strip the acronyms away and ISO 19650 asks a small firm for decisions, not headcount: agree how things are named, agree where information lives and what state it is in, agree what is needed and when. Made before the project starts, those decisions are cheap and they compound. Made during the project, they are made one error at a time, at the most expensive possible moment.

That is the honest version of "no BIM manager required." The function exists; it is carried in setup rather than in salary.

The Revit Project Template carries the setup half of that load: naming conventions, browser organisation, graphic controls, and a structured parameter set, configured to ISO 19650 principles and applied across 400+ live projects. The guide to what a structured template contains unpacks each layer; the launch list is open at datumaec.com.