Can Beginners Adopt Drone Surveying? 4 Common Stumbling Points

Table of Contents

• Can beginners implement drone surveying?

• Reasons why beginners often stumble at first

• Four common pitfalls

• How Beginners Should Proceed to Ensure a Successful Implementation

• Building a system that reduces on-site failures

• Summary

Many people in charge are interested in drone surveying but feel anxious about whether they can truly use it effectively on their own sites. While there is an expectation that it could improve efficiency compared with traditional surveying, it also looks like there is a lot to learn — aircraft operation, flight preparation, shooting conditions, data processing, checking deliverables, and so on. Especially in civil engineering, construction, land development, and maintenance projects, simply being able to fly the drone is meaningless; you must prepare the data so it can ultimately be used for on-site decision-making and construction management. For this reason, when beginners consider adoption, it is often even harder to see where to start.

But to get to the point, drone surveying can be implemented even by beginners. The difficult part is trying to handle everything perfectly in-house from the very start. In drone surveying, it is more important to assemble appropriate procedures tailored to the object you want to measure than it is to focus on the flight itself. Conversely, if you grasp the thinking behind the purpose, scope, required accuracy, deliverables, and operational setup, the hurdles to adoption drop significantly. What beginners truly need is not to memorize advanced technical terms, but to know in advance where failures are likely to occur.

In actual field operations, even after preparing the aircraft and performing test flights, problems often arise: the expected accuracy is not achieved, the captured images cannot be processed properly, the desired deliverables cannot be produced on site, or only one person understands the system so continuous operation is impossible. These failures are caused less by beginners than by starting with an unclear design at the time of introduction. If the initial design is carried out carefully, even beginners can make it sufficiently practical.

This article explains in detail an approach for introducing drone surveying without undue strain, aimed at operational staff who are planning to adopt it, while outlining four common pitfalls that beginners tend to encounter. Rather than offering abstract judgments such as “difficult” or “easy,” it delves into why those pitfalls occur, how they can be avoided, and what is required to translate the approach into on-site operations. It should serve as an easy-to-use basis for decision-making for those preparing internal proposals, those who want to switch from outsourcing to in-house work, and those who want to try it out on small-scale sites.

Can beginners adopt drone surveying?

The realistic answer to the question of whether drone surveying can be adopted by beginners is that it can be introduced, but if the initial approach is wrong it will be difficult to make it stick. Here, "beginners" refers to personnel who have never operated drones in full-scale surveying operations, or who have experience in photography or aerial shooting but not in operations that handle survey deliverables. Even in such positions, it is entirely possible to introduce drone surveying by narrowing the target sites, clarifying the required deliverables, and conducting phased trials.

The reason it can be introduced is that drone surveying work becomes easier to understand when broken down into smaller steps. Broadly speaking, the workflow is: defining the objective, checking site conditions, planning the flight, conducting photography or measurements, processing the data, reviewing the deliverables, and applying them on site. This workflow itself is easy to organize, and by addressing the key points in each stage you can improve reproducibility. If beginners avoid tackling large-scale projects or sites with stringent accuracy requirements at the outset, they can steadily accumulate sufficient experience.

On the other hand, implementing a system and being able to use it immediately are different things. Confusing the two will lead to failure. Many site personnel tend to think that once they learn how to operate the drone they can implement it, but what matters in practice is which decisions the collected data will be used for. For example, whether you want to use it for as-built verification, for calculating earthwork quantities, or for recording progress will change the required accuracy, the capture method, and the deliverables. Even if you only learn how to operate it, if you cannot acquire and process the data appropriately for the intended use, you ultimately won't be able to use it on site.

Another reason beginners find drone surveying difficult is that its connection to existing workflows is not obvious. On site, surveying itself is not the objective; its value only becomes apparent when it leads to subsequent tasks such as design verification, as-built confirmation, quantity estimation, report preparation, and consensus building. However, in the early stages of adoption attention tends to focus on flying and image processing, and consideration of how to integrate it into existing workflows is often postponed. As a result, it is easy to end up in a situation where data was collected but business processes did not change.

