Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Public Health, Safety, and Welfare–Climate Change Induced Conditions
Step 4 of 5

199

Entities

8

Provisions

2

Precedents

16

Questions

17

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's duty begins as an internal advisory obligation to Client B (propose specialized analysis, advise of concerns under III.1.b). When Client B refuses to authorize the costly hydrologic study, the Board transfers the operative obligation away from the client relationship entirely: Engineer A no longer bears responsibility for compelling the client's assent, but instead must document the concern for 'regulatory agencies and the public,' who become the new bearers of decision-making responsibility for whether further action is warranted.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (8)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

I.1 board + analysis Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 24)
Obligation
Engineer A Public Safety Duty
This obligation directly restates the paramount duty to protect public safety health and welfare
Action
Flood Risk Judgment
Assessing flood risk directly concerns public safety and welfare
State
Upstream Homes Flood Exposure
Public safety is directly endangered by unaddressed upstream flooding risk
Obligation (3)
  • Engineer A Public Safety Duty
    This obligation directly restates the paramount duty to protect public safety health and welfare
  • Engineer A Public Safety Duty Beyond Law
    This obligation extends the paramount safety duty beyond mere legal compliance
  • Engineer A Future Conditions Duty
    Considering future climate impacts is necessary to uphold paramount public safety
Action (3)
  • Flood Risk Judgment
    Assessing flood risk directly concerns public safety and welfare
  • Client Directive Issuance
    Directives that risk safety must be evaluated against paramount public welfare duty
  • Project Withdrawal
    Withdrawing from a project may be necessary to uphold paramount safety obligations
State (6)
  • Upstream Homes Flood Exposure
    Public safety is directly endangered by unaddressed upstream flooding risk
  • Unquantified Upstream Flood Risk Awareness
    Paramount duty to public welfare requires addressing known but unquantified flood risks
  • Outdated Climate Design Standards
    Using outdated standards threatens public safety amid changing climate conditions
  • 25-Year Storm Design Requirement
    A minimal legal storm standard may not protect public safety under changing conditions
  • Foregone Flood Analysis
    Skipping flood analysis risks public safety and welfare
  • Changing Climate Dataset Condition
    Emerging climate data implicates public safety obligations beyond old standards
Constraint (2)
  • Engineer A Flood Analysis Suppression
    Suppressing flood impact analysis conflicts with holding public safety paramount
  • Engineer A Legal Ceiling Prohibition
    Public welfare obligation exceeds mere legal compliance under this provision
Principle (3)
  • Public Welfare in Tidal Crossing
    The provision requires holding public safety paramount which directly matches the flooding risk judgment
  • Public Welfare Paramount Beyond Law
    The provision establishes public welfare as paramount regardless of legal minimums
  • Climate Change Standards Responsiveness
    Addressing evolving climate risks to protect public welfare aligns with this provision
Role (1)
  • Engineer A Consulting Engineer
    Engineer A must hold paramount the safety of the upstream homeowners affected by flooding risks
Event (2)
  • Ongoing Climate Change
    Engineer must consider public safety implications of changing climate conditions
  • Historical Dataset Shift
    Public safety depends on using accurate current data rather than outdated historical datasets
Capability (4)
  • Engineer A Risk Assessment
    Identifying flood risk to homes directly relates to protecting public safety and welfare
  • Engineer A Risk Disclosure
    Disclosing safety risk to client upholds paramount duty to public safety
  • Engineer A Professional Judgment
    Judging future flood risk to homes reflects prioritizing public safety
  • Engineer A Evaluation Threshold Judgment
    Deciding flooding risk merits further study reflects paramount concern for public welfare
I.4 board + analysis Act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 11)
Obligation
Engineer A Client Engagement Disclosure Duty
Faithful agency requires engaging the client with full disclosure of risks
Action
Project Scope Acceptance
Accepting scope implicates the duty to act as a faithful agent to the client
State
Engineer A Engagement By Client B
Engineer must act as faithful agent to the client in this engagement
Obligation (2)
  • Engineer A Client Engagement Disclosure Duty
    Faithful agency requires engaging the client with full disclosure of risks
  • Engineer A Regulatory Report Proposal Duty
    Proposing a report to the client reflects faithful agent responsibilities
Action (2)
  • Project Scope Acceptance
    Accepting scope implicates the duty to act as a faithful agent to the client
  • Client Discussion Engagement
    Discussing concerns with client reflects faithful agency responsibilities
State (2)
  • Engineer A Engagement By Client B
    Engineer must act as faithful agent to the client in this engagement
  • Directive To Proceed Without Analysis
    Faithful agency requires balancing client directives with professional duties
Constraint (1)
  • Engineer A Flood Analysis Suppression
    Client directive to skip analysis conflicts with faithful agent duty when public safety is at risk
Principle (1)
  • Loyalty to Client B
    The provision requires faithful agency to the client which matches this entity directly
Role (1)
  • Engineer A Consulting Engineer
    Engineer A owes faithful agency duties to Client B while designing the project
Capability (2)
  • Engineer A Risk Disclosure
    Bringing risk to client fulfills faithful agent duty to inform client of material issues
  • Engineer A Engineering Design
    Acting as faithful agent while performing design work for the client
II.1.a board + analysis If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
How this applies in the case (showing 3 of 12)
Obligation
Engineer A Regulatory Report Proposal Duty
Notifying other authorities aligns with reporting concerns when judgment is overruled
Action
Client Directive Issuance
If judgment is overruled by this directive, notification obligations are triggered
State
Directive To Proceed Without Analysis
Engineer must notify appropriate authority if judgment to analyze risk is overruled endangering property
Obligation (2)
  • Engineer A Regulatory Report Proposal Duty
    Notifying other authorities aligns with reporting concerns when judgment is overruled
  • Engineer A Conditional Withdrawal Duty
    Withdrawal is the appropriate action when engineering judgment is overruled endangering public safety
Action (3)
  • Client Directive Issuance
    If judgment is overruled by this directive, notification obligations are triggered
  • Concern Documentation Proposal
    Documenting concerns supports notifying appropriate authority when overruled
  • Project Withdrawal
    Withdrawal may follow when overruled judgment endangers life or property
State (3)
  • Directive To Proceed Without Analysis
    Engineer must notify appropriate authority if judgment to analyze risk is overruled endangering property
  • Foregone Flood Analysis
    Overruling need for flood analysis endangering property triggers notification duty
  • Upstream Homes Flood Exposure
    Endangerment of upstream properties requires notification if engineer's concerns are overridden
