The phrase "real-time" appears in the marketing of nearly every BIM tool on the market. But if nearly every tool offers this, why isn’t it commonplace yet?

Because the gap between "real-time" as a marketing term and real-time as an architectural capability is the gap between concurrent workflows and sequential ones. When you’re evaluating new tools here are some true real time capabilities to look out for.

Capability 1: Simultaneous multi-user editing

Not "check in, check out." Not "sync when you save." True simultaneous editing where multiple users author geometry in the same model at the same time.

Most BIM tools were designed as single-user authoring environments. When they added multi-user support, they added it through workarounds: worksharing, file-locking, central models with local copies, sync-to-central operations that periodically reconcile divergent work. These mechanisms exist because the underlying data model assumes one author at a time. Everything else is conflict resolution.

The consequence is familiar to anyone who has worked on a large Revit project. You wait for sync. You discover conflicts after the fact. You avoid editing elements near someone else's work because the merge might break something. The tool technically supports multiple users, but the experience is sequential. People take turns.

True simultaneous editing requires a fundamentally different data model. The model lives on the server. Every user's changes are applied to the same state in real time. There is no local copy to reconcile. There is no sync operation. Conflicts are resolved at the keystroke level, not the session level.

This is not a marginal improvement. It is the difference between a team that works together and a team that works in parallel and periodically compares notes.

Capability 2: Live data and design

Drag a line. See the impact

This is not post-processing. This is real-time feedback that changes how design decisions get made.

In most BIM workflows, cost, quantity, zoning etc data are extracted after the design session. The architect models. The model is exported. The numbers come back days or weeks later. If the design is over budget, the team iterates and repeats the cycle. Each loop takes time. Each loop costs money. Each loop represents a design decision made without the information that would have made it better.

Live metrics change the feedback loop from days to seconds. The architect does not need to guess whether a design move is within budget. They see it. The developer does not need to wait for a feasibility study to be re-run. The feasibility data is live, embedded in the model, updating as the geometry changes.

This capability requires the model to be more than geometry. It requires a structured data model where every element carries cost intelligence, area calculations, and program data natively. And it requires that data to be computed on the server in real time, not batched and exported.

Capability 3: Instant stakeholder review without exports

The owner wants to see the design. The contractor wants to evaluate constructability. The planning authority needs to review massing in context.

Today, fulfilling any of these requests means an export. Someone generates a PDF, a slide deck or books a meeting. The export represents a frozen moment in time. By the time the stakeholder reviews it, the model may have changed. Their feedback references a version that no longer exists.

The export also strips information. A 3D model becomes a 2D drawing. A parametric model becomes a static file. Cost data, program data, structural metadata are all lost or flattened in translation. The stakeholder reviews a simplified representation of the design, not the design itself.

In a cloud-native BIM environment, stakeholder review is a link. The owner opens a URL and sees the live model, current state, full fidelity. They can navigate, measure, and interrogate the design without installing software. The contractor can evaluate structural systems in 3D, with real geometry, not a set of flattened sections.

This eliminates an entire category of production work. The time spent creating presentation exports, formatting slide decks, and preparing review packages can be redirected to actual design work. For firms where partners or owners request frequent reviews, the cumulative time savings is substantial.

More importantly, it changes the quality of feedback. A stakeholder reviewing a live 3D model gives different, better, more specific feedback than a stakeholder reviewing a PDF. The review becomes a conversation about the actual design, not an interpretation of a representation of the design.

The question that matters when evaluating BIM tools

The question for firms evaluating cloud BIM tools is not "is it in the cloud?" Nearly every vendor can claim some version of cloud capability. The question is: what can it do in real time?

Can multiple users author simultaneously? Can cost data update as geometry changes? Can stakeholders review the live model without an export? Can AI agents access and operate within the design environment?

Arcol answers yes to all four. That is what Connected Constructible Design means in practice. Not a marketing phrase, but a description of specific, real-time capabilities that exist today: browser-native multiplayer editing, live metrics extraction, link-based stakeholder review, and an API-accessible environment built for agentic workflows.

Concurrent or sequential: the infrastructure choice

The answers to those four questions determine whether a firm's workflow is concurrent or sequential. Concurrent means multiple disciplines working simultaneously, with live data, continuous coordination, and AI agents augmenting capacity. Sequential means one person at a time, periodic sync, batch processing, and manual exports.

Most firms operate sequentially today. Not by choice. By constraint. The tools enforce it.

The shift to concurrent workflows will not happen through better project management or more disciplined meeting cadences. It will happen when firms adopt tools whose architecture makes concurrency the default, not the exception.

That infrastructure choice is available now. The question is whether firms will make it before the competitive gap between concurrent and sequential workflows becomes impossible to close.