Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Public Health and Safety—Building Codes to Address Environmental Risk
Step 4 of 5

164

Entities

5

Provisions

2

Precedents

13

Questions

16

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's paramount safety obligation begins as a duty owed within the Client A engagement (persuade client, refuse to seal unsafe design) but, upon Client A's refusal and Engineer A's withdrawal, the obligation is reframed as one owed to local government officials, potential successor engineers, and possibly environmental/regulatory authorities—effectively transferring the responsibility for safeguarding public welfare from the private engineer-client relationship to the public governance apparatus.
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 (5)
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.

II.1 board + analysis Engineers shall hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 23)
Obligation
Engineer A Public Safety Duty
This provision directly requires engineers to prioritize public safety which defines this obligation.
Action
Professional Safety Determination
Engineer must hold public safety paramount when making this determination
State
Coastal Storm Surge Safety Risk
This provision requires engineers to prioritize public safety against identified storm surge risks
Obligation (3)
  • Engineer A Public Safety Duty
    This provision directly requires engineers to prioritize public safety which defines this obligation.
  • Engineer A Client Persuasion Duty
    Persuading the client relates to upholding public safety as paramount.
  • Engineer A Conditional Withdrawal Duty
    Withdrawal is justified by the need to hold public safety paramount when client disagrees.
Action (4)
  • Professional Safety Determination
    Engineer must hold public safety paramount when making this determination
  • Building Code Advocacy
    Advocating for stricter codes directly protects public safety and welfare
  • Client Standard Refusal
    Refusing substandard client requests upholds paramount duty to public safety
  • Project Withdrawal
    Withdrawing from a project protects public safety when standards are inadequate
State (3)
  • Coastal Storm Surge Safety Risk
    This provision requires engineers to prioritize public safety against identified storm surge risks
  • Client Duty Versus Public Safety Conflict
    This provision resolves conflicts by mandating that public safety take precedence over client interests
  • Property And Environmental Damage Exposure
    This provision requires engineers to consider welfare implications including property and environmental harm
Constraint (2)
  • Owner Cost Refusal Design Limit
    Safety must be held paramount over the owners refusal to build to the higher storm surge elevation
  • Engineer A Cost Over Safety Limit
    Safety must be held paramount over the clients desire to reduce costs
Principle (3)
  • Public Welfare in Coastal Design
    Requires engineer to prioritize public safety when designing for coastal hazards
  • Public Welfare in Storm Surge Design
    Mandates paramount safety in setting storm surge elevation standards
  • Client Loyalty Balanced Against Safety
    Public safety must override cost-driven client preferences
Role (2)
  • Engineer A Public Responsibility Engineer
    Engineer A must prioritize public safety over developer cost concerns regarding the coastal development risks
  • Engineer A Consultant Engineer
    The consultant engineer performing coastal risk assessment must hold public safety paramount in evaluating flood risks
Event (1)
  • New Data Release
    New data on environmental risk directly affects public safety and welfare considerations
Capability (5)
  • Engineer A Coastal Risk Assessment
    Identifying public safety risks directly reflects holding public safety paramount
  • Engineer A Professional Judgment
    Recommending the higher storm surge standard is an application of holding safety paramount
  • Engineer A Ethical Reasoning
    Weighing cost against life safety risk is a direct application of this paramount duty
  • Engineer A Hydrodynamic Modeling
    Modeling climate risk supports the paramount duty to protect public safety
  • Engineer A Risk Persuasion
    Persisting to convince the client of danger to future residents reflects safety as paramount
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 15)
Obligation
Engineer A Client Persuasion Duty
This provision requires notifying appropriate authority if judgment is overruled endangering safety, aligning with continued persuasion efforts.
Action
Building Code Advocacy
Engineer must notify appropriate authority when judgment on safety is overruled
State
Engineer A Storm Surge Finding
This provision requires notification when engineering judgment about safety risks is overruled
Obligation (2)
  • Engineer A Client Persuasion Duty
    This provision requires notifying appropriate authority if judgment is overruled endangering safety, aligning with continued persuasion efforts.
  • Engineer A Conditional Withdrawal Duty
    If overruled on safety grounds, the provision supports escalation or withdrawal as appropriate action.
Action (3)
  • Building Code Advocacy
    Engineer must notify appropriate authority when judgment on safety is overruled
  • Project Withdrawal
    Withdrawal may follow after notifying authorities when judgment is overruled
  • Client Standard Refusal
    Refusal to comply with unsafe standards relates to notifying appropriate authority
State (3)
  • Engineer A Storm Surge Finding
    This provision requires notification when engineering judgment about safety risks is overruled
  • Owner Cost Based Refusal
    This provision addresses the scenario where an owner overrules engineering judgment based on cost concerns
  • No Building Code In Project Area
    This provision requires notifying appropriate authority when no code exists to address the safety concern
Constraint (2)
  • Owner Cost Refusal Design Limit
    Engineer must notify appropriate authority if judgment on storm surge design is overruled endangering life or property
  • Engineer A Cost Over Safety Limit
    Engineer must notify appropriate authority if safety judgment is overruled due to cost concerns
