Step 4: Review

Hold paramount the safety, health, and welfare of the public.

Act for each employer or client as faithful agents or trustees.

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 undertake assignments only when qualified by education or experience in the specific technical fields involved.

Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.

Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter.

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 support the principle that engineers must include all relevant and pertinent information regarding potential public/environmental harm in reports submitted to public authorities, even when not strictly required by regulation.

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

Engineer A has an obligation to consider potential impacts on public health, safety, and welfare, regardless of whether that is required by applicable law, including changing weather patterns and climate.

If Engineer A is reasonably certain that the project will result in adverse impacts to public health, safety, and welfare, and if the Client B denies the requisite evaluation, Engineer A should include the concern regarding potential adverse public health, safety, and welfare impacts in an engineering report for consideration by regulatory agencies and the public.

The Board's conclusion that Engineer A must act on 'reasonable certainty' leaves unresolved how much confidence an informal, conference-derived judgment must provide before triggering a disclosure obligation. Since Engineer A's belief rests on hydraulic evaluation procedures presented at a conference rather than a completed specialized hydrologic study, there is an inherent tension between the competence requirement of undertaking only assignments within one's qualifications and the duty to act on a professional judgment that is admittedly preliminary. The Board's framework implies that engineers may be ethically obligated to disclose concerns even when their own judgment falls short of the rigor normally required for the underlying technical work, provided the judgment is honestly and reasonably held.

The Board's second conclusion directs disclosure through an engineering report to regulatory agencies and the public, but does not address whether Engineer A has a further obligation to directly notify the twenty upstream homeowners whose property and safety are most immediately at stake. Public disclosure via a report filed with regulators may not reach the affected homeowners in a timely or comprehensible way, particularly if the report is technical, filed only upon regulatory request, or buried within a larger permitting record. A more robust reading of the paramountcy of public welfare could require Engineer A, or urge Client B, to ensure the affected homeowners receive direct or accessible notice of the risk, rather than relying solely on the passive mechanism of a regulatory filing.

The Board's first conclusion establishes that Engineer A's ethical duty to consider climate-driven impacts exists independent of current legal requirements, but this creates an asymmetry between the engineer's forward-looking professional judgment and the client's reliance on existing, unamended design codes. Because Client B's directive to withhold the costly analysis unless requested by regulators is itself lawful under current standards, the case illustrates that compliance with applicable law is a necessary but insufficient condition for satisfying the engineer's ethical obligations. This suggests that the Board views the paramountcy of public welfare as imposing an evolving, forward-looking duty that outpaces static regulatory frameworks, placing engineers in the position of anticipating standards not yet codified.

Regarding Q101, the threshold for triggering an ethical obligation to disclose is not the completion of a full specialized hydrologic and hydraulic study, but rather Engineer A's good-faith professional judgment—informed by generally accepted evaluation procedures, even if learned through a conference presentation rather than personal original research—that adverse impacts are reasonably likely to occur. The obligation to raise the issue with the client and propose further study arises at the point of reasonable technical suspicion; the obligation to formally document the concern in a report for regulators arises once Engineer A is 'reasonably certain' of adverse impact, a higher but still professional (not scientific-certainty) standard.

Regarding Q102, the Code's disclosure mechanisms (public reports, statements to regulatory bodies) are designed to channel technical concerns through institutional review rather than direct engineer-to-affected-party communication. Engineer A's ethical obligation is satisfied by ensuring the concern reaches the regulatory agencies and enters the public record (e.g., through hearing testimony or a report), which indirectly informs the upstream homeowners via the public process; a freestanding duty to individually contact the twenty homeowners is not established by the Code, though it would not be prohibited and could be seen as a further expression of holding public welfare paramount.

Regarding Q103 and Q104, Engineer A's competence to flag a concern (grounded in generally accepted, conference-disseminated hydraulic evaluation methods) is distinguishable from competence to issue definitive quantified findings, which would require the specialized subconsultant analysis Engineer A originally proposed. Client B's refusal to fund that analysis does not constitute an 'overruling of engineering judgment endangering life or property' under II.1.a, because no immediate danger exists and the harm is prospective and uncertain in degree; however, it does trigger the separate duty under III.1.b to advise the client of concerns about the project, and refusal to heed that advice shifts the ethical burden toward documentation for regulators.

From a deontological standpoint (Q301), Engineer A's duty to hold public safety paramount (I.1) is not conditioned on the existence of an applicable legal or code requirement; it is a free-standing professional duty. Engineer A fulfilled this duty by forming a considered judgment about future harm, proposing the appropriate specialized analysis, and being willing to document the concern for regulators notwithstanding the absence of any legal mandate to consider climate-driven conditions—thus satisfying the deontological requirement even though the underlying uncertainty was not fully resolved.