What is important for beginners is to view drone surveying not as the introduction of new equipment but as an effort to rethink the ways of acquiring site information. By deciding in advance what you want to visualize on site, who will use it, how often you want to update it, and in what format you want to store it, the necessary operations will naturally be narrowed down. In other words, whether beginners can adopt it depends greatly not only on technical level but also on how clearly they organize the purpose of the implementation.

Reasons Beginners Commonly Struggle at First

The main reason beginners stumble with drone surveying is that the many things it can do actually make decision-making more difficult. The appeal of being able to record an entire site from the air is very strong, but conversely it's easy to proceed with unclear assumptions about how much accuracy is required, what deliverables should be produced, and how much should be handled in-house. The more options there are, the more beginners are left wondering “what criteria should I use to decide?”

Another major mistake is thinking of aerial photography and surveying in the same way. Shooting attractive aerial footage or overhead photos and acquiring data for surveying with positional accuracy in mind may look similar, but they require different approaches. In surveying, you must carefully ensure elements that directly affect the consistency of results—overlap, flight path, altitude, condition of the target, handling of control points, correction information, processing parameters, and so on. Beginners in particular tend to judge only by whether they managed to capture images, and often lose sight of whether the data are actually usable.

Moreover, underestimating the impact of field conditions is another common stumbling block. Because drone surveying is outdoor work, it is greatly affected by wind, sunlight, terrain, obstacles, the surrounding environment, ground surface conditions, and occlusion from trees and structures. Unlike tasks that can be completed solely by operating software indoors, results change depending on site conditions, so beginners are likely to encounter situations that do not go as expected. If these variable factors are not incorporated during the preparation stage, a single failure can make them feel that “after all, it’s difficult.”

Another issue that cannot be overlooked is insufficient understanding within the company. Even if the person in charge of implementation is positive, use will not spread unless site managers, administrative departments, construction staff, and designers share an understanding of the role of drone surveying. Even if measurements are taken, if the deliverables do not match the information and formats the recipients want, they will eventually go unused. Beginners tend to stumble not only because of the technology, but because planning that includes how to use it across the organization is often lacking.

That's precisely why, at the outset, the important thing is not to try to understand all the difficult technical details. Instead, address the points most likely to cause failure first, narrow the initial scope of deployment, and aim for small successes. In the next chapter, we will take a detailed look, from the perspective of on-site implementation, at four points where beginners are particularly likely to stumble.

Four Common Pitfalls

The first is starting without a clear purpose for the introduction

What beginners most often stumble over is starting to consider adopting drone surveying without a clear understanding of why they are doing it. Motivations such as “it’s a hot topic within the company,” “other firms are using it,” or “it seems like it could improve efficiency” are natural entry points, but by themselves they won’t lead to successful operational implementation. If the purpose is unclear, the required accuracy, the scope of targets, and the deliverables won’t be determined, and as a result you end up choosing an operational approach that is more complex than necessary.

For example, if the purpose is to check current site conditions, the first requirement is to record the entire site at a consistent quality so that changes can be tracked. In this case, capturing under the same conditions each time and producing outputs that are easy to compare are important. On the other hand, if the goal is to estimate earthwork volumes or verify as-built conditions, managing positional accuracy and processing parameters becomes more important. Even in drone surveying, priorities differ completely depending on the objective. If a beginner starts without clarifying this, discrepancies will arise between site expectations and actual results.

Also, when the objective is vague, the evaluation criteria become vague as well. Whether success is judged by having been able to fly, by having been able to produce point clouds or orthophotos, or by having been able to use the results for on-site decision-making will change whether the implementation is deemed successful. Beginners are more likely to be satisfied with intermediate steps and may not reach an awareness of the ultimate business value. However, in actual operations it is important that outcomes be visible in forms such as reduced time spent preparing documents, fewer site visits, or having documented the basis for quantity calculations.

To avoid this stumbling block, clearly verbalize at the outset "which tasks will be replaced," "which decisions you want to make easier," and "who will use the deliverables." For example, if you can concretize the intended use to the level of "want to use it for monthly progress records," "want to use it for pre- and post-construction comparisons," or "want to use it to monitor changes in embankments and excavations," it becomes easier to see the necessary operations. In the initial phase of implementation, it is more important to achieve reliable results in one task first than to broaden the range of uses.