Principle (2)
  • Client Loyalty Balanced Against Safety
    Engineer must notify appropriate authority if judgment on safety is overruled by client
  • Public Welfare in Storm Surge Design
    Requires escalation if safety-based design decisions are overridden
Role (1)
  • Engineer A Public Responsibility Engineer
    Engineer A should notify appropriate authorities when professional judgment on safety risks is overruled
Capability (2)
  • Engineer A Withdrawal Judgment
    Withdrawing and notifying appropriate authority applies when judgment is overruled endangering life or property
  • Engineer A Stakeholder Engagement
    Contacting government officials aligns with notifying other appropriate authority
II.1.b board + analysis Engineers shall approve only those engineering documents that are in conformity with applicable standards.
How this applies in the case (showing 3 of 13)
Obligation
Engineer A Conditional Withdrawal Duty
Engineer A should not approve documents inconsistent with his safety standards, supporting withdrawal if standards are not met.
Action
Client Standard Refusal
Engineer must refuse to approve documents that do not meet applicable standards
State
No Building Code In Project Area
This provision requires conformity to applicable standards even when local building codes are absent
Obligation (1)
  • Engineer A Conditional Withdrawal Duty
    Engineer A should not approve documents inconsistent with his safety standards, supporting withdrawal if standards are not met.
Action (2)
  • Client Standard Refusal
    Engineer must refuse to approve documents that do not meet applicable standards
  • Professional Safety Determination
    Determining conformity with standards governs approval of engineering documents
State (2)
  • No Building Code In Project Area
    This provision requires conformity to applicable standards even when local building codes are absent
  • Coastal Storm Surge Safety Risk
    This provision requires that documents approved reflect appropriate safety standards for identified risks
Constraint (2)
  • Owner Cost Refusal Design Limit
    Engineer should not approve documents that fail to meet applicable storm surge safety standards
  • Engineer A Cost Over Safety Limit
    Engineer should not approve designs that compromise standards to satisfy cost reduction demands
Principle (2)
  • Professional Judgment on Technical Competence
    Engineer must ensure design documents conform to applicable safety standards
  • Public Welfare in Coastal Design
    Approval of documents must reflect sound technical judgment protecting public welfare
Role (1)
  • Engineer A Public Responsibility Engineer
    Engineer A should only approve documents conforming to updated building codes addressing coastal risk
Resource (1)
  • Historic Weather Data and Algorithm
    Approving documents in conformity with applicable standards requires using the newly available storm surge data and algorithm
Capability (2)
  • Engineer A Professional Judgment
    Approving design documents must conform to the standard the engineer believes is safe
  • Engineer A Withdrawal Judgment
    Refusal to approve nonconforming documents underlies the duty to withdraw
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 15)
Obligation
Engineer A Client Persuasion Duty
This provision requires advising the client when the project may not succeed, matching the persuasion obligation.
Action
Continued Client Persuasion
Engineer must advise client when project will not succeed as proposed
State
Owner Cost Based Refusal
This provision requires advising the client when their cost-based decision may lead to project failure
Obligation (1)
  • Engineer A Client Persuasion Duty
    This provision requires advising the client when the project may not succeed, matching the persuasion obligation.
Action (2)
  • Continued Client Persuasion
    Engineer must advise client when project will not succeed as proposed
  • Client Engagement Retention
    Retaining engagement while advising client of project issues aligns with this duty
State (2)
  • Owner Cost Based Refusal
    This provision requires advising the client when their cost-based decision may lead to project failure
  • Client Duty Versus Public Safety Conflict
    This provision requires engineers to advise clients when a project will not succeed due to safety conflicts
Constraint (2)
  • Owner Cost Refusal Design Limit
    Engineer must advise the owner that refusing the higher elevation design risks project failure
  • Engineer A Cost Over Safety Limit
    Engineer must advise the client that prioritizing cost over safety risks project failure
Principle (2)
  • Client Loyalty Balanced Against Safety
    Engineer should advise client if reduced design standards could cause project failure
  • Professional Judgment on Technical Competence
    Engineer must communicate concerns about technical adequacy to client
Role (2)
  • Engineer A Public Responsibility Engineer
    Engineer A must advise the client that the project may not be successful given new coastal risk information
  • Engineer A Consultant Engineer
    The consultant engineer must advise on project viability based on hydrodynamic modeling results
Event (1)
  • New Data Release
    New data may indicate the project will not succeed or is unsafe, requiring advisement to client
Resource (1)
  • Historic Weather Data and Algorithm
    Advising the client of project success requires informing them about the new storm surge determination data
Capability (2)
  • Engineer A Risk Persuasion
    Advising the client the project may not be successful or safe fits this provision
  • Engineer A Professional Judgment
    Recommending a higher design standard is advising the client of project risk
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 15)
Obligation
Engineer A Public Safety Duty
Considering sustainable development supports the coastal risk assessment protecting future public welfare.
Action
Building Code Advocacy
Advocating for codes addressing environmental risk supports sustainable development
State
Property And Environmental Damage Exposure
This provision encourages sustainable development to protect against environmental damage
Obligation (1)
  • Engineer A Public Safety Duty
    Considering sustainable development supports the coastal risk assessment protecting future public welfare.
Action (1)
  • Building Code Advocacy
    Advocating for codes addressing environmental risk supports sustainable development
