Why Structural Quality Is A Fiduciary Duty For Corporate Directors
Fiduciary duty is a phrase that lives comfortably in the language of finance. Directors are told, correctly, that they owe a fiduciary duty to act in the best interests of the company and its shareholders, to exercise reasonable care and diligence, and to avoid conflicts of interest. What is far less commonly discussed is that for directors of construction, real estate, and infrastructure companies, fiduciary duty extends squarely into a domain that sounds, at first, purely technical: whether the buildings and structures the company delivers are actually, physically sound.
Structural integrity is not a subject most boards think of as a governance matter. It sits, in most organizational charts, safely within the domain of design engineers and quality control teams. This article argues that this framing is a mistake. Ensuring adherence to structural codes like IS 456, the Indian standard governing plain and reinforced concrete, is not merely good engineering practice delegated downward. It is a direct expression of a director’s fiduciary duty, with legal consequences that follow directors personally when that duty is neglected.
What Fiduciary Duty Actually Requires, Applied to Structural Risk
Fiduciary duty requires directors to act with the care, skill, and diligence a reasonably prudent person would exercise in the same position, and to act in good faith in the interests of the company as a whole. For a company whose core business is designing and constructing physical structures that people will live in, work in, and depend on for safety, this duty cannot be meaningfully discharged while treating structural integrity as someone else’s technical concern, entirely outside the board’s own sphere of responsibility.
Codes like IS 456 specify minimum reinforcement ratios, permissible stress limits, cover requirements to protect steel from corrosion, and quality control procedures for concrete mix design and testing, calibrated through decades of engineering research and, in many cases, hard lessons from previous failures. A structural failure, when it occurs, is very often a failure to adhere to requirements that were already known, documented, and codified — which means the relevant governance question is not whether the risk was foreseeable, but whether the organization had genuine systems in place to ensure the code was actually followed.
A director who approves aggressive project timelines without asking whether they allow for proper concrete curing periods mandated by code, or who receives quality assurance reports without genuinely engaging with what they contain, is not exercising the level of care fiduciary duty requires — even without a personal engineering background, because fiduciary duty does not require technical expertise, only genuine, informed oversight.
LEGAL PERSEPECTIVE“Courts don’t expect directors to personally check rebar spacing. They do expect directors to be able to demonstrate that the company had a genuine system for ensuring code compliance, and that the board had real, not nominal, oversight of that system. The gap between those two things is where liability lives.”
— a senior advocate who has handled construction liability litigation
Why Structural Quality Often Escapes Board Attention
Structural design and quality control are technically dense subjects, and boards, quite reasonably, delegate detailed technical review to qualified engineers and consultants. The problem is not delegation itself, but the frequent absence of any board-level mechanism to verify that delegation is functioning as intended.
Project reporting to boards tends to emphasize schedule and cost performance, because these are the metrics most directly visible to investors. Structural quality assurance, by contrast, often surfaces at board level only as a compliance checkbox — a confirmation that certification was obtained — without the underlying data genuinely reaching board scrutiny. This creates a governance blind spot that is entirely invisible until a failure occurs.
There is also a subtler pressure: structural quality control, done properly, sometimes conflicts directly with schedule and cost pressure — additional curing time, a rejected batch of steel, additional piling based on updated geotechnical data. In organizations where commercial pressure dominates without a genuinely empowered technical voice at a senior level, there is a structural incentive to treat code compliance as a target to be minimally satisfied rather than a threshold that protects lives.
LEGAL PERSEPECTIVE“In almost every failure case I’ve reviewed, somewhere in the documentation, there’s a memo or an email where an engineer flagged a code deviation and asked for more time or budget to address it properly. The failure wasn’t a mystery to everyone in the organization. It was a known risk that lost an internal argument about schedule.”
— a structural engineer who has served as an expert witness in building failure investigations
The Specific Role of Codes Like IS 456 in Governance
IS 456 and similar structural codes deserve particular attention because they are not simply best-practice guidelines; in most Indian jurisdictions, compliance with relevant structural codes is a legal requirement tied to building approvals, occupancy certificates, and the professional liability of the certifying structural engineers. This means code compliance sits at the intersection of engineering practice and legal obligation in a way that gives boards a genuinely actionable governance lever: the code itself defines, with considerable specificity, what “reasonable care” looks like in a structural context.
Directors do not need to develop independent engineering judgment about reinforcement ratios or deflection limits. They need to ensure the organization has genuine, verifiable systems confirming designs are checked against code requirements, that construction quality control verifies compliance during execution, and that any deviations are documented, justified by a qualified structural engineer, and reviewed with appropriate seniority.
What Genuine Board-Level Oversight Looks Like
Independent structural design review, separate from the original design team, for significant projects — with the board informed of what, if anything, it flagged.
Aggregated site-level quality control data — concrete cube test results, steel mill certificates, reinforcement inspection records — reviewed at a frequency proportionate to project risk.
A clear escalation and sign-off process for any documented code deviation, reaching a level of seniority appropriate to the risk, with the board informed of significant deviations before, not after, a failure.
Genuine independence for structural quality assurance, treated the way boards treat financial audit — with a reporting line that reaches senior leadership without being filtered by the same management structure under schedule pressure.
A Closing Thought
The language of fiduciary duty can feel abstract when discussed in the context of governance training, disconnected from the physical reality of what a construction or real estate company actually produces. But for directors of companies whose core output is buildings that people will occupy, structural integrity is not a peripheral technical concern sitting outside the scope of that duty. It is one of the most direct, consequential expressions of it.
A director who ensures the organization has genuine, verifiable systems for structural code compliance, who asks pointed questions when quality data suggests a gap, and who insists that schedule and cost pressure never silently override a legitimate structural concern, is doing exactly what fiduciary duty has always required: exercising informed, diligent oversight of the risks that matter most — which, for a company that builds structures, begins and ends with whether those structures are genuinely, verifiably sound.
