Step 4: Review

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

If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.

Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.

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

Cited to establish the fundamental importance of holding public safety paramount, using a scenario where a nonengineer reopened a dangerous closed bridge.

Cited to show that an engineer who discovers safety deficiencies has an obligation to pursue resolution by contacting authorities with jurisdiction, supporting the duty to report beyond just the client.

Cited to establish that engineers have a paramount obligation to report safety violations to appropriate public authorities even when confidentiality agreements exist or professional judgment is overruled.

In fulfillment of their ethical obligations under the Code, Engineers A and B should formally communicate their concerns to the MWC, including that they believe the project will not be successful.

Both Engineers A and B have ethical obligations to notify the MWC and other appropriate authorities that prematurely changing the water source puts the public health and safety at risk. Furthermore, Engineers A and B have independent obligations to formally and in writing report their concerns to the state regulatory agency. While they may provide a joint and cooperative report, each has an independent obligation. Neither the consent nor opposition of the client is a factor in their fulfillment of this obligation.

The Board's conclusion implicitly resolves the tension between confidentiality (II.1.c) and public safety reporting duties (II.1.a) by treating paramountcy of public welfare as a threshold condition that activates an exception to confidentiality. Because II.1.c itself contains an implicit exception for legally mandated or safety-critical disclosures, Engineer A and Engineer B's duty to report to the state regulatory agency is not a breach of client confidentiality but an application of the Code's hierarchy, in which public safety obligations under II.1 and II.1.a take precedence over confidentiality when lead-leaching risk to public health is at stake.

The Board's finding that each engineer bears an independent reporting obligation is not diminished by differences in their contractual relationship to the MWC. Engineer A's status as a salaried employee and chief engineer, and Engineer B's status as an independent consultant, do not create differing thresholds of duty; both hold licenses and both possess professional judgment implicating II.1.a. The independence of the obligation reflects the personal nature of licensure and professional responsibility, not the structure of employment or contract.

The Board's conclusion that MWC consent or opposition is not a factor in fulfilling the reporting obligation implies that the MWC's institutional authority as governing decision body cannot override or supersede the engineers' independent professional duty. While the MWC retains ultimate authority to make policy and budgetary decisions about the water source change, that authority does not extend to controlling whether its engineers report public health risks to external regulatory bodies; the engineers' obligations under the Code operate independently of, and are not subordinate to, the client relationship or governance structure.

The sparse public attendance at the MWC meeting does not satisfy or substitute for the engineers' independent duty to notify the state regulatory agency. The Board's reasoning suggests that the adequacy of public awareness through open meetings is a separate governance concern from the engineers' professional duty, which exists specifically because ordinary citizens attending a public meeting cannot be relied upon to trigger regulatory intervention; only formal notification to a competent authority with jurisdiction over drinking water standards can adequately protect the public.

The Board's recommendation to formally communicate concerns to the MWC (Conclusion 1) and its finding of an independent duty to notify the state regulatory agency (Conclusion 2) together imply a sequential escalation model: engineers must first exhaust internal advisory channels with their employer/client before or concurrently with external regulatory notification, but failure of the internal channel to produce a satisfactory outcome does not excuse or delay the external reporting obligation. The MWC's override of the delay recommendation is precisely the triggering event that converts an internal advisory duty into an external reporting duty.

Neither Engineer A's continued employment as chief engineer for the MWC nor Engineer B's continued consulting relationship is inherently incompatible with fulfilling the reporting obligation; the Board's conclusion does not require resignation as a precondition for ethical compliance. Rather, the obligation to report to the state regulatory agency can be discharged while the engineers remain in their professional roles, since the duty is definitional to their licensure rather than contingent on severing the employment or consulting relationship.

Engineer A's dual role as MWC employee and licensed PE does not create a different or lesser obligation than Engineer B's. Code provision II.1.a is triggered whenever a professional engineer's judgment is overruled under circumstances endangering life or property, regardless of whether the engineer is an internal employee or an outside consultant. Employment loyalty to the MWC cannot dilute Engineer A's independent duty to notify appropriate authorities; if anything, Engineer A's insider position and greater knowledge of the accelerated timeline heighten the urgency of that duty rather than excusing it.

Nothing in the Board's reasoning suggests that resignation or removal from the project is an ethical prerequisite for Engineer A. The Code's emphasis is on affirmative reporting action, not on withdrawal from employment. Engineer A can simultaneously remain chief engineer and satisfy the II.1.a duty by formally and independently notifying the state regulatory agency; continued employment only becomes ethically problematic if Engineer A allows that employment to suppress or delay the required disclosure.