State (2)
  • Property And Environmental Damage Exposure
    This provision encourages sustainable development to protect against environmental damage
  • Coastal Storm Surge Safety Risk
    This provision relates to designing for environmental risks like storm surge to protect future development
Constraint (1)
  • Owner Cost Refusal Design Limit
    Sustainable development principles support designing for long-term environmental risk like storm surge
Principle (1)
  • Environmental Protection in Coastal Development
    Directly relates to sustainable development and environmental protection responsibilities
Role (2)
  • Engineer A Public Responsibility Engineer
    Engineer A is encouraged to advocate for sustainable development principles in advising on the coastal project
  • Engineer A Consultant Engineer
    The consultant engineer's risk assessment should incorporate sustainable development considerations for environmental protection
Event (1)
  • New Data Release
    New environmental data relates directly to sustainable development considerations
Resource (3)
  • NSPE Code of Ethics
    This provision is part of the Code addressing environmental protection responsibilities
  • BER Case 04-8
    This prior case concerns environmental protection through wetland fill violations relevant to sustainable development
  • BER Case 07-6
    This prior case concerns environmental protection through reporting threatened species relevant to sustainable development
Capability (3)
  • Engineer A Data Currency
    Using updated climate and sea level data reflects sustainable development principles
  • Engineer A Hydrodynamic Modeling
    Modeling climate change and sea level rise supports sustainable development considerations
  • Engineer A Stakeholder Engagement
    Advocating for updated regional codes supports broader sustainable development goals
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, even if it may be unfavorable to the client's interests.

Citation Context:

Cited to support the principle that engineers must include all relevant and pertinent information, including environmental risks, in reports submitted to public authorities, reinforcing Engineer A's obligation to disclose safety risks despite client resistance.

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..."

Principle Established:

When an engineer discovers that a client has violated environmental laws or regulations, the engineer should inquire about the client's actions, advise on remedial steps in compliance with the law, and report to appropriate authorities if the client fails to act.

Citation Context:

Cited to illustrate an engineer's obligation to address a client's violation of environmental laws, including advising remediation and reporting to authorities if unresolved, analogous to Engineer A's duty to protect public safety and the environment.

Relevant Excerpts
discussion: "In BER Case No. 04-8, Engineer A, an environmental engineer, performed wetland delineation services on the client’s wetland site..."
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 59% Facts Similarity 56% Discussion Similarity 62% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 68%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 67% Discussion Similarity 60% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 53%
Shared provisions: III.2.d Same outcome unclear View Synthesis
Component Similarity 51% Facts Similarity 38% Discussion Similarity 52% Outcome Alignment 100% Tag Overlap 60% Principle Overlap 59%
Same outcome unclear View Synthesis
Component Similarity 59% Facts Similarity 52% Discussion Similarity 63% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 61%
Same outcome unclear View Synthesis
Component Similarity 52% Facts Similarity 49% Discussion Similarity 67% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 67%
Same outcome unclear View Synthesis
Component Similarity 57% Facts Similarity 44% Discussion Similarity 68% Outcome Alignment 100% Tag Overlap 17% Principle Overlap 53%
Same outcome unclear View Synthesis
Component Similarity 48% Facts Similarity 40% Discussion Similarity 39% Outcome Alignment 100% Tag Overlap 30% Principle Overlap 62%
Same outcome unclear View Synthesis
Component Similarity 53% Facts Similarity 42% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 11% Principle Overlap 62%
Same outcome unclear View Synthesis
Component Similarity 52% Facts Similarity 58% Discussion Similarity 41% Provision Overlap 33% Outcome Alignment 50% Tag Overlap 11% Principle Overlap 56%
Shared provisions: III.2.d View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

What are Engineer A’s obligations under the circumstances?

Board conclusion Engineer A should continue to pursue discussions with Client A to convince Client A of the danger in which future residents, as well as the general public, could be placed, and the potential for significant property and environmental damage. If Client A refuses to agree with Engineer A’s design standard, Engineer A should withdraw from the project.
Resolved by: Client loyalty and project revenue are subordinated to the paramount duty to protect public safety, but only after Engineer A exhausts good-faith persuasion before withdrawing. (confidence 0.85)
II.1. III.1.b. 3 principles 3 facts Conditions Narrative
Implicit (2)

Given that the project area has no building code, does Engineer A have an obligation to advocate for local government adoption of a storm surge building standard, independent of Client A's decision?

AnalyticalBeyond advising withdrawal, the Board's reasoning implies but does not state that Engineer A has an independent professional interest in advocating for the adoption of a storm surge building standard by the local government, separate from the outcome of the Client A engagement. Given the absence of any code in the area, Engineer A's specialized knowledge positions the engineer uniquely to promote broader regulatory reform that would protect not just Client A's future residents but all future development in the region, aligning with the spirit of sustainable development encouraged under Code III.2.d.
Resolved by: The board implicitly favors broader public welfare and regulatory reform over confining Engineer A's role to the single client engagement. (confidence 0.65)
III.2.d. 2 principles 3 facts Conditions Narrative
AnalyticalBecause the project area currently has no building code addressing storm surge, Engineer A's obligation under II.1 to hold public safety paramount arguably extends beyond the immediate client relationship. Even if Client A ultimately agrees to a lower standard or Engineer A withdraws, Engineer A has a strong ethical basis for independently advocating that local government adopt a storm surge design standard, since the absence of any code leaves future residents and the public without baseline protection that would otherwise be presumed to exist.
Resolved by: The board treats the independent public advocacy obligation as outweighing any narrower reading that would confine Engineer A's duty to the client relationship alone. (confidence 0.75)
II.1. III.2.d. 3 principles 3 facts Conditions Narrative

