What to Start with i-Construction 2.0? Six Introductory Items for On-site Personnel

Facing challenges such as labor shortages at construction sites, skills transfer, quality assurance, the burden of paperwork, and improving the efficiency of surveying and as-built management, many on-site practitioners have likely heard the term "i-Construction 2.0." However, even if they know the term, it is often unclear where to start on site, what remains an extension of conventional practice, and what constitutes a new initiative.

On-site, it is more important whether a plan can be translated into today's tasks, this month's schedule, and this fiscal year's organization than whether it is grand in scope. No matter how admirable the policy, if the surveying workflow does not change, the methods for verifying as-built conditions do not change, and the way information is shared remains paper-centered, site personnel will have difficulty feeling its impact. Put differently, i-Construction 2.0 is far more practical when approached from the perspective of how it will change daily on-site operations than when understood as an abstract or difficult term.

What's especially important for on-site staff is not to try to change everything from the outset. Within the basic tasks of measuring, recording, sharing, verifying, and managing, identify where rework is frequent, where waiting times occur, and where processes depend on people, and build up improvements in those areas — doing so will ultimately help adapt to i-Construction 2.0.

This article assumes on-site practitioners who are searching for "iconstruction 2.0" to gather information. Rather than explaining systems and policies in an abstruse way, it organizes and explains 6 items on what to start doing on-site. It is presented so that those who are in the stage of considering adoption, as well as those who have already begun partial digitalization, can both see their next step.

Table of Contents

• How on-site personnel should view i-Construction 2.0

• First thing to start with 1: Review on-site measurement work

• What to Start With 2: Switch Your Record-Keeping to Digital-First

• First things to start 3: Establish the workflow for as-built management and quality verification

• First things to start with 4: Establish procedures to reduce delays in information sharing

• 5 Things to Start With: Standardize coordinates and rules before introducing equipment

• 6. First steps: Start small and build a system you can sustain

• Summary: i-Construction 2.0 is an initiative to change the order of on-site operations

How should on-site personnel perceive i-Construction 2.0

When faced with i-Construction 2.0, many site personnel tend to think, "Isn't this about introducing new machines and advanced systems?" Indeed, digital technologies, automation, and the use of three-dimensional data are important elements. However, from the perspective of on-site operations, the essence is not limited to that. More important is reorganizing the flow of information on site from the ground up.

On traditional construction sites, it was common to hand-record surveyed measurements, return to the office to organize them, update drawings and forms, and share them with stakeholders as needed. While this workflow has been used for a long time, it is also prone to problems such as transcription errors, delays in sharing, missed checks, and the need for re-surveys. Although this method worked when there were many people and sufficient experienced staff, its limitations have become apparent in the modern era of labor shortages and shorter construction schedules.

It is easier to understand i-Construction 2.0 if you think of it as a concept that shifts this trend toward "connecting information obtained on site as quickly, accurately, and in a form that is easy to reuse." In other words, rather than isolating surveying as only surveying, construction as only construction, and management as only management, it is an approach that links each process through data.

There are three important perspectives for field personnel. The first is to bring information as close as possible to a usable state at the time of acquisition, rather than organizing it later. The second is to convert judgments that relied on an individual’s experience and intuition into forms that are easy to verify. The third is to reuse data collected once for multiple purposes. For example, instead of stopping at merely measuring location information, if that information can be linked to as-built verification, progress monitoring, updating drawings, and report preparation, you can reduce the waste of repeating the same work multiple times.

From this perspective, it becomes clear what should be started in i-Construction 2.0. Rather than aiming from the outset for large-scale transformations or costly systems, the starting point is to review the four activities that occur on-site almost every day—"measuring," "recording," "checking," and "sharing"—and add the unification of coordinates and rules and the establishment of a sustainable framework.

There is also a common misconception in the early stages of implementation that productivity will immediately improve simply by introducing equipment. However, in reality, what determines the effect is operational practices. Even when using the same equipment, if measurement rules are ambiguous, file management is not standardized, and who is responsible for checking what is not decided, confusion can actually increase. Conversely, if you organize operations and then choose the necessary measures, even a relatively small implementation can greatly reduce the on-site workload.