Constraint (1)
  • Engineer A Flood Analysis Suppression
    If overruled on necessary analysis endangering property, engineer must notify appropriate authority
Role (3)
  • Engineer A Consulting Engineer
    Engineer A must notify Client B and appropriate authorities if judgment on flood risk is overruled
  • Client B Developer Client
    Client B is the party who overrules Engineer A's judgment and must be notified
  • Applicable Regulatory Authorities
    These authorities are the other appropriate bodies Engineer A may need to notify
II.2.a board + analysis Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.
How this applies in the case (showing 3 of 10)
Obligation
Engineer A Sufficient Understanding Duty
Engineers must be qualified with sufficient technical understanding before undertaking such assignments
Action
Project Scope Acceptance
Engineer must only accept scope within their qualified expertise
State
Engineer A Sufficient Understanding
Engineer must be qualified and possess sufficient understanding of climate impacts to undertake the assignment
Obligation (1)
  • Engineer A Sufficient Understanding Duty
    Engineers must be qualified with sufficient technical understanding before undertaking such assignments
Action (2)
  • Project Scope Acceptance
    Engineer must only accept scope within their qualified expertise
  • Specialized Analysis Proposal
    Proposing specialized analysis relates to ensuring qualified expertise is applied
State (2)
  • Engineer A Sufficient Understanding
    Engineer must be qualified and possess sufficient understanding of climate impacts to undertake the assignment
  • Climate Impact Evaluation Gray Area
    Undertaking climate-related assignments requires appropriate qualification amid uncertain technical areas
Constraint (1)
  • Engineer A Modelling Expertise Limit
    Defines the qualification boundary for undertaking hydrologic modelling assignments
Principle (1)
  • Sufficient Understanding for Specialized Evaluation
    The provision requires qualification by education or experience matching the need for technical understanding
Role (1)
  • Engineer A Consulting Engineer
    Engineer A must be qualified in hydrologic and hydraulic analysis to assess flood impacts
Capability (2)
  • Engineer A Interdisciplinary Understanding
    Possessing sufficient competence across hydrology and coastal modeling justifies undertaking the assignment
  • Engineer A Standards Currency
    Staying current with evolving procedures supports qualification to perform the assignment
II.3.a board + analysis Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.
How this applies in the case (showing 3 of 12)
Obligation
Engineer A Regulatory Report Proposal Duty
Proposed reports must be objective truthful and include all relevant information
Action
Flood Risk Judgment
Judgment must be objective, truthful, and include all pertinent flood risk information
State
Foregone Flood Analysis
Objective and complete reporting requires including relevant flood risk information
Obligation (1)
  • Engineer A Regulatory Report Proposal Duty
    Proposed reports must be objective truthful and include all relevant information
Action (2)
  • Flood Risk Judgment
    Judgment must be objective, truthful, and include all pertinent flood risk information
  • Concern Documentation Proposal
    Documenting concerns requires objective and complete reporting
State (3)
  • Foregone Flood Analysis
    Objective and complete reporting requires including relevant flood risk information
  • Unquantified Upstream Flood Risk Awareness
    Truthful reporting requires disclosing known but unquantified risks
  • Outdated Climate Design Standards
    Reports should note when design standards are outdated relative to current data
Principle (1)
  • Evolving Standards in Hydraulic Evaluation
    The provision requires objective truthful reports based on current relevant information matching the evaluation basis
Role (1)
  • Engineer A Consulting Engineer
    Engineer A must be objective and truthful in reports regarding flood risk impacts
Event (2)
  • Conference Procedure Presentation
    Presentation must be objective and truthful with dated relevant information
  • Historical Dataset Shift
    Reports must disclose that historical data may no longer reflect current conditions
Capability (2)
  • Engineer A Risk Assessment
    Characterizing the risk requires objective and complete technical reporting
  • Engineer A Risk Disclosure
    Proposing further analysis and disclosing findings requires truthful and complete reporting
II.3.b board + analysis Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter.
How this applies in the case (showing 3 of 6)
State
Climate Impact Evaluation Gray Area
Public technical opinions on climate impacts must be founded on adequate knowledge and competence
Role
Engineer A Consulting Engineer
Engineer A may publicly express technical opinions on flood risk based on competence
Event
Conference Procedure Presentation
Public technical opinions expressed at the conference must be founded on facts and competence
State (2)
  • Climate Impact Evaluation Gray Area
    Public technical opinions on climate impacts must be founded on adequate knowledge and competence
  • Changing Climate Dataset Condition
    Expressing opinions on evolving climate data requires factual and competent basis
Role (1)
  • Engineer A Consulting Engineer
    Engineer A may publicly express technical opinions on flood risk based on competence
Event (1)
  • Conference Procedure Presentation
    Public technical opinions expressed at the conference must be founded on facts and competence
Capability (2)
  • Engineer A Professional Judgment
    Forming an opinion on future flood risk is a technical opinion grounded in competence and facts
  • Engineer A Interdisciplinary Understanding
    Sufficient understanding of relevant fields supports competence to express technical opinions
III.1.b board + analysis Engineers shall advise their clients or employers when they believe a project will not be successful.
How this applies in the case (showing 3 of 14)
Obligation
Engineer A Client Engagement Disclosure Duty
Advising the client about potential project failure aligns with this disclosure obligation
Action
Client Discussion Engagement
Advising client of unsuccessful project risks occurs through direct discussion
State
Directive To Proceed Without Analysis
Engineer should advise client if proceeding without analysis risks project failure
Obligation (2)
  • Engineer A Client Engagement Disclosure Duty
    Advising the client about potential project failure aligns with this disclosure obligation
  • Engineer A Regulatory Report Proposal Duty
    Proposing further evaluation reflects advising the client the project may not succeed
Action (2)
  • Client Discussion Engagement
    Advising client of unsuccessful project risks occurs through direct discussion
  • Concern Documentation Proposal
    Documenting concerns serves to formally advise the client of project risks
State (3)
  • Directive To Proceed Without Analysis
    Engineer should advise client if proceeding without analysis risks project failure
  • Obligation Beyond Law Condition
    Engineer must advise client when legal minimums may not ensure project success or safety
  • 25-Year Storm Design Requirement
    Engineer should advise if minimal storm design standard risks project inadequacy
