BIM coordination: Revit or Tekla for the agency

In BIM, comparing Revit and Tekla as two interchangeable products sets up the wrong question. On many projects, teams are not looking for a single winner: they must define the boundary between design, coordination, detailing and fabrication. This boundary determines the responsibility of each model.

The central criterion is therefore not the number of functions. It is the ability to exchange the expected information, at the right level of detail, without suggesting that a coordination model is already a production model.

Contents

We cover roles, the level of information, exchanges, clash detection, responsibility, training and a test protocol between Revit and Tekla.

Start with the project roles

The software boundary must follow an explicit boundary of responsibility. List who designs, who coordinates, who sizes, who details and who prepares fabrication. For each party, state the model they produce and the one they consult.

Without this map, two teams can model the same object with different assumptions. The clash appears late, at the moment when one believes it has received validated geometry and the other thinks it only transmitted an intent.

The official documentation of Autodesk Revit and of Tekla Structures lets you check the functions and formats of each version. It does not replace a BIM protocol suited to the contract and the parties.

Distinguish design, detailing and fabrication

A visually precise object is not necessarily authorised for fabrication. The project must state what each element represents, with what tolerance and for what use.

Take three sample objects: a main structural element, a connection and a penetration. Ask each team to describe the information it needs and the information it guarantees. This comparison reveals the areas where an automatic transfer could create false confidence.

The comparison of AI software for architecture helps tie the tool to the workflow. The Revit or Archicad comparison answers a different decision and must not be applied to the structural detailing chain.

Test a representative exchange

Interoperability is measured on a round-trip modification, not on a successful open. Prepare a reduced model containing grids, levels, objects, properties and penetrations. Export it in the agreed format, then open it in the other environment.

Check the position, the units, the identifiers, the classifications and the indispensable properties. Then make a change in the responsible tool and repeat the exchange. The test must show how a correction is recognised, validated and integrated, without creating a silent duplicate.

Keep a loss report

A loss is not necessarily blocking if it is known and worked around. Classify it as acceptable, to be corrected or unacceptable. Attach a person and an action. The report must be reviewed at every version change, because connectors and formats evolve.

Organise clash detection

Detecting a clash is not enough: you must know who resolves it and in which model. Define a priority rule, a status and a verification date. A screenshot emailed around does not constitute a resolution process.

For the sample project, create a few known clashes: a moved penetration, an inconsistent level, a duplicated object and a missing property. Verify that the team finds each problem, assigns it and confirms its closure after the new exchange.

The protocol may use a third-party coordination tool; that does not change the need to identify the source. The federated model is for observing, while the correction must return to the model whose author is responsible.

Prevent double modelling

Double modelling becomes costly when it is neither acknowledged nor limited. Some information may be recreated for a specific use, but the protocol must state which version is authoritative and how discrepancies are checked.

Set up a simple matrix: object, author, reader, exchange format, frequency and comparison method. If two teams modify the same object, add an arbitration procedure. The Revit MCP resource recalls the same rule for automations: a write capability must have a scope, a log and an owner.

Train on checks rather than buttons

The key skill is to recognise what can be used, not only to run an export. A training path must cover reading the protocol, the checks before sending, the analysis of losses and the handling of a correction.

1. Read the requirement. The learner identifies the model's use and the expected properties.
2. Prepare the exchange. They check units, coordinates, version and object selection.
3. Check the reception. They compare a list of elements and document the discrepancies.
4. Handle a clash. They assign the correction to the right author and keep the evidence.
5. Replay the exchange. They verify that the problem is closed without creating a new duplicate.

The guide to AI training in the company offers a method to turn these tasks into observable levels of autonomy.

Delimited experience and recommended pilot

Educasium does not claim here a proprietary Revit-Tekla benchmark or the measured return of a client project. The recommendation is methodological: reproduce a small coordination chain before changing the organisation of an active project.

Choose a known subset, such as one level and a few structural elements. Write down the assumptions, prepare the test clashes and name the validators. Keep the source files, the exports, the loss report and the decision record.

Define the stop threshold

The pilot must stop if contractual information cannot be checked, if the correction does not return to the right source, or if handover depends on a single person. This threshold avoids pursuing a fragile workflow simply because hours have already been invested.

A reasonable conclusion may be to limit the exchange, change the level of information or keep the current process. The test is there to reduce uncertainty, not to justify a purchase decided in advance.

Limits and points to check

Functions, licences, connectors and compatibilities change across versions. Check the current documentation, the project requirements and the available skills. A specialised office may have an already-stabilised protocol that makes a migration unnecessary.

This guide replaces neither a contractual BIM protocol nor the opinion of the project's technical leads. When fabrication or safety depends on the information, add the appropriate professional checks and do not entrust validation to a mere software transfer.

Frequently asked questions

Can Revit and Tekla be used on the same project?

Yes, if the roles and exchanges are defined. The teams must know which model is authoritative for each object and each property. A round-trip test reveals the losses. The protocol must also assign clash resolution.

Must the whole model be converted?

Not necessarily. Exchange what is useful to the recipient and checkable at the relevant milestone. A smaller scope reduces noise and duplicates. The decision depends on the contractual uses and the expected level of detail.

How do you avoid a false impression of precision?

Attach each object to a use, an author and a tolerance. Clearly distinguish the coordination model from the fabrication model. Check the properties, not only the appearance. Have the assumptions validated by the responsible professional.

Which project should be chosen for the pilot?

Use a finished or non-urgent subset whose difficulties are known. Include grids, levels, objects, properties and a few prepared clashes. Keep all the results. Avoid turning an urgent project into a laboratory.

Train an autonomous coordination team

Training eligible for OPCO/FIF PL funding under conditions. Qualiopi-certified organisation. See the AI training for architects or contact Educasium to build a path centred on your BIM exchanges.