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 BER Case 20-4 to establish recent precedent emphasizing an engineer's primary responsibility to public health, safety and welfare, with specific emphasis on safe drinking water.

Cited alongside BER Case 22-5 to establish recent precedent emphasizing an engineer's primary responsibility to public health, safety and welfare, with specific emphasis on safe drinking water.

Cited as the foundational environmental ethics case establishing that an engineer's duty to public safety is paramount over client interests, and that engineers must report findings affecting public water quality to authorities.

Quoted within BER Case 76-4 to establish the foundational principle that members of the engineering profession must devote their interests to the public welfare.

Cited as the primary example of 'the disclosure question,' establishing that engineers must include all relevant facts-including environmental threats-in written reports submitted to public authorities, not merely mention them verbally.

Cited as one of several cases where disclosure of known facts was required, specifically involving safety violations confided by the client.

Cited as one of several cases where disclosure of known facts was required, specifically involving incomplete drawings and specifications.

Cited as one of several cases where disclosure of known facts was required, specifically involving violations of federal and state laws and regulations.

Cited as one of several cases where disclosure of known facts was required, specifically involving public safety risks from future surge level rise.

Cited as one of several cases where disclosure of known facts was required, specifically involving the effects of sea level rise and changes in precipitation intensities due to climate change.

Cited as a direct parallel to the present case, establishing that an engineer who notifies a client of a safety concern but then continues work when the client refuses to address it has abandoned their ethical duty to the public and violated the Code.

It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk.

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.

The Board's conclusion that Engineer L's silence during the suspension was not unethical rests implicitly on the distinction between a quantified, fact-grounded professional finding and a preliminary, unquantified concern. However, this distinction has limits that the Board did not fully articulate. Code provision II.3.b permits engineers to express technical opinions founded upon knowledge of the facts and competence in the subject matter, and provision III.1.b obligates engineers to advise clients when they believe a project will not be successful. Taken together, these provisions suggest that even a qualitative, pre-analytical concern - when held by an engineer with Engineer L's demonstrated expertise in stormwater control design - may carry sufficient epistemic weight to trigger at least a qualified advisory obligation to the client. The Board's conclusion that silence was permissible should therefore be understood as narrowly fact-specific: it applies only because Engineer L's concern had not yet crossed the threshold from professional intuition to professional judgment. Had Engineer L possessed even a preliminary qualitative estimate of elevated risk at the time of suspension, the same silence would likely have constituted a material omission under provision III.3.a, which prohibits statements containing omissions that are intended or likely to mislead the client. The Board's conclusion does not establish a general safe harbor for withholding early-stage safety concerns; it merely reflects that the epistemic threshold for mandatory disclosure had not yet been reached in this specific instance.

The Board's conclusion that Engineer L's silence during the suspension was not unethical does not resolve the separate question of whether that silence, in combination with the subsequent historic rainfall event, created a compounded ethical deficit. The suspension period was not ethically neutral in its consequences: it coincided with a historic rainfall event that materially elevated the runoff risk to the community's drinking water source, and the absence of any protective design during that period was a direct consequence of the project's suspended state. While Engineer L cannot be held ethically responsible for the rainfall event itself, the Board's analysis does not adequately address whether Engineer L had an obligation, upon resuming work and discovering the elevated risk, to disclose not only the current risk but also the fact that the preliminary concern had existed prior to suspension. Provision III.3.a's prohibition on material omissions that mislead the client applies to the totality of Engineer L's professional communications, and a post-resumption disclosure that omits the pre-suspension history of concern could itself constitute a misleading omission by creating the false impression that the risk was entirely a product of the rainfall event rather than a foreseeable trajectory that Engineer L had already begun to perceive. The Board's approval of the suspension-era silence should not be read as approving a pattern of selective disclosure that obscures the developmental history of the risk.

The Board's marking of Question 2 as 'unknown' - whether it would be ethical for Engineer L to continue working after Client X refuses protective measures - reflects genuine analytical difficulty, but the weight of the applicable code provisions and precedent strongly suggests that continued work under these conditions would be ethically impermissible rather than merely inadvisable. Code provision I.1 establishes that holding paramount the safety, health, and welfare of the public is the engineer's first and overriding obligation. Provision II.1.a requires that when an engineer's judgment is overruled under circumstances that endanger life or property, the engineer shall notify the proper authority. Provision III.1.b obligates engineers to advise clients when a project will not be successful and to refuse to proceed when the client insists on proceeding in a manner that endangers health, safety, or welfare. In this case, Engineer L has not merely expressed a concern - Engineer L has conducted studies, qualitatively confirmed the runoff risk, identified that local environmental standards require protective measures, and communicated this to Client X. Client X has explicitly refused to implement those measures and stated it will address compliance issues 'later, if needed.' This sequence of facts - confirmed risk, identified regulatory obligation, explicit client refusal - satisfies the conditions under which continued work crosses from permissible professional disagreement into active participation in a project that Engineer L knows poses an unmitigated risk to the community's primary drinking water source. Continued work under these conditions would constitute acquiescence to an unsafe client directive in violation of the principle established in BER Case 84-5 and would undermine the paramount public welfare obligation that the Code places above client loyalty. The Board's 'unknown' designation should therefore be resolved in the direction of ethical impermissibility, with withdrawal being the minimum required response.

Even if the Board were to conclude that Engineer L's withdrawal from the project is ethically required upon Client X's refusal of protective measures, withdrawal alone does not exhaust Engineer L's ethical obligations under the Code. Provision II.1.a requires that when an engineer's judgment is overruled under circumstances that endanger life or property, the engineer shall notify the proper authority. In this case, the 'proper authority' is not merely Client X - who has already been notified and has refused to act - but the local environmental regulatory authorities whose standards explicitly require safeguarding the community's primary drinking water source. The community's reliance on the nearby watershed as its primary drinking water source elevates this situation beyond a routine contractual dispute into a matter of direct public health consequence. Engineer L's confidentiality obligations to Client X are real but are not absolute: provision I.1's paramountcy clause and the Code's overall structure establish that confidentiality yields when public safety is at stake. Precedent from BER Case 76-4 and BER Case 07-6 reinforces that engineers cannot suppress or withhold findings that bear on public welfare simply because a client prefers non-disclosure. Accordingly, Engineer L's ethical obligations upon Client X's refusal include not only withdrawal from the project but also notification to the relevant environmental or public health regulatory authorities of the confirmed, unmitigated stormwater runoff risk to the community's drinking water source. This escalation is not merely ethically permissible - it is ethically required once Engineer L has confirmed the risk, communicated it to the client, and received an explicit refusal to act.

