5 Tips to Streamline As-Built Surveys with RTK

When aiming to improve the efficiency of as-built surveys, many people first focus on "how can we measure faster." Of course, shortening travel time and observation time is important. However, in field practice, efficiency measures that truly work go beyond simply speeding up. Reducing rework—such as coordinates not matching after measurement, discovering missed observations, losing attribute information during drafting, or unstable communications that prevent obtaining a fix—ultimately leads to much greater time savings.

RTK in particular allows immediate acquisition of coordinates, but if reference checks are insufficient or observation conditions are overlooked, it’s a method that—despite appearing to go smoothly on site—tends to cause problems in later stages. That’s why, to operate it efficiently, you need to have your approach organized before you take the equipment out to the site. In as-built surveys there are many items to capture—terrain undulations, roads and boundaries, structures, drainage-related features, manholes and inspection chambers, slope shoulders and slope toes, pavement edges, locations of existing features, and so on—and their priorities change from site to site. If you proceed in an ad hoc manner here, the more you have to measure, the more mistakes you will make.

In this article, we organize and explain five practical tips for streamlining on-site surveys with RTK. From five perspectives—preparation, observation order, verification of known points, communications and satellite environment, and data organization—we explain methods to consistently achieve results while reducing re-measurements and revisits, rather than simply measuring faster. The content is organized to be easy to understand for those who are just starting to use RTK and to provide review hints for those already operating it.

Table of Contents

• During the preparation phase, first settle what to measure and to what extent.

• Design the observation sequence to reduce travel loss and missed measurements

• Do not omit verification of known points; ensure the reliability of the coordinates first.

• Conduct observations within safe limits while monitoring communications and the satellite environment.

• Organize data on-site to lighten downstream processes.

• Summary

During preliminary preparation, decide first what to measure and to what extent

When using RTK to make as-built surveys more efficient, the first thing to review is the pre-survey preparation. Many people think it’s fine to decide things after arriving on site, but in reality the time spent worrying on-site is often the most wasteful. If you enter the field with vague answers to where to measure, what to reflect in the deliverables, and what level of accuracy is required, observations may proceed, yet you’ll later face situations like “this is missing,” “that point was unnecessary,” or “we can’t use it because its attributes are unknown.”

The subject of an as-built survey is not simply taking a lot of points. What is required is to collect points that can be used in downstream processes, at the necessary density and with meaningful annotation. For example, around roads you should prioritize capturing locations that affect drafting and design: pavement edges, gutter tops, gutter bottoms, curbs, change points near the road centerline, the top and toe of slopes, corners of structures, boundary markers, driveway entrances, and so on. Conversely, placing excessive points on straight sections with little geometric change increases time on site while hardly improving the quality of the deliverables.

In preparation, first review drawings, aerial photographs, past results, and on-site photos, and organize in advance which targets to record. At this stage, deciding observation policies such as "prioritize terrain change points," "use separate naming rules for locations related to boundaries," and "be mindful of elevation control for drainage systems" will make on-site decision-making significantly faster. Because beginners are more likely to hesitate over each decision on site, it is effective to document and share the approach to selecting observation targets in advance.

Also, it is important not to let equipment preparation end as a mere checklist of items. You need to confirm in advance not only the presence of the receiver unit, controller, batteries, communication terminals, pole, spike, tripod, backup power, etc., but also the coordinate system to be used, geoid settings, the source for correction information connections, data storage format, point naming rules, and code entry methods. If any of these are insufficiently checked, it can lead to a critical mistake in which it appears measurements were taken correctly on site, but the settings were actually different.

Furthermore, from an efficiency standpoint, it is also useful to decide the "on-site work units" in advance. For example, deciding whether to complete a pass on the right side of the road before moving to the left, whether to survey structures first and then capture the terrain, or how to combine planimetric and elevation information makes the work more streamlined. If multiple workers are present, clarifying who checks what and who performs the final verification of the records reduces on-site verbal communication and the number of confirmations.

The essence of preparation is not to reduce on-site decision-making to zero. It is to reduce the number of decisions required on site and to improve the quality of those decisions. Precisely because RTK is highly mobile, work can often proceed even when preparations are lacking. However, the more a job proceeds in a haphazard way, the more rework will be required. If you want to improve efficiency, the first step is to clearly determine what to collect, to what extent, and how before entering the site.