From a consequentialist perspective (Q302), Client B's directive to forgo the costly analysis in order to save project cost, while leaving open the possibility of decade-earlier uninhabitability for twenty upstream homes, produces an ethically troubling asymmetry: a bounded, quantifiable private cost is weighed against a diffuse, deferred, but potentially serious harm to an identifiable group of homeowners. Regardless of whether the harm ultimately materializes, the decision to accept this asymmetric risk without disclosure fails a utilitarian calculus that would require at least informing those who bear the downside risk or the regulators who could compel further study.

Regarding Q303, Engineer A acted with professional integrity by proposing the complex analysis despite its cost and by contemplating documentation of the concern despite anticipated difficulty at public hearings; integrity in this context is measured not by whether the concern is ultimately resolved with certainty, but by Engineer A's willingness to surface an uncomfortable technical judgment even when it complicates the client relationship and project approval process.

Regarding Q401, if Engineer A lacked reasonably certain judgment that the project would cause adverse impacts—for example, if the conference-based procedures suggested only speculative or negligible risk—the Board's documentation obligation would likely not apply, since Conclusion 2 is explicitly conditioned on Engineer A being 'reasonably certain' of adverse impact. In that counterfactual, Engineer A's ethical duty would instead be limited to continuing to monitor emerging standards and perhaps recommending (without insisting upon) the specialized analysis, without the heightened obligation to formally document a report-level concern.

Regarding Q402, if local development regulations already required evaluation of sea level rise and climate-driven precipitation changes, Engineer A's obligation to consider these impacts would be grounded in ordinary legal/code compliance (II.2.a-type competence and design compliance duties) rather than in the Board's 'beyond the law' reasoning. The ethical analysis would then shift from whether Engineer A must act absent legal requirement to whether Engineer A adequately fulfilled an existing legal duty—though the underlying obligation to disclose to regulators if the client resists a required analysis would likely remain, now reinforced by explicit code language rather than derived solely from I.1.

Regarding Q403, had Client B approved the costly hydrologic and hydraulic analysis, the Board's conclusion regarding an engineering report would still apply if the completed analysis confirmed adverse impacts to the upstream homes; the obligation to disclose to regulators and the public flows from the existence of reasonably certain adverse findings, not from whether the client resisted the analysis. The character of the report would differ, however—shifting from a precautionary disclosure of an unresolved concern to a documented, quantified finding—but the underlying duty under I.1 and III.1.b to ensure the information reaches decision-makers would persist.

The Board resolves the tension between Loyalty to Client B and Public Welfare Paramount Beyond Law not by requiring Engineer A to override the client's directive outright, but by establishing a graduated response: the engineer must first attempt to secure client agreement to the specialized analysis, and only if that is refused and the engineer remains reasonably certain of harm does the obligation shift to documenting the concern in an engineering report for regulators and the public. This shows that client loyalty is subordinate to public welfare, but is honored procedurally through sequential escalation rather than immediate breach of the client relationship or project withdrawal.

By explicitly stating that Engineer A's obligation to consider health, safety, and welfare impacts applies 'regardless of whether required by applicable law,' the Board subordinates Design Compliance Duty and reliance on current codes to Climate Change Standards Responsiveness. This establishes that formal regulatory or code compliance is a floor, not a ceiling, for ethical practice, and that engineers must exercise independent professional judgment about emerging risks like climate change even where standards lag behind scientific understanding.

The case reveals an unresolved tension between Sufficient Understanding for Specialized Evaluation and the duty to disclose potential impacts: Engineer A's judgment rests on informally presented conference procedures rather than a completed rigorous hydrologic study, yet the Board treats this level of confidence as sufficient to trigger disclosure obligations. This suggests that in matters of public safety, the threshold for acting on professional judgment is lower than the threshold for asserting scientific certainty—engineers need not have definitive proof of harm, only a reasonably informed and good-faith belief that harm may occur, in order to be ethically obligated to raise the concern.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Development Project Initiation carries no direct normative weight itself, but as the originating cause of Project Scope Acceptance it sets in motion the entire chain that eventually forces the engineer to confront a safety versus scope conflict, so its significance lies in triggering the downstream ethical tension rather than in any obligation it fulfills or violates.

Flood Risk Judgment being guided by the duty to hold paramount public safety matters because it is this safety-driven assessment, produced from the Conference Procedure Presentation, that causally compels Engineer A to propose the Specialized Analysis rather than silently accept outdated data, making the paramountcy principle the engine of the whole protective response.

Client Directive Issuance itself fulfills or violates nothing directly, but because it is caused by the Specialized Analysis Proposal and in turn forces Client Discussion Engagement, it functions as the pivotal point where the client's authority collides with the engineer's safety concerns, making its downstream effects normatively consequential even though the action is normatively neutral in isolation.

