Is i-Construction Possible for Small and Medium Construction Companies? 6 Tips for Implementation

When people hear the term i-Construction, many may feel it’s an advanced system only large companies can undertake. While the idea of digitizing the sequence of tasks—surveying, design, construction, inspection, and maintenance—to increase productivity across a site is certainly attractive, for small and medium construction companies that face concerns like “not enough people,” “can’t assign a dedicated person,” “can’t suddenly increase expensive equipment,” or “the site is too busy to adopt new things,” it can seem unrealistic.

In fact, i-Construction does not have to mean a big change from the start. By beginning with parts of current workflows that can be replaced without strain, small and medium construction companies can advance i-Construction sufficiently. The important thing is not to assemble an impressive system all at once. Within a scope that fits the company, improve processes with frequent rework, those prone to being person-dependent, and those that require time-consuming record-keeping, in that order, and gradually change site standards.

Especially at small and medium construction companies, it is common for a limited number of people to manage multiple sites while handling schedule management, safety management, photo management, as-built checks, and coordination with subcontractors. For that reason, the i-Construction approach is not incompatible; rather, it can help mitigate issues like staff shortages and experience dependence. Reducing paper-based exchanges, increasing the amount of information that can be verified on-site, making handling of coordinates and positions easier to understand, and making it easier to keep records are effective regardless of company size.

This article clearly organizes, from a practical viewpoint, whether i-Construction is truly possible for small and medium construction companies. It then explains six practical tips for progressing adoption without overreach and for avoiding failure. It’s presented in a way that makes on-site decision-making easier, for those who want to start now or who are interested but unsure where to begin.

Table of contents

• Why i-Construction looks difficult for small and medium construction companies

• Why i-Construction is possible even for small and medium construction companies

• Tip 1 for introduction: Don’t make the goal too big—focus on site problems

• Tip 2 for introduction: Don’t change all processes at once—start with some tasks

• Tip 3 for introduction: Translate operations into ways the on-site staff can understand

• Tip 4 for introduction: Decide how to use the data before deciding how to create it

• Tip 5 for introduction: Standardize procedures to prevent reliance on specific individuals

• Tip 6 for introduction: Choose equipment that balances labor-saving and accuracy improvements

• Failures small and medium construction companies should avoid during introduction

• Summary

Why i-Construction looks difficult for small and medium construction companies

The main reason i-Construction appears difficult for small and medium construction companies is that the image of adoption is too large. When words like 3D data, positioning, as-built management, digital construction, and remote verification are lined up, it feels like an advanced system that only large sites or companies with specialized departments can undertake. As a result, many decide at an early stage, “It’s impossible at our scale,” and the consideration itself tends to stop.

Also, at many small and medium construction companies, a single person often has multiple responsibilities. It is not uncommon for a site supervisor to handle not only schedule management but also surveying assistance, photo organization, as-built verification, documentation, and coordination with subcontractors. From the site’s perspective, learning a new workflow raises concerns like “won’t this just add more work?” The burden of learning and initial effort tends to be noticed before the benefits of introduction appear.

Moreover, when a site is operating under traditional methods, it can be difficult to share the reasons for change internally. For example, even if handwritten field books, circulating paper drawings, verbal position confirmations, and photo–as-built linking depend on individual staff, as long as veterans manage to keep things running, these do not appear as major issues outwardly. However, when a person changes, differences in quality and speed emerge, checks are missed, and re-surveys or rework increase—these accumulated problems eventually affect management.

Additionally, if adopting i-Construction becomes the goal in itself, companies tend to choose unnecessarily complex systems. The real emphasis should be on solving practical issues—making on-site work easier, speeding up checks, simplifying record-keeping, and reducing labor—but when there is pressure to “start something big,” operations that don’t fit the site can be introduced. This is a common cause of failure.

In short, for small and medium construction companies, the difficulty is not just the technology itself. Misperceiving the scale of introduction, feeling that new operations will increase the workload on busy sites, not verbalizing visible problems, and letting means precede objectives all make the hurdle appear higher than it needs to be.

Why i-Construction is possible even for small and medium construction companies

On the other hand, i-Construction is perfectly possible for small and medium construction companies. In fact, companies that need to run sites efficiently with few people often stand to gain greater benefits from adoption. This is because waste at each step becomes a direct burden in smaller operations. Frequent travel, repeated back-and-forths for checks, re-measuring, time-consuming record organization, and situations where progress stalls without a particular person all have a bigger impact the smaller the company.

The essence of i-Construction is making site information visible, speeding decisions at each step, and reducing rework. Therefore, you don’t need to digitize every process to a high degree; start with parts that will show results. For example, improving the accuracy of layout and status checks, recording photos and positioning information on the spot, performing as-built checks early on-site rather than retrospectively, and reducing reliance on paper drawings to prevent misunderstandings among stakeholders are areas that small and medium construction companies can implement relatively easily.

