Can RTK Be Used for As-Built Management? 5 Conditions to Check

When considering how to streamline as-built management, many field personnel wonder whether RTK can be used. This is because traditional surveying work takes time for setting out and verification, making staffing and schedule coordination burdensome. That has put the spotlight on RTK, which makes it easy to confirm coordinates on-site in real time.

However, to conclude, RTK can be used for as-built management, but it is not unconditionally usable at every site. Only when the required accuracy, site conditions, the way reference standards are aligned, operating rules, and methods for organizing results all fit together will it become possible to use it stably in practice. Conversely, if it is introduced while leaving those aspects ambiguous, even if you think you have measured, it will often be difficult to use the data as management values, hard to incorporate into reports, and prone to issues such as an increase in re-measurements.

In this article, we organize, from a practical perspective, whether as-built management can be performed with RTK and clearly explain the five conditions you should check before implementation. This is presented as useful content not only for those who want to know during the search phase whether RTK can be used, but also for those who have already started using it on-site and want to determine how far it can be used for management.

Table of Contents

• Can RTK be used for as-built management?

• Condition 1: The required accuracy and management tolerances are aligned.

• Condition 2: The coordinate system and the method of establishing reference points are standardized across the site.

• Condition 3: The radio environment and surrounding conditions are stable.

• Condition 4: Observation procedures and verification methods are codified into rules

• Condition 5 Ability to design operational processes that include organizing results and methods for recording them

• As-built management tasks RTK is well-suited for and those it is not

• Summary

Can RTK be used for as-built management?

RTK is a method of obtaining high positional accuracy by combining correction information with satellite positioning. It makes it easy to obtain coordinates on site and is well suited for tasks such as verifying point positions, checking construction locations, and comparing with specified dimensions. For this reason, it is by no means incompatible with as-built management. Rather, on sites that meet certain conditions, it has the potential to greatly improve work speed and the ease of verification.

However, as-built management is not simply a matter of obtaining coordinates. What is required is that measurements are made with appropriate accuracy relative to the control standards, that the measurements are reproducible, and that records are kept in a form that can be explained to anyone. On site, the objective is to compare the design values with the post-construction position and elevation and to verify their differences. Therefore, not only the accuracy of the positioning itself but also which reference standard, which procedures, and under what conditions the observations were made are extremely important.

A common misunderstanding here is the belief that because RTK is highly accurate, it can be used for anything. In reality, in locations where the required accuracy is extremely strict, where sky visibility is poor, or where measurements are prone to reflections, the expected stability may not be achieved. Also, even if horizontal positioning is easy to handle, there are situations where careful judgment is required for height management. In short, whether RTK can be used for construction quality control should not be decided solely by the performance of the equipment, but by the compatibility between site conditions and the management objectives.

In practice, rather than trying to complete everything solely with RTK, it is more realistic to distinguish between processes where RTK can be used as the primary method and processes where other verification methods should be used in combination. For example, while RTK is convenient for position checks on large sites, verification of control points, and checking representative points around slopes and structures, other methods may be more suitable in heavily obstructed locations or when confirming fine shape details. Making this assessment before implementation is the first step to avoiding failure.

Below, we will look sequentially at five conditions you should particularly verify to make RTK-based as-built management viable in practice.

Condition 1 Required accuracy and management tolerances are aligned

First, confirm whether the assumed accuracy of RTK matches the tolerances required for as-built management at the site. If this is unclear when introduced, measurements may appear valid in the field but cannot be adopted as management values.

In as-built control, you verify that completed structures and finished surfaces have been completed according to the design. For that reason, simply saying they can be measured to within a few centimeters is not sufficient. What is important is specificity about what you want to control in that process: plan position or elevation, a representative point or a continuous surface, and what the allowable tolerance is. For example, in some processes the focus is on checking plan direction and you need to quickly see relative positional relationships. In such cases, the mobility of RTK is a major advantage. On the other hand, when elevation control is strict and judging slight differences is important, a different level of care from that used for plan measurements is required.