Design the observation order to reduce travel losses and missed measurements

In RTK surveying of existing conditions, it's movement and setup changes—not the observations themselves—that are most likely to cause time loss. Especially on sites with a wide coverage area, increased walking distances, overlooked observation targets, and repeated trips to the same locations compound and greatly inflate working time. Therefore, if you want to improve efficiency, you must design the observation sequence itself rather than decide how to move after arriving on site.

A common mistake is to measure things in the order they catch your eye. For example, if you measure a structure near the entrance, then move to a distant boundary point, stop to measure a drainage ditch you noticed along the way, and then head to another structure, the number of measurement points may increase but the site workflow becomes fragmented. With this approach you end up returning to the same area repeatedly and are more likely to miss measurements. Moreover, because it becomes harder to keep track in your head of what has been completed, rechecking takes more time.

To prevent this, it is important to think of the observation sequence in terms of areas. Divide the site into several zones and proceed with the mindset of completing each zone before moving on; this reduces movement loss and makes it easier to spot omissions. For example, on a roadside site, measuring continuously one side at a time is effective. It is more efficient to cover the pavement edge, gutter, structures, slope changes, and boundary-related features on the right side of the road in one direction, then turn back to handle the opposite side, rather than constantly going back and forth between left and right.

Also, the order of observations should be adjusted according to the nature of the objects. Securing points that form the skeleton of the deliverables early on—such as boundary markers, known points, and corners of reference structures—stabilizes the subsequent overall work. On the other hand, it is easier to maintain an overall perspective if fine terrain variations and supplementary information are added after the main framework has been established. The idea is to first secure the overall frame, then fill in the details.

Furthermore, when designing the observation sequence, it is important to eliminate workflows that "assume you'll go back." On site, people tend to plan to add items they notice are missing later while measuring, but when these "later" tasks accumulate, revisits to the same locations increase. Therefore, in practice it is effective to develop the habit of completing all necessary checks for a section before finishing that section. For example, after completing each road section, quickly review the sequence of acquired points to check for unnatural gaps, missing elevations, or missing corners of structures. Spending just a few minutes doing this can greatly reduce the rework of "why isn't this here?" when back at the office.

In field surveying, it is more important to ensure that the necessary locations are covered adequately—no more and no less—than to simply increase the number of observation points. To achieve this, you need to consider the order in which you walk the site and the sequence of targets to be measured as an integrated whole. An efficient site has no wasted steps for the workers and a clear flow in the survey data. Conversely, an inefficient site shows hesitation in walking patterns and greater variability in the data. A key to using RTK effectively is not just measurement skill but also the ability to design the walking sequence.

Do not skip verification of known points; ensure the reliability of the coordinates first.

When conducting a field survey with RTK, confirming known points is something you must not omit for the sake of efficiency. Especially for beginners, confirming known points can seem like a time-consuming step. However, in reality, the re-measurements and reprocessing that result from skipping this confirmation are a far greater loss. Efficiency is not about shaving off a few minutes now, but about reducing the risk of losing hours, or in some cases days, later.

Because RTK can display coordinates instantly, it is a method that easily gives the impression that the numbers are correct once values appear. However, if prerequisites such as the selection of correction information, coordinate system settings, consistency with known points, the geoid model, or the handling of localization are misaligned, the entire results can be shifted even when observations appear stable. This type of mistake is hard to notice on site and often only becomes apparent at the stage of drafting, overlaying with other data, or comparing with existing drawings.

That is why, once you enter the site you need to verify known points early on and check whether the current setup and the observations are consistent. What is important here is not to simply check a single point and assume “it seems correct.” If possible, confirm with multiple points and examine consistency not only in the horizontal direction but also in elevation. Especially in existing-condition surveys, because elevation information has a large impact on drainage gradients, structure heights, and slope geometry, you cannot be reassured even if the plan view matches.

