Step 4: Full View

Entities, provisions, decisions, and narrative

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

349

Entities

5

Provisions

2

Precedents

17

Questions

27

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's public safety obligation undergoes a two-stage sequential transfer: first, the faithful agent notification duty is discharged by formally advising Client A in writing of the 100-year storm surge risk and its rejection, transferring formal notice of the deficiency to the client's record; second, upon withdrawal, the residual obligation to protect future residents transfers from Engineer A's private professional role to local government officials and public authorities, who become the new obligated actors capable of establishing a regulatory floor. Engineer A's post-withdrawal notification is the mechanism of transfer — it is the act by which responsibility for addressing the identified risk is handed off to a body with jurisdiction and enforcement capacity, relieving Engineer A of the duty to prevent harm through continued project participation while ensuring the risk does not disappear with Engineer A's departure.
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
II.1. Engineers shall hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 69)
Obligation
Engineer A 100-Year Storm Surge Recommendation Obligation
Holding public safety paramount directly requires recommending the 100-year storm surge standard to protect future residents.
Action
Accept Coastal Risk Engagement
Taking on this project requires the engineer to hold public safety paramount when addressing environmental risk.
State
Public Safety at Risk. Coastal Residential Development Storm Surge
Engineer A must hold paramount the safety of future residents exposed to storm surge risk.
Obligation (14)
  • Engineer A 100-Year Storm Surge Recommendation Obligation
    Holding public safety paramount directly requires recommending the 100-year storm surge standard to protect future residents.
  • Engineer A Non-Acquiescence Client Cost Refusal Storm Surge Obligation
    Paramount duty to public safety prohibits yielding to client cost preferences that endanger future residents.
  • Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation
    Paramount public safety duty requires assessing whether further escalation is needed after client refuses the safety standard.
  • Engineer A Faithful Agent Written Risk Notification Storm Surge Obligation
    Holding public safety paramount requires notifying the client in writing of the material risks created by building below the storm surge elevation.
  • Engineer A Formal Client Project Failure Risk Notification Storm Surge Obligation
    Paramount public safety duty requires formally advising the client that the project as defined will fail its public safety objectives.
  • Engineer A Graduated Escalation Before Withdrawal Storm Surge Obligation
    Paramount public safety duty requires pursuing escalation steps rather than simply acquiescing or withdrawing without action.
  • Engineer A Coastal Risk Assessment Persistent Client Persuasion Before Withdrawal
    Paramount public safety duty obligates continued efforts to persuade the client of the danger before withdrawing.
  • Engineer A Coastal Risk Assessment Cost-Benefit Safety Primacy Determination
    Paramount public safety duty requires determining that cost-reduction interests do not override the apparent risk to future residents.
  • Engineer A Coastal Risk Assessment 100-Year Storm Surge Design Standard Recommendation
    Holding public safety paramount directly underpins the obligation to recommend the 100-year storm surge design standard.
  • Engineer A Coastal Risk Assessment Client Cost-Refusal Non-Acquiescence
    Paramount public safety duty prohibits acquiescing to cost-driven refusals that endanger the public.
  • Engineer A Coastal Risk Assessment Post-Cost-Refusal Escalation Assessment
    Paramount public safety duty requires assessing the need for escalation after the client refuses the safety standard.
  • Engineer A Wetland Case BER 04-8 Incidental Observation Safety Disclosure
    Paramount public safety duty requires disclosing observed environmental violations that could harm the public.
  • Engineer A Threatened Species Case BER 07-6 Threatened Species Report Inclusion
    Paramount public safety and welfare duty extends to environmental risks such as threatened species impacts that affect public welfare.
  • Engineer A Threatened Species Case BER 07-6 Non-Endangered Threatened Species Disclosure
    Paramount public welfare duty requires disclosing environmental risks to public authorities even for non-endangered threatened species.
Action (4)
  • Accept Coastal Risk Engagement
    Taking on this project requires the engineer to hold public safety paramount when addressing environmental risk.
  • Determine 100-Year Surge Standard
    Setting the safety standard directly governs whether public health and safety are adequately protected.
  • Continue Advocating Higher Safety Standard
    Advocating for a higher standard reflects the duty to hold public safety paramount above client preferences.
  • Withdraw from Project
    Withdrawal may be necessary to uphold the paramount duty to public safety if the engineer cannot ensure it.
State (5)
  • Public Safety at Risk. Coastal Residential Development Storm Surge
    Engineer A must hold paramount the safety of future residents exposed to storm surge risk.
  • Client Refusal of 100-Year Storm Surge Elevation Recommendation
    Client A's refusal to adopt the safety standard directly threatens public welfare, which Engineer A must hold paramount.
  • Confirmed Risk Without Adequate Safeguards. Storm Surge Elevation
    The identified storm surge risk without protective safeguards is a direct public safety concern Engineer A must prioritize.
  • Public Safety at Risk from Inadequate Storm Surge Design Standard
    Foreseeable harm to future residents from an inadequate design standard is the core public safety concern Engineer A must hold paramount.
  • Regulatory Standard Climate Gap. No Code Jurisdiction
    The absence of adequate regulatory standards compounds public safety risk that Engineer A must hold paramount.
Constraint (12)
  • Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint
    The paramount safety obligation requires Engineer A to self-impose a safety standard even absent a local code.
  • Engineer A Client Cost-Refusal Non-Acquiescence Storm Surge Constraint
    Holding public safety paramount prohibits acquiescing to client cost-driven refusal to meet the safe design elevation.
  • Engineer A Public Safety Paramount Over Client Cost Preference. Storm Surge
    This provision is the direct source of the canon that public safety must be held paramount over client cost preferences.
  • Engineer A Cost-Benefit Safety Primacy Storm Surge Non-Subordination
    The paramount safety obligation prohibits subordinating public safety to cost-benefit considerations.
  • Engineer A No-Code Jurisdiction Safety Standard Self-Imposition Storm Surge
    The paramount safety obligation requires Engineer A to self-impose a storm surge safety standard where no code exists.
  • Engineer A Client Cost-Refusal Non-Acquiescence Storm Surge Safety
    The paramount safety obligation directly prohibits acquiescing to the client's cost-driven refusal to build to the safe elevation.
  • Engineer A Public Safety Paramount Client Cost Preference Storm Surge
    This provision is the foundational source of the constraint that public safety must prevail over client cost preferences.
  • Engineer A Client Cost-Refusal Withdrawal Trigger Storm Surge
    The paramount safety obligation ultimately requires withdrawal if the client refuses to meet the safety standard.
  • Engineer A Post-Client-Refusal Escalation Assessment Constraint. Storm Surge
    The paramount safety obligation requires Engineer A to assess whether escalation is needed following client refusal.
  • Engineer A Capital Constraint Resilience Gap Disclosure. Storm Surge Elevation
    The paramount safety obligation requires disclosure of the resilience gap created by the client's cost-based refusal.
  • Engineer A Client Budget Limitation Storm Surge Design Constraint
    The paramount safety obligation constrains how Engineer A responds to the client's budget-driven design limitation.
  • Engineer A Client Budget Limitation Storm Surge Design Standard
    The paramount safety obligation constrains Engineer A from accepting a lower design standard due to client financial limitations.
Principle (11)
  • Public Welfare Paramount Invoked By Engineer A Coastal Risk Assessment
    Engineer A's determination to build to 100-year storm surge elevation directly embodies holding public safety paramount.
  • Non-Acquiescence to Client Directive Suppressing Safety Analysis Invoked By Engineer A
    Refusing client pressure to lower safety standards reflects the paramount duty to public safety.
  • Client Direction Does Not Authorize Ethical Violation Invoked By Engineer A
    Client instructions cannot override the engineer's paramount obligation to public safety.
  • Post-Client-Refusal Escalation Assessment Obligation Invoked By Engineer A
    Assessing whether to escalate after client refusal is driven by the paramount duty to protect public safety.
  • Project Withdrawal as Ethical Recourse Invoked by Engineer A
    Withdrawing from a project that endangers the public upholds the paramount safety obligation.
  • Public Welfare Paramount Invoked by Engineer A Coastal Risk Assessment
    Engineer A's insistence on the 100-year storm surge standard to protect future residents directly embodies this provision.
  • Non-Acquiescence to Client Directive Suppressing Safety Analysis Invoked by Engineer A
    Maintaining the professionally determined safety standard against client direction reflects the paramount public safety duty.
  • Client Direction Does Not Authorize Ethical Violation Invoked by Engineer A Coastal Case
    Client instructions to lower standards do not override the engineer's paramount public safety obligation.
  • Post-Client-Refusal Escalation Assessment Obligation Invoked by Engineer A
    Evaluating escalation options after client refusal is grounded in the paramount duty to protect the public.
  • Proportional Escalation Obligation Invoked by Engineer A Coastal Case
    The broad geographic scope of the risk justifies escalation consistent with the paramount public safety duty.
  • Client Loyalty Obligation of Engineer A Bounded by Public Safety
    Client loyalty is explicitly bounded by the paramount obligation to public safety under this provision.
Role (4)
  • Engineer A Coastal Risk Assessment Engineer
    Engineer A must hold paramount public safety when conducting hydrodynamic modeling and coastal risk assessment for the residential development.
  • Engineer A Present Case Coastal Risk Assessment
    Engineer A determined elevated storm surge risk and is obligated to prioritize public safety over client preferences when recommending design standards.
  • Engineer A Wetland Delineation Case (BER 04-8)
    Engineer A discovered illegal wetland fill and must hold paramount public safety and environmental welfare in responding to that violation.
  • Engineer A Threatened Species Case (BER 07-6)
    Engineer A received a report of threat to a protected species and must hold paramount public welfare and environmental safety in deciding how to proceed.
Event (3)
  • No Building Codes Exist
    The absence of building codes creates a public safety gap that engineers must address by holding public safety paramount.
  • Client Refuses Higher Standard
    When a client refuses a higher safety standard, the engineer must still prioritize public health and safety above client preferences.
  • Public Safety Risk Persists
    A persisting public safety risk directly implicates the engineer's paramount duty to protect public health and welfare.
Resource (5)
  • NSPE Code of Ethics for Engineers
    This provision is the primary normative authority requiring Engineer A to hold public safety paramount when the client refuses the recommended design elevation.
  • Qualitative Risk Assessment. Storm Surge Public Safety
    This provision requires Engineer A to weigh the likelihood and magnitude of harm to future residents, which is directly assessed in this risk evaluation.
  • Hydrodynamic Modeling and Coastal Risk Assessment Methodology
    This provision's mandate to protect public safety is grounded in the technical determination of storm surge risk that this methodology provides.
  • Coastal Hazard Storm Surge Algorithm and Historic Weather Data
    This provision's public safety obligation is directly informed by the technical data establishing the storm surge threat to future residents.
  • Engineer Safety Recommendation Rejection Standard – Storm Surge Context
    This provision underlies the standard governing Engineer A's obligations to continue advocating for public safety after the client rejects the recommendation.
Capability (11)
  • Engineer A Public Welfare Paramountcy Storm Surge
    This provision directly requires engineers to hold public safety paramount, which is the core obligation this capability addresses.
  • Engineer A Storm Surge Cost-Refusal Non-Acquiescence
    Holding public safety paramount requires not acquiescing to cost-driven refusals that endanger future residents.
  • Engineer A No-Code Jurisdiction Proactive Safety Standard Recommendation
    The paramount duty to public safety applies even in the absence of a local building code.
  • Engineer A Present Case Public Welfare Paramountcy Recognition Capability
    This capability directly operationalizes the paramount duty to public health, safety, and welfare.
  • Engineer A Present Case Storm Surge Non-Acquiescence Capability
    Refusing to acquiesce to cost-driven safety compromises is a direct expression of holding public welfare paramount.
  • Engineer A Present Case No-Code Jurisdiction Proactive Safety Recommendation Capability
    The paramount safety obligation extends to no-code jurisdictions, requiring proactive safety recommendations.
  • Engineer A Present Case Cost-Benefit Safety Primacy Determination Capability
    Determining that safety must take primacy over cost directly reflects the paramount duty to public welfare.
  • Engineer A Present Case Persistent Client Safety Persuasion Capability
    Persistently persuading the client of danger to future residents is an expression of holding public safety paramount.
  • Engineer A Climate-Adjusted Design Standard Gap Identification
    Identifying gaps in design standards that leave the public exposed to risk relates directly to the paramount safety obligation.
  • Engineer A Faithful Agent Written Risk Notification Storm Surge
    Notifying relevant parties of storm surge risk is required by the duty to hold public safety paramount.
  • Engineer A Client Budget Constraint Disclosure Storm Surge
    Disclosing that budget constraints create public safety risks is required by the paramount duty to public welfare.
II.1.a. 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 51)
Obligation
Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation
When the client overrules the storm surge recommendation, this provision requires assessing whether to notify appropriate authorities.
Action
Continue Advocating Higher Safety Standard
When the engineer's safety judgment is overruled, this provision requires notifying the employer and appropriate authorities.
State
Client Refusal of 100-Year Storm Surge Elevation Recommendation
Client A's overruling of Engineer A's safety recommendation triggers the obligation to notify appropriate authorities.
Obligation (8)
  • Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation
    When the client overrules the storm surge recommendation, this provision requires assessing whether to notify appropriate authorities.
  • Engineer A Graduated Escalation Before Withdrawal Storm Surge Obligation
    This provision directly requires notifying the employer or client and appropriate authorities when safety judgment is overruled, matching the graduated escalation obligation.
  • Engineer A No-Code Jurisdiction Climate Risk Disclosure Obligation
    Absence of applicable building code in a hazardous area requires notifying appropriate authorities as circumstances endangering life or property.
  • Engineer A Coastal Risk Assessment Post-Cost-Refusal Escalation Assessment
    Client overruling the storm surge standard triggers the obligation to notify appropriate authorities under this provision.
  • Engineer A Coastal Risk Assessment No-Code Jurisdiction Climate Risk Proactive Disclosure
    Proactive disclosure to local government officials when no building code exists aligns with notifying appropriate authorities about endangering circumstances.
  • Engineer A Wetland Case BER 04-8 Incidental Observation Safety Disclosure
    If the client fails to act on the wetland violation, this provision requires notifying appropriate authorities about the endangering situation.
  • Engineer A Wetland Case BER 04-8 Environmental Law Violation Client Inquiry and Remediation Direction
    Unauthorized wetland fill constitutes a circumstance endangering property and environment, requiring notification of appropriate authorities if the client does not remediate.
  • Engineer A Threatened Species Case BER 07-6 Faithful Agent Client Notification of Inclusion
    Notifying the client that threatened species findings will be reported to public authorities aligns with the requirement to notify the employer or client when safety-related judgment may be overruled.