If Engineer A withdraws from the project, does Engineer A have any further duty to notify local government officials or a successor engineer about the identified storm surge risk to protect future residents and the public?

AnalyticalThe Board's recommendation to withdraw addresses Engineer A's direct relationship with Client A, but does not resolve whether Engineer A retains a residual duty to protect future residents and the public after withdrawal. Because the project area lacks a building code, withdrawal alone may not prevent Client A from retaining another engineer willing to design to a lower standard, leaving the underlying public safety risk unaddressed. Engineer A's obligation under Code II.1 to hold paramount public safety arguably extends to considering whether notification to local government officials of the identified storm surge risk is warranted, even though the Code does not mandate breaching client confidentiality absent an imminent danger comparable to that in BER Case 04-8 or BER Case 07-6.
Resolved by: The board weighs the paramount public safety duty against client confidentiality, finding the latter yields only where imminent danger is shown, which was not established here. (confidence 0.75)
II.1. 3 principles 3 facts Conditions Narrative
AnalyticalIf Engineer A withdraws after failing to persuade Client A, II.1.a's requirement to notify appropriate authorities when judgment is overruled under circumstances endangering life or property suggests an ongoing duty. Withdrawal alone may not fully discharge Engineer A's public welfare obligation; Engineer A should consider notifying local government officials of the identified storm surge risk so that future permitting decisions or a successor engineer are informed, even though the Board's stated conclusion focuses only on persuasion and withdrawal.
Resolved by: The board weighed Engineer A's residual public safety duty under II.1.a against the client confidentiality and loyalty interests normally attaching to a withdrawn engagement, finding the former to extend beyond the termination of the client relationship. (confidence 0.75)
II.1.a. 3 principles 3 facts Conditions Narrative
Principle tension (1)

How should Client Loyalty Balanced Against Safety be reconciled with Public Welfare in Storm Surge Design when Client A refuses to pay for the higher design standard Engineer A believes is necessary for public safety?

AnalyticalThe Board resolved the tension between Client Loyalty Balanced Against Safety and Public Welfare in Storm Surge Design by establishing a strict lexical priority: public welfare is paramount and non-negotiable, while client loyalty is conditional and instrumental. Engineer A's obligation to the client is satisfied only through good-faith persuasion; if that fails, loyalty yields entirely to withdrawal rather than compromise on the safety standard. This shows that under Code II.1, client loyalty cannot function as a countervailing principle of equal weight to public safety—it is subordinate and must give way once a genuine safety determination is made.
Resolved by: The Board establishes a strict lexical priority in which public welfare is non-negotiable and client loyalty is conditional, so loyalty is satisfied only through persuasion and yields entirely to withdrawal once persuasion fails. (confidence 0.85)
II.1. III.1.b. 2 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill the duty under Code section II.1 to hold paramount the safety, health, and welfare of the public by insisting on the 100-year storm surge design standard despite Client A's refusal?

AnalyticalFrom a deontological standpoint grounded in II.1, Engineer A fulfilled the paramount duty to public safety by insisting on the 100-year storm surge standard and being willing to withdraw rather than compromise. The duty is satisfied not merely by achieving an outcome but by Engineer A's rule-based refusal to approve or proceed with a design believed to endanger public safety, regardless of the financial cost to Engineer A or the client relationship.
Resolved by: The board applied a deontological frame in which the rule-based duty under II.1 to hold public safety paramount outweighs financial or client-relationship considerations regardless of the project's ultimate outcome. (confidence 0.80)
II.1. 2 principles 3 facts Conditions Narrative

Did the likely outcome of protecting future residents and the general public from storm surge risk justify Engineer A's willingness to withdraw from a paying engagement and forgo the project revenue?

AnalyticalFrom a consequentialist perspective, Engineer A's willingness to forgo project revenue by withdrawing is justified because the likely harm averted—risk to future residents' safety and significant property and environmental damage—substantially outweighs the private financial loss to Engineer A, satisfying a public-interest cost-benefit rationale for withdrawal even without certainty that withdrawal will change the ultimate outcome of the project.
Resolved by: The board weighed the certain private financial loss to Engineer A against the substantial, though uncertain, public and environmental harm averted, finding the latter to justify withdrawal on cost-benefit grounds. (confidence 0.75)
2 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity by first attempting sustained, good-faith persuasion of Client A regarding the storm surge risk before resorting to withdrawal from the project?