Small and medium companies also have the advantage of fast decision-making. In large organizations, consideration, approval, training, and operational changes can take time, but in smaller companies internal coordination is typically quicker. Site staff voices reach management more easily, and if a good practice exists it can be rolled out company-wide quickly. This is a major advantage when introducing i-Construction in stages.

Moreover, in an era when securing personnel is difficult, building a system that maintains consistent quality with few people is important. Reducing tasks that require an experienced person to accompany every time, standardizing verification steps, and making it easier to handle positions and records on-site all make it easier for newcomers and younger staff to work. i-Construction is not just about introducing equipment; it is an effort to capture on-site knowledge in a system. With this perspective, the significance of adoption becomes clear for small and medium construction companies.

In short, what small and medium construction companies need is not a large-scale transformation but the accumulation of small digital improvements suited to their operations. Those small steps eventually lead to i-Construction. A realistic, sustainable approach is to start improving the parts that truly trouble the site rather than aiming for perfection from the beginning.

Tip 1 for introduction: Don’t make the goal too big—focus on site problems

The most important point for small and medium construction companies advancing i-Construction is not to broaden the goal too much. If you set a grand objective like “change the whole company at once” or “digitize every site,” the site will brace itself and operations become complicated. Adoption should not start from a grand ideal but from specific problems.

For example, many sites experience time-consuming status checks, multiple returns to the office for coordinate verification, effort to ensure paper drawings match the site, time spent organizing photos, or as-built checks postponed until it causes rework. These are all themes that i-Construction can improve. Conversely, if you act on the notion of “we should implement something new” without identifying concrete issues, the new system tends to go unused after introduction.

Focusing the objective also makes internal explanation easier. To management, you can explain it in terms of productivity improvement and rework reduction; to the site, you can present it as fewer trips, faster checks, and easier record-keeping. It is important to show specifically what will become easier at the action level. Rather than abstract expressions, phrases like “making position checks easier at the site,” “enabling decisions without returning to the office,” and “reducing the number of re-measurements” make understanding easier.

When objectives are clear, it’s also easier to assess the effect of adoption. For example, you can evaluate whether the number of re-measurements decreased, whether time spent organizing photos shortened, whether the number of round-trips for on-site checks decreased, and whether a new person can perform the same tasks—these perspectives allow relatively quick judgment on whether a system fits the site. Even without rigorous numerical control of effects, whether the site burden truly decreased will be sensed. That sense of benefit helps adoption stick within the company.

Because small and medium construction companies must deliver results with limited personnel and time, keeping the initial objective narrow and focused on site problems is the first step to success.

Tip 2 for introduction: Don’t change all processes at once—start with some tasks

A common reason i-Construction introductions fail is attempting to expand the scope too quickly. If you try to change surveying, construction, as-built, inspection, photo management, and report creation all at once, the amount to learn increases and site burden grows. Small and medium construction companies often cannot assign a dedicated promotion person, so aiming for total optimization tends to stall.

Therefore, it is realistic to begin by narrowing the scope to just some tasks. The easiest areas to introduce are those used frequently on site with clear improvement effects. For example, position checks, simple positioning, status assessment, pre- and post-construction records, and support for as-built checks are relatively easy to start with. These tasks impose a heavy burden on site but show immediate effects when improved, which builds internal consensus.

Starting with some tasks also keeps training burdens lower. It is difficult to learn a complex system all at once on site. But if the use case is clear and the scenarios limited, staff can understand more easily. Creating a successful first step reduces resistance when broadening the application later.

Even limited-scope changes make it easy to compare before-and-after differences. For example, work that took time for verification may be shortened, information that used to be circulated on paper becomes easier to share on-site, or linkage of photos and position information becomes simpler—small changes can deliver significant practical value. Accumulating these small improvements eventually leads to productivity gains across the site.

Additionally, site conditions at small and medium companies often vary widely by project. Different work types—land development, roads, landscaping, around equipment, repairs—or different environments will require different workable operations. Thus, instead of setting a single company-wide operation from the start, it’s safer to begin small on a trial site and refine operations through actual use.

i-Construction is not a system to complete all at once. First, reliably improve one task, share the results internally, and then expand to the next process. Following this order is a manageable approach for small and medium construction companies.

Tip 3 for introduction: Translate operations into ways the on-site staff can understand

No matter how good an idea, it won’t stick if the people using it on-site don’t understand it. A commonly overlooked point in i-Construction adoption at small and medium construction companies is that clarity of operation matters more than the system itself. On-site there are many situations requiring quick judgments in short timeframes, and complex operations or multi-step checks are avoided. If only those central to introduction understand the system while the actual users do not, the system becomes merely symbolic.

