Seven Items That Are Often Omitted in Drone Surveying Procurement Specifications

When outsourcing drone surveying, clients tend to proceed with the broad understanding that “the contractor will fly, measure, and deliver maps and point clouds.” However, in practice that high-level understanding is not enough. If you issue an order while leaving vague how to delineate the target area, how to define required accuracy, the formats of deliverables, coordinate systems, or how to share site conditions, the contractor may be able to complete the work itself but produce deliverables that are difficult to use in downstream processes, or cause additional costs and re-surveys.

Especially in construction, surveying, and civil engineering sites, drone survey deliverables seldom stand alone; they feed into multiple processes such as design, as-built verification, volume calculations, current condition surveys, construction planning, and stakeholder briefings. For that reason, the procurement specification is not a simple request memo but an important document to lock in, in advance, “what deliverables are required for which tasks, under what conditions, and to what extent.”

This article organizes seven items that are particularly easy to omit from drone surveying procurement specifications, from the perspective of recognition gaps that commonly occur in practice. It offers review hints for those considering outsourcing and for anyone who has experienced “the deliverables were delivered but were hard to use on site.”

Table of contents

• Why drone surveying procurement specifications tend to be vague

• 1. Ambiguous definition of the target area

• 2. Abstract wording for required accuracy

• 3. Insufficient specification of deliverable formats

• 4. Coordinate system, elevation datum, and unit assumptions are not shared

• 5. Shallow sharing of site conditions and flight constraints

• 6. Re-survey responses and responsibility scope are not decided

• 7. Deadlines and verification methods are set only on a deliverable-receipt basis

• What clients should fix is not “measurement conditions” but “usage conditions”

• Things to confirm internally before ordering to avoid recognition gaps

• How to think to make a procurement specification usable in practice

• Summary

Why drone surveying procurement specifications tend to be vague

Drone surveying looks simpler and more transparent than traditional ground surveying and gives the impression that a large area can be captured in a short time. As a result, clients often think that it is sufficient to state only “where to measure.” In reality, however, even on the same site, flight planning, handling of control points, required accuracy, and the way deliverables are packaged all change depending on the purpose of the survey.

For example, the required conditions differ greatly depending on whether the purpose is current condition checking, preliminary work for as-built management, volume calculation, or comparison against design. If the client does not write the purpose in detail and the contractor proceeds with general assumptions, the work itself may finish without issue but later produce mismatches such as “this format is hard to import into our CAD,” “this accuracy is weak as a basis for quantity calculations,” or “the desired area was not captured.”

Moreover, it is common that site staff, the ordering department, subcontractors, design engineers, and construction managers each expect slightly different things from the deliverables. If the specification is superficial, those differences cannot be absorbed and problems surface near the end of the project. For that reason, a procurement specification should not specify the process of “flying and measuring” but should define the preconditions for use: “what deliverables are required for which uses and under what conditions.”

1. Ambiguous definition of the target area

The most commonly omitted item in procurement specifications is the definition of the target area. Expressions such as “the entire planned reclamation area,” “the whole site,” or “around the slope” leave room for differing interpretations between the client and the contractor. In practice, what is actually needed may include not only the exact interior of construction sections but also surrounding roads, temporary yards, slope toes, drainage routes, access roads, and interface areas with adjacent structures that will be referenced in downstream processes.

If imaging is conducted with the target area ambiguous, post-delivery issues may arise such as “necessary edges are cut off,” “the upper part of a slope is captured but the lower part is missing,” or “there is not enough margin to compare height differences with adjacent land.” If such problems are discovered during volume calculations or construction planning, additional imaging or supplementary surveys by other means may be required, costing extra time and money.

In the specification, it is important not only to state the planar target area but to indicate, in line with usage purpose, how much of the surroundings should be secured as deliverables. For example, if the purpose is comparison with design, margins around the design area are necessary; if the purpose is checking slope or embankment deformation, both the top and bottom edges must be captured without being cut off. Marking on site drawings or plan views, explicitly indicating excluded areas, and noting additional areas to be included will greatly reduce recognition gaps.

Also, the target area should be considered not only in plan but in the height dimension. On sites with tall trees, overhead lines, scaffolding, or heavy-equipment storage, you must decide whether the target is only what is visible from above or whether occlusion requires separate supplementary surveys; if this is not decided, the contractor will be left to decide. As the client, reflect in the specification “how much visibility is needed to achieve the purpose.”

2. Abstract wording for required accuracy

Another common issue is that the required accuracy is described too abstractly. Expressions like “high accuracy,” “accuracy usable for surveying,” or “accurate enough for volume calculations” may seem convenient but are practically useless as standards. Contractors will respond with general assumptions or, to be safe, estimate with stricter conditions.