AnalyticalEngineer A acted with professional integrity by first engaging in continued, good-faith persuasion under III.1.b before resorting to withdrawal. This sequencing reflects the Code's preference for advising clients and attempting resolution prior to more drastic action, demonstrating that withdrawal was treated as a last resort rather than an immediate response to disagreement.
Resolved by: Client loyalty is honored through sustained persuasive effort, but once that effort is exhausted it yields to the paramount safety obligation via withdrawal. (confidence 0.85)
III.1.b. II.1. 2 principles 3 facts Conditions Narrative
Counterfactual (2)

If a local building code had existed in the project area mandating a lower storm surge design standard than the 100-year projection, would the Board still have concluded that Engineer A must withdraw upon Client A's refusal to exceed that code minimum?

AnalyticalHad a local building code existed mandating a lower storm surge standard, the Board would likely have faced a harder question, since II.1.b directs engineers to approve only documents conforming to applicable standards. However, given II.1's paramount safety duty and precedent treating code minimums as floors rather than ceilings for professional judgment, the Board would likely still have concluded that Engineer A should withdraw if convinced the code minimum was unsafe, though the analysis would need to address potential conflict between code compliance and independent professional judgment.
Resolved by: Even where a codified minimum exists, the Board weighs II.1's paramount safety duty as outweighing II.1.b's conformity requirement, treating code minimums as floors rather than ceilings. (confidence 0.70)
II.1.b. II.1. 3 principles 3 facts Conditions Narrative

If Engineer A's 100-year storm surge recommendation had been based on speculative concern rather than on newly released historic weather data and a newly developed algorithm, would the Board still have found Engineer A's public safety determination professionally justified and the withdrawal obligation applicable?

AnalyticalIf Engineer A's recommendation had rested on speculative concern rather than newly released historic weather data and a validated algorithm, the Board would likely not have found the public safety determination professionally justified, and the withdrawal obligation would be considerably weaker. The Board's implicit reliance on the technical grounding of the 100-year projection is central to legitimizing both the persuasion effort and the recommended withdrawal; without such grounding, Engineer A's position would resemble an unsupported preference rather than a defensible safety determination.
Resolved by: The Board implicitly weighs the strength of technical grounding as a precondition for the safety obligation to override client loyalty, so persuasion and withdrawal are legitimated only by demonstrable data support. (confidence 0.75)
II.1. 2 principles 3 facts Conditions Narrative
Analytical questions (4)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (2)

How much confidence must Engineer A have in the newly developed algorithm and historic weather data before treating the 100-year storm surge projection as a firm professional determination rather than a precautionary recommendation?

AnalyticalThe Board's conclusion presumes that Engineer A's 100-year storm surge determination is a well-founded professional judgment, but it does not explicitly examine the threshold of confidence required in newly developed algorithms and newly released historic weather data before such a determination can justify withdrawal from a paying engagement. Because the standard is not yet codified into any building code or regulatory requirement, Engineer A's technical competence and the reliability of the underlying data become central to whether the withdrawal obligation is ethically compelled or merely a precautionary best practice. This raises a nuance the Board did not address: the degree of scientific certainty needed to elevate a risk assessment to the level of a paramount safety obligation under Code II.1.
Resolved by: The board implicitly weighs technical reliability against the urgency of paramount safety, presuming reliability without articulating the confidence threshold required. (confidence 0.70)
II.1. II.1.b. 2 principles 3 facts Conditions Narrative
AnalyticalEngineer A need not have absolute certainty in the newly developed algorithm and historic weather data to treat the 100-year storm surge projection as a professional determination rather than mere precaution. Consistent with reasonable engineering judgment standards, Engineer A must have a good-faith, technically defensible basis grounded in the best currently available data and methodology; the newness of the algorithm does not, by itself, undermine the legitimacy of the determination so long as Engineer A applied sound professional judgment in validating it.
Resolved by: The board balanced the demand for certainty in technical determinations against the practical impossibility of absolute proof, concluding that good-faith, technically defensible validation suffices to treat the projection as a firm determination. (confidence 0.70)
2 principles 3 facts Conditions Narrative

Does the potential for significant property and environmental damage impose obligations on Engineer A that extend beyond the client relationship, such as informing regulatory or environmental authorities?

AnalyticalThe potential for significant property and environmental damage does create obligations extending beyond the client relationship. Under principles reflected in III.2.d and analogous prior Board reasoning (as in BER Case 04-8 and BER Case 07-6 concerning disclosure to public authorities), Engineer A's duty to protect the environment and public may require informing relevant regulatory or environmental authorities if withdrawal alone leaves the risk unaddressed, particularly given the absence of a governing building code.
Resolved by: The board weighed the client-confined scope of the engagement against the broader public and environmental interest in disclosure, concluding that the latter can extend obligations beyond the client relationship when withdrawal alone would leave the risk unaddressed. (confidence 0.75)
III.2.d. 2 principles 3 facts Conditions Narrative
Principle tension (2)

Does Professional Judgment on Technical Competence conflict with Public Welfare in Coastal Design when the underlying data and algorithm supporting the 100-year projection are newly developed and not yet codified into any regulatory standard?