There is another important purpose to checking known points: it allows the operator to grasp the observation conditions for that day. For example, signs such as taking longer than usual to obtain a Fix, needing to wait a little before the difference from the known point stabilizes, or slightly unstable communications can be noticed during the known-point check. If you pick up on these anomalies here, you can identify which points should be handled more cautiously throughout that day's observations. Conversely, if you continue observing while overlooking such anomalies, you may spread the problem across the entire site.

In practice, it is important not to treat verification of known points as a mere start-up ritual. Record the verification results and retain them as that day’s baseline; they will serve as a basis for judgment when reviewing the data later. Also, if you recheck as needed during the job, you will more easily notice condition changes or shifts in settings over time. For example, simply reviewing the baseline at milestones such as after the lunch break, after a battery change, or after relocating can help prevent unnecessary re-measurements.

In topographic surveys, the more points there are, the greater the impact a single reference shift has on the entire survey. If you prioritize efficiency, you should first firmly establish the reference. Verifying known points is not a detour but the most reliable shortcut. To make the most of RTK's speed, confirm the reliability of the coordinates upfront and then carry out observations in one sweep; this workflow leads to an efficient site with no need for re‑surveys.

Conduct observations within reasonable limits while monitoring communications and the satellite environment

RTK is a convenient method that enables high-precision positioning, but its performance is not always consistent. Because it is heavily influenced by communication conditions and the satellite reception environment, using it efficiently requires judging on-site whether "you can really get stable measurements at this location right now." Ignoring this and forcing observations to continue can cause problems such as failing to obtain a fix, unstable solutions, and varying measurements at the same point, which ultimately increases the need for re-measurements.

Especially on-site for surveys of existing conditions, there are many factors that affect the reception environment, such as proximity to buildings, tree branches and foliage, slopes and retaining walls, and the presence of heavy machinery or vehicles. Furthermore, when using network-based corrections, the condition of mobile communications also affects stability. In other words, for RTK it is not enough to judge only whether “the sky is visible”; you must also determine whether the necessary satellites can be stably tracked and whether correction data can be continuously received.

From an efficiency perspective, the important thing is not to linger too long in locations with poor conditions. For example, if you enter a spot near a building or under a tree where it’s hard to get a fix, waiting there for a long time will disrupt the overall work tempo. Moreover, the values you finally obtain may not necessarily be truly stable. In such situations, flexible judgment is required: first look for a nearby position where conditions are stable, change your approach to the observation target, or postpone the location and proceed from places with better conditions. An efficient worksite is not one that always takes the shortest route, but one that does not waste time in places with poor conditions.

Also, checking the communication status should not be overlooked. Even if communication is weak in just part of the site, reception of correction information may be delayed or the connection may be interrupted. Ideally you would grasp the overall communication trends of the area in advance, but in practice there are many situations where you proceed while checking on site. In that case, it's reassuring to check the communication status not only near the site entrance but also deeper into the work area and in locations with changes in elevation. Even if everything seems fine at first, it is not uncommon for the connection to become unstable once you go further in.

When evaluating the satellite environment, it is important not to judge solely by whether the number of received satellites is high. You need to determine the on-site reliability by comprehensively considering factors such as the stability of the position solution, the time to Fix, consistency with known points, and the results of re-observing the same point. In other words, rather than passively accepting the displayed values, you should take it upon yourself to judge whether those numbers are practically usable.

Furthermore, in practice it is effective to keep more detailed records for locations with poor conditions. For example, points observed near buildings, points that may be affected by trees, and points acquired after a communication dropout should be recorded in notes or attributes so they can be checked later, making it easier to make decisions during the processing stage. This prevents having to doubt and recheck everything and allows you to focus reviews only on the necessary locations.

Those who use RTK efficiently do not insist on the same procedure every time. They check the communications and satellite environment and adjust how they carry out observations to suit the day's site. This flexibility is the key to reducing unnecessary waiting time and remeasurements. Rather than sticking it out in locations with poor conditions, reading the conditions and proceeding smartly leads to more efficient field surveys.

Organize data on-site to ease downstream processes

In RTK as-built surveys, the work is not finished the moment the observations are completed. Rather, differences in efficiency tend to appear in the subsequent data organization. Even if you can measure quickly in the field, if, after returning to the office, you cannot identify point names, do not know what each point represents, cannot read the connectivity of alignments, or have different codes mixed for the same object, organizing and drafting will take extra time. In that case, the time saved in the field is simply lost in the downstream processes.

