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 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 shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.

Cited alongside Case 20-4 to establish the Board's recent emphasis on an engineer's primary responsibility to public health, safety and welfare, particularly regarding safe drinking water.

Cited alongside Case 22-5 to establish the Board's recent emphasis on an engineer's primary responsibility to public health, safety and welfare, particularly regarding safe drinking water.

Used as a foundational case establishing that an engineer's duty to the public is paramount, even when it conflicts with client instructions; the Board reviews its facts and conclusions as the starting point for the present analysis.

Quoted within the discussion of Case 76-4 to reinforce the foundational principle that professional engineers must devote their interests to public welfare as required by the Code.

Discussed as a classic disclosure case where an engineer failed to include known material facts (threat to a species) in a written report; later contrasted with Engineer L's situation because Engineer L's initial concern was not yet an established 'fact.'

Listed as an example of similar facts requiring disclosure (safety violations confided by the client), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Listed as an example of similar facts requiring disclosure (incomplete drawings and specifications), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Listed as an example of similar facts requiring disclosure (violation of federal and state laws and regulations), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Listed as an example of similar facts requiring disclosure (public safety risk of future surge level rise), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Listed as an example of similar facts requiring disclosure (effects of sea level rise and changes in precipitation from climate change), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Cited and discussed in detail as a direct parallel case where an engineer notified a client of a safety concern (need for an on-site representative) that the client resisted funding due to cost, and the engineer improperly continued work; the Board applies this precedent to conclude Engineer L cannot ethically continue without proper safeguards.

It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk. Later, Engineer L did comply with Code provisions that require engineers to notify their employers or clients if a project will not be successful.

It would not be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by Engineer L. Continuing to work on the project after concerns about runoff were quantified would in effect mean Engineer L was placing the clients’ financial interest above the engineer’s paramount obligation to the public health, safety, and welfare. This, the engineer cannot ethically do.

The Board's finding that Engineer L acted ethically in staying silent during suspension rests on a critical distinction between a speculative, unquantified concern and a verified fact. Under II.3.a and II.3.b, engineers are only obligated to disclose founded, evidence-based determinations, not preliminary hunches. Since Engineer L had not yet completed the risk assessment, the concern did not yet rise to the level of a 'fact' requiring disclosure under III.3.a. This suggests the Board's conclusion is contingent on the epistemic status of the risk at the time of suspension, not simply on the act of ceasing work itself.

Had Engineer L already quantified the increased runoff risk before Client X requested suspension, the ethical calculus would likely have shifted: the concern would then constitute a material fact under III.3.a and I.1, obligating disclosure regardless of the client's financial distress or the inconvenience of the timing. This indicates the Board's first conclusion is time- and knowledge-dependent, not a general license for engineers to withhold known risks during contract suspensions.

The Board's second conclusion establishes that Engineer L cannot ethically continue work absent adequate safeguards, but it does not resolve whether Engineer L's obligations end with withdrawal. Given the paramount public safety duty under I.1 and the precedent in BER Case 18-9 regarding disclosure of future risk to third parties, Engineer L may have a further obligation to notify relevant regulatory or environmental authorities if Client X proceeds without safeguards, since simple withdrawal may not adequately protect the community's drinking water source once the risk has been confirmed as fact.

The Board's reasoning treats the increased runoff risk as an emergent discovery tied to a historic rainfall event, but BER Case 21-2's treatment of climate-driven precipitation changes suggests that a reasonably prudent engineer with expertise in stormwater design might have been expected to anticipate evolving risk profiles at the preliminary design stage. This raises a nuance the Board did not explicitly address: whether Engineer L's original scope of work and risk assessment methodology were themselves adequate given foreseeable climate trends, independent of the specific rainfall event that ultimately triggered quantification.

Regarding Q101, the Board's own distinction between a 'concern' and a 'fact' (as reflected in cases like BER Case 89-7, BER Case 99-8, and BER Case 04-8) implies that Engineer L had no strict ethical duty to disclose the unquantified risk at the time of suspension. Code provisions II.3.a and II.3.b require engineers to be objective and to found opinions on known facts; since the risk had not yet been quantified or established, it remained speculative rather than a disclosable fact. However, this does not foreclose the possibility that prudent practice would have counseled at least a general mention of an emerging concern, even without full quantification, to keep the client informed as the paramount public welfare obligation in I.1 looms in the background.

