7 Criteria for Choosing a Point Cloud CAD That Excels at Earthwork Volume Calculations | Points to Check Before Comparing

Table of Contents

• Reasons why a point-cloud CAD with strong earthwork volume calculation capabilities is required

• Checkpoint 1: Can it stably handle large point-cloud datasets?

• Checkpoint 2: Is it easy to create the existing surface?

• Checkpoint 3: Is it easy to align comparison conditions with the design surface?

• Checkpoint 4: Is it easy to partition the area and assess partial earthwork volumes?

• Checkpoint 5: Is it easy to perform cross-section checks and 3D inspections?

• Checkpoint 6: Is it easy to manage coordinates and integrate site data?

• Checkpoint 7: Can it provide robust data management for recalculation and explanatory needs?

• Practical conditions to clarify before comparing point-cloud CADs

• Common pitfalls when selecting point-cloud CAD

• Summary

Why Point-Cloud CADs That Excel at Earthwork Volume Calculations Are Needed

In practical earthwork volume calculations, it is not sufficient to merely produce quantities. You must be able to explain afterward what area was targeted, which terrain surface was adopted as the existing surface, which design conditions it was compared against, and where you regarded the work as cut and where as fill. Producing numbers and having numbers that can be used in practice are different things. Even if quantities are calculated in detail, if the assumptions are ambiguous and not reproducible, rework will occur each time for internal approval, explanations to the client, or recalculations during construction.

Using point clouds makes it easier to capture site topography in detail. Because you can view current conditions based on denser information than before, it is certainly easier to improve the accuracy of earthwork quantity calculations. However, simply having point clouds does not automatically make quantity calculations easier. Point clouds include not only the ground but also vegetation, temporary structures, materials, wheel ruts from heavy machinery, and temporary undulations during construction. How those elements are organized and converted into an as-built surface, how the as-built surface is compared with the design surface, and how the area of interest is delineated can cause quantities derived from the same point cloud to vary greatly.

Therefore, for practitioners searching for information with "point cloud volume calculation CAD", what matters is not simply whether the point cloud can be read. What is important is whether it fits their workflow, including the preprocessing required for volume calculation, standardizing comparison conditions, extent management, verification tasks, and handling recalculations. An environment that only imports point clouds will ultimately require a lot of manual work and will not deliver the expected efficiency. Conversely, if the environment makes it easy to create surfaces, perform checks, and set up processes for reuse, it becomes easier to improve not only the accuracy of the quantities themselves but also the time spent on tasks and the ease of explanation.

In earthwork volume calculations, what matters in practice is not the level of numeric detail but the clarity of the basis for the numbers. On sites where the current conditions change during construction, it is not uncommon to have to recalculate quantities that were previously produced. If you start over from scratch each time, the value of introducing point clouds is diminished. That is why, when choosing point-cloud CAD, you should focus less on the apparent number of features or the flashiness of the interface and more on how reliably it can stabilize the entire earthwork volume calculation workflow.

Moreover, choosing a point-cloud CAD that is strong in earthwork volume calculations does not mean treating volume calculation in isolation. You need to consider the surrounding workflows as well—assessing current conditions, comparing with the design, checking cross sections, reconfirming completed quantities, and reconciling with on-site records. There is a completely different practical value between an environment that merely produces quantities and one in which those numbers can continue to be used on-site.

This article organizes and explains seven items you should check before comparing point-cloud CADs that excel at earthwork volume calculations. Rather than naming specific products or superficially introducing features, it explains in detail why each check is necessary and how it leads to practical differences in work. The purpose of this article is to help those considering adoption or reassessment develop decision criteria that truly suit their needs.

Please translate the following input into English.

Check 1: Can it stably handle large-capacity point clouds?

When choosing a point-cloud CAD for earthwork volume calculations, the first thing you should check is whether it can stably handle large-volume point clouds. This may seem like a basic requirement, but in practice it makes a very big difference. Point-cloud data tends to become heavier as the area grows, and when you compare before-and-after construction or multiple time points, the amount of information to handle increases further. If the display becomes slow, you have to wait every time you change the viewpoint, or the operation freezes whenever you change section conditions, you will end up spending more time on verification tasks than on the volume calculations themselves.

