Is RTK Certification Necessary? 4 Points Implementers Should Know

Table of Contents

• RTK itself does not necessarily require a national certification.

• Qualifications become an issue with respect to the scope of work and the handling of deliverables.

• When introducing something, what you should look at is the operational structure rather than the presence or absence of qualifications.

• Internal measures for the safe and effective use of RTK

• A national qualification is not necessarily required for RTK itself.

One of the first concerns for those responsible for considering the introduction of RTK is whether a qualification is required to use it. To be clear, simply using the RTK technology or equipment does not necessarily require a specific national license. If this point is left unclear, decision-making on adoption can be delayed, or conversely, people may mistakenly assume that because no qualification is required, anyone can do anything.

First, it should be understood that RTK is, fundamentally, a positioning method for obtaining high-precision location information. It uses signals from satellites combined with correction information to achieve centimeter-level positioning accuracy (half-inch accuracy). Therefore, the term RTK is not the name of a qualification but is closer to a technical term. For example, just as using a personal computer does not in itself require a qualification, handling RTK equipment or RTK-compatible devices is not immediately determined solely by the presence or absence of a national certification.

Meanwhile, on-site RTK is widely used for surveying, construction management, as-built verification, setting out, point cloud alignment, maintenance management, and recording equipment coordinates. What becomes important here is the purpose for which RTK is used. Whether it is simply to check approximate positions within the site, to use it as an internal construction aid, or to treat it as formal deliverables for external submission will change the required level of management and the level of personnel who should be involved.

What many implementation personnel often confuse here is the distinction between operating the equipment and the scope of operational responsibility. Turning on the RTK terminal, connecting to correction data, checking the positioning status, and recording points—if you isolate just this sequence of operations, it is not uncommon for them to be adequately learned through manufacturer training or in-house education. In fact, the number of RTK devices that link with smartphones and tablets has recently increased, and ease of operation has greatly improved. When using an iPhone-mounted high-precision GNSS positioning device such as LRTK, the psychological hurdle to adoption can be lower than with traditional specialized equipment.

However, ease of operation and lighter professional responsibility are separate matters. When coordinates acquired on site are used for construction reference lines, judgments near boundaries, as-built evaluation, or checking differences from the design, the issue becomes how much accuracy assurance is required of that data. In other words, qualification requirements do not attach to RTK itself, but to the types of work for which the data obtained by RTK will be used.

Therefore, in the early stages of deployment, it is important not to think in binary terms about whether RTK requires qualification or not. The correct approach is to determine whether there are tasks within RTK use cases that require the involvement or supervision of qualified personnel. Understanding this makes it easier to avoid both halting adoption out of excessive caution and, conversely, underestimating it and causing operational problems.

Because the term "qualifications" is widely used on site, national qualifications, private-sector qualifications, completion of manufacturer training, and internal company certifications tend to be mixed together. As the person in charge of implementation, it is important not to treat these as the same. By distinguishing situations that require national qualifications from those that can be adequately addressed through education and training, you can avoid setting overly strict personnel requirements and make it easier to develop a realistic implementation plan.

It's natural to feel anxious before introducing RTK, but the key point to grasp first is clear. Operating RTK equipment itself does not always require a specific qualification. However, some tasks performed using RTK do require the involvement of qualified personnel, an organizational framework that includes qualified personnel, or a certain level of accountable management. Those responsible for implementation need to understand this distinction from the outset.

Qualifications become an issue regarding the scope of work and the handling of deliverables

One reason RTK qualifications become a topic of discussion is that the act of positioning is closely linked to the professional responsibilities involved in surveying and construction. What those responsible for implementation really need to confirm is not just whether there are people who can operate the equipment. It is what kinds of tasks the work they plan to perform with that equipment falls under, and what kind of deliverable it will ultimately be treated as.

For example, when using RTK for purposes such as verifying the placement of temporary structures on site, understanding work flow lines, checking reference positions of construction machinery, or internal progress recording, operational rules and an understanding of positioning are often more important than qualifications. In these situations, RTK can be fully effective if staff who have received in-house training handle it and understand the positioning status and the criteria for re-observation.