Regarding Q103, BER Case 21-2's treatment of climate-driven changes in precipitation intensity and recurrence intervals suggests that a forward-looking engineer with expertise in stormwater control design should treat evolving climate risk as a foreseeable design parameter rather than an unforeseen contingency. This implies that Engineer L's original scope of work, which included ensuring no impact to the drinking water source, should have anticipated the possibility of increasing heavy rainfall frequency during preliminary design, making the later risk discovery less a novel event and more the materialization of an anticipatable design consideration.

Regarding Q104, the combination of Engineer L's explicit contractual duty to prevent watershed impact and the Code's paramount public welfare obligation under I.1 suggests that even during a suspension of paid work, Engineer L retained a residual duty of awareness regarding developments that could affect public safety, such as the historic heavy rainfall event. This does not require unpaid active design work, but it does support the reasonableness of Engineer L conducting new risk studies promptly upon resumption rather than treating the suspension as a complete ethical hiatus.

Regarding Q301, from a deontological perspective Engineer L's duty of faithful agency to Client X (I.4) was not violated by ceasing work without voicing the unquantified concern, because faithful agency duties do not require disclosure of speculative, unverified risks. The paramount duty to public health and safety under I.1 only becomes operative as a competing duty once the risk is sufficiently established as fact; prior to that point, no genuine deontological conflict existed between the two duties.

Regarding Q302, from a consequentialist standpoint, Engineer L's decision to disclose the quantified runoff risk to Client X, despite the likelihood of straining the client relationship or jeopardizing the project's continuation, produces a better aggregate outcome than silence would have, because the potential harm of contaminated drinking water to an entire community vastly outweighs the financial harm to a single private developer. The disclosure thus satisfies a consequentialist justification even though it imposes near-term costs on Client X.

Regarding Q303, Engineer L's refusal to continue the project without the identified protective measures reflects professional integrity consistent with II.1.a, which protects engineers who decline to have their judgment overridden under circumstances endangering public health or property. By refusing to acquiesce to Client X's insistence on proceeding without safeguards, Engineer L demonstrated fidelity to the profession's ethical core rather than mere compliance with client wishes.

Regarding Q401, had Engineer L already quantified the increased runoff risk before Client X requested suspension, the Board would likely have reached a different conclusion on ceasing work silently, since III.3.a prohibits omission of material facts and II.3.a requires truthful, objective communication. A quantified risk would constitute an established fact requiring disclosure regardless of the client's request to suspend work, unlike the unquantified concern that existed in the actual case.

Regarding Q403, even absent explicit local environmental standards requiring protective measures, the Board's second conclusion would likely remain unchanged, because Engineer L's obligation not to continue work while Client X refuses safeguards derives primarily from the paramount duty to public health, safety, and welfare under I.1, not merely from regulatory compliance requirements. The existence of local standards reinforces but is not the sole basis for the ethical obligation identified by the Board.

During the suspension period, the apparent tension between Transparency in Risk Disclosure and Loyalty to Client X was resolved not by subordinating one principle to the other, but by a prior gating principle: Fact-Based Opinion. Because Engineer L's concern was still qualitative and unquantified, it did not yet rise to the level of a 'fact' that Code provisions II.3.a and II.3.b require engineers to disclose. This meant Loyalty to Client X and the duty to avoid speculative or unfounded statements pointed in the same direction, dissolving what might otherwise look like a conflict between candor and client fidelity. The case shows that Transparency obligations are epistemically triggered, not automatically weighed against loyalty at all times.

Once the runoff risk moved from an unquantified concern to a confirmed, qualitatively-estimated finding, the same two principles—Public Welfare in Stormwater Design and Loyalty to Client X—that had been reconcilable earlier became genuinely and irreconcilably opposed. The Board resolved this later-stage tension by invoking the lexical priority the Code assigns to the paramount duty to public health, safety, and welfare (I.1.) over faithful agency to the client (I.4.). This demonstrates that principle prioritization in engineering ethics is not fixed in the abstract but activates hierarchically once risk crosses an evidentiary threshold: below that threshold, loyalty and restraint from speculation can coexist; above it, public welfare categorically overrides client financial interest, even to the point of requiring withdrawal from the project.

The case illustrates that Fact-Based Opinion functions as a temporal hinge between two otherwise competing regimes of obligation: a client-protective regime governing engineers' communications about unconfirmed risks, and a public-protective regime governing confirmed ones. Engineer L's conduct across the two phases of the case—remaining silent while the risk was speculative, then disclosing and ultimately refusing to continue once the risk was established—shows that the Code does not ask engineers to choose once and for all between client loyalty and public welfare, but to recalibrate that choice continuously as factual certainty about risk develops.