What requires particular attention in practice is how height is handled. While RTK tends to perform well in determining horizontal positions, the vertical direction is more susceptible to being affected by site conditions and by alignment with reference surfaces. Because height often directly ties into quality evaluations in as-built management, it is dangerous to assume that correct horizontal positions can be used as-is for height control. When verifying height, it is necessary to confirm—by checking against known points, by repeated observations within the site, and by comparisons with other methods—that the precision actually achievable for that process is sufficient.

Also, what is required is not theoretical accuracy but accuracy that can be reproduced on-site. If values are stable in the morning but fluctuate in the afternoon, if results shift because observation times differ between measurers, or if the condition changes with only slight movement, the reliability as a management value decreases. Therefore, before implementation, trial operations should be carried out for each target process to confirm how much reproducibility can be achieved under actual working conditions.

Deciding whether to use RTK for as-built management cannot be based solely on the RTK performance table. You need to see whether there is enough margin for comparison with the design values, whether it produces stable results when repeated on site, and whether it has sufficient certainty to be incorporated into management forms; only then can you judge it usable. Do not leave the discussion of accuracy abstract—consider it primarily in relation to the allowable tolerances.

Condition 2 The coordinate system and reference procedures are standardized across the site

The second requirement is that the coordinate system and the way references are taken are standardized across the site. Even if numerical values are obtained by RTK, if it is unclear what those values are referenced to, they cannot be used for as-built management. This is a very common oversight in practice.

In as-built management, the designed positions are compared with the post-construction positions. For this, the design data, on-site reference points, the coordinates used for observation, and the numerical values recorded as deliverables must all be based on the same conventions. For example, even if the plan coordinates appear to match, if the interpretation of the reference origin or orientation differs, the comparison results become meaningless. The same applies to elevations: if the adopted reference surface is not consistent, the control values will be confused.

When RTK is brought onto the site, coordinates can be seen on the spot, so people tend to be reassured by the mere fact that numbers are produced. However, what is required for as-built management is not that coordinates are produced, but that they can be compared within the same reference frame as the design values. If this is misaligned, something that seemed correct on site can later be irreconcilable during data processing or when responding to inspections.

To meet these conditions, it is important first to organize the coordinate system and the management of reference points used on site. Clarify which known points will be used as references, where the control points for construction management will be located, and what should be checked before beginning observations. Furthermore, organize the correspondence between the design drawings and the construction data, and ensure that all site personnel are able to handle them with the same understanding.

Especially on sites where multiple operators take turns, if reference standards are not consistently shared the results will vary. Yesterday’s operator may have aligned to one reference point, while today’s person used a different point, or simply interpreted the check point differently—and that alone can change the as-built comparison results. It isn’t the RTK’s performance itself; insufficient standardization of operations is what causes the errors.

Therefore, if you carry out as-built management with RTK, once site standards are decided they must be shared as documents and procedures so that anyone performing the work will arrive at the same judgment. As-built management is ultimately a task that carries accountability. Rather than numbers simply appearing to match, you need operations that can explain why those values were used for comparison. Unifying the coordinate system and reference standards provides that foundation.

Condition 3: The radio environment and surrounding conditions are stable

The third condition is that the radio environment and surrounding conditions at the site using RTK are stable. RTK is a convenient method, but it is affected by the surrounding environment. When used for as-built management, it is not enough that measurements happen to be possible; it is important that observations can be made reliably at the required times.

First and foremost, RTK must receive signals from satellites. Therefore, it is at a disadvantage in locations with poor sky visibility. Places with tall surrounding structures, sites where the sky appears narrow such as cut slopes or excavations, and areas with many trees tend to have unstable observation conditions. In as-built management, it is not uncommon for the construction site itself to be in such an environment. In other words, even if RTK can be used in theory, stable operation may be difficult depending on the site layout.

Another thing to pay attention to is the effect of reflections. If there are nearby walls, metal objects, heavy machinery, or temporary materials, measurements are more likely to be affected by signals other than the direct wave, causing values to become unstable. In as-built management, you may want to measure exactly in places where reflections are likely to occur, such as next to structures or around equipment. Therefore, you need to consider not only the proximity of the measurement target but also what is around it.

