What skills are needed for i-Construction? Five items practitioners should check

When organizations consider responding to i-Construction, many practitioners first worry about which equipment to buy or which task to start with. Choosing equipment and systems is indeed important, but what really makes the difference in practice is not the individual tools themselves but how one understands the techniques to be used on site and how those techniques are translated into operations. Many people who search for the term i-Construction are not interested in the term as a policy buzzword; they want to know what to look for on site tomorrow and how much preparation is required to be operational in practice.

i-Construction is not merely an effort to digitize surveying nor a scheme that ends once three-dimensional data are created. It is an approach that reconnects the sequence of measuring, creating, constructing, checking, and archiving through data. For that reason, even if you understand needed skills partially, you are unlikely to see benefits unless the preceding and following processes are linked. Conversely, if you grasp the important techniques from five perspectives, you can proceed step by step in ways that fit each site without changing everything at once. This article organizes, from an operational viewpoint, the five techniques practitioners should especially look at to make i-Construction functional on site.

Table of contents

• Organize the skills needed for i-Construction first

• The first skill: the ability to stabilize coordinates and positioning

• The second skill: the ability to create and reinterpret three-dimensional data

• The third skill: the on-site operational ability to translate into construction

• The fourth skill: the ability to verify as-built condition and quality with data

• The fifth skill: the ability to share data and sustain continuous operation

• How to proceed without failing in i-Construction adoption

• Conclusion

• Organize the skills needed for i-Construction first

A common misunderstanding about i-Construction is the idea that introducing one advanced technology will be sufficient. In reality, what is needed are multiple practical techniques that link the site’s preceding and following processes. For example, even if you have a means of measuring position with high accuracy, if the coordinate reference is not unified within the site, discrepancies will appear when comparing with design data. Even if you can create three-dimensional data, if it cannot be properly referenced on site during construction, rework will not decrease. Even if you can verify as-built condition with data, if the method of recording and sharing is ambiguous, you will still struggle with inspection responses.

In other words, i-Construction readiness means making surveying techniques, three-dimensional data utilization techniques, construction support techniques, as-built verification techniques, and data operation techniques work as a single flow. From this perspective, the necessary skills can be broadly organized into five areas. First, the ability to stabilize coordinates and positioning. Second, the ability to treat site and design information as three-dimensional data. Third, the operational skill to convert that data into a form usable on the construction site. Fourth, the ability to verify as-built condition and quality with data and leave supporting evidence. Fifth, the technology for sharing and standardizing to continuously run these processes.

The reason for examining these five in order is clear. Site productivity is determined not by the most expensive equipment but by the weakest process. If positioning is unstable, construction decisions will waver. If reinterpretation of design data is insufficient, the meaning of figures checked on site becomes ambiguous. If record operation is not organized, valuable data will end up as one-off work results. What practitioners should really look at is not cutting-edge technology names but how well these five areas are connected on their own sites.

Also, it is not necessary to master all five skills to the same depth. The emphasis differs for those who operate equipment on site, those who plan construction, those who verify as-built condition, and those who compile documents and data. However, even with different roles, having a minimum common understanding among each person is indispensable. Companies that successfully progress with i-Construction avoid a situation where only specialists understand things and instead translate concepts into practical terminology and share them. That is why it is important to first organize the five skills not as individual functions but as the foundation that moves the whole site.

1st skill: the ability to stabilize coordinates and positioning

The first thing to grasp is the ability to stabilize coordinates and positioning. In i-Construction, on-site location information is the starting point for everything. No matter how well construction planning and three-dimensional data are prepared, if the positions obtained on site fluctuate, subsequent decisions and records will be unstable. What matters in practice is not merely being able to use high-accuracy positioning functions. It includes managing which coordinates are used as the reference, under what conditions measurements are taken, and to what degree of reproducibility the operation can be run.

The greatest pitfall to watch for here is starting operations while the coordinate reference remains ambiguous on site. If the reference on drawings, the reference in design data, and the reference actually used on site do not match, measuring the same point can still produce discrepancies in construction positions and as-built evaluations. Especially on sites with temporary relocations, changing construction phases, or overlapping work by multiple crews, if reference points and verification methods are not documented, differences in judgment among persons in charge will grow. When considering the introduction of high-accuracy positioning, it is essential to prepare not only the stated accuracy of the equipment but also the procedures for establishing control points, checking against known points, re-measurement procedures, and methods for confirming observation environments.

Positioning technology is also strongly influenced by site conditions. The openness of the sky, surrounding structures, communication conditions, radio signal shielding, and weather conditions all affect results even with the same equipment. Therefore, practitioners need the judgment not to take numbers at face value. For example, one needs a quick sense to determine whether a fixed solution has been obtained, whether observations show scatter, or whether there is any inconsistency compared with known points. On-site positioning should not end with a single measurement; the basic operation involves raising reliability through multiple checks and cross-verification under different conditions.