Was it ethical for Engineer L to cease work when requested by Client X, without voicing concern about increased risk?

Would it be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by Engineer L?

Did Engineer L have an ethical duty to at least flag the existence of an unquantified but plausible increased risk to Client X at the time of suspension, even without full quantification, given the paramount duty to public health and safety?

If Client X proceeds with construction without adopting the protective measures Engineer L identified, does Engineer L have any further ethical obligation beyond withdrawing from the project, such as notifying regulatory authorities or the affected community?

Should the original scope of work and preliminary design have anticipated evolving climate-driven stormwater risk (as reflected in BER Case 21-2) rather than treating the increased risk as an unforeseen development discovered only later?

Does Engineer L's acceptance of the contract with a stated duty to prevent watershed impact create a heightened, ongoing monitoring obligation that persists even during a suspension of paid work?

How should Loyalty to Client X be balanced against Public Welfare in Watershed Protection when Client X's financial constraints directly conflict with the protective measures needed to safeguard the community's drinking water source?

Does Transparency in Risk Disclosure conflict with Loyalty to Client X in the period before suspension, when Engineer L withheld mention of a still-unquantified risk rather than raising it despite the client's financial distress?

How does Fact-Based Opinion by Engineer L constrain Transparency of Risk to Client, given that engineers are expected to voice only founded, evidence-based concerns rather than speculative ones during the suspension period?

How should Public Welfare in Stormwater Design be weighed against Loyalty to Client X once the risk of runoff into the drinking water source has been quantified and Client X still declines to invest in safeguards?

From a deontological perspective, did Engineer L fulfill the duty of faithful agency to Client X by ceasing work without raising the unquantified risk, given the competing paramount duty to public health and safety?

From a consequentialist perspective, did the outcome of Engineer L's disclosure of the quantified runoff risk justify the potential harm to Client X's financial interests and the project's continuation?

Did Engineer L act with professional integrity in refusing to continue the project once Client X declined to invest in the identified protective measures?

If Engineer L had already quantified the increased runoff risk before Client X requested the work suspension, would the Board still have concluded that ceasing work without voicing concern was not unethical?

If the historic heavy rainfall event had not occurred, and stormwater accumulation had not increased, would Engineer L's risk concerns have ever been established as a confirmed fact requiring disclosure, and would the Board's second conclusion still apply?

If local environmental standards had not explicitly required protective measures to safeguard public water sources, would the Board still have concluded that Engineer L could not ethically continue working without those safeguards?

If Client X's financial setback had not occurred and work had never been suspended, would Engineer L's later notification of quantified risk still have satisfied the Code's requirement to advise on an unsuccessful project, or would earlier disclosure have been required?

Although the Work Suspension Request itself carries no direct fulfills or violates tags, it is the causal trigger for the Nondisclosure at Suspension, meaning its normative weight lies in setting up a context where Engineer L's later silence about risk becomes ethically consequential.

Risk Notification fulfills the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because it is the direct downstream act of the Risk Study having established the risk as fact, so the engineer discharges the duty to inform the client honestly and factually, even though this notification then precipitates the client's Safeguard Refusal.

Risk Study Conduct fulfills the Opinions Founded on Facts Obligation because it transforms the observed Stormwater Accumulation Increase into a factually grounded Risk Established as Fact, which is the necessary evidentiary basis for the engineer's subsequent duty to notify the client.

Safeguard Refusal carries no fulfills or violates tags for the client, but it is the pivotal causal link that forces Engineer L into the Refusal to Acquiesce, showing that the client's rejection of safety measures directly generates the engineer's obligation to stand firm on public safety.

Refusal to Acquiesce fulfills the Public Safety Paramountcy Obligation and Project Success Advisement Obligation because, in response to the client's Safeguard Refusal, Engineer L prioritizes public welfare over compliance with the client's wishes, completing the causal chain from risk discovery to a firm ethical stand.

By accepting the contract Engineer L fulfilled the Faithful Agent Obligation to Client X, but this same acceptance set in motion the causal chain toward Risk Concern Emergence, meaning the loyalty owed to the client from the outset was already in latent tension with the public safety risks that would later surface from stormwater accumulation.