Constraint (1)
  • Engineer A Flood Analysis Suppression
    Engineer should advise client that skipping analysis risks project failure or harm
Principle (1)
  • Disclosure of Potential Impacts to Client
    The provision requires advising clients of project risks matching the disclosure duty described
Role (2)
  • Engineer A Consulting Engineer
    Engineer A should advise Client B if the project risks failing due to unaddressed flood impacts
  • Client B Developer Client
    Client B is the recipient of Engineer A's advice regarding project success concerns
Event (1)
  • Historical Dataset Shift
    Engineer should advise client that reliance on outdated data may cause project failure
Capability (2)
  • Engineer A Risk Disclosure
    Advising client of potential project risks aligns with duty to warn of possible project failure
  • Engineer A Evaluation Threshold Judgment
    Determining that risk merits further evaluation reflects advising client of project concerns
III.2.d board + analysis Engineers are encouraged to adhere to the principles of sustainable development1in order to protect the environment for future generations.Footnote 1"Sustainable development" is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development.
How this applies in the case (showing 3 of 14)
Obligation
Engineer A Future Conditions Duty
Considering future climate changes supports sustainable development principles
Action
Development Project Initiation
Initiating development should consider sustainable development principles for future generations
State
Changing Climate Dataset Condition
Sustainable development principles call for incorporating updated climate data into design
Obligation (2)
  • Engineer A Future Conditions Duty
    Considering future climate changes supports sustainable development principles
  • Engineer A Design Compliance Duty
    Designing to withstand future conditions relates to sustainable development for future generations
Action (2)
  • Development Project Initiation
    Initiating development should consider sustainable development principles for future generations
  • Flood Risk Judgment
    Assessing climate-related flood risk aligns with protecting environmental quality
State (3)
  • Changing Climate Dataset Condition
    Sustainable development principles call for incorporating updated climate data into design
  • Outdated Climate Design Standards
    Sustainability encourages updating standards to reflect long-term environmental protection
  • Obligation Beyond Law Condition
    Sustainable development encourages exceeding minimum legal requirements for future protection
Constraint (1)
  • Engineer A Legal Ceiling Prohibition
    Sustainable development principles extend obligations beyond minimal legal compliance
Principle (2)
  • Public Welfare in Tidal Crossing
    The provision encourages sustainable development to protect future generations matching flood risk from sea level rise
  • Climate Change Standards Responsiveness
    The provision's focus on protecting environment for future generations aligns with adapting to changing climate conditions
Role (1)
  • Engineer A Consulting Engineer
    Engineer A is encouraged to adhere to sustainable development principles to protect the environment and upstream community
Event (1)
  • Ongoing Climate Change
    Sustainable development principles directly address adapting to climate change impacts
Capability (2)
  • Engineer A Risk Assessment
    Considering sea level rise impacts reflects sustainable development principles protecting future environment
  • Engineer A Professional Judgment
    Judging long-term climate-related impacts aligns with sustainable development considerations
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 2 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

Engineers have an obligation to be objective and truthful in professional reports and must include all relevant and pertinent information, including potential adverse impacts, even if not legally mandated, because such information would reasonably interest the reviewing public authority.

Citation Context:

Cited to support the principle that engineers must include all relevant and pertinent information regarding potential public/environmental harm in reports submitted to public authorities, even when not strictly required by regulation.

Relevant Excerpts
discussion: "In BER Case 07.6 , Engineer A was a principal in an environmental engineering firm and had been requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area..."

Principle Established:

An engineer who identifies a public safety risk from climate-related conditions (e.g., storm surge) should advocate for appropriate design standards and, if the client refuses to agree, should withdraw from the project.

Citation Context:

Cited to support the principle that when a client refuses to accept an engineer's judgment regarding future climate-related risks to public safety, the engineer should attempt to persuade the client and, failing agreement, withdraw from the project.

Relevant Excerpts
discussion: "In BER Case 18-9 , Engineer A worked for a developer to perform hydrodynamic modeling and coastal risk assessment regarding a proposed residential development... failing agreement on Engineer A’s proposed design standard, Engineer A should withdraw from the project."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 68% Facts Similarity 73% Discussion Similarity 54% Outcome Alignment 100% Tag Overlap 27% Principle Overlap 70%
Same outcome unclear View Synthesis
Component Similarity 53% Facts Similarity 41% Discussion Similarity 50% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 74%
Same outcome unclear View Synthesis
Component Similarity 46% Facts Similarity 35% Discussion Similarity 48% Outcome Alignment 100% Tag Overlap 58% Principle Overlap 69%
Same outcome unclear View Synthesis
Component Similarity 51% Facts Similarity 44% Discussion Similarity 58% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 70%
Same outcome unclear View Synthesis
Component Similarity 53% Facts Similarity 58% Discussion Similarity 52% Outcome Alignment 100% Tag Overlap 18% Principle Overlap 72%
Same outcome unclear View Synthesis
Component Similarity 53% Facts Similarity 52% Discussion Similarity 59% Outcome Alignment 100% Tag Overlap 17% Principle Overlap 70%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 57% Discussion Similarity 44% Outcome Alignment 50% Tag Overlap 70% Principle Overlap 62%
View Synthesis
Component Similarity 53% Facts Similarity 61% Discussion Similarity 53% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 56%
Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 49% Discussion Similarity 57% Outcome Alignment 100% Tag Overlap 18% Principle Overlap 52%
Same outcome unclear View Synthesis
Component Similarity 47% Facts Similarity 34% Discussion Similarity 47% Outcome Alignment 100% Tag Overlap 27% Principle Overlap 66%
Same outcome unclear View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Does Engineer A have an ethical obligation to address or evaluate the impacts of a project on public health, safety, and welfare with respect to climate change induced conditions that have not yet occurred?

Board conclusion Engineer A has an obligation to consider potential impacts on public health, safety, and welfare, regardless of whether that is required by applicable law, including changing weather patterns and climate.
Resolved by: The board subordinated strict legal/code compliance to the broader ethical duty of holding public welfare paramount, treating code compliance as a floor rather than a ceiling. (confidence 0.85)
I.1. III.2.d. 3 principles 3 facts Conditions Narrative
Implicit (2)

What standard of certainty must Engineer A have—based on conference-presented hydraulic evaluation procedures rather than a completed specialized analysis—before an ethical obligation to disclose upstream flood risk is triggered?

