The flight was fine. The processing was fine. You provide a volume — cut, fill or stockpile quantity — and the contractor invoices off of it. Then the engineer for your account does his own math and brings you a different number. Now it isn't a flight that you're defending; it's an entire dataset, sinking the payment application until someone resolves which number is correct.
This is one of the more awkward positions you can find yourself in as a drone surveyor on site, because rarely does the dispute center around whether or not the drone was right — if there are two seemingly normal measurements from two different techniques for the same piece of ground that don't match, you'll end up needing to defend some technique. What you do about it, and how well you document your efforts — so that it doesn't turn into a stalled payment — is far more important than a marginally better GSD on the flight itself.
I could be honest about something here: this is not an edge case. Quantity disputes over cut fill and stockpile volumes are the most common billing conflicts on active sites — exactly why the documentation habits below are worthwhile building into your workflow before the first dispute hits. Earthwork is where construction projects lose or gain margin more predictably than anywhere else.
Two Drone Surveys of the Same Site May Have Inconsistent Results
Earthwork volume disputes are common enough to be a specific class of construction billing controversy, and even low-tech cross-section survey techniques can produce large quantities variance on big earthwork packages — variances large enough to spark a change-order battle before anybody has so much as touched a drone collection. The numbers become more accurate once we add drones and photogrammetry into the mix, but "more accurate" doesn't necessarily translate to "not subjectable to dispute." Most mismatches are driven by a handful of specific factors.
Ground control point count and placement. GCPs are the ground control points that provide a real world coordinate system to the photogrammetric model, and therefore its surface accuracy is dependent on how many were used and their positions. Georeferencing with five well-positioned GCPs vs. two poorly placed ones across equivalent physical terrain yields consistently different elevations on the same terrain — again not due to "wrong-ness" of flight but varying quality of georeferencing.
Ground point classification. Before a volume calculation can run, the software has to separate true ground points from everything else — vegetation, parked equipment, stockpiled material that shouldn't count as "ground." If one survey's classification settings are looser than another's, vegetation or vehicles left in the ground surface will skew the resulting volume, sometimes significantly.
Calculation method. There are several methods available to transform a surface model into a volume number. The grid method partitions the site into a number of cells and adds up the cut/fill per node, while TIN (triangulated irregular network) creates a triangle mesh from the point data, and volumes can be computed directly from that surface. Both approaches are valid but not always yielding the same number on the same data set — which can matter when two parties used different tools or settings unknowingly.
Baseline mismatch. Take the cut/fill number, which is always in comparison: current surface vs. old survey, or current surface vs. design surface. However, if one party is measuring against the progress survey completed last month while the other measured against the original pre-construction baseline, that discrepancy in two numbers will occur for reasons completely unrelated to how targeted and accurate either survey was.
Timing gaps. The survey flown Monday and a survey flown the following Monday might legitimately document two very different volumes if hauling, grading or weather events happened in between — a gap that is easily overlooked in someone comparing two reports side by side without checking flight dates.
Issues That Make the Volume Report Defensible
None of the above factors render drone-derived volumetrics inaccurate, but rather, make documentation the difference between a report that settles a dispute versus one that is at odds with established science. There are a few practices that do consistently separate the two.
GCP residuals in every report (not only the final volume number) is documented by you. This allows anyone reviewing the data to gauge how closely the model fits ground truth without merely taking the number on faith by plotting RMSE against check points.
Set a baseline survey (and explicitly reference it in every report) If progress flights need to be made weekly or biweekly at all, then each report where these are used should make clear which previous surface is being compared against — the true, pre-construction baseline; the previous progress survey; or the design surface — so that nobody downstream needs to guess.
Disclose methodology, not just results. Identify what calculation method you used (grid or TIN), the point cloud density and ground classification settings; This way, a competing surveyor or an adjudicator has something to reference against; Otherwise there are two unexplained numbers that simply do not match! For example, at a recent Arizona earthwork job a contractor's drone-measured stockpile volumes agreed with their GPS-guided dozer logs to within a couple percentage points — and that result held true specifically because they could check against the real methodologies employed and not just the final number (because the GCP data was there).
Come out and fly on a regular, released schedule. Weekly or biweekly progress surveys, conducted on a known cadence and tied to billing milestones, provide both sides with a common timeline that is much more compelling than an ad hoc flight organized only when a dispute has already arisen.
Grid Method or TIN – Does it Matter Which One?
Neither method will be inaccurate enough for billing and tracking purposes in most standard earthwork jobs, but the more important point is that both sides of any dispute compare numbers generated in the same way. Because each cell's volume can be hand-checked if necessary, grid-based calculations are easier to explain and audit manually. Because the triangulated mesh closely follows the surface shape without imposing a grid, TIN-based calculations often treat rough or complicated terrain more accurately. For high-stakes earthwork billing, you might as well check which method your software defaults to and have an answer if the number ever gets challenged.
How Much This Actually Costs If It Goes Wrong
The sudden cost of a contested volume number is an application for payment unable to be processed — the contractor won't get paid on time and everyone above them in the chain are asking questions. That delay isn't by any means insignificant on larger earthwork packages; adjudication and formal dispute resolution for quantity claims can take as long as many months and cost an order of magnitude more in time and legal fees than the combined cost of a second survey with better documentation.
The less obvious cost is that if an engineer for a client sees a drone survey producing numbers they cannot explain, the whole data source loses credibility — not just that one report. Drone surveys have been adopted by industry for verifying earthwork quantities, a trend that has seen clear advantages over traditional methods in recent years — a 2024 study conducted by the Associated General Contractors of America demonstrated that 68 percent of earthwork contractors used drone surveys to perform quantity verification, compared to just a few years ago. That growth happened exactly because drone data supersedes guesswork with independent, repeatable measurement; an individual undocumented discrepancy directly undermines the credibility advantage of precision derived from best practices over manual cross-sections.
And what I mean by that is if you have a volume number that keeps getting challenged, the solution is never just fly it again and hope for a cleaner number. This is typically a problem of processing and documentation — tighter GCP placement, consistent classification settings, and more of a report that tells the story than just a number for cubic-yards at the end. Not only does it solve the first dispute, but getting that processing pipeline standardized from the very first baseline flight is what prevents the second one.
Getting It Right In The First Attempt
A disputed cut/fill number doesn't often mean the flight was bad — it usually means the two sides comparing numbers weren't ever using the same methodology. What makes volume reporting evidence, rather than a claim, are consistent GCPs, disclosure of classification settings, a clearly defined baseline and description of the method of calculation.
Going through a project setup for earthwork monitoring, or curious to see how documented, transparent methodology surveys fit together across other site types? Here's some recent work worth having a look at.