Furthermore, coordinate and positioning knowledge should not be confined to those who measure. Construction supervisors and as-built verification staff must understand which reference determines the position; otherwise they cannot correctly interpret the figures. For instance, a position may appear to match the design under one reference but show a deviation when converted to another. Such confusion arises less from a lack of technical skill and more from a lack of common language. On site, it is important to establish a concise common understanding of coordinate systems, elevation references, observation conditions, and verification rules.

The technology of coordinates and positioning might seem unglamorous, but if this area remains unstable, subsequent three-dimensional data creation, construction support, and as-built verification will not function correctly. What to look for in practice is not whether positioning functions exist but whether anyone on site can reproduce the same position. That reproducibility is the foundation of i-Construction readiness.

2nd skill: the ability to create and reinterpret three-dimensional data

Next is the ability to create, reinterpret, and handle three-dimensional data as information meaningful on site. i-Construction shifts operations from relying solely on two-dimensional drawings to operations premised on three-dimensional terrain, structures, and as-built conditions. That said, what is required here is not producing visually attractive 3D representations. It is preparing three-dimensional data that is sufficiently necessary and usable for on-site decision-making.

In practice, the quality of three-dimensional data is largely determined by how the underlying information is organized. If the point density representing the existing ground surface is insufficient, surface undulations will not be represented correctly. Conversely, if you handle excessively detailed points in an unordered manner, the data becomes heavy and burdensome for on-site use and verification tasks. The important thing is to clarify what the data will be used for. Whether it will be used for construction planning, earthwork calculation, or as-built management changes the required accuracy, point density, boundary representation, and handling of lines. In other words, the skill of creating three-dimensional data is not just collecting points but configuring information according to the purpose.

On site, there are frequent situations where you must go back and forth between two-dimensional drawings and three-dimensional data. If you cannot understand how contents shown on plan, longitudinal, and cross sections are reflected in three-dimensional space, you may be able to create data but still fail to connect it to construction. Conversely, if you only look at the three-dimensional model, you may miss design intent or sectional conditions. Therefore, practitioners need the ability to translate between two-dimensional and three-dimensional representations. It is essential to grasp which height, slope, or edge on site corresponds to the numerical values on the design drawings and to reflect them in the three-dimensional data as necessary.

Also, three-dimensional data is not complete the moment it is created; it requires updates and consistency checks. It is common for the initial data and the current conditions to diverge due to changes in construction conditions, excavation progress, or temporary works. If it is unclear which point-in-time data is the latest, which file is the official version, or what basis was used for corrections, the site will be confused. The skill of handling three-dimensional data thus requires not only creation ability but also operational capability that includes version control and change history.

Moreover, when using photogrammetry-derived measurements or point cloud data, you should not use the acquired information verbatim; you need the perspective to reorganize it into the necessary surfaces and lines. A large quantity of points does not equal ease of judgment. What is truly needed on site are the boundaries of fills and cuts, heights to manage, positions of crest and toe of slopes, and reference positions of structures—information directly linked to construction and inspection. Therefore, the ability to create and reinterpret three-dimensional data is less about increasing information and more about shaping it into a form usable on site.

Once this ability is developed, mistakes in reading drawings, variations in section interpretation, and repetitive hand calculations decrease. The emphasis on three-dimensional data in i-Construction is not for appearances but because it becomes a common foundation for on-site decision-making. Practitioners should not treat three-dimensional data as solely the domain of outsourced or specialist staff; they should aim to at least be able to read the content, detect anomalies, and judge whether it meets the purpose.

3rd skill: the on-site operational ability to translate into construction

The third area to examine is the on-site operational ability to convert positioning and three-dimensional data into actual construction. By operational ability here, we do not mean simply being able to view data; we mean the ability to shape the data so it can be used in the flow of on-site work procedures, construction decisions, safety management, and verification. On sites where i-Construction fails, data exists but workers and construction managers cannot fully use it in the field. Conversely, on sites where introduction succeeds, it’s not so much that they are using complex functions as that it is clear who checks what, when, and in which situations.

For example, even when digitizing stakeout, displaying coordinates alone is not sufficient. On site you need an operational design that specifies which points to verify first, how to avoid the influence of temporary works and obstacles, who approves the verification results, and what re-check procedure to follow if abnormal values occur. Construction always proceeds under time constraints. Therefore, theoretically convenient but operationally complex procedures, too many verification items, or ambiguous responsibility will not become established. In practice, what matters is not the technology itself but whether it has been translated into procedures that can actually run on site.