AnalyticalThe Board's conclusion that Engineer A must act on 'reasonable certainty' leaves unresolved how much confidence an informal, conference-derived judgment must provide before triggering a disclosure obligation. Since Engineer A's belief rests on hydraulic evaluation procedures presented at a conference rather than a completed specialized hydrologic study, there is an inherent tension between the competence requirement of undertaking only assignments within one's qualifications and the duty to act on a professional judgment that is admittedly preliminary. The Board's framework implies that engineers may be ethically obligated to disclose concerns even when their own judgment falls short of the rigor normally required for the underlying technical work, provided the judgment is honestly and reasonably held.
Resolved by: The board left in tension the competence constraint against undertaking unqualified assignments and the disclosure duty, implicitly favoring disclosure so long as the underlying judgment is honestly and reasonably, even if informally, held. (confidence 0.70)
II.2.a. I.1. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, the threshold for triggering an ethical obligation to disclose is not the completion of a full specialized hydrologic and hydraulic study, but rather Engineer A's good-faith professional judgment—informed by generally accepted evaluation procedures, even if learned through a conference presentation rather than personal original research—that adverse impacts are reasonably likely to occur. The obligation to raise the issue with the client and propose further study arises at the point of reasonable technical suspicion; the obligation to formally document the concern in a report for regulators arises once Engineer A is 'reasonably certain' of adverse impact, a higher but still professional (not scientific-certainty) standard.
Resolved by: The board balances the risk of premature or under-informed disclosure against the risk of withholding a plausible public-safety concern by setting a graduated standard, a lower threshold of reasonable suspicion for raising the issue internally and a higher threshold of reasonable certainty for formal regulatory reporting. (confidence 0.82)
I.1. II.3.a. III.1.b. 3 principles 3 facts Conditions Narrative

Is Engineer A qualified under the standard of undertaking assignments only within one's competence to make a judgment about long-term climate-driven flood impacts based solely on a conference presentation, absent the specialized hydrologic and hydraulic analysis?

AnalyticalThe Board's first conclusion establishes that Engineer A's ethical duty to consider climate-driven impacts exists independent of current legal requirements, but this creates an asymmetry between the engineer's forward-looking professional judgment and the client's reliance on existing, unamended design codes. Because Client B's directive to withhold the costly analysis unless requested by regulators is itself lawful under current standards, the case illustrates that compliance with applicable law is a necessary but insufficient condition for satisfying the engineer's ethical obligations. This suggests that the Board views the paramountcy of public welfare as imposing an evolving, forward-looking duty that outpaces static regulatory frameworks, placing engineers in the position of anticipating standards not yet codified.
Resolved by: The board treated legal compliance as necessary but not sufficient, subordinating Client B's lawful reliance on current codes to Engineer A's independent, forward-looking duty to anticipate climate-driven risks not yet codified. (confidence 0.75)
I.1. I.4. III.2.d. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q103 and Q104, Engineer A's competence to flag a concern (grounded in generally accepted, conference-disseminated hydraulic evaluation methods) is distinguishable from competence to issue definitive quantified findings, which would require the specialized subconsultant analysis Engineer A originally proposed. Client B's refusal to fund that analysis does not constitute an 'overruling of engineering judgment endangering life or property' under II.1.a, because no immediate danger exists and the harm is prospective and uncertain in degree; however, it does trigger the separate duty under III.1.b to advise the client of concerns about the project, and refusal to heed that advice shifts the ethical burden toward documentation for regulators.
Resolved by: The board separates the competence question from the client-loyalty question, treating Client B's refusal to fund analysis not as an overruling of judgment endangering life or property but as triggering a lesser advisory duty that, if unheeded, escalates toward regulatory documentation. (confidence 0.80)
II.1.a. II.2.a. III.1.b. 3 principles 3 facts Conditions Narrative
Principle tension (2)

Does Climate Change Standards Responsiveness conflict with Engineer A's Design Compliance Duty to follow current local development regulations and national codes that have not yet been updated to reflect sea level rise and changing precipitation patterns?

AnalyticalBy explicitly stating that Engineer A's obligation to consider health, safety, and welfare impacts applies 'regardless of whether required by applicable law,' the Board subordinates Design Compliance Duty and reliance on current codes to Climate Change Standards Responsiveness. This establishes that formal regulatory or code compliance is a floor, not a ceiling, for ethical practice, and that engineers must exercise independent professional judgment about emerging risks like climate change even where standards lag behind scientific understanding.
Resolved by: The board subordinated Engineer A's Design Compliance Duty and reliance on the 25-Year Storm Design Requirement to the paramount duty of public welfare, treating code compliance as a minimum floor rather than a safe harbor against ethical scrutiny. (confidence 0.82)
I.1. III.2.d. 3 principles 3 facts Conditions Narrative

How should Engineer A reconcile Sufficient Understanding for Specialized Evaluation, given that only an informal conference-based judgment exists rather than a completed subconsultant study, with the duty of Disclosure of Potential Impacts to Client and to regulators?

AnalyticalThe case reveals an unresolved tension between Sufficient Understanding for Specialized Evaluation and the duty to disclose potential impacts: Engineer A's judgment rests on informally presented conference procedures rather than a completed rigorous hydrologic study, yet the Board treats this level of confidence as sufficient to trigger disclosure obligations. This suggests that in matters of public safety, the threshold for acting on professional judgment is lower than the threshold for asserting scientific certainty—engineers need not have definitive proof of harm, only a reasonably informed and good-faith belief that harm may occur, in order to be ethically obligated to raise the concern.
Resolved by: The board weighed the relatively low evidentiary threshold available from an informally presented conference procedure against the duty to disclose, concluding that a good-faith, reasonably informed professional belief of possible harm outweighs the need for a completed rigorous study before disclosure is triggered. (confidence 0.78)
II.2.a. II.3.a. III.1.b. 3 principles 3 facts Conditions Narrative
Theoretical (1)

From a deontological perspective, did Engineer A fulfill their duty to hold paramount the safety, health, and welfare of the public even though no current law or code required evaluation of climate-change-induced flood risk?

