A newbuild has three principals who must agree for years. Managing that relationship is as much a project deliverable as the ship.
Owner, yard and class don't disagree because any of them is being unreasonable, they disagree because their success criteria are genuinely different: the owner wants the vessel in service on the promised date at the promised performance, the yard wants scope and payment milestones that match what was actually agreed, and class wants enough time and information to verify compliance properly regardless of anyone's schedule pressure. A newbuild contract that doesn't anticipate where these interests will collide is relying on goodwill to resolve conflicts that goodwill alone won't settle once real money and real deadlines are involved.
A Realistic Conflict, and How It Actually Gets Resolved
Take a common scenario: the owner requests a late change to a ventilation system layout, the yard assesses it as a variation requiring additional time and cost, and the change also needs re-approval from class since it affects a previously-approved drawing. If the contract's variation procedure doesn't explicitly address how class re-approval time factors into the schedule impact, the yard and owner can reach commercial agreement on cost and still be stuck, because class's own review timeline wasn't part of either party's negotiation. The fix isn't better goodwill, it's a variation clause that explicitly requires any change assessment to include class's estimated re-approval time as a line item, not an afterthought discovered once the commercial terms are already settled.
Where Information Asymmetry Actually Bites
A drawing revision that reaches the owner's technical representative a week before it reaches class, or vice versa, doesn't just create a delay, it creates a situation where one party is making decisions based on information the other hasn't seen yet. This is less often a matter of bad faith than of no single shared source of truth: three parties maintaining their own copies of "the current drawing" independently is how the same nominal document ends up meaning three different things in three different offices.
What a RACI Matrix Is Actually For
A RACI matrix for drawing approval, material inspection, sea trial witnessing and final class certification is genuinely useful, but only if it resolves the specific ambiguities that cause real disputes, who is Accountable for a decision versus who merely needs to be Consulted, and what happens when an Informed party disagrees after the fact. A RACI built as a generic template rather than against this project's actual approval chain (who on the owner's side has sign-off authority, which class surveyor's decisions can be escalated and to whom) doesn't prevent the argument it was meant to prevent.
Where Schedule Pressure and Class Review Genuinely Conflict
An owner and yard both under commercial pressure to accelerate approvals are, structurally, pushing against class's own need for adequate review time, and that tension doesn't resolve by asking class to go faster. It resolves by building class's realistic review windows into the schedule from the start, submitting packages with enough lead time that "faster" isn't the only lever left when a deadline gets tight. A schedule that assumes class turnaround will always be at the fastest end of its normal range is building in a risk that shows up as a "surprise" delay every time it doesn't happen that way.
What Actually Breaks Down Between the Three Parties
- A verbal agreement in a tripartite meeting isn't captured in the minutes the same way by all three parties. Each side leaves with a slightly different understanding of what was actually decided.
- Class is looped in on a design change after the owner and yard have already informally agreed to it. Class's technical concern then reads as an obstacle to a decision that was never really theirs to begin with, rather than input that should have shaped the decision from the start.
- Payment milestones tied to class approval create a dispute when approval is delayed for a reason outside the yard's control. The commercial and technical tracks weren't designed to handle that scenario, so it gets negotiated ad hoc under time pressure.
- A single point of contact is named on paper but isn't actually the person with real decision authority. Queries route through them anyway and stall waiting for someone else's actual approval.
Where Digital Tools Genuinely Help
A common data environment only resolves the information-asymmetry problem if all three parties actually work from it as the single source of truth rather than treating it as one more channel alongside their own internal copies. The value isn't the platform, it's the discipline of everyone actually abandoning their parallel, unofficial version of "the current status."
The owner-yard-class relationship works when the points of likely conflict, class re-approval time on variations, decision authority on each side, how commercial and technical approval tracks interact, are addressed in the contract and governance structure before they're needed, not negotiated in real time under the exact pressure they were meant to prevent.