The Board's analysis does not address the obligations that arise for Engineer L with respect to any successor engineer who might assume responsibility for the project after Engineer L's withdrawal. If Engineer L withdraws and a successor engineer is engaged by Client X without knowledge of the confirmed stormwater runoff risk and Client X's explicit refusal to implement protective measures, that successor engineer will be placed in a position of unknowing participation in a project with an unmitigated public health risk. Provision III.3.a's prohibition on material omissions that mislead, and the broader principle of professional accountability embedded in the Code, suggest that Engineer L has at minimum an obligation not to actively conceal the confirmed risk from a successor. More affirmatively, the principle of public welfare paramountcy under provision I.1 supports the conclusion that Engineer L should, to the extent permitted by applicable confidentiality constraints, ensure that any successor engineer is made aware of the confirmed risk before assuming project responsibility. This obligation is distinct from and supplementary to the obligation to notify regulatory authorities: it operates within the professional community to prevent the risk from being perpetuated through uninformed professional succession. The Board's silence on this point leaves a significant gap in the ethical analysis of Engineer L's post-withdrawal responsibilities.

In response to Q101: An engineer's preliminary, unquantified concern about public safety crosses the threshold for mandatory disclosure to the client when the concern is (a) grounded in professional judgment rather than mere speculation, (b) directed at a specific, identifiable harm pathway - here, stormwater runoff into a primary drinking water source - and (c) material to the client's ability to make informed decisions about the project, including whether to suspend it. Code provision II.3.b permits engineers to express technical opinions 'founded upon knowledge of the facts and competence in the subject matter,' and provision III.1.b requires engineers to advise clients when they believe a project will not be successful. Engineer L's preliminary concern, though unquantified, was rooted in professional expertise in stormwater control design and was directed at a specific, high-stakes harm pathway. The suspension decision itself was a material project decision that could have been informed by that concern. Accordingly, the threshold for disclosure was met at the moment of suspension, even absent a quantified risk estimate. The Board's conclusion that silence was not unethical (Conclusion 1) appears to rest on the absence of quantification, but the Code does not limit disclosure obligations to quantified findings - it requires disclosure of professional judgment that is fact-grounded and competence-based. Engineer L's silence during suspension communications therefore represents a missed, though arguably not clearly unethical, disclosure opportunity under the applicable provisions.

In response to Q102: Engineer L's silence about the potential drinking water risk during the suspension period constitutes a material omission under Code provision III.3.a, which prohibits statements containing 'a material misrepresentation of fact or omitting a material fact necessary to prevent misrepresentation.' The omission is material because Client X's decision to suspend work - and the terms under which work would resume - was directly affected by whether a latent public safety risk existed. A client who knows that suspension leaves an unmitigated and growing risk to a community's primary drinking water source may choose different suspension terms, accelerate resumption, or take interim protective steps. By omitting this concern, Engineer L deprived Client X of information necessary to make a fully informed decision. The fact that the risk was unquantified does not render it immaterial; materiality is determined by whether a reasonable client would consider the information significant, not by whether the engineer has completed a full quantitative analysis. The affected community's reliance on the watershed as its primary drinking water source elevates the materiality of even a qualitative, preliminary concern. This conclusion extends the Board's finding in Conclusion 1 by identifying a specific provision under which the omission is analytically problematic, even if the Board declined to find it unethical.

In response to Q103: Once Client X refused to implement protective measures after Engineer L had quantified and communicated the confirmed stormwater runoff risk, Engineer L incurred an independent ethical obligation - and likely a mandatory one - to notify local environmental or public health regulatory authorities. This conclusion follows from Code provision I.1, which makes public safety, health, and welfare paramount, and from provision II.1.a, which requires engineers whose judgment is overruled under circumstances that endanger life or property to notify their employer or client and such other authority as may be appropriate. The phrase 'such other authority as may be appropriate' is not permissive language for a trivial risk - it is a directive triggered when a client overrides safety-critical professional judgment. Here, the risk is not abstract: local environmental standards explicitly require safeguarding the community's primary drinking water source, Client X has explicitly refused to comply, and the affected population has no alternative water source. The confidentiality constraint on client information is defeasible under these circumstances. Code provision III.3.a's prohibition on material omissions, combined with the paramount public welfare obligation, creates a hierarchy in which confidentiality yields to safety when the harm is concrete, the affected population is identifiable, and the client has affirmatively refused to act. Engineer L's withdrawal alone, without regulatory notification, would be ethically insufficient under these conditions. BER Case 76-4 and BER Case 07-6 both support the principle that public welfare overrides client loyalty when safety is genuinely at stake.

In response to Q104: If Engineer L withdraws from the project after Client X refuses protective measures, Engineer L bears an ethical obligation to ensure that any successor engineer is made aware of the confirmed stormwater runoff risk to the community's drinking water source before that engineer assumes responsibility for the project. This obligation derives from Code provision I.1's paramount public welfare mandate and from the principle that withdrawal cannot be used as a mechanism to launder a known safety risk by transferring it to an uninformed professional. A successor engineer who is unaware of the confirmed risk may proceed without implementing protective measures, producing the same harm that Engineer L sought to prevent. The ethical force of Engineer L's withdrawal is nullified if it merely substitutes an uninformed engineer for an informed one. While the Code does not contain an explicit successor-notification provision in the extracted text, the combination of the public welfare paramount obligation, the non-deception constraint under III.3.a, and the professional accountability principle supports the conclusion that Engineer L must, at minimum, document the confirmed risk findings and make them available to any successor. If Client X refuses to permit such disclosure to a successor, that refusal itself constitutes an additional ground for regulatory escalation under II.1.a.