Action (3)
  • Continue Advocating Higher Safety Standard
    When the engineer's safety judgment is overruled, this provision requires notifying the employer and appropriate authorities.
  • Contact Government Officials for Code Advocacy
    Notifying appropriate authorities when judgment is overruled in a life-endangering situation directly governs this action.
  • Withdraw from Project
    Before or upon withdrawal due to overruled safety judgment, the engineer must notify relevant authorities as required by this provision.
State (5)
  • Client Refusal of 100-Year Storm Surge Elevation Recommendation
    Client A's overruling of Engineer A's safety recommendation triggers the obligation to notify appropriate authorities.
  • Post-Client-Refusal Regional Code Advocacy Obligation
    After the client's refusal endangers life, Engineer A must notify appropriate authorities such as local government.
  • Client A Cost-Based Refusal of 100-Year Storm Surge Standard
    The cost-based refusal that overrules Engineer A's safety judgment requires notification of the employer and appropriate authorities.
  • Confirmed Risk Without Adequate Safeguards. Storm Surge Elevation
    The confirmed risk following client refusal requires Engineer A to escalate notification to appropriate authorities.
  • No Building Code in Project Jurisdiction
    The absence of a building code means Engineer A must notify appropriate authorities when safety is endangered without regulatory backstop.
Constraint (8)
  • Engineer A Graduated Escalation Before Withdrawal. Storm Surge Client Refusal
    This provision requires Engineer A to notify appropriate authorities when judgment is overruled, supporting the graduated escalation sequence.
  • Engineer A Post-Client-Refusal Escalation Assessment Constraint. Storm Surge
    This provision directly requires Engineer A to assess and pursue notification of appropriate authorities after client refusal endangers public safety.
  • Engineer A Client Cost-Refusal Withdrawal Trigger Storm Surge
    This provision supports the requirement to notify authorities and ultimately withdraw when the client's refusal endangers life or property.
  • Engineer A Written Documentation Safety Recommendation Client Refusal Storm Surge
    This provision supports documenting the overruled judgment and notifying appropriate parties of the client's refusal.
  • Engineer A Capital Constraint Resilience Gap Disclosure. Storm Surge Elevation
    This provision requires disclosure of the safety gap to the employer, client, and appropriate authorities when judgment is overruled.
  • Engineer A Post-Withdrawal Regional Code Advocacy Storm Surge
    This provision supports Engineer A contacting local government officials as an appropriate authority after the client overrules the safety recommendation.
  • Engineer A Persistent Persuasion Before Withdrawal Storm Surge
    This provision underlies the requirement to notify the employer or client before escalating further or withdrawing.
  • Engineer A BER 04-8 Environmental Law Violation Regulatory Escalation Wetland Fill
    This provision requires escalation to appropriate regulatory authorities when the client fails to remediate the environmental violation.
Principle (9)
  • Post-Client-Refusal Escalation Assessment Obligation Invoked By Engineer A
    After client refusal, Engineer A must assess notifying appropriate authorities, directly reflecting this provision.
  • Proactive Risk Disclosure Invoked By Engineer A
    Communicating storm surge risk to local government officials and others mirrors the obligation to notify appropriate authorities.
  • Written Documentation Requirement for Safety Notification Invoked By Engineer A
    Documenting safety notifications in writing supports the notification obligation when judgment is overruled.
  • Post-Client-Refusal Escalation Assessment Obligation Invoked by Engineer A
    Engineer A's required assessment of whether to notify authorities after client refusal directly applies this provision.
  • Building Code Advocacy Engineer Principle Invoked By Engineer A
    Contacting local government officials about building code deficiencies reflects notifying appropriate authorities when safety is endangered.
  • Building Code Advocacy Engineer Principle Invoked by Engineer A
    Advocating to local officials for updated building codes reflects notifying appropriate authorities when safety judgments are overruled.
  • Proportional Escalation Obligation Invoked by Engineer A Coastal Case
    The broad risk scope requiring notification of multiple jurisdictions directly reflects the obligation to notify appropriate authorities.
  • Regulatory Gap Awareness and Proactive Risk Disclosure Invoked By Engineer A
    Disclosing the regulatory gap to authorities when no building code exists reflects notifying appropriate authorities about endangerment.
  • Regulatory Gap Awareness Invoked by Engineer A Coastal Case
    Identifying and disclosing inadequate building codes to relevant authorities reflects the obligation to notify when safety is at risk.
Role (5)
  • Engineer A Present Case Coastal Risk Assessment
    When Client A refused to implement Engineer A's recommended design standards, Engineer A was obligated to notify the employer or client and appropriate authorities such as local government officials.
  • Engineer A Coastal Risk Assessment Engineer
    If Engineer A's professional judgment on coastal risk mitigation is overruled by the developer, Engineer A must notify appropriate authorities to protect public safety.
  • Engineer A Wetland Delineation Case (BER 04-8)
    Upon discovering the client's illegal wetland fill, Engineer A's judgment was effectively overruled by the client's actions and Engineer A must notify appropriate authorities.
  • Engineer A Threatened Species Case (BER 07-6)
    If the developer client disregards the threatened species report, Engineer A must notify appropriate authorities as the situation endangers environmental welfare and public interest.
  • Local Government Officials Building Code Authority
    Local government officials are identified as the appropriate authority to be notified by Engineer A when the developer overrules Engineer A's safety recommendations.
Event (2)
  • Client Refuses Higher Standard
    When the client overrules the engineer's judgment on a safer standard, the engineer must notify appropriate authorities of the resulting danger.
  • Public Safety Risk Persists
    A continuing public safety risk after the client's refusal requires the engineer to escalate notification to appropriate authorities.
Resource (4)
  • Engineer Public Safety Escalation Standard. Client Refusal Context
    This provision directly governs what Engineer A must do after the owner refuses the recommended design, including notifying appropriate authorities.
  • Absence of Local Building Code. Unregulated Jurisdiction Context
    This provision's escalation requirement is shaped by the absence of a local building code, which affects which authorities Engineer A can notify.
  • Engineer Public Safety Escalation – Local Government Building Code Advocacy
    This provision provides the basis for Engineer A contacting local government officials as an appropriate authority when the client overrules the safety recommendation.
  • BER Case No. 04-8
    This precedent establishes the course of action for engineers whose safety recommendations are overruled, directly supporting application of this provision.
Capability (7)
  • Engineer A Storm Surge Post-Refusal Escalation Assessment
    This provision requires assessing whether to notify appropriate authorities when client overrules engineer judgment on safety matters.
  • Engineer A Post-Client-Override Regulatory Escalation Assessment Storm Surge
    This capability directly addresses the obligation to escalate to appropriate authorities after a client override endangering life or property.
  • Engineer A Graduated Escalation Before Withdrawal Storm Surge
    The graduated escalation sequence includes notifying the employer, client, and appropriate authorities as required by this provision.
  • Engineer A Faithful Agent Written Risk Notification Storm Surge
    Written notification to the client and potentially other authorities when judgment is overruled is directly required by this provision.
  • Engineer A Present Case Post-Cost-Refusal Escalation Assessment Capability
    Assessing whether to notify appropriate authorities after client refusal directly corresponds to this provision's requirements.
  • Engineer A Building Code Advocacy Storm Surge
    Advocating to local government officials represents notifying an appropriate authority when client decisions endanger public safety.
  • Engineer A Present Case Building Code Advocacy Capability
    Advocacy to local officials after client override is a form of notifying appropriate authority as required by this provision.
II.1.b. Engineers shall approve only those engineering documents that are in conformity with applicable standards.
How this applies in the case (showing 3 of 42)
Obligation
Engineer A 100-Year Storm Surge Recommendation Obligation
Approving only conforming engineering documents requires recommending and approving designs that meet the 100-year storm surge standard.
Action
Apply Newly Released Algorithm and Data
Engineers must ensure that engineering documents and methods conform to applicable standards before approving them.
State
Climate-Informed 100-Year Storm Surge Elevation Recommendation
Engineer A should only approve engineering documents that conform to applicable standards, including the recommended storm surge elevation.
Obligation (6)
  • Engineer A 100-Year Storm Surge Recommendation Obligation
    Approving only conforming engineering documents requires recommending and approving designs that meet the 100-year storm surge standard.
  • Engineer A Non-Acquiescence Client Cost Refusal Storm Surge Obligation
    Engineer A must not approve documents for a design that does not conform to the applicable storm surge standard, regardless of client cost preferences.
  • Engineer A Coastal Risk Assessment 100-Year Storm Surge Design Standard Recommendation
    This provision directly supports the obligation to recommend and approve only documents conforming to the applicable storm surge standard.
  • Engineer A Coastal Risk Assessment Client Cost-Refusal Non-Acquiescence
    Engineer A cannot approve non-conforming engineering documents even under client cost-driven pressure.
  • Engineer A Threatened Species Case BER 07-6 Threatened Species Report Inclusion
    Approving only conforming documents requires including all relevant findings such as the threatened species report in submitted documents.
  • Engineer A Coastal Risk Assessment Objective Completeness Public Authority Reports
    Approving only conforming documents requires that reports submitted to public authorities be objective, truthful, and complete.
Action (3)
  • Apply Newly Released Algorithm and Data
    Engineers must ensure that engineering documents and methods conform to applicable standards before approving them.
  • Determine 100-Year Surge Standard
    Approving a surge standard requires it to conform with applicable engineering and safety standards.
  • Present Findings to Client
    Presenting findings that form the basis of engineering documents requires those findings to conform to applicable standards.
State (4)
  • Climate-Informed 100-Year Storm Surge Elevation Recommendation
    Engineer A should only approve engineering documents that conform to applicable standards, including the recommended storm surge elevation.
  • Regulatory Standard Climate Gap. No Code Jurisdiction
    The absence of adequate standards means Engineer A cannot approve documents that fail to meet appropriate safety benchmarks.
  • Newly Released Climate Data Informing Safety Standard
    Engineer A must ensure engineering documents conform to standards informed by the latest climate data.
  • No Building Code Jurisdiction for Residential Development Project
    The lack of a building code in the jurisdiction makes conformity with applicable standards Engineer A's direct professional responsibility.
Constraint (7)
  • Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint
    This provision requires conformity with applicable standards, constraining Engineer A from approving documents below the appropriate safety standard even absent a local code.
  • Engineer A No-Code Jurisdiction Safety Standard Self-Imposition Storm Surge
    This provision prohibits approving engineering documents that do not conform to applicable standards, requiring self-imposition of a standard where none is locally mandated.
  • Engineer A Climate-Adjusted Design Standard Gap. No Code Jurisdiction
    This provision requires conformity with applicable standards, constraining Engineer A from approving documents based on outdated or inapplicable code baselines.
  • Engineer A Newly Released Algorithm Competence Currency Constraint. Coastal Storm Surge
    This provision requires that approved engineering documents conform to applicable standards, including use of current data and modeling methods.
  • Engineer A Newly Released Algorithm Competence Currency Storm Surge
    This provision prohibits approving documents based on outdated datasets or superseded methods when current standards require updated modeling.
  • Engineer A Client Cost-Refusal Non-Acquiescence Storm Surge Constraint
    This provision prohibits approving engineering documents that do not conform to applicable safety standards regardless of client cost preferences.
  • Engineer A Client Cost-Refusal Non-Acquiescence Storm Surge Safety
    This provision directly prohibits Engineer A from approving documents that fall below the applicable storm surge safety standard due to client refusal.
Principle (6)
  • Climate-Informed Infrastructure Design Standard Invoked By Engineer A
    Applying newly developed algorithms and data to determine conforming design standards reflects approving only documents meeting applicable standards.
  • Client Direction Does Not Authorize Ethical Violation Invoked By Engineer A
    Engineer A cannot certify documents below the required storm surge standard, directly reflecting this provision.
  • Client Direction Does Not Authorize Ethical Violation Invoked by Engineer A Coastal Case
    Client instructions do not authorize Engineer A to approve engineering documents below the required safety standard.
  • Climate-Informed Infrastructure Design Standard Invoked by Engineer A
    Using current data and algorithms to establish the conforming design standard reflects the obligation to approve only conforming documents.
  • Non-Acquiescence to Client Directive Suppressing Safety Analysis Invoked By Engineer A
    Refusing to adopt a lower standard ensures Engineer A does not approve documents that fail to conform to applicable safety standards.
  • Non-Acquiescence to Client Directive Suppressing Safety Analysis Invoked by Engineer A
    Maintaining the 100-year storm surge standard ensures engineering documents conform to applicable professional standards.
Role (2)
  • Engineer A Coastal Risk Assessment Engineer
    Engineer A must only approve engineering documents for the coastal development that conform to applicable building codes and safety standards.
  • Engineer A Present Case Coastal Risk Assessment
    Engineer A must not approve design documents that fail to incorporate the recommended storm surge mitigation standards required by applicable codes.
