How to Reduce Monthly RTK Costs? 5 Points to Review

Introducing RTK can improve positioning accuracy, making it easier to streamline field operations such as surveying, construction, inspections, agriculture, and infrastructure management. However, it is not uncommon for running costs after implementation to exceed expectations, creating a burden for continued operation. In particular, monthly costs are not determined solely by the correction service subscription fee; they can grow as multiple factors accumulate, such as communication charges, number of lines, device configuration, operational methods, and staffing.

Therefore, when you want to reduce the monthly cost of RTK, the important thing is not simply switching to a cheaper service. You need to review, in line with actual work processes, whether the contract type matches your current usage, whether the actual usage frequency contains waste, whether communication arrangements are excessive, whether the equipment configuration is too heavy for the site, and whether the operational structure involves duplicated roles or over-reliance on specific individuals. The sites that succeed in cutting costs organize not only unit prices but the entire operation, eliminating waste while maintaining the necessary level of quality.

This article organizes five points to review in order to reduce monthly RTK fees, and provides a detailed explanation from the perspectives of contract type, usage frequency, communication lines, equipment configuration, and operational structure. From a practical standpoint, we delve into common patterns of waste that occur on site, decision-making criteria, precautions when conducting a review, and approaches to lowering costs without sacrificing accuracy or operability.

Table of Contents

• Introduction

• Review Point 1: Align the contract type with actual business operations

• Review Point 2: Identify unnecessary fixed costs based on usage frequency

• Review Point 3 Reconsider how you manage your lines to reduce communication costs

• Review Point 4: Optimize equipment configuration to reduce monthly costs

• Review Point 5: Streamline the Operational Structure to Reduce Hidden Costs

• Summary

Introduction

When considering the monthly costs of RTK, many people first focus on the fees for correction services. Of course, this is a central expense. However, in practice, simply reviewing the correction service often doesn't reduce the overall cost as much as expected. The reason is that RTK operating costs are not contained within a single contract.

For example, if multiple communication lines are contracted for each site, if always-on contracts are attached to terminals that are actually used only a few times a month, or if the number of simultaneous connections for correction services is set higher than actual operational needs, the monthly fixed costs can expand without you realizing it. Furthermore, if only a few personnel are knowledgeable about configuration and troubleshooting and each startup takes time, those labor costs and standby times also become real operational expenses. If you only look at the monthly subscription fees on the books, this part is often overlooked.

Another important point is that when cutting RTK costs, getting the order of cuts wrong can lead to a decline in on-site quality. For example, if you switch to the cheapest contract regardless, you may end up lacking coverage area and stability, and corrections may become harder to receive on site, causing re-surveys and rework. In that case, although the apparent monthly fee may go down, the overall cost of operations can actually increase. It’s important to trim fixed costs without forcing reductions in the aspects that affect accuracy and uptime.

What is needed, then, is a perspective that breaks down RTK costs. Specifically, start by confirming whether the contract type matches the workload, and then check whether there are excessive connections or devices relative to actual use. Next, clarify who on site is using the system and how, and reduce hidden costs caused by inadequate training or management. Reviewing in this order makes it easier to cut costs while maintaining accuracy and operability.

Because RTK handles high-precision positioning information, it is a system that entails a certain amount of maintenance cost. However, that does not mean you must accept high fixed costs as they are. By configuring it to suit the site, there is ample room to reasonably reduce monthly expenses while ensuring the required accuracy. From here, we will go through five points, in order, that tend to yield the most noticeable improvements in practical operations.

Review Point 1: Align the contract type with actual work practices

When trying to reduce the monthly cost of RTK, the first thing to check is the contract type. On sites, it's common to keep an earlier contract in place by default, so that even though the workload and number of users have changed, only the contract remains as it used to be. In this situation, you are likely to continue paying fixed costs that are too high relative to the actual circumstances.

When reviewing contract types, the first thing to consider is whether continuous operation is required or whether access is only needed during certain periods. For example, for a company that uses RTK at multiple sites throughout the year and performs high-precision positioning on a daily basis, a flat-rate monthly contract is reasonable. On the other hand, for work that uses it intensively only during specific periods or operations that require RTK only a few days per month, a continuous contract tends to be costly. In such cases, short-term use, device-limited contracts, or plans that allow switching by period may be more suitable.

Also, the way you think about the number of contracts is important. In companies with many sites, they may have separate contracts for each device, but in reality many devices are not operating at the same time. For example, even if you own 5 devices, if you only use about 2 of them at any given time and the rest are kept as spares, you don't need to maintain 5 contracts. If you match the number of contracts to the number of devices you own, you'll incur monthly fees for devices that aren't being used. What you need to base your considerations on is the number of devices operating simultaneously, not the number you own.