Additionally, when operating with correction information, the communication condition is also important. If the connection is unstable, problems can occur such as difficulty achieving a fixed state, the status changing during an observation, and the consistency of results being compromised. Especially at large sites or in areas with uneven terrain, communication conditions can vary by area. You should not assume everything is fine just because it connected once beforehand; you need to check whether it will work across the entire work area.

In practice, it is effective to perform a desk-based evaluation of the environment before entering the field and to corroborate that assessment with trial observations. It is not meaningful to check only locations with an open sky; you must confirm whether it is stable at the actual points you intend to manage. It is important to select several representative points, measure them repeatedly at different times of day, and observe changes in condition. If instability is observed here, it is safer to design the workflow on the assumption that you will not proceed with RTK alone but will combine it with other verification methods.

When using RTK for as-built management, you need to evaluate it not by accuracy under ideal conditions but by taking into account the site-specific characteristics. Whether the radio environment and surrounding conditions are stable is an essential factor to check before selecting equipment.

Condition 4: Observation procedures and verification methods are standardized

The fourth condition is that observation procedures and verification methods are standardized. When RTK is used on site, numerical values can be obtained immediately, which speeds up work. However, as-built management cannot rely on speed alone; the same level of reliability must be ensured regardless of who takes the measurements. For that reason, observation methods should not be left to individual experience but must be defined as formal procedures.

For example, you should clearly define what to check before observations. Whether to perform reference point matching, how to verify the fixed state, how to synchronize observation times, and under what conditions to decide on re-observation are the kinds of matters involved. If you operate with these left ambiguous, judgments will vary among personnel. If one person accepts values after a short period while another cautiously re-observes, the overall quality of the results will not be consistent.

In as-built management, not only the measured values themselves but also the reliability of those measurements are important. The more subtle the difference from the design, the more the measurement method will affect the results. That is why standardizing the small details—how you approach observation points, how you set up the pole, how long you wait before taking a reading, whether to repeatedly confirm the same point, and so on—pays off. On site you may be tempted to omit steps because of busyness, but if you establish rules you can reduce rework caused by repeat measurements or insufficient explanations.

Also, verification methods need to be considered together. Rather than adopting an RTK value just once, reliability can be improved by having checking mechanisms such as repeated observations at the same point for critical locations, pre- and post-checks using known points or control points, and comparisons made immediately after construction and after a certain period of time. In as-built management, operations must not only record numerical values but also be able to identify anomalous values.

What's important for field personnel is not to create rules that are too complicated. If they are too strict, they will end up not being followed. The key is to decide the minimum set of checks that must never be skipped and to make them executable in the same way every time. By standardizing the flow of pre-observation checks, go/no-go decisions during measurement, and post-measurement verification, you can greatly reduce variability when using RTK for as-built management.

Whether introducing RTK makes work on site easier is not determined solely by how easy the equipment is to use. The quality of the results varies greatly depending on whether operational rules are in place. Standardizing observation procedures and verification methods is an unavoidable requirement when using RTK for as-built management.

Condition 5: Able to design operations that include organizing results and methods for recording

The fifth requirement is that the operational design must not stop at taking measurements but must also cover organizing the results and methods for recording them. This point is often surprisingly overlooked, but it is extremely important in as-built management. Even if numerical values can be collected on-site, if the subsequent organization is cumbersome or converting them into standardized reports is difficult, the process will not take root in practice.

The purpose of as-built management is to confirm the condition after construction, retain records as needed, and be able to explain them. Therefore, measurements must be managed in a way that makes them traceable later. If it is unclear where, when, to which standards, and by which personnel a measurement was taken, rechecks and inspection responses become problematic. RTK allows values to be viewed immediately on site, but if recording methods are not standardized, the data can easily become scattered afterward.

Particular attention should be paid to managing point names and survey stations, linking them to design values, and organizing the history when re-surveying. In as-built management, it is necessary not only to know a point’s position but also to understand what that point signifies. Whether it is a slope shoulder or slope toe, the center or an edge, a point used for as-built comparison or an auxiliary point for verification—if such meanings are not organized, merely looking at the numbers later will be of little use.