AnalyticalThe case demonstrates that Professional Judgment on Technical Competence does not need to be validated by an existing regulatory standard or codified building code to trigger the Public Welfare in Coastal Design obligation. Even though the 100-year storm surge projection rests on a newly developed algorithm and newly released historic weather data, and no local building code exists to anchor the determination, the Board treats Engineer A's professional judgment as sufficient to establish a paramount safety duty. This suggests that in emerging risk domains (e.g., climate change and sea level rise), the absence of codified standards increases rather than diminishes the engineer's independent responsibility to apply best available data and judgment in service of public welfare.
Resolved by: The Board weighs the absence of a codified standard as increasing rather than diminishing the weight of professional judgment, so technical competence alone can trigger the paramount public welfare obligation. (confidence 0.75)
II.1. 2 principles 3 facts Conditions Narrative

How should Environmental Protection in Coastal Development be balanced against Client Loyalty Balanced Against Safety when the client's cost-driven refusal increases the risk of future environmental damage from storm surge?

AnalyticalEnvironmental Protection in Coastal Development is not treated by the Board as an independent principle requiring separate action (such as notifying environmental authorities), but is instead absorbed into and reinforces the overarching Public Welfare in Storm Surge Design duty. The risk of property and environmental damage functions as an aggravating factor that strengthens the case for persuasion and withdrawal, rather than generating a distinct obligation running to environmental regulators. This indicates a hierarchy in which environmental protection is instrumental to, rather than co-equal with, the paramount public safety and welfare obligation.
Decisions & Arguments (6)
View Extraction

Should Engineer A continue persuading Client A to adopt the 100-year storm surge standard and withdraw if refused, or instead accept Client A's lower standard and proceed with the project?

Options considered:
O1 Continue good-faith discussions to convince Client A of the storm surge danger, and withdraw from the project if Client A still refuses the 100-year standard. Board's choice
O2 Defer to Client A's cost-based decision and design to the lower storm surge elevation Client A is willing to fund.
O3 Withdraw from the project as soon as Client A refuses the 100-year standard, without continuing to press for reconsideration.
Argument structure (Toulmin):
Grounds

Client A refused to agree to the 100-year projected storm surge design standard citing increased cost. Engineer A's determination relies on newly released historic weather data and a newly developed algorithm.

Warrant

Engineers must hold paramount the safety, health, and welfare of the public, which takes priority over client cost preferences once those preferences are shown to conflict with a well-founded safety determination; client loyalty is discharged through good-faith persuasion, not through compliance with an unsafe standard.

Rebuttal

Would not apply if no building code exists to define a mandatory minimum and Client A's cost-based refusal is a good-faith, legitimate business judgment rather than disregard for safety, in which case the warrant to override client authority weakens.

Engineer A Client Persuasion Duty Owner Cost Refusal Design Limit

After withdrawing from the project, should Engineer A notify local government officials or a successor engineer of the identified storm surge risk, or treat withdrawal alone as fully discharging the safety duty?

Options considered:
O1 After withdrawing, inform local government officials of the identified storm surge risk so future permitting decisions account for it. Board's choice
O2 Limit disclosure to informing any successor engineer of the identified risk, without contacting local government officials.
O3 Treat withdrawal from the engagement as fully discharging the public safety duty, without further notification to authorities or successors.
Argument structure (Toulmin):
Grounds

The project area has no building code addressing storm surge. Engineer A withdrew after Client A refused the 100-year design standard.

Warrant

Code section II.1.a requires engineers to notify appropriate authorities when their professional judgment is overruled under circumstances that endanger life or property.

Rebuttal

Would not apply if disclosure is barred by confidentiality obligations to Client A absent an imminent, verified danger comparable to that recognized in prior Board precedent.

Engineer A Public Safety Duty

Should Engineer A independently advocate for local government adoption of a storm surge design standard, regardless of how the Client A engagement is resolved?

Options considered:
O1 Independently engage local government to advocate for adoption of a storm surge design standard, regardless of the Client A outcome. Board's choice
O2 Confine professional effort to the Client A project and refrain from separate advocacy to local government.
O3 Wait until the Client A engagement is fully resolved (through agreement or withdrawal) before raising the code issue with local government.
Argument structure (Toulmin):
Grounds

The project area currently has no building code addressing storm surge. Engineer A possesses specialized knowledge from a newly developed algorithm and newly released historic weather data.

Warrant

Engineers should promote sustainable development practices consistent with the public welfare (III.2.d) and hold public safety paramount (II.1), which supports using specialized expertise to advance broader regulatory protections beyond a single client engagement.

Rebuttal

Would not apply if Engineer A lacks standing or an appropriate channel to influence local government, or if such advocacy would require disclosing confidential client information.

Engineer A Public Safety Duty

Should Engineer A treat the newly developed algorithm's 100-year storm surge projection as a firm professional determination justifying persuasion and withdrawal, or as a precautionary recommendation pending further validation?

Options considered:
O1 Rely on the validated algorithm and historic data as sufficient basis to treat the 100-year projection as a firm professional safety determination warranting persuasion and withdrawal. Board's choice
O2 Present the 100-year projection to Client A as a precautionary best practice pending further peer review, without treating it as an absolute professional mandate.
O3 Commission independent third-party review of the algorithm and data before committing to persuasion or withdrawal based on the projection.
Argument structure (Toulmin):
Grounds

Engineer A's 100-year storm surge determination is grounded in newly released historic weather data and a newly developed algorithm incorporating that data.

Warrant