In response to Q201 and Q203: The tension between Client Loyalty and Proactive Risk Disclosure is not a symmetrical conflict between equally weighted principles. Code provision I.1 establishes a lexical priority: public safety, health, and welfare are paramount, and client loyalty operates within that constraint rather than alongside it as an equal. When Engineer L chose not to mention the preliminary stormwater concern during the suspension communications, the silence was defensible only because the concern had not yet crossed the fact-grounded threshold required by II.3.b. Once the risk was confirmed and communicated, and Client X refused protective measures, the Client Loyalty principle was no longer available as a justification for continued work or silence. At that point, the Non-Acquiescence to Unsafe Client Directives principle governed, and the resolution required not merely formal objection while continuing work, but withdrawal - and, as argued in response to Q103, regulatory escalation. The Board's unresolved Conclusion 2 implicitly recognizes this hierarchy by suggesting continued work would not be ethical, but the analysis is incomplete without acknowledging that withdrawal alone may be insufficient when a confirmed, unmitigated risk to a community's primary drinking water source persists after client refusal.

In response to Q202: The Code does not limit disclosure obligations to findings that meet a threshold of full analytical rigor or quantification. Code provision II.3.b permits engineers to express technical opinions 'founded upon knowledge of the facts and competence in the subject matter,' and provision III.1.b requires advising clients when a project will not be successful. Both provisions contemplate disclosure of professional judgment, not merely of completed analyses. The principle of Professional Competence in Risk Assessment does not create a safe harbor for silence until quantification is complete; rather, it defines the epistemic standard for the opinion expressed. Engineer L's preliminary concern was founded on years of stormwater design experience and on specific observations about the development's likely impact on the watershed. That concern was a competence-based professional judgment, not speculation. The Fact-Based Disclosure Obligation therefore applied to it, even in qualitative form. The appropriate disclosure would have been a qualified statement - acknowledging the concern, noting its preliminary nature, and recommending that quantification be completed before or upon resumption - rather than silence. This conclusion is consistent with BER Case 07-6, where the Board found that an engineer's obligation to report objectively extended to findings that were inconvenient to the client, regardless of whether they were fully developed.

In response to Q301 and Q303 (deontological and virtue ethics perspectives): From a deontological standpoint, Engineer L's omission of preliminary stormwater concerns during suspension communications represents an incomplete fulfillment of the categorical duty of candor toward Client X. The duty of candor is not contingent on the completeness of analysis; it is grounded in the engineer's role as a trusted professional whose communications must not mislead by omission on matters material to the client's decision-making. However, Engineer L's subsequent disclosure of confirmed risk upon resumption - proactively and in the face of client resistance - demonstrates that the deontological duty was ultimately honored in its most critical application. From a virtue ethics perspective, this sequence reveals a professional whose moral courage was exercised when the stakes were highest and the facts were clearest, but who may have fallen short of the ideal of proactive candor during the earlier, more ambiguous phase. The later disclosure does not fully redeem the earlier silence, because the silence coincided with a period during which the historic rainfall event elevated risk and interim protective measures might have been taken. A fully virtuous engineer - one embodying the character of a trustworthy steward of public welfare - would have communicated the preliminary concern in qualified terms at the moment of suspension, preserving both client loyalty and public safety obligations. The contrast with Engineer A in BER Case 84-5, who failed to withdraw when a client overrode safety-critical judgment, is instructive: Engineer L's later disclosure and implicit withdrawal trajectory represent a morally superior response, but the earlier silence introduces a character inconsistency that the virtue ethics framework cannot fully excuse.

In response to Q302 and Q305 (consequentialist perspectives): The Board's conclusion that omitting unquantified risk during the suspension was not unethical (Conclusion 1) does not adequately account for the consequentialist dimension of the timing gap. The suspension period was not a neutral interval - it coincided with a historic rainfall event that materially elevated runoff risk, and the absence of any interim protective measures during that period was a direct consequence of Client X's uninformed suspension decision. Had Engineer L disclosed the preliminary concern at suspension, Client X might have taken interim protective steps or accelerated resumption, potentially reducing the risk exposure during the rainfall event. The consequentialist calculus therefore weighs against the Board's permissive conclusion, even if the deontological analysis is more forgiving. On Q305, the argument that Engineer L continuing to work after Client X's refusal - while advocating internally for protective measures - would produce better outcomes than withdrawal is not persuasive under the facts. Internal advocacy has already failed: Client X has explicitly refused protective measures and stated it will address compliance issues 'later, if needed.' Continued work by Engineer L under these conditions would lend professional credibility to a non-compliant design, potentially reducing regulatory scrutiny and making it harder for the community to obtain protection. Withdrawal, combined with regulatory notification, is the consequentially superior outcome because it removes Engineer L's implicit endorsement of the unsafe design and activates the regulatory mechanism that local environmental standards provide for exactly this situation.

In response to Q401 and Q402 (counterfactual questions): Had Engineer L disclosed the preliminary, unquantified stormwater runoff concerns to Client X at the moment of work suspension, two beneficial outcomes were plausible. First, Client X would have been better positioned to make an informed suspension decision - potentially choosing to fund a rapid risk quantification study before suspending, or to implement interim protective measures during the suspension period. Second, the gap in protective design that coincided with the historic rainfall event might have been narrowed or eliminated. The counterfactual disclosure would not have required Engineer L to overstate the risk; a qualified statement acknowledging a preliminary professional concern and recommending quantification upon resumption would have satisfied both the candor obligation and the fact-grounded opinion standard. On Q402, requiring Client X to commit in writing to fund protective measures before resuming work would have been ethically superior to the path actually taken - resuming work and then notifying Client X of risk after additional studies. A written commitment would have established a contractual and ethical baseline for the resumed project, reduced the likelihood of the current impasse, and demonstrated Engineer L's proactive stewardship of public welfare. The absence of such a precondition allowed Client X to resume the project without any acknowledged obligation to address the risk, making the subsequent refusal of protective measures predictable and the community's exposure to harm more likely.

In response to Q403: If Client X had agreed to implement protective measures only partially - addressing some but not all of the quantified runoff risks - Engineer L would face a graduated ethical obligation that cannot be resolved by a simple binary of continue or withdraw. The ethical analysis would require Engineer L to assess whether the partial safeguards reduce the residual risk to a level that is consistent with local environmental standards for drinking water source protection and with the paramount public welfare obligation under Code provision I.1. If the partial measures bring the project into compliance with applicable environmental standards, continued work would be ethically permissible, provided Engineer L documents the residual risks and continues to advocate for full implementation. If the partial measures are insufficient to meet regulatory standards or to protect the community's primary drinking water source from a material risk of harm, continued work would not be ethically permissible, because Engineer L would be lending professional credibility to a design that knowingly falls short of the required safety threshold. The key evaluative criterion is not whether Client X has made a good-faith effort, but whether the resulting design meets the objective standard of protecting public health, safety, and welfare. Engineer L's professional judgment - informed by the quantitative risk assessment - is the appropriate instrument for making this determination, and that judgment must be exercised independently of Client X's budget constraints.

