Construction software
Why use Woub alongside your existing BIM software?
The changed opening is in the model. But does the installer know their team needs to start elsewhere tomorrow? BIM helps organise design questions and model issues. Woub brings conversations and follow-up actions around site work together. That keeps both technical development and coordination between people in the right place.

By: Floris Meulensteen

Direct answer
Use Woub alongside BIM when phone conversations, site meetings and work agreements become scattered across people and channels. Keep model issues, technical assessments and revisions in the designated BIM workspace. Use Woub to organise discussions and follow-up around them, referring to the relevant issue. Wouby AI can automatically turn identified agreements from supported conversations into tasks. A Woub task does not change the model or close a BIM issue.
What does BIM software already do for communication and issues?
BIM software supports more than viewing a building in 3D. Depending on the package and configured modules, you can raise questions against the model, assign people responsible, collect responses and track resolution. A model issue records a question or problem with its associated technical context.
This matters when a pipe crosses a beam. The designer involved must be able to see where the problem lies, which models were used and what changed in the solution. A phone conversation without that context is insufficient. A screenshot in a chat can also become outdated when a new model version appears.
The complementary question is what the technical outcome means for work on site. Must the installer arrive later? Can the carpentry team start on another floor? Who informs the subcontractor who did not attend the design meeting?
BIM supports technical resolution. Woub helps organise daily coordination around that resolution. If your team already handles both well in the existing environment, you do not need an extra application for the same process.
How do Dalux, Autodesk ACC and Trimble Connect differ?
All three environments provide collaboration capabilities themselves. The relevant comparison is therefore: which process do you already use, who participates and where does handover to site operations stall?
Woub alongside Dalux: keeping model comments and construction agreements distinct
Dalux BIM Viewer supports viewing and commenting on models. Comments can have a person responsible and a resolution history. Dalux distinguishes BIM Viewer from Field Basic, which supports site tasks among other functions. It is therefore incorrect to portray Dalux solely as a model viewer without communication. See the Dalux BIM Viewer product guide.
Suppose a detail is changed in Dalux and the site manager must establish with the installer how work proceeds meanwhile. Keep the technical question and response in the Dalux process used for them. Use Woub for the complementary conversation about resource allocation and agreed feedback if that conversation would otherwise become scattered across separate calls and WhatsApp groups.
Include the issue reference in the message or task, with an accessible link where possible. The designated employee processes a technical outcome back into Dalux. If everyone has the necessary rights and coordination already works well there, keep it there.
Woub alongside Autodesk ACC: from resolved model clash to coordinated construction
Autodesk Construction Cloud, often still called ACC, has been part of Autodesk Forma since March 2026. Autodesk describes this transition in its official announcement. Use current product and module names when assessing your setup.
The solutions for Autodesk model management support clash detection, issue management and tracking design changes, among other functions. A clash is a detected conflict between model components, such as a duct passing through a structural beam.
A resolved clash does not automatically establish the agreements the businesses involved have made about their sequence of works. Through Woub, the site manager can discuss with the installer when the team can proceed and who receives the new work instruction. Refer to the Autodesk issue. The person technically responsible checks the solution and processes the status in the designated model environment.
This is a workflow alongside Autodesk, rather than a claim of an automatic Woub integration. Avoid an extra conversation where your existing issue and construction process already reaches those involved in time.
Woub alongside Trimble Connect: connecting the BCF topic with the people involved
Trimble Connect provides a shared data environment, model viewing and BCF topics for model-related questions. BCF stands for BIM Collaboration Format. The described topic workflow lets you use a person responsible, deadline, status, comments and references, among other things. This is shown in the platform documentation and guide to topics.
A question about a steel connection can therefore remain in a BCF topic. Woub becomes relevant if the answer also requires discussion with the installation team, construction project coordinator and another subcontractor about access or the sequence of works. Use the same topic reference in communication and identify who provides technical feedback.
Do not create a second topic register in Woub. A Woub task such as ‘inform installation team after approval’ has a different function from assessing and closing the model question in Trimble Connect.
Which phone conversations and construction meetings stay outside the model?
Conversations about deliveries, staffing, access and the sequence of works do not always concern a model object. They may still determine whether work proceeds. Organise such agreements within the construction project without creating a model issue for every practical question.
A phone conversation usually involves one immediate question: can the team proceed, who arrives when or who makes contact? With calling from Woub, the conversation starts within the project context and the call information can be found afterwards.
To construction meeting involves several subjects and participants. Include the location or issue reference for each subject and state who takes which step. Woub supports recording and processing meetings. The output still needs checking, particularly when a discussed possibility and final decision sound similar. Also read how to make AI meeting notes for construction meetings useful.
Illustrative example: a changed opening, three different actions
An installer discovers that a pipe does not fit through the planned opening. The situation below is a workflow example, rather than a measured customer result.
Record the technical question. The BIM coordinator records the problem against the right location and model version. The project uses issue B-214, for example. The structural engineer or designer assesses the change.
Coordinate site operations. Through Woub, the site manager discusses with the installer what the team can do while the solution is not yet approved. Communication uses the same reference B-214. They agree who informs the team and when feedback is needed.
Bring approval and instruction together. The authorised employee records the technical outcome in the agreed BIM process. The site manager then checks which approved information applies and ensures the team involved has received the correct instruction.
The model issue, coordination and informing the team are therefore three identifiable actions. A completed calling task does not mean the structural engineer has approved anything. Nor does a closed model issue automatically mean the people on site know the new working agreement.
How does Wouby turn conversations into actions, and how does Pro identify risks?
Wouby AI can capture and summarise supported conversations and automatically turn identified agreements into tasks. Speak specifically: who investigates the detail, who calls the installer and when is an answer needed? Afterwards, check that the task contains the correct action, person and deadline. This product functionality has been confirmed by Woub and aligns with the described Business functionality.
In the opening example, the follow-up action may be for the construction project coordinator to check approval of B-214 and then inform the site manager. Wouby does not thereby make a design decision. Assessment of structural consequences remains with the authorised expert.
Risk identification requires a further distinction. A model clash needs technical checking within the BIM process. A construction risk identified in a conversation could be a team expecting to start tomorrow while the necessary confirmation is still missing. An AI warning may prompt someone to ask about it; it is not an established clash or proven loss.
The version consulted on 22 October 2026 of the Woub pricing page lists the analyst for costs arising from errors and rework under Pro, with a waiting-list notice. Do not assume general availability. Before choosing, discuss which functions have actually been released for your environment. You can assess the basic workflow with project conversations and task follow-up without waiting for it.
Practical evidence: Karel Kamp keeps colleagues informed about conversations
In the Woub customer case about aannemer Karel Kamp Roland describes employees alternately calling him and his colleague Angelo. They therefore had to bring each other up to date afterwards. According to the case, Roland can read the summary in the project chat of what Angelo agreed with employees. The case also describes automatic task creation from conversations.
This supports the value of shared call information and follow-up. The case does not demonstrate use of Dalux, Autodesk or Trimble Connect or prove a BIM integration. For your BIM project, the question remains which complementary construction agreements currently stay with individual people.

