A company can use modern software and still have fragmented management. Documents are in the cloud, the budget is monitored elsewhere, operational communications take place in chats, attendance is tracked with another tool, and some of the information remains in the site manager’s head.
Taken individually, each system may work well. The problem emerges when a company needs to quickly reconstruct the overall situation of a project: who is working, which phase is underway, where the latest documentation is located, what has been communicated, and which information must be shared with a collaborator or another company.
This need is the starting point for the concept of a Construction Operating System.
We are not referring to a regulatory category or a universally codified software standard. We use this expression to describe an operating model in which the main elements of construction work — projects, people, phases, documents, communications and professional relationships — begin to share the same digital context.
The difference from simple management software therefore does not lie in the number of functions available in the menu. It lies in the ability to reduce the steps needed to connect what actually happens on site with the information the company uses to organise its work.
What a Construction Operating System really is
To understand the concept, it can be useful to start with what a Construction Operating System should not be.
It is not simply a cloud archive. It is not a construction-site chat. It is not accounting software, nor is it an app that tries to indiscriminately replace every tool the company already uses.
The goal is to create a shared operating layer in which fundamental information retains its context.
A document belongs to a project. A collaborator has a role. A phase has people involved and an execution period. A communication concerns a specific activity. An attendance record occurs in a particular place and at a precise time.
When these elements are managed in completely separate environments, the company must manually reconstruct the relationships between them. When they share a common structure instead, it becomes easier to understand what is happening.
This is the principle behind a COS: fewer isolated tools, more information connected to the real work.
A global market that continues to seek greater productivity
This topic concerns more than Italy or Europe. The fragmentation of processes, information and tools is an international issue for the entire Architecture, Engineering & Construction sector.
According to McKinsey — How AI is reshaping the future of the AEC industry, global construction output reached approximately $15 trillion in 2025, while the sector continues to show significant room for improvement in productivity.
This makes the target market for a Construction Operating System naturally international.
The target audience mainly includes construction companies, main contractors and organisations that must coordinate multiple projects, people and partners at the same time. It also includes technical practices, project managers, construction managers and specialist contractors that frequently collaborate with other companies.
Company size matters less than organisational complexity. Even a small or medium-sized business with only a few active projects can face a very real fragmentation problem if documents, people and communications exist in different systems.
The problem is not having too little software. It is having too many sources of truth
Digital transformation in construction began some time ago. That does not mean, however, that information has automatically become more organised.
A company may use one platform for documents, Excel for certain financial elements, WhatsApp for coordination, email with clients and suppliers, and a separate app for attendance.
The problem becomes clear when a decision crosses more than one of these environments.
Imagine that a work activity needs to be postponed. The change may affect the planned crew, the supplier, the documents being used, subsequent activities and the project’s financial monitoring.
If each element is updated separately, the quality of the result depends on people’s ability to remember every step.
In an integrated operating system, by contrast, the construction site becomes the context in which the different pieces of information are organised.
From file to context: why information management is central
The need to organise information did not begin with the term Construction Operating System.
The ISO 19650 series addresses the subject of information management in construction and the built environment.
The ISO 19650-1 defines principles for organising and managing information throughout the life cycle of built assets.
A Construction Operating System is not the same as ISO 19650 and should not be presented as an ISO 19650 certification. It does, however, share a fundamental need: ensuring that the right information is organised, identifiable and available to the people who need to use it.
How a Construction Operating System should work in practice
The most useful test is not counting how many features a platform has. It is following a normal working day.
The manager opens the project and finds the information relevant to it. Collaborators have access according to their roles. Documentation is associated with the project. Operational communications remain connected to the context in which they originated. Attendance can be reviewed without manually reconstructing different sheets.
When a new company joins the project, it should not be necessary to recreate the entire information relationship from scratch. When a new phase begins, people and information should be organisable around that phase.
The value increases further when the same environment also makes it possible to maintain professional relationships with companies, suppliers and partners.
This is where the concept moves beyond traditional single-project management software and begins to resemble a true operating system for a construction company.
What the 2026 data tells us about the sector’s digitalisation
The latest figures show an interesting situation: the sector is using more and more technology, but integration remains incomplete.
The report Deloitte Access Economics / Autodesk — State of Digital Adoption in the Construction Industry 2026 analysed 954 construction and engineering companies across six Asia-Pacific markets.
Some 56% use data analytics, 50% use cloud construction management software, and 47% use mobile applications. The figures show how digital tools have become a tangible part of the sector.
The same study also shows that fewer than half of companies report that field teams primarily have real-time access to project data, while approximately one quarter still rely mainly on paper-based systems.
The median number of systems and point solutions used by the companies surveyed also fell from eleven to six.
Six is much better than eleven, but it still represents six potentially different environments in which data can originate, be modified or need to be found.
Only 16% of the companies in the sample also reach the level defined as advanced digital capability.
The figure cannot automatically be extended to the entire world, because the research covers six APAC markets. It is nevertheless a useful snapshot of a problem also found in other international studies: adopting technology is different from truly integrating it into work.
RICS 2026: productivity also remains a people and coordination issue
A Construction Operating System should not be presented as an automatic solution to productivity.
The RICS Construction Productivity Report 2026, based on responses from nearly 3,000 professionals across multiple regions of the world, shows how skills, coordination, planning and site supervision remain central.
RICS also highlights significant fragmentation in how companies measure productivity and the still limited use of external benchmarks.
Technology therefore makes sense when it strengthens people’s work. If it adds unnecessary procedures or forces the site team to duplicate records, it may simply move the problem from paper to screen.
The arrival of AI makes organised data even more important
In 2026, the discussion is no longer only about cloud and mobile.
The report Autodesk — 2026 State of Design & Make: AI Pulse, based on 2,500 global leaders in the Design & Make industries, shows how deeply artificial intelligence has entered organisational workflows.
The most interesting point is that competitive advantage is shifting from access to technology to the ability to integrate it with systems, processes, data and people.
McKinsey also describes a future in which AI systems can act on workflows, requests for information, scheduling and cost analysis.
But an intelligent system can use context effectively only if that context exists.
If the correct document is in one application, the decision is in a chat and the financial data is in a separate spreadsheet, the integration problem remains even with more advanced tools.
A realistic scenario: eight projects, one technical office and a great deal of overlapping information
Consider a company managing eight projects at the same time.
The crews are not always the same, some people work on multiple projects, suppliers change depending on the work, and the technical office must maintain visibility across all projects.
In fragmented management, there is not necessarily one single major problem. Instead, dozens of small steps accumulate: asking where a document is, checking who is present, retrieving a communication, updating someone who was not in the original conversation, or reconstructing the status of a phase.
By progressively bringing these elements into the same operating context, the manager does not eliminate the complexity of the construction site. They do, however, reduce the work needed to reconstruct it.
This is one of the most realistic promises of a Construction Operating System.
Five rules for introducing a COS without creating more work
1. Start with one or two projects, not the entire company
The platform must be tested on real activities. A pilot project makes it possible to discover which steps work and which need to be simplified before extending the method.
2. Choose the problems first, then the features
“We want to digitise the company” is too general an objective. It is better to start with observable problems: documents that are difficult to find, unclear responsibilities, scattered communications or difficulty knowing who is present.
3. Avoid permanent double handling
During the transition, it may be necessary to maintain the old and new processes together. If this phase continues indefinitely, however, digitalisation doubles the work instead of reducing it.
4. Design roles and permissions around how work is actually done
The site manager, collaborator, partner company and administration do not need the same information or the same permissions. The system must respect this difference without becoming complicated.
5. Measure before and after
Before introducing the new method, it is worth measuring several indicators. After a few weeks, repeat the same observation.
Without a comparison, even a real improvement risks remaining a mere impression.
How to tell whether the Construction Operating System is working
Dozens of KPIs are not necessary. For an initial assessment, very simple indicators may be sufficient:
- average time needed to find an important document;
- number of requests to resend files;
- time needed to reconstruct the status of a phase;
- percentage of collaborators who actually use the new process;
- problems caused by outdated information;
- time used by the office to respond to requests that the site team could resolve independently;
- number of different tools needed to complete a normal operational workflow.
The goal is not to reach zero immediately. It is to verify that the direction is right and that the new system is actually reducing friction.
How Edil-Up interprets the Construction Operating System
Edil-Up was created with the goal of progressively connecting two areas that are often managed separately in the sector: operational work and the professional network.
In the management area, projects, phases, collaborators, roles and permissions, documents, communications, basic budgets and attendance can be organised in the same environment.
In the Network area, meanwhile, companies in the sector can build their profile, find other businesses, publish listings, connect and develop professional relationships.
The COS logic emerges when these two worlds move closer together: a company discovered through the network can become an operational partner, while a collaboration formed around a project can remain part of the company’s professional network.
This distinguishes Edil-Up’s vision from that of simple software dedicated to a single function.
Those evaluating the tools available can explore the comparison in the guide to construction management software or consult the alternatives for construction management.
For more on information management, it is also useful to explore the method for organising construction-site documents.
A COS does not necessarily have to replace everything the company uses
A company may already have accounting software, BIM tools, administrative procedures or specialist systems that work well.
In that case, the goal should not be to change technology simply to have a single logo on the screen.
An effective Construction Operating System should focus on the operational level and reduce discontinuities between the tools that still need to exist.
The most useful question is therefore: where is the data entered, who needs to use it, and how many times must it be copied before reaching the right person?
If a platform reduces those steps, it is creating integration. If it merely adds another record, it is creating a new silo.
International reference sources — 2026
- RICS — Construction Productivity Report 2026 , international analysis of productivity in the construction sector.
- Deloitte Access Economics / Autodesk — State of Digital Adoption in the Construction Industry 2026 , research into digitalisation among construction and engineering companies.
- McKinsey & Company — How AI is reshaping the future of the AEC industry, 2026 , international analysis of productivity, workflows, data and AI in AEC.
- Autodesk — 2026 State of Design & Make: AI Pulse , research on AI adoption in the Design & Make industries.
- ISO 19650-1 — Information management using BIM , international standard on principles for organising and managing information in the built environment.
Conclusion: the next leap is not having more software, but making it work around the same project
The construction sector does not need to turn every activity into technology.
It needs to reduce the number of times a person must interrupt their work to find out where information is, who is responsible for it or what has changed since the previous day.
This is where the concept of a Construction Operating System gains meaning.
Not as a promise to automate everything, but as a structure capable of holding together the company’s operating context: projects, people, documents, communications and relationships.
When these elements stop being independent fragments, digital tools genuinely begin to reduce complexity instead of merely moving it from one tool to another.
The Edil-Up Team