What is easily overlooked here is the pattern of contracts increasing based on the individual judgment of on-site personnel. If one department takes out additional contracts as a backup and another increases contracts just in case, the company as a whole can end up with excessive contracts. Such waste may look small at each site, but it becomes a large fixed cost over a year. When reviewing contracts, it is important to list them company-wide rather than by department.

When reviewing contract arrangements, you should check not only the fees but also the constraints. For example, switching to a cheaper plan may result in a limited service area, fewer simultaneous connections, weaker support, or stricter conditions for renewal. What works fine under normal circumstances can become inconvenient during peak periods or at remote sites. Rather than deciding based solely on price, clarify which conditions are required for each task before switching.

As a concrete review method, first extract usage records for the past three to twelve months and check the number of operating days per month, the number of concurrent devices, and the areas of the usage sites. Based on that, separate devices that require permanent contracts from those that can be handled by short-term expansions. Simply organizing this makes it easier to optimize the number of contracts that incur fixed costs. It is important to make decisions based on actual usage records rather than solely on on-site intuition.

Furthermore, the timing of contract renewals is also a good opportunity to review costs. Many companies renew contracts under the same terms as the previous year without scrutinizing the details. However, if there has been an increase or decrease in the number of sites, changes in the number of personnel in charge, or changes in the scope of work, you should reconsider how the contract is structured at that time. By making it a habit to check at each renewal whether it matches the current workload, you can avoid paying unnecessary fixed costs for extended periods.

When reviewing contract types, what matters is not finding the cheapest plan but switching back to a contract that fits your current operations. If you can streamline your agreement to what is necessary and sufficient, it becomes easier to reduce monthly costs without sacrificing accuracy or usability. Starting here is the most effective way to cut RTK operational costs.

Review Point 2: Identify unnecessary fixed costs based on usage frequency

Next to review is the frequency of RTK use. Even if the contract appears reasonable at first glance, if fixed costs are excessive relative to actual usage or operating hours, cost efficiency will suffer. In particular, on-site contracts are often drawn up based on initial expectations, and if actual use later proves lower than anticipated, reviews are frequently not carried out, leaving only the fixed costs.

When considering usage frequency, it's important not only to look at how many days per month it's used, but also to examine which operations it's used for and how much time is spent on each. For example, even if a device is taken to the field 10 days a month, RTK may actually be needed for only about one hour each day. The remaining time may be spent on preparation, travel, and verification tasks, so the use of high-precision positioning itself may be limited. In that case, rather than contracting multiple units on a permanent basis, it may be possible to respond by sharing devices or adjusting dispatching/assignment for each site.

Also, monthly fluctuations should not be overlooked. In work such as civil engineering, surveying, agriculture, and equipment inspection, usage can vary greatly between busy and slow seasons. Maintaining a high-capacity contract year-round to match peak season results in wasted fixed costs during inactive periods. Rather than looking at the annual average, if you separate the maximum configuration required for the busy season from the standard configuration needed during normal periods, you can identify opportunities to adjust the number of contracts and lines.

In practice, contracts are sometimes maintained based on the impressions of the person in charge while the actual frequency of use remains unclear. At the operational level, people often say, "We need it because we use it occasionally," or "We want to keep it just in case." However, equipment and contracts that are used only occasionally can add up to very high costs. What matters is not judging whether something is necessary or unnecessary by intuition, but recording how frequently it is used, for which tasks, and to what level of accuracy.

A simple visualization of usage logs and on-site daily reports is effective here. You don't need complex analysis; simply recording when, who, at which site, and how many units were used is sufficient. Reviewing several months' worth of this will reveal that contracts you thought were needed all the time are actually used only a few times a month, or conversely that usage is concentrated on specific days of the week or particular tasks. Once you understand usage patterns, it becomes easier to consider concrete measures to reduce fixed costs.

For example, if, within the same company, Team A uses RTK in the morning and Team B in the afternoon, you can reduce the number of contracts by creating shared-use rules instead of completely separating devices and contracts. Also, if devices that were individually assigned to each site can be managed in a reservation-like manner, you may be able to reassess ongoing contracts for devices with low usage frequency. Of course, you need to balance travel distance and the effort of handing devices over, but this is more rational than continuing to pay fixed costs without understanding actual usage.

One important point to bear in mind is that low usage frequency does not automatically mean it should be reduced immediately. For example, in emergency response, ad-hoc surveys, or restoration work, a capacity that can respond immediately is valuable even if its usage frequency is low. In such cases, judging solely by simple utilization rates risks cutting even the necessary preparedness. Therefore, when reviewing usage frequency, it is necessary to consider contracts for routine operations separately from reserve arrangements for emergency response.