Engineers must apply sound professional judgment using the best currently available data and methodology when making safety determinations, even absent codified standards.

Rebuttal

Would not apply if the algorithm's methodology were unverified, untested by peer review, not generally accepted in the profession, or if the recommendation rested on speculative concern rather than data driven analysis.

Professional Judgment on Technical Competence

If a local building code mandated a lower storm surge standard than Engineer A's 100-year projection, should Engineer A still withdraw upon Client A's refusal to exceed the code minimum, or comply with the code minimum as satisfying professional obligations?

Options considered:
O1 Withdraw from the project if Client A refuses to exceed a code-mandated lower standard that Engineer A believes is unsafe. Board's choice
O2 Treat compliance with the local building code's lower storm surge standard as satisfying Engineer A's professional obligations, and proceed with the design.
O3 Continue to press Client A to exceed the code minimum, but accept the code-mandated standard as a fallback if persuasion fails, rather than withdrawing.
Argument structure (Toulmin):
Grounds

Hypothetical: a local building code mandates a storm surge design standard lower than Engineer A's 100-year projection, and Client A refuses to exceed that code minimum.

Warrant

Code section II.1's paramount safety duty is not displaced by mere regulatory compliance; code minimums function as floors, not ceilings, for independent professional judgment, though II.1.b directs engineers to approve only documents conforming to applicable standards.

Rebuttal

Would not apply if the code minimum itself reflected a considered, publicly vetted safety determination representing an acceptable risk tradeoff, in which case compliance with the code might be treated as sufficient.

Engineer A Conditional Withdrawal Duty Owner Cost Refusal Design Limit

Should Engineer A separately notify environmental regulatory authorities about the risk of environmental damage from a lower storm surge standard, or treat that risk as a factor reinforcing the persuasion and withdrawal duty already owed to Client A?

Options considered:
O1 Use the environmental damage risk as additional justification within ongoing persuasion of Client A and potential withdrawal, without separate regulatory notification. Board's choice
O2 Independently inform environmental regulatory authorities of the foreseeable property and environmental damage risk from the lower design standard.
O3 Address only the client relationship and public safety persuasion, treating environmental risk as outside Engineer A's scope of responsibility.
Argument structure (Toulmin):
Grounds

Client A's cost-driven refusal of the 100-year storm surge standard increases the risk of future property and environmental damage.

Warrant

Environmental protection under III.2.d is instrumental to, and reinforces, the overarching duty to hold public welfare paramount under II.1, rather than constituting a co-equal independent obligation running to environmental regulators.

Rebuttal

Would not apply if the environmental damage were imminent and severe enough to independently warrant regulatory notification, analogous to the disclosure obligations recognized in BER Cases 04-8 and 07-6.

Engineer A Public Safety Duty
Event Timeline (7)
7 sequenced 6 actions 1 events
Case timeline
Client A, a developer, retains Engineer A to perform hydrodynamic modeling and coastal risk assessment for a residential development project near a coastal area.
Causal-normative reasoning(confidence 0.70)
Client A's decision to retain the engineer's services sets in motion the technical evaluation that follows, so even though this action carries no explicit normative fulfillment or violation, it is causally significant as the trigger for the professional safety determination that anchors the entire case.
Newly released information and a recently developed algorithm incorporating newly identified historic weather data become available, leading Engineer A to conclude the project should be built to a 100-year projected storm surge elevation due to public safety risks.
State changes (2)
  • began: Coastal Storm Surge Safety Risk
  • began: Property And Environmental Damage Exposure
Engineer A, based on newly released information and a recently developed algorithm incorporating newly identified historic weather data, determines that the project should be built to a 100-year projected storm surge elevation due to public safety risks.
At stake (1)
  • Obligation to Protect Public Health and Safety
Fulfills (1)
  • Obligation to Exercise Professional Judgment Based on Technical Competence
Causal-normative reasoning(confidence 0.80)
By fulfilling the obligation to exercise professional judgment based on technical competence and being guided by paramountcy of safety and environmental protection, this determination is the critical causal link that transforms new data and client retention into a concrete safety standard whose rejection by the client sets off the ensuing chain of persuasion and withdrawal.
State changes (2)
  • began: Coastal Storm Surge Safety Risk
  • began: Property And Environmental Damage Exposure
The Owner refuses to agree that the residential development project be built to the 100-year projected storm surge elevation, citing the increased cost.
Causal-normative reasoning(confidence 0.70)
The client's refusal of the recommended standard directly follows from the engineer's professional safety determination and directly causes both the engineer's continued persuasion efforts and separate building code advocacy, making it a pivotal but normatively neutral pivot point that escalates the ethical stakes without itself fulfilling or violating a duty.
State changes (2)
  • began: Coastal Storm Surge Safety Risk
  • began: Client Duty Versus Public Safety Conflict
The BER prescribes that Engineer A should continue to pursue discussions with Client A to convince the client of the danger to future residents and the general public and the potential for significant property and environmental damage.
At stake (1)
  • Obligation to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.75)
Because Engineer A's persistence in persuading the client stems directly from the client's refusal to accept the safety-based standard, this action is guided by paramountcy of public health and safety and environmental protection, and its failure to change the client's position is what ultimately forces the more consequential step of withdrawing from the project.
The BER prescribes that if Client A refuses to agree with Engineer A's design standard, Engineer A should withdraw from the project.
Fulfills (1)
  • Obligation to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.80)
