Step 4: Review

Engineers shall hold paramount the safety, health, and welfare of the public.

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.

Engineers shall approve only those engineering documents that are in conformity with applicable standards.

Engineers shall advise their clients or employers when they believe a project will not be successful.

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.

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

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

Engineer A should continue to pursue discussions with Client A to convince Client A of the danger in which future residents, as well as the general public, could be placed, and the potential for significant property and environmental damage. If Client A refuses to agree with Engineer A’s design standard, Engineer A should withdraw from the project.

The Board's recommendation to withdraw addresses Engineer A's direct relationship with Client A, but does not resolve whether Engineer A retains a residual duty to protect future residents and the public after withdrawal. Because the project area lacks a building code, withdrawal alone may not prevent Client A from retaining another engineer willing to design to a lower standard, leaving the underlying public safety risk unaddressed. Engineer A's obligation under Code II.1 to hold paramount public safety arguably extends to considering whether notification to local government officials of the identified storm surge risk is warranted, even though the Code does not mandate breaching client confidentiality absent an imminent danger comparable to that in BER Case 04-8 or BER Case 07-6.

The Board's conclusion presumes that Engineer A's 100-year storm surge determination is a well-founded professional judgment, but it does not explicitly examine the threshold of confidence required in newly developed algorithms and newly released historic weather data before such a determination can justify withdrawal from a paying engagement. Because the standard is not yet codified into any building code or regulatory requirement, Engineer A's technical competence and the reliability of the underlying data become central to whether the withdrawal obligation is ethically compelled or merely a precautionary best practice. This raises a nuance the Board did not address: the degree of scientific certainty needed to elevate a risk assessment to the level of a paramount safety obligation under Code II.1.

Beyond advising withdrawal, the Board's reasoning implies but does not state that Engineer A has an independent professional interest in advocating for the adoption of a storm surge building standard by the local government, separate from the outcome of the Client A engagement. Given the absence of any code in the area, Engineer A's specialized knowledge positions the engineer uniquely to promote broader regulatory reform that would protect not just Client A's future residents but all future development in the region, aligning with the spirit of sustainable development encouraged under Code III.2.d.

Because the project area currently has no building code addressing storm surge, Engineer A's obligation under II.1 to hold public safety paramount arguably extends beyond the immediate client relationship. Even if Client A ultimately agrees to a lower standard or Engineer A withdraws, Engineer A has a strong ethical basis for independently advocating that local government adopt a storm surge design standard, since the absence of any code leaves future residents and the public without baseline protection that would otherwise be presumed to exist.

If Engineer A withdraws after failing to persuade Client A, II.1.a's requirement to notify appropriate authorities when judgment is overruled under circumstances endangering life or property suggests an ongoing duty. Withdrawal alone may not fully discharge Engineer A's public welfare obligation; Engineer A should consider notifying local government officials of the identified storm surge risk so that future permitting decisions or a successor engineer are informed, even though the Board's stated conclusion focuses only on persuasion and withdrawal.

Engineer A need not have absolute certainty in the newly developed algorithm and historic weather data to treat the 100-year storm surge projection as a professional determination rather than mere precaution. Consistent with reasonable engineering judgment standards, Engineer A must have a good-faith, technically defensible basis grounded in the best currently available data and methodology; the newness of the algorithm does not, by itself, undermine the legitimacy of the determination so long as Engineer A applied sound professional judgment in validating it.

The potential for significant property and environmental damage does create obligations extending beyond the client relationship. Under principles reflected in III.2.d and analogous prior Board reasoning (as in BER Case 04-8 and BER Case 07-6 concerning disclosure to public authorities), Engineer A's duty to protect the environment and public may require informing relevant regulatory or environmental authorities if withdrawal alone leaves the risk unaddressed, particularly given the absence of a governing building code.

From a deontological standpoint grounded in II.1, Engineer A fulfilled the paramount duty to public safety by insisting on the 100-year storm surge standard and being willing to withdraw rather than compromise. The duty is satisfied not merely by achieving an outcome but by Engineer A's rule-based refusal to approve or proceed with a design believed to endanger public safety, regardless of the financial cost to Engineer A or the client relationship.

From a consequentialist perspective, Engineer A's willingness to forgo project revenue by withdrawing is justified because the likely harm averted—risk to future residents' safety and significant property and environmental damage—substantially outweighs the private financial loss to Engineer A, satisfying a public-interest cost-benefit rationale for withdrawal even without certainty that withdrawal will change the ultimate outcome of the project.

Engineer A acted with professional integrity by first engaging in continued, good-faith persuasion under III.1.b before resorting to withdrawal. This sequencing reflects the Code's preference for advising clients and attempting resolution prior to more drastic action, demonstrating that withdrawal was treated as a last resort rather than an immediate response to disagreement.