Nondisclosure at Suspension fulfilled the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because at that point the risk had not yet been established through study, so withholding a still-unverified concern was consistent with client loyalty and factual restraint even though it delayed information that would later prove critical once Risk Established as Fact emerged from the Risk Study Conduct.

Work Resumption fulfilled the Faithful Agent Obligation by honoring the client's renewed instructions after Client Financial Recovery, but this resumption reactivated the underlying conditions of Stormwater Accumulation Increase, making the engineer's subsequent Risk Study Conduct and Risk Notification necessary once the natural rainfall event exposed the danger that loyalty alone could no longer justify concealing.

The question arises because the suspension request coincided with an unresolved, undisclosed safety concern, creating ambiguity over whether loyalty to the client's instruction or duty to public safety should have governed Engineer L's silence at that moment.

The question arises because a confirmed public risk and a client's financial refusal to mitigate it collide, forcing a choice between the paramount duty to public welfare and the duty of loyal service to the paying client.

The question arises because Engineer L possessed early, unquantified awareness of a risk to a drinking water source but chose not to disclose it during a suspension driven by the client's financial setback, creating tension between acting on partial knowledge for public welfare and respecting the client's need for confirmed, fact based communications.

The question emerged because Client X's refusal to adopt protective measures converts a private professional disagreement into a public safety issue, forcing a choice between the traditionally bounded faithful agent warrant and the paramount public welfare warrant that some BER cases extend beyond mere withdrawal.

The question arose because the gap between when the original design was completed and when the increased risk was later confirmed as fact creates ambiguity over whether the risk was truly unforeseeable or should have been reasonably anticipated under evolving professional and scientific understanding of climate change.

The question arises because Client X's financial setback paused paid work after Engineer L had already accepted a contract with an explicit watershed protection duty, leaving unclear whether that duty survives the suspension or is contractually dormant.

The question emerged because Client X's financial setback forced a suspension of protective stormwater work just as evidence of drinking water contamination risk solidified, forcing a direct clash between contractual loyalty and paramount public welfare obligations under the NSPE Code.

The question arises because Engineer L's silence during suspension sits at the boundary between an unconfirmed technical concern and a known threat to a drinking water source, so it is unclear whether paramount public welfare obligations or faithful agent obligations should have governed his conduct at that moment.

The question arises because Engineer L's professional obligation to only voice founded concerns collides with the public welfare imperative to disclose emerging risks, and the unquantified state of the runoff risk during suspension leaves it unclear which warrant should govern the engineer's communication with the client.

The question arises because moving from a confirmed technical fact (quantified runoff risk) to an ethical conclusion requires choosing between two legitimate but conflicting NSPE obligations, and the client's refusal to invest in safeguards removes the easy resolution of simply advising and complying.

The question arises because Engineer L's silent work suspension sits at the exact fault line between two NSPE-recognized duties, agency loyalty to the client and paramount responsibility to public safety, and the BER must determine which principle governs when the underlying risk was not yet fully confirmed.

The question arises because evaluating disclosure purely by its outcomes forces a comparison between averted public harm and inflicted client harm, and Toulmin's model exposes this as a genuine warrant conflict rather than a factual dispute since both outcomes were real and simultaneous.

The question arises because Engineer L's decision to stop work sits at the intersection of two legitimate but conflicting professional obligations, and the Board must determine which warrant properly governs given the confirmed risk finding.

The question arises because the Board's ethical judgment hinged on the timing and evidentiary status of the runoff risk, and altering that timing tests whether the same nondisclosure action would still fall under the faithful agent warrant or shift into the public safety disclosure warrant.

This question arises because the Board's second conclusion depends on treating the risk as an established fact rather than a mere professional concern, and the contingent, external nature of the rainfall event exposes the fragility of that fact/concern distinction underlying the ethical obligation.

The question arose because the Board's actual decision was grounded partly in a concrete environmental regulation, leaving ambiguous whether the ethical prohibition on continuing work stemmed from that specific legal requirement or from the broader, standard-independent duty to safeguard public water sources.

The question arises because the financial suspension created a natural break point that could be read either as an excuse for delayed disclosure or as an unrelated event that should not have affected an independent duty to warn once risk was suspected.

Given that Engineer L's runoff concern was still preliminary and unquantified when Client X requested suspension, the Board concluded that silence at that moment was not unethical, especially since Engineer L subsequently honored the Code's advisory duty once the risk became a confirmed fact.

Because the runoff risk had by this point been quantified and Client X still refused the necessary protective investment, the Board concluded that continuing work would improperly subordinate public welfare to the client's financial interest, which Engineer L could not ethically do.