If the required accuracy is not clearly written, the client will also find it hard to judge the quality of the deliverables. Even if the contractor believes they delivered according to the specification, the client may feel “the errors are larger than expected.” This gap is usually caused by insufficient definition at the ordering stage rather than a quality problem.

When considering required accuracy, basic practice is to work backward from the purpose. For current condition overview or progress sharing, overall visibility and readability may be prioritized over strict centimeter-level control. On the other hand, if the deliverables will be used for quantity calculations, as-built verification, checking interfaces with existing structures, or design comparison, you must first organize the required accuracy levels in both horizontal and vertical dimensions. If this is ambiguous, you often end up with deliverables that are “usable as presentation materials but weak as a basis for quantity calculations.”

Also, accuracy is not only an overall average property of the deliverable; it matters where the accuracy must be ensured. Whether you need uniform accuracy across the entire target area, higher accuracy only in key parts, or tolerate some errors at edges will change the work plan. In the specification, try to write not just the accuracy requirements but “for what use, in which parts, and to what degree accuracy is required” so the contractor can make clearer judgments.

Listing how accuracy will be verified will also reduce post-delivery troubles. If it is unclear how the contractor will validate and report results, a raw number alone may be hard for the client to evaluate. Required accuracy and verification methods should always be specified together.

3. Insufficient specification of deliverable formats

Because contractors can provide many types of deliverables for drone surveying, clients sometimes specify broadly that “point clouds, orthophotos, and drawings should be sufficient.” However, even the same “point cloud” can be handled in different ways, and even the same “drawing” may or may not be usable in downstream processes. Insufficient specification of deliverable formats is one of the most common sources of mismatch discovered after delivery.

For example, if your internal software requires a specific import format and you do not state that in the specification, the deliverable may be provided in a general format. Even without ill intent on the contractor’s part, you may need conversion work, attribute data may be missing, or layer organization may differ from expectations, adding extra work before use. Point cloud density and whether classification is provided, orthophoto resolution, CAD layer structure, and the need for cross-sections or longitudinal/transverse profile materials—if requested later, these increase coordination cost.

It is important to reflect not only “what to deliver” but “who will use the deliverable and how” in the specification. Deliverables suitable for site staff reviewing information, for design engineers to import into CAD, for quantity calculation, or for internal presentation materials will differ. If you organize the intended users and their use cases at order time, you can avoid creating unnecessary deliverables and more easily ensure what is truly needed.

The granularity and composition of delivered data are also easily omitted. Whether you want the target area split by construction section or delivered as one set, whether raw data are required, whether intermediate results are needed, and the desired report format are all important in practice. If these are vague, the contractor will package deliverables in a convenient way that may not match your internal operations, requiring reorganization later.

Deliverable formats are not merely about file extensions. Decide from the perspective of whether they can be reused downstream and whether they can be incorporated reasonably into existing internal workflows. The specification should, as much as possible tied to usage purpose, state deliverable types, formats, units, splitting method, and any necessary accompanying documents.

4. Coordinate system, elevation datum, and unit assumptions are not shared

One of the most serious mismatches in outsourcing arises from insufficient sharing of coordinate systems and elevation datums. Drone surveying deliverables may look well-organized, but if the coordinate system does not match, they cannot be overlaid with existing drawings or design data. This problem is often not noticed immediately after delivery; it frequently appears only when integrating with other data, which makes rework burdensome.

In the specification, you must explicitly state not only the horizontal coordinate system but also the elevation datum, unit system, and the requirements for alignment with existing data. For example, if your internal drawings are managed in a certain coordinate system and the contractor processes and delivers under a different assumption, the shapes may appear to align visually but require conversion for proper positional alignment. If elevation datums do not match, quantity and height comparisons will also be affected.

On site people sometimes say “make it alignable with our drawings,” but this is a weak specification. From the contractor’s perspective, it is unclear what exactly to align and under which standard. You need to confirm whether existing control points will be used, whether coordinate tag information is available, whether verification points will be set on site, and whether the deliverable should be checked against design drawings or an existing registry. Without clarifying these, the responsibility for misalignment becomes ambiguous later.

Unit handling must not be overlooked either. If units for distance, elevation, area, and volume differ between internal materials, procurement documents, and delivered results, oversights are likely during verification. To avoid confusion despite having numerical results, standardize numerical assumptions in the specification.

Coordinate system issues are less about the intrinsic quality of the drone survey and more about connectivity with existing workflows. That is why this is one of the items you should fix at the procurement stage. Prioritize “use” over “measurement” when organizing conditions.