In response to Q404 and Q304 (deontological perspective on regulatory escalation): From a deontological standpoint, once Client X refused to invest in protective measures after Engineer L had quantified and communicated the confirmed stormwater runoff risk, regulatory escalation was not merely ethically permissible - it was ethically required. Code provision II.1.a directs engineers whose judgment is overruled under circumstances that endanger life or property to notify 'such other authority as may be appropriate.' This language, read in conjunction with the paramount public welfare obligation of I.1 and the existence of local environmental standards explicitly requiring safeguarding of the community's primary drinking water source, identifies the local environmental regulatory authority as precisely the 'appropriate' authority contemplated by the provision. The deontological duty is triggered by the combination of: (1) a confirmed, quantified risk to public health; (2) an explicit client refusal to implement required protective measures; and (3) the existence of a regulatory authority with jurisdiction over the specific harm. Under these conditions, withdrawal alone satisfies Engineer L's duty to avoid personal complicity in an unsafe design, but it does not satisfy the affirmative duty to protect the public that II.1.a imposes. Regulatory escalation would also have produced superior consequentialist outcomes by activating the enforcement mechanism that local environmental standards provide, potentially compelling Client X to implement protective measures regardless of budget preferences. BER Case 76-4 and BER Case 22-5 both support the conclusion that the public welfare paramount obligation generates affirmative duties of escalation, not merely duties of withdrawal, when client non-compliance creates a concrete risk to an identifiable community.

The tension between Client Loyalty and Proactive Risk Disclosure was resolved differently across the two phases of Engineer L's engagement, revealing a phase-sensitive framework for when disclosure obligations attach. During the suspension phase, the Board accepted that an unquantified, preliminary concern did not yet trigger a mandatory disclosure obligation to Client X, effectively treating Client Loyalty as the governing principle when risk remains speculative and work is being suspended rather than completed. However, once work resumed and Engineer L conducted additional studies that qualitatively confirmed the runoff risk, the Proactive Risk Disclosure principle became paramount and Engineer L's notification to Client X was not merely appropriate but obligatory. This phased resolution teaches that the Code does not demand disclosure of every nascent professional worry, but it does demand disclosure once a concern crosses from speculative to professionally grounded - even if that grounding is qualitative rather than fully quantified. The threshold is professional judgment, not mathematical certainty. Critically, however, the Board's resolution leaves unaddressed whether the suspension period itself created a disclosure gap that was ethically problematic in light of the historic rainfall event that occurred during that gap, suggesting the phase-sensitive framework may be under-inclusive when external risk conditions escalate independently of the engineer's analytical progress.

The principle of Non-Acquiescence to Unsafe Client Directives and the principle of Client Loyalty are not merely in tension in this case - they are structurally incompatible once Client X refuses to implement protective measures after Engineer L has confirmed and communicated the stormwater runoff risk. The Board's implicit conclusion that it would not be ethical for Engineer L to continue working under those conditions reflects the Code's hierarchy: when a client's directive would result in a design that endangers public health - specifically the drinking water supply of a community - the engineer's obligation to hold public welfare paramount under Canon I.1 overrides the faithful agent obligation under Canon I.4. This case reinforces the precedent established in BER Case 84-5, where continuing to work after a client overrides safety-critical professional judgment was found to be a failure of the engineer's non-acquiescence obligation. The synthesis here is that Client Loyalty is a bounded principle: it governs the engineer's conduct within the space of professionally and ethically permissible client service, but it cannot authorize the engineer to become an instrument of a design that the engineer has identified as posing unmitigated risk to public health. Withdrawal is not merely one option among several - it is the minimum ethically required response when the client refuses safeguards that the engineer has determined are necessary. Whether withdrawal alone is sufficient, or whether escalation to regulatory authorities is also required, remains the unresolved frontier of this principle tension.

The principle of Environmental Stewardship applied to drinking water watershed protection and the principle of Client Loyalty interact in this case to expose a gap in the Board's explicit conclusions: neither conclusion addresses whether Engineer L's obligations extend beyond the client relationship to encompass direct notification of regulatory authorities. The Code's confidentiality expectations, while real, are not absolute - they yield when public safety is at stake, as reflected in the defeasible nature of the confidentiality constraint recognized in the Code's structure and in precedents such as BER Case 76-4. When Client X refuses protective measures and explicitly defers regulatory compliance to a future contingency, the unmitigated risk to the community's primary drinking water source does not disappear with Engineer L's withdrawal - it persists and may worsen as the project proceeds under less safety-conscious direction. Environmental Stewardship, understood as an active rather than passive obligation, requires Engineer L not merely to refrain from contributing to the harm but to take affirmative steps to prevent it where the engineer possesses unique knowledge of a confirmed risk. The synthesis of these principles suggests that the Code, properly interpreted in light of Canon I.1 and the local environmental standards requiring safeguarding of public water sources, supports - and may require - escalation to regulatory authorities as the final expression of the engineer's paramount public welfare obligation when client-level remediation has been exhausted. Client Loyalty, having already been overridden by the withdrawal obligation, cannot serve as a shield against this further duty. The confidentiality constraint is defeasible precisely in circumstances like these, where the safety of a community's drinking water is at stake and the client has affirmatively refused to act.

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?

At what point does an engineer's preliminary, unquantified concern about public safety become sufficiently concrete to trigger a mandatory disclosure obligation to the client, even if work is being suspended rather than completed?

Does Engineer L's silence about the potential drinking water risk during the suspension period constitute a material omission under the Code, even if the risk had not yet been quantified, given that the affected community's primary drinking water source was at stake?

When Client X refuses to implement protective measures and states it will address compliance issues 'later, if needed,' does Engineer L have an independent obligation to notify local environmental or public health regulatory authorities about the unmitigated risk to the community's drinking water source, even if doing so requires disclosing confidential client information?

If Engineer L withdraws from the project after Client X refuses protective measures, is Engineer L ethically obligated to ensure that any successor engineer is made aware of the confirmed stormwater runoff risk to the community's drinking water source before that engineer assumes responsibility for the project?