Event (3)
  • No Building Codes Exist
    Without applicable building codes, engineers must determine what standards apply before approving engineering documents.
  • 100-Year Surge Standard Identified
    The identified 100-year surge standard represents the applicable standard that engineering documents must conform to for approval.
  • Client Refuses Higher Standard
    If the client refuses a standard the engineer deems necessary for conformity, the engineer cannot approve documents that fall short of applicable standards.
Resource (4)
  • Climate-Adjusted Hydraulic and Coastal Design Standard
    This provision requires Engineer A to approve only documents conforming to applicable standards, which this resource defines for storm surge and climate-adjusted design.
  • Hydrodynamic Modeling and Coastal Risk Assessment Methodology
    This provision requires conformity with applicable standards, and this methodology establishes the technical standard Engineer A used to determine the required design elevation.
  • Coastal Hazard Storm Surge Algorithm and Historic Weather Data
    This provision prohibits approving documents not in conformity with applicable standards, and this technical basis defines what the conforming design elevation should be.
  • BER Case No. 07-6
    This precedent establishes the obligation to include all relevant information in professional reports, directly supporting the requirement to approve only conforming engineering documents.
Capability (7)
  • Engineer A Climate-Adjusted Design Standard Gap Identification
    This provision requires approving only documents conforming to applicable standards, making identification of design standard gaps directly relevant.
  • Engineer A No-Code Jurisdiction Proactive Safety Standard Recommendation
    The obligation to approve only conforming documents applies even in no-code jurisdictions, requiring proactive standard recommendations.
  • Engineer A Present Case No-Code Jurisdiction Proactive Safety Recommendation Capability
    Recognizing that no applicable code does not relieve the obligation to meet applicable standards is directly tied to this provision.
  • Engineer A Storm Surge Cost-Refusal Non-Acquiescence
    Refusing to approve documents that do not conform to applicable storm surge standards is required by this provision.
  • Engineer A Present Case Storm Surge Non-Acquiescence Capability
    Not acquiescing to a design that fails to meet applicable storm surge standards directly reflects the obligation to approve only conforming documents.
  • Engineer A Hydrodynamic Modeling Coastal Risk Assessment Competence
    Technical competence in modeling is necessary to determine whether engineering documents conform to applicable safety standards.
  • Engineer A Present Case Hydrodynamic Modeling Capability
    Hydrodynamic modeling capability is required to assess whether design documents conform to applicable storm surge standards.
III.1.b. 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 37)
Obligation
Engineer A Formal Client Project Failure Risk Notification Storm Surge Obligation
This provision directly requires advising the client when the project will not be successful, matching the obligation to notify the client the project will fail its safety objectives.
Action
Present Findings to Client
Presenting findings is the direct opportunity to advise the client if the chosen standard will not adequately protect against coastal risk.
State
Client Refusal of 100-Year Storm Surge Elevation Recommendation
Engineer A must advise Client A that the project will not be successful or safe without adopting the recommended storm surge standard.
Obligation (6)
  • Engineer A Formal Client Project Failure Risk Notification Storm Surge Obligation
    This provision directly requires advising the client when the project will not be successful, matching the obligation to notify the client the project will fail its safety objectives.
  • Engineer A Faithful Agent Written Risk Notification Storm Surge Obligation
    Advising the client of material risks that undermine project success aligns with the duty to inform clients when a project will not be successful.
  • Engineer A Client Budget Constraint Disclosure Storm Surge Obligation
    Communicating that the client's budget refusal creates a risk of project failure directly reflects the duty to advise clients when a project will not be successful.
  • Engineer A Coastal Risk Assessment Cost-Benefit Safety Primacy Determination
    Determining and communicating that cost-reduction interests jeopardize project success aligns with advising the client when the project will not be successful.
  • Engineer A Coastal Risk Assessment Persistent Client Persuasion Before Withdrawal
    Continuing to advise the client of the danger and project failure risk reflects the duty to inform clients when a project will not succeed.
  • Engineer A Wetland Case BER 04-8 Environmental Law Violation Client Inquiry and Remediation Direction
    Advising the client that unauthorized wetland fill actions jeopardize the project's legal and environmental success aligns with this provision.
Action (2)
  • Present Findings to Client
    Presenting findings is the direct opportunity to advise the client if the chosen standard will not adequately protect against coastal risk.
  • Continue Advocating Higher Safety Standard
    Continued advocacy fulfills the duty to advise the client that the lower standard may lead to project or safety failure.
State (4)
  • Client Refusal of 100-Year Storm Surge Elevation Recommendation
    Engineer A must advise Client A that the project will not be successful or safe without adopting the recommended storm surge standard.
  • Client A Cost-Based Refusal of 100-Year Storm Surge Standard
    Engineer A has an obligation to advise the client that cost-based rejection of the safety standard risks project failure and harm.
  • Engineer A Private Practice Client Relationship
    Within the professional client relationship, Engineer A must advise Client A when the project approach will not be successful.
  • Confirmed Risk Without Adequate Safeguards. Storm Surge Elevation
    Engineer A must advise the client that proceeding without adequate safeguards means the project will not be successful in protecting residents.
Constraint (7)
  • Engineer A Preliminary Judgment Disclosure Qualification. Storm Surge Risk
    This provision requires Engineer A to advise the client of the storm surge risk and the likelihood the project will not be successful or safe as proposed.
  • Engineer A Coastal Risk Assessment Written Documentation Constraint
    This provision supports the requirement to document and communicate to the client all relevant risk information indicating the project may not succeed safely.
  • Engineer A Written Documentation Safety Recommendation Client Refusal Storm Surge
    This provision requires Engineer A to advise the client in writing that the project will not be successful without meeting the 100-year storm surge elevation.
  • Engineer A Graduated Escalation Before Withdrawal. Storm Surge Client Refusal
    This provision underlies the requirement to advise the client of project failure risk before escalating or withdrawing.
  • Engineer A Persistent Persuasion Before Withdrawal Storm Surge
    This provision requires Engineer A to persistently advise the client that the project will not be successful before withdrawing.
  • Engineer A Capital Constraint Resilience Gap Disclosure. Storm Surge Elevation
    This provision requires Engineer A to advise the client of the resilience gap and resulting risk of project failure created by the cost-based refusal.
  • Engineer A BER 07-6 Threatened Species Client Notification Inclusion Constraint
    This provision requires Engineer A to advise the client that omitting the threatened species findings would undermine the integrity and success of the project report.
Principle (4)
  • Faithful Agent Notification Obligation for Project Success Risk Invoked By Engineer A
    Advising Client A in writing that building below the 100-year standard creates material risk directly embodies this provision.
  • Faithful Agent Notification Obligation Invoked by Engineer A Coastal Case
    Continuing to advise Client A of danger to residents and project risk reflects the obligation to notify clients when a project will not be successful.
  • Written Documentation Requirement for Safety Notification Invoked By Engineer A
    Documenting the safety recommendation and its basis in writing fulfills the obligation to advise clients of project risk.
  • Client Loyalty Obligation of Engineer A Bounded by Public Safety
    Faithful service to the client includes advising when the project approach creates unacceptable risk of failure or harm.
Role (3)
  • Engineer A Coastal Risk Assessment Engineer
    Engineer A must advise Client A that the residential development project will not be successful or safe if the recommended coastal risk mitigation standards are not adopted.
  • Engineer A Present Case Coastal Risk Assessment
    Engineer A is obligated to advise Client A that proceeding without implementing the recommended design standards will result in an unsafe and unsuccessful project.
  • Engineer A Threatened Species Case (BER 07-6)
    Engineer A must advise the developer client that the condominium project will not be successful if it proceeds in a manner that threatens a protected species.
Event (2)
  • Client Refuses Higher Standard
    The engineer should advise the client that refusing the higher standard may result in project failure to adequately protect against environmental risk.
  • Public Safety Risk Persists
    The engineer is obligated to inform the client that the project will not successfully protect public safety if the risk remains unaddressed.
Resource (3)
  • Qualitative Risk Assessment. Storm Surge Public Safety
    This provision requires Engineer A to advise the client of project risks, which is grounded in this professional assessment of harm likelihood at various design elevations.
  • Engineer Safety Recommendation Rejection Standard – Storm Surge Context
    This provision underlies the obligation to advise the client that the project will not be successful or safe, which this standard applies when the client rejects the recommendation.
  • Hydrodynamic Modeling and Coastal Risk Assessment Methodology
    This provision's duty to advise the client of project failure risk is supported by the technical findings this methodology produces regarding inadequate design elevations.
Capability (6)
  • Engineer A Project Failure Risk Notification Storm Surge
    This provision directly requires advising clients when a project will not be successful, which this capability reframes in terms of public safety failure.
  • Engineer A Client Budget Constraint Disclosure Storm Surge
    Disclosing that budget constraints will cause the project to fail its safety objectives is required by this provision.
  • Engineer A Present Case Persistent Client Safety Persuasion Capability
    Persistently advising the client of the danger and project failure risk directly corresponds to the obligation to advise when a project will not succeed.
  • Engineer A Preliminary Judgment Risk Disclosure Qualification Storm Surge
    Disclosing identified risks while qualifying the preliminary nature of findings is part of advising the client about project success prospects.
  • Engineer A Faithful Agent Written Risk Notification Storm Surge
    Written notification to the client about storm surge risk is a direct expression of the obligation to advise when a project will not be successful.
  • Engineer A Threatened Species Case BER 07-6 Faithful Agent Client Notification Capability
    Advising the developer client that findings would be included in the report reflects the obligation to notify clients of factors affecting project success.
III.2.d. 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 56)
Obligation
Engineer A Building Code Advocacy Storm Surge Obligation
Advocating for building codes addressing storm surge elevation directly supports sustainable development and environmental protection for future generations.
Action
Accept Coastal Risk Engagement
Engaging with coastal environmental risk projects implicates the principle of sustainable development and environmental protection.
State
Moving Target Climate Baseline. Coastal Storm Surge
The evolving climate data baseline directly implicates sustainable development principles requiring protection of the environment for future generations.
Obligation (11)
  • Engineer A Building Code Advocacy Storm Surge Obligation
    Advocating for building codes addressing storm surge elevation directly supports sustainable development and environmental protection for future generations.
  • Engineer A Climate Change Moving Target Design Consideration Storm Surge Obligation
    Treating climate projections as a dynamic moving target reflects the sustainable development principle of protecting environmental quality for future generations.
  • Engineer A Newly Released Algorithm Application Competence Obligation
    Applying newly released climate data and modeling algorithms to address future storm surge risk supports sustainable development by protecting future residents and the environment.
  • Engineer A No-Code Jurisdiction Climate Risk Disclosure Obligation
    Disclosing climate risks in a no-code jurisdiction supports sustainable development by prompting protective measures for future generations.
  • Engineer A Coastal Risk Assessment Building Code Advocacy
    Advocating for region-wide building codes addressing storm surge directly supports sustainable development and environmental protection for future generations.
  • Engineer A Coastal Risk Assessment Newly Released Climate Algorithm Application Competence
    Applying newly released climate data and algorithms to protect against future storm surge aligns with sustainable development principles.
  • Engineer A Coastal Risk Assessment No-Code Jurisdiction Climate Risk Proactive Disclosure
    Proactively disclosing climate risks to promote protective action supports sustainable development and protection of the environment for future generations.
  • Engineer A Wetland Case BER 04-8 Incidental Observation Safety Disclosure
    Disclosing unauthorized wetland fill protects natural resources and environmental quality consistent with sustainable development principles.
  • Engineer A Wetland Case BER 04-8 Environmental Law Violation Client Inquiry and Remediation Direction
    Directing remediation of unauthorized wetland fill directly protects the natural resource base consistent with sustainable development.
  • Engineer A Threatened Species Case BER 07-6 Threatened Species Report Inclusion
    Including threatened species findings in reports supports sustainable development by protecting biodiversity and environmental quality for future generations.
  • Engineer A Threatened Species Case BER 07-6 Non-Endangered Threatened Species Disclosure
    Disclosing risks to threatened species protects environmental quality and biodiversity consistent with sustainable development principles.
Action (4)
  • Accept Coastal Risk Engagement
    Engaging with coastal environmental risk projects implicates the principle of sustainable development and environmental protection.
  • Determine 100-Year Surge Standard
    Choosing the surge standard affects long-term environmental and community resilience, directly invoking sustainable development principles.
  • Contact Government Officials for Code Advocacy
    Advocating for stronger building codes to address environmental risk supports sustainable development for future generations.
  • Continue Advocating Higher Safety Standard
    Pushing for a higher safety standard aligns with protecting the environment and community welfare for future generations.
State (5)
  • Moving Target Climate Baseline. Coastal Storm Surge
    The evolving climate data baseline directly implicates sustainable development principles requiring protection of the environment for future generations.
  • Environmental Damage Risk from Inadequate Storm Surge Standard
    The risk of environmental damage from an inadequate storm surge standard is directly addressed by the sustainable development provision.
  • Climate-Informed 100-Year Storm Surge Elevation Recommendation
    Engineer A's climate-informed recommendation reflects adherence to sustainable development principles protecting future generations.
  • Newly Released Climate Data Informing Safety Standard
    Using current climate data to set safety standards aligns with sustainable development obligations to protect the environment for future generations.
  • Regulatory Standard Climate Gap. No Code Jurisdiction
    The gap between existing standards and current climate science highlights the need for sustainable development principles to guide Engineer A's recommendations.