Therefore, to operate efficiently, it is important not to push data organization too far outside the field. In other words, be mindful of ease of organization while observing, and complete checks that can be done on-site. For example, simply standardizing how point names and codes are assigned can greatly affect how quickly the data can be read later. If you establish rules that make major categories—road edge, top of gutter, bottom of gutter, slope shoulder, slope toe, structure corners, boundary-related, etc.—identifiable at a glance, it will be easier to proceed with drafting and verifying point-cloud arrangements.

Also, in as-built surveys, not only the coordinate values themselves but also "what the point represents" are extremely important. Even at the same location, whether it is the top, the bottom, a corner or the center, a boundary marker, or a temporary position-check point changes the implications for the survey results. If this is ambiguous, you will have no choice but to rely on site memory later. But site memory fades far faster than you might imagine. That is precisely why assigning meaningful names and attributes at the time of observation is actually the most efficient approach.

Furthermore, it is also effective to make a habit of performing quick checks for each section. Rather than waiting until the end of the day to review everything at once, check the flow of acquired points, any omissions, duplicates, and any unnatural jumps in elevation each time you finish a given area. If you notice an anomaly at that moment, you can correct it by spending only a few extra minutes on site; if you discover it after returning to the office, a revisit may be necessary. Comparing a few minutes on site with half a day for a revisit makes it clear which is more efficient.

Improving the efficiency of data organization directly helps prevent re-measurement. For example, even if you think you have measured a row of structures on one side of a road, if you see a single blank spot on the organization screen you can take an additional observation on the spot. However, if you take the data back without confirming it on-site, you won't know whether that blank really meant there was no target object or that it was a missed measurement, leaving you unsure how to decide. Such hesitation itself is inefficient. Things that can be confirmed on-site should be completed on-site as much as possible.

Also, when multiple people are working, sharing rules for data organization becomes especially important. If different people use different conventions for point names or codes for the same object, integration work in downstream processes increases. If you are aiming for greater efficiency, you need to focus not only on measurement techniques but also on standardizing the organization rules. Teams that are fast on site are those that can produce data readable by anyone, not just teams that rely on individual skill.

RTK's major strength is its ability to acquire coordinates instantly on site. However, to truly capitalize on that strength, it is important not to separate observation from data organization. Simply measuring and stopping there does not lead to efficiency; only when results are preserved in a usable form does efficiency occur. If you want to improve the quality of as‑built survey results while also reducing work time, it is important not to postpone data organization but to advance it while still on site.

Summary

To make surveying of existing conditions with RTK more efficient, simply speeding up each individual observation is not enough. What matters is reducing waste across the entire workflow and creating a process that makes re-measurements and backtracking less likely. The five fundamentals for that are prior preparation, observation order, verification of known points, assessment of communications and the satellite environment, and data organization.

First, during the preparatory stage, it is important to clarify in advance what and to what extent you will measure, reducing the number of times you hesitate on site. Next, design the observation sequence to suppress walking losses and missed measurements. Furthermore, secure the coordinate reference by verifying known points, thereby ensuring the reliability of the entire observation. And, while checking communications and satellite conditions on site, avoid forcing things through and maintain the flexibility to change your approach according to conditions. Finally, by being mindful of data organization from the field, you can reduce the burden after returning to the office and improve overall efficiency through to the production of deliverables.

Efficiency in as-built surveying means not only shortening work time but also reducing hesitation. On sites where it is clear where to check, where to make decisions, and where to record, mistakes naturally decrease and outcomes become more consistent. Conversely, sites that proceed on an ad-hoc basis may seem faster at first, but the burden will inevitably return later.

If you want to leverage RTK for as-built surveying from now on, before trying to "measure faster" try focusing first on "ways of measuring that avoid having to go back." Prepare the steps in advance, proceed on site in an orderly sequence, verify your reference points, make observations sensibly according to conditions, and record with organization in mind. Once this workflow becomes second nature, RTK will be not just a convenient positioning method but a powerful tool for streamlining the entire site. Adapting it into a form that is easy to use in actual practice is the key to achieving the most reproducible efficiency.