Had a local building code existed mandating a lower storm surge standard, the Board would likely have faced a harder question, since II.1.b directs engineers to approve only documents conforming to applicable standards. However, given II.1's paramount safety duty and precedent treating code minimums as floors rather than ceilings for professional judgment, the Board would likely still have concluded that Engineer A should withdraw if convinced the code minimum was unsafe, though the analysis would need to address potential conflict between code compliance and independent professional judgment.

If Engineer A's recommendation had rested on speculative concern rather than newly released historic weather data and a validated algorithm, the Board would likely not have found the public safety determination professionally justified, and the withdrawal obligation would be considerably weaker. The Board's implicit reliance on the technical grounding of the 100-year projection is central to legitimizing both the persuasion effort and the recommended withdrawal; without such grounding, Engineer A's position would resemble an unsupported preference rather than a defensible safety determination.

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

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

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

What are Engineer A’s obligations under the circumstances?

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

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

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

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

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

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

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

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

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

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

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

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

Because Engineer A's persistence in persuading the client stems directly from the client's refusal to accept the safety-based standard, this action is guided by paramountcy of public health and safety and environmental protection, and its failure to change the client's position is what ultimately forces the more consequential step of withdrawing from the project.

Client A's decision to retain the engineer's services sets in motion the technical evaluation that follows, so even though this action carries no explicit normative fulfillment or violation, it is causally significant as the trigger for the professional safety determination that anchors the entire case.

The client's refusal of the recommended standard directly follows from the engineer's professional safety determination and directly causes both the engineer's continued persuasion efforts and separate building code advocacy, making it a pivotal but normatively neutral pivot point that escalates the ethical stakes without itself fulfilling or violating a duty.

By fulfilling the obligation to exercise professional judgment based on technical competence and being guided by paramountcy of safety and environmental protection, this determination is the critical causal link that transforms new data and client retention into a concrete safety standard whose rejection by the client sets off the ensuing chain of persuasion and withdrawal.

As the culmination of the client's repeated refusal and the engineer's failed persuasion, withdrawing from the project fulfills the obligation to protect public health and safety and is guided by the paramountcy of that safety, demonstrating that when persuasion fails, removing oneself from the engagement is the necessary final safeguard against compromised professional standards.

Because Engineer A's Building Code Advocacy arose directly from the Client's refusal to adopt the safer standard, pursuing code-level advocacy instead of silently dropping the issue fulfills the paramount obligation to protect public health and safety and reflects the environmental protection principle, ensuring that the safety concerns raised by the new data are addressed through a systemic channel even after the client relationship could not resolve them.

The question arises because new hydrodynamic data revealed a coastal safety risk that the client refuses to fund addressing, creating a direct conflict between the engineer's duty to the client and the paramount duty to protect public health and safety, with no binding code to resolve the ambiguity.

The question emerges because the regulatory vacuum forces a choice between treating public safety as satisfied through client-level withdrawal versus treating it as requiring proactive systemic advocacy, and the NSPE Code's paramountcy clause does not specify how far that duty extends beyond a single client relationship.

The question arises because withdrawal removes Engineer A from the project but does not resolve whether the public safety warrant that justified withdrawal also generates an ongoing post engagement duty to warn, especially when no code or successor is guaranteed to catch the identified storm surge risk.

The question arises because Engineer A's Coastal Risk Assessment and Hydrodynamic Modeling capabilities rely on new, unproven tools, forcing a judgment call about how much epistemic confidence is required before technical findings can ethically be elevated from cautionary advice to binding professional conclusions.

The absence of a local building code combined with the engineer's own storm surge findings and the client's refusal creates ambiguity about whether the engineer's public welfare obligation extends beyond the client to external authorities.

The question arises because the absence of a mandatory code standard leaves the storm surge design threshold to professional judgment, so a client's cost based refusal directly pits contractual obedience against the engineer's independent safety obligation.

The question arises because Engineer A's Storm Surge Finding rests on data and methods that are technically sound but institutionally unrecognized, creating a gap between what professional judgment supports and what regulatory legitimacy currently sanctions.

The question emerges because Engineer A's technical finding of increased storm surge risk collides with the owner's cost driven refusal in a jurisdiction lacking a mandatory code, forcing a choice between environmental and public welfare protection and continued client engagement.

The question emerges because Engineer A's professional judgment (Engineer A Storm Surge Finding) collided with Client A's cost-driven refusal (Owner Cost Based Refusal), leaving ambiguous whether verbal insistence, without escalation to withdrawal or public disclosure, is sufficient to satisfy the deontological duty to hold public safety paramount.

