Six Reasons Drone Surveying Fails to Be Adopted Internally and How to Address Them

Although many companies are interested in drone surveying, discussions about internal adoption often stall. On-site operations face labor shortages and increasing needs for efficiency, yet management, administrative departments, and field staff frequently see things differently, causing progress to stall. Especially in construction, surveying, and civil engineering practice, it is difficult to decide adoption purely at a desk; decisions must cover cost, accuracy, safety, operational setup, and how deliverables will be used.

For that reason, proceeding simply because “it seems convenient” or “others are starting to use it” can actually breed distrust among cautious stakeholders. Conversely, if you organize the reasons adoption stalls and prepare realistic countermeasures for each, internal adoption becomes much easier to advance. The key is not to steamroll opposition but to anticipate and eliminate the reasons projects get stuck.

This article organizes six typical factors that cause internal drone surveying adoption to stall, and explains from a practical perspective why adoption stops and how to address each issue. It avoids framing in-house versus outsourced as an antagonistic choice and includes the realistic concept of phased implementation so you can see approaches that make internal consensus easier to build.

Table of contents

• Why does drone surveying seem necessary but fail to progress?

• Reason 1: Hard to budget for and difficult to explain cost-effectiveness

• Reason 2: Perceived lack of personnel leads to “it won’t be manageable after adoption”

• Reason 3: Accuracy concerns make it difficult to link with existing surveying tasks

• Reason 4: Operational burden is unclear and it looks like “post-adoption will be troublesome”

• Reason 5: Unclear usage image leads to “even if we adopt it, we won’t make full use of it”

• Reason 6: Large differences in interdepartmental perceptions prevent internal agreement

• If you want to advance internal adoption, think in terms of phased implementation rather than in-house vs outsourcing

• Four perspectives to set up first to overcome internal adoption barriers

• Common mindsets of companies that successfully establish drone surveying

• Summary

Why does drone surveying seem necessary but fail to progress?

Drone surveying is attracting attention as a method that makes it easy to grasp large areas in a short time and is useful for current-condition assessment, as-built verification, earthwork volume estimation, and progress sharing. However, actual internal adoption tends to stall more than expected. The reason is that, beyond the performance of the drone itself, there are many decision items required within the company.

For example, field departments expect improvements in work efficiency and safety, while administrative departments worry about cost-effectiveness and training burdens. Surveying and design staff emphasize accuracy and deliverable compatibility, and executives look at whether a sustainable system can be established. In other words, even though the word “adoption” is used, each stakeholder is focusing on different points. If you proceed without organizing these perspectives, proponents will talk about positive effects while cautious stakeholders raise risks and burdens, and discussions often stall without convergence.

Moreover, drone surveying is not finished by purchasing the aircraft. When you include flight planning, on-site checks, safety management, shooting condition settings, georeferencing and validation, analysis, deliverable verification, and internal sharing, the scope of operations becomes broad. This breadth creates high expectations but also raises the adoption hurdle.

That is why it is important not to treat drone surveying as a panacea. Defining what you will use it for, what you will keep in-house, and how to connect it with ground surveying and existing workflows is the starting point for advancing internal adoption.

Reason 1: Hard to budget for and difficult to explain cost-effectiveness

One of the most common initial reasons adoption stalls is budget. While drone surveying may appear to help reduce labor and shorten time, budget proposals will not pass if “how much for what” and “what can be reduced” remain vague.

A frequent mistake is discussing only the cost of the aircraft. In reality, besides the aircraft there are peripheral devices, maintenance, training, analysis environment, and possibly external contracting costs. Additionally, the first year involves trial and error, so if you present adoption on the assumption of immediate large profits, cautious stakeholders will see the proposal as unrealistic.

Also, explaining cost-effectiveness only with abstract phrases like “fewer people” or “shorter time” rarely convinces internal audiences. In field practice, value often manifests as reduced entry into hazardous areas, fewer re-surveys, faster wide-area understanding, or easier explanations to stakeholders rather than complete workforce reductions. If you do not quantify these in numbers or in terms of work units, the persuasive power of adoption weakens.

An effective countermeasure is to narrow target tasks rather than claiming enterprise-wide optimization from the start. For example, focusing on recurring tasks such as monthly current-condition checks, volume verification, fixed-point monitoring of development sites, or initial post-disaster assessments makes it easier to compare with traditional methods. Converting benefits into manageable indicators—on-site time, required personnel, need for revisit, time to share deliverables, frequency of responses to hazardous areas—makes the effects of adoption more visible.

Furthermore, in the early stage, instead of seeking a budget for “full deployment,” it is realistic to propose phased implementation such as “small-scale verification,” “operation start for limited tasks,” or “use external resources only during busy seasons.” Projects that would stall with a large initial investment can pass if you premise adoption on limited operation to confirm results.