Reasoning from the distinction between a hunch and a verified fact, the Board explained that Engineer L's silence was permissible only because the runoff concern had not yet been elevated to a founded, evidence-based determination under II.3.a and II.3.b.

Reasoning counterfactually, the Board indicated that had Engineer L already quantified the runoff risk before Client X asked to suspend work, the same silence would have violated disclosure duties, showing that Conclusion 1's leniency was strictly contingent on the timing and epistemic status of the risk.

Because withdrawal alone leaves the confirmed risk to the drinking water source unaddressed if Client X proceeds unsafeguarded, the Board suggested, drawing on BER Case 18-9, that Engineer L's paramount duty under I.1 may require further action such as notifying regulatory authorities.

Given that BER Case 21-2 recognizes climate-driven precipitation change as a foreseeable design factor, the Board's framing of the runoff risk as a purely emergent discovery from a historic rainfall event leaves open whether Engineer L's original risk methodology was itself deficient, a question the Board did not resolve.

Because the risk was still unquantified when Client X requested suspension, the Board's own concern-versus-fact distinction from prior cases supports treating disclosure as prudent but not ethically mandatory, though it stops short of excusing silence entirely given the paramount public welfare backdrop.

Given that BER Case 21-2 treats evolving precipitation risk as foreseeable for a stormwater design specialist, and Engineer L's contract explicitly targeted watershed protection, the Board reasons that the original scope of work should have anticipated increasing rainfall frequency rather than treating its later discovery as wholly novel.

Because Engineer L's contract explicitly assigned a watershed protection duty and the suspension only paused paid work rather than ending the relationship, the Board reasons that some residual awareness obligation persisted, supporting prompt risk studies upon resumption rather than treating the suspension as an ethical blank slate.

Since the runoff risk remained speculative when Engineer L ceased work, the Board concludes that faithful agency under I.4 was not breached because the competing paramount duty under I.1 had not yet become operative, meaning no real deontological conflict existed at that stage.

Given that the risk had been quantified and threatened an entire community's drinking water, the board concluded that Engineer L's disclosure produced a better aggregate outcome than silence, even though it imposed near-term costs on Client X.

Because Client X refused to invest in identified protective measures despite a confirmed risk, the board found that Engineer L's refusal to continue reflected professional integrity protected under II.1.a rather than mere insubordination.

Had Engineer L already quantified the risk before Client X requested suspension, the board would have treated that quantified risk as a material fact requiring disclosure under III.3.a and II.3.a, reversing the original conclusion that silence was permissible.

Even in the absence of explicit local standards, because the risk to the community's drinking water remained real, the board concluded that Engineer L's obligation to withhold work absent safeguards would still follow from the paramount duty under I.1.

Because Engineer L's concern was still unquantified during the suspension period, the board concluded that the apparent tension between transparency and loyalty dissolved, since disclosure obligations under II.3.a and II.3.b are triggered only once a concern rises to the level of a fact.

Given that the historic rainfall event and subsequent study turned an unquantified concern into a confirmed risk to the community's drinking water source, and Client X continued to refuse funding for the identified safeguards despite an explicit compliance duty, the Board concluded that I.1's paramount public welfare duty categorically overrides I.4's faithful agency once risk crosses this evidentiary threshold, making withdrawal from the project the ethically required outcome.

Because Engineer L had no evidentiary basis for the runoff concern when Client X requested suspension, the Board found silence permissible under Fact-Based Opinion and faithful agency, but once the historic rainfall event produced a confirmed increase in stormwater accumulation, the same principle required disclosure and eventually refusal to continue, showing that the Code recalibrates the loyalty-versus-public-welfare balance as factual certainty develops rather than fixing it once and for all.

Should Engineer L disclose the preliminary, unquantified runoff concern before ceasing work, or comply silently with Client X's suspension request?

Should Engineer L continue working on the project without the identified protective measures, or refuse to proceed until Client X funds those safeguards?

Should Engineer L notify regulatory authorities or a successor engineer about the unaddressed risk after withdrawing, or limit the ethical response to withdrawal alone?

Should Engineer L's original design scope have incorporated projected climate-driven precipitation increases, or was reliance on historical rainfall data at the time of design sufficient?

Should Engineer L maintain reasonable awareness of watershed-relevant developments during the suspension without performing unpaid design work, or treat the suspension as a complete pause in professional attention?