Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (5)
View Extraction-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 ExtractionExplicit 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.
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.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (1 board)
View ExtractionWhat are Engineer A’s obligations under the circumstances?
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?
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?
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?
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?
Cross-cutting analytical questions (12)
These questions consider the case as a whole rather than a specific board question above.
Show 12 cross-cutting questionsPrinciple 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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
Decisions & Arguments (8)
View ExtractionAfter 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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
Event Timeline (13)
Case timeline
- NSPE obligation to provide competent professional services within area of expertise
- Obligation to serve client interests by undertaking legitimate professional work
- Obligation to contribute engineering expertise to projects with public safety implications
- 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)
- 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
- 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
- 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
- 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
- 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
- Contractual obligation to complete services for Client A (superseded by overriding public safety obligation)
- 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
Narrative (2 main characters)
View ExtractionOpening 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 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.
Tension between Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation and Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint
Tension between Engineer A Faithful Agent Written Risk Notification Storm Surge Obligation and Engineer A No-Code Jurisdiction Self-Imposed Safety Standard Constraint
Tension between Engineer A Building Code Advocacy Storm Surge Obligation and Client Cost-Refusal Non-Acquiescence Storm Surge Safety Obligation
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.
Tension between Engineer A Post-Cost-Refusal Escalation Assessment Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint
Tension between Engineer A Climate Change Moving Target Design Consideration Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint
Tension between Engineer A Non-Acquiescence Client Cost Refusal Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint
Tension between Engineer A Newly Released Algorithm Application Competence Obligation and Engineer A Climate Change Moving Target Design Baseline Constraint — Coastal Storm Surge
Tension between Engineer A Formal Client Project Failure Risk Notification Storm Surge Obligation and Engineer A Client Budget Limitation Storm Surge Design Constraint
Tension between Newly Released Climate Algorithm Application Competence Obligation and Engineer A Climate Moving Target Design Baseline Constraint — Coastal Storm Surge
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.
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.
Show 3 other tensions
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)
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.