BIM coordination for the client: a minimum set

Updated: 2026 · Reading time: ~6 min

BIM modeling increases transparency and efficiency of delivering projects of any complexity and functional purpose.

1) Use of BIM technologies in the EU

In EU countries, BIM has long stopped being a “nice 3D picture” — it is information management across the entire asset life cycle: from concept and design to construction, operation and modernization. At EU level, digitization is supported, among others, through the public procurement approach: Directive 2014/24/EU enables contracting authorities/member states to require electronic tools (including BIM) in works procurement. Practical guidance for public clients is also available — the EU BIM Task Group Handbook, describing how to implement BIM in the public sector.

In practice, a “minimum set” approach is common in Europe: the client defines clear rules of the game:
• which models are required (architecture/structures/MEP/networks/infrastructure);
• in which formats and at which stages (IFC, BCF, PDF, schedules/specs);
• where the “single source of truth” lives (CDE — Common Data Environment);
• who is responsible for coordination and which checks are mandatory (clash control, attribute checks, revisions).

An important nuance for the client: in many EU countries, BIM is regulated not by a single “one‑button law”, but by a system of requirements, standards and public programs. For example, in the UK, government construction strategy fixed requirements for collaborative BIM on central government projects, and later evolved into systematic information management based on ISO processes.

2) Ukrainian framework for BIM modeling

In Ukraine, BIM is practical to consider in two dimensions: (a) the baseline construction/regulatory field (laws/DBN/procedures), and (b) standards and contractual requirements that the client explicitly sets in the ToR, contract and tender documentation.

The baseline framework for urban development is formed, in particular, by the Law of Ukraine “On Regulation of Urban Development Activities” No. 3038‑VI. But the key “BIM lever” for the client is information management standards:
• DSTU ISO 19650‑1:2020 (concepts and principles of information management using BIM);
• DSTU ISO 19650‑2:2020 (processes at the design/construction stage — information requirements, delivery, checks, container statuses, etc.).

Practical conclusion: even if BIM is not mandated “by one line in the law for everyone”, you can make BIM mandatory contractually. Two core documents are needed:
• EIR/AIR (client’s information requirements / asset information requirements);
• BEP (BIM Execution Plan from the delivery team).

It is also recommended to consider information security, especially for critical infrastructure. Internationally, this is addressed by requirements such as ISO 19650‑5 (security‑minded approach), which describes principles of working with sensitive information without disclosing it to “extra” participants.

3) The effect of increased construction transparency

For the client, transparency is not “more reports”, but less uncertainty. BIM coordination provides a controlled data structure: what exactly is being built, what it consists of, what changes exist, who approved them, and how this impacts schedule and cost.

A minimum set that really increases transparency:
• CDE: a common data environment with versions, statuses (WIP/Shared/Published/Archived), change logs and controlled access;
• IFC as a neutral model exchange format between different software (to avoid vendor lock‑in);
• BCF to record clashes/remarks as tasks linked to model elements (not “phone/screenshot/chat”);
• coordination report at each milestone: list of clashes, statuses, responsible parties, closure dates;
• naming rules for files/models/revisions and a classification structure (so QTO/specifications are built without manual “cutting”).

Result: predictability (plan vs. actual), less rework, fewer “grey zones” in as‑built documentation, and most importantly — change control both in finances and technical decisions.

4) BIM as the basis for Ukraine’s recovery

A BIM approach is critical for recovery because recovery is not one asset but a system of thousands of assets that must be manageable and interoperable. If each project lives “in its own format”, the state/community/donors receive an archive of PDFs without the ability to quickly analyse quantities, typical solutions, material needs and priorities.

BIM as a “basis” means:
• unified information requirements (what exactly must be in the model and documents);
• scalable libraries of solutions (typical details/elements/specifications);
• compatibility and longevity (IFC as a neutral standard so data does not “disappear” after changing contractor or software);
• support for operation (AIR: information does not end with commissioning — it is needed for repairs, inspections, upgrades).

For the client (public or private), this becomes a practical requirement: “The model must be not only for design but also for asset management” — especially for critical infrastructure where data access rules and sensitive information control matter (ISO 19650‑5 approach).

5) Affordable BIM software on the Ukrainian market

The Ukrainian market already has a full toolset for “minimum BIM”. The key for the client is to avoid tying requirements to a single brand and instead tie them to the result (formats, checks, CDE, reports).

Typical software structure by roles:
• Authoring (modeling): Autodesk Revit / Civil 3D, Graphisoft Archicad, Tekla Structures, Allplan, Bentley (OpenBuildings/OpenRoads), etc.;
• Coordination/verification: Navisworks Manage, Solibri Office, BIMcollab ZOOM, Revizto, etc.;
• CDE (common data environment): Autodesk Construction Cloud, Bentley ProjectWise, Trimble Connect, Dalux, Asite/Oracle Aconex (for large projects) — or a corporate solution with controlled access;
• 4D/5D (schedule/cost): model‑based solutions (platforms and plug‑ins) + integration with estimating and planning tools.

Additionally, the client should have “lightweight” control tools:
• IFC viewers/validators (to accept the model regardless of which software the contractor used);
• BCF service/task tracker (so clash handling is an official process).

Important: open standards are your insurance. IFC is the international BIM data exchange standard (ISO 16739), and BCF is an open standard for communicating tasks/clashes across different BIM systems.

6) Design companies and BIM in Ukraine

BIM maturity in Ukraine varies greatly: from “3D for visualization” to full ISO‑oriented information management. Therefore, for the client the key is not “can they use Revit/Archicad”, but whether they can run a controlled process.

Minimum criteria for selecting a design/engineering team for BIM:
• defined roles: BIM Manager (rules/standards/processes) and BIM Coordinator (checks, clashes, reports);
• readiness to work using ISO logic (DSTU ISO 19650‑1/‑2): information statuses, revisions, change control;
• ability to demonstrate a BEP example and a coordination report (real artefacts, not “we do it”);
• ability to deliver in neutral formats (IFC + required attributes) and support it via BCF tasks;
• experience with approvals and procedures (expert review/coordination) without loss of information quality.

Typical client mistakes that “kill” BIM at the start:
• requiring “BIM” without EIR/AIR and without defined control points;
• not appointing a responsible person on the client side (who accepts models/reports);
• allowing delivery of only “native” files of one software without IFC (lock‑in and data loss risk);
• not allocating time/budget for coordination (clash control and fixing are work, not an “option”).

PRO recommendation: start with a “minimum set”, but fix it contractually (EIR + BEP + CDE + IFC/BCF + verification procedure). This delivers real quality control, transparency and scalability for the next assets.