Also, during construction phases, decisions to reconcile design data and site conditions frequently arise. Even if a design is expressed with a specific slope or height, actual ground conditions, access routes, temporary works layout, and construction sequence can change on-site priorities. In such cases, you must not treat data merely as instruction values but use it in light of on-site conditions. In other words, i-Construction calls not for excessive expectations of automation but for operation that uses data as evidence to improve judgment quality.

This perspective is especially important on small- to medium-scale sites. Where you cannot allocate many dedicated staff as on large sites, people will handle multiple roles while dealing with data. Thus, on-site operational ability does not mean only advanced specialist skills. It includes the ability to establish procedures that are easily reproducible with limited personnel, the ability to explain to align understanding among staff with differing experience, and the scheduling ability to complete pre- and post-construction checks quickly. To put i-Construction into operation, it is more important to create an easy-to-follow workflow than to increase the number of people who can operate the tools.

Furthermore, when translating into construction, attention must be paid to the granularity of the data used on site. Instead of bringing all design information, it is effective to filter and present only the scope needed for that day’s work, the heights and positions to be checked, and the slopes to verify. Too much information increases the chance of oversight or erroneous operation. On-site operational ability is not the technology of increasing information but the skill of making necessary information available where and when it is needed.

On sites with this skill, stakeout rework, missed checks, and differences in judgment among persons in charge tend to decrease. i-Construction is not about competing to introduce advanced equipment; it is about standardizing construction decisions. Therefore, practitioners should evaluate construction operations from the viewpoint of on-site usability, simplicity of verification procedures, and ease of re-checking.

4th skill: the ability to verify as-built condition and quality with data

The fourth required skill is the ability to verify as-built condition and quality with data. In i-Construction, it is important not only to check positions and elevations during construction but also to leave the results as objective records that can be explained later. While as-built and quality checks have been performed on conventional sites, in the digital data era, reproducibility of checking methods and traceability of records are emphasized more than mere measurement accuracy.

First to determine is what to check, in what units, and at what timing. On sites where as-built verification fails, measurement points are ad hoc, measurements are taken too late, or comparison methods with design values are not standardized. As a result, numbers exist but cannot be evaluated, re-measurement becomes necessary, and record consistency cannot be maintained. In practice, it is important to organize whether checks should be done at points, lines, or surfaces for each process and to standardize verification methods.

From a quality verification perspective, numerical agreement alone is sometimes insufficient. For example, even if a point’s elevation is within tolerance, if transitions with surrounding surfaces or the overall feel of the construction surface are poor, the finished result can be problematic. Conversely, local differences may appear but be judged differently depending on measurement conditions or how references are taken. Therefore, the ability to verify as-built condition and quality with data is not merely measurement skill but the ability to read numbers in light of design intent and site conditions.

Equally important is how records are kept. If it is unclear who checked what, when, by which method, and based on which standard, later accountability is difficult. On busy sites, organizing verification data is often postponed. However, in i-Construction it is essential not to separate checking and recording. If you design a system where position information, date and time, target location, responsible person, and verification results are linked at the time of measurement, subsequent document organization and inspection responses change dramatically.

The technology for as-built verification also reduces rework. If defects are found only after completion, the scope of correction and the impact on the schedule increase. If checks are made at appropriate times during construction, deviations can be corrected at an early stage. Thus, the value of data verification lies not only in compiling completion records but also in improving in-process construction decisions. Verification should be positioned not as a final-stage task but as interim management to stabilize construction.

Companies that successfully embed i-Construction in practice do not treat as-built verification as a separate special inspection task; they integrate it into daily construction. If the people who check numbers and those who construct are disconnected, data may be preserved but will not lead to improvement. Conversely, when construction decisions and verification data are linked, both quality and explainability tend to improve. Practitioners should look not at whether things can be measured but at whether verification results are operated in a way that leads to the next decision.

5th skill: the ability to share data and sustain continuous operation

The fifth critical area is the ability to share data and sustain continuous operation. In i-Construction, positioning, three-dimensional data, construction checks, and as-built records are digitized. However, if these remain on individual devices or only in the heads of particular staff, they will not lead to overall site improvement. The real differentiator in practice is not the skill of creating data but the operational skill to ensure the right people can use the necessary data at the right time without hesitation.

First, it is important to align file names, storage locations, update rules, and handling of official versions. If these are ambiguous, multiple “latest” versions can coexist on the same site, causing confusion in construction and inspection. Because data circulates under busy conditions on site, the fewer detailed rules you have, the more likely operations become person-dependent. That is why it is necessary to establish basic sharing rules such as naming conventions anyone can understand, version control that shows when updates occurred, and the idea of separating files for viewing from files for editing.

