A Reproducible Site-to-Corridor Workflow with site3d, Shapezo, Archshaper, PlaceMaker, and OpenRoads

The easiest way to lose trust in a 3D workflow is to let every model arrive without context. A review scene may contain imported mapping, AI-generated geometry, a conceptual building, and controlled civil design, but look like one seamless file. I use site3d, Shapezo, Archshaper, PlaceMaker, and OpenRoads as separate stages and attach a small contract to every handoff.

Step 1: define the artifact contract

Before I model, I write down the area of interest, coordinate reference, horizontal and vertical units, source date, expected level of detail, target format, and intended use. I also assign a status: source, imported, generated, conceptual, designed, or verified.
The status prevents a common failure. A quick location model may be appropriate for an options meeting, while a controlled corridor model is required for a technical decision. Both are useful, but they must not be mistaken for each other after the files move.

Step 2: establish place context with PlaceMaker

PlaceMaker is a place-context handoff in my workflow. I bring in streets, building context, terrain, and other mapped information, then confirm units, coordinate reference, area coverage, and source date. I test a small area first and compare a few known positions before I build a larger study around it.
If an import generalizes or omits information, I record that gap. The context is still useful for site questions, but the next stage should not have to infer what the source did not provide.

Step 3: generate a location branch in Shapezo

Shapezo starts from a map boundary. I draw around a region and its AI generates a model for the selected area. The branch record stores the selected polygon or extent, generation date, visible coverage, and assumptions about inferred geometry.
I use the output for early questions about adjacency, rough massing, public space, and access. It remains generated context. I do not pass its geometry into controlled design without verification against authoritative mapping, survey data, or explicit project constraints.

Step 4: review the assembled site in site3d

site3d is where I inspect the project as a connected setting. Terrain, roads, buildings, vegetation, water, and utilities can be seen together. I save stable views with a layer note, a camera name, and the source date so another review can reproduce the frame.
The practical use is to find relationships that become hidden in a narrow discipline model. I can see an access conflict, a low point, a missing path, or an exposed edge before I spend time adding detailed geometry.

Step 5: keep Archshaper studies bounded

Archshaper holds the building-scale concept branch. For each option, I record the site boundary, assumed grade, access approach, surrounding context, and form constraints. The output remains conceptual until it is checked against setbacks, code, structure, services, and project requirements.
The model can inform a corridor or site review without becoming a source of measured design coordinates. Keeping it on its own branch makes that boundary clear.

Step 6: establish the civil corridor in OpenRoads

OpenRoads is where I create or rebuild the route with controlled engineering inputs. I verify horizontal and vertical reference, stationing, surface source, corridor limits, profiles, templates, drainage relationships, and quantities. An early line from a site scene is a visual clue, not an authoritative alignment.
The important handoff is explicit: intent can travel forward, but controlled geometry must be established from constraints and verified data.

Checks I keep in every review

• Confirm coordinate reference, units, origin, and vertical reference.
• Preserve source dates, selected boundaries, and import settings.
• Mark imported, generated, conceptual, designed, and verified geometry separately.
• Keep stable camera views for comparison.
• Retain source files, prompts, rules, exports, and transformations.
• State what the next tool is allowed to prove. The pipeline works because each tool has a distinct claim. PlaceMaker provides place context. Shapezo produces a map-selected AI model. site3d keeps the site readable as a whole. Archshaper studies building form. OpenRoads carries the corridor as connected civil design. Reproducibility comes from the records between those stages.