GenAnywhere Generate Now

Select a map area. Generate a 3D city model with AI.

No drone survey required. Turn map data into editable 3D buildings, terrain, water and vegetation for BIM, GIS and 3D workflows.

Generate now

BIM modeling handoffs: what to check before Revit, GenAnywhere

The scene leaves as a general file, and the receiving team is the one that decides what it becomes.

BIM modeling handoffs fail on small things: a scale that was assumed, a layer that merged, an origin nobody wrote down. GenAnywhere exports a scene as a general GLB, and the file carries geometry and materials rather than native elements. This article sets out the checks that turn that export into a reliable reference before it reaches Revit.

Aerial view of a city block with a new excavation on site

1 What a handoff carries

1.1 Which file travels?

A general GLB travels, exported after a preview in the browser. It holds buildings, terrain, water and planting as geometry, with materials attached. It is not a project file for any single application, which is what makes it portable.

The format is maintained through the Khronos Group and is widely read. Widely read does not mean identical everywhere. The differences show up at import, so the check belongs at the receiving end rather than the sending one.

Industry exchange frameworks, such as those published by buildingSMART, describe how project information moves between parties. A GLB handover is a simpler exchange, and the same discipline applies: agree what is being sent before it is sent.

1.2 What does the receiver expect?

The receiver expects context: a site, a street and a set of neighbours around the building being authored. That expectation is reasonable and easy to satisfy. The trouble starts when the receiver expects elements, properties or a history that a GLB does not carry.

Say what the file is before it is sent. One sentence in the covering note prevents most of the disappointment, and it gives the receiver a reason to treat the scene as a reference rather than a model.

Ask what the receiver will do with it. A linked reference, a traced outline and a rendered background are three different jobs, and each one has a different tolerance for merged geometry.

2 Before the export

2.1 How do you set the area and layers?

Draw the area with the neighbours included, then review each layer alone. A missing block, a building at the wrong height or a water edge in the wrong place is easier to fix in the browser than in Revit. The fix takes minutes and saves an argument.

Decide which layers the receiver needs. A coordination team may want buildings, ground and planting, while a massing study may want buildings and ground alone. Export what the use requires, and the file stays lighter.

Plan the grouping before the export. If the receiver will link the scene as one object, the internal grouping matters less; if they will toggle parts, the grouping matters a great deal.

Close view of a brick building beside a gravel road

2.2 What do you check in the preview?

Check the scene from the angle the receiver will use. A model that reads from above can look thin at eye level, and coordination views are often closer to the ground. Orbit the site before exporting.

Check one known dimension in the browser. A road width or a footprint is enough to confirm that the scene has not been resized somewhere along the way. If the number looks wrong before export, it will look wrong after import.

Check the vertical as well as the horizontal. A ground surface that sits slightly above a road will hide the kerb, and the error is much harder to see once the model is in a section view.

3 On import

3.1 How do you confirm scale and origin?

Measure a known feature in the receiving tool. If the size is wrong, correct it through the import settings rather than scaling the model by eye, because a manual correction is hard to repeat and harder to explain.

Check the origin next. A scene placed far from the project base point can behave oddly, and the fault reads as a display problem. Agree a base point before the import and record it in the note.

Test the import on a second machine where you can. Import settings differ between workstations, and a scene that behaves on the machine that made it can arrive elsewhere at a different size.

Three colleagues reviewing drawings and a site model

3.2 What happens to the object structure?

Open the object list. Some layers arrive separate, some merge and some names change. What survives determines how much regrouping the receiving team has to do, and that work belongs in the plan rather than in a surprise.

Rebuild the groups the team will actually use. A context group and a ground group cover most coordination needs, and a deeper structure is often a preference that nobody maintains.

Give the groups names that mean something in the receiving tool. A name carried over from the browser can be opaque in a project environment, and the rename is cheaper than the explanation.

4 What Revit gets

4.1 Is it geometry or elements?

It is geometry with materials. There are no walls, floors or categories in the file, and nothing arrives with parameters attached. That is a property of the exchange, not a fault, and it should be stated before the opening import.

Treat the scene as a linked reference. It shows where the building sits and what surrounds it. The authored content stays in the authoring tool, where it can carry properties and a history.

4.2 What does a reference do?

A reference answers position questions. It shows whether the building sits inside the boundary, whether the neighbouring block is closer than assumed and whether the entrance faces the street. Those questions are common and the reference answers them quickly.

A reference does not answer documentation questions. It cannot schedule elements or coordinate services. Saying this early keeps the scene in its proper role and prevents a request it cannot meet.

It also cannot confirm that a design is correct. The reference shows position, and the design judgement stays with the team that authored it. A scene is evidence about context, not about compliance.

5 The note

5.1 What do you write?

Write the source, the date, the area, the layers, the base point and the checker. Add one line about what the scene is and is not. Six lines cover it, and the note is what the receiving team reads before opening the file.

Record the import settings that worked. A scale factor, an axis convention or a shared coordinate is worth more than a paragraph of explanation, and it makes the next import repeatable.

Keep the note where the receiver will look. A note in the sender's folder is invisible to the person who opens the file in the authoring tool, and that person is the one who needs it.

5.2 Who signs it?

Name the person who checked the import, not the team. A name answers a question and takes responsibility for the check. When that person changes, the note changes with them.

Preview an export in the GenAnywhere app and check the scene before the opening handoff of a project.

6 After the handoff

6.1 What do you fix at the start?

Fix the scale and the origin, then the grouping. Those two determine whether the reference is usable at all, while the grouping is a convenience. A team that starts with naming spends its time on the least important problem.

6.2 When do you re-export?

Re-export when the design changes massing or the context changes. A small edit inside the building rarely needs a new scene, while a new block or a changed street usually does. Tie the re-export to the reference, not to a calendar.

Follow the export path in the GenAnywhere workflow when a second handoff is due.

6.3 When does the scene retire?

The scene retires when the design is documented and the context no longer informs a decision. Archive it with the note. A retired reference is still useful when someone asks why a building sits where it does.

7 FAQ

FAQ-1 Is this a Revit importer?

No. It is a general GLB exported from a browser scene, and Revit is one of the tools that can read it as a reference. There is no plugin and no live link. A new export is how a change in the scene reaches the model. Plan for a fresh file rather than an update.

FAQ-2 Do native elements come across?

No. The file carries geometry and materials, not walls, floors or categories. Properties and authored relationships stay in the authoring tool. Teams that need native elements build them in that tool and use the scene for context. The two roles stay separate by design, and the note should say which one applies.

FAQ-3 What happens to materials?

Materials arrive with the geometry, and their appearance depends on the receiving tool. Some teams keep them and some replace them with project standards. Treat the exported set as a starting point and plan a short pass after import. Texture paths are the usual source of a missing surface, so check the opening import closely.

FAQ-4 How do we keep the files aligned?

Agree a base point, record it and check it on import. A shared coordinate, a corner or a road centreline works as long as both files use the same one. Write the agreement down, because an alignment that lives in memory lasts until the next staff change. Draw it as well as write it.

Content and technical notes

This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.

Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.

For technical questions or corrections, contact support@genanywhere.com.

Last reviewed: 2026-11-06.