5. Shallow sharing of site conditions and flight constraints

The more familiar the client is with the site, the more likely they are to omit detailed site descriptions in the specification because they assume “the contractor will understand once they see the site.” For the contractor, however, insufficient sharing of site conditions is one of the factors that most affects planning. Lack of information about topography, obstacles, surrounding environment, access conditions, allowable working hours, heavy-equipment operation, and third-party traffic can affect both safety and quality.

For example, even if aerial imaging is assumed, a site where trees or structures obscure the ground may not be completable by drone alone. Areas sensitive to wind such as valleys or slopes, terrain with large elevation differences, busy adjacent roads, nearby structures, and scheduled temporary installations all influence imaging conditions and flight planning. Without prior sharing, plans may need to be changed on site or imaging quality may be lower than expected.

Insufficient sharing of site conditions does not only lower operational efficiency. If the contractor plans using general assumptions without fully understanding site constraints, the required areas may not be captured, poor lighting conditions may reduce readability, or coordinating with operating equipment may take time. The client may think “couldn’t they survey it?” and the contractor may say “we weren’t told,” damaging trust.

You don’t need to write all site conditions in technical detail in the specification, but at least organize and share information that affects deliverable quality in advance. Examples include allowable access times, whether any equipment needs to be stopped, obstacles around the site, vegetation or temporary installations that affect ground visibility, and whether safety coordination with adjacent parties is necessary. Attaching site photos, simple plan-view annotations, or past site issues greatly improves the contractor’s understanding.

What is obvious to the client is often the most important information for the contractor. In the specification, convey not only what you want measured but also what makes measurement difficult with equal weight to prevent recognition gaps.

6. Re-survey responses and responsibility scope are not decided

When outsourcing drone surveying, you should decide in the specification how to handle not only delivery-time issues but also post-delivery “deficiencies.” In reality, the approach to re-surveys is often omitted and becomes a frequent point of contention. The client may assume “if the deliverables do not meet the required quality, they will redo it,” while the contractor may assume “we completed the work within the original specification.”

It is important to separate the causes that might necessitate a re-survey. The response differs depending on whether the issue stems from clear workmanship defects or failure to meet specification, ambiguity in order conditions that created expectation gaps, or changes in site conditions requiring additional imaging. If you do not decide this in advance, disputes arise later about whether re-shooting is chargeable or free, stalling site decisions.

The specification should at least specify what conditions constitute acceptance and what conditions qualify for supplemental surveys or reprocessing. Being specific about items prone to disputes—omitted areas within the specified range, failure to meet required accuracy, inability to deliver in the specified format, or poor alignment with existing data—will help. Conversely, state that additions to the target area after ordering or changes in purpose that require additional deliverables will be handled under separate agreement, thereby delineating responsibility.

Also important in practice is the decision process for whether issues can be resolved by reprocessing or require a site revisit. Clients tend to immediately assume “re-shoot,” but often issues can be resolved by adjusting processing parameters or supplementing with existing data. Conversely, if the root cause is insufficient capture range or poor site visibility, a revisit may be the only solution. Without this organization, both parties end up speaking in terms of gut feeling and fail to align.

To maintain a good relationship with contractors, treat re-survey terms not as clauses to bind the other party but as rules to speed decisionmaking when problems occur. Draw the boundary lines at the ordering stage to avoid passing blame later.

7. Deadlines and verification methods are set only on a deliverable-receipt basis

Deadlines and verification methods tend to be handled lightly in specifications. Many orders say only “deliver by [date],” but that alone is insufficient in practice. Drone survey deliverables are not necessarily usable the instant they are delivered; only after content checks, overlaying with existing data, internal review, and any required correction requests do they become ready for operational use. If the deadline is set as merely a receipt date, downstream schedule delays are likely.

For example, if you plan to use deliverables in a site briefing or design meeting, it may be too late to inspect contents only on the day of receipt; if format mismatches or omissions are found, there is no time to adjust. A practical specification should include, in addition to the final delivery date, whether intermediate checks are required, timing for submission of verification data, deadlines for corrections, and the method for acceptance decisions.

Verification methods are also important. Writing only “we will inspect and accept if no issues are found” leaves ambiguity about what constitutes “no issues.” When multiple reviewers within the client organization are involved, a site staffer may approve while design or survey staff find deficiencies. The specification should predefine verification criteria: coverage of target area, materials for confirming specified accuracy, coordinate system conformance, compliance of deliverable formats, and presence of required drawings and reports. Sharing these acceptance criteria in advance reduces later discrepancies.