AnalyticalFrom a deontological standpoint (Q301), Engineer A's duty to hold public safety paramount (I.1) is not conditioned on the existence of an applicable legal or code requirement; it is a free-standing professional duty. Engineer A fulfilled this duty by forming a considered judgment about future harm, proposing the appropriate specialized analysis, and being willing to document the concern for regulators notwithstanding the absence of any legal mandate to consider climate-driven conditions—thus satisfying the deontological requirement even though the underlying uncertainty was not fully resolved.
Resolved by: The board treats the duty to hold public safety paramount as independent of legal mandates, weighing the absence of a legal requirement against Engineer A's affirmative professional conduct and finding the latter sufficient to satisfy the duty. (confidence 0.75)
I.1. III.2.d. 3 principles 3 facts Conditions Narrative
Counterfactual (1)

If local development regulations had already been updated to require evaluation of sea level rise and climate-driven precipitation changes, would the Board still have needed to invoke an ethical obligation 'beyond the law' for Engineer A to consider these impacts?

AnalyticalRegarding Q402, if local development regulations already required evaluation of sea level rise and climate-driven precipitation changes, Engineer A's obligation to consider these impacts would be grounded in ordinary legal/code compliance (II.2.a-type competence and design compliance duties) rather than in the Board's 'beyond the law' reasoning. The ethical analysis would then shift from whether Engineer A must act absent legal requirement to whether Engineer A adequately fulfilled an existing legal duty—though the underlying obligation to disclose to regulators if the client resists a required analysis would likely remain, now reinforced by explicit code language rather than derived solely from I.1.
Resolved by: The board balanced code-based compliance duties against the 'beyond the law' ethical rationale, finding that when the law itself mandates the analysis, ordinary legal/competence duties subsume the need for an independent ethical-beyond-law justification. (confidence 0.75)
II.2.a. I.1. III.1.b. 3 principles 3 facts Conditions Narrative
Board Board question 2

In this set of circumstances, what are Engineer A’s reasonable courses of action with respect to engineering ethics?

Board conclusion If Engineer A is reasonably certain that the project will result in adverse impacts to public health, safety, and welfare, and if the Client B denies the requisite evaluation, Engineer A should include the concern regarding potential adverse public health, safety, and welfare impacts in an engineering report for consideration by regulatory agencies and the public.
Resolved by: Loyalty to Client B's directive was outweighed by the public safety obligation once Engineer A reached reasonable certainty of harm and the client refused to authorize further evaluation, shifting the duty from private advice to public-facing disclosure. (confidence 0.85)
I.1. II.3.a. II.3.b. III.1.b. 3 principles 3 facts Conditions Narrative
Implicit (2)

Does Engineer A's ethical obligation extend to directly informing the upstream homeowners who may be affected, or is disclosure to regulatory agencies and the public via an engineering report sufficient?

AnalyticalThe Board's second conclusion directs disclosure through an engineering report to regulatory agencies and the public, but does not address whether Engineer A has a further obligation to directly notify the twenty upstream homeowners whose property and safety are most immediately at stake. Public disclosure via a report filed with regulators may not reach the affected homeowners in a timely or comprehensible way, particularly if the report is technical, filed only upon regulatory request, or buried within a larger permitting record. A more robust reading of the paramountcy of public welfare could require Engineer A, or urge Client B, to ensure the affected homeowners receive direct or accessible notice of the risk, rather than relying solely on the passive mechanism of a regulatory filing.
Resolved by: The board's chosen remedy (a regulatory report) privileges institutional/public disclosure channels over direct notice to the most immediately affected private parties, leaving unresolved whether paramountcy of public welfare demands more direct communication. (confidence 0.65)
I.1. II.3.b. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q102, the Code's disclosure mechanisms (public reports, statements to regulatory bodies) are designed to channel technical concerns through institutional review rather than direct engineer-to-affected-party communication. Engineer A's ethical obligation is satisfied by ensuring the concern reaches the regulatory agencies and enters the public record (e.g., through hearing testimony or a report), which indirectly informs the upstream homeowners via the public process; a freestanding duty to individually contact the twenty homeowners is not established by the Code, though it would not be prohibited and could be seen as a further expression of holding public welfare paramount.
Resolved by: The board weighs a duty of direct notification to identifiable third parties against the Code's institutional design, concluding that channeling disclosure through regulators and public hearings satisfies the ethical obligation while leaving direct notice as a permissible but not required additional step. (confidence 0.78)
I.1. II.3.a. II.3.b. 3 principles 3 facts Conditions Narrative

Does Client B's directive to withhold the costly analysis unless requested by regulators constitute the kind of overruling of engineering judgment on a matter endangering life or property that requires notification under the professional code, even though no immediate danger currently exists?

Also discussed in: C203
Principle tension (2)

How should Engineer A balance Loyalty to Client B, who has directed against performing the costly flood analysis, with Public Welfare Paramount Beyond Law, given Engineer A's own judgment that the project may cause future harm?

AnalyticalThe Board resolves the tension between Loyalty to Client B and Public Welfare Paramount Beyond Law not by requiring Engineer A to override the client's directive outright, but by establishing a graduated response: the engineer must first attempt to secure client agreement to the specialized analysis, and only if that is refused and the engineer remains reasonably certain of harm does the obligation shift to documenting the concern in an engineering report for regulators and the public. This shows that client loyalty is subordinate to public welfare, but is honored procedurally through sequential escalation rather than immediate breach of the client relationship or project withdrawal.
Resolved by: The board resolved the loyalty-versus-public-welfare tension not by outright subordination through immediate breach, but by sequencing loyalty-preserving persuasion first and escalating to public welfare-driven disclosure only upon client refusal. (confidence 0.80)
I.1. I.4. III.1.b. 3 principles 3 facts Conditions Narrative

Does Disclosure of Potential Impacts to Client create tension with Loyalty to Client B when raising the climate-related flood risk publicly could undermine the client's business interests or the project's approval?

Theoretical (2)

Did the outcome of Client B's directive to forgo the costly hydrologic analysis justify the resulting uncertainty about harm to the twenty upstream homes, given the cost savings to the client versus the potential decade-earlier uninhabitability of those homes?