Companies that fail at cost reduction often implement across-the-board cuts without looking at usage frequency, which leads to complaints from the frontline and causes them to revert to the original contracts. This approach does not produce lasting effects. First, it is important to classify contracts into those for frequently used tasks, those used only during certain periods, and those kept only as a precaution, and to consider the appropriate way to manage each. By organizing based on usage frequency, you can optimize fixed costs to match reality rather than enforce unreasonable cuts.

Because RTK is convenient, it can also be a system that makes it easy to increase subscriptions without noticing. For that reason, it’s important to quantify how much you’re using it and adjust costs to match your level of operation. Reviewing usage frequency is a basic task for returning to operations without excess or shortfall.

Review Point 3: Reassess How You Manage Your Lines to Reduce Communication Costs

When considering the monthly cost of RTK, attention tends to focus solely on correction service fees, but communication charges are also an important ongoing expense. In particular, when using network-based RTK, a communication environment is required to receive correction information, so many sites give each terminal its own SIM or mobile data connection. However, if these connections are not optimized, unnecessary fixed costs can arise that exceed the correction contract.

A common situation is assigning separate lines to each receiver, tablet, smartphone, mobile router, and so on. When introducing them, it can feel safer to give each device its own line to avoid connection troubles, but in actual operation, such redundancy is often unnecessary. At some sites, a single device shared as the primary line would suffice, yet the number of lines keeps increasing simply because past practices are being followed.

When reviewing communication costs, it's important to first separate and consider what each connection is needed for. Is it for receiving correction information, for communications of on-site apps, for uploading photos or data, or for general contact? Different uses require different capacity and stability. If it's only for receiving correction information, a costly plan built around high-volume data may not be necessary. Conversely, if point cloud data and images are transmitted over the same connection, data caps or speed reductions can impact operations. To reduce costs, you need to organize connection requirements by use.

Also, optimizing the number of network lines is a major point. For example, if a receiver and an operation terminal are always used together on-site, you can reassess whether both need independent lines. In some cases, smartphone tethering or a shared connection can sufficiently cover the needs. Of course, you must balance this against stability, battery consumption, and the simplicity of connection procedures, but excessive line subscriptions that do not match on-site realities should be candidates for reduction.

On the other hand, reducing communication lines too much can increase on-site troubles. In mountainous areas or regions with unstable network quality, relying on a single line can make correction data prone to interruptions. Also, if staff are not familiar with tethering settings and spend time connecting each time, labor costs and downtime waiting for work may end up higher. When cutting communication costs, you need to take into account not only the fees but also on-site connection stability and connection setup time.

For example, if a backup device that is used only a few times a month has its own dedicated line, that is an area where review can yield noticeable results. Even if the backup device is necessary, it may not be necessary to maintain a permanent communications contract. Changing operations so that you use a shared line only when the device is in use, or add a line only during the periods when it is needed, makes it easier to reduce fixed costs. Also, if multiple departments have contracted similar lines separately, it can be effective to reorganize company-wide to reduce duplication.

When reviewing, it's important to check the communication environment at each site. The required network connection quality differs between operations focused on urban areas and those that include suburban or mountainous areas. If you align connection requirements for all sites to the most expensive conditions, many sites will be over-specified. Conversely, if you standardize company-wide on conditions suited to mainly flat terrain, problems will occur at sites with more demanding conditions. Separating standard and exception configurations according to site characteristics leads to a balance between cost and stability.

Furthermore, communication costs should be considered not only in terms of unit price but also in terms of management effort. As the number of lines increases, the work involved in update management, usage monitoring, fault isolation, and invoice verification also increases. Although these are not easily visible, they accumulate as a burden on the administrators. By streamlining how lines are managed, it may be possible to reduce not only monthly communication fees but also management costs.

Communication lines in RTK operations form the foundation that supports accuracy, but they are also an area with considerable room for review. By reducing expensive lines that don't match the intended use and duplicate contracts while maintaining the stability required on site, monthly expenditures can be steadily reduced. Communication requires caution—cutting too much can affect operations—but if you clarify the current situation, it becomes an area that can be configured without excess or shortfall.

Review Point 4: Optimize equipment configuration to reduce monthly expenses

When considering RTK costs, the equipment itself may be perceived primarily as an initial expense. However, in reality, the way you choose the equipment configuration also has a significant impact on monthly costs. This is because the more complex the configuration, the more likely you are to need additional correction subscriptions, communication lines, maintenance, spare units, and related software. In other words, over-specifying the equipment configuration drives up monthly fixed costs in ways that are not immediately visible.