In short, i-Construction 2.0 is an initiative that should be considered not from “what to buy” but from “which operations to change and how.” The first thing on-site personnel should do is not memorize the overall picture of the system. They should identify at their own worksite which tasks take time, where mistakes and rework occur, and what information is getting stuck. With that perspective, it becomes much easier to make concrete decisions about what to start next.

First Action 1: Review On-Site Measurement Tasks

The most accessible and effective entry point to i-Construction 2.0 is to review on-site "measuring" work. This is because surveying and position verification are involved in many processes—from preparation for construction, checks during construction, and as-built management, to record creation. If this remains inefficient, digitizing other tasks will not lead to overall optimization.

In-field measurement tasks include a variety of situations such as batter boards, setting out, verifying existing conditions, checking the positions of structures, as-built measurement, and confirming the placement of temporary structures. Looking back on these tasks, a surprisingly large amount of time can be spent on "moving", "waiting", "rechecking", and "transcribing". In particular, at sites where measurement results cannot be fully utilized on site and are reorganized later, the same information may be handled multiple times.

The first step in a review is to organize the measurement tasks carried out on site by type. For example, whether it is a daily position check, a weekly as-built verification, or a pre-construction site assessment will change the required accuracy, speed, number of personnel, and recording methods. Trying to do everything the same way is impractical. Conversely, if you organize by purpose, it becomes clear where you should focus efficiency improvements.

The next important point is to make measured values verifiable on-site. With the traditional approach—recording only numbers on-site and checking them against drawings and forms back in the office—errors tend to be discovered late. If position information can be linked to the actual object and verified on-site, omissions or anomalies are more likely to be noticed immediately. This is not just convenient; it directly prevents re-measurement and rework.

Also, when reviewing measurement tasks, it is also important who performs the measurements. If the operation can only be done by experienced personnel, work tends to stop when the responsible person is absent. In line with the i-Construction 2.0 approach, it is desirable that only specialized judgments be handled by experienced staff, and that routine position checks and record acquisition be structured so that on-site personnel can reproduce them under a set of rules. This not only reduces manpower but also eases the training burden.

Furthermore, when reviewing measurement work, it is necessary to clarify the concept of accuracy. On site, people tend to think "the higher the accuracy, the better," but in practice it is important to determine the accuracy required for each purpose. Demanding accuracy that is stricter than necessary increases both time and effort. On the other hand, if the required accuracy is not met, it can cause major problems in downstream processes. Therefore, it is important to document which tasks require what level of accuracy and to choose methods in accordance with those standards.

What is effective in this case is to review the measuring work in four stages: "planning", "implementation", "verification", and "recording." In the planning stage, decide what to measure, at which coordinates, and to what level of accuracy. In the implementation stage, standardize the on-site acquisition methods. In the verification stage, identify abnormalities or deficiencies on the spot. In the recording stage, save the data in a form that is easy to reuse in subsequent processes. When the entire sequence is organized like this, it becomes not just a mere survey improvement but the establishment of a foundation for on-site operations.

There is no need to begin introducing i-Construction 2.0 with grand words. First, identify the measuring tasks you perform on-site every day, and review the parts that "have a lot of rework," "are dependent on people," or "take a long time to record"—this is the most realistic and effective first step.

What to Start With 2: Change Your Record-Keeping to Be Digital-First

A factor that is often overlooked as affecting on-site productivity is how records are kept. It may seem unremarkable compared with surveying or the construction work itself, but in practice record-keeping — such as organizing photos, reconciling with location data, daily work reports, as-built records, progress reports, and internal sharing — occupies a large portion of field staff time. If you are going to advance i-Construction 2.0 on site, the effects will be limited unless you change the structure of these records.

