IFC Model Version Control: Managing BIM Revisions on Site

In an ideal world, the design is finalized before construction begins. In reality, models change constantly — coordination issues surface, RFIs get answered, shop drawings reveal conflicts, and client change orders arrive at the worst possible time. Managing these revisions is one of the most underappreciated challenges in construction.

Why Models Keep Changing During Construction

There are many legitimate reasons why BIM models change after construction starts:

• Design coordination — clash detection reveals conflicts between structural, mechanical, and electrical systems that require redesign
• RFI responses — requests for information result in clarifications that change the model
• Shop drawing integration — fabrication details from subcontractors feed back into the coordination model
• Change orders — client-requested changes to scope, materials, or layout
• Field conditions — existing conditions that differ from what was surveyed require model adjustments
• Value engineering — cost-saving modifications during construction

On a typical mid-size project, the structural model alone might go through 10-20 revisions during construction. Across all disciplines, that's dozens of model updates that the field team needs to track.

The Cost of Working with Outdated Models

When field teams work from an old model version, the consequences are expensive:

• Rework — elements built according to an outdated design must be demolished and rebuilt. Rework typically costs 5-15% of total project cost.
• On-site clashes — ductwork that doesn't fit because the structural beam was moved in a later revision. Discovering clashes during installation is orders of magnitude more expensive than catching them in the model.
• Wrong materials — ordering based on outdated specifications wastes money and time. Restocking fees, lead time delays, and storage costs add up.
• Schedule delays — any of the above cascades into schedule impacts. On a project with liquidated damages, this hits the bottom line directly.

The root cause is almost always the same: someone was looking at the wrong version of the model.

Version Control Best Practices for IFC Files

Good version management doesn't require complex software — it requires discipline:

Use a Single Source of Truth

Every team member should access models from one central location. Emailing IFC files creates forks — within days, different people are looking at different versions with no way to reconcile them. A centralized platform eliminates this problem entirely.

Clear Naming and Communication

When a new version is uploaded, the team needs to know: what changed, why it changed, and who approved it. This isn't just good practice — on many projects, it's a contractual requirement for design change documentation.

Preserve Previous Versions

Never overwrite an old version. You need the ability to go back and see what the model looked like at any point in time — for dispute resolution, change order tracking, and understanding the evolution of the design.

Lock Versions After Milestones

Certain versions correspond to contractual milestones: issued for construction (IFC), issued for tender, as-built. These should be clearly marked and immutable.

Comparing Model Versions to Spot Changes

Knowing that a new version exists is one thing. Knowing what actually changed is another. A version comparison (or "model diff") compares two versions element by element using GlobalIds:

• Added elements — new GlobalIds that didn't exist in the previous version
• Deleted elements — GlobalIds that were in the previous version but are gone
• Modified elements — same GlobalId, but geometry or properties changed

This lets a site engineer quickly focus on what's different without manually comparing two models side by side. On a model with 50,000 elements, a revision might only affect 200 of them — but finding those 200 without a diff tool is like finding needles in a haystack.

How a Web-Based Platform Simplifies Versioning

A web-based approach to version management offers structural advantages over file-based workflows:

• Central upload point — one place to upload new versions, one place for the team to access them
• Automatic version history — every upload is preserved with metadata (date, uploader)
• Always current — when someone opens the model, they see the latest version by default
• Previous versions accessible — one click to switch to any previous version
• Version comparison built in — see added, deleted, and modified elements between any two versions
• Custom data carries over — attributes linked by GlobalId persist automatically across versions

Bimvue supports this workflow out of the box. Upload a new IFC file as a new version of an existing model, and the platform handles the rest: processing, element extraction, version indexing, and custom attribute migration. Your team always has access to the latest model — and the confidence that they're building from the right one.