For example, if you standardize each site by fixing a dedicated receiver, a dedicated operator terminal, a dedicated line, and a dedicated mount as a package, operations become easier to manage, but maintenance costs increase accordingly. Moreover, in reality the same configuration is not necessarily required at every site. Sites focused on single-point position checks and those carrying out continuous surveying or collecting many points require different equipment usage and numbers of devices. If you ignore differences in use and uniformly deploy a heavy configuration, the monthly costs tend to rise.

When reviewing equipment configurations, the important thing is to break down what is truly needed for each task. For example, at sites where continuous high-precision guidance or ongoing operations are required, a dedicated configuration will be highly valuable. On the other hand, at sites focused on coordinate checks or one-off positioning, a simpler configuration may be sufficient. Instead of applying top-spec equipment to every site, simply separating standard and simplified configurations according to the work content can make it easier to reduce operating costs.

Also, how spare devices are managed should be reviewed. Securing spare devices as a precaution against failures is important, but if you maintain permanent contracts or active lines for the spares, fixed costs will continue to accrue during periods when they are not used. While retaining spare devices, there is room to optimize their management—structure contracts on a shared basis, add or activate services only when in use, or consolidate spares at specific locations and reallocate them as needed. If you prioritize only the peace of mind provided by spare devices, routine fixed costs can easily grow.

Also, attention must be paid to duplication of peripheral devices and related software. In RTK operations, not only receivers but also position-checking apps, drawing-review terminals, data-transfer terminals, and the like tend to increase. If each person responsible creates their own convenient setup, devices and services with similar uses can become duplicated, resulting in higher monthly fees and more items to maintain. When optimizing device configurations, it is important not to deny convenience, but to confirm whether the same thing is being done by separate devices.

A common situation in practice is that, due to anxiety at the start of implementation, more equipment is procured than necessary and then maintained without being reduced. It’s understandable to decide to have extra terminals and additional lines at first to avoid problems. However, once operations have stabilized, you should review whether that configuration is still needed. As on-site staff become accustomed, they may be able to handle things without as many spares or redundant setups as before.

However, simplifying equipment configurations must be carried out with caution. If you reduce configurations too much, you can incur other costs — such as lacking backups in case of failure, complicating handovers at each site, and introducing errors whenever connections are changed. If you rush to cut expenses and degrade on-site setup and operability, you will ultimately lose out to longer work times and rework. The important point is not to aim for the minimal configuration, but to reduce excessive configurations on a per-site basis.

As a way to proceed with the review, first list the current configuration and organize what is permanently deployed at each site. Next, check how much each piece of equipment is operating each month, whether it can be replaced, and whether it can be shared. Based on that, separating equipment required across all sites from equipment needed only at some sites makes it easier to optimize the configuration. Even just this organization will prompt a review of the number of devices and contracts that must be maintained at all times, leading to a reduction in monthly costs.

While RTK is highly accurate and convenient, once you start increasing the system configuration the associated peripheral costs also rise. That is why the perspective of not what you own but what you need to maintain on an ongoing basis is important. By tailoring equipment configurations to actual needs, you can keep fixed costs down while more easily maintaining the required accuracy and operability.

Review Point 5: Establish an operational framework to reduce hidden costs

When it comes to reducing monthly RTK costs, attention tends to focus on contracts, communications, and equipment, but in fact organizing the operational setup is also a very significant issue. This is because on sites where the operational setup is not well established, even when using the same contract and equipment, unnecessary labor costs, standby time, remeasurements, and inquiry handling increase, inflating the effective monthly burden. Although they do not appear on the estimate, costs caused by operational deficiencies certainly occur.

For example, when the connection procedure differs by person and only a limited number of people know how to configure the system, it takes time to get things up and running on site. Each time problems occur—corrections not being applied, not knowing the connection endpoint, or mismatched coordinate system settings—an operation that relies on calling the knowledgeable staff causes delays to accumulate before work can begin. These delays become a cost separate from the monthly usage fee.

Also, in sites where work has become person-dependent, contracts and spare equipment kept “just in case” tend to increase. Because there isn’t a system that allows anyone to use things in the same way, people become anxious and want to secure extra lines and devices. In other words, the weaker the operational framework, the more likely you are to over-defend on the equipment side. In this state, even if you review contracts and devices, fixed costs tend to remain for the reason, “we can’t reduce them because we’re worried.”

The first thing needed when establishing an operational framework to reduce costs is to document standard procedures. It is important to concisely organize the steps from powering on, connection checks, correction reception, position verification, to shutdown procedures so that anyone can start up following the same flow. This reduces connection errors and missed settings, making it easier to shorten startup time. As standardization progresses, unnecessary backup contracts and excessive reliance on support also become easier to reduce.