In practical earthwork volume calculations, you repeatedly perform operations such as viewing the whole before examining local areas, slicing cross sections to check, redefining ranges and recalculating, and verifying overlaps with design surfaces. In other words, whether an environment is strong for earthwork volume calculations depends largely not simply on whether files open, but on how smoothly point clouds can be displayed and switched without interruption. Even a slight display delay, when repeated tens or hundreds of times, results in a significant loss.

Also, in environments where the display is slow, workers may unconsciously reduce how often they check things. Even in situations that should be reviewed from a different perspective, they proceed as is because it's a hassle to move things. As a result, they don't notice discrepancies in quantities quickly and end up fixing them all at once later. In other words, display performance is not merely a matter of comfort; it also affects the accuracy of results and the speed at which mistakes are detected.

Furthermore, the ability to stably handle large point clouds also leads to greater flexibility in creating as-built surfaces. In environments where rendering and switching are sluggish, operators tend to thin out point clouds more than necessary or split the area into excessively small segments in an attempt to reduce the load. Of course, cleanup is necessary in some cases, but if that becomes the default every time, even data that could have been used as-is must be processed. As a result, preprocessing takes more time and the overall workflow suffers.

Before making comparisons, it is important not just to check whether files can be loaded, but to test them as you would actually use them on site. You need to confirm whether the transition from an overall display to a localized zoom is smooth, whether it refreshes immediately when section conditions are changed, whether overlaying the design surface causes any sluggishness in operation, and whether it remains stable when comparing multiple areas. In earthwork volume calculations, viewing point clouds itself becomes the core of the work, so environments that are weak in this area will inevitably become a burden later.

If you want to choose a point-cloud CAD that excels at earthwork volume calculations, first determine whether it can handle large amounts of data without interruption. No matter how many features it offers, if the display is unstable you'll end up relying on users' patience to keep it running. Make sure you don't overlook this in your initial comparisons.

Checkpoint 2: Is it easy to create the existing surface?

In earthwork volume calculations, the ease of creating the existing-ground surface is extremely important. No matter how dense the point cloud is, if the existing surface used for calculations is unstable, the quantity results will not be stable. That is why, when comparing point-cloud CADs, you need to focus on whether they make it easy to create an existing surface usable for earthwork volume calculations, rather than simply whether they can display point clouds.

Point clouds collected on-site always contain information other than the ground. Typical examples include vegetation, materials, temporary structures, heavy machinery, temporary mounds during construction, and vehicle tracks. Although these are correctly observed data, they are often not the ground surface itself that you want to compare in volume calculations. If these elements cannot be effectively removed, unnecessary irregularities will remain on the current surface, making quantity differences appear unnatural. Conversely, over-filtering can remove legitimate terrain features that should remain, such as slope crests and toes, excavation bottoms, and steps.

In other words, creating the existing surface requires balancing the removal of unnecessary objects with the preservation of necessary terrain features. Supporting this balance is the operability of the point-cloud CAD tools. The easier the environment makes it to determine which area to inspect, which information to retain, and which disturbances to remove, the more stable the existing surface will be. Conversely, in environments where it is difficult to check the relationship between the point cloud and the ground surface, trial and error increases and you end up losing a great deal of time just creating the existing surface.

Also, when creating as-built surfaces, balancing local detail and overall smoothness is important. Leaving every minor surface irregularity intact may look precise at first glance, but in earthwork calculations those fine details can cause quantities to fluctuate with each recalculation. Conversely, over-smoothing can erase shape differences that affect quantities, such as slopes and steps. What is practical and easy to use is an as-built surface that preserves necessary features while not being swayed by noise that is irrelevant to quantities. To achieve this, an environment that makes it easy to incrementally refine the surface while checking the terrain is required.

When making comparisons, it is not enough to look only at how easily you can derive an existing surface from the point cloud. What matters is whether the existing surface can be easily verified to actually represent the ground. It is important to be able to check the validity of the surface not only with plan views but also using cross-sections and three-dimensional views. The easier it is to assess not just numerical processing but also whether the terrain looks natural, the more the environment helps reduce mistakes.

Furthermore, the existing-condition surface is not something you create once and then finish. It is also important that it be easy to reuse when the design surface changes, when the scope of work changes, or when the existing conditions change during construction. Surfaces created on an ad hoc basis make subsequent work heavier. When selecting, you should also confirm whether the process of preparing the existing-condition surface is designed with later recalculations in mind.

