Workflow blueprint

3D landscaping software should label a visual as a proposal, not a site fact

A page-specific review aid, not a universal product or compliance claim.

Keep site observation, model version, customer change, material assumption and estimate source separate through the design handoff.

TL;DR — Keep site observation, model version, customer change, material assumption and estimate source separate through the design handoff.
1

Frame the site

Record address, observation date, measurement source and access limitation.

2

Version the concept

Relate model edition, materials, plants, hardscape and customer comment.

3

Prepare the handoff

Keep variation, quantity assumption, crew note and supplier question distinct.

4

Review the estimate

Assign survey, drainage, horticulture, permits, safety and contract questions.

Page-specific decision aid

Landscape concept revision card

A site note, measurement source, 3D model edition, plant or material assumption, customer revision, crew note and estimate card.

  • Models retain their measurement source
  • A render is not a survey
  • Estimate changes keep customer context
Scope first

What Codeblix would confirm before implementation

This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.

  • Site and measurement identity
  • Model and design revision
  • Material or plant assumptions
  • Customer, crew and estimate owner

Use the related planning tools

Run the operational calculation, save the result in the URL and share it with your team.

Map this workflow to your operation

Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.

Discuss your workflow