The tension framed in Q201 is more apparent than real. Advising the MWC that the project will not be successful (III.1.b) and holding public welfare paramount (II.1) are mutually reinforcing rather than competing obligations in this case: both point toward prompt, transparent disclosure. Any concern about public alarm or undermining confidence in the MWC is subordinate to the Code's clear priority ordering, which places public safety above institutional reputation or public perception management.

Regarding Q202, the apparent conflict between client confidentiality (II.1.c) and public welfare is resolved within the Code itself rather than left as an open tension: II.1.c's confidentiality obligation is explicitly subordinate to the paramount duty to protect public health and safety. Once a bona fide risk to public health from lead leaching is identified, disclosure to the state regulatory agency is not an exception requiring special justification but the direct application of the Code's built-in hierarchy of duties.

From a deontological standpoint (Q301), the joint verbal recommendation delivered at the sparsely attended MWC meeting does not by itself discharge the II.1.a duty. A duty framed as notifying 'appropriate authorities' requires formal, documented communication to a body with regulatory authority beyond the client itself. Because Engineers A and B's efforts stopped at persuading the MWC internally, their duty under II.1.a remained unfulfilled until and unless they separately notified the state regulatory agency in writing, as the Board's second conclusion makes explicit.

On the virtue-ethics question (Q303), Engineer A's continuation as chief engineer after being overruled is not itself a failure of integrity. Professional virtue is demonstrated not by exit from the role but by persistence in advocacy: continuing to press the concern through formal, written, and independent channels to the regulatory agency, even after being outvoted internally. Abandoning the position without ensuring proper notification would arguably reflect a greater lapse in integrity than remaining employed while fulfilling the reporting duty.

Counterfactually (Q401), even if the MWC meeting had been well attended by the public and press, the Board's reasoning would likely still require formal notification to the state regulatory agency. Public awareness of a recommendation is not equivalent to formal regulatory reporting, and the Code's obligation runs to 'appropriate authorities' with jurisdiction to act, not merely to an informed citizenry. Media or public attendance does not substitute for the independent professional duty each engineer owes under II.1.a.

Regarding Q402, the reporting obligation is contingent on the existence of a genuine risk to public health, not an automatic feature of any water source change. If Engineer B's report had concluded that the accelerated timeline posed no material corrosion or lead-leaching risk, the predicate 'circumstances that endanger life or property' required by II.1.a would not be present, and the independent duty to report to the state regulatory agency would not arise merely from the water source change itself.

On Q403, had the MWC accepted the engineers' recommendation and delayed the water source change, the triggering event for the regulatory notification duty—professional judgment being overruled under circumstances endangering public health—would not have occurred. In that scenario, the ordinary duty to advise the client under III.1.b would still apply, but the heightened, independent obligation to report externally to the state regulatory agency described in the Board's second conclusion would not be activated.

Concerning Q404, the Board's reasoning that each engineer bears an independent reporting obligation flows from individual professional licensure rather than employment structure. Whether Engineer B is a salaried MWC employee or an independent consultant is immaterial: the duty under II.1.a attaches personally to each licensed engineer who forms the professional judgment that public health is endangered, and cannot be discharged vicariously through a single organizational report.

The Code resolves the apparent tension between Public Welfare Paramount and the duty of confidentiality (II.1.c) by building an explicit override into II.1.a: when engineering judgment on a public-safety matter is overruled, the duty to notify appropriate authorities activates automatically and supersedes the client-consent requirement that would otherwise govern disclosure of client facts and data. The Board's conclusion that 'neither the consent nor opposition of the client is a factor' shows that confidentiality is not treated as a competing principle of equal weight in safety-critical situations, but as a default rule that is explicitly suspended once paramount welfare obligations are triggered.

Transparency in Advising MWC of Project Failure (III.1.b) and Public Welfare Paramount are not actually in tension in this case but operate as sequential, complementary duties: III.1.b requires engineers to tell the client the project will not succeed as designed, while II.1.a requires them to go further and report to external authorities once that professional judgment is overruled. The Board's two conclusions can be read as a duty ladder, informing the client first, then escalating to the regulator when the client rejects the warning, rather than a conflict requiring the engineers to choose between candor to the employer and protection of the public.