Furthermore, for beginners it is important not to expect all-in-one capabilities from the outset. Drone surveying is versatile, but trying to achieve everything on the first site increases the amount of preparation and checks and makes failure more likely. It is more realistic to start with relatively easy-to-adopt uses such as recording current site conditions, sharing progress, and simple quantity comparisons, and to gradually expand into tasks that require higher accuracy. If the purpose of adoption is clear, even beginners can focus on the necessary scope.

The second is taking flight and data acquisition too lightly.

In drone surveying, the step of flying the aircraft to capture photos and point clouds is the most visible, so beginners tend to assume that “once you get used to it, you’ll be fine.” However, in reality, designing data acquisition with survey-quality requirements in mind is more difficult than the flight itself. If you take this lightly, you will end up with more data that is unusable despite having flown.

The first thing to address is planning the image capture according to the site conditions. Whether the subject is flat or undulating, whether there are many structures or many trees, and whether the site is confined or wide-area will change the appropriate altitude and route planning. Beginners tend to focus mainly on aircraft performance and flight time, and often overlook perspectives such as how to shoot the target to make processing easier, reduce data gaps, or produce data that is easy to compare.

Also, the effects of weather and ground surface conditions cannot be overlooked. Strong winds can affect the aircraft’s stability and image quality, sunlight conditions can change how surfaces appear, and after rain or in muddy conditions the state of the ground itself differs from normal. Furthermore, the quality of information that can be obtained varies greatly between periods when vegetation is dense and after mowing. Even if a novice attempts to achieve ideal results in a single flight, they may be unable to fully anticipate changes in field conditions, resulting in greater variability in outcomes.

Additionally, for surveying purposes it is important to acquire data at the same quality every time. If used for progress management or comparison, inconsistent results—such as one day covering a wide area but another day having many gaps, or one day having high resolution but another being coarse—make continued use difficult. What beginners often overlook is that being able to reproduce the same results stably using the same procedure is more important than performing a single good flight. When deploying on site, procedures will not take hold unless they are operated in a way that maintains a consistent standard even when personnel change.

To avoid this stumbling block, don’t treat flight as an individual skill from the outset. For each target site, even if only briefly, organizing the capture area, reference altitude, flight-path strategy, checklist items, and criteria for deciding whether to retake shots will make it easier for beginners to stabilize quality. Also, rather than relying solely on the first live site, it is effective to run trial operations in relatively favorable conditions, review the acquired data, and then proceed to full implementation. It is important to understand that being able to fly and being able to achieve survey-quality results are separate things.

The third is that they cannot visualize the process and the deliverables.

Another major reason beginners struggle with adoption is that they start with flights without a clear picture of post-acquisition processing and the expected deliverables. On site, imaging and measurement are merely the entry point. What is truly needed are deliverables that have been processed and organized into a form usable in operations. If you proceed with adoption while leaving this vague, you can end up with data but no clear use for it.

The information obtained from drone surveying is varied: aerial images, sets of geotagged images, point cloud data, terrain models, images arranged for easy planar viewing, and shape information that can be used to check cross sections, among others. However, for beginners it can be difficult to understand what each is best suited for. Those suited for on-site inspection, for quantity estimation, for explanatory materials, and for comparison with drawings each have slightly different characteristics. If you produce deliverables that do not match the intended purpose, they will not lead to the expected use.

For example, bird’s-eye, easy-to-understand deliverables are helpful for sharing site conditions, but evaluating subtle elevation changes or earthwork volumes requires data organized in a different way. If you want to compare before and after construction, it is essential to collect data to the same standard each time and prepare it so it can be overlaid and easily viewed. If you want to compare against the design, you also need to handle alignment and coordinate conventions. If beginners overlook the processing steps, something that appeared fine at the time of flight may later turn out to be impossible to produce what was needed.

Underestimating the processing load is also a common stumbling block. Data processing can take time, and you need to distinguish between what must be checked quickly on site and what should be carefully refined during post-processing. Beginners tend to think that once the flight is over they will immediately have results, but in reality there are a number of unglamorous yet important steps that follow, such as organizing data, verifying it, handling unnecessary portions, and making adjustments for comparison. If you don't allow leeway here, operations will not run smoothly after implementation.