AnalyticalFrom a consequentialist perspective (Q302), Client B's directive to forgo the costly analysis in order to save project cost, while leaving open the possibility of decade-earlier uninhabitability for twenty upstream homes, produces an ethically troubling asymmetry: a bounded, quantifiable private cost is weighed against a diffuse, deferred, but potentially serious harm to an identifiable group of homeowners. Regardless of whether the harm ultimately materializes, the decision to accept this asymmetric risk without disclosure fails a utilitarian calculus that would require at least informing those who bear the downside risk or the regulators who could compel further study.
Resolved by: The board applies a utilitarian calculus comparing a certain, bounded private cost savings against a diffuse but potentially severe harm to identifiable third parties, concluding the asymmetry is ethically unjustified absent disclosure to those at risk or to regulators. (confidence 0.78)
I.1. III.1.b. 3 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity in proposing the specialized hydrologic analysis and later considering documentation of concerns, despite the added cost, complexity, and difficulty of raising the issue at public hearings?

AnalyticalRegarding Q303, Engineer A acted with professional integrity by proposing the complex analysis despite its cost and by contemplating documentation of the concern despite anticipated difficulty at public hearings; integrity in this context is measured not by whether the concern is ultimately resolved with certainty, but by Engineer A's willingness to surface an uncomfortable technical judgment even when it complicates the client relationship and project approval process.
Resolved by: The board treated the willingness to surface an uncomfortable technical judgment, even at cost to the client relationship and project approval, as outweighing the comfort of silence, regardless of whether the concern is ever conclusively resolved. (confidence 0.75)
I.1. II.3.a. III.1.b. 3 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer A had not possessed reasonably certain judgment (based on the conference-presented hydraulic evaluation procedures) that the project would cause adverse impacts, would the Board still have concluded that Engineer A must document the concern in an engineering report?

AnalyticalRegarding Q401, if Engineer A lacked reasonably certain judgment that the project would cause adverse impacts—for example, if the conference-based procedures suggested only speculative or negligible risk—the Board's documentation obligation would likely not apply, since Conclusion 2 is explicitly conditioned on Engineer A being 'reasonably certain' of adverse impact. In that counterfactual, Engineer A's ethical duty would instead be limited to continuing to monitor emerging standards and perhaps recommending (without insisting upon) the specialized analysis, without the heightened obligation to formally document a report-level concern.
Resolved by: The board weighed the strength of Engineer A's evidentiary basis against the heightened duty to document, concluding that a documentation-level obligation is only triggered once a reasonably certain judgment of harm exists. (confidence 0.80)
I.1. III.1.b. 3 principles 3 facts Conditions Narrative

If Client B had approved the costly hydrologic and hydraulic analysis rather than directing Engineer A to proceed without it, would the Board's conclusion regarding the need for an engineering report documenting concerns for regulators and the public still apply?

AnalyticalRegarding Q403, had Client B approved the costly hydrologic and hydraulic analysis, the Board's conclusion regarding an engineering report would still apply if the completed analysis confirmed adverse impacts to the upstream homes; the obligation to disclose to regulators and the public flows from the existence of reasonably certain adverse findings, not from whether the client resisted the analysis. The character of the report would differ, however—shifting from a precautionary disclosure of an unresolved concern to a documented, quantified finding—but the underlying duty under I.1 and III.1.b to ensure the information reaches decision-makers would persist.
Resolved by: The board weighed the source of the disclosure duty, finding that reasonably certain adverse findings, not the client's resistance to funding, are the operative trigger, so client cooperation does not eliminate the obligation once harm is confirmed. (confidence 0.80)
I.1. III.1.b. II.3.a. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A propose a specialized flood risk analysis based on conference derived judgment, or defer action until a fully rigorous study is independently available?

Options considered:
O1 Engineer A raises the flood risk concern with the client and proposes a subconsultant specialized hydrologic and hydraulic study, acting on the conference derived judgment. Board's choice
O2 Engineer A proceeds with the project using existing design data without raising the flood risk concern, treating the conference presented judgment as insufficient to act on.
Argument structure (Toulmin):
Grounds

Engineer A attended a conference presentation describing hydraulic evaluation procedures indicating potential upstream flood risk from changing precipitation and sea level patterns affecting the project area.

Warrant

Engineers must hold paramount public safety and must consider climate driven impacts on public health, safety, and welfare independent of whether such consideration is legally required; this duty prevails over the competence limitation when the concern is based on generally accepted evaluation procedures rather than novel research.

Rebuttal

This would not apply if the conference derived judgment had no basis in generally accepted engineering procedures, in which case raising it could itself exceed Engineer A's competence to render a professional opinion.

Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare

Should Engineer A engage Client B in discussion of the flood risk findings, or simply comply with the client's directive to withhold analysis?

Options considered:
O1 Engineer A discusses the flood risk findings directly with Client B, attempting to persuade the client to reconsider before the directive becomes final. Board's choice
O2 Engineer A accepts Client B's directive to withhold the costly analysis unless regulators request it, without raising further concerns.
Argument structure (Toulmin):
Grounds

Client B directed that the costly specialized analysis be withheld unless requested by regulators, after Engineer A proposed it based on flood risk findings.

Warrant

Engineers must advise clients of concerns about a project's technical decisions, and this duty to advise operates alongside, and does not require overriding, the duty of loyalty to the client at this preliminary stage.

Rebuttal

This would not apply if immediate danger to life or property existed, which would instead trigger a mandatory notification duty under the code rather than a discretionary discussion.

Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare

Must Engineer A document and report the flood risk concern to regulatory agencies and the public once reasonably certain of adverse impact, or may the concern remain unrecorded given the client's refusal?

Options considered:
O1 Engineer A includes the flood risk concern in an engineering report for consideration by regulatory agencies and the public, once reasonably certain of adverse impact. Board's choice
O2 Engineer A takes no further action to record or report the concern, deferring entirely to Client B's decision to withhold the analysis.
Argument structure (Toulmin):
Grounds

Client B refused to fund the specialized analysis and directed that it be withheld unless regulators requested it, leaving Engineer A's flood risk concern unresolved by further study.

Warrant

Engineers must hold paramount public welfare and must formally document and disclose concerns once reasonably certain of adverse public impact, even where a client declines to authorize further study, and this duty prevails over the client's authority to limit scope.

Rebuttal

This would not apply if Engineer A's judgment remained at the level of mere technical suspicion rather than reasonable certainty, in which case only the lesser duty to advise the client would be triggered.

Regulatory Report Proposal Duty

Does Engineer A's disclosure obligation require directly notifying the affected upstream homeowners, or is disclosure to regulators and the public record sufficient?