Constraint (9)
  • Engineer A Environmental Protection Additional Responsibility Storm Surge
    This provision is the direct source of the additional professional responsibility for environmental protection in the coastal development context.
  • Engineer A Climate Moving Target Design Baseline Constraint. Coastal Storm Surge
    This provision encourages sustainable development, requiring Engineer A to account for evolving climate conditions rather than fixed historical baselines.
  • Engineer A Climate Moving Target Design Baseline Storm Surge
    This provision supports the constraint that Engineer A must treat climate data as dynamic in order to protect the environment for future generations.
  • Engineer A Post-Withdrawal Regional Code Advocacy Storm Surge
    This provision encourages Engineer A to advocate for updated regional codes to protect the environment and future residents consistent with sustainable development principles.
  • Engineer A BER 04-8 Environmental Law Violation Client Inquiry Wetland Fill
    This provision supports the constraint that Engineer A must address the unauthorized wetland fill as part of the obligation to protect the environment.
  • Engineer A BER 04-8 Environmental Law Violation Regulatory Escalation Wetland Fill
    This provision supports escalation to regulatory authorities to protect the environment when the client fails to remediate the wetland fill violation.
  • Engineer A BER 07-6 Threatened Species Report Inclusion Constraint
    This provision supports including threatened species findings in the report as part of the obligation to protect the environment for future generations.
  • Engineer A BER 07-6 Threatened Species Client Notification Inclusion Constraint
    This provision supports the constraint that environmental findings must not be suppressed, consistent with the duty to protect the environment.
  • Engineer A Climate-Adjusted Design Standard Gap. No Code Jurisdiction
    This provision encourages sustainable development practices that account for environmental change, supporting the constraint to apply climate-adjusted design standards.
Principle (7)
  • Climate Change as Moving Target in Engineering Design Invoked By Engineer A
    Treating climate data as dynamic inputs to design reflects the principle of sustainable development accounting for future environmental conditions.
  • Climate Change as Moving Target Invoked by Engineer A
    Using newly released data and algorithms to address evolving storm surge risk reflects sustainable development principles protecting future generations.
  • Environmental Stewardship in Engineering Practice Invoked by Engineer A Wetland and Threatened Species Cases
    Environmental stewardship obligations in engineering practice directly reflect the sustainable development principle of this provision.
  • Building Code Advocacy Engineer Principle Invoked By Engineer A
    Advocating for updated building codes addressing climate risk supports sustainable development and environmental protection for future generations.
  • Building Code Advocacy Engineer Principle Invoked by Engineer A
    Promoting region-wide building codes informed by current climate science supports sustainable development for future generations.
  • Climate-Informed Infrastructure Design Standard Invoked By Engineer A
    Incorporating newly identified historic weather data into design standards reflects sustainable development by protecting future residents from environmental risk.
  • Climate-Informed Infrastructure Design Standard Invoked by Engineer A
    Applying current climate science to infrastructure design standards reflects the sustainable development obligation to protect future generations.
Role (4)
  • Engineer A Coastal Risk Assessment Engineer
    Engineer A is encouraged to adhere to sustainable development principles by recommending design standards that protect the coastal environment for future generations.
  • Engineer A Present Case Coastal Risk Assessment
    Engineer A's recommendations for storm surge mitigation and coastal risk standards align with sustainable development principles to protect the coastal environment.
  • Engineer A Wetland Delineation Case (BER 04-8)
    Engineer A must adhere to sustainable development principles by addressing the illegal wetland fill that damages the natural resource base essential for future development.
  • Engineer A Threatened Species Case (BER 07-6)
    Engineer A must adhere to sustainable development principles by ensuring the condominium project does not threaten a protected species or degrade the wetlands environment.
Event (3)
  • 100-Year Surge Standard Identified
    Adopting the 100-year surge standard reflects adherence to sustainable development principles by protecting the environment and future generations.
  • Client Refuses Higher Standard
    The client's refusal to adopt a higher standard conflicts with the principle of sustainable development that engineers are encouraged to uphold.
  • No Building Codes Exist
    The lack of building codes addressing environmental risk highlights the need for engineers to apply sustainable development principles proactively.
Resource (4)
  • NSPE Code of Ethics Section III.2.d
    This provision is directly cited as placing additional environmental protection responsibilities on Engineer A, grounding the obligation to advocate for appropriate design standards.
  • Climate-Adjusted Hydraulic and Coastal Design Standard
    This provision encourages sustainable development practices, and this standard provides the technical framework for incorporating climate projections that protect the environment for future generations.
  • Engineer Public Safety Escalation – Local Government Building Code Advocacy
    This provision supports Engineer A's option to advocate for updated regional building codes as a means of protecting the environment and future residents consistent with sustainable development principles.
  • Absence of Local Building Code. Unregulated Jurisdiction Context
    This provision's sustainable development mandate is particularly relevant given the absence of a local building code that would otherwise enforce minimum environmental and safety standards.
Capability (9)
  • Engineer A Climate Moving Target Design Adaptation
    Treating climate conditions as a dynamic moving target in design directly reflects the principle of sustainable development for future generations.
  • Engineer A Present Case Climate Moving Target Design Capability
    Applying dynamic climate projections to design decisions is a direct expression of sustainable development principles protecting future generations.
  • Engineer A Building Code Advocacy Storm Surge
    Advocating for building codes that address climate-driven storm surge risk supports sustainable development and environmental protection for future generations.
  • Engineer A Present Case Building Code Advocacy Capability
    Advocating for adoption of climate-informed building codes aligns with the sustainable development obligation to protect future generations.
  • Engineer A Newly Released Algorithm Application Competence
    Applying newly released climate data and algorithms to design supports sustainable development by incorporating current environmental science.
  • Engineer A Technical Literature Currency Storm Surge Algorithm
    Monitoring and incorporating newly published climate and storm surge literature supports sustainable development by keeping designs current with environmental science.
  • Engineer A Climate-Adjusted Design Standard Gap Identification
    Identifying gaps in design standards relative to current climate science is necessary to fulfill the sustainable development obligation to protect future generations.
  • Engineer A Wetland Case BER 04-8 Environmental Law Violation Client Inquiry Capability
    Recognizing unauthorized wetland fill as an environmental law violation relates to the obligation to protect the environment under sustainable development principles.
  • Engineer A Wetland Case BER 04-8 Incidental Observation Capability
    Recognizing environmental harm upon observation supports the sustainable development obligation to protect environmental quality.
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 must include all relevant and pertinent information in professional reports submitted to public authorities, including information that may threaten environmental or public interests, regardless of the client's preferences.

Citation Context:

The Board cited this case to reinforce that engineers have an obligation to be objective and truthful in professional reports and must include all relevant information, even when it may be unfavorable to the client's development interests.

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 for potential development as a residential condominium."

Principle Established:

When an engineer discovers a client has violated environmental laws, the engineer must confront the client, demand remedial action in compliance with applicable laws, and if the client fails to act, report the matter to appropriate authorities.

Citation Context:

The Board cited this case to establish the appropriate course of action when an engineer discovers a client has violated environmental laws, including the obligation to notify authorities if the client fails to remedy the violation.

Relevant Excerpts
discussion: "In BER Case No. 04-8 , Engineer A, an environmental engineer, performed wetland delineation services on the client's wetland site. A few months after Engineer A completed the services, he drove by his client's property and noticed that the client had installed a substantial amount of fill material on more than half an acre across a portion of the wetlands without any permits, variances, or permissions."
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 69% Facts Similarity 73% Discussion Similarity 54% Provision Overlap 73% Outcome Alignment 100% Tag Overlap 75%
Shared provisions: I.1, II.1, II.1.a, II.3, II.3.a, III.1.b, III.2, III.3.a Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 68% Discussion Similarity 67% Provision Overlap 42% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 48% Discussion Similarity 59% Provision Overlap 31% Outcome Alignment 100% Tag Overlap 75%
Shared provisions: I.1, II.3.a, III.1.b, III.2.d Same outcome True View Synthesis
Component Similarity 46% Facts Similarity 51% Discussion Similarity 60% Provision Overlap 67% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.1, II.1, II.3, II.3.a, III.1.b, III.2, III.3, III.3.a Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 52% Discussion Similarity 63% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 42% Discussion Similarity 64% Provision Overlap 54% Outcome Alignment 100% Tag Overlap 30%
Shared provisions: I.1, II.1, II.1.a, II.3, II.3.a, III.2, III.3 Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 53% Discussion Similarity 69% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 42% Discussion Similarity 65% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 51% Facts Similarity 37% Discussion Similarity 50% Provision Overlap 42% Outcome Alignment 100% Tag Overlap 40%
Shared provisions: I.1, II.3.a, III.1.b, III.2.d, III.3.a Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 32% Discussion Similarity 64% Provision Overlap 47% Outcome Alignment 100% Tag Overlap 23%
Shared provisions: I.1, II.1, II.1.a, II.3, II.3.a, III.1.b, III.2, III.3.a Same outcome True 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.
II.1. II.1.a. III.1.b.
Board conclusion If Client A refuses to agree with Engineer A's design standard, Engineer A should withdraw from the project.
II.1. II.1.a. II.1.b. III.2.d.
Implicit (4)

Does Engineer A have an obligation to notify local government officials or other public authorities about the identified storm surge risk even after withdrawing from the project, given that no building code exists in the jurisdiction and future residents remain exposed to foreseeable danger?

AnalyticalThe Board's conclusion that Engineer A should withdraw if Client A refuses to accept the 100-year storm surge standard does not exhaust Engineer A's ethical obligations. Withdrawal removes Engineer A from complicity in an unsafe design but does not eliminate the foreseeable risk to future residents and the general public, who remain exposed to storm surge danger regardless of which engineer ultimately executes the project. In a jurisdiction with no building code, there is no regulatory mechanism that will independently capture or correct the identified deficiency after Engineer A's departure. Accordingly, Engineer A's post-withdrawal obligations extend to notifying appropriate local government officials or public authorities of the identified storm surge risk and the absence of any regulatory standard adequate to address it. This obligation is grounded in the public welfare paramount principle and is reinforced by the building code advocacy engineer principle, which encourages engineers to engage with public authorities to establish protective standards. Engineer A's duty to the public does not terminate at the boundary of the client relationship, and the residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal from the project.
AnalyticalIn response to Q101: Engineer A bears an affirmative obligation to notify local government officials or other relevant public authorities about the identified storm surge risk even after withdrawing from the project. The absence of a building code in the jurisdiction does not eliminate the foreseeable danger to future residents; it amplifies it. Code provision II.1.a makes clear that when an engineer's judgment is overruled under circumstances that endanger life or property, the engineer shall notify the proper authority. Withdrawal alone satisfies the negative duty not to participate in an unsafe design, but it does not discharge the positive duty to protect public welfare. Because no regulatory floor exists in this jurisdiction, Engineer A's notification to local government officials is the only remaining mechanism by which the identified risk can be surfaced to a body capable of acting on it. Silence after withdrawal, in a no-code jurisdiction where the developer may simply retain a less scrupulous engineer, leaves the public safety risk entirely unaddressed and is ethically insufficient.

Is Engineer A obligated to document in writing the 100-year storm surge recommendation and Client A's refusal, and if so, to whom must that documentation be provided and retained?

AnalyticalBeyond the Board's recommendation that Engineer A continue to pursue discussions with Client A, Engineer A bears an affirmative obligation to document in writing the 100-year storm surge recommendation, the technical basis for that recommendation including the newly released algorithm and historic weather data, and Client A's explicit refusal on cost grounds. This written record serves two distinct functions: first, it fulfills Engineer A's faithful agent duty by formally notifying Client A that the project as currently scoped carries foreseeable risk to future residents and the general public; and second, it creates a contemporaneous professional record that may be essential if Engineer A is later called upon to demonstrate that the safety-critical recommendation was made and rejected. The absence of a local building code in the jurisdiction makes this documentation obligation more urgent, not less, because there is no regulatory paper trail that would otherwise capture the identified deficiency. Engineer A should provide this written notification to Client A before withdrawing from the project, and should retain copies as part of the professional record.
AnalyticalIn response to Q102: Engineer A is obligated to document in writing the 100-year storm surge recommendation and Client A's explicit refusal. This obligation flows from multiple converging sources. First, code provision II.1.a requires that when an engineer's judgment is overruled under circumstances endangering life or property, the engineer shall notify the proper authority - a notification that is only credible and actionable if supported by a written record. Second, code provision III.1.b requires Engineer A to advise the client when a project will not be successful, and written documentation of that advice protects the integrity of that communication. Third, the Written Documentation Requirement for Safety Notification principle establishes that oral advocacy alone is insufficient when safety-critical recommendations are rejected. The documentation must be retained by Engineer A as a professional record, provided to Client A as formal notice of the safety concern and its rejection, and made available to any public authority to whom Engineer A subsequently discloses the risk. It should not be treated merely as a liability shield for Engineer A's professional standing; its primary ethical function is to create a durable, verifiable record of the safety risk that can inform regulatory or legal action.

To what extent does the absence of a local building code expand Engineer A's independent professional duty to self-impose a safety standard, and does that duty persist regardless of client cost objections?

AnalyticalThe absence of a local building code in the project jurisdiction does not merely create a regulatory gap - it affirmatively expands Engineer A's independent professional duty to self-impose a technically defensible safety standard. Where a building code exists, an engineer's minimum obligation is compliance with that code, even if the engineer believes a higher standard is warranted. Where no code exists, the engineer's professional judgment is the only operative safety standard, and that judgment must be exercised with full application of available technical knowledge, including newly released algorithms and historic weather data. Client A's cost objection cannot function as a substitute for the absent regulatory floor. The Board's framework implicitly recognizes this dynamic by treating Engineer A's 100-year storm surge recommendation not as a discretionary preference but as a professional obligation grounded in public safety. This obligation persists regardless of cost constraints and is not diminished by the fact that a lower standard might have been acceptable in a jurisdiction with a more permissive building code.
AnalyticalIn response to Q103: The absence of a local building code materially expands Engineer A's independent professional duty to self-impose a safety standard. Where a regulatory floor exists, an engineer can at minimum point to codified requirements as a baseline, even if personally recommending a higher standard. In a no-code jurisdiction, the engineer's professional judgment is the only operative safety standard in the design process. This places the full weight of public safety determination on Engineer A's expertise, making the self-imposed standard not merely aspirational but ethically mandatory. Client A's cost objections do not diminish this duty; the Public Welfare Paramount principle and the constraint that public safety is not subordinate to client cost preference together establish that economic considerations cannot override a safety-critical technical determination. Furthermore, this duty persists regardless of cost objections because the harm at stake - storm surge danger to future residents and the general public - is foreseeable, serious, and irreversible in the event of a major storm event. The no-code context therefore heightens rather than relaxes Engineer A's obligation to hold the 100-year storm surge standard as a non-negotiable professional floor.