Does the principle of Client Loyalty as a faithful agent conflict with the principle of Proactive Risk Disclosure when Engineer L chooses not to mention an unquantified but plausible public safety concern during a client-initiated work suspension, and if so, which principle should govern?

Does the principle of Fact-Based Disclosure Obligation conflict with the principle of Professional Competence in Risk Assessment when Engineer L's concern is real but not yet quantified - specifically, does the Code require disclosure of qualitative professional judgment about risk, or only of findings that meet a threshold of analytical rigor?

Does the principle of Non-Acquiescence to Unsafe Client Directives conflict with the principle of Client Loyalty when Client X insists on proceeding without protective measures, and does the resolution of this tension require Engineer L to withdraw from the project entirely or merely to formally object while continuing work?

Does the principle of Environmental Stewardship applied to drinking water watershed protection conflict with the principle of Client Loyalty when fulfilling the stewardship obligation would require Engineer L to escalate the unmitigated runoff risk to regulatory authorities over the explicit objection of Client X, and how should the Code's confidentiality expectations be weighed against the paramount public welfare obligation?

From a deontological perspective, did Engineer L fulfill a categorical duty of candor toward Client X when Engineer L omitted mention of preliminary stormwater runoff concerns during the work suspension communications, even though those concerns were not yet quantified?

From a consequentialist perspective, did the Board's conclusion that omitting unquantified risk during the suspension was not unethical adequately weigh the potential downstream harm to the small community's drinking water supply, given that the suspension period itself delayed protective measures and coincided with a historic rainfall event that elevated runoff risk?

From a virtue ethics perspective, did Engineer L demonstrate the professional integrity and moral courage expected of a licensed engineer by notifying Client X of confirmed runoff risk after resumption, and does this later disclosure redeem the earlier silence during suspension, or does it reveal an inconsistency in Engineer L's character as a trustworthy steward of public welfare?

From a deontological perspective, once Client X refused to invest in protective measures after Engineer L had quantified and communicated the stormwater runoff risk, did Engineer L incur a strict duty not merely to withdraw from the project but also to escalate the identified risk to local environmental regulatory authorities, given that local environmental standards explicitly require safeguarding the community's primary drinking water source?

From a consequentialist perspective, would Engineer L continuing to work on the project after Client X's refusal of safeguards-while simultaneously advocating internally for protective measures-produce better outcomes for the community's drinking water safety than immediate withdrawal, given that withdrawal removes Engineer L's influence over the design entirely and leaves the project in potentially less safety-conscious hands?

From a virtue ethics perspective, does Engineer L's willingness to continue working on the project after Client X refuses protective measures-even framed as continued advocacy-reflect a failure of the virtue of moral courage, and how does this compare to the conduct of Engineer A in BER Case 84-5, who similarly failed to withdraw when a client overrode safety-critical professional judgment?

If Engineer L had disclosed the preliminary, unquantified stormwater runoff concerns to Client X at the moment of work suspension, would Client X have been better positioned to make an informed decision about whether to suspend work at all, and would earlier disclosure have prevented the gap in protective design that coincided with the historic rainfall event?

If Engineer L had refused to resume work on the project unless Client X first committed in writing to fund the protective measures identified during the preliminary design phase, would this contractual precondition have been ethically superior to resuming work and then notifying Client X of risk after conducting additional studies?

If Client X had agreed to implement the protective measures identified by Engineer L but only partially-addressing some but not all of the quantified runoff risks-would it have been ethical for Engineer L to continue working on the project under those conditions, and how should Engineer L have evaluated whether partial safeguards were sufficient to meet the paramount obligation to public health, safety, and welfare?

If Engineer L had escalated the confirmed stormwater runoff risk directly to local environmental regulatory authorities after Client X refused protective measures, rather than simply withdrawing from the project, would this action have better served the community's drinking water safety, and would such escalation have been ethically required or merely ethically permissible under the applicable code provisions?

Withholding preliminary risk concerns may superficially serve client loyalty during the pre-analysis phase, but it violates Engineer L's timely risk disclosure and fact-grounded opinion obligations because even unverified concerns about public safety must be communicated to the client in a professionally qualified manner.

Omitting risk information during the project suspension period directly violates Engineer L's non-deception omission constraint and timely disclosure obligations, as the suspension does not suspend the engineer's ethical duty to communicate known safety risks to the client and potentially affected parties.

Resuming work without disclosing identified runoff risks constitutes a serious violation of Engineer L's post-resumption disclosure obligation and public welfare paramount principle, as proceeding with design work while concealing confirmed watershed contamination risks directly endangers the community's drinking water supply.

Conducting additional risk studies fulfills Engineer L's professional competence and fact-grounded opinion obligations by transforming preliminary concerns into verified findings, thereby providing the evidentiary basis required before formal disclosure obligations are fully triggered, while remaining constrained by scope of practice and client budget limitations.

Formally notifying the client of confirmed stormwater runoff risk is the ethically required action that fulfills Engineer L's core disclosure, public welfare, and non-acquiescence obligations, guided by the proactive risk disclosure and public welfare paramount principles, while being constrained by procedural documentation requirements, confidentiality boundaries, and the regulatory escalation pathway that must be followed if the client refuses to implement protective measures.

Continuing work after Client X refuses to implement protective safeguards for a confirmed stormwater runoff risk to the community's drinking water watershed superficially satisfies the engineer's fiduciary duty to the client but fundamentally violates the paramount obligation of public welfare protection, the non-acquiescence obligation to unsafe client directives, and the duty to escalate to regulatory authorities, as established by NSPE Code of Ethics and BER precedents including BER Case 84-5 where a similar failure to refuse unsafe client directives was found ethically impermissible.

This question arose because Engineer L's silence at suspension sits precisely at the contested boundary between the Fact-Grounded Opinion Constraint (which limits engineers to disclosing verified findings) and the Public Safety Paramount Constraint (which demands early communication of any credible risk to a drinking water source). The question is not merely whether Engineer L acted wrongly, but whether the ethical architecture of the NSPE Code permits silence when risk is real but unquantified.