On the other hand, when it comes to data submitted as external surveying results, coordinates treated as contractual deliverables, or records for which accuracy and the allocation of responsibility are clearly in question, the situation is different. Depending on what work is being contracted, which laws and specifications the work follows, and what level of accuracy certification is required, the requirements for the personnel and organizational arrangements that should be involved become more stringent. What is important here is that precisely because RTK is highly accurate, misuse can make the results appear misleadingly plausible. Even if fine coordinate values are visible at first glance, if the reference standards or verification methods are inappropriate, those values do not have operational reliability.

A clear way of thinking for those responsible for implementation is to divide the use of RTK into three categories. The first is the stage of using it as an internal support tool. The second is the stage of using it as practical data for construction and maintenance. The third is the stage of using it as official deliverables and external-facing explanatory materials. Of these, the first is relatively less affected by qualification requirements, the second places importance on internal rules and quality control, and the third tends to require greater involvement of qualified personnel and a heavier organizational responsibility framework.

For example, when using RTK on construction sites to assist with batter boards and layout marking, to perform preliminary confirmation of as-built conditions, or to verify reference points for excavation locations, the primary objective is often to improve work efficiency. At this stage, what matters more than holding certifications is whether the operator understands site conditions, can consistently obtain a fixed solution, has not misconfigured the coordinate system, and whether there are rules for naming survey points and for recording methods. There are cases where operations can be carried out under certain rules even without a qualified person.

However, when it comes to judgments made near boundaries, work that is similar in nature to public surveying, deliverables directly tied to inspection or acceptance, or the submission of coordinates based on arrangements with the client or the prime contractor, mere equipment use is not sufficient. The validity of the coordinates, consistency with control points, observation procedures, reproducibility of records, and the verification system for the person responsible are all called into question. At that stage, in answer to whether qualifications are necessary, the response is not that they are required because it is RTK, but that a cautious framework is necessary because of the nature of the work.

What you need to watch out for here is the difference in perception between site personnel and management. Field staff tend to think that because measurements were taken with RTK at high precision, they can be used. By contrast, management and the client focus on which procedures were used to collect the data, who verified it, and by what criteria its validity was judged. When the person responsible for implementation stands between these two parties, if the debate centers only on whether someone has the necessary qualifications, the essential discussion is lost. What really needs to be asked is which personnel and procedures will guarantee the quality assurance required for the work.

Furthermore, RTK is not a self-contained technology. In the field it depends on many prerequisites such as reference points, known points, drawings, design coordinates, localization, the geoid, network conditions, and the quality of correction information. Therefore, the person who can operate the equipment is not necessarily the same as the person who can use positioning results for business decisions. The need to discuss qualifications arises in situations where the latter bears greater responsibility.

As the person responsible for implementation, it is easier to organize matters by listing the planned uses of RTK and classifying each as internal support use, construction operational use, or formal deliverables use. By doing so, there is no need to impose the same qualification requirements across the board, and conversely it becomes easier to determine that only the parts related to formal deliverables should have stronger supervision and verification workflows by qualified personnel. This is a practical way to reduce risk without halting deployment.

What to look at when introducing is the operational framework rather than the presence or absence of qualifications

Companies that successfully implement RTK do not decide whether to adopt it solely based on whether staff are certified. Rather, they put effort into creating an operational system that can be used reliably on site. This is because RTK, while highly accurate, is also a technology that can easily lead to reduced accuracy or misunderstandings if operated incorrectly. The core that those in charge of implementation should look at is not who will use it, but under what conditions it will be used, how it will be recorded, and how it will be verified.

First and foremost, it is important to clarify the intended use of RTK. Some people responsible for deployment choose the equipment first and then decide how to use it. However, that approach leaves discussions about required qualifications and system design vague. Whether you want to streamline as-built verification, simplify point-cloud georeferencing, speed up current-condition recording, or reduce labor for setting out construction positions, the required accuracy level, staff training, and verification workflows will differ.