Does Engineer A bear any residual ethical responsibility for harm to future residents if Engineer A withdraws from the project but takes no further action to alert public authorities or advocate for protective building codes in the jurisdiction?

AnalyticalIn response to Q104: Engineer A does bear residual ethical responsibility for harm to future residents if Engineer A withdraws from the project but takes no further action to alert public authorities or advocate for protective building codes. Withdrawal is a necessary but not sufficient ethical response once Client A refuses the safety-critical recommendation. The Board's conclusion that Engineer A should withdraw if Client A refuses is correct as far as it goes, but it does not exhaust Engineer A's obligations. Code provision II.1.a explicitly contemplates post-overruling notification to proper authorities, and the Building Code Advocacy Engineer Principle and Post-Client-Refusal Escalation Assessment Obligation together establish that Engineer A's professional duty extends beyond the client relationship into the broader public sphere. In a no-code jurisdiction, where no regulatory body will independently discover the risk, Engineer A's silence after withdrawal is functionally equivalent to acquiescence in the unsafe outcome. The residual responsibility is not unlimited - Engineer A cannot compel the developer or the jurisdiction to act - but it does require Engineer A to take affirmative steps to surface the risk to those with authority to address it.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the Faithful Agent Notification Obligation - which requires Engineer A to serve Client A's interests and notify the client of project risks - conflict with the Public Welfare Paramount principle when serving the client's cost preference would expose future residents to foreseeable storm surge danger?

AnalyticalIn response to Q201: The Faithful Agent Notification Obligation and the Public Welfare Paramount principle do not fundamentally conflict in this case - they operate in sequence rather than in opposition, but Public Welfare Paramount takes lexical priority when they diverge. Engineer A's duty as a faithful agent requires notifying Client A of the storm surge risk and the likelihood that a lower design standard will expose the project and its future residents to foreseeable danger. This notification duty is fully compatible with public welfare protection so long as Client A accepts the recommendation. The conflict arises only when Client A refuses: at that point, continuing to serve the client's cost preference would require Engineer A to subordinate public safety to client interest, which the NSPE Code does not permit. Code provision II.1. establishes that public safety is paramount, and the Client Loyalty Obligation of Engineer A is explicitly bounded by public safety. The faithful agent role therefore terminates at the boundary of ethical permissibility - Engineer A cannot be a faithful agent to a client directive that endangers the public.
AnalyticalThe tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a clear lexical ordering: Engineer A's duty to serve Client A's interests is bounded by, and ultimately subordinate to, the obligation to hold public safety paramount. The Board's conclusions confirm that Engineer A must first attempt persuasion - satisfying the faithful agent duty by fully informing Client A of the risk and its consequences - but when Client A's cost-driven refusal persists, the public welfare obligation overrides client loyalty and compels withdrawal. This resolution teaches that client service is not an independent ethical value in engineering; it is a conditional obligation that operates only within the space permitted by public safety. The moment client direction would require Engineer A to acquiesce to a design standard that exposes future residents to foreseeable storm surge danger, the faithful agent role collapses into the public welfare role, and the latter governs. Notably, the absence of a local building code does not relax this hierarchy - it intensifies it, because Engineer A's independent professional judgment becomes the only operative safety standard in the jurisdiction.

Does the Climate Change as Moving Target principle - which acknowledges inherent uncertainty in projecting future storm surge baselines - conflict with the Professional Competence in Risk Assessment principle, which demands that Engineer A render a definitive and defensible safety recommendation rather than hedging on the basis of evolving data?

AnalyticalIn response to Q202: The Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle are in genuine tension, but that tension does not license indefinite hedging. Engineer A is correct to acknowledge that climate projections carry inherent uncertainty and that the baseline for storm surge risk may shift over time. However, professional competence requires that Engineer A render a definitive and defensible recommendation based on the best available data at the time of the assessment - in this case, the newly released algorithm and historic weather data. Epistemic humility does not mean refusing to commit to a standard; it means selecting the most protective standard that the current evidence supports and disclosing the uncertainty range transparently. The 100-year storm surge elevation standard represents Engineer A's best professional judgment given available tools, and that judgment must be stated clearly enough to be actionable. Qualifying the recommendation to the point of ambiguity would undermine its protective function and would itself constitute a failure of professional competence. Engineer A should state the recommendation definitively while noting that the standard may need to be revisited as climate data evolves.
AnalyticalThe interaction between the Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle reveals an important synthesis: epistemic uncertainty about future climate baselines does not diminish Engineer A's obligation to render a definitive and defensible safety recommendation - it actually strengthens the case for adopting the more protective standard. When the technical baseline is inherently uncertain and evolving, a competent professional does not hedge toward the lower bound of risk; rather, professional competence in a no-code jurisdiction requires Engineer A to apply the best available tools - here, the newly released algorithm and historic weather data - and recommend the standard that accounts for the upper plausible range of foreseeable harm. The availability of superior technical tools creates a heightened professional duty, because Engineer A can no longer claim ignorance of the more protective standard. At the same time, the moving-target nature of climate data requires Engineer A to qualify the recommendation transparently - not to weaken it, but to explain its basis and acknowledge that future data may require design revision. This synthesis teaches that professional competence and epistemic humility are not in conflict: a competent engineer discloses uncertainty while still committing to the most defensible protective standard available at the time of the assessment. The Building Code Advocacy Engineer Principle further extends this synthesis: because the climate baseline will continue to evolve, Engineer A's obligation to advocate for a local building code incorporating the 100-year standard is not merely a post-withdrawal courtesy but a forward-looking professional responsibility to ensure that the jurisdiction's regulatory framework keeps pace with improving climate science.

Does the Proportional Escalation Obligation - which calls for graduated steps before withdrawal - conflict with the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle, which may demand immediate refusal to proceed once Client A explicitly rejects the safety-critical 100-year storm surge standard?

AnalyticalThe Board's recommendation that Engineer A pursue persistent discussions with Client A before withdrawing does not require Engineer A to engage in indefinite or open-ended negotiation. The proportional escalation obligation is bounded by the point at which continued engagement becomes functional acquiescence to a design standard that Engineer A has already determined endangers life and property. Once Client A has explicitly and unambiguously refused the 100-year storm surge elevation standard on cost grounds, and once Engineer A has made a good-faith written effort to explain the public safety consequences of that refusal, the escalation obligation is satisfied. Continued discussion beyond that point risks creating the appearance that the safety standard is negotiable, which would itself undermine Engineer A's professional integrity and the clarity of the public safety message. The Board's two-step framework - persuade, then withdraw - should therefore be understood as a sequential and time-bounded process, not a license for indefinite deferral of withdrawal.
AnalyticalIn response to Q203: The Proportional Escalation Obligation and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle are in tension, but the resolution depends on the nature and clarity of Client A's refusal. Proportional escalation - attempting to persuade, documenting the disagreement, and escalating through available channels before withdrawing - is the appropriate framework when a client's position is ambiguous, negotiable, or based on incomplete information. However, when Client A has made an explicit, cost-driven refusal of a safety-critical standard, continued engagement that delays withdrawal risks becoming a form of tacit acquiescence. The Board's recommendation that Engineer A continue to pursue discussions is appropriate only if those discussions are genuinely aimed at changing Client A's position, not at finding a compromise that falls below the safety threshold. If Client A's refusal is unequivocal and no further persuasion is plausible, the Non-Acquiescence principle demands that Engineer A not continue to participate in a design process that will produce an unsafe outcome. The escalation obligation does not require Engineer A to exhaust every conceivable avenue before withdrawing; it requires that withdrawal be preceded by a good-faith effort to resolve the disagreement through professional persuasion.
AnalyticalThe tension between the Proportional Escalation Obligation - which calls for graduated steps before withdrawal - and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle was resolved in this case by treating them as sequentially compatible rather than genuinely conflicting. The Board's recommendation that Engineer A continue to pursue discussions before withdrawing reflects the proportional escalation logic: withdrawal is the terminal step in a graduated response, not the first. However, this sequential compatibility has a critical limit. Once Client A has explicitly and finally refused the 100-year storm surge standard on cost grounds, continued discussion that merely delays withdrawal without any realistic prospect of changing the client's position would itself become ethically problematic - it would allow Engineer A to remain nominally engaged with a project whose safety standard Engineer A has already determined to be inadequate. The non-acquiescence principle therefore functions as a ceiling on how long proportional escalation may continue: Engineer A may pursue persuasion, but may not use the escalation framework as a pretext for indefinite engagement with a project that endangers the public. This case teaches that proportional escalation is a procedural obligation, not a substantive one - it governs the sequence of Engineer A's response but does not alter the ultimate outcome once client refusal is confirmed.

Does the Building Code Advocacy Engineer Principle - which encourages Engineer A to engage local government to establish protective standards - conflict with the Regulatory Gap Awareness and Proactive Risk Disclosure principle in terms of timing and scope, specifically whether Engineer A's disclosure duty to public authorities is triggered before or only after withdrawal from the project?

AnalyticalIn response to Q204: The Building Code Advocacy Engineer Principle and the Regulatory Gap Awareness and Proactive Risk Disclosure principle are not fundamentally in conflict regarding timing, but they operate on different tracks. Proactive risk disclosure to public authorities is triggered by the identification of a foreseeable public safety risk that cannot be adequately addressed through the client relationship - a trigger that may be reached before withdrawal if Client A's refusal is clear and the risk is serious. Building code advocacy, by contrast, is a longer-horizon obligation that involves engaging local government to establish systemic protective standards and is appropriately pursued both during and after the client engagement. The disclosure duty is narrower and more urgent: it requires Engineer A to surface the specific identified risk to authorities capable of acting on it. The advocacy duty is broader and more structural: it requires Engineer A to work toward closing the regulatory gap that allowed the risk to go unaddressed in the first place. These duties are complementary rather than conflicting, and both are activated by the combination of a no-code jurisdiction, a foreseeable public safety risk, and a client's refusal to adopt the recommended protective standard.
Theoretical (4)

From a deontological perspective, does Engineer A's duty to hold public safety paramount create an absolute obligation to withdraw from the project once Client A refuses the 100-year storm surge elevation standard, regardless of whether withdrawal actually prevents harm to future residents?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A's duty to hold public safety paramount does create a near-absolute obligation to withdraw once Client A explicitly refuses the 100-year storm surge elevation standard, but the deontological analysis does not end there. Withdrawal is obligatory because continuing to participate in the design of a structure that Engineer A knows to be unsafe would make Engineer A complicit in a foreseeable harm to future residents - a violation of the categorical duty not to use persons merely as means. However, the deontological framework also imposes a positive duty of beneficence toward those future residents, which withdrawal alone does not satisfy. The duty to withdraw is therefore necessary but not sufficient: it must be accompanied by the affirmative duty to notify proper authorities, as specified in code provision II.1.a. The fact that withdrawal may not actually prevent harm - because another engineer may replace Engineer A - does not diminish the deontological obligation to withdraw; acting from duty is not contingent on producing the desired outcome. But it does reinforce the importance of the notification duty as the mechanism through which Engineer A's moral agency extends beyond the client relationship.

From a consequentialist perspective, does Engineer A's withdrawal from the project after Client A's refusal actually produce better outcomes for future residents and the public than remaining engaged and attempting to influence the project design from within, given that another engineer with fewer safety scruples might simply replace Engineer A?

AnalyticalIn response to Q302: From a consequentialist perspective, the question of whether withdrawal produces better outcomes than remaining engaged is genuinely difficult, but the analysis ultimately supports withdrawal as the ethically superior choice under the specific conditions of this case. The argument for remaining engaged - that Engineer A might influence the design from within - is plausible only if Client A's refusal is soft and subject to ongoing persuasion. If Client A's refusal is firm, remaining engaged produces no safety benefit and instead lends Engineer A's professional credibility to an unsafe design. The replacement engineer scenario - where a less scrupulous engineer simply adopts the lower standard - is a real consequentialist concern, but it does not justify Engineer A's continued participation in an unsafe project. The better consequentialist response to the replacement risk is not to remain on the project but to pursue the post-withdrawal notification and advocacy obligations that can alert public authorities to the risk regardless of who ultimately designs the structure. Withdrawal combined with proactive disclosure to local government officials produces better expected outcomes than continued engagement without client agreement on the safety standard.
AnalyticalFrom a consequentialist perspective, the Board's recommendation that Engineer A withdraw if Client A refuses the 100-year storm surge standard requires supplementary analysis to avoid a potentially counterproductive outcome. If Engineer A withdraws and a replacement engineer with fewer safety commitments accepts the engagement and designs to a lower storm surge elevation, the net effect on future residents may be worse than if Engineer A had remained engaged and continued to advocate for the higher standard from within the project. This replacement engineer risk does not, however, override the deontological obligation to withdraw - Engineer A cannot ethically lend professional credentials to a design that Engineer A has determined endangers life and property. But it does reinforce the importance of the post-withdrawal obligations identified above: Engineer A's notification to public authorities and advocacy for a protective building code are not merely optional extensions of professional responsibility but are the consequentialist mechanism by which withdrawal produces better rather than worse outcomes for the public. Withdrawal without post-withdrawal public disclosure may protect Engineer A's professional integrity while leaving the underlying public safety risk entirely unaddressed.

