Introduction
In large EPC projects, especially those governed by FIDIC-based contracts, contractors are constantly required to balance two competing realities. On one hand, there is a genuine obligation to maintain high standards of health, safety, and environmental compliance. On the other hand, there is a growing tendency for employers and clients to use “HSE” as a vehicle to introduce additional systems, technologies, and reporting burdens that were never contractually agreed.
This article is written for contract managers, project managers, and commercial professionals who find themselves facing requests that feel reasonable, well-intentioned, and even urgent — but subtly fall outside the original contractual scope.
The key question is not whether safety matters (it always does), but whether every new “requirement” is actually a contractual obligation or simply a corporate expectation being passed down the supply chain.
The Modern Pattern: Corporate Reporting Disguised as HSE
In many contemporary projects, employers operate sophisticated internal governance platforms — ESG dashboards, safety portals, enterprise risk systems, or centralized reporting tools. These systems require structured data: vehicle tracking, driver behavior analytics, training records, environmental metrics, and real-time performance indicators.
The problem arises when these internal tools are treated as if they are automatically binding on contractors.
Instead of issuing formal variations or new contractual instructions, clients often frame such demands as:
- “Required for HSE compliance”
- “Necessary for audit closure”
- “Mandatory for corporate reporting”
- “Part of best practice”
The language sounds technical, responsible, and non-negotiable. In reality, what is happening is far simpler: the client needs data for its own systems and is attempting to shift the cost and operational burden onto the contractor without formally changing the contract.
This is not always malicious. Often it is driven by internal compliance teams who are not deeply familiar with the project contract. But commercially, the effect is the same: scope creep.
Why This Is Particularly Dangerous Under EPC Contracts
Under EPC or design–build models (such as FIDIC Silver Book), the contractor already carries substantial risk:
- design risk,
- performance risk,
- schedule risk,
- cost risk.
The only real protection the contractor has is the contractual boundary itself.
Once you start accepting obligations that are not written in the contract, two things happen:
- You absorb permanent cost without compensation.
- You weaken your legal position for future claims.
The danger is not the first extra system. The danger is the precedent it creates.
After the first concession, every future demand becomes easier:
another dashboard, another certification, another reporting format, another external audit.
All justified by the same phrase: “It’s for HSE.”
What Contracts Usually Require
Most modern contracts legitimately require:
- Environmental Management Systems (ISO 14001)
- Health & Safety Management Systems (ISO 45001)
- Internal training programs
- Traffic management procedures
- Risk assessments and method statements
- Incident reporting and monitoring
These are framework obligations. They define processes, not technologies.
They tell you what outcomes to achieve, not what tools to buy.
Crucially, they almost never specify:
- GPS tracking systems,
- telematics platforms,
- driver behavior scoring,
- client-owned software portals,
- or external certification regimes.
If a system is not expressly stated, it is not automatically included simply because it feels “reasonable” or “modern”.
Contracts are legal instruments, not evolving corporate wishlists.
The Psychological Trap: Why Contractors Often Comply Anyway
Most contractors do not lose their commercial position because they misunderstand the contract. They lose it because of psychology.
There are three powerful pressures:
- Safety framing — Nobody wants to be seen as “anti-safety”.
- Urgency framing — “We need this for reporting by next month.”
- Authority framing — “This is coming from corporate / head office / the auditor.”
Together, these create a situation where saying “no” feels morally wrong, even when it is contractually correct.
The result is silent acceptance — and silent acceptance is legally fatal.
The Correct Professional Response
Defending contractual boundaries does not require being adversarial.
The correct approach is:
- Partial compliance — Provide everything that is genuinely in scope.
- Formal clarification — Identify what is outside scope.
- Commercial reservation — State that new systems require formal variation.
This keeps the tone cooperative while preserving your legal position.
You are not refusing safety.
You are refusing unpaid scope.
That distinction is fundamental.
The Core Principle Every Contract Manager Must Internalize
The most important lesson is this:
“Corporate governance systems do not automatically become contractual obligations.”
No matter how well-intentioned a requirement is, it only becomes binding if:
- it is written in the contract, or
- it is instructed through formal contractual mechanisms.
Everything else is a business request, not a legal duty.
Why This Issue Will Only Get Bigger
As ESG, sustainability, digital transformation, and real-time reporting become standard across industries, contractors will increasingly face demands for:
- integrated platforms,
- data transparency,
- continuous monitoring,
- behavioural analytics.
These systems are expensive, permanent, and operationally intrusive.
If the industry does not learn to distinguish between:
- contractual compliance and
- corporate convenience,
then contractors will become unpaid data providers for every client governance framework in existence.
Conclusion
The true role of a senior contract manager is not to block progress or resist safety. It is to recognize when a business problem is being presented as a compliance problem.
That moment — when something feels reasonable, urgent, and responsible, yet is not actually written in the contract — is where professional judgment matters most.
This is where contracts quietly fail or quietly protect you.
And in most projects, nobody will ever thank you for holding that line —
except your future self when the claims, audits, and disputes arrive.
(The views and opinions expressed in this article are solely those of the author and do not necessarily reflect the official policy or position of any organization or entity.)
Disclaimer: This article is for general informational purposes only and does not constitute legal, technological, or professional advice. Laws and regulations vary by jurisdiction; readers should consult a qualified professional for advice specific to their situation.
While every effort has been made to ensure the accuracy of the information provided, readers should be aware that information is inherently dynamic. Laws, regulations, technology, etc., may change over time, and the author assumes no responsibility for errors, omissions, or outcomes resulting from the use of this information.
Links to external websites are provided for convenience and do not constitute endorsement.
