Step 4: Full View

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.

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 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 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.

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.

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 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.

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 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.

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.

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 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.

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.

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.

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.

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.

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.

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.

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 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 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 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.

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 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.

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 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.

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.

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.

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.

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 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.

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.

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.

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 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 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 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 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 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 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.