To secure a budget, it is more important to clarify target tasks, comparison indicators, trial period, and evaluation criteria than to talk about visionary benefits. Proposals that advance internal adoption usually have these four items well organized.

Reason 2: Perceived lack of personnel leads to “it won’t be manageable after adoption”

Personnel shortage is another major barrier to internal drone surveying adoption. On-site staff are already busy with routine work, and if adoption proceeds without deciding who will take on the new tasks, it tends to be postponed. Especially when proponents say “let’s buy it first and figure things out later,” field staff often react with “who will bear that burden in the end?”

The trouble here is that it is not enough to have an operator. In practice, roles must cover pre-checks, flight planning, safety management, data organization, analysis requests and deliverable verification, and internal sharing. If it is not clear who will fly, who will receive the deliverables, and who will reflect them in operations, the field will be confused after adoption.

Also, concentrating responsibilities on a single person risks halting operations when that person transfers or leaves. Some companies where internal adoption did not take root have had the experience of only a few enthusiastic individuals pushing things forward, resulting in person-dependent processes that could not be sustained. For this reason, cautious stakeholders often worry “won’t this end up being a temporary initiative again?”

A practical countermeasure is to break down roles in detail before adoption. Design the process so tasks can be shared as an extension of existing work rather than assuming one person will handle operation, assistance, safety checks, deliverable verification, and internal explanation. For example, limit flight operation to a small set of responsible staff while surveying or site management personnel handle deliverable verification and utilization decisions. This prevents concentrating the burden on one person.

Also, it is important not to aim for full in-house operation from the start. In the early stages, outsource part of flight or analysis and focus internal efforts on contracting decisions, organizing site conditions, and how to use deliverables. This enables operation with a small team. In practice, it is often easier to start by increasing in-house capabilities gradually while identifying appropriate use cases than to try to manage everything internally at once.

Countermeasures to personnel shortages are not limited to hiring more staff. By dividing roles, avoiding person-dependence, and combining external resources, you can design an operation that runs with few people.

Reason 3: Accuracy concerns make it difficult to link with existing surveying tasks

A common worry when considering drone surveying adoption is accuracy. This concern is valid and should not be taken lightly. In construction, surveying, and civil works, deliverables affect design, construction, as-built control, and quantity estimation; when accuracy concerns remain, adoption stalls.

A frequent situation is: “Drone surveying is fast, but it’s unclear how much we can trust it.” If proponents emphasize efficiency while cautious stakeholders point to accuracy risks, discussions tend to stop. In reality, while drone surveying is effective in many situations, the stability of results depends on targets, terrain, vegetation, shooting conditions, ground control, and analysis settings. In other words, it is not a binary question of usable or not; you must determine which applications require what accuracy level.

One reason accuracy concerns halt adoption is ambiguity in the comparison target. For example, the meaning of required accuracy differs if the drone is used for general situational awareness, auxiliary as-built verification, or final reference values. If you lump these together as “drone surveying raises accuracy concerns,” it is natural the response will be cautious.

The countermeasure is to organize expected accuracy per intended use. First, list the situations in which you want to use drone surveying and clarify purposes such as “overview,” “progress comparison,” “volume estimation,” “drawing-support,” or “detailed inspection.” Then separate locations that require ground verification from those where aerial assessment suffices. This approach allows you to use drone surveying without over- or under-valuing it.

Moreover, internal verification should not stop at data acquisition; always compare drone results with existing surveying results and on-site checks. In the early stage, do not rely solely on the drone. Compare it against ground control points and check points to reduce internal unease. What cautious stakeholders want to know is less “is it theoretically okay?” and more “how usable is it at our sites?” The answer comes only from comparative verification at limited sites.

The value of drone surveying is not in completely replacing ground surveying but in combining the speed of aerial overview with the certainty of ground checks. The countermeasure for accuracy concerns is to stop treating it as universally applicable and instead organize roles by application.

Reason 4: Operational burden is unclear and it looks like “post-adoption will be troublesome”

A frequently overlooked reason adoption stalls is perceived operational burden. Pre-adoption considerations tend to focus on shooting and deliverable presentation, but what really becomes an issue internally is whether the operation can be sustained. If post-adoption preparations are heavy, there are many check items, data organization takes time, or the results require human interpretation, initial enthusiasm will fade and the practice will not take root.

Especially for tasks with site-specific varying conditions, decision items tend to increase each time. Considering weather, surrounding environment, safety measures, shooting area, landing spots, stakeholder coordination, and storage and sharing after acquisition places a significant burden on responsible staff. When this becomes visible, field and administrative sides think “it looks convenient but won’t be manageable within regular work,” and become cautious about adoption.