When designing operations, prioritize making them usable by site staff without hesitation. Simplifying the flow—where it is used, what to check, what to record, who inputs what and when—is essential. Reducing points where judgments differ is more effective for adoption than adding long operation explanations.

For example, even for on-site positioning or position verification, confusion arises if procedures vary each time. It is important to standardize basic actions: what to check on arrival at site, what to prepare before work, whether to record on the spot or整理 later, and who to consult in case of anomalies. These measures help limit quality variability when personnel change.

Also, during training, teaching along the actual work flow is more effective than explaining the theory at length. While “why it is needed” is important on-site, “how it will make current work easier” is even more crucial. Convey the background of introduction but emphasize specific benefits to the people who will use it; this fosters understanding and buy-in.

Small and medium companies often cannot secure sufficient training time. In such cases, aiming for a state where minimum procedures can be reliably performed is more realistic than demanding perfect understanding from the start. There is no need to use all advanced features. Clearly define the scope of on-site use and ensure anyone can perform those tasks consistently.

Introducing i-Construction is more business improvement than pure technology adoption. Whether you can translate operations into a form on-site staff can understand determines whether the practice will continue.

Tip 4 for introduction: Decide how to use the data before deciding how to create it

When talking about i-Construction, attention often focuses on how to create 3D data or position information. However, for small and medium construction companies, producing high-accuracy data alone is meaningless if it cannot be used on-site. What matters is deciding first which data will be used, by whom, in what situations, and for what decisions.

For example, whether you need position information for status confirmation, coordinates for construction checks, or data to assist as-built management will change the types of data required and the operation. If data creation proceeds with ambiguous objectives, the site will not know how to use it and will revert to old methods.

Deciding the data use first avoids unnecessary complexity. For instance, if you only need a quick on-site position check but choose a format that requires excessive information and complex preparation, the preparation burden will outweigh the benefits. Conversely, if the decision purpose is clear, you can narrow the data to what is necessary and sufficient.

When the use is clear, sharing with stakeholders is also easier. If the site supervisor, construction staff, surveying assistant, and management each have different perspectives, the data will exist but won’t be used. For example, the site side may want position confirmation, management may want records, and executives may want to see labor-saving effects. Organizing these differences and deciding what to use on-site first reduces operation drift.

Moreover, small and medium companies usually cannot afford to redo systems repeatedly. That is why concretizing the use early is crucial. Tailoring the initial form to how the site will actually use it reduces later revisions and lowers staff burden.

Data creation is not an end in itself. It is a means to speed site judgment, reduce rework, and simplify record-keeping. To effectively leverage i-Construction in small and medium construction companies, start by working backward from the intended data usage.

Tip 5 for introduction: Standardize procedures to prevent reliance on specific individuals

At small and medium construction companies, experienced staff often support sites, which is a strength but also leads to work dependency on individuals. When introducing i-Construction, it is important not to create a system that only certain people can use. If only a few people understand, operate, and judge, the system won’t function at sites where those people are absent. That undermines continuity despite the initial investment.

What is needed is standardization of procedures. “Standardization” may sound rigid, but it simply means creating a state where “anyone can perform at a consistent quality.” Aligning on-site workflow, check items, recording methods, responses to anomalies, and handover procedures reduces individual dependency.

For instance, even with positioning and location checks, if pre-work checks differ by person, accuracy and recorded content will vary. If how construction records are kept differs by person, they become hard to use later. If the criteria for as-built checks are vague, responses will vary by site. These variances, though small individually, accumulate into quality differences and rework.

The key to standardization is not creating complicated manuals but making procedures instantly understandable on-site. For example, organize the work flow into short steps, fix check items, limit the information to be recorded, and decide mandatory items to confirm during handover. Creating such operational patterns makes it easier to maintain consistent quality despite differences in experience.

Standardization also facilitates training. When training newcomers, inconsistent explanations slow learning, but a clear pattern is easier to remember. Small and medium companies often conduct training on-site due to limited staff. In that environment, having aligned procedures reduces training costs.

The benefit of introducing i-Construction is not only using convenient functions but also stabilizing work quality. If you can create a system that doesn’t depend too much on individual skill, continuous improvement becomes easier for small and medium construction companies.

Tip 6 for introduction: Choose equipment that balances labor-saving and accuracy improvements

Choosing equipment is critical when advancing i-Construction at small and medium construction companies. But what matters is not just high functionality. It is crucial that equipment can actually be used continuously on-site, is manageable by few people, and facilitates simultaneous verification and record-keeping. In other words, select equipment while keeping in mind a balance between labor-saving and accuracy improvement.