Options considered:
O1 Engineer A channels the flood risk concern through an engineering report and regulatory process, relying on the public record to indirectly inform affected homeowners. Board's choice
O2 Engineer A, or urges Client B to, directly contact the twenty upstream homeowners to ensure they receive accessible notice of the flood risk.
Argument structure (Toulmin):
Grounds

Twenty upstream homeowners are the parties most immediately at risk from the flood impact, while the Code's disclosure mechanisms consist of reports and statements to regulatory bodies.

Warrant

The professional code channels technical disclosure through institutional review such as regulatory reports and public hearings rather than requiring direct engineer to affected party notification, and this institutional channeling process satisfies the paramountcy duty.

Rebuttal

This would not apply if the regulatory report were filed only upon request or buried within a permitting record such that it failed to reach the homeowners in a timely or comprehensible way, in which case a more robust reading of paramountcy could require direct notice.

Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare

Should Engineer A withdraw from the project after documentation fails to change Client B's stance, or continue the engagement within the original scope?

Options considered:
O1 Engineer A exits the project because documentation of the concern failed to prompt corrective action from Client B, avoiding complicity in an unaddressed flood risk. Board's choice
O2 Engineer A remains on the project and continues to perform services within the originally accepted scope despite the unresolved flood risk concern.
Argument structure (Toulmin):
Grounds

Engineer A documented the concern and proposed it be raised with regulators, but Client B continued to refuse the specialized analysis and maintained the original directive.

Warrant

Engineers must hold paramount the protection of public health, safety, and welfare, and this duty prevails over the duty to perform services within the scope accepted from the client when continued participation would make the engineer complicit in a knowingly unaddressed risk.

Rebuttal

This would not apply if the client agreed to pursue the specialized analysis or otherwise addressed the concern, in which case continued performance within scope would remain appropriate.

Hold Paramount the Protection of Public Health, Safety, and Welfare
Event Timeline (11)
11 sequenced 8 actions 3 events
Case timeline
Continuing changes in climate and weather patterns, including sea level rise and changes in precipitation intensities and recurrence intervals, form the background occurrence affecting the tidal crossing design.
As climate and weather data are updated in recent decades, the historical dataset itself changes, making climate and weather patterns a moving target for design assumptions rather than a fixed baseline.
State changes (1)
  • began: Changing Climate Dataset Condition
Client B, a developer, decides to propose development of a health care facility requiring a significant upgrade of the access road crossing a tidal saltmarsh.
Causal-normative reasoning(confidence 0.60)
Development Project Initiation carries no direct normative weight itself, but as the originating cause of Project Scope Acceptance it sets in motion the entire chain that eventually forces the engineer to confront a safety versus scope conflict, so its significance lies in triggering the downstream ethical tension rather than in any obligation it fulfills or violates.
Engineer A accepts an engagement representing Client B covering design and local permitting of the roadway, including upgrading the tidal crossing from a small culvert to a small bridge.
Fulfills (1)
  • Perform Services Within Scope for Client
Causal-normative reasoning(confidence 0.75)
Project Scope Acceptance fulfilling the duty to perform services within scope matters because this contractual commitment, caused by Development Project Initiation, later constrains how far Engineer A can unilaterally act on safety concerns, creating the very tension that the paramountcy obligation in A2 and A5 must override.
State changes (1)
  • began: Engineer A Engagement By Client B