Also, drone surveying does not end with on-site flight. If the purpose of the data is not clear, extra effort will be needed for processing and sharing. For example, if it is not decided in what format to share with stakeholders, who will check it, and when to use it for decision-making, the acquired data may end up unused within the company. Companies with such an experience become more cautious about subsequent adoptions.

The countermeasure is to simplify the operational flow in advance. Concretely, standardize which tasks will use drones, what to check before going to site, where the data goes after acquisition, and what decisions it will inform. In other words, design from a task-centric rather than aircraft-centric perspective. This reduces the feeling of “too many things to think about every time.”

Furthermore, do not expand usage too broadly during the initial phase. While it is attractive to say it can be used for current-condition checks, volume estimation, and progress management, broad usage increases operational complexity. Start with one or two tasks, fix procedures and roles, and it will be easier to establish. Technologies that stick in organizations are those with repeatable procedures rather than just being convenient.

Countermeasures for operational burden should not rely on enthusiasm. The shortcut to adoption is to narrow target tasks so anyone can maintain an acceptable standard, standardize procedures, and clarify where deliverables are passed.

Reason 5: Unclear usage image leads to “even if we adopt it, we won’t make full use of it”

Companies where internal adoption stalls often exhibit the state of “it seems good somehow, but we don’t know how to use it in our company.” This is a problem of unclear usage image. Although drone surveying is widely known as a term, if you cannot visualize how it maps onto your workflows, adoption decisions easily stall.

For example, field staff may expect overall understanding of slopes and development sites, daily progress records, or checks of access and temporary works. Management, however, may feel “will that really aid site decision-making?” or “isn’t it just adding more photos?” This temperature difference tends to occur when you have not concretized use cases before adoption.

Also, the broader proponents describe “it can be used in many ways,” the more cautious stakeholders become wary. That is because overbroad use cases often fail to deeply affect any single area. In practice, it is more important that concrete value emerges in specific tasks than that a tool can be used widely.

A countermeasure is to view your workflows and first clarify where the pain points are. If there are issues such as frequent site visits for on-site checks, time-consuming preparation of explanatory materials for stakeholders, slow overall understanding on large sites, or repeated corrections in as-built or volume checks, you can more easily find connections with drone surveying. When advancing adoption, talk not about “what it can do” but about “which problems it reduces.”

To propagate the usage image internally, you need to show not just deliverables but how they are used in business decisions. Even if you obtain aerial images or point clouds, if it’s not clear how they relate to meeting discussions, as-built volume checks, revision of construction plans, or explanations to clients, the value will not be conveyed. Conversely, if you convert them into concrete effects such as shorter meetings, fewer site revisits, and reduced misunderstandings, cautious stakeholders will be more receptive.

Countering unclear usage image is not about increasing technical explanations. It is about tying drone surveying to your operational pain points and clarifying at what scene, by whom, and for what decision it will be used.

Reason 6: Large differences in interdepartmental perceptions prevent internal agreement

Another major reason adoption stalls is differences in perceptions among departments. Field operations, surveying, construction management, design, IT, general affairs, and executives each emphasize different points, so even when discussing the same adoption, conversations can fail to align.

Field staff emphasize usability and safety, surveying staff evaluate accuracy and deliverable validity, administrative departments focus on cost and training burden, and executives worry about continuity and reproducibility. If any single department’s logic is pushed through to advance adoption, other departments may have concerns, and final approval can be stopped.

A common pattern is proponents saying “the field will get easier,” while cautious stakeholders respond “who will manage the workload and risks?” Both perspectives are valid. The problem is that evaluation axes are not aligned. Discussions of benefits and discussions of risks proceed separately, so no conclusion is reached.

The countermeasure is to create common evaluation axes for internal consensus. For example, organize adoption evaluation around viewpoints such as “safety,” “efficiency,” “accuracy,” “operational burden,” “continuity,” and “scalability,” and make visible which points each department emphasizes. This shifts discussion from simple for-or-against to constructive debate about “what conditions must be met to proceed.”

Also, involve related departments from the verification stage. If proponents test alone and then explain results later, other departments find it hard to view it as their own issue. If representatives from field, surveying, and management join the evaluation from the beginning, verification results are more easily shared internally. For cautious stakeholders, knowing their concerns are considered from the start reduces the tendency for outright opposition.

Interdepartmental perception gaps are not problematic because opinions differ; they are problematic because there is no common decision framework. Once that is established, adoption discussions are much easier to move forward.

If you want to advance internal adoption, think in terms of phased implementation rather than in-house vs outsourcing

