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 workflow: a pre-model checklist GenAnywhere supports

Twelve checks that sit between a generated scene and the opening wall of a building model.

BIM modeling workflow usually starts with a scene that nobody checked, and the opening model inherits the mistake. A generated site base arrives with a source, a date and a set of estimates, and each of those needs a look before the authoring team begins. GenAnywhere supplies the editable base; the list below is what the team does with it.

Aerial view of a hillside town with a road winding below

1 Before drawing

1.1 What is the question?

Write the question in one sentence. A scene built to test massing is not the scene you need for a coordination round, and a checklist run without a question becomes a ritual. The sentence decides which checks matter and which can be skipped.

Keep the sentence with the file. When the question changes, the checklist changes with it, and the record shows why the scene was built the way it was. A question that needs two sentences is usually two questions.

The sentence also sets the scale of the area. A question about one building needs the block, while a question about access needs the street and the junction. Let the question draw the boundary.

1.2 Who is the audience?

The audience decides how much of the scene to show and how much to explain. A client needs the arrangement and a clear statement of limits, a design team needs the layers and the export, and a reviewer needs the source and the date.

Write the audience next to the question. Two lines at the top of the note save a paragraph of explanation later, and they keep the scene from being shown to the wrong room.

Audiences also differ in patience. A client will sit through a short explanation of limits, while a colleague wants the file. Prepare both and lead with the one the meeting needs.

2 Source checks

2.1 Are the date and coverage right?

Check the source date at the start. A scene built from older data may miss a new road, a demolition or a completed building, and it will look confident while being wrong. Compare the date with what the team already knows about the site.

Then check the coverage. The area should include the neighbours and the street, because the argument usually lives there. A scene that stops at the plot line answers a narrower question than the model is asking.

Coverage can also fade at the edge of a dataset. Look at the outer row of buildings before accepting the area, and extend it if a block arrives half drawn.

Physical model of a riverside district on a table

2.2 What is missing?

Name the gaps rather than hoping nobody notices. A missing building, a changed access or a cleared plot are normal gaps in a map source. Each one needs an edit or a line in the note before the modeller starts.

Put the list where the modeller will see it. A gap recorded in a message is lost by the next meeting, while a gap in the note is read when the file is opened.

Records conventions such as the FGDC metadata standards exist because sources need to outlive the people who made them. A short note in the same spirit is enough for a project scene.

3 Scene checks

3.1 Are the layers usable?

Look at the layers a reviewer will use. Buildings, ground, water and vegetation should be separable, and the names should mean something outside the person who made them. A scene with four numbered layers is hard to discuss.

Toggle each layer once. If a toggle produces a surprise, fix it before the session rather than during it. The check takes a minute and prevents the moment when the room waits for a laptop.

Aerial view of a large warehouse complex and loading yards

3.2 Are the edits recorded?

Every replaced building and every changed height should have a line. The line does not need to be elaborate; a date and a reason are enough. What matters is that a reader can tell the source from the team's changes.

Edits without a record become facts. A raised terrain edge that nobody remembers making will be defended in a meeting as if it came from the map, and the conversation will be poorer for it.

Keep the log beside the scene, not in a separate system. The reader who opens the file should meet the note before the geometry, and the note should say what changed and when.

4 Export checks

4.1 Are scale and origin correct?

Open the file in the receiving tool and measure one known feature. A road width or a building footprint is enough to confirm the scale. If the number is wrong, fix the import settings and write down what worked.

Check the origin at the same time. A scene placed far from the project base point can behave oddly as the camera moves, and the fault looks like a display problem rather than a placement one.

4.2 What survives the export?

Check the object list and the materials. Some layers arrive separate, some merge and some names change. What survives determines how much work the receiving team has to do, and that work belongs in the plan.

If the structure matters, rebuild the groups a reviewer will toggle. Rebuilding everything is a common overreaction, and it consumes the time that the two useful groups needed.

5 Review checks

5.1 Which views do you show?

Show the view that matches the question. Massing needs an oblique view, access needs a ground view and a plan, and a coordination meeting needs both. The order should follow the argument rather than the software.

Keep the proposal visually distinct from the context. A muted context and a clear proposal are easier to read than a scene where everything is the same colour, and the distinction prevents a predictable question.

5.2 What do you say?

Say what the scene is and what it is not, in one sentence, before the discussion starts. A context scene built from map data is not a measured record, and the room should hear that early. The sentence protects the model and the team.

Then let the scene do its work. A review that spends its time on caveats has wasted the model, and a review that spends its time on the arrangement has used it well.

6 Close the checklist

6.1 What do you keep?

Keep the scene, the note and the export that went with it. Three items, one folder, and the review can be reconstructed later. The note carries the question, the date, the source, the edits and the person who checked the file.

Run the checklist on a new scene in the GenAnywhere app when a new question needs a fresh scene, and run the same list.

6.2 When do you stop?

Stop when the checks that matter to the question have passed. A checklist that grows after every project becomes a document nobody reads, and the useful checks drown in the inherited ones. Cut the ones that have not changed an answer.

6.3 When do you repeat?

Repeat when the question changes, the site changes or the scene goes to a new tool. Those three events are where the assumptions move, and a short repeat run is cheaper than a late discovery.

Use the pre-model checklist with the GenAnywhere workflow before the opening model is started.

7 FAQ

FAQ-1 How long should the checklist take?

Most of it is quick: the source date, the coverage, the layers and one dimension. An opening run may take half an hour while the team learns what it is looking at. Later runs are shorter, and the previous note does most of the work. Keep the list to the checks that change a decision.

FAQ-2 Who should run it?

The person who built the scene runs it and the person who will use the scene confirms it. That pairing catches the assumptions the builder stopped noticing and the user will notice at the wrong moment. A third reviewer helps for client-facing scenes. Keep the group small enough to finish.

FAQ-3 Does it need a survey?

No, and a survey does not replace it. The checklist is about whether the scene is fit for the question, not whether the site has been measured. Where a measured fact is required, the checklist should flag it and point to the survey rather than pretending the scene covers it. The two steps are separate.

FAQ-4 Can it support a client handover?

Yes, with the note attached. The scene, the export and the note make a package a client can open and understand. The note says what the scene is for and what it does not cover, so the client does not read it as a measured record or a fixed design.

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.