Existing image from the Karel Kamp customer case; not an illustration of a BIM integration.
When should you choose Teams or Woub alongside BIM?
Teams may suit the situation if your meetings, participants and follow-up are already configured in Microsoft. Teams also offers AI support: Microsoft describes how Copilot in meetings can help process discussion points and follow-up actions, depending on licences and settings. Do not compare ‘Teams without AI’ with ‘Woub with AI’. See the Microsoft documentation on Copilot and transcription.
Woub is worth investigating when daily coordination between the office, site and external parties still relies on separate project groups, calls and personal lists. You then organise conversations and resulting actions around the project. For that communication, Woub can replace WhatsApp and any separate task app, and reduce project email. The specialist BIM environment stays in use.
Test that choice with one real handover, such as B-214. Can the installer find the relevant information? Does the agreement reach both the site manager and construction project coordinator? Is it clear who reports back? Must someone still track the same action in two lists?
If the existing BIM environment with Teams already handles this well, another channel adds little. If only the project manager uses Woub while the site team continues communicating elsewhere, the problem is not resolved either. Agree beforehand which channel you are replacing for daily project coordination and practise the workflow with colleagues and subcontractors involved.
Which tasks stay in the BIM system?
Keep technical model records and formal resolution in the designated BIM environment. This includes recording a clash, assessing the solution and tracking revisions and issue statuses. Where a project uses a separate environment for formal approval, that project agreement remains authoritative.
Woub can organise complementary actions: speaking to the right specialist, informing the site manager or coordinating with a subcontractor what happens while a decision is pending. Record each action where it is carried out and assessed. Do not copy the entire BIM issue merely to remind someone they still need to call.
Agree four things for handover: the identifiable issue or topic reference, the person processing the technical outcome, the person informing site operations and when that feedback is needed. Check with the recipient that a shared link also works with their permissions. Access to the relevant environment remains necessary for opening and assessing model information.
You can use them together without an automatic integration. This article does not claim verified synchronisation between Woub and model issues in Dalux, Autodesk or Trimble Connect. View the documented Woub integrations if you want to automate a data flow, and have the specific application confirmed before working with it.
Start with one project and one clear handover
Choose an ongoing project where construction agreements regularly arise outside the model. Keep the model workflow in place. Organise daily project communication in Woub and check that decisions reach the right people without creating a second set of model records.
View the subscriptions and conditions and try Woub free for 14 days.
Start small. Enjoy the peace of mind. Expand only then.
Frequently asked questions
Does Woub still add value if my contractor already uses Dalux or Autodesk?
That depends on daily coordination. If participants already handle both model questions and work agreements well in the existing workspace, an extra channel offers little value. Woub can add value when calls and actions between office, site and subcontractors become scattered. Model issues and technical approval remain in the agreed BIM process.
Can a Wouby task automatically close a BIM issue?
This article makes no such integration claim. A task can remind someone to review an issue or inform a team. The authorised employee processes the technical outcome and status in the designated BIM workspace. A completed task is not technical release.
Do all subcontractors need to use both Woub and the BIM workspace?
That depends on their work and project requirements. Anyone assessing model information needs the necessary access to it. Woub can help organise daily coordination but does not replace that access. Agree for each role where questions, technical answers and site instructions are shared.
Can you use Woub alongside BIM without a connection?
Yes. Use a recognisable project and issue reference and specify who processes confirmed outcomes and informs the site team. That organises a handover without assuming automatic synchronisation. Only investigate a connection when a specific data flow calls for it.
This site is protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.