A design overlay that flags a difference is only half the story. The harder part is knowing whether that difference is real, catching it before the area is graded or poured, and having something to show for it when a client, engineer, or finance team asks for proof.
In this session, we run Propeller’s design conformance workflow start to finish: importing a design surface (DXF, LandXML, TTM, or IFC), aligning it to a survey-grade 3D mesh, running a cut/fill comparison, and reading the resulting heatmap and cross-sections. This isn’t a slide deck standing in for the product. It’s the actual workflow, on demand.
You’ll leave with a clear way to catch grade and volume differences early enough to correct them, and what it takes to export a variance report your team can use for progress claims, dispute avoidance, and phase closeout.
What you’ll learn
- How to bring in a design surface, DXF, LandXML, TTM, or IFC, and align it to your site’s survey-grade 3D mesh without vertical drift
- How to run a cut/fill comparison and read the heatmap and cross-sections it produces
- How to catch a grade or volume difference early enough to fix it before it’s buried or handed off
- What a defensible variance report looks like, and how teams use it for progress claims and phase closeout
- How design conformance fits with the rest of a Propeller site: AeroPoints accuracy, DirtMate tracking, mobile capture