On-site work is rarely ideal. There are situations where you need to check while moving, quickly view positions with limited time, make on-the-spot construction decisions, and move to the next task while keeping records. In practice, speed and clarity are required. Therefore, even if a device excels in accuracy, if its operation is too complex it will be difficult to sustain use.

On the other hand, if you prioritize labor-saving alone and neglect accuracy considerations, later verification and correction efforts will increase. For smaller companies, a single rework can significantly impact the schedule, so ensuring necessary on-site accuracy is vital. The key is to assess the accuracy needed for the intended on-site use. By separating situations that require high precision from those that prioritize quick checks, you can create a feasible operation.

Also, consider equipment not as standalone items but within the workflow. It is not enough to perform positioning; you must consider how to verify that information, how to record it, and how to feed it into the next process. If on-site devices, position information, photos, and construction records are managed separately, the workload can actually increase. Configurations that allow handling tasks without interrupting workflow are better suited for small and medium construction companies.

Furthermore, since equipment will be used on-site, ease of handling is directly tied to adoption. Consider whether equipment is easy to carry, quick to prepare, operable by a small number of people, and easy to check on-site. Complex equipment tends to end up used by only a few specialists. Equipment that anyone can handle with fixed procedures will naturally broaden its usage.

Good equipment selection for small and medium construction companies is not simply choosing the highest-performance items. Choose devices that can be used continuously on-site, are easy to operate with few people, secure the necessary accuracy, and improve verification and recording efficiency. With this perspective, adopting i-Construction becomes realistic.

Failures small and medium construction companies should avoid during introduction

There are several failures small and medium construction companies should avoid when advancing i-Construction. The most common is being satisfied with having introduced the system itself. Installing devices or processes alone does not change the site. It only becomes meaningful when the system is actually used on-site, work time and verification methods change, and rework decreases. The worst failure is a system that goes unused after introduction.

Next, starting with aspects unrelated to on-site problems is risky. If attention focuses on flashy systems or advanced operations while daily burdens remain unaddressed, sites will not perceive value. For small and medium companies, reducing daily burdens should come first. Rather than pursuing novelty, start with modest but effective improvements.

Leaving everything to the site is also dangerous. While site staff use the tools, if you leave everything to individual ingenuity the operation will vary. Conversely, deciding operations only from management without understanding site realities also fails. What is needed is a balance: reflect site opinions while defining minimum company-wide standards. If that balance collapses, adoption becomes difficult.

Also, demanding perfection in the early stages is problematic. Trying to use the same practices at all sites from the start makes it hard to accommodate small differences and eventually exhausts the site. It is more realistic to begin within a range that works well and assume improvements will be made while using it. Small starts and iterative refinement suit small and medium construction companies.

Finally, failing to share the effects of adoption is an often-overlooked mistake. Even if one site achieves good results, if those are not shared internally they cannot be expanded. Keep a brief record within the company of which tasks became easier, which checks speeded up, and which rework decreased. This lowers the barrier for the next site’s introduction.

To avoid failures, align the introduction process with practical realities rather than focusing solely on the system. For small and medium construction companies, creating a form that will surely be used within a feasible range is more important than anything else.

Summary

i-Construction is not only an initiative for large companies. Small and medium construction companies can implement it effectively by clarifying objectives, narrowing target tasks, and translating operations into forms that are easy to use on-site. Indeed, companies that must handle multiple tasks with few people often find i-Construction concepts particularly effective against issues such as wasted travel, time-consuming checks, burdensome record organization, and variability due to individual staff.

The important point is not to aim for a large transformation from the start. Identify what truly troubles the site and begin with improvements that directly address those issues. By not overreaching on objectives, starting with some tasks, structuring procedures so anyone can use them, clarifying data usage, reducing reliance on specific people, and choosing equipment and operations that are manageable with few personnel while ensuring necessary accuracy, adoption becomes realistic.

Going forward, for small and medium construction companies to maintain stable on-site capabilities, building reproducible work systems rather than relying solely on experience is indispensable. As a first step, rethinking how to handle position information, how to keep on-site records, and how to streamline verification work is highly effective. Especially when you want to advance site checks and positioning with few people, adopting methods that are easy to use on-site and that facilitate the use of high-accuracy position information will further ease practical i-Construction adoption.

As one option, leveraging an iPhone-mounted GNSS high-accuracy positioning device like LRTK can make it easier to confirm positions on-site while progressing recording and sharing, enabling small and medium construction companies to move digitization forward in a manageable way. Don’t overcomplicate i-Construction—start by steadily reducing one on-site burden, and that steady start will lead to sustainable adoption.