What burdens many sites is that information collected on site is not finalized there but is later reworked into another format. When tasks such as taking photos, writing notes, recording dimensions, and noting locations are carried out separately, someone later has to mentally link “where was this photo taken?”, “what does this number indicate?”, and “which process does this record correspond to?”. It is precisely this linking work that represents a large, often invisible burden.

Changing records to be digitally native is not simply about eliminating paper. It means standardizing the units of record from the start with the explicit intent that they will be used later. For example, if information such as location, object, date and time, work performed, person responsible, and photos are linked, searching and verification in later stages become much easier. Conversely, if each of these items is stored in separate places, people will have to hunt around every time they need to check.

What's important here is not to increase the number of recording formats. When a new mechanism is introduced, additional input screens or reporting formats can end up being added alongside the conventional paper forms. That only increases the burden on-site. What we should aim for is a situation in which information entered or captured once in the field can be used directly for sharing and reporting. To achieve that, it is necessary to minimize and organize "who", "in what situations", and "what to record", and to design the process to reduce duplicate data entry.

Also, how photos are handled is an important point to review. Photos are used extensively on site, but when photographing rules are vague, records tend to become unverifiable later. If the photo subject, shooting direction, linkage to position, file-naming method, and storage location are not standardized, the more photos taken the harder they become to manage. Under the i-Construction 2.0 approach, photos should be treated not merely as evidence but as operational data linked to locations and work processes.

Furthermore, when digitizing records, it is important to reduce the divide between on-site work and office administration. If it takes time for records taken on site to reach the office staff, checks and corrections are delayed. Conversely, if information collected on site is shared quickly, it leads to earlier detection of issues and adjustments to schedules and workflows. This is not merely a matter of information sharing; it is important in that it accelerates on-site decision-making.

On the other hand, when advancing the digitization of records, on-site personnel may raise concerns that "data entry will become cumbersome." That is a legitimate worry. Precisely because of that, it is important not to demand perfect input from the start. First, narrow the fields down to the bare minimum and create rules that prevent users from getting confused. After the system has taken root, it is easier to succeed if you review the fields and workflows as needed.

The purpose of changing how records are kept is not to increase the amount of data. It is to reduce rework, make information easier to explain, easier to verify, and easier to reuse. For on-site staff, the benefits are a reduced burden of creating documents later from memory, less time spent searching for necessary information, and smaller gaps in understanding among stakeholders. These changes, though they may seem small at first glance, will steadily transform the overall quality and speed of work on site.

3 Things to Start With: Establish the Workflow for As-Built Management and Quality Verification

One of the areas where i-Construction 2.0 is most readily experienced on-site is as-built management and quality verification. This is because it is the area where construction results are objectively verified, recorded as evidence, and tied to accountability. It is directly linked to daily progress and has a large impact on rework, so it is also an area where improvement effects are easy to see.

Under conventional as-built management, the flow of measurement, recording, organizing, and report generation is divided into separate stages, and each step takes time. Furthermore, measured values are not immediately compared with design or management standards; in some cases they are organized later and then evaluated. With this approach, problem detection is delayed, and decisions about re-measurement or correction can fall behind. Especially on sites where the schedule is tight, this delay becomes a direct burden.

What is important, then, is to redesign as-built management not as a task of "verifying everything at the end" but as a task of "continuously verifying during construction." In other words, you need to shift from the mindset of producing reports collectively after construction to an approach that performs the necessary checks at each stage of construction and accumulates those results. Doing so makes it easier to address problems while they are still small and reduces the cost of rework.

What site personnel should be aware of first is the priority of items to be checked. If you try to check everything with the same level of detail, the management workload becomes too heavy. The key is to address first those items that are difficult to correct later, that are likely to affect other processes, or that are likely to become points of contention when explaining quality. For example, items that form the basis of construction—such as reference positions, elevations, alignments, slopes, and thicknesses—should be clearly confirmed at an early stage.

Also, to improve the efficiency of as-built management, it is essential to be conscious of its link to design information. On site, design drawings, construction drawings, site conditions, and measured values tend to be handled separately. However, when these are connected only in people's heads, discrepancies occur when the person in charge changes or when multiple people check them. It is important to operate in a way that makes it as clear as possible what each measurement indicates and what it is being compared against.