This question emerged because Client X's refusal transformed the ethical situation from a disclosure problem into a continuation problem: Engineer L now possessed confirmed data that the design would be unsafe, and the NSPE Code's Non-Acquiescence to Client Economic Override Constraint directly collides with the Faithful Agent Constraint when the client's economic decision produces a foreseeable public safety harm. The question crystallizes the unresolved tension between serving the client and refusing to be the instrument of harm.

This question arose because the NSPE Code and BER precedents do not explicitly define the evidentiary threshold at which a preliminary engineering concern becomes a disclosure-triggering finding, and the suspension of work - which removes the normal project-completion context for disclosure - creates a procedural gap that the Code's general principles do not cleanly resolve. The question is structurally novel because it asks whether the suspension event itself resets or accelerates the disclosure clock.

This question emerged because the suspension event created a temporal gap in which Engineer L held a risk concern but had no active project obligation to document or report it, and the Code's silence on engineer duties during work suspension periods left the materiality of the omission legally and ethically ambiguous. The question is further sharpened by the specific identity of the endangered resource - a community's primary drinking water source - which invokes heightened public welfare obligations that may not be suspended merely because the project is.

This question arose because it sits at the most contested intersection in engineering ethics: the point where client loyalty, confidentiality, and public welfare obligations all converge and conflict simultaneously. Client X's explicit refusal and indefinite deferral of compliance removed the possibility of client-mediated resolution, forcing the question of whether Engineer L's public safety obligations extend beyond the client relationship to encompass independent regulatory action - a question the NSPE Code addresses in principle but does not resolve with procedural specificity, particularly when the triggering risk is qualitative rather than quantified.

This question emerged because Engineer L's withdrawal does not extinguish the confirmed public safety risk, and the act of handing off a project without disclosing a known watershed contamination threat could itself constitute a form of acquiescence to an unsafe condition. The tension between post-withdrawal confidentiality norms and the continuing paramount obligation to public welfare forces the question of whether Engineer L bears an affirmative successor-notification duty.

This question arose because the work suspension created a temporal gap in which Engineer L possessed a risk concern but had no active project context in which to formally raise it, and the Code's silence on disclosure obligations during client-initiated suspensions left the governing principle ambiguous. The question crystallizes the structural conflict between loyalty-based restraint and welfare-based proactivity when the engineer's knowledge is real but not yet analytically confirmed.

This question emerged because the Code's disclosure obligations were drafted with reference to factual findings, not to the intermediate epistemic state of a professional concern that is real but not yet analytically confirmed, creating a gap in which two legitimate professional norms - rigor before speaking and transparency when knowing - point to opposite conduct. The question forces a determination of whether the Code's disclosure threshold is epistemological (requiring quantification) or professional-judgment-based (requiring only genuine expert concern).

This question arose because BER precedents such as BER Case 84-5 establish that engineers must not acquiesce to client overrides of safety requirements, but they do not uniformly specify whether the remedy is withdrawal or documented objection, leaving the resolution dependent on a risk-severity judgment that is itself contested. The confirmed threat to drinking water infrastructure raises the stakes sufficiently that the adequacy of mere formal objection becomes genuinely uncertain.

This question emerged because the NSPE Code of Ethics establishes public welfare as paramount and recognizes environmental stewardship as a professional obligation, but it also imposes confidentiality duties to clients and does not specify the procedural trigger for unilateral regulatory escalation against a client's wishes, creating a structural gap precisely at the point where the obligations are most in conflict. The drinking water context amplifies the stakes to the level where the defeasibility of confidentiality is most plausible yet most contested, forcing the question of which principle governs and by what mechanism.

This question arose because Engineer L's omission during suspension sits at the contested boundary between the deontological duty of complete candor and the professional constraint against communicating unverified opinions as facts. The question is structurally necessary because the data-an unquantified concern withheld during a suspension-activates two legitimate but incompatible warrants, and neither the NSPE Code nor BER precedent unambiguously resolves which warrant governs when risk is real but not yet measurable.

This question arose because the consequentialist framework demands that ethical adequacy be judged by outcomes actually produced, and the coincidence of the suspension period with a historic rainfall event introduces a causal pathway from omission to elevated community risk that the Board's analysis may not have fully weighted. The question is structurally generated by the tension between the Board's warrant (unquantified risk does not obligate disclosure) and the consequentialist rebuttal condition (foreseeable harm amplification during the omission window overrides the quantification threshold).

This question arose because virtue ethics evaluates character holistically across time, and the two-phase behavioral pattern-silence then disclosure-creates an interpretive contest over whether Engineer L's character is unified by prudent integrity or fractured by situational responsiveness. The question is structurally necessary because the same sequence of actions (omit, then disclose) is simultaneously evidence for and against the virtue of trustworthy stewardship of public welfare, and no single warrant resolves the ambiguity without adjudicating the relationship between prudence and candor as virtues.

This question arose because Client X's refusal after confirmed risk disclosure creates a data state in which the faithful-agent relationship is exhausted and the public-welfare paramount principle is fully activated, but the specific content of the local environmental standards introduces a second, independent warrant (regulatory compliance obligation) that may impose a positive escalation duty beyond what the NSPE Code's withdrawal provision alone requires. The question is structurally generated by the contest between the withdrawal warrant and the regulatory-escalation warrant, both triggered by the same data event but leading to materially different required actions.

This question arose because the consequentialist framework requires comparing the expected-outcome distributions of two available action paths-continued engagement versus withdrawal-under conditions of client non-compliance, and the answer depends critically on empirical assumptions about Engineer L's residual influence, the quality of potential replacement engineers, and the probability that internal advocacy can shift Client X's decision. The question is structurally necessary because the same data state (confirmed risk, client refusal) is consistent with both action paths being welfare-maximizing depending on which empirical assumptions are warranted, and no a priori ethical principle resolves the contest without those factual determinations.

This question emerged because the same factual pattern-confirmed risk, client refusal, continued work-appeared in both Engineer L's situation and BER Case 84-5, yet the ethical evaluation of 'continuing' depends entirely on which warrant governs: the non-acquiescence principle condemns continuation as moral cowardice, while the faithful-agent principle permits it as sustained advocacy. The parallel to Engineer A, who was found to have failed by not withdrawing, sharpens the question by providing a precedent that contests Engineer L's framing of continued work as virtuous.

This question arose because the historic rainfall event created a counterfactual pressure point: had Client X known of even preliminary concerns at suspension, the suspension decision itself might have been different, potentially preventing the gap in protective design that coincided with the damaging event. The tension between the disclosure warrant and the fact-grounded opinion constraint means the question cannot be resolved without first resolving the epistemic threshold question, which the case facts leave ambiguous.