Also, on-site confirmation is not necessarily completed in a single pass; multiple checks may be performed as construction progresses. In that process, workflows such as comparing with previous values, identifying trends in deviations from the design, and rechecking after corrections occur. If data storage formats and naming conventions are not standardized, it becomes unclear which is the latest version and which value was adopted. If you use RTK for as-built management, you need to design how data is stored just as carefully as the measurement work itself.

Furthermore, the ease of organizing results is directly linked to the continued operation of the site. If the system requires manual organization every time, the busier the site, the more the operation will break down. Conversely, if the flow from measurement to verification to recording is naturally connected, the benefits of introducing RTK increase. The burden on workers is reduced, decision-making speeds up, and it becomes easier to explain things later.

When operational staff decide whether to adopt it, please look not only at whether it can measure, but also whether it can retain the records. As-built management is also a record-keeping task. Only when you can design operations to include organizing the results and the recording methods will RTK become a weapon on-site.

As-built Management Suitable for RTK and Less Suitable for RTK

So far we have examined five conditions, but in practice it is useful to take one step further and clarify which types of as-built management RTK is well suited to and which it is less suited to, making it easier to decide.

RTK is particularly well suited to situations where you want to efficiently perform planar position checks. Its mobility proves valuable in wide construction areas when you need to quickly verify control points or representative points, when you need to measure while moving between multiple locations, or when conventional methods tend to involve cumbersome setup. Because it enables immediate position determination on site, another major advantage is that it makes it easier to make judgments while observing the construction conditions there.

Moreover, on sites where sky visibility is relatively good and there are few obstructions from structures or trees, it is easier to achieve stable operation. For projects with a wide construction area, such as land development or earthworks, where you want to efficiently capture representative points, RTK helps shorten working time. It is also suitable for interim checks during construction; by quickly identifying discrepancies from the design on site, it helps prevent rework.

On the other hand, there are also challenging situations. For example, in areas with poor sky visibility or many reflections, concerns remain about the stability of the measurements. In locations such as close to narrow structures, alongside walls, around equipment, or in deep excavations, it can be difficult to carry out stable as-built management using RTK alone. Also, in processes that demand strict verification in the vertical direction, it is safer to assume that RTK results will be used alongside other validation methods rather than adopted as-is.

Furthermore, when you want to capture the fine geometry itself at high density, RTK alone has limitations. RTK is well suited for managing point positions, but for capturing subtle variations across an entire surface or complex shapes, a different measurement approach may be more appropriate. The optimal method depends on what you want to know in as-built management—whether representative points are sufficient or whether you need the quality of a continuous surface.

The important thing is not to view RTK as a万能 tool but to position it as a means that plays a well-suited role within construction quality control. In processes where it is appropriate, significant efficiency gains can be expected; where it is not, you should opt for a different method rather than forcing it. The more a site can make this distinction, the less likely RTK implementation will fail.

Summary

RTK can be used for as-built management. However, that does not mean it will automatically work simply by bringing in high-precision positioning equipment. The required accuracy and the management tolerances must be aligned, the coordinate system and the method of establishing references must be unified, the radio environment and surrounding conditions must be stable, observation procedures and verification methods must be standardized, and the operational design must include how results are organized and recorded. Only when these five conditions are met does as-built management become usable in practice.

What really matters on site is not whether RTK can be used, but whether it can be confidently adopted as a control value at your own site. Before implementation, it is important to decide the target process concretely, carry out trial observations, confirm reproducibility and recordability, and then finalize operational procedures. Once that is organized, RTK can greatly contribute to streamlining as-built management. Conversely, if you introduce it without checking the conditions, you may be able to take measurements, but you will likely struggle with management, report preparation, and inspection responses.

If you are planning to use RTK to make as-built management more efficient from a field perspective, it's important not simply to look for equipment that can measure, but to select with an eye toward operations that are easy to handle in daily management tasks. For example, by adopting a configuration that makes it easy to confirm coordinates on site—such as LRTK, an iPhone-mounted GNSS high-precision positioning device—you can lighten the initial steps of as-built verification. If you want to avoid leaving as-built management as paper-only checks and instead establish a flow that enables quick on-site decisions and links them to the necessary records, it's worth considering these kinds of field-friendly options.