The same applies to quality checks. Quality is something checked not for the sake of paperwork but to stabilize construction outcomes. However, on some sites the creation of reporting materials becomes the objective, and the actual checks are postponed. The practical value of i-Construction 2.0 lies in making the checks themselves faster, more accurate, and reproducible. In other words, the essence is not to organize documents but to reduce variability in construction quality and to retain records in a form that is easy to explain.

A useful measure here is to standardize the timing of checks. Clarifying which process requires which checks, who performs them, and how thoroughly something must be confirmed before moving on reduces dependence on specific individuals. Operations that rely solely on the experience of on-site staff tend to be more prone to omissions during busy periods. Conversely, if the check points are shared, it becomes easier to maintain a minimum level of quality even when personnel change.

Furthermore, when improving as-built management and quality verification, it is necessary to reassess the granularity of records. Records that are too detailed are difficult to maintain, while records that are too coarse lack explanatory power. It is important to define a necessary and sufficient granularity from the perspective of what information will allow you to explain the construction status later and withstand re-inspection. This is not merely a matter of record-keeping methods; it is also about setting a level of management that can be sustained on-site without undue burden.

Establishing construction outcome management and quality verification is one of the initiatives within i-Construction 2.0 that produces particularly visible results. It reduces rework, shortens verification time, makes reporting easier, and simplifies handovers, so project sites can readily recognize the value of adopting it. For that reason, it's worth tackling early.

First Things to Start With 4: Establish Processes to Reduce Delays in Information Sharing

One of the reasons problems on site escalate is not so much a lack of information itself but delays in information sharing. Even if the necessary information exists, if it reaches the relevant parties late, decision-making and responses will be delayed. If you are advancing i-Construction 2.0 on site, it is essential not only to make data collectable but also to establish operations that ensure the data reaches the people who need it at the time they need it.

On-site work involves people in various roles—construction personnel, surveyors, quality personnel, supervisors, subcontractors, and office staff. Each requires slightly different information, but they all share the common need to grasp the latest status. In practice, however, means of sharing are often dispersed: phone calls, verbal communication, paper notes, personal devices, handwritten drawing revisions, and so on. In that situation, it becomes hard to tell which version is the most up to date, and redundant checks multiply.

The first thing to do to improve information sharing is to distinguish the types of information to be shared. Treating everything the same makes operations cumbersome. For example, information that should be shared immediately and information that can be organized on a daily basis should be handled differently. Information that directly informs on-site decisions, such as positional misalignment or changes in construction conditions, needs to be shared quickly. On the other hand, information organized for periodic reporting can sometimes be compiled at regular intervals.

Next, it's important to make clear who will update information and who will verify it. Even if there is a sharing mechanism, information will become outdated if responsibility for updates is unclear. Conversely, if responsibility for verification is unclear, people won't look at what has been shared. To make it an operation usable in the field, you need to design not just "it's finished once it's entered" but also "who will look at it and how that will lead to decisions." This is simple, but it's a point that is surprisingly easy to overlook.

Also, when sharing information, it is important not to overload people with excessive detail. Staff in the field make decisions in a busy environment, so if the necessary information gets buried it is effectively the same as not sharing it. What matters is that the information needed for decision-making is immediately clear. For example, simply being able to quickly grasp the location, the subject, the nature of the problem, the scope of impact, and whether a response is required can drastically change on-site operations.

In the context of i-Construction 2.0, the purpose of information sharing is not simply to improve communication efficiency. Its aim is to speed up on-site decision-making, reduce differences in understanding, and create a situation where the same explanations no longer have to be repeated multiple times. This makes it less likely that site personnel will be tied up responding to inquiries and providing explanations, allowing them to concentrate more on their core management duties.