Next, what is required is to clarify the accuracy requirements. RTK is often described as centimeter-level, but that phrase alone is insufficient. In the field, you need to understand the difference between horizontal and vertical accuracy, the time required for initialization, the influence of sky conditions, changes to the reception environment caused by surrounding structures, and stability during movement versus when stationary. If the person responsible for deployment is vague about these points, field personnel will trust the numbers alone and may become overconfident about the actual accuracy required.

Furthermore, the handling of coordinate systems is at the heart of operational procedures. RTK can provide high accuracy when used correctly, but if the coordinate system or reference settings are wrong, the entire result can be shifted no matter how good the positioning quality is. Common on-site errors include confusing drawing coordinates with observed coordinates, mistakes in converting to local coordinates, insufficient cross-checking with known points, and misinterpretation of height handling. Having a qualification alone will not prevent these practical mistakes. What is needed is standardizing the workflow of pre-measurement confirmation, verification with known points, and post-measurement checks.

Also, checking the communication environment is indispensable. If you use network RTK, you need a communication condition that can stably receive correction information. In mountainous areas, around structures, near underground locations, and on sites with many temporary facilities, both communications and reception tend to become unstable. In such cases, even if there is one qualified person, operational quality will not improve unless procedures for deciding whether to re-survey on site and alternative procedures are in place. Those responsible for deployment must design the system to include what to do in the event of communication failures and how to determine action when a fixed solution cannot be obtained.

Training is also extremely important. When implementing RTK, explanations tend to emphasize that it can be used by beginners, but in reality there are several items that must be understood at a minimum. For example: the difference between fixed and float solutions, how to read positioning status, the meaning of initialization, the necessity of re-observation, how to handle antenna height, the approach to verifying known points, how to name records, linking with photographs, and how to save observation logs. If these are used without understanding them, it won’t be a case of being usable without qualifications; rather, it may appear to be working while you accumulate incorrect data.

A practical approach is to define internal usage categories. For example, beginners would be limited to current-condition recording and internal verification purposes; intermediate users would be allowed to assist with construction and perform preliminary checks of as-built conditions; and, with supervisor approval, to have findings reflected in official reports—this phased operation. This is not a substitute for national certification, but it is a realistic way to prevent accidents during the initial rollout. As the person responsible for implementation, it is more practical to create a safety margin through training and the design of authorities than to draw a hard line based solely on the presence or absence of qualifications.

Equipment selection is directly linked to the operational framework. Devices that require complex configuration may be suitable for experienced users but can be ill-suited for initial field deployment. Conversely, devices that are easy to operate and readily integrate with smartphones can reduce the training burden. For example, configurations that prioritize portability and operability, such as LRTK, can be advantageous for establishing routine practice in the early stages of implementation. However, ease of use does not mean that quality control is unnecessary. Even with user-friendly equipment, observation rules and verification workflows are required.

What those responsible for implementation should avoid most are halting on the judgment that deployment is impossible because there are no qualified personnel, and believing that because the equipment is simple, anyone can use it anywhere with the same level of accuracy. The former becomes an opportunity loss, and the latter leads to quality incidents. To avoid these extremes, it is important to position the qualification discussion within the operational framework: who is involved in which tasks, at what stages a responsible person performs confirmation, and which data are treated as the official deliverables. This design itself determines the success or failure of RTK deployment.

Internal company measures for the safe and effective use of RTK

When introducing RTK, merely confirming whether staff have the required qualifications and stopping there makes it easy to stumble in actual field operations. What the person responsible for implementation should truly put in place, before the equipment procurement process, are internal standards for how it should be used. If this remains vague, even after investing in RTK you may end up with a situation where only a few knowledgeable people can use it, or conversely where anyone can use it but the quality varies.

What is needed first are operational rules by use case. Data obtained with RTK include various types such as current condition surveys, construction support, pre-inspection checks, internal management of as-built conditions, position records for maintenance ledgers, and georeferencing of point clouds and photos. Treating all of these with the same weight leads to confusion. It is important to distinguish whether the data are internal reference data, data used for process decision-making, or data intended as the basis for external submission, and to define for each the required number of verifications and whether confirmation by a responsible person is necessary.