A point-cloud CAD that is strong in earthwork volume calculations is an environment that not only displays point clouds but also makes it easy to organize them into existing surfaces that are meaningful as calculation targets. If this capability is weak, no matter how comprehensive the downstream functions are, the foundation of the quantities will become unstable. It is important to carefully assess the ease of creating the existing surface before making comparisons.

Checkpoint 3: Is it easy to align the comparison conditions with the design aspects?

Earthwork volume calculation is the task of finding the difference between the existing surface and the design surface, but if the comparison conditions are not aligned, the numbers produced will not represent meaningful quantities. Therefore, when selecting point-cloud CAD you must always check whether it makes it easy to align the comparison conditions with the design surface. This is not simply a question of whether the two surfaces can be overlaid, but whether it is easy to clarify exactly what is being compared under the same assumptions.

The existing surface is a surface created from observations, and the design surface is a surface created from planning conditions. Because these two serve different roles, treating them with the same mindset can easily compromise the comparison conditions. For example, if the existing surface still contains many small irregularities while the design surface has been considerably simplified, comparing them will produce differences that reflect not the true construction quantities but also the differences in how the surfaces were created. Conversely, if the existing surface is over-smoothed so that it no longer corresponds to important breaks or changes in the design surface, necessary volume differences can be overlooked.

To align comparison conditions, it is important to clearly standardize the scope of the subject, the treatment of boundaries, how slope faces connect, handling around structures, and the boundaries between flat areas and slopes. In particular, slope shoulders and slope toes, excavation bottoms, and the tops of slopes can cause large differences in quantities with only slight changes in conditions. If these parts are left ambiguous, even detailed numerical outputs tend to produce results that do not match site intuition.

Also, the design side is not necessarily limited to a single one. When you want to compare by construction stage or by work section, it is important to be able to organize the design conditions by part. Rather than comparing the entire area all at once, dividing the design side into meaningful units makes it easier to identify the causes of quantity differences and speeds up recalculation for each part. In other words, an environment that makes it easy to align the comparison conditions with the design side is one that clearly separates the existing side and the design side while allowing flexible comparison units as needed.

A point that is easy to overlook here is that having design surfaces and being easy to compare are not the same. Even if an existing design surface appears usable as-is, if it does not meet the comparison conditions with the as-built surface, you'll ultimately have to rework it. When comparing point-cloud CAD tools, you need to consider not only how to prepare the design surfaces, but also whether it's easy to organize the differences in conditions when they are placed side by side with the as-built surface.

Furthermore, the ease of aligning comparison conditions has a direct impact on recalculation and on responding to explanations. If design changes occur or the current status is updated, having the comparison conditions organized makes it easier to review only the changed parts. Conversely, if the comparison conditions are ad hoc, you end up re-examining everything from scratch each time, increasing both the time required and the burden of explanations.

When choosing a point-cloud CAD that is strong in earthwork volume calculations, you should determine whether it can clearly and consistently align comparison conditions, rather than just whether it can overlay surfaces. The reliability of the numbers depends greatly on how easily those comparisons can be organized.

Checkpoint 4: Is it easy to segment the area and determine partial soil volumes?

In practical earthwork quantity calculations, cases where it is sufficient to know only the overall quantity are relatively rare. There are many situations in which you need to see quantities for meaningful areas, such as by work section, construction stage, slope, or inbound/outbound management. Therefore, when comparing point-cloud CAD systems, you should always check whether area partitioning and the determination of partial earthwork quantities are easy. This is a factor that greatly affects the usability of downstream processes.

Because point clouds make it easy to capture existing conditions over a wide area at once, you may be tempted to treat the entire area in one batch. However, in earthwork volume calculations, quantities computed over a broad area are not necessarily usable as-is. For example, if the data includes terrain outside the construction scope, temporary storage yards, areas around existing structures, or areas scheduled for construction in later stages, you may obtain a total quantity that is difficult to use on site. Being able to clip the necessary area for calculation directly affects not only accuracy but also practical usability.

Also, having partial quantities makes it easier to verify the validity of the figures. When there is a large discrepancy in the overall quantities, tracing where the cause lies can be surprisingly difficult. However, if you can view quantities by work section or plot, it becomes easier to find places where discrepancies are concentrated or where results look anomalous. This is also highly effective for detecting mistakes quickly.

Furthermore, dividing the work area into sections also proves useful for recalculation during construction. On-site, the entire area is not always constructed at once; progress typically advances in parts. Therefore, there are times when you want to update the current conditions and revise quantities only for the completed sections. If the areas have been organized from the start, it becomes easy to replace just that portion and recalculate. If operations treat the whole as a single surface, even partial changes force you to modify the entire area, greatly reducing efficiency.