This question emerged because the sequential structure of Engineer L's actual conduct-resuming work and then notifying-created an apparent gap between the moment of confirmed risk and the moment of client commitment, raising the question of whether the ethical obligation to protect public safety required a structural precondition rather than a concurrent notification. The non-acquiescence principle, reinforced by BER Case 84-5, contests the adequacy of notification-after-resumption as a substitute for commitment-before-resumption.

This question arose because the binary framing of 'full safeguards or withdrawal' obscures the practical reality that clients often implement partial measures, and the ethical framework must provide guidance on how engineers evaluate sufficiency rather than simply demanding perfection. The tension between the inviolable public safety constraint and the professional judgment required to assess partial compliance creates a question that cannot be resolved by rule alone but requires application of Engineer L's stormwater risk assessment competence to the specific residual risk profile.

This question emerged because the NSPE Code and BER precedents (including BER Cases 76-4 and 07-6) establish a hierarchy in which public welfare is paramount, but they do not clearly specify whether the engineer's obligation to protect the public is discharged by withdrawal or whether confirmed, client-refused risks to community drinking water sources trigger an affirmative duty to notify regulatory authorities. The defeasible confidentiality constraint and the safety escalation obligation are both present in the ethical framework, but their interaction in the specific context of a refused protective measure and a threatened public water supply creates genuine normative uncertainty about the threshold between permissible and required escalation.

The board concluded that Engineer L's silence was not unethical because the risk concern was too preliminary and unquantified to constitute a professional finding requiring disclosure; without a fact-grounded judgment, the epistemic threshold for mandatory advisory communication under provisions II.3.b and III.1.b had not been reached, leaving compliance with the client's suspension request as the permissible course of action.

The board concluded that continued work would be unethical because the combination of confirmed risk, identified regulatory requirements, and explicit client refusal satisfied the conditions under which Engineer L's participation would cross from loyal service into complicity in an unmitigated public safety hazard, consistent with the principle established in BER Case 84-5 and the overriding obligation under Code provision I.1.

The board refined Conclusion 1 by articulating that the permissibility of Engineer L's silence was narrowly contingent on the concern not yet having crossed into professional judgment - had even a qualitative preliminary estimate of elevated risk existed, the same silence would likely have constituted a material omission under III.3.a, meaning the conclusion does not license engineers to routinely withhold early-stage safety concerns but only reflects the specific epistemic state at the moment of suspension.

The board concluded that approval of suspension-era silence does not extend to approving a pattern of selective post-resumption disclosure, because III.3.a's prohibition on misleading omissions applies to the full arc of Engineer L's professional communications - meaning that upon resuming work, Engineer L bore an obligation to disclose not only the current confirmed risk but also the fact that a preliminary concern had existed before suspension, so that Client X could understand the risk as a foreseeable trajectory rather than an unexpected consequence of the rainfall event.

The board resolved the 'unknown' designation on Question 2 in the direction of ethical impermissibility, reasoning that the weight of provisions I.1, II.1.a, and III.1.b - combined with the precedent of BER Case 84-5 - compels the conclusion that Engineer L's continued participation after confirmed risk and explicit client refusal would constitute active complicity in an unmitigated public safety hazard, with withdrawal being the minimum required response and regulatory notification remaining an open but strongly implied additional obligation.

The board concluded that Engineer L's ethical obligations upon Client X's refusal extended beyond withdrawal to mandatory notification of environmental or public health regulatory authorities, because provision II.1.a's directive to notify 'such other authority as may be appropriate' is triggered precisely when a client overrides safety-critical professional judgment, and because the community's exclusive reliance on the threatened watershed transformed this from a contractual matter into a direct public health emergency that confidentiality obligations cannot suppress.

The board identified a gap in the prior analysis and concluded that Engineer L bears a supplementary post-withdrawal obligation - distinct from regulatory notification - to ensure that any successor engineer is made aware of the confirmed risk before assuming project responsibility, grounded in provision III.3.a's prohibition on material omissions and the overarching public welfare mandate of provision I.1, because allowing a successor to proceed in ignorance would perpetuate the unmitigated risk through professional succession rather than resolve it.

The board concluded that Engineer L's preliminary, unquantified concern crossed the mandatory disclosure threshold at the moment of suspension because it was grounded in professional expertise, targeted a specific high-stakes harm pathway, and was material to Client X's suspension decision - extending the original board finding by identifying that the Code's disclosure provisions do not require quantification as a precondition, even while stopping short of declaring the silence clearly unethical.

The board concluded that Engineer L's silence about the potential drinking water risk during the suspension period constituted a material omission under provision III.3.a because the information was directly relevant to Client X's suspension decision and the community's sole dependence on the threatened watershed made even a qualitative concern significant to any reasonable client - extending the original board finding by identifying the specific provision under which the omission is analytically problematic, even if the board declined to label it unethical.

The board concluded that Engineer L incurred a mandatory - not merely permissive - obligation to notify local environmental or public health regulatory authorities once Client X refused protective measures, because provision II.1.a's 'other authority' directive is triggered by exactly this scenario, the confidentiality constraint is defeated by the combination of concrete harm, identifiable affected population, and client refusal, and BER Cases 76-4 and 07-6 confirm that public welfare overrides client loyalty when safety is genuinely at stake - making withdrawal without regulatory notification ethically insufficient under these conditions.

The board concluded that Engineer L bears a post-withdrawal notification obligation to any successor engineer because the ethical force of withdrawal is nullified if it merely substitutes an uninformed engineer for an informed one; the combination of I.1's paramount mandate, the non-deception constraint under III.3.a, and professional accountability principles compelled at minimum documentation and disclosure of confirmed risk findings, with Client X's refusal to permit such disclosure treated as an independent ground for regulatory escalation under II.1.a.

The board concluded that the Client Loyalty versus Proactive Risk Disclosure tension is not a symmetrical conflict but a hierarchical one in which I.1 establishes lexical priority, meaning that once the risk was confirmed and Client X refused protective measures, the Non-Acquiescence principle governed and required withdrawal - not merely formal objection while continuing work - and further that withdrawal alone may be insufficient when a confirmed, unmitigated risk to a community's primary drinking water source persists after client refusal.