Deadlines must also consider the influence of weather and site conditions. Drone surveying includes both field work and processing; therefore, plan schedules including shooting date, contingency days, processing period, and verification period. If the client sets a tight schedule with little margin when working backward from the final use date, small changes can cause the entire schedule to bottleneck.

Deadlines and verification methods are not mere formal items to be tacked on at the end of the specification. They are the operational design to bring deliverables into practical use. Defining not only what is delivered but how it will be checked and made usable increases outsourcing success.

What clients should fix is not “measurement conditions” but “usage conditions”

A common thread among the seven items above is that specifications written as “job requests” are prone to omissions, while specifications written as “definitions of usage conditions” are easier to organize. Drone surveying highlights flight and imaging steps, which leads to a tool-centered approach. However, what really matters in a procurement specification is to clearly state what you want to be able to do with the deliverables after delivery.

Target area, required accuracy, deliverable formats, coordinate system, site conditions, re-survey policy, deadlines, and verification methods are all conditions to enable downstream use. If you issue an order with these items ambiguous and “try it once” as the approach, you may advance experimentally but will see problems surface when moving to full operational use. In construction and civil engineering, the measurement itself is not the goal—connecting results to design, construction, and management decisionmaking is the goal. That premise must be reflected in the specification.

Even if the client cannot write every technical detail, organizing internal use cases first will reveal needed conditions. Who will use the deliverables, for what purpose, which existing data must be overlaid, by when are they needed, and where will quality be checked? Thinking in that sequence makes it easier to organize what should be written in the specification.

Things to confirm internally before ordering to avoid recognition gaps

Internal alignment before contacting a contractor is essential to reduce misalignment. In practice, clients sometimes proceed to estimates or consultations before their own conditions are settled. In that case, the contractor must estimate on provisional assumptions, increasing the likelihood of later condition additions.

First, confirm the intended uses of the deliverables: current condition overview, quantity calculation, construction planning, presentation materials, maintenance, design comparison, etc. If purposes are mixed, set priorities. Next, organize existing drawings, control points, internal software, and who will operate the deliverables post-delivery. Without this, no one may be immediately able to use the delivered data.

Also collect site constraints the site team knows as early as possible: difficult flight time windows, access procedures, movements of heavy equipment and workers, and the need for coordination with adjacent parties. These are the kinds of information only those familiar with the site possess and directly influence quality. Drafting the specification is not merely preparing a document for the contractor but a process of aligning internal preconditions.

How to think to make a procurement specification usable in practice

A practical procurement specification is not one that piles on technical jargon. It is a specification where purpose, conditions, and verification methods are connected. Conversely, even if terminology is tidy, if the relationship to usage conditions is not described, the specification will be hard to use on site.

For example, “deliver a point cloud” is insufficient. But writing “deliver a point cloud in a format compatible with our internal workflow, aligned to coordinate conditions that match existing drawings, to be used for volume calculation and design comparison” allows the contractor to interpret necessary assumptions. Similarly, instead of “measure with high accuracy,” write “secure accuracy sufficient to confirm embankment shape and quantity within the specified area, with verification materials,” which makes later judgments easier.

In other words, think of the procurement specification as a translation document of business requirements rather than a list of technical specs. What clients most struggle with in practice is not the absence of deliverables but deliverables that exist and are unusable. To avoid that, keep the seven items discussed here as the minimum axes of confirmation.

Summary

The seven items that are often omitted in drone surveying procurement specifications are: target area, required accuracy, deliverable formats, coordinate system, site conditions, re-survey response, and deadlines/verification methods. Although they appear as separate caution points, they all connect to a single goal: obtaining deliverables that are usable in downstream processes.

If the client leaves these conditions ambiguous and the contractor proceeds with general assumptions, mismatches will surface after delivery. Conversely, if you organize in advance what the deliverable will be used for, how much is needed, and how it will be verified, conversations during the estimation stage will be more concrete and reduce the risk of unnecessary additional work or re-surveys.

In practice, it is effective to combine drone surveying with ground-based control or verification surveys as needed instead of relying solely on aerial surveys. Combining the broad overview from the air with high-precision ground positioning improves deliverable reliability and usability on site. For example, establishing control checks before and after imaging, obtaining checkpoints at key locations, and conducting on-site verification after delivery helps connect drone deliverables more directly to practical use.

In that sense, a drone surveying procurement specification is not a document that only describes aerial measurement conditions. It is a document that designs data operations usable on the ground including positioning and verification methods. When advancing such an operation, having the capability to provide high-precision ground positioning alongside drone surveying stabilizes practice. Touching lightly on high-precision positioning systems like LRTK and considering combinations suited to your company’s sites will make it easier to streamline the flow from procurement to utilization.