From a virtue ethics perspective, does Engineer A demonstrate genuine professional integrity by relying on newly released climate data and a recently developed algorithm to recommend the 100-year storm surge standard, or does epistemic humility require Engineer A to qualify that recommendation more explicitly given the inherent uncertainty in climate projections?

AnalyticalThe Board's conclusions do not address the epistemic dimension of Engineer A's recommendation, specifically the tension between the professional obligation to render a definitive and defensible safety standard and the inherent uncertainty in climate projections derived from newly released algorithms and recently identified historic weather data. Engineer A's reliance on newly released tools is itself an expression of the professional competence obligation - engineers must apply the best available technical knowledge, not merely established consensus methods. However, professional integrity also requires that Engineer A qualify the recommendation appropriately: the 100-year storm surge standard should be presented as the technically defensible minimum given current best-available data, with explicit acknowledgment that evolving climate baselines may require future reassessment. This qualification does not weaken the recommendation or provide Client A with grounds to reject it on grounds of uncertainty; rather, it demonstrates the epistemic honesty that distinguishes a professionally credible safety recommendation from an overconfident assertion. The qualification also reinforces the case for building to the higher standard, since uncertainty in climate projections generally argues for greater rather than lesser conservatism in safety-critical infrastructure design.
AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A demonstrates genuine professional integrity by applying the newly released algorithm and historic weather data to recommend the 100-year storm surge standard, but epistemic humility requires that the recommendation be accompanied by a transparent disclosure of the uncertainty inherent in climate projections - not as a qualification that weakens the recommendation, but as a demonstration of intellectual honesty that strengthens it. A virtuous engineer does not suppress uncertainty to make a recommendation appear more authoritative than the evidence warrants; nor does the virtuous engineer use uncertainty as a reason to avoid making a definitive professional judgment. The virtue of practical wisdom - phronesis - requires Engineer A to calibrate the recommendation to the best available evidence, state it clearly and confidently, and acknowledge the evolving nature of the climate baseline in a way that informs rather than undermines the client's decision-making. Recommending the 100-year standard on the basis of the best current tools, while noting that the standard may need to be revisited as data improves, reflects the kind of honest, competent, and courageous professional conduct that virtue ethics demands.

From a deontological perspective, does Engineer A's duty as a faithful agent to Client A - which includes notifying the client when a project is unlikely to succeed - conflict with the duty to hold public safety paramount, and if so, which duty takes lexical priority when Client A's cost-driven refusal creates foreseeable risk to future residents?

AnalyticalIn response to Q304: From a deontological perspective, Engineer A's duty as a faithful agent to Client A and the duty to hold public safety paramount do conflict when Client A's cost-driven refusal creates foreseeable risk to future residents, and public safety takes unambiguous lexical priority. The faithful agent duty - including the obligation under code provision III.1.b to notify the client when a project will not be successful - is a genuine professional obligation, but it is explicitly bounded by the public safety paramount principle established in code provision II.1. The NSPE Code does not treat these duties as equally weighted and subject to balancing; it establishes a clear hierarchy in which public safety is paramount. This means that when the two duties conflict, Engineer A cannot satisfy the faithful agent obligation by continuing to serve Client A's cost preference at the expense of public safety. The faithful agent duty is fully discharged when Engineer A provides Client A with a clear, written notification of the safety risk and the consequences of refusing the recommended standard - after which the public safety duty takes over and requires Engineer A to withdraw and notify appropriate authorities.
Counterfactual (4)

If the geographic area had an existing building code that mandated only a lower storm surge elevation standard, would Engineer A still be obligated to recommend the 100-year projection, and would the ethical calculus for withdrawal change given that compliance with the code would provide a legal safe harbor even if Engineer A believed it was technically insufficient?

AnalyticalIn response to Q401: If the jurisdiction had an existing building code mandating a lower storm surge elevation standard, Engineer A would still be ethically obligated to recommend the 100-year projection if professional judgment - supported by the best available data - indicated that the code-mandated standard was technically insufficient to protect public safety. Code provision II.1.b requires engineers to approve only those engineering documents in conformity with applicable standards, but it does not limit Engineer A's professional duty to recommend a higher standard when the applicable code is inadequate. Legal compliance provides a legal safe harbor but not an ethical one: an engineer who knows that a code-compliant design will expose future residents to foreseeable danger cannot discharge the public safety obligation merely by pointing to the code. However, the ethical calculus for withdrawal would change in a coded jurisdiction: Engineer A could not refuse to certify a code-compliant design on safety grounds alone without a stronger evidentiary basis that the code itself was deficient, and the appropriate response might shift toward formal advocacy for code revision rather than project withdrawal. The no-code jurisdiction in the present case removes this complication and places the full weight of the safety determination on Engineer A's professional judgment.

Would the outcome for future residents have been materially different if Engineer A had proactively contacted local government officials to advocate for a building code incorporating the 100-year storm surge standard before presenting findings to Client A, rather than treating that advocacy as a post-withdrawal obligation?

AnalyticalIn response to Q402: Proactive contact with local government officials before presenting findings to Client A would likely have produced better outcomes for future residents than treating advocacy as a post-withdrawal obligation. If Engineer A had engaged local government at the outset - alerting officials to the identified storm surge risk and the absence of a protective building code - the jurisdiction might have initiated a code development process that would have established a regulatory floor independent of Client A's cost preferences. This would have changed the negotiating dynamic: Client A would have faced not only Engineer A's professional recommendation but also the prospect of an emerging regulatory requirement. However, this sequencing raises its own ethical complexity: Engineer A's primary engagement is with Client A, and disclosing project-specific findings to public authorities before informing the client could be seen as a breach of the faithful agent obligation. The more defensible approach is for Engineer A to raise the regulatory gap issue with local government in general terms - advocating for a building code that addresses storm surge risk in the jurisdiction - without disclosing Client A's project-specific information before the client relationship has broken down. Post-withdrawal, the disclosure obligation becomes more direct and project-specific.

If Engineer A had provided written documentation of the safety recommendation and Client A's refusal at the outset of the disagreement rather than only during ongoing discussions, would that written record have changed Client A's willingness to accept the 100-year storm surge standard, or would it have served primarily to protect Engineer A's professional standing while leaving the underlying public safety risk unresolved?

AnalyticalIn response to Q403: Written documentation of the safety recommendation and Client A's refusal, provided at the outset of the disagreement rather than only during ongoing discussions, would likely have served a dual function: it would have created a formal record that could influence Client A's decision-making by making the professional stakes of the refusal explicit, and it would have protected Engineer A's professional standing. However, the evidence suggests that Client A's refusal is cost-driven and firm, which means the written record's primary practical effect would be protective of Engineer A rather than persuasive to Client A. This does not diminish the obligation to document: the Written Documentation Requirement for Safety Notification principle establishes that documentation is required regardless of its persuasive effect, because its function extends beyond the client relationship to the broader public safety record. The written record is the instrument through which Engineer A's professional judgment becomes available to public authorities, future investigators, and regulatory bodies. Its value is not exhausted by its effect on Client A's decision, and the underlying public safety risk remains unresolved regardless of whether Client A is persuaded - which is precisely why the post-withdrawal notification obligation to public authorities is independently required.

If the newly released algorithm and historic weather data had not been available and Engineer A had relied only on previously established climate models, would the ethical obligation to recommend the 100-year storm surge standard have been weaker, and does the availability of superior technical tools create a heightened professional duty that did not previously exist?

AnalyticalIn response to Q404: The availability of the newly released algorithm and historic weather data does create a heightened professional duty that did not previously exist to the same degree, and the ethical obligation to recommend the 100-year storm surge standard is correspondingly stronger than it would have been under previously established climate models alone. Professional competence requires engineers to apply the best available tools and data to their assessments; when superior technical tools become available, the standard of care rises accordingly. If Engineer A had relied only on older climate models that did not support the 100-year projection, the obligation to recommend that specific standard would have been weaker - though the obligation to recommend the most protective standard supported by available evidence would have remained. The newly released algorithm does not create the ethical obligation from scratch; it provides the technical basis for a more specific and more demanding recommendation. This also means that Engineer A's obligation to stay current with technical literature and newly released tools is itself an ethical obligation, not merely a professional development aspiration: failing to apply available superior tools when assessing a safety-critical design would itself constitute a failure of professional competence under the circumstances of this case.
Decisions & Arguments (8)
View Extraction

After Client A explicitly refuses to fund construction to the 100-year storm surge elevation, what sequence of professional actions must Engineer A take to satisfy the public welfare paramount obligation while respecting the proportional escalation framework?

Options considered:
O1 Continue pursuing substantive discussions with Client A to explain the foreseeable danger to future residents, provide written documentation of the 100-year recommendation and Client A's refusal, and withdraw from the project if Client A's refusal remains explicit and firm after good-faith persuasion efforts are exhausted Board's choice
O2 Withdraw from the project immediately upon Client A's first explicit refusal of the 100-year standard, without further persuasion attempts, on the grounds that any continued engagement after an unambiguous cost-driven rejection of a safety-critical standard constitutes tacit acquiescence
O3 Remain engaged on the project while continuing to advocate internally for the 100-year standard, on the grounds that Engineer A's continued presence preserves residual influence over design decisions and that a replacement engineer with fewer safety commitments would produce worse outcomes for future residents
Argument structure:
Warrants

The Public Welfare Paramount principle establishes that Engineer A's primary duty is to the safety of future residents over client cost preferences. The Proportional Escalation Obligation requires good-faith persuasion and written documentation before withdrawal: withdrawal is the terminal step, not the first. The Non-Acquiescence to Client Directive Suppressing Safety Analysis principle prohibits Engineer A from remaining engaged once Client A's refusal is explicit and firm, because continued participation constitutes tacit acquiescence. The Faithful Agent Notification Obligation requires Engineer A to formally advise Client A in writing that the project as scoped will not protect future residents, satisfying the faithful agent duty before the public welfare duty takes over. The Written Documentation Obligation requires a contemporaneous professional record of the recommendation, its technical basis, and Client A's refusal.

Rebuttals

The proportional escalation warrant is rebutted when Client A's refusal is so categorical and the safety risk so severe that further persuasion attempts only delay harm prevention. The written documentation obligation loses ethical sufficiency if the record serves only to insulate Engineer A from liability while leaving future residents exposed. The absence of a building code removes the regulatory trigger that would normally mandate escalation, and the preliminary nature of the newly released algorithm may qualify the certainty of the risk finding.

Grounds

Engineer A has applied newly released climate data and a recently developed storm surge modeling algorithm to determine that the 100-year storm surge elevation is necessary to protect future residents of a coastal residential development. No building code exists in the jurisdiction. Client A has refused to fund construction to that elevation on cost grounds. The public safety risk to future residents persists regardless of Client A's refusal.

Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation Engineer A Client Budget Limitation Storm Surge Design Constraint

After withdrawing from the project, does Engineer A bear an affirmative obligation to notify local government officials or public authorities of the identified storm surge risk and advocate for adoption of a protective building code, or does withdrawal alone discharge Engineer A's professional duty to the public?

Options considered:
O1 After withdrawing from the project, notify appropriate local government officials or public authorities of the identified storm surge risk and the absence of any regulatory standard adequate to address it, and separately advocate to those officials for adoption of a building code incorporating the 100-year storm surge elevation standard Board's choice
O2 After withdrawing from the project, treat withdrawal as fully discharging Engineer A's professional obligation, on the grounds that Engineer A's duty runs to the client relationship and that post-withdrawal notification to public authorities exceeds the scope of the engagement and risks breaching client confidentiality regarding project-specific findings
O3 After withdrawing from the project, advocate to local government officials for storm surge building codes in general terms applicable to the broader geographic region, without disclosing Client A's project-specific information, on the grounds that general code advocacy satisfies the public welfare obligation while preserving the boundary between the client engagement and the public sphere
Argument structure:
Warrants

The Public Welfare Paramount principle establishes that Engineer A's duty to the public does not terminate at the boundary of the client relationship, foreseeable residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal. Code provision II.1.a requires that when an engineer's judgment is overruled under circumstances endangering life or property, the engineer shall notify the proper authority, withdrawal satisfies the negative duty not to participate in an unsafe design but does not discharge this positive notification duty. The Building Code Advocacy Engineer Principle encourages engineers to engage with public authorities to establish protective standards, and the absence of any building code makes this advocacy obligation more urgent post-withdrawal. The Proportional Escalation Obligation and the Post-Client-Refusal Escalation Assessment Obligation together establish that Engineer A's professional duty extends beyond the client relationship into the broader public sphere. The replacement engineer risk reinforces the non-optional character of post-withdrawal public disclosure as the consequentialist mechanism by which withdrawal produces better rather than worse outcomes for future residents.

Rebuttals

The post-withdrawal notification obligation is rebutted if Engineer A's risk finding is insufficiently certain to constitute a definitive public danger warranting governmental notification, the newly released algorithm may not yet have achieved broad peer validation. The obligation is further rebutted if another competent engineer is already engaged to assess the risk independently, or if the proportionality of the escalation response is not justified by the severity and probability of the identified harm. Early government contact before withdrawal may also be constrained by the faithful agent obligation, which limits pre-withdrawal disclosure of project-specific client information.

Grounds

Engineer A has withdrawn from the coastal residential development project after Client A refused the 100-year storm surge elevation standard on cost grounds. No building code exists in the jurisdiction. Future residents remain exposed to foreseeable storm surge danger regardless of Engineer A's withdrawal. No regulatory mechanism will independently capture or correct the identified deficiency after Engineer A's departure. The developer may retain a replacement engineer with fewer safety commitments who will design to a lower storm surge elevation.

Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint

Should Engineer A present the 100-year storm surge elevation as a non-negotiable design standard, qualify it as preliminary pending broader peer validation of the new algorithm, or anchor the recommendation to previously validated models?

Options considered:
O1 Apply the newly released algorithm and historic weather data to establish the 100-year storm surge elevation as the professionally required design standard, and present it to Client A as a non-negotiable floor that cannot be reduced without compromising public safety. In a no-code jurisdiction, Engineer A's judgment is the sole operative safety standard, making this commitment ethically mandatory. Board's choice
O2 Present the 100-year storm surge elevation as a strongly recommended standard supported by newly released data, while explicitly qualifying it as a preliminary finding pending broader peer validation of the algorithm. This approach acknowledges the rebuttal that the new modeling tool has not yet achieved the professional acceptance required to anchor a non-negotiable safety floor.
O3 Use the newly released algorithm to inform the risk assessment but base the formal design recommendation on the most protective standard supported by previously established and peer-validated climate models. This preserves a defensible standard of care while avoiding reliance on an algorithm whose professional acceptance is still uncertain.
Argument structure:
Warrants

The Public Welfare Paramount principle establishes that in a no-code jurisdiction, the engineer's professional judgment becomes the sole operative safety standard, making the self-imposed standard not merely aspirational but ethically mandatory. The Professional Competence in Risk Assessment principle requires Engineer A to apply the best available technical knowledge, including newly released algorithms and historic weather data, and the standard of care rises when superior tools become available. The Climate-Informed Infrastructure Design Standard principle holds that Engineer A's reliance on newly released data and a recently developed algorithm is itself an expression of the professional competence obligation. The Client Direction Does Not Authorize Ethical Violation principle establishes that Client A's cost objections cannot substitute for the absent regulatory floor. The Climate Change as Moving Target principle requires Engineer A to treat storm surge projections as dynamic inputs rather than fixed historical baselines, and epistemic uncertainty about future climate baselines argues for greater conservatism in safety-critical design, not lesser.

Rebuttals

The self-imposition warrant is rebutted if the newly released climate algorithm has not yet achieved broad peer validation or is not yet professionally accepted as the governing standard of care. The heightened duty claim is rebutted by the condition that the public welfare paramount obligation exists regardless of the precision of available instruments, meaning the duty to recommend the most protective standard is not newly created by the algorithm but is merely more specifically quantified by it. The cost differential between the 100-year standard and the lower elevation may be so disproportionate as to raise questions about whether the recommendation is practically actionable, though this does not eliminate the obligation to make it.

Grounds

Engineer A applied newly released climate data and a recently developed storm surge modeling algorithm, incorporating newly identified historic weather data, to determine that the 100-year storm surge elevation standard is necessary to protect future residents of the coastal residential development. No building code exists in the jurisdiction, meaning Engineer A's professional judgment is the only operative safety standard in the design process. Client A refused to fund construction to that elevation on cost grounds. The harm at stake, storm surge danger to future residents, is foreseeable, serious, and irreversible in the event of a major storm event.

Engineer A Faithful Agent Written Risk Notification Storm Surge Obligation Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint

When a newly released climate algorithm supports a 100-year storm surge standard that Client A refuses on cost grounds, and no local building code exists to establish a regulatory floor, should Engineer A treat that standard as a non-negotiable professional floor and continue advocating it, or calibrate the recommendation to account for algorithmic uncertainty and client budget constraints?

Options considered:
O1 Maintain the 100-year storm surge standard as a non-negotiable professional floor, present it definitively to Client A with transparent acknowledgment of climate projection uncertainty, and continue advocating it through persistent good-faith discussion before any withdrawal decision Board's choice
O2 Present the 100-year standard as the preferred recommendation but offer a qualified alternative design scenario at a lower elevation with explicit written disclosure of the residual risk, allowing Client A to make an informed cost-risk tradeoff while Engineer A remains engaged
O3 Apply the newly released algorithm to establish the 100-year standard as the technically defensible recommendation, but qualify the recommendation explicitly as preliminary pending broader peer validation of the algorithm, and defer the advocacy posture until the algorithm achieves wider professional acceptance
Argument structure:
Warrants

The Professional Competence in Risk Assessment obligation requires Engineer A to apply the best available tools and render a definitive, defensible recommendation, the newly released algorithm raises the standard of care. The Public Welfare Paramount principle establishes that in a no-code jurisdiction, Engineer A's judgment is the only regulatory floor, making the 100-year standard ethically mandatory rather than aspirational. The Climate Change as Moving Target principle acknowledges inherent uncertainty in climate projections, which could justify qualifying or softening the recommendation. The Client Budget Limitation constraint recognizes that cost differentials may be disproportionate and that client direction carries some weight in design scoping.

Rebuttals

The self-imposed standard warrant is rebutted if the newly released algorithm has not yet achieved broad peer validation or if the cost differential is so disproportionate that a lower standard with appropriate disclosure is professionally defensible. The moving-target principle could be weaponized by Client A as a pretext to reject any protective standard, converting an honest epistemic qualification into a mechanism for suppressing safety analysis. The absence of a building code cuts both ways: it removes the regulatory trigger for mandatory escalation while simultaneously placing the full weight of public safety on Engineer A's independent judgment.

Grounds

A newly released algorithm and historic weather data support a 100-year storm surge elevation standard. No local building code exists in the jurisdiction, making Engineer A's professional judgment the sole operative safety standard. Client A refuses the recommended standard on cost grounds. Future residents face foreseeable storm surge danger if a lower standard is adopted.

Engineer A Climate Change Moving Target Design Consideration Storm Surge Obligation Engineer A Client Budget Limitation Storm Surge Design Constraint

Once Client A explicitly refuses the 100-year storm surge standard on cost grounds, should Engineer A continue pursuing discussions and provide formal written documentation of the recommendation and refusal before withdrawing, or does the categorical nature of Client A's refusal trigger an obligation to withdraw without further engagement that risks signaling the standard is negotiable?

Options considered:
O1 Continue pursuing good-faith discussions with Client A, provide formal written documentation of the 100-year recommendation and Client A's refusal before withdrawing, and treat that written notice as the mechanism that fully discharges the faithful agent duty and triggers the withdrawal obligation if refusal persists Board's choice
O2 Treat Client A's explicit cost-driven refusal as a categorical rejection that immediately triggers the non-acquiescence obligation, withdraw from the project without further discussion to avoid signaling that the safety standard is negotiable, and provide written documentation of the recommendation and refusal as part of the withdrawal communication
O3 Continue discussions with Client A while simultaneously preparing written documentation of the recommendation and refusal, but condition continued engagement on Client A's willingness to formally acknowledge receipt of the written safety notice, treating that acknowledgment as the threshold that determines whether further persuasion is professionally appropriate or constitutes tacit acquiescence
Argument structure:
Warrants

The Proportional Escalation Obligation requires Engineer A to pursue good-faith persuasion and written documentation before withdrawing: withdrawal is the terminal step, not the first response to client disagreement. The Faithful Agent Notification Obligation requires Engineer A to formally notify Client A in writing that the project as scoped carries foreseeable risk, satisfying the duty under code provision III.1.b to advise the client when a project will not be successful. The Written Documentation Requirement for Safety Notification establishes that oral advocacy alone is insufficient when safety-critical recommendations are rejected, and the absence of a building code makes Engineer A's own documentation the only contemporaneous professional record. The Non-Acquiescence principle demands that once Client A's refusal is explicit and unambiguous, continued discussion risks creating the appearance that the safety standard is negotiable, which itself undermines professional integrity.

Rebuttals

The proportional escalation warrant is rebutted when the client's refusal is so categorical and the safety risk so severe and irreversible that further persuasion attempts would only delay harm prevention without any realistic prospect of changing the client's position. The written documentation obligation loses its ethical sufficiency if the record serves only to insulate Engineer A from liability while leaving future residents exposed to foreseeable storm surge harm without triggering any further protective action.

Grounds

Client A has explicitly refused the 100-year storm surge standard on cost grounds. Public safety risk to future residents persists. No building code exists to provide an independent regulatory record of the identified deficiency. Engineer A has presented findings verbally but has not yet provided written documentation of the recommendation or Client A's refusal. The proportional escalation framework calls for graduated steps before withdrawal; the non-acquiescence principle demands that Engineer A not participate in a design process that will produce an unsafe outcome.

Engineer A Coastal Risk Assessment Persistent Client Persuasion Before Withdrawal

After withdrawing from the project because Client A refuses the 100-year storm surge standard, does Engineer A bear an affirmative obligation to notify local government officials of the identified risk and advocate for a protective building code, obligations that survive the termination of the client relationship, or does withdrawal discharge Engineer A's professional responsibilities, leaving further action to Engineer A's discretion?

Options considered:
O1 After withdrawing, proactively notify local government officials of the identified storm surge risk and the absence of a protective building code, provide the written technical record of the 100-year recommendation and Client A's refusal to support regulatory action, and engage in ongoing advocacy for a jurisdiction-wide building code incorporating the 100-year standard Board's choice
O2 After withdrawing, engage local government officials in general terms to advocate for storm surge building codes in the jurisdiction without disclosing Client A's project-specific information, treating the broader regulatory gap as the appropriate subject of public advocacy while preserving residual confidentiality obligations to the former client
O3 Treat withdrawal as discharging Engineer A's primary professional obligations, retain the written documentation of the recommendation and refusal as a professional record available if later called upon, but defer notification to public authorities unless Engineer A is directly contacted by a regulatory body or future investigator, on the grounds that the risk finding's preliminary algorithmic basis does not yet meet the threshold for mandatory governmental disclosure
Argument structure:
Warrants

The Public Welfare Paramount principle establishes that Engineer A's duty to the public does not terminate at the boundary of the client relationship, foreseeable residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal. The Building Code Advocacy Engineer Principle encourages engineers to engage with public authorities to establish protective standards, and the absence of any building code makes this advocacy obligation more urgent post-withdrawal. The Regulatory Gap Awareness and Proactive Risk Disclosure principle establishes that where no regulatory mechanism exists to independently capture the identified deficiency, Engineer A bears an affirmative duty to notify appropriate public authorities. From a consequentialist perspective, withdrawal without post-withdrawal public disclosure may protect Engineer A's professional integrity while leaving the underlying public safety risk entirely unaddressed, and the replacement engineer risk reinforces the non-optional character of post-withdrawal notification.

Rebuttals

The post-withdrawal notification obligation is rebutted if Engineer A's risk finding is preliminary or insufficiently certain to constitute a definitive public danger warranting governmental notification, or if another competent engineer or regulatory process will independently surface the risk. The residual responsibility is not unlimited, Engineer A cannot compel the developer or the jurisdiction to act, and the proportionality of post-withdrawal obligations may be limited by the degree of certainty in the risk finding and the availability of public authorities with jurisdiction or capacity to act on the information.

Grounds

Engineer A has withdrawn from the project after Client A's explicit refusal of the 100-year storm surge standard. No building code exists in the jurisdiction, meaning no regulatory mechanism will independently capture or correct the identified deficiency after Engineer A's departure. Future residents remain exposed to foreseeable storm surge danger. A replacement engineer with fewer safety commitments may accept the engagement and design to a lower standard. Code provision II.1.a requires that when an engineer's judgment is overruled under circumstances endangering life or property, the engineer shall notify the proper authority.

Engineer A Coastal Risk Assessment Post-Cost-Refusal Escalation Assessment

When Engineer A has identified a 100-year storm surge standard as the technically defensible safety floor using newly released tools, and Client A refuses on cost grounds in a jurisdiction with no building code, how should Engineer A respond to that refusal?

Options considered:
O1 Maintain the 100-year storm surge standard as a non-negotiable professional floor, present the recommendation in writing with explicit technical basis and transparent acknowledgment of climate projection uncertainty, and continue advocating that standard to Client A before taking any further escalation step Board's choice
O2 Present the 100-year standard as the preferred recommendation while offering Client A a formally documented alternative design at a lower storm surge elevation, with written disclosure that the alternative falls below Engineer A's professional safety judgment, allowing Client A to make an informed cost-risk decision
O3 Qualify the 100-year storm surge recommendation as preliminary pending broader peer validation of the newly released algorithm, and propose engaging an independent coastal engineering expert to co-validate the standard before treating it as the binding professional floor in negotiations with Client A
Argument structure:
Warrants

The Public Welfare Paramount principle (II.1) establishes that Engineer A's safety determination is not subordinate to client cost preference. The No-Code Jurisdiction Self-Imposed Safety Standard principle holds that in the absence of a regulatory floor, the engineer's professional judgment becomes ethically mandatory rather than aspirational. The Professional Competence in Risk Assessment obligation requires Engineer A to apply the best available tools, here the newly released algorithm, and the availability of superior tools heightens the duty to recommend the most protective defensible standard. The Non-Acquiescence to Client Directive Suppressing Safety Analysis principle prohibits Engineer A from accepting a lower standard once a safety-critical determination has been made. Competing against these is the Client Budget Limitation Constraint and the Climate Change as Moving Target principle, which acknowledge that cost differentials may be disproportionate and that the newly released algorithm may not yet have achieved broad peer validation, potentially qualifying the certainty of the recommendation.

Rebuttals

The self-imposition warrant is rebutted if the newly released climate algorithm has not yet achieved broad professional acceptance as the governing standard of care, which could reduce the certainty required to override client cost objections. The heightened duty argument is rebutted by the observation that the public welfare paramount obligation exists regardless of the precision of available instruments, meaning the duty to recommend the most protective standard does not depend solely on the availability of the new algorithm. The cost differential may be so disproportionate relative to the marginal safety gain that a reasonable professional could conclude a lower standard remains defensible.