The MWC's institutional authority as the governing decision body is treated by the Board as legally legitimate but ethically non-dispositive: the Commission retains the power to vote to proceed with the accelerated water source change, yet that authority does not discharge or diminish the engineers' independent professional obligations. This case therefore illustrates that Public Welfare Paramount functions as a floor beneath organizational decision-making authority, an employer or client can overrule an engineer's technical recommendation, but cannot overrule the engineer's downstream duty to protect the public once that recommendation is rejected.

What are the ethical obligations of Engineer A and Engineer B in this circumstance?

What should Engineer A and Engineer B do?

Given that Engineer A is both an employee of the MWC and a licensed PE, does the dual role create a distinct set of obligations when the governing body overrules Engineer A's professional judgment on a matter endangering public health?

Does the sparse public attendance at the MWC meeting where the delay recommendation was presented raise a separate concern about whether the public was adequately informed before the vote, independent of the engineers' reporting duties?

If the MWC proceeds with the accelerated water source change despite the warnings, what ongoing monitoring or follow-up obligations do Engineer A and Engineer B have once construction and evaluation begin concurrently with the source change?

Should Engineer A consider resignation or removal from the project if the MWC continues to disregard the recommendation to delay the water source change despite the identified lead-leaching risk?

How should Public Welfare Paramount in Water Source Change be balanced against Transparency in Advising MWC of Project Failure, given that publicly disclosing the project's likely failure could alarm the public or undermine confidence in the MWC before regulatory authorities can act?

Does Public Welfare in Water Source Change conflict with the engineers' confidentiality obligations to the MWC, given that reporting concerns to the state regulatory agency may require revealing facts or data about MWC operations without the client's consent?

How should Public Welfare Paramount in Water Source Change be weighed against the MWC's institutional authority as governing decision body to approve infrastructure changes despite the engineers' explicit recommendation to delay?

From a deontological perspective, did Engineer A and Engineer B fulfill their duty under Code provision II.1.a to notify appropriate authorities once their professional judgment recommending delay was overruled under circumstances that could endanger public health?

Did the MWC's decision to proceed simultaneously with the accelerated water source change and treatment improvements produce outcomes (cost savings versus lead-contamination risk) that could consequentially justify overriding the engineers' recommended delay?

Did Engineer A act with professional integrity, as a virtuous engineer would, by continuing in the role of chief engineer for the MWC after the Commission overruled the joint recommendation to delay the source change despite known public health risks?

Would a purely consequentialist calculation of reputational and financial harm to Engineer A and Engineer B from reporting the MWC to the state regulatory agency outweigh the public health benefit of that disclosure, and does the Board's conclusion reject such a calculation?

If the MWC meeting at which the engineers recommended delay had been well-attended by the public and press rather than sparsely attended, would the Board still conclude that Engineers A and B have an independent obligation to notify the state regulatory agency, or would public awareness satisfy their disclosure duty?

If Engineer B's report had found that the existing service pipes posed no corrosion or lead-leaching risk under the accelerated timeline, would the Board still find that Engineers A and B had a duty to report to the state regulatory agency that the project endangers public health?

If the MWC had voted to accept the engineers' recommendation and delay the water source change rather than overriding it, would the Board still hold that Engineers A and B were obligated to formally report their concerns to the state regulatory agency?

If Engineer B had been a salaried MWC employee rather than an independent consulting engineer, would the Board still find that each engineer bears a separate, independent obligation to report concerns to the state regulatory agency rather than a single shared obligation?

Retaining the consultant set in motion the entire causal chain, since without this action there would be no consulting report, no joint delay recommendation, and no subsequent override, making it the unattributed but pivotal origin point of the ethical conflict.

The Commission's override vote directly overruled the engineers' considered judgment and caused the emergence of a public health danger, so even though it carries no explicit fulfills or violates tag, its downstream effects show it disregarded the paramount safety principle the engineers had upheld.

The consulting report submission fulfilled the duty to hold public safety paramount because it honestly conveyed risk information that then became the basis for the engineers' joint delay recommendation, showing that responsible technical reporting properly triggered the next protective step.

The joint delay recommendation fulfilled both the paramount safety duty and the duty to notify the client of endangerment, and its causal role in prompting the Commission's override vote shows that even a proper, duty-fulfilling warning could be causally followed by an improper managerial decision.

The regulatory agency notification, guided by the paramount safety principle, was the engineers' causal response to having their judgment overruled, showing that when internal channels failed to prevent danger, external notification became the necessary mechanism to still protect the public.