As the culmination of the client's repeated refusal and the engineer's failed persuasion, withdrawing from the project fulfills the obligation to protect public health and safety and is guided by the paramountcy of that safety, demonstrating that when persuasion fails, removing oneself from the engagement is the necessary final safeguard against compromised professional standards.
The BER prescribes that Engineer A should also consider contacting local government officials to advocate for implementation of appropriate and updated region-wide building codes in the geographical area where or near where the project is being built.
Fulfills (1)
  • Obligation to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.75)
Because Engineer A's Building Code Advocacy arose directly from the Client's refusal to adopt the safer standard, pursuing code-level advocacy instead of silently dropping the issue fulfills the paramount obligation to protect public health and safety and reflects the environmental protection principle, ensuring that the safety concerns raised by the new data are addressed through a systemic channel even after the client relationship could not resolve them.
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, an engineer in private practice retained by Client A, a developer, to perform hydrodynamic modeling and coastal risk assessment related to climate change and sea level rise for a planned residential development near the coast. The jurisdiction where the project will be built currently has no building code governing storm surge design. Using newly released data and a recently developed algorithm incorporating updated historic weather records, you have determined that the project should be designed to withstand a 100-year projected storm surge elevation, given the public safety risks present even at lower surge projections. Client A has rejected this recommendation due to the additional construction costs involved and wants to proceed with a lower design standard. You must now consider how to proceed with your professional obligations regarding this project, the client relationship, and any broader public safety concerns tied to the absence of a governing code.

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: Public Responsibility EngineerConsultant Engineer

Guided by: Public Welfare in Coastal Design, Public Welfare in Storm Surge Design, Client Loyalty Balanced Against Safety

Tension between Engineer A Client Persuasion Duty and Owner Cost Refusal Design Limit

Attaches to role: Public Responsibility Engineer

Tension between Engineer A Conditional Withdrawal Duty and Owner Cost Refusal Design Limit

Attaches to role: Public Responsibility Engineer

The engineer's fundamental duty to hold public safety paramount is directly constrained by the owner's refusal to fund the design elements needed to satisfy that safety standard. This is arguably the core ethical conflict of the case, more fundamental than the persuasion or withdrawal duties that flow from it, since it defines what triggers those subsidiary obligations.

Attaches to role: Public Responsibility Engineer

The duty to keep attempting to persuade the owner can conflict with the duty to withdraw once persuasion has clearly failed. Continuing to negotiate too long risks tacit participation in an unsafe design, while withdrawing too quickly risks abandoning a client relationship and opportunity to influence the outcome before persuasion is genuinely exhausted.

Attaches to role: Public Responsibility Engineer

The engineer is bound by a professional limit never to let cost concerns override safety, while simultaneously operating under an owner-imposed budget constraint that refuses to pay for the very safety measures at issue. These two constraints box the engineer in, since satisfying one (refusing to compromise safety) means violating the practical limit imposed by the other (the owner's budget), leaving no compliant path forward without escalation.

Attaches to role: Public Responsibility Engineer
Client A Roles in this case: / Owner (Developer)

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

The engineer's fundamental duty to hold public safety paramount is directly constrained by the owner's refusal to fund the design elements needed to satisfy that safety standard. This is arguably the core ethical conflict of the case, more fundamental than the persuasion or withdrawal duties that flow from it, since it defines what triggers those subsidiary obligations.

The engineer's fundamental duty to hold public safety paramount is directly constrained by the owner's refusal to fund the design elements needed to satisfy that safety standard. This is arguably the core ethical conflict of the case, more fundamental than the persuasion or withdrawal duties that flow from it, since it defines what triggers those subsidiary obligations.

The engineer is bound by a professional limit never to let cost concerns override safety, while simultaneously operating under an owner-imposed budget constraint that refuses to pay for the very safety measures at issue. These two constraints box the engineer in, since satisfying one (refusing to compromise safety) means violating the practical limit imposed by the other (the owner's budget), leaving no compliant path forward without escalation.

The Board’s deliberation

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

Engineer A should continue to pursue discussions with Client A to convince Client A of the danger in which future residents, as well as the general public, could be placed, and the potential for significant property and environmental damage. If Client A refuses to agree with Engineer A’s design standard, Engineer A should withdraw from the project.
Opening States (7)
No Building Code In Project Area Engineer A Storm Surge Finding Coastal Storm Surge Safety Risk Owner Cost Based Refusal Presumed Good Faith Determination Client Duty Versus Public Safety Conflict Property And Environmental Damage Exposure
Summary
  • When an owner's cost constraints threaten to undermine public safety, the engineer's paramount duty to safety requires active persuasion efforts before any consideration of withdrawal.
  • The duty to withdraw from a project is not a first response but a conditional fallback that only becomes relevant after persuasion has failed to resolve the safety conflict.
  • Budget refusals by clients do not excuse engineers from the obligation to design to code and safety standards, they instead trigger a professional obligation to advocate and document rather than simply comply.

© Licensed under the GNU GPL v3