Grounds

Engineer A has applied a newly released climate algorithm and historic weather data to determine that a 100-year storm surge elevation standard is the technically defensible minimum for the coastal project. No building code exists in the jurisdiction, making Engineer A's professional judgment the sole operative safety standard. Client A has explicitly refused the recommendation on cost grounds. Future residents and the general public remain exposed to foreseeable storm surge danger if a lower standard is adopted.

100-Year Storm Surge Design Standard Recommendation Obligation Client Budget Limitation Storm Surge Design Constraint

Should Engineer A apply the newly released climate algorithm and historic weather data to determine the 100-year storm surge standard as a definitive professional recommendation, qualify that recommendation to reflect epistemic uncertainty, or defer to previously established climate models pending broader peer validation of the new algorithm?

Options considered:
O1 Apply the newly released algorithm and historic weather data to determine the 100-year storm surge standard, present it as the definitive professionally defensible minimum, and explicitly acknowledge in the recommendation that the evolving climate baseline may require future design reassessment Board's choice
O2 Apply the newly released algorithm to inform the assessment but present the resulting 100-year projection as a preliminary finding subject to peer validation, recommending the client commission independent expert review of the algorithm before committing to the higher design standard
O3 Base the storm surge recommendation on previously established and peer-validated climate models, note the existence of the newly released algorithm as an emerging tool warranting monitoring, and defer full application until the algorithm achieves broader professional acceptance
Argument structure:
Warrants

The Professional Competence in Risk Assessment principle requires Engineer A to apply the best available technical knowledge, not merely established consensus methods: when superior tools become available, the standard of care rises accordingly. The Climate-Informed Infrastructure Design Standard requires Engineer A to incorporate current best-available climate data into safety-critical assessments. The Climate Change as Moving Target principle acknowledges that climate projections carry inherent uncertainty and that baselines may shift, which argues for greater conservatism rather than lesser. Epistemic humility requires transparent disclosure of uncertainty without weaponizing it to avoid a definitive commitment.

Rebuttals

The obligation to apply the newly released algorithm is rebutted if the tool has not yet achieved broad peer validation or if the climate data baseline is acknowledged to be a moving target in ways that make the 100-year projection premature. The unqualified recommendation warrant is rebutted if the algorithm's preliminary status means the recommendation should be presented as a best current estimate subject to revision rather than a settled professional standard. Relying on previously established models could be defended as the more conservative professional choice pending independent validation of the new tool.

Grounds

A newly released algorithm and recently identified historic weather data are available to Engineer A at the time of the coastal risk assessment. No building code exists in the jurisdiction. Application of the new algorithm yields a 100-year storm surge standard that is higher, and more costly, than what previously established climate models would have indicated. The algorithm has not yet achieved broad peer validation consensus.

Newly Released Climate Algorithm Application Competence Obligation Engineer A Climate Moving Target Design Baseline Constraint. Coastal Storm Surge
13 sequenced 7 actions 6 events
Case timeline
The residential development site is located in a jurisdiction with no existing building codes governing storm surge or coastal construction standards, creating a regulatory vacuum that places full burden of safety determination on the engineer.
A newly developed hydrodynamic modeling algorithm incorporating newly identified historic weather data becomes publicly available, providing more accurate coastal risk assessment capabilities than previously possible.
Engineer A voluntarily accepts retention by Client A to perform hydrodynamic modeling and coastal risk assessment for a residential development in a coastal area with no existing building codes.
At stake (1)
  • NSPE obligation to provide competent professional services within area of expertise
Fulfills (2)
  • Obligation to serve client interests by undertaking legitimate professional work
  • Obligation to contribute engineering expertise to projects with public safety implications
Engineer A deliberately employs a recently developed algorithm incorporating newly identified historic weather data and newly released information to conduct the coastal risk assessment, rather than relying solely on conventional or previously established methods.
At stake (2)
  • Obligation to be objective and truthful in professional assessments
  • Obligation to include all relevant and pertinent information in professional reports (per BER Case 07-6 precedent)
Fulfills (2)
  • NSPE obligation to perform services only in areas of competence using current technical knowledge
  • Duty to apply best available science to protect public health and safety
As a direct result of applying the new algorithm and historic weather data, Engineer A's analysis yields the finding that the development must be built to a 100-year projected storm surge elevation to meet public safety requirements, a standard higher than what the developer anticipated.
Based on technical analysis using newly released data and algorithm, Engineer A makes a professional judgment determination that the residential development must be built to a 100-year projected storm surge elevation standard due to unacceptable public safety risks at lower projections.
Fulfills (4)
  • NSPE paramount obligation to hold public health and safety above all other considerations
  • Obligation to exercise independent professional judgment based on technical competence
  • Obligation to be objective and truthful in professional assessments
  • NSPE Code Section III.2.d. obligations regarding environmental protection
Engineer A communicates the technical determination that the project must be built to the 100-year projected storm surge elevation standard to Client A, including the public safety rationale underlying that recommendation.
Fulfills (4)
  • NSPE obligation to be objective and truthful in professional reports and communications
  • Obligation to include all relevant and pertinent information in professional assessments (per BER Case 07-6)
  • Duty of faithful agency including honest communication of professional findings to client
  • Obligation to advise client of actions necessary to protect public safety
After receiving Engineer A's findings and recommendation for the 100-year storm surge elevation standard, Client A refuses to incorporate it into the project due to the increased construction costs it would impose.
After Client A refuses to agree to the 100-year storm surge standard, Engineer A is prescribed to continue pursuing discussions with Client A to persuade the developer of the danger posed to future residents and the general public, and the potential for significant property and environmental damage.
Fulfills (4)
  • NSPE obligation to hold public health and safety paramount
  • Duty to advise client of actions necessary to protect public safety before escalating to withdrawal
  • Obligation to act in good faith to resolve professional disagreements through communication before severing engagement
  • Responsibility to protect future residents and general public from foreseeable harm
As a consequence of Client A's refusal to adopt the 100-year surge standard, future residents of the development remain exposed to elevated storm surge risk that Engineer A's analysis has identified as a genuine public safety hazard.
If Client A continues to refuse the 100-year storm surge elevation standard after sustained advocacy, Engineer A is prescribed to withdraw from the project rather than continue providing services that would facilitate a development Engineer A believes poses unacceptable public safety risks.
Fulfills (4)
  • NSPE paramount obligation to hold public health and safety above client and employer interests
  • Obligation to refuse to approve or participate in plans that endanger public safety
  • Duty to avoid professional complicity in knowingly unsafe engineering decisions
  • Obligation to maintain professional integrity when client refuses to adopt necessary safety standards
Violates (1)
  • Contractual obligation to complete services for Client A (superseded by overriding public safety obligation)
Engineer A is prescribed to consider contacting local government officials to advocate for the implementation of appropriate and updated region-wide building codes for the geographical area where the residential development project is located, addressing the systemic regulatory vacuum that enabled the client-engineer conflict.
Fulfills (5)
  • NSPE obligation to hold public health and safety paramount, extended to systemic and policy dimensions
  • NSPE Code Section III.2.d. obligations regarding environmental protection at a regional scale
  • Obligation to protect third parties (future residents of the broader region) who are not party to the immediate client engagement
  • Professional responsibility to contribute engineering expertise to public policy for the benefit of society
  • Obligation analogous to BER Case 04-8 precedent of bringing matters to appropriate authorities when client fails to take necessary action
The Discussion section of the case references prior Board of Ethical Review decisions (Cases 04-8 and 07-6) involving environmental and public safety obligations, establishing that Engineer A's situation fits within a recognized pattern of professional ethical precedent.
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 licensed engineer in private practice specializing in hydrodynamic modeling and coastal risk assessment. You have been retained by Client A, a developer, to evaluate climate change and sea level rise risks for a residential development project in a coastal area that currently has no applicable building code. Using newly released climate data and a recently developed storm surge modeling algorithm incorporating newly identified historic weather data, you have determined that the project should be built to a 100-year projected storm surge elevation to protect future residents from public safety risks present even at lower surge projections. Client A has refused to fund construction to that standard, citing the increased cost. With no regulatory floor in place to enforce your recommendation, the decisions you make now regarding your professional obligations to your client and to the public will define how this situation is resolved.

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: Coastal Risk Assessment EngineerWetland Delineation Case (BER 04-8)Threatened Species Case (BER 07-6)Present Case Coastal Risk Assessment

Engineer A must produce written documentation of the safety recommendation and the client's refusal to protect the public record and future residents, yet the preliminary-judgment disclosure qualification constrains how definitively that documentation can be framed — particularly when climate projections carry inherent uncertainty. Documenting too cautiously may undermine the protective purpose of the record; documenting too assertively may overstate certainty beyond what the engineer's current analysis supports. The tension is between the duty to create a clear, actionable safety record and the epistemic constraint that limits the strength of claims that can responsibly be made in writing.

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation and Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Faithful Agent Written Risk Notification Storm Surge Obligation and Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Building Code Advocacy Storm Surge Obligation and Client Cost-Refusal Non-Acquiescence Storm Surge Safety Obligation

Attaches to role: Coastal Risk Assessment Engineer

Engineer A is obligated to apply the most current climate risk algorithms to the coastal storm surge assessment, reflecting the professional duty to use state-of-the-art methods. However, the competence currency constraint recognizes that newly released algorithms may not yet be fully validated, peer-reviewed, or within Engineer A's demonstrated expertise. Applying an algorithm the engineer is not yet fully competent in risks producing unreliable outputs that could either overstate or understate risk; declining to apply it risks using outdated baselines that underestimate climate-driven storm surge. Either path carries professional and public safety consequences.

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Climate Change Moving Target Design Consideration Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Non-Acquiescence Client Cost Refusal Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Newly Released Algorithm Application Competence Obligation and Engineer A Climate Change Moving Target Design Baseline Constraint — Coastal Storm Surge

Attaches to role: Coastal Risk Assessment Engineer

Tension between Engineer A Formal Client Project Failure Risk Notification Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint

Attaches to role: Coastal Risk Assessment Engineer

Tension between Newly Released Climate Algorithm Application Competence Obligation and Engineer A Climate Moving Target Design Baseline Constraint — Coastal Storm Surge

Attaches to role: Coastal Risk Assessment Engineer
Client A Roles in this case: DeveloperCost-Refusing Developer

Engineer A must produce written documentation of the safety recommendation and the client's refusal to protect the public record and future residents, yet the preliminary-judgment disclosure qualification constrains how definitively that documentation can be framed — particularly when climate projections carry inherent uncertainty. Documenting too cautiously may undermine the protective purpose of the record; documenting too assertively may overstate certainty beyond what the engineer's current analysis supports. The tension is between the duty to create a clear, actionable safety record and the epistemic constraint that limits the strength of claims that can responsibly be made in writing.

Attaches to role: Developer

Engineer A is obligated to apply the most current climate risk algorithms to the coastal storm surge assessment, reflecting the professional duty to use state-of-the-art methods. However, the competence currency constraint recognizes that newly released algorithms may not yet be fully validated, peer-reviewed, or within Engineer A's demonstrated expertise. Applying an algorithm the engineer is not yet fully competent in risks producing unreliable outputs that could either overstate or understate risk; declining to apply it risks using outdated baselines that underestimate climate-driven storm surge. Either path carries professional and public safety consequences.

Attaches to role: Developer

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

Engineer A must produce written documentation of the safety recommendation and the client's refusal to protect the public record and future residents, yet the preliminary-judgment disclosure qualification constrains how definitively that documentation can be framed — particularly when climate projections carry inherent uncertainty. Documenting too cautiously may undermine the protective purpose of the record; documenting too assertively may overstate certainty beyond what the engineer's current analysis supports. The tension is between the duty to create a clear, actionable safety record and the epistemic constraint that limits the strength of claims that can responsibly be made in writing.

Engineer A is obligated to apply the most current climate risk algorithms to the coastal storm surge assessment, reflecting the professional duty to use state-of-the-art methods. However, the competence currency constraint recognizes that newly released algorithms may not yet be fully validated, peer-reviewed, or within Engineer A's demonstrated expertise. Applying an algorithm the engineer is not yet fully competent in risks producing unreliable outputs that could either overstate or understate risk; declining to apply it risks using outdated baselines that underestimate climate-driven storm surge. Either path carries professional and public safety consequences.


These tensions did not map cleanly to a single character.

Tension between Building Code Advocacy and Post-Cost-Refusal Escalation Assessment Obligation and Project Withdrawal as Ethical Recourse

Tension between 100-Year Storm Surge Design Standard Recommendation Obligation and Client Budget Limitation Storm Surge Design Constraint

Tension between Post-Cost-Refusal Escalation Assessment and Written Documentation Safety Recommendation Obligation and Client Loyalty Obligation Bounded by Public Safety

Opening States (10)
No Building Code Jurisdiction State Client-Rejected Engineer Safety Elevation Recommendation State Engineer A Private Practice Client Relationship No Building Code in Project Jurisdiction Climate-Informed 100-Year Storm Surge Elevation Recommendation Moving Target Climate Baseline - Coastal Storm Surge Client Refusal of 100-Year Storm Surge Elevation Recommendation Public Safety at Risk - Coastal Residential Development Storm Surge Regulatory Standard Climate Gap - No Code Jurisdiction Confirmed Risk Without Adequate Safeguards - Storm Surge Elevation
Summary
  • Engineers retain an independent safety obligation to the public that supersedes client budget constraints, even in jurisdictions lacking formal building codes.
  • When a client refuses to fund adequate safety measures, the engineer must escalate through persistent advocacy and written risk notification rather than simply deferring to the client's financial decision.
  • The absence of a legally mandated code standard does not eliminate the engineer's professional duty to apply self-imposed safety standards commensurate with known hazards like storm surge.