However, it is not simply better to divide the scope into ever finer segments. If you split it too finely, management becomes cumbersome and the relationship to the overall quantities becomes difficult to see. What matters is that the scope can be divided into units that are meaningful for construction and explanation. It is desirable to have an environment that allows you to define scopes in units suited to your actual work, such as construction sections, work phases, slope classifications, or soil categories.

Before making comparisons, rather than simply checking whether you can extract a portion, it's better to also verify whether you can naturally manage the quantities of each part. Important considerations are whether quantity differences are easy to spot, whether it's easy to reorganize when you change the range later, and whether you can easily move between total quantities and part quantities. Whether point-cloud CAD is strong at earthwork volume calculations is reflected less in its ability to compute everything in one go and more in how easy it is to work with the units you need.

To make the results of earthwork volume calculations useful on site, it's important not only to view them broadly in aggregate but also to manage the necessary areas in meaningful units. An environment that makes it easy to divide areas and grasp partial earthwork volumes enhances not only efficiency but also the ability to detect mistakes and to provide explanations.

Checkpoint 5: Is it easy to perform cross-sectional and 3D verification?

When calculating earthwork volumes, it is dangerous to judge based only on the numbers. Even if the quantities appear clean in the calculations, if there are inconsistencies or unreasonable interpretations in how surfaces connect or where boundaries lie, the results can deviate from reality. That is why, when choosing a point-cloud CAD, you should prioritize how easy it is to check cross-sections and verify in 3D. This is an indispensable requirement for assessing the validity of the quantities.

First, the value of checking cross-sections lies in being able to clearly grasp local shape differences. The positions of slope shoulders and slope toes, the depth of excavation bottoms, the height of crests, the way road edges terminate, and the connection between flat areas and slope faces can be difficult to judge by looking only at quantitative differences on a plan. By examining cross-sections, it becomes easier to see where the existing surface and the design surface intersect and where they diverge significantly. When there is a sense that the quantities are off, it becomes easier to determine whether the cause lies in local surface treatment or in the area boundaries.

On the other hand, sectional views alone can cause you to overlook the overall continuity. A given section may look natural, but a short distance away the flow of the surface can suddenly become unnatural. That’s why 3D inspection is necessary. Viewed in three dimensions, it’s easier to intuitively grasp the overall slope, the continuity of slope faces, local hills and valleys, and any unnatural bulges or gaps. In earthwork volume calculations, it’s important to evaluate not only local areas but whether the surface as a whole across the entire extent looks natural.

What makes practical work easier is an environment that allows you to switch back and forth between section checks and 3D checks. Find areas with large quantity differences in 3D and dig into the causes in the section view. For places where an unnatural discrepancy appears in the section view, verify them again in 3D in the context of the whole. When this back-and-forth can be done naturally, problem areas are discovered faster and unnecessary recalculations are reduced. Conversely, in an environment where verification is cumbersome, workers tend to rely on the numbers alone, and mistakes are discovered late.

Moreover, the ease of verification directly affects internal approvals and explanations to the client. There are many situations where presenting numbers alone fails to convince people. However, if you can show local differences in cross-sections and present the overall picture in 3D, it becomes much easier to share where quantity discrepancies originated. Making quantities easier to explain also means that subsequent checks and approvals proceed more smoothly.

Before comparing, you should assess not whether superficial features like the ability to cut sections or view in 3D exist, but whether those actions can be performed without interrupting the workflow. In environments where verifying quantity differences is cumbersome, operations tend to proceed based solely on numbers. It is easier to understand a point-cloud CAD that is strong in earthwork volume calculations as an environment where calculation results and shape verification are naturally linked.

Not relying too heavily on numbers and being able to confirm things from the shape of surfaces are fundamental to improving the accuracy of earthwork volume calculations. In that sense, the ease of checking cross-sections and 3D views is an important criterion that must not be overlooked when making comparisons.

Checklist item 6: Is coordinate management and field data integration easy?

In practical earthwork volume calculations, it is rare that the work can be completed solely within CAD. You will determine quantities while going back and forth among various pieces of information, such as point clouds acquired on-site, site photos, positioning information, records from before and after construction, and partial supplementary checks. Therefore, when selecting a point cloud CAD, you must always verify whether coordinate management and on-site data integration are easy to perform.

