A construction project is a joint effort between parties whose interests are not always the same. The owner wants the building on time and on budget. The consultant must administer the contract fairly. The contractor needs to be paid for the work and the time. Subcontractors need approvals and payment. Good projects are the ones where these parties can work from the same facts, even when they disagree.
Why collaboration usually breaks down
- Each party keeps its own registers, so the first part of every meeting is reconciling lists.
- Items wait in someone's inbox and nobody knows whose turn it is.
- Information is shared by email attachments, so everyone has a different version.
- Companies are rightly afraid of exposing their commercial information to the other side.
One project, every party, the right access
In Quanto Management, the company that runs the project invites the owner, the consultant, subcontractors and viewers by link. Invited parties join that project free. Access is set by party and level (view, edit, approve), and each party gets its own home page and "waiting on you" list.
Collaboration does not mean exposure:
- Contractor-only information, such as orders, costs, margins, cheques and suppliers, is never shown to the owner or the consultant.
- Drafts stay with the company that wrote them until they are sent.
- Answers from the AI Assistant respect each party's access.
What each party sees
- The owner sees progress, variations awaiting approval, certified payments and the final account forecast on its own dashboard, without waiting for a monthly report.
- The consultant sees submittals, inspection requests and RFIs to review, payment applications to certify line by line, and the contract clocks that apply to the Engineer.
- The contractor runs the project: contract, BOQ, valuations, procurement, cost, programme, site records and letters.
- Subcontractors work on their own part of the project, with their submittals and approvals.
Clear turns, fewer arguments
When every item shows who is holding it and by when, collaboration stops depending on reminders and phone calls. A variation moves from submitted, to reviewed by the consultant, to approved by the owner, with every step dated and named. An instruction is answered by the contractor as no cost, variation or disputed. A letter carries a reply-by date and a read receipt.
Disagreements still happen; that is the nature of contracts. But they become disagreements about the merits, not about whether a document was received or which version is current.
Languages that suit the team
On Gulf projects, the owner's team, the consultant and the contractor often work in different languages. Quanto shows every screen in Arabic and English, and each user chooses their own, while everyone works on the same record.
Tomorrow: never missing a deadline, with contract clocks under any form of contract.
Follow Quanto for a new article every day: LinkedIn · X · YouTube · Instagram · Facebook