Furthermore, it is important that shared information be easy to search later. On-site, situations such as "the same problem occurred at this location before" or "I want to check how this was being shared as of last week" occur frequently. When information exists only in people’s memories or in one-off exchanges, reconfirmation takes time. If it can be managed by linking it to location, subject, date and time, and process, it becomes easier to trace the past history.

Seen in this light, it becomes clear that improving information sharing should start with operational design before introducing advanced systems. What to share, when to share it, who will update it, who will verify it, and where it will be stored. Simply organizing these five points can significantly reduce confusion at the worksite. i-Construction 2.0 is not simply about increasing the amount of data, but about creating a state in which data moves work forward. In that sense, creating operations that reduce delays in information sharing is an extremely important foundation.

What to Start With No. 5: Unify Coordinates and Rules Before Introducing Equipment

When attempting to implement i-Construction 2.0, the first topic that comes up at many sites is the introduction of equipment and software. While establishing those tools is of course important, what should truly be prioritized in field operations is the harmonization of coordinate systems and operating rules. If these remain ambiguous, no matter how convenient the tools are, data will not connect and will likely cause greater confusion.

One common problem that tends to occur on site is that, even though the same object is being handled, each person in charge uses different references or expressions. For example, if one person thinks in site references, another in drawing coordinates, and another manages objects using abbreviations, inconsistencies arise when the information is overlaid. Even if this appears to be a small discrepancy, it broadly affects subsequent processes such as setting out, as-built checks, drawing revisions, and the preparation of materials for discussions.

The reason unifying coordinates is important is not just for surveying. It becomes a common language that connects records, photos, drawings, construction checks, progress management, and so on. If you plan to utilize location information, you need to organize from the start which coordinate system to use, what will serve as the reference point, how to handle elevations, and how to define local on-site rules. If this is left ambiguous, the same numbers can end up meaning different things.

Rules for file names, folder structures, and recorded items are equally important. For example, if different people use different names for the same location, date formats are not standardized, or photos and measurement data are stored in scattered locations, it increases the time required to find them later. What i-Construction 2.0 aims for is not the accumulation of data but making data usable when needed. To achieve that, rules that remain understandable even when personnel change are necessary.

The key point here is not to create overly perfect rules from the outset. Because circumstances differ at each site, overly detailed procedures will actually fail to take hold. First, it is important to prepare basic items such as coordinate systems, the names of objects, date formats, data storage locations, the person responsible for verification, and the required fields in records. Even this alone will considerably organize site information.

Furthermore, the rules need to be documented and shared. Simply conveying verbally that "we've always done it this way" leads to inconsistent interpretations whenever the person in charge changes. Especially on sites where multiple subcontractors or other departments are involved, making the common rules visible—even if brief—is effective. This also helps reduce training costs.

If you rush to deploy equipment, on-site problems tend to arise such as "only people who know how to use it can operate it," "no one can process the data produced," and "it can't be reconciled with existing documentation." Many of these failures stem less from the means themselves than from insufficiently defined prerequisites. If coordinates and rules are standardized, the meaning of the data will be more consistent regardless of which methods are used, and operational flexibility will increase.

From the perspective of site personnel, this is an unglamorous but critically important preparation. Although flashy implementation effects are not readily visible, they pay off later. Standardizing coordinates and rules provides the foundation for reducing information mismatches, conflicting explanations, time spent searching for items, and the effort of reconfirmation. To prevent i-Construction 2.0 from becoming a mere formality, establishing this foundation first is indispensable.

6 Things to Start First: Start Small and Create a Sustainable System

Not only with i-Construction 2.0, a common reason on-site reform fails is expanding too widely at the outset. Even if you ambitiously try to change everything at once, the site is already pressed by daily schedule management, safety management, coordination and consultation work, and ensuring quality. Introducing new operations in a simultaneous, widespread manner increases the burden on site personnel and can result in reverting to the old ways. That is why it is important to start small and build a system that can be sustained.

A sustainable system is not one in which only a specific person works hard. Even if a single person knows the details, an operation that stops when that person becomes busy or is transferred will not last. What matters is creating a state in which the minimum workflow is carried out by multiple people. For example, if roles are clearly divided so that routine location checks are handled by on-site staff and only cases requiring judgment are reviewed by the person in charge, operations on the ground will run more smoothly.