The question emerged because MWC's governing body overrode the engineers' technical recommendation on a public health risk, leaving unresolved how far each engineer's ethical obligation extends beyond formal advisement when their employer or client rejects their counsel.

The question of what Engineer A and Engineer B should do next emerged because MWC's governing body rejected their professional recommendation to delay the water source change despite identified public health risks, leaving unresolved whether their ethical obligations require further disclosure or action beyond their initial advisory role.

The question arises because Engineer A occupies two roles, employee and licensed professional, whose obligations were not in conflict until the MWC formally rejected the engineering judgment on a matter that endangers public health, forcing a choice between institutional loyalty and independent professional duty.

The question arises because low public attendance at a meeting deciding a public health risk creates a gap between the engineers' narrow reporting duty to MWC and the broader principle that public welfare decisions require informed public participation.

The question arises because the engineers' initial duty to warn was discharged through the Joint Delay Recommendation, but the MWC's override creates ambiguity about whether that duty transforms into a continuing obligation to monitor a project they no longer control.

The question arises because the engineer's technical judgment was overruled by a governing body on a matter with public health implications, creating a conflict between loyalty to the employer and the paramount duty to protect the public that only escalated action might resolve.

This question arose because Engineer A's duty to hold public welfare paramount collides with a duty to protect the MWC's institutional standing and avoid premature alarm, and the sparse public attendance and informal agency contact leave it unclear whether existing disclosure steps satisfy the paramount welfare obligation.

The question arises because the MWC's decision to override the engineers' safety-based recommendation forces a choice between two legitimate but conflicting NSPE obligations, namely protecting public welfare through regulatory disclosure and preserving client confidentiality.

The question arises because two legitimate authority structures collided: the engineers' technical judgment grounded in public safety duty, and the MWC's institutional right to make final infrastructure decisions, leaving unresolved whose authority should prevail when they conflict.

The question arises because the engineers' recommendation was overruled in a matter touching public health, and Code provision II.1.a demands notification of authorities, yet the engineers only made informal contact, leaving unresolved whether that action meets the deontological threshold of duty fulfillment.

This question arises because the MWC's override of the joint engineering recommendation created a gap between engineering judgment grounded in public safety and a governing body's authority to make final resource allocation decisions, leaving unresolved whether outcomes alone can retroactively validate a process that bypassed safety-first warrants.

The question arises because the data shows a clear conflict between the engineers' professional judgment and the Commission's authority, leaving unresolved whether continued service after being overruled reflects complicity or responsible stewardship under uncertain regulatory and public engagement conditions.

The question arises because the case data shows engineers facing real personal costs from reporting, prompting scrutiny of whether the Board's ethical conclusion implicitly rejects a strict cost benefit trade off in favor of an absolute paramountcy principle.

The question arises because Toulmin's warrant linking disclosure to public safety is ambiguous about whether procedural notice (holding a public meeting) or substantive notice (actual public awareness) is the operative standard, and the sparse attendance exposes this gap by making the two readings diverge in practical effect.

This question arose because the original case ties the duty to notify the regulatory agency to a belief that the accelerated timeline endangered public health, and altering the factual basis for that belief (Engineer B Water Treatment Report finding no risk) exposes an unresolved ambiguity in whether the NSPE Code duty is outcome-based or judgment-based.

The question arises because the case ties the engineers' regulatory notification duty to the specific fact pattern of being overruled, leaving unclear whether that duty is contingent on institutional rejection of safety advice or is an independent obligation flowing directly from awareness of public risk.

The question arises because the Board's finding of separate independent obligations was reached under a specific employment configuration (chief engineer versus consulting engineer), and altering that configuration tests whether the warrant for independent reporting is grounded in individual professional identity or in organizational role and status.

Given that Engineers A and B jointly believed the accelerated project would fail and that this belief had not yet been formally communicated, the board concluded that III.1.b required them to advise the MWC directly and in terms that included their doubt about success, prior to any external escalation.

Given that Engineer B's report identified a lead-leaching risk and the MWC overruled the joint delay recommendation, the board concluded that II.1 and II.1.a impose an independent, non-waivable duty on each engineer to report both to the MWC and to the state regulatory agency, regardless of the client's wishes.

Given that the lead-leaching risk implicated public health directly, the board concluded that II.1.c's confidentiality duty must yield to II.1 and II.1.a, so reporting to the state agency is treated as an application of the Code's internal hierarchy rather than a breach of client confidence.

Given that both Engineer A and Engineer B are licensed PEs who independently evaluated the same lead-leaching risk, the board concluded that their differing employment relationships with MWC do not create differing duties, since licensure rather than contract status is the source of the obligation.