Hydraulic evaluation procedures were presented at a recent transportation agency conference, providing the technical basis for Engineer A's later judgment about accelerated flooding of upstream homes.
Engineer A forms a professional judgment, based on hydraulic evaluation procedures from a recent transportation agency conference, that the project may cause some upstream homes to become uninhabitable a decade or more earlier than otherwise.
At stake (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Causal-normative reasoning(confidence 0.80)
Flood Risk Judgment being guided by the duty to hold paramount public safety matters because it is this safety-driven assessment, produced from the Conference Procedure Presentation, that causally compels Engineer A to propose the Specialized Analysis rather than silently accept outdated data, making the paramountcy principle the engine of the whole protective response.
State changes (1)
  • began: Unquantified Upstream Flood Risk Awareness
Engineer A proposes a complex and costly hydrologic and hydraulic analysis by a specialized subconsultant to predict flood damage to twenty upstream homes from sea level rise and the increased hydraulic capacity of the crossing.
At stake (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Causal-normative reasoning(confidence 0.80)
Specialized Analysis Proposal being guided by the paramount safety obligation is significant because it translates Engineer A's flood risk judgment into a concrete protective recommendation that causes the Client Directive Issuance, showing the engineer attempting to fulfill the safety duty within the bounds of professional practice before the client's response creates further conflict.
Client B directs Engineer A to proceed with the project without the costly analysis unless and until regulatory authorities request such an analysis.
Causal-normative reasoning(confidence 0.60)
Client Directive Issuance itself fulfills or violates nothing directly, but because it is caused by the Specialized Analysis Proposal and in turn forces Client Discussion Engagement, it functions as the pivotal point where the client's authority collides with the engineer's safety concerns, making its downstream effects normatively consequential even though the action is normatively neutral in isolation.
State changes (1)
  • began: Directive To Proceed Without Analysis
Prescribed next step in which Engineer A engages Client B in discussions about the need for the detailed evaluation, disclosure of potential impacts on the public, mitigation alternatives, and the risk to Client B of not evaluating the impacts.
At stake (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Fulfills (1)
  • Consider Climate and Weather Changes Impacting Public Health, Safety, and Welfare
Causal-normative reasoning(confidence 0.75)
By engaging Client B in discussion of the flood risk findings, Engineer A directly acts on the paramount duty to safeguard public welfare, translating the prior specialized analysis into a concrete attempt to influence the client's directive before it causes downstream harm, which sets up the subsequent need for documentation once the client resists.
Prescribed fallback in which Engineer A proposes to Client B that the potential concern needing more detailed evaluation be provided in an engineering report for consideration by regulatory agencies and the public.
At stake (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Causal-normative reasoning(confidence 0.70)
Proposing to document the concern is a guided but not fully obligation-fulfilling step, since it preserves a record of Engineer A's professional judgment for accountability purposes, and its causal link to the client's refusal shows that even a paramount safety duty can be only partially discharged through documentation when the client resists corrective action.
Prescribed final step in which Engineer A withdraws from the project if Client B refuses both the detailed evaluation and the disclosure of concerns in an engineering report.
Fulfills (1)
  • Hold Paramount the Protection of Public Health, Safety, and Welfare
Causal-normative reasoning(confidence 0.80)
Withdrawing from the project fulfills the paramount obligation to protect public health, safety, and welfare because it is the causal endpoint after documentation failed to change the client's stance, meaning Engineer A's exit is the necessary act to avoid complicity in a project whose flood risk was knowingly unaddressed.
State changes (1)
  • ended: Engineer A Engagement By Client B
Narrative (2 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer A, a consulting engineer retained by Client B, a developer proposing a health care facility that requires upgrading the site's access road, including replacing a small culvert with a bridge to cross a tidal saltmarsh. Local development regulations require the crossing to accommodate a 25-year fresh-water storm using updated historical precipitation data, but these regulations, along with applicable national design codes, have not been revised to reflect sea level rise or shifting storm intensity and frequency patterns. Based on hydraulic evaluation methods you learned about at a recent transportation agency conference, you believe the increased hydraulic capacity of the redesigned crossing may accelerate flooding for twenty upstream homes, potentially rendering some uninhabitable a decade or more sooner than would otherwise occur. Confirming this would require a complex and costly hydrologic and hydraulic study by a specialized subconsultant, a study that falls outside your current scope and that Client B has not authorized. You must now navigate what to propose, what to disclose, and to whom, as the project moves forward.

Main characters (2)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer A Roles in this case: Consulting Engineer

Guided by: Public Welfare in Tidal Crossing, Loyalty to Client B, Public Welfare Paramount Beyond Law

Engineer A has a duty to disclose relevant risks and findings to the client during engagement, but also a conditional duty to withdraw from the project if the client refuses to act on safety concerns or report them to regulators. Fulfilling the disclosure duty in good faith may trigger the client's refusal to proceed appropriately, forcing the engineer into the difficult position of choosing between continued disclosure efforts and outright withdrawal, each carrying different professional and financial consequences.

Engineer A is constrained from fully presenting or pursuing flood analysis findings, likely at the client's direction, while simultaneously holding a paramount duty to protect public safety. Suppressing or downplaying flood risk data directly undermines the ability to warn upstream homeowners and regulators of potential harm, creating a direct conflict between client-driven suppression and the engineer's core safety obligation.

Engineer A is prohibited from designing or recommending measures that exceed the legal regulatory ceiling, yet also holds an ethical obligation to protect public safety even when minimum legal standards are insufficient to prevent foreseeable harm, such as flooding under future or extreme conditions. This creates a direct tension between legal compliance limits and the professional duty to exceed mere code minimums when safety demands it.

Client B Roles in this case: Developer Client

Engineer A has a duty to disclose relevant risks and findings to the client during engagement, but also a conditional duty to withdraw from the project if the client refuses to act on safety concerns or report them to regulators. Fulfilling the disclosure duty in good faith may trigger the client's refusal to proceed appropriately, forcing the engineer into the difficult position of choosing between continued disclosure efforts and outright withdrawal, each carrying different professional and financial consequences.

Engineer A is constrained from fully presenting or pursuing flood analysis findings, likely at the client's direction, while simultaneously holding a paramount duty to protect public safety. Suppressing or downplaying flood risk data directly undermines the ability to warn upstream homeowners and regulators of potential harm, creating a direct conflict between client-driven suppression and the engineer's core safety obligation.

Other people involved in the case but not central to the opening narrative.

Engineer A has a duty to disclose relevant risks and findings to the client during engagement, but also a conditional duty to withdraw from the project if the client refuses to act on safety concerns or report them to regulators. Fulfilling the disclosure duty in good faith may trigger the client's refusal to proceed appropriately, forcing the engineer into the difficult position of choosing between continued disclosure efforts and outright withdrawal, each carrying different professional and financial consequences.

Engineer A is constrained from fully presenting or pursuing flood analysis findings, likely at the client's direction, while simultaneously holding a paramount duty to protect public safety. Suppressing or downplaying flood risk data directly undermines the ability to warn upstream homeowners and regulators of potential harm, creating a direct conflict between client-driven suppression and the engineer's core safety obligation.

Engineer A is prohibited from designing or recommending measures that exceed the legal regulatory ceiling, yet also holds an ethical obligation to protect public safety even when minimum legal standards are insufficient to prevent foreseeable harm, such as flooding under future or extreme conditions. This creates a direct tension between legal compliance limits and the professional duty to exceed mere code minimums when safety demands it.

Engineer A is constrained from fully presenting or pursuing flood analysis findings, likely at the client's direction, while simultaneously holding a paramount duty to protect public safety. Suppressing or downplaying flood risk data directly undermines the ability to warn upstream homeowners and regulators of potential harm, creating a direct conflict between client-driven suppression and the engineer's core safety obligation.

Engineer A is prohibited from designing or recommending measures that exceed the legal regulatory ceiling, yet also holds an ethical obligation to protect public safety even when minimum legal standards are insufficient to prevent foreseeable harm, such as flooding under future or extreme conditions. This creates a direct tension between legal compliance limits and the professional duty to exceed mere code minimums when safety demands it.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

Engineer A has an obligation to consider potential impacts on public health, safety, and welfare, regardless of whether that is required by applicable law, including changing weather patterns and climate.
If Engineer A is reasonably certain that the project will result in adverse impacts to public health, safety, and welfare, and if the Client B denies the requisite evaluation, Engineer A should include the concern regarding potential adverse public health, safety, and welfare impacts in an engineering report for consideration by regulatory agencies and the public.
Opening States (10)
25-Year Storm Design Requirement Outdated Climate Design Standards Unquantified Upstream Flood Risk Awareness Upstream Homes Flood Exposure Directive To Proceed Without Analysis Foregone Flood Analysis Engineer A Engagement By Client B Obligation Beyond Law Condition Engineer A Sufficient Understanding Climate Impact Evaluation Gray Area
Summary
  • Engineers must place public safety above client instructions when those instructions would suppress or minimize legitimate technical findings such as flood risk data.
  • Meeting the minimum legal or regulatory standard does not satisfy an engineer's ethical duty if that standard is foreseeably inadequate to prevent harm, especially under evolving conditions like climate change.
  • When a client refuses to disclose or act on safety findings, the engineer faces an escalating duty that may require withdrawal from the project rather than continued silent participation.

© Licensed under the GNU GPL v3