One common frustration in point-cloud earthwork volume calculations is that reproducing or explaining the calculation results takes a long time. A major reason is that it isn’t organized which area, which positional datum, and which records were referenced when making judgments. Especially on large sites, similar terrain often continues, and if the basis for the coordinates is ambiguous, you may think you are looking at the same location but actually be handling a slightly different area. It is not uncommon for slight discrepancies in quantities to be caused by shifts in position.

In an environment that facilitates coordinate management, it becomes easier to clearly document which area was targeted. If work-section boundaries, the calculation target area, the positions of the as-built point cloud, and the reference for the design surface are organized, later recalculations and verifications become markedly easier. Also, when site conditions change during construction, comparing against the same reference becomes easier, improving the reproducibility of the numerical results.

Furthermore, it is important that integration with on-site data be easy. There are always locations that are difficult to judge from point clouds alone. Ground beneath grass, the effects of temporary material stockpiles, temporary shapes during construction, and interfaces at structures can often be assessed more quickly by looking at site photos and notes. If those photos and records are linked to location information, you can immediately see which location the evidence relates to. Records without location information may be useful as references, but they tend to be weak as a basis for quantities.

When comparing CAD systems, it is important to evaluate not whether they can handle point clouds alone, but whether they make it easy to connect information collected on site with quantity calculations. If you want to track changes in existing conditions over time or later review a specific section, the better organized the coordinate management and record linkage are, the faster you can respond. This affects not only the efficiency of the initial calculation but also has a major impact on the burden of ongoing operations.

This ease becomes even more important when multiple people are working. If you rely on each person's memory and intuition, it becomes difficult to hand over conditions later. However, if the association between coordinates and records is clear, anyone can trace the same rationale. This is also very effective in preventing mistakes.

When choosing a point-cloud CAD that excels at earthwork quantity calculations, you should check not only the point-cloud visualization and calculation features but also whether it can connect site information with a verifiable positional basis. Earthwork quantity calculation is not only a task of producing numbers but also a task of maintaining the justification for those numbers. The foundation for this is the ease of coordinate management and integration with field data.

Checkpoint 7: Can you manage data that is robust for recalculation and explanatory responses?

When choosing a point-cloud CAD strong in earthwork volume calculations, the last thing to confirm is whether it offers data management that supports robust recalculation and explanations. This is easily overlooked during comparisons, but it makes a very big difference in practice. That's because earthwork volume calculations are not necessarily finished once the numbers are produced; rather, it's more often the case that they will need to be reviewed or explained later.

Changes in site conditions during construction are common, and parts of the design conditions may be updated. It is also not unusual to redraw only part of the scope, to recalculate quantities by construction section, or to recompute from a different angle for internal review; if the original calculation conditions are not organized, the work can end up being almost a complete redo.

What’s important is not just saving the resulting numbers, but making them easy to manage by recording which point cloud was used, which area was targeted, which as‑built surface and which design surface were compared, and where any gap‑filling judgments were made. If such assumptions are clarified, when changes occur it becomes easy to replace only the necessary parts and recompute. By contrast, if work is carried out on an ad‑hoc basis, it can take a long time just to recall why those numbers were produced.

The ease of providing explanations is the same. In practice, it is not sufficient for only the person who produced the quantities to understand them. You need to explain to other in-house personnel, site staff, managers, and, in some cases, external parties under what conditions the quantities were produced. If, at that time, not only the results but also the conditions and the verification history are left in a state that is easy to trace, explaining becomes considerably easier. Conversely, if the numbers become detached and stand alone, you will have to go back and re-find cross-sections, the scope, and surface conditions, and work will stop.

Moreover, data management that facilitates recalculation is also resilient to personnel changes. Because the initial person in charge may not remain the same, it is important that successors can easily understand the link between conditions and results. To avoid making the operation of earthwork volume calculations a matter of individual skill, manageability that makes it easy to retain conditions and rationale is an important criterion for comparison.

When comparing, you should not simply check whether it has save or export features, but evaluate whether it makes it easy to trace calculation conditions later, handle partial changes, and produce verification documents. An environment well suited to earthwork quantity calculations is not only one where the initial calculation is fast, but also one in which you are unlikely to get confused on subsequent calculations.

In practical work, there are situations where being able to reconfirm the same conditions later is more valuable than producing the initial numbers. Therefore, whether data management is capable of robust recalculation and explanatory responses is an important point you should always check when making a selection.