Given that the MWC exercised its governance authority to overrule the delay recommendation despite the identified lead-leaching risk, the board concluded that this institutional authority does not extend to suppressing the engineers' independent duty to report public health risks externally.

Given that only a few members of the public attended the MWC meeting where the delay recommendation was overridden, the Board concluded that this sparse attendance could not be treated as a substitute for formal regulatory notification, because the engineers' duty runs to a competent authority, not to whatever segment of the public happens to be present.

Because the engineers first raised their concerns internally through the joint recommendation and the MWC then voted to override that recommendation, the Board reasoned that this override is precisely the event converting the engineers' internal advisory obligation into a mandatory external notification duty to the state agency.

Since nothing in the facts shows that Engineer A's or Engineer B's ongoing roles prevent them from formally notifying the state agency, the Board concluded that resignation is not required and that the reporting duty can be fulfilled from within their existing positions.

Given that Engineer A, as an employee-PE, possessed the same overruled judgment and even greater insider knowledge of the accelerated timeline as consultant Engineer B, the Board concluded that II.1.a applies identically to both, so employment loyalty cannot excuse or lessen Engineer A's notification duty.

Because the Code's emphasis is on affirmative reporting rather than withdrawal from a position, the Board concluded that Engineer A may remain chief engineer for the MWC provided that role is not allowed to suppress the required notification to the state agency.

Given that a real lead-leaching risk and a belief that the project would fail both existed, the board concluded that advising the MWC and protecting public welfare pointed in the same direction, so any tension with public alarm or institutional confidence was resolved by the Code's built-in hierarchy favoring safety.

Because the lead-leaching risk was found credible, the board read the Code's own hierarchy as already resolving the apparent conflict, so disclosure to the regulator was not an exception needing special justification but a direct application of paramount welfare over confidentiality.

Because Engineers A and B stopped at an internal, sparsely attended verbal presentation to the MWC itself, the board concluded that the formal notification duty to appropriate authorities remained outstanding, since persuading the client is not equivalent to notifying a regulator.

Since remaining as chief engineer was consistent with continuing to press the concern through formal channels, the board concluded that persistence in advocacy, not exit from the role, was the true measure of virtue, and that quitting without ensuring notification would have been the greater failure.

Even supposing the meeting had been well attended by the public and press, the board reasoned that this would not satisfy the II.1.a duty, since informing citizens is not equivalent to notifying the regulatory authority empowered to act.

Because the board treated the II.1.a reporting duty as contingent on an actual public-health risk rather than on the mere fact of a water source change, it reasoned that a hypothetical no-risk finding by Engineer B would remove the predicate and the independent duty to report externally would not arise.

Since the board anchored the external reporting duty specifically to the act of the client overruling safety-driven engineering judgment, it concluded that had MWC accepted the delay recommendation instead, that triggering event would be absent and only the routine duty to advise the client would remain.

Because the board located the reporting duty in personal licensure rather than employment relationship, it concluded that even if Engineer B were a salaried MWC employee like Engineer A, both would still bear separate, non-vicarious reporting obligations.

Given that the engineers' recommendation was in fact overruled under circumstances the board found endangered public health, it read II.1.a as displacing the client-consent requirement of II.1.c, concluding that confidentiality is a suspendable default rather than a co-equal competing duty.

Because the engineers actually informed MWC of the project's likely failure before the MWC's override occurred, the board characterized III.1.b and II.1.a as a duty ladder, informing the client first and escalating to the regulator only once that internal warning was rejected, rather than as a forced choice between candor and public protection.

Given that the MWC exercised its lawful authority to override the engineers' joint recommendation despite the identified lead-leaching risk, the Board concluded that this institutional authority settles only the organizational decision, not the engineers' separate professional obligation to safeguard the public, which survives the override as an independent floor duty under II.1 and II.1.a.

Should Engineer A and Engineer B formally notify the state regulatory agency after the MWC Commission overrode their delay recommendation?

Should Engineers A and B formally communicate to the MWC their belief that the project will not be successful, even at the risk of public alarm?

Must Engineers A and B report the public health risk to the state regulatory agency even without, or against, the MWC's consent?

Should Engineer A resign or seek removal from the project rather than continue as chief engineer while the MWC disregards the delay recommendation?

Must Engineer A apply the same independent reporting duty as Engineer B despite being an MWC employee, rather than deferring to employment loyalty?