To avoid this issue, it is important to clarify, before implementation, exactly what you ultimately want to deliver to the field and in what format. If you define in advance the deliverables required for each purpose—images for progress sharing, comparative data for earthwork volume assessment, shape data for design verification, visualization materials for reports, etc.—it becomes easier to determine how to plan flights and data acquisition methods. For beginners to succeed in implementation, deciding on the outputs before flying is indispensable.

The fourth is leaving it to the person in charge without creating a structure for ongoing operations.

One thing that is surprisingly often overlooked when onboarding beginners is building the organizational structure. At first, a motivated person often drives the effort, so the initial rollout may appear smooth. However, if operations rely on a single individual, continuity will break down when they become busy, are transferred, or have other responsibilities that overlap. Drone surveying gains more value from regular use than from one-off projects, so an inability to sustain ongoing operations is a significant loss.

A common problem when tasks are left to individual staff is that know-how becomes tied to specific people. If information such as where and how something was flown, under what conditions data were acquired, and which deliverables were handed to which departments remains only in the responsible person's head, reproducibility declines. For beginners in particular, recording trial and error is important, but if those records aren't shared they will repeat the same mistakes. As a result, the work becomes "work that cannot be done without the person in charge."

Also, in continuous operations, not only the flight personnel but also those who receive the deliverables need to understand. If stakeholders such as construction management, design, sales, and administrative departments do not share how they will use the results of drone surveying, the data that was produced will not be utilized. For example, if you want to use it for progress sharing, you need to align with others on what timing and in what format you want the data. When introducing to beginners, attention tends to focus on technical training, but in reality the operational design on the recipient side is just as important.

Furthermore, in the early stages of implementation, there are cases where organizations become exhausted trying to handle everything in-house. If a single person is responsible for flight, processing, verification, reporting, storage, and reuse, the workload will naturally be high. Beginners tend to try to do everything out of a sense of responsibility, but in reality it is necessary to separate what the site handles, what is standardized, and what is supplemented by a support system. If you start without a proper structure, it may run temporarily but will not last.

To prevent this stumbling block, establish a minimal set of operational rules. Decide who will make flight decisions, who will check the deliverables, where outputs will be stored, how to record site-specific settings, and what information will be needed for future comparisons — merely deciding these matters can greatly affect how easy it is to maintain the practice. For beginners to adopt it without strain, it is more important to build a sustainable process than to prioritize mastering advanced technical skills.

How Beginners Should Proceed to Successfully Implement

To succeed in drone surveying as a beginner, it's important not to aim for the ideal setup from the outset. Common mistakes during the introduction include trying to tackle a large site, complex terrain, high-accuracy requirements, and multiple deliverables at once. These place a heavy burden even on experienced operators, and for beginners there are too many potential causes of failure. It's realistic to first narrow the intended use, work on sites with favorable conditions, and begin with relatively straightforward deliverables.

We recommend setting the initial deployment target to tasks where benefits are relatively easy to perceive, such as current-condition recording or progress sharing. These are characteristics that make it easier for stakeholders to understand the outcomes and for the value of the implementation to be communicated. If results are visible early in the deployment, internal buy-in will increase and it will be easier to expand to additional use cases. Rather than immediately taking on operations with demanding accuracy requirements, it is better to first create a success experience by visualizing the field, which leads to sustained operation.

The next important step is small-scale standardization. You don't need to create complicated manuals, but if you briefly organize the on-site inspection workflow, pre-shoot checklist items, post-capture inspection points, and rules for storing deliverables, even beginners will find it easier not to get lost. Much of the confusion during rollout arises from the absence of clear decision criteria. For example, if it's decided how severe a defect must be to warrant retaking, which format to use for sharing, and what to keep for future comparisons, you can reduce individual variation.

Separating trial operations from actual operations can also be effective. If you evaluate only at the actual site from the start, you may not be able to perform sufficient verification due to weather or process constraints. First, conduct a test flight, check the acquired data, and, if necessary, review the conditions—experiencing this sequence once will reduce anxiety during actual operations. For beginners to start operating with confidence, it is ideal to have an environment where they can learn in a setting where failures have minimal impact.

