A construction site may have a general contractor, subcontractors, installers, suppliers, technicians, and specialist crews working at the same time.
All these people collaborate on the same project, but they do not necessarily use the same information flow.
A technical data sheet arrives by email. A change is communicated in a chat. A photograph remains on the crew leader’s phone. A certificate is saved by the office. The supplier keeps a different copy of the documentation.
As long as no one needs to connect this information, the system appears to work.
The problem emerges when someone needs to understand which document is up to date, who should approve it, which company should use it, and which project phase is affected.
That is why construction site collaboration depends on more than people’s ability to communicate.
It also depends on the company’s ability to create a shared environment where documents, roles, and decisions can be found without having to reconstruct them each time.
Better collaboration does not mean communicating more. It means reducing the number of times we have to ask for the same information again.
The problem is not having many stakeholders: it is having many versions of reality
Let us imagine an ordinary material delivery.
The supplier sends a technical data sheet to the technician.
The technician forwards it to the site manager.
The site manager shares it with the crew.
Meanwhile, the office keeps an earlier version and an external company continues using the one it received the previous week.
Everyone has a document.
But not everyone has the same document.
This is one of the main differences between simple sharing and structured collaboration.
Sharing answers the question:
“Did I send you the file?”
Collaboration must also answer:
“Is it the correct one? Who should use it? Who can modify it? What is it linked to?”
The first rule of collaboration: know where to look
It is not realistic to expect email, messaging, and phone calls to disappear.
They are extremely effective tools.
The problem arises when they are also used simultaneously as the definitive archive.
For each construction site, there should therefore be a recognizable source where an authorized person can find the operational information of reference.
This principle is consistent with international information management.
The ISO 19650-1:2018, still current in 2026, defines a framework for information management that includes activities such as exchange, recording, versioning, and organization.
In 2026, the second edition of the standard, ISO/DIS 19650-1, is also under development.
ISO 19650 belongs to a specific information management and BIM framework: using a management platform does not automatically mean applying or complying with the standard.
The principle is nevertheless useful for any company:
shared information must be identifiable, organized, and reconstructable over time.
Collaboration does not mean allowing everyone to modify everything
A project involving multiple companies requires different access levels.
The supplier may need to upload a technical data sheet.
The manager must be able to view it.
The technician may need to review it.
The owner may have no need to work on that individual file.
A collaborative system should therefore distinguish at least between:
- viewing;
- uploading;
- editing;
- managing;
- accessing only relevant areas.
Collaboration works better when each person can do what is needed without automatically gaining access to the entire project.
And an important misunderstanding must be avoided.
Assigning a role or permission within software does not automatically create or modify a legal, contractual, or professional responsibility.
The platform must represent the real organization, not replace it.
The real test comes when another company joins
A process can appear perfectly organized as long as it is used only by the company’s employees.
Then a supplier arrives.
They send their documents by email.
A subcontractor prefers WhatsApp.
A technician uses their own cloud folder.
Within a few days, the construction site once again has several parallel archives.
That is why onboarding an external company should define a few essential pieces of information:
- who the contact person is;
- what information they must provide;
- where it must be entered;
- who can view it;
- how changes are communicated;
- which channel serves as the operational source of reference.
There is no need to provide a fifty-page manual.
The best procedure is the one the new partner quickly understands and can actually use.
It is the same principle we explored in the article dedicated to collaboration among construction companies.
Collaboration can fail even when everyone has received the document
The problem of versions is particularly insidious.
The file is not missing.
There are simply several apparently correct files.
Names such as:
progetto_finale.pdf
progetto_finale2.pdf
progetto_finale_CORRETTO.pdf
are a very simple signal to recognize.
A revision should make it possible to understand at least:
- which version represents the current reference;
- when it was updated;
- who uploaded it;
- who must be informed;
- the reason for the change, if applicable.
It is not necessarily necessary to delete every previous version.
What matters is avoiding a superseded copy being mistaken for the current one.
Chat is perfect for communicating quickly. Much less so for remembering
A photo sent from the field can solve a problem in just a few seconds.
That is one reason messaging is so widely used in construction.
But imagine having to reconstruct that decision six months later.
You need to understand:
- which construction site it referred to;
- what activity it showed;
- who responded;
- what decision was made;
- whether that decision generated a new document or a change.
The solution is not to stop using chats.
It is to establish which important information must leave the temporary conversation and enter the permanent context of the project.
Organizing by phase makes a document easier to understand
A folder with five hundred files is an archive.
It is not necessarily a management system.
A more useful way to organize information is to progressively link it to the real structure of the work.
Construction site → Phase → Document → People → Communications
In this way, a data sheet is not simply a PDF.
It is a document that belongs to a construction site, concerns a specific phase, and must be used by certain people.
This logic also makes handovers easier.
Someone joining the project does not necessarily need to know the history of every previous email to understand where to find what they need.
Why all this also affects productivity
The RICS Construction Productivity Report 2026 shows how coordination continues to have a significant impact on industry performance.
Scheduling, sequencing, and coordination are assessed as high-impact factors for productivity in four of the five regions analyzed, while site management also retains a significant role.
RICS also highlights that no single technology is considered a transformative solution by the majority of the sample.
This is an important point.
Collaboration does not improve because we installed software.
It improves when software reduces the work needed to coordinate people who are already trying to collaborate.
Being digital does not mean having a single source
In 2026, much of the industry already uses digital tools.
The study Deloitte Access Economics / Autodesk — State of Digital Adoption in the Construction Industry 2026 is based on 954 construction and engineering companies in six Asia-Pacific markets.
The research shows that digital adoption continues to accelerate.
However, this makes a new challenge more evident:
it is not enough to digitize each process separately; fragmentation between already digital processes must be reduced.
A company can have several modern tools and still require people to connect information manually.
And it is precisely this invisible connecting work that more integrated management should seek to reduce.
Seven mistakes that make collaboration difficult even with good software
1. Letting everyone choose where to store information
Total autonomy inevitably creates parallel archives.
2. Treating every copy as official
If the version in the chat and the one in the folder have the same operational value, neither is a true source of reference.
3. Giving everyone the same permissions
Collaboration does not mean giving up access control.
4. Sending every notification to everyone
Too many alerts turn even an important message into noise.
5. Asking external companies to learn overly complex procedures
The new partner must be able to quickly understand where to find and where to enter the information concerning them.
6. Completely separating documents and communications
In a few months, it will be difficult to understand why a document was modified.
7. Digitizing without eliminating the old step
If the document is first completed on paper and then manually entered into the new system, we have added technology but not necessarily efficiency.
How to tell whether collaboration is really improving
I would avoid complicated KPIs in the first phase.
On a pilot construction site, I would measure:
- average time to find a document;
- number of requests to resend information;
- number of duplicate versions identified;
- number of times information is requested again from another company;
- time between uploading and verifying a document;
- time needed to reconstruct a change;
- number of tools used to complete a single workflow;
- number of manual steps between the field and the office.
Measure them before changing the process and repeat the same assessment afterwards.
This way, improvement is not described using generic percentages.
It is measured against the reality of your own company.
A 30-day test for better collaboration
Days 1–7 — Document the situation
Choose a construction site with at least one external company or supplier.
Identify where documents, communications, and revisions currently reside.
Days 8–14 — Define five rules
Establish:
- official source;
- main categories;
- version management;
- permissions;
- people responsible for the main workflows.
Days 15–21 — Actually involve a partner
The test must include an external company or supplier.
If the process works only with the people who designed it, it is not yet a collaborative process.
Days 22–30 — Measure
Review the initial indicators and check whether the following have decreased:
searches, resends, duplicates, clarifications, and manual steps.
If the new system has added more operations instead, simplify it before extending it.
Edil-Up: from relationships between companies to collaboration on site
Edil-Up is being developed as a Construction Operating System with the aim of reducing the distance between collaborating companies and the project’s operational information.
Within construction site management, the company can organize the following in the same environment:
- construction sites;
- phases;
- collaborators;
- roles and permissions;
- documents;
- communications;
- attendance;
- basic financial information.
The mobile app also makes it possible to bring part of the workflow directly into the field.
The Edil-Up Network adds a distinctive element: the possibility of bringing the professional relationship between companies closer to subsequent operational collaboration.
The goal is not to force every company to work in exactly the same way.
It is to create an environment in which the information needed for collaboration does not constantly have to be reconstructed through separate systems.
Edil-Up does not replace technical checks, professional responsibilities, or requirements established by applicable regulations.
It organizes the information flow on which those people need to work.
To explore the more specifically document-related aspect, you can also read the guide to managing construction site documents; to compare different tools, consult the construction site management software.
Checklist: is your construction site really collaborating?
- Do all companies know where to find the reference document?
- Is it immediately clear which version to use?
- Do partners know where to send information?
- Do permissions change according to role?
- Do important decisions remain linked to the project?
- Can a new collaborator quickly understand the workflow?
- Do the field and office use the same reference?
- Do we measure requests to resend, searches, and duplicates?
International reference sources
- ISO 19650-1:2018 , international standard on information management concepts and principles in the built environment, confirmed in 2024 and still current in 2026.
- ISO/DIS 19650-1 — Edition 2 , a new edition under development in 2026 dedicated to information management principles.
- RICS — Construction Productivity Report 2026 , international research on the role of skills, coordination, sequencing, and site management in construction productivity.
- Deloitte Access Economics / Autodesk — State of Digital Adoption in the Construction Industry 2026 , a study of 954 construction and engineering companies concerning the sector’s digital maturity.
Conclusion: collaboration means reducing the distance between those who know and those who must act
Construction site collaboration is not measured by the number of messages sent.
It is measured by how easy it is for the right person to obtain the correct information without interrupting three other people.
When more companies join, this ability becomes even more important.
Each new company adds expertise, but it can also add a new archive, a new chat, and a new procedure.
The organization’s task is to prevent information complexity from growing at the same rate as the project.
To do this, a few rules are needed: a recognizable source, understandable versions, clear roles, and a process simple enough to be used even during a demanding day in the field.
Collaboration improves when information belongs not to the person who possesses it, but to the construction site that needs it.
Edil-Up Team
