Why Senior Management Usually Learns About Contractual Problems Too Late

Every major construction dispute follows a pattern that senior management finds deeply frustrating. When the dispute finally reaches the boardroom, the first question is always the same: "Why are we only hearing about this now?"

The answer is rarely that people were hiding information. It is that the structural incentives, reporting systems and project culture combine to ensure bad news does not travel upward until it is too late to act effectively.

The Optimism Bias

Project teams are under pressure to deliver. Reporting a potential claim or dispute is perceived — often correctly — as reporting failure. The project manager who flags a contractual problem early may be seen as unable to manage the project. The result is a tendency to treat emerging problems as temporary issues that will resolve themselves, rather than escalating them while the company still has options.

Progress Reporting Conceals Commercial Deterioration

Standard project reporting focuses on physical progress, milestones and cost-to-date. A project can be ahead of programme while simultaneously accumulating unvalued variations, unrecovered costs and expired notice periods. The monthly report looks healthy. The commercial reality is deteriorating. Because no one is asked to report on contractual health, no one does.

Contractual Expertise Is Not on Site

Most project teams are technically competent but contractually inexperienced. They do not recognise the significance of a missing notice, an unconfirmed instruction or a procedural failure because no one has briefed them on the contractual consequences. By the time a contract manager or quantity surveyor identifies the problem, the position has already hardened.

The Escalation Path Is Unclear

Even when a team member recognises a problem, it is often unclear who should be told and how. Should it go to the project director? The commercial director? Legal? Without a defined escalation path for contractual risks, issues are discussed informally and never formally recorded. When they finally surface, the trail is cold and the evidence is weak.

What Management Can Do

The solution is not to demand more reporting. It is to change what is reported and how contractual risk is managed.

• Define what must be escalated. Unresolved variations above a threshold, missed notices, unconfirmed instructions, payment shortfalls — these should be reported by exception, not buried in project files.
• Require a contractual-health dashboard. Every monthly project report should include a section on variations, claims, notices, payment exposure and management-flagged risks.
• Brief the team on contractual obligations. Before work begins, the project team should understand the specific notice periods, authority levels and procedural requirements that apply.
• Create an independent escalation channel. A person or function outside the direct project reporting line who can surface contractual risks without being filtered through project optimism.