Next, assigning responsibilities on-site is crucial. If RTK management is unclear, contract renewals, line management, device management, fault response, and decisions about usage rules become fragmented, causing duplication and omissions. For example, if one department independently adds lines, another increases spare devices, and headquarters does not know the total number, optimizing fixed costs becomes difficult. By consolidating the management contact point to some extent and simply deciding who approves what, it becomes easier to prevent unnecessary expansions.

Training and education systems also translate directly into hidden costs. If new hires or staff with multiple roles do not fully understand RTK, they may make incorrect settings on site or skip accuracy checks, which can lead to re-surveys later. Re-surveys are very costly because they involve travel expenses, labor costs, and project delays. If you are considering monthly cost reductions, it can be more effective to ensure users can operate without hesitation before cutting equipment or contracts.

As a concrete example, even if the monthly fee isn’t that high, if administrators are spending a lot of time each week handling inquiries from each site, the effective cost becomes quite large. If basic operating procedures and troubleshooting are rolled out to the sites and the rate of simple self-resolution can be increased, you can reduce administrative burden while improving operational quality. As a result, the need for unnecessary standby contracts and excessive support decreases, leading to long-term reductions in fixed costs.

When reviewing operational systems, quality control is indispensable alongside reductions. Because RTK is highly precise, incorrect use can nevertheless appear plausible at first glance. For that reason, it is important to standardize the minimum verification procedures—such as reference points for accuracy checks, start-of-day inspections, coordinate system confirmation, and communication checks. By streamlining operations, you stabilize not only costs but also the reliability of results.

It should be noted that improving the operational framework does not end once rules are created. As personnel are reassigned, job responsibilities change, and equipment is updated, procedures and training content need to be reviewed. If this is left unattended, reliance on specific individuals will re-emerge and waste in contracts, network connections, and equipment will increase. Conversely, if you maintain a habit of regularly auditing operations, it becomes easier to prevent monthly cost increases.

If you really want to lower monthly RTK costs, you need to consider not only the visible billed items but also the costs buried in operations. Advancing standardization, clarifying roles, providing training, and streamlining management makes it easier to cut unnecessary contracts and excessive spares, which in turn reduces ongoing burdens. Organizing the operational structure may seem mundane, but it is one of the most reproducible ways to reduce costs.

Summary

Lowering monthly RTK costs requires more than simply switching to a cheaper service. Costs can balloon not only from the correction subscription but also from fixed fees that don’t match usage frequency, duplicate communication lines, excessive equipment configurations, and an uncoordinated operational structure. Therefore, to conduct a review that truly delivers results, it is important to inspect the five areas together: contract type, usage frequency, communication lines, equipment configuration, and operational structure.

First, contract types should be considered according to the number of units operating simultaneously and the seasonality of operations, rather than the number of units owned. Even simply separating items that require continuous contracts from those that are only needed on demand can help reduce fixed costs. Next, by capturing usage frequency based on actual usage data, it becomes easier to identify contracts and devices that are being maintained without a clear reason. Rather than relying on intuition, it is important to visualize where and to what extent they are being used.

For communication lines, optimization according to usage and on-site conditions is necessary. Share parts that can be shared without compromising stability, and there is room to review independent lines for backup units and devices used infrequently. Regarding equipment configuration, rather than equipping every site with the same heavy gear, it is effective to separate standard configurations and simplified configurations by use. Simply reorganizing how backup units and related terminals are held can reduce monthly costs.

And finally, putting an operational framework in place directly reduces hidden costs. By standardizing procedures, consolidating management, and providing training, you can reduce start-up losses, inquiries, remeasurements, and excessive standby contracts. Even if you cut contracts and equipment alone, if operations are disordered, costs will ultimately arise in other forms. That is why cost reduction and operational quality must be considered together.

In practical work, what matters is not aiming for the lowest price but cutting waste while maintaining the necessary accuracy and stability. RTK is an effective means to improve on-site productivity, but simply introducing it does not automatically maximize cost-effectiveness. Only by continuously aligning contracts and operations with how it is used will it become feasible to sustain operations at a reasonable cost.

If you're worried about monthly expenses, it's recommended to start not by looking at the billed amount itself but by organizing which contracts exist for which operations. If you find contracts that don't match on-the-ground realities, inactive devices, duplicate lines, or management that depends on specific individuals, there is room for improvement. The monthly cost of RTK can be substantially reduced depending on how it's reviewed. What is needed is not blanket cuts but a redesign that reflects actual conditions.