Next, clarifying the division of responsibilities among personnel is critical. Not everyone needs to handle data at the same depth, but if it is unclear who inputs, who checks, who approves, and who archives, operations will quickly stall. Especially in small- to medium-sized organizations where one person often covers multiple tasks, a simple workflow that assumes overlapping roles is important. To sustain i-Construction operations, you need a system that keeps running even when people change, not one that depends on just the capable few.

Education is also indispensable for continuous operation. Teaching only advanced operations makes it difficult to establish practices on site. Rather, sharing the reasons behind standards—why you measure to that reference, why you save in that format, and why you check at that timing—is important. When reasons are understood, staff can adapt more flexibly if unexpected events occur. Conversely, if only operational steps are transmitted, the moment the person in charge changes, quality tends to decline.

Data-sharing technology is not limited to internal use. When information exchange occurs with subcontractors, clients, or inspectors, the format, granularity, and timing of shared data become important. Abbreviations and conventions understood within the company may not be understood externally. To stabilize i-Construction in practice, it is essential to organize information in a way that recipients can understand.

Thus, the ability to share data and sustain continuous operation may at first appear to be management rather than technical, but in reality this is the part that turns technology into outcomes. Coordinates, three-dimensional data, and as-built records only gain value when they are shared, reused, and applied to subsequent decisions. The fifth item practitioners should look at is often underestimated at introduction, but it is the decisive factor in sustaining effectiveness on site.

How to proceed without failing in i-Construction adoption

All five technologies discussed above are important, but trying to raise them all to a high level at once can hinder adoption. To avoid failure in i-Construction, it is important to sequence implementation and start from areas where your sites are likely to see early benefits. In practice, it is easier to succeed by focusing on one site, one task, or one problem first rather than trying to change all processes from the start.

For example, choosing initial targets such as improving stakeout confirmation efficiency, checking slope heights, intermediate as-built checks, or reducing effort for construction records—tasks where site problems are clearly identified—makes results more visible. If you introduce something with an unclear purpose, using it becomes the purpose itself and only leaves sites feeling burdened. If you clearly define which work time you want to reduce or which rework you want to prevent, it becomes easier to narrow down the necessary technologies. Rather than considering the five skills in parallel, start by improving the technology most directly tied to the problem you want to solve.

Before introduction, it is also important to align on-site standards and terminology. If coordinate references, the official design data version, verification frequency, and storage locations are ambiguous, operations will fluctuate regardless of how convenient the tools are. When introducing new technology, it is effective to simplify basic rules and reduce situations where people hesitate on site. Preparing simple procedure manuals and checklists that are understandable without special knowledge helps reduce variation due to differences in staff experience.

Moreover, indicators for judging introduction effects should be practical. Instead of only checking whether data was acquired, evaluate whether verification time shortened, rework decreased, recognition differences among staff reduced, or the burden of record organization lessened. This kind of evaluation increases on-site buy-in. i-Construction tends to be discussed as dazzling technology introduction, but on sites it is easier to establish as an accumulation of small improvements.

Most importantly, understand that introducing technology and having the technology used on site are different things. It is not only the simplest operations that stick on site. Systems that stick are those with clear purposes, shared decision criteria, easy re-checks, and easy record keeping. What practitioners should look at in i-Construction is not the number of functions but whether the system actually runs on site. Holding that perspective alone will significantly reduce the risk of failed introduction.

Conclusion

The skills needed for i-Construction do not stand alone. Only when there is the ability to stabilize coordinates and positioning, the ability to create and reinterpret three-dimensional data, the operational ability to translate that into construction, the ability to verify as-built condition and quality with data, and finally the ability to share and sustain continuous operation, will site productivity improve. The five items practitioners should look at can be rephrased as: measuring techniques, connecting techniques, using techniques, verifying techniques, and techniques for continuous operation.

For practitioners collecting information under the term i-Construction, it is important not to try to equip every technology at once but to find the entry point that will produce the greatest effect on their own sites. For example, starting by stabilizing high-accuracy position checks, reducing effort from coordinate acquisition to recording on site, or sharing the same reference among multiple staff makes i-Construction practical and approachable.

As an entry point, measures that introduce high-accuracy positioning in an easy-to-handle form on site—such as LRTK (an iPhone-mounted GNSS high-precision positioning device)—are well-suited. They make it easy to start the sequence of capturing coordinates, confirming positions, recording pre- and post-construction conditions, and sharing information among staff without excessive complexity. If you want to bring i-Construction out of desk-based consideration and into a form that is truly usable on site, the most reliable shortcut is to first develop technologies that can run smoothly within daily work.