Project Scope Acceptance fulfilling the duty to perform services within scope matters because this contractual commitment, caused by Development Project Initiation, later constrains how far Engineer A can unilaterally act on safety concerns, creating the very tension that the paramountcy obligation in A2 and A5 must override.

Specialized Analysis Proposal being guided by the paramount safety obligation is significant because it translates Engineer A's flood risk judgment into a concrete protective recommendation that causes the Client Directive Issuance, showing the engineer attempting to fulfill the safety duty within the bounds of professional practice before the client's response creates further conflict.

By engaging Client B in discussion of the flood risk findings, Engineer A directly acts on the paramount duty to safeguard public welfare, translating the prior specialized analysis into a concrete attempt to influence the client's directive before it causes downstream harm, which sets up the subsequent need for documentation once the client resists.

Proposing to document the concern is a guided but not fully obligation-fulfilling step, since it preserves a record of Engineer A's professional judgment for accountability purposes, and its causal link to the client's refusal shows that even a paramount safety duty can be only partially discharged through documentation when the client resists corrective action.

Withdrawing from the project fulfills the paramount obligation to protect public health, safety, and welfare because it is the causal endpoint after documentation failed to change the client's stance, meaning Engineer A's exit is the necessary act to avoid complicity in a project whose flood risk was knowingly unaddressed.

The question arises because current design codes have not caught up with climate science, forcing the engineer to decide whether professional ethical obligations extend beyond legal minimums into predictive risk territory that is inherently uncertain.

The question arises because Engineer A Engagement By Client B combined with a Directive To Proceed Without Analysis leaves open whether minimal legal compliance is ethically sufficient when foreseeable climate-driven flood risk to Upstream Homes Flood Exposure is not directly required by outdated standards.

The question arises because Engineer A possesses emerging but unofficial technical knowledge about flood risk that sits in a gray zone between informal awareness and a completed formal analysis, so it is unclear how much certainty is required before silence becomes an ethical violation.

The question arises because Engineer A's risk assessment reveals a gap between what regulatory compliance requires and what public welfare paramountcy might demand, leaving unclear whether professional duty terminates at formal reporting or extends to direct communication with those bearing the risk.

The question arises because Engineer A must judge long-term flood risk under evolving climate standards without having performed the specialized analysis normally required, creating ambiguity about whether informal or conference-level knowledge meets the threshold of competence demanded by the engineering code.

The question arises because Client B's directive suppresses a risk analysis that Engineer A believes is professionally warranted, but the absence of immediate danger and the ambiguity of evolving climate standards make it unclear whether this constitutes the kind of overruling that triggers mandatory regulatory notification.

The question arises because Engineer A possesses professional judgment suggesting future harm to Upstream Homeowners Affected Public, yet is contractually and financially bound by Client B's explicit refusal to fund further analysis, creating a direct clash between fidelity to the client relationship and the profession's paramount duty to public safety that existing regulatory compliance does not resolve.

The question arises because Engineer A is bound to codes that lag behind recognized climate trends, creating a gap between legal compliance and substantive risk to Upstream Homes Flood Exposure that no single warrant resolves cleanly.

The question arises because Engineer A's understanding of the upstream flood risk rests on an informal, conference-based judgment rather than a completed subconsultant analysis, creating uncertainty about whether that understanding is sufficient to satisfy the threshold needed to trigger disclosure obligations to Client B and regulators.

The question arises because Client B's directive to proceed without a flood analysis leaves Engineer A holding safety relevant information whose disclosure could serve the public but damage the client relationship, creating a direct clash between two legitimate professional obligations.

This question emerged because Engineer A accepted a project scope defined by outdated design standards even while aware of unquantified upstream flood risk from climate change, creating a gap between legal compliance and the deontological ideal of paramount public welfare.

The question arises because the engineer's compliance with a client's cost-saving directive and adherence to outdated but legally sufficient design standards collided with an evolving professional expectation to consider climate change impacts on public safety, leaving the ethical status of the outcome contested rather than settled.

The question arises because Engineer A's proactive proposal of analysis and consideration of documenting concerns exceeded the letter of regulatory compliance, creating tension between minimal legal duty and a broader professional obligation to public welfare under uncertain and evolving climate standards.

The question arises because the Board's conclusion presumes a specific epistemic state (reasonably certain judgment) as the trigger for the documentation obligation, and it is unclear whether the obligation would survive if that specific evidentiary basis were absent, exposing tension between a threshold-based warrant and an unconditional public-welfare warrant.

The question arises because the case relies on a gap between outdated design standards and evolving climate knowledge to justify an ethical duty beyond legal compliance, so hypothetically closing that gap forces scrutiny of whether the ethical warrant was ever independent of the legal one.