The question arises because Engineer A's technical finding of significant storm surge risk conflicts with the client's cost-based refusal, forcing a judgment about whether forgoing revenue is ethically required or merely one of several defensible responses to protect the public.

The question arises because the case record shows Engineer A took time attempting persuasion before withdrawing, raising uncertainty about whether that sequence reflects genuine integrity or an unjustified delay in fulfilling the paramount duty to public safety.

The question arises because introducing a codified but lower safety standard forces a choice between two legitimate warrants, one rooted in legal/regulatory compliance and one rooted in independent professional judgment about paramount public safety, and it is unclear which should control when they conflict.

This question emerged because the case ties the legitimacy of Engineer A's safety determination and withdrawal obligation to the presence of new objective data, prompting inquiry into whether the same conclusion would hold without that evidentiary support.

Given that Client A refused a design standard Engineer A believed necessary for public safety, and no code existed to resolve the dispute, the board concluded Engineer A must first press Client A to reconsider and, failing that, withdraw rather than complete a design Engineer A views as unsafe.

Because withdrawal only severs Engineer A's direct relationship with Client A and does nothing to prevent a successor from building to a lower standard in an area lacking any code, the board recognized an unresolved tension between confidentiality and II.1's paramountcy duty, but declined to require notification absent facts showing imminent danger.

Because Engineer A's finding rested on new, uncodified data and modeling, the board's conclusion assumed but did not test the reliability of that determination, leaving open how much scientific certainty is needed before such a finding rises to a paramount safety obligation.

Because the area has no storm surge code and Engineer A's expertise is directly relevant, the board's reasoning suggests, without stating outright, that Engineer A has a professional interest in pursuing broader regulatory advocacy beyond the outcome of the Client A engagement.

Given the absence of any applicable code and the risk to future residents regardless of how the Client A engagement resolves, the board concluded Engineer A has a strong ethical basis to independently advocate for local government adoption of a storm surge standard.

Given that Engineer A withdrew only after failing to persuade Client A and that no code or successor mechanism guarantees the risk will be addressed, the board concluded that II.1.a's overruled-judgment notification duty implies an ongoing obligation to inform authorities even after withdrawal, though the Board's formal conclusion text stopped short of stating this as a firm requirement.

Because the algorithm and historic weather data were the best currently available tools and Engineer A applied sound professional judgment in validating them, the board concluded that novelty alone does not undermine the legitimacy of treating the 100-year projection as a firm professional determination rather than mere precaution.

Given the foreseeable significant property and environmental damage and the absence of any governing code, and drawing on the reasoning in BER Cases 04-8 and 07-6, the board concluded that Engineer A's duty under III.2.d may require informing regulatory or environmental authorities beyond simply withdrawing from the client engagement.

Because Engineer A insisted on the 100-year standard and was prepared to withdraw rather than yield, the board concluded that the paramount public safety duty under II.1 was fulfilled through this rule-based refusal, independent of whether the project outcome ultimately changed.

Given that the potential harm to future residents and the environment was substantial while the cost to Engineer A was merely financial, the board concluded from a consequentialist standpoint that willingness to forgo revenue by withdrawing was justified even without certainty that withdrawal would alter the project's course.

Given that Engineer A persisted in advising Client A before withdrawing, the Board treated this sequencing as evidence of professional integrity, since the Code favors resolution attempts over immediate exit from a paying engagement.

Facing a hypothetical lower code standard, the Board reasoned that because II.1's safety paramountcy is not displaced by mere regulatory compliance, Engineer A would likely still be obligated to withdraw if convinced the code minimum was unsafe, though the reasoning would need to address the code compliance versus judgment tension.

Because Engineer A's recommendation relied on newly released historic weather data and a validated algorithm, the Board treated the safety determination as professionally justified, implying that without such grounding the position would be an unsupported preference rather than a defensible finding.

Given the standoff between Client A's cost-based refusal and Engineer A's safety determination, the Board concluded that client loyalty cannot counterbalance public welfare, since under II.1 loyalty is discharged only through good-faith advocacy and must give way entirely once that advocacy fails.

Because no local building code existed to anchor the storm surge standard, the Board reasoned that Engineer A's professional judgment, grounded in new data and an algorithm, was itself sufficient to establish a paramount safety duty, treating regulatory silence as heightening rather than excusing professional responsibility.

Given that the property and environmental damage exposure here flows directly from the same storm surge risk already triggering Engineer A's paramount public welfare obligation, and given that no specific environmental law or permit was shown to be violated, the board concluded that environmental protection functions as an intensifier of the safety duty rather than a separate obligation, distinguishing this case from precedents involving discrete legal violations or protected species requiring independent disclosure to authorities.

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

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

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

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

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

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