Next, what is required are the checks to be performed before observation. RTK is a technology that is prone to failure if you start measuring as soon as you arrive on site. Before observation, you need to check the presence or absence of control points and known points, coordinate system settings, the connection status of correction information, the reception environment, surrounding obstacles, the required accuracy, inputting the antenna height, battery levels of the equipment to be used, and so on. Leaving this to individual experience causes large quality differences between operators. As an internal measure, standardizing this in the form of a pre-observation checklist is effective.

Criteria for judgment during observations are also necessary. In RTK, even when the positioning status appears stable, it can actually be affected by the reception environment. Do not be reassured merely because numbers are displayed; make a habit of checking the fix status, the time required to stabilize, consistency with known points, and the variability in continuous observations. Without this understanding, less experienced personnel are more likely to treat the displayed coordinates as correct as they are. Sharing these judgment criteria is more important than whether someone is certified.

Post-observation processing and recording methods are also indispensable for in-house procedures. The way survey point names are assigned varies by person, photos are not linked to observations, it’s unclear which coordinate system was used for recording, and the observation date/time and the responsible person are not retained. In this condition, the data are unusable upon later review. To maximize the benefits of introducing RTK, it is important that the acquired data be organized so that it connects to downstream processes. If point clouds, photos, drawings, and construction records can be managed in an integrated way, RTK becomes not merely a positioning device but the foundation of site information.

The line for responsible-person sign-off should also be made clear. Even if not all data must be observed by a qualified person, you need to decide at which stages responsible verification will be applied. For example, values used as internal references can be left to on-site staff judgment, but when reflecting them into documents intended for external submission, require confirmation by a responsible person. This way, you can leverage the convenience of RTK while applying appropriate levels of scrutiny to data handling.

For training, it is important not to stop at a single one-off course. RTK operations will not become established if users only receive an initial explanation. In the actual field, it is necessary to learn through experience where accuracy is likely to be disturbed, which observation procedures offer high reproducibility, and in which cases you should switch to alternative methods. Therefore, during implementation it is effective to combine classroom instruction with on-site checks, verification at known points, and internal reviews.

Also, part of our internal arrangements is adopting a stance of not treating RTK as a万能 technology. If the term "high accuracy" takes on a life of its own, it can create the misunderstanding that all location-related operations can be handled solely with RTK. In reality, however, in places with poor reception, locations with limited sky view, situations requiring strict vertical accuracy, or tasks that require clear standards, it is necessary to combine other measurement techniques and verification methods. Those responsible for implementation should, while making RTK the main tool, share internally the situations in which it is better not to use it.

Finally, from the implementation manager’s perspective, the most important thing is not to limit RTK to a matter of qualifications alone. Of course, depending on the nature of the work, confirming the involvement of qualified personnel and the responsibility framework is important. However, to actually achieve results on site, more than whether someone holds a qualification, you need standardization of usage, training, record-keeping, verification, and clear allocation of responsibilities. When these are in place, RTK becomes a highly effective technology to implement and is easier to roll out across the company.

When asked whether an RTK qualification is required, the answer that the person responsible for deployment should have is not a simple one-word response. Handling RTK equipment itself does not always require a national certification. However, the necessary organizational setup and the level of responsibility will vary depending on what you measure with RTK, what tasks you use it for, and what results you treat as deliverables. Starting from this understanding, separating use cases, defining verification procedures, and establishing a training system is the shortest route to a successful deployment.

Rather than postponing implementation due to concerns about qualifications, it is important to correctly distinguish the situations where qualifications are relevant and then design operational procedures that fit your company. When used correctly, RTK can greatly contribute to faster positioning, reduced labor, and more advanced information sharing. If it is introduced in a way that suits the field and allows you to set the necessary level of verification for each task, RTK will take root not as a technology for a limited number of specialists but as a practical system that boosts productivity across the entire site.