The question arises because the Board's original conclusion was contingent on unquantified risk resulting from a directive to skip analysis, so the hypothetical reversal of that directive forces examination of whether the disclosure obligation is tied to the existence of risk itself or merely to the act of foregoing analysis.

Given that climate change is producing shifting precipitation and storm patterns not yet reflected in the 25-year storm design standard, the board concluded that Engineer A's ethical duty to the public extends beyond what current law demands, because paramountcy of public welfare is not limited by the static scope of applicable codes.

Given that Client B directed Engineer A to forgo the costly hydrologic analysis despite Engineer A's reasoned belief in future flood risk, the board concluded that documenting the concern in an engineering report for regulators and the public becomes the appropriate course once private channels of client advice are exhausted.

Because Engineer A's flood-risk judgment rested on conference-presented hydraulic procedures rather than a completed specialized study, the board's reasoning implies that disclosure obligations can still attach to a preliminary but reasonably held professional judgment, leaving open exactly how much confidence is required.

Given that the board's second conclusion only requires an engineering report to regulators and the public, and given that twenty upstream homeowners bear the most direct risk, the board's silence on direct notification suggests an unresolved gap between passive regulatory disclosure and the paramountcy of public welfare owed to specifically identifiable victims.

Because Client B's instruction to withhold the costly analysis was legally permissible under existing, unamended design codes, the board concluded that compliance with current law cannot alone satisfy Engineer A's ethical obligations, positioning the engineer's forward-looking professional judgment as necessarily outpacing static regulatory frameworks.

Given that Engineer A's concern rested on generally accepted hydraulic procedures learned at a conference rather than a bespoke study, the board concluded that ethical disclosure obligations attach in stages, first to raise the issue with the client at the point of reasonable suspicion, then to formally document it once reasonably certain, because requiring full scientific proof before any obligation arises would undermine the profession's precautionary function.

Because the Code routes technical concerns through public reports and regulatory testimony rather than private communication, the board concluded that Engineer A satisfies the disclosure duty by ensuring the concern enters that institutional channel, even though directly informing the twenty homeowners is not itself required.

Given that the harm at issue was future and unquantified rather than imminent, the board concluded that Engineer A's conference-based competence suffices to raise the concern under III.1.b but not to make definitive findings, so Client B's refusal to fund further study shifts the burden toward eventual documentation rather than immediate notification of an overruled judgment.

Since no law required Engineer A to consider climate-driven flood risk, the board concluded that the deontological duty under I.1 was nonetheless fulfilled because Engineer A proactively formed a judgment, proposed further study, and remained willing to document concerns, actions that satisfy the free-standing duty even though the underlying scientific uncertainty was never resolved.

Because Client B's cost savings were weighed against an undisclosed, deferred but potentially serious harm to twenty upstream homeowners, the board concluded that the consequentialist calculus fails unless at least the regulators or the affected homeowners are informed, regardless of whether the harm ultimately materializes.

Given that Engineer A proposed the expensive analysis and continued to consider documenting the concern despite the anticipated backlash at public hearings, the board concluded this constituted professional integrity because integrity is measured by the willingness to raise the issue, not by achieving certainty of resolution.

Given that Conclusion 2's documentation duty is conditioned on reasonable certainty of adverse impact, the board reasoned that if the conference-based procedures had instead indicated only speculative or negligible risk, Engineer A's obligation would shrink to monitoring and informal recommendation rather than formal disclosure.

Given that the actual case involved outdated codes silent on climate-driven flood risk, the board reasoned counterfactually that had regulations already required such evaluation, Engineer A's duty would rest on ordinary design compliance and competence obligations rather than on the board's beyond-the-law rationale, while the disclosure duty itself would persist under explicit code language.

Given that the disclosure duty flows from reasonably certain findings of harm rather than from the client's refusal to fund analysis, the board concluded that even had Client B approved and paid for the study, a confirmed adverse finding would still require an engineering report, though now as a quantified conclusion rather than a precautionary concern.

Given that Client B directed against the costly analysis while Engineer A retained judgment of possible future harm, the board concluded that public welfare ultimately prevails over client loyalty, but only through a graduated escalation that first respects the client relationship before requiring disclosure.

Given that the applicable development regulations and codes had not been updated to reflect sea level rise and shifting historical rainfall datasets, the board concluded that Engineer A's obligation to protect public health, safety, and welfare could not be discharged merely by following outdated design requirements, so independent professional judgment about emerging climate risk was ethically required regardless of legal compliance.

Given that Engineer A's judgment rested only on conference-presented hydraulic procedures rather than a completed subconsultant hydrologic study, the board still concluded that this level of informed, good-faith concern was sufficient to trigger a disclosure obligation, reasoning that ethical duties to protect public safety demand a lower threshold of certainty than would be required to assert definitive scientific proof of harm.

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

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

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

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

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