A common debate in drone surveying adoption is whether to do it in-house or outsource. In practice, this dichotomy can actually stop adoption. If you aim for full in-house capability from the start, the burden looks large; conversely, if you outsource everything, concerns arise about not retaining know-how internally.

Phased implementation is effective here. Start small by narrowing target tasks and proceed while clarifying what to keep in-house and what to outsource. For example, handle on-site applicability decisions and deliverable utilization in-house while receiving external support for some flights or analysis at first to avoid excessive initial burden. As you gain experience, expand the in-house scope.

The advantage of this approach is lowering the failure risk. Trying to run everything internally at once makes training, equipment, rule establishment, and quality checks all become simultaneous challenges. Phased implementation lets you identify and improve issues one by one. It is also easier to build internal consensus and reassures cautious stakeholders by avoiding a sudden large start.

Phased implementation also fits well with budget applications. If you break phases into initial verification, full trial, and expansion of target tasks, you can confirm results at each stage before progressing. This creates a system of “expand while evaluating” rather than “buy and finish.”

In practice, phased implementation is the realistic method to promote internal adoption of drone surveying. Instead of making a binary decision on adoption, nurture it while finding where it is most useful.

Four perspectives to set up first to overcome internal adoption barriers

We have reviewed six reasons and countermeasures, but the order in which you set things up matters when you actually move internal adoption forward. If you jump into equipment or organizational discussions without organizing the debate, you will create confusion. To overcome adoption barriers, it is easier to proceed if you align four perspectives first.

First, narrow the adoption purpose. Rather than assuming “it can do everything,” clarify which operational issues you want to solve. The necessary setup and deliverables differ depending on whether the goal is current-condition assessment, progress sharing, or volume verification. Vague purpose prevents agreement on cost-effectiveness and accuracy.

Second, define success criteria. If you define in advance what outcomes will justify adoption, verification gains meaning. Translate into internal, measurable indicators such as reduced field time, fewer revisits, more efficient meeting material creation, or improved hazardous location checks.

Third, decide the role-sharing with ground operations. Do not assume drone surveying will stand alone; clarify what is seen from the air and what should be confirmed on the ground. When this is clear, accuracy concerns and operational burden are easier to reduce.

Fourth, clarify responsibility ranges. If it is unclear who will promote adoption, who will evaluate deliverables, and who will convert them into operational use, verification will not lead to the next step. Make minimal role assignments visible rather than concentrating responsibility on one person.

If these four are in place, discussions about budget, organization, accuracy, operations, and interdepartmental coordination are easier to organize. Conversely, without clarity here, even the most attractive proposals tend to stall internally.

Common mindsets of companies that successfully establish drone surveying

Companies that successfully advance internal adoption share several traits. One is that they position drone surveying not as a standalone new technology but as a means to improve existing operations. In other words, “using drones” is not the objective; the objective is operational outcomes such as “speeding up on-site decisions,” “making hazardous location checks easier,” or “reducing misunderstandings among stakeholders.”

Another common trait is incorporating cautious stakeholders’ concerns early. By including accuracy, operational burden, training, and continuity as verification items from the start, it is easier to gain internal trust. Proponents need enthusiasm, but enthusiasm alone cannot create consensus. Incorporating cautious viewpoints often accelerates adoption.

Additionally, successful companies distinguish between “what is visible from the air” and “what is verified on the ground.” They assign the aerial overview to capturing the whole picture and ground checks to capturing precise locations and details. This mindset reduces both excessive expectations and unnecessary distrust.

The key to establishment is avoiding the view of drones as万能 (all-purpose). Use them reliably in the right situations. Practical adoption that integrates into daily work with feasible procedures, rather than flashy use cases, produces sustained results.

Summary

The reason internal adoption of drone surveying stalls is not simply because it is a new technology. Practical and natural concerns—difficulty budgeting, personnel shortages, accuracy worries, unclear operational burden, unclear usage image, and interdepartmental perception gaps—accumulate. Therefore, to advance adoption you must answer those concerns one by one rather than dismiss opposition.

Particularly important are narrowing adoption purpose, defining success criteria, not framing the choice as in-house versus outsourcing, and organizing the roles of aerial overview and ground verification. Drone surveying is effective at speeding wide-area situation understanding, progress checks, and stakeholder sharing, but making it truly usable on-site requires operations that combine ground verification and high-precision positioning.

In practice, start by using drones to grasp the whole site and then accurately secure necessary locations on the ground to balance efficiency and certainty. Connecting wide aerial perspectives with reliable ground positional information makes adoption effects more realistic. When designing such operations, options such as LRTK, an iPhone-mounted GNSS high-precision positioning device, should be considered. Thinking of drone surveying not as a standalone tool but in combination with ground high-precision positioning to design the overall workflow is a practical step to move internal adoption forward.