Also, narrowing the implementation theme to one item at a time makes success more likely. For example, start by limiting the initial target to only as-built verification or only current-condition recording—beginning with tasks where the effects are easy to see. Narrowing the scope makes it easier to establish rules, provide training, and carry out reviews. Once results are visible, it becomes easier to expand to other tasks and to gain buy-in on site.

A review mechanism is also important. When you start a new initiative, you need to verify whether it truly reduced the burden on site, improved the quality of records, or sped up information sharing. What matters here is to assess from a practical, not idealistic, perspective. Check whether data entry hasn’t become excessive, whether verification hasn’t become more complicated, whether on-site travel has decreased, whether re-measurements have been reduced, and whether explaining things has become easier. Reviewing from these viewpoints leads to operational improvements.

Furthermore, for continued use, it is also necessary to devise ways to lower the difficulty of training. Systems that require long explanations of how to operate them before they can be used are unlikely to become established in busy workplaces. Operations that are easier to sustain on-site have a clear purpose, short procedures, and are easy to correct when mistakes occur. In other words, being easy to reproduce is often more important than being highly functional.

For on-site personnel, the difference between success and failure of an implementation is determined less by "whether it can be used" and more by "whether it can be sustained." Even if it goes well the first time, it's meaningless if nobody uses it the following week. That's why you should estimate the on-site burden from the outset, set a realistic scope, define clear role allocations, establish concise rules, and incorporate short review cycles.

Starting small is not a passive stance. Rather, it is a practical way to root changes on-site. i-Construction 2.0 is not something that advances on slogans alone; it becomes established gradually through day-to-day work. Reviewing measurement tasks, improving recording methods, organizing as-built management, streamlining shared operational practices, and standardizing coordinates and rules—implementing these initiatives in a realistic sequence will ultimately make a big difference.

Summary: i-Construction 2.0 is an initiative to change the order of on-site operations

When thinking about what to start with in i-Construction 2.0, there is no need to begin with special technologies or large-scale implementation plans. What really matters to on-site personnel is changing the order of daily operations. Instead of measuring everything later in a batch, verify quickly at the moments when it is needed. Instead of recording later from memory, leave records in a form that can be used on the spot. Instead of explaining to stakeholders later, make sure those who need it can check quickly. Revising these sequences is the practical entry point to i-Construction 2.0.

The six items introduced in this article all relate to basic on-site operations. Reviewing measurement work, shifting recordkeeping to be digital-first, organizing the workflow for as-built management and quality checks, reducing delays in information sharing, unifying coordinates and rules, and starting small to create a system that can be sustained. These may seem independent, but they are actually closely connected. Improving one makes it easier to improve the others.

At construction sites, the very busyness makes it difficult to try new things. However, the busiest sites are precisely where invisible losses—rework, searching for things, repeated explanations, and waiting for confirmations—pile up. The value of i-Construction 2.0 lies in reducing those losses and making it easier to run sites with limited personnel. In other words, it is an initiative for the future that also lightens the current on-site burden.

If you are going to start now, it's realistic to begin by choosing one task at your worksite that occurs most frequently and where rework has the greatest impact, and to start improvements from there. For example, small steps such as changing how position checks are done, reviewing how photos are linked to location information, fixing the timing of as-built verification, or standardizing recording rules are sufficient; once that step becomes established on site, it will lead to the next improvement.

And if you want to make on-site position checks and record collection more agile, the idea of using an iPhone-mounted GNSS high-precision positioning device like LRTK is also effective. Without setting up a large, dedicated system, making it easier for site personnel to handle high-precision location information in their daily work makes it easier to revisit the whole process of measuring, recording, and sharing from a point closer to the field. To avoid leaving i-Construction 2.0 as a difficult concept and instead turn it into improvements that actually work on site, starting from such a familiar entry point is a perfectly practical option.