Furthermore, it is important to adopt the perspective of judging the success of an introduction not by whether it was merely "deployed" but by whether it was "usable." If you evaluate from viewpoints such as whether deliverables that are useful on site were produced, whether you obtained a realistic outlook on the required work time, and whether stakeholders' understanding advanced, it becomes easier to identify areas for improvement. Beginner implementations are not something to be completed in a single attempt; they are refined through operation to improve accuracy and efficiency. Proceeding on that premise will prevent it from feeling unduly difficult.

Building a System That Is Less Likely to Fail on Site

To make drone surveying easy for beginners to adopt, creating a system that does not rely on individual effort is indispensable. By "system" here I do not mean large-scale organizational changes, but rather a minimum division of roles and mechanisms for sharing information. Even in small companies or on sites with few personnel, simply being mindful of such a system can greatly change how easily it becomes established.

First, what you should be aware of is separating the perspectives of the flight team and the utilization team. In practice the same person may take on both roles, but conceptually it is easier to make improvements if you separate the perspective of acquiring data from the perspective of using it in operations. Even if flights go well, if the deliverables are difficult to use on site they need improvement; conversely, if the desired deliverables are clear, it becomes easier to identify points for revising the acquisition method. This separation of perspectives is especially effective when introducing the system to beginners.

Next, keep records. If you briefly note which site, under what conditions, for what purpose, and what deliverables you produced, reproducibility will be higher next time. Especially at the beginner stage, not only successful cases but also conditions that failed are important assets. If you record the weather, ground surface conditions, imaging coverage, problems after processing, and so on, experience will accumulate within the organization. Without this, you will have to make decisions from scratch each time.

Also, it’s important to have a venue for internal sharing. It doesn’t necessarily have to be a large meeting, but having opportunities to share post‑implementation results and issues with stakeholders makes it easier to gather requests from the field. For example, if administrators prioritize progress comparisons, construction personnel want to see changes in height, and sales want overview materials for explanations, the direction of implementation becomes clearer. Rather than having beginners work in isolation, involving the end users makes success more likely.

It is also important to organize the handling of location information on-site in a way that is practical. In drone surveying, practical value comes not only from being able to see shapes but from correctly determining where they are. To link and use site photographs, point clouds, drawings, as-built measurements, and construction records, an approach for stabilizing positional references is necessary. For beginner onboarding, first putting in place a method for capturing location information that is easy to handle on-site will greatly change the usability of downstream processes. If this is left ambiguous, even data that has been carefully acquired will become difficult to use for comparison and overlay.

Summary

Drone surveying can be adopted even by beginners. However, it is not as simple as preparing a drone and flying it to start using it immediately. Common pitfalls are starting with unclear implementation objectives, underestimating the complexity of flight and data acquisition, not planning for processing and deliverable outputs, and leaving everything to the person in charge without establishing a system for continuous operation. Simply understanding these four points in advance can significantly reduce the likelihood of implementation failure.

What’s important for beginners is not to try to tackle difficult things all at once. Start by narrowing the use case, test on small sites or sites with favorable conditions, and realistically increase the number of deliverables that are truly usable on site, one by one. Rather than rushing implementation, carefully establish the operations needed for the objective; this will ultimately lead to faster adoption. Only when it becomes a system used on site will drone surveying demonstrate its power to improve efficiency and visualization.

Also, for practical use, it is important not only to acquire data from the air but also to connect it with ground-based positional information. While aerial data can be captured broadly and quickly, what is needed on site are on-site verification, alignment with existing drawings, confirmation of as-built conditions, and coordination with additional measurements. When these elements are connected, drone surveying becomes more than a mere recording tool and serves as a foundation for construction management and information sharing.

In that sense, when beginners introduce drone surveying it is effective to have not only flight skills but also an approach for making positional information easy to handle on-site. For example, in situations where you want to quickly capture required points on the ground, link aerially acquired data with on-site verification, or expand operations to be conscious of drawings and coordinates, combining an iPhone-mounted GNSS high-precision positioning device like LRTK can make early-stage operations easier to organize in a more practical, field-oriented way. If you want to introduce drone surveying on-site without placing undue strain on beginners, thinking of aerial acquisition and high-precision ground position checking as an integrated process is a less failure-prone way to proceed.