The board concluded that the Fact-Based Disclosure Obligation applied to Engineer L's preliminary qualitative concern because II.3.b and III.1.b contemplate disclosure of professional judgment rather than only completed analyses, and that the appropriate response was a qualified statement acknowledging the concern, noting its preliminary nature, and recommending quantification - not silence - consistent with BER Case 07-6's holding that reporting obligations extend to inconvenient, incompletely developed findings.

The board concluded that Engineer L's omission during suspension represented an incomplete fulfillment of the categorical duty of candor under deontological analysis and a character inconsistency under virtue ethics analysis, because a fully virtuous engineer would have communicated the preliminary concern in qualified terms at suspension to preserve both client loyalty and public welfare obligations; while Engineer L's later disclosure and implicit withdrawal trajectory were morally superior to Engineer A's conduct in BER Case 84-5, the earlier silence during an elevated-risk period introduced an inconsistency that neither framework could fully excuse.

The board concluded that the consequentialist dimension weighs against the Board's permissive conclusion on omission during suspension because the historic rainfall event made the timing gap materially harmful rather than neutral, and that on the question of continued work versus withdrawal, withdrawal combined with regulatory notification is the consequentially superior outcome because it removes Engineer L's implicit endorsement of the unsafe design and activates the regulatory mechanism that local environmental standards provide for exactly this situation - while the 'continued advocacy' alternative is not persuasive because internal advocacy had already demonstrably failed.

The board concluded that earlier disclosure of preliminary concerns - framed as a qualified professional judgment rather than a confirmed finding - would have enabled Client X to make a more informed suspension decision and potentially narrowed the protective design gap that coincided with the historic rainfall event. On Q402, the board determined that requiring a written commitment to fund protective measures before resuming work was ethically superior because it would have established an acknowledged obligation, reduced the likelihood of the subsequent impasse, and demonstrated proactive stewardship of public welfare rather than reactive notification after additional studies.

The board resolved Q403 through a graduated, compliance-anchored framework: if partial safeguards bring the project into conformity with applicable environmental standards, continued work is ethically permissible provided Engineer L documents residual risks and continues advocating for full implementation; if partial measures fall short of regulatory standards or leave a material risk to the drinking water source unmitigated, continued work is not ethically permissible because Engineer L would be lending professional credibility to a knowingly deficient design. The key criterion is objective regulatory compliance, not the client's subjective effort or financial situation.

The board concluded from a deontological standpoint that once the three triggering conditions were met - confirmed quantified risk, explicit client refusal, and a regulatory authority with jurisdiction - regulatory escalation was not merely permissible but ethically required under II.1.a read in conjunction with I.1. The board further found that escalation would have produced superior consequentialist outcomes by activating the enforcement mechanism that local environmental standards provide, and cited BER Cases 76-4 and 22-5 to support the principle that the paramount public welfare obligation generates affirmative escalation duties, not merely duties of withdrawal.

The board resolved the Client Loyalty versus Proactive Risk Disclosure tension through a phase-sensitive framework that treats the disclosure obligation as contingent on whether the engineer's concern has crossed from speculative to professionally grounded. It accepted Engineer L's silence during the suspension as not yet triggering mandatory disclosure, but found the post-resumption notification obligatory once qualitative confirmation was achieved. The board acknowledged, however, that this framework may be under-inclusive when external risk conditions - such as the historic rainfall event - escalate independently of the engineer's analytical progress, suggesting the phase-sensitive resolution may not fully account for the community's exposure during the suspension gap.

The board concluded that once Client X refused safeguards for a confirmed, quantified public health risk, the principles of Non-Acquiescence and Client Loyalty became structurally incompatible rather than merely in tension, and the Code's hierarchy required Engineer L to prioritize public welfare over client service. Withdrawal was identified as the minimum ethically required response - not merely one option among several - with the board citing BER Case 84-5 to reinforce that continued work under these conditions constitutes a failure of the non-acquiescence obligation, while leaving open the unresolved question of whether withdrawal alone is sufficient or whether escalation to regulatory authorities is also required.

The board concluded that Engineer L's obligations under Canon I.1 and applicable local environmental standards - interpreted through the lens of active Environmental Stewardship rather than mere non-participation in harm - support and may require direct notification of regulatory authorities after Client X's refusal of protective measures, because withdrawal alone leaves the community's drinking water at continued and potentially worsening risk; the board reached this conclusion by synthesizing the defeasible confidentiality framework recognized in BER Case 76-4 with the principle that Client Loyalty, having already been overridden by the withdrawal duty, cannot function as a secondary shield against the engineer's paramount public welfare obligation when the engineer uniquely possesses confirmed knowledge of an unmitigated environmental risk.

Was it ethical for Engineer L to cease work when requested by Client X without voicing concern about the preliminary, unquantified risk of stormwater impact to the community drinking water source?

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 as necessary to protect the community's primary drinking water source?

After withdrawing from the project following Client X's refusal to implement protective measures, is Engineer L ethically obligated to notify local environmental or public health regulatory authorities of the confirmed, unmitigated stormwater runoff risk to the community's primary drinking water source?

Should Engineer L disclose the preliminary, unquantified stormwater runoff concern to Client X during the work suspension communications, even though the concern has not yet been quantified or confirmed through additional studies?

After resuming work and qualitatively confirming the stormwater runoff risk to the community's drinking water source, should Engineer L formally notify Client X of the confirmed risk and withdraw from the project if Client X refuses to invest in the protective measures identified as necessary?

When Engineer L discloses the confirmed stormwater runoff risk to Client X after resuming work, should Engineer L also disclose the pre-suspension history of the preliminary concern - including that the concern existed before the suspension and before the historic rainfall event - so that Client X can make a fully informed decision about the risk's origins and trajectory?

Should Engineer L disclose preliminary, unquantified stormwater runoff concerns to Client X when Client X requests suspension of work, even though the risk has not yet been formally quantified?

After Client X refuses to invest in protective measures for a confirmed stormwater runoff risk to the community's primary drinking water source, should Engineer L withdraw from the project and notify local environmental regulatory authorities, or continue working while advocating internally for protective measures?

After withdrawing from the project, should Engineer L ensure that any successor engineer is made aware of the confirmed stormwater runoff risk and Client X's explicit refusal to implement protective measures before that engineer assumes project responsibility?