The real problem is not authority—it is how authority is used
Construction contracts need defined roles. Someone must instruct, certify, approve, assess and decide. Removing those responsibilities would create uncertainty rather than collaboration.
The difficulty arises when control becomes an end in itself: information is withheld, decisions are delayed to preserve leverage, instructions remain ambiguous, or every issue is treated as a test of contractual dominance. The project then pays for the appearance of control through disrupted sequencing, defensive records and claims.
Decision latency creates delay
A decision can be contractually correct and still arrive too late to protect the programme. Project teams should therefore manage decision dates with the same discipline applied to construction activities.
Design approvals, access releases, variation instructions, material selections and mitigation proposals should identify the date by which the decision is required, the activities affected and the consequence of missing that date. This creates transparency without predetermining liability.
A party can retain contractual authority while committing to timely, evidence-based decisions and transparent escalation.
Collaboration does not mean giving up rights
Collaboration is sometimes criticised as vague or commercially naïve. Properly implemented, it does not require parties to surrender notices, valuation rights, extension-of-time provisions or access to formal dispute resolution.
It requires the parties to distinguish operational resolution from final entitlement. Work can proceed under an interim instruction, agreed assumption or reserved position while the contractual consequences are assessed separately.
What collaborative behaviour looks like under a traditional contract
- A joint risk and decision register linked to programme dates.
- Early-warning meetings focused on mitigation rather than blame allocation.
- Agreed factual chronologies and shared access to relevant project data.
- Clear authority matrices and escalation periods.
- Interim directions where waiting for final agreement would cause greater loss.
- Without-prejudice discussions for genuine settlement, kept distinct from routine project administration.
- Targeted independent review where technical disagreement is preventing a decision.
Control can suppress useful information
Teams stop raising problems early when they expect the information to be used against them. Risks then remain hidden until they are unavoidable, by which time the available solutions are fewer and more expensive.
Leaders should reward accurate early reporting, even where the information is uncomfortable. A project cannot manage a risk it refuses to acknowledge.
Collaboration must be supported by governance
Goodwill is not enough. Collaborative projects need meeting structures, decision deadlines, reliable records, common data and a defined escalation ladder. They also need individuals capable of challenging their own organisation's preferred narrative.
The contract can reinforce those behaviours. Singapore's BCA identifies collaborative contractual provisions, the PSSCOC collaborative contracting option module and NEC4 as available approaches, together with early contractor involvement and appropriate training.
A contract cannot compensate for the wrong behaviour
A collaborative form may create better mechanisms, but no form can guarantee collaboration. Parties can administer NEC4 defensively or use a traditional form constructively. The difference lies in capability, authority, trust and consistent conduct.
Equally, collaborative language should not be used to pressure a party into accepting unsubstantiated entitlement. Evidence and contract compliance remain essential.
Final thoughts
The party with authority does not become weaker by using it transparently and promptly. It becomes more effective. Collaboration reduces uncertainty by putting risks, decisions and consequences into the open while there is still time to act.
Construction projects are not delivered by contractual power alone. They are delivered through thousands of coordinated decisions. The most successful leaders use authority to make those decisions happen—not to prevent the conversations required to reach them.