Practical conditions to clarify before comparing point cloud CAD

So far we've looked at seven checklist items, but to compare them properly it's important first to organize your own operational conditions. No matter how many features a product has, if it doesn't match your company's operations, you may not be able to use it effectively after implementation. What you should clarify before comparing is not what it can do, but what you want to do.

First, what you need to confirm is in what unit you want to capture the earthwork quantities. Whether the focus is on total quantities, by construction section, by construction stage, or by slope will change how you should think about subdividing the area. Next, it is also important to consider how frequently recalculations will occur. The emphasis you place on reusability will differ depending on whether the site is one that is reviewed many times during construction or whether the focus is on quantity verification at completion.

Also, you should organize how point clouds are acquired and how on-site records are brought back. The importance of on-site data integration varies depending on how much you make use of supplementary records such as site photos and records with location information. Furthermore, who carries out the work is also important. Whether a small number of designated staff handle it on rotation or multiple people divide the tasks changes how much weight is placed on the ease of data management and the sharing of conditions.

By clarifying your operational requirements in advance like this, the points to check when comparing options become clear. You’ll be less likely to be distracted by features that merely seem convenient, and it becomes easier to compare based on the conditions you truly need. When selecting point cloud CAD, it’s safer to think of the choice as verifying compatibility with your actual workflow rather than simply comparing products.

Common Pitfalls When Selecting Point Cloud CAD

When trying to choose a point-cloud CAD that excels at earthwork quantity calculations, you can end up selecting an environment that is hard to use. Here, we summarize common mistakes that often occur during selection.

The first issue is judging solely on whether a point cloud can be read. Being able to load data is different from being adept at earthwork quantity calculations. Unless you examine everything up to creating the existing surface, organizing comparison conditions, subdividing the area, checking cross-sections, and handling recalculations, you won’t be able to tell the difference from actual practice.

The second is focusing solely on the speed of the initial calculation. Earthwork quantity calculations often require recalculations and responses to inquiries, so being fast only on the first run is meaningless if you can't trace the conditions later. It's important to take ease of reuse into account as well.

The third point is failing to test under realistic data volumes and field conditions. Lightweight samples may feel responsive, but in production point clouds, rendering and verification can become sluggish. When making comparisons, you should evaluate under conditions that closely match your own projects.

The fourth is underestimating the connection with site records and coordinate management. If you choose based on the assumption that everything will be completed within CAD, you'll have trouble later when on-site verification becomes necessary. To maintain the basis for earthwork quantity calculations, connection with the site is also important.

The fifth is deciding based solely on an individual handler’s personal habits. If you don’t also consider whether it will be easy to operate and easy to share conditions when the person in charge changes, it will become difficult to use in the long term.

To avoid these failures, it is important to place the perspective of comparison on the operational workflow rather than on a list of features. Making decisions based on the sequence of what to look at, what to prepare, what to verify, and how to retain things will improve the accuracy of selection.

Summary

When choosing a point-cloud CAD that is strong in earthwork volume calculation, it is important to confirm seven items: that it can stably handle large-capacity point clouds; that it makes it easy to create existing ground surfaces; that it makes it easy to align comparison conditions with the design surface; that it facilitates area partitioning and grasping partial earthwork quantities; that it makes cross-section checks and 3D verification easy; that coordinate management and integration with field data are easy; and that it can perform robust data management for recalculations and explanatory responses.

What matters is not whether you can read point clouds, but how easily you can organize the assumptions for earthwork quantity calculations. The accuracy of earthwork quantity calculations depends greatly not only on the presence or absence of calculation functions but also on how the current surface is modeled, the standardization of comparison conditions, the ease of verification, and the ease of reuse. By organizing your operational conditions before making comparisons and making decisions according to your practical workflow, you can more easily reduce failures after implementation.

Also, to further stabilize earthwork volume calculations, it is effective to consider not only the choice of CAD but also how to record information with location data on site. If you have photos and records that make it easy to trace the basis for later judgments about the existing surface, recalculations and explanations become much smoother. The idea of using iPhone-mounted GNSS high-precision positioning devices such as LRTK to make it easier to keep such georeferenced records pairs well with operations for point-cloud volume calculations. If you truly want to create an environment strong in earthwork volume calculations, it is important not to stop at comparing point-cloud CADs, but to also organize how records are taken on site.