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 act for each employer or client as faithful agents or trustees.

Cited to establish that an engineer has an obligation to report likely public health/environmental risks to appropriate regulatory authorities, even after being dismissed by the client.

Cited to reinforce the principle that engineers must report known safety violations to appropriate authorities, even when discovered confidentially and outside their area of expertise.

Cited as the directly related prior case involving the same Engineer B and MWC facts, establishing that Engineer B had an ethical obligation to report the risk to the appropriate regulatory authority regardless of client consent; the current case confirms that this reporting obligation was fulfilled.

Clear reporting of unresolved public health and safety risks to “appropriate authorities” satisfies Engineer B’s obligation to protect public health, safety and welfare.

Any additional steps taken beyond the notification of appropriate authorities are not an obligation of Engineer B but rather a personal choice as a citizen, and should be taken with due consideration of the multiple stakeholders in this matter and the engineer’s many ethical obligations.

The Board's conclusion that notification to appropriate authorities satisfies Engineer B's obligation rests on an assumption that such notification is actually effective in prompting protective action. Here, the notification chain produced a materially adverse outcome for public health: the regulator approved the source change with a five-year delay before treatment, and an intervening consultant (XYZ) reported that risk severity could not be predicted, potentially undermining or diluting Engineer B's original warning. This suggests the adequacy of 'notifying appropriate authorities' as a discharge of duty may need to be assessed not merely by whether notification occurred, but by whether the notification was actually considered on its merits and not effectively countermanded by a subsequent, less rigorous analysis submitted to the same authority.

The Board's framing of further action as purely a 'personal choice as a citizen' understates the possibility that Engineer B's discharge from the project was itself a foreseeable consequence of complying with Code provision II.1.a., which requires notifying authorities when professional judgment on safety matters is overruled. If engineers can be terminated as a direct result of fulfilling this notification duty, the practical effect is to sever any professional, employer-linked framework through which further advocacy could occur, effectively forcing safety concerns to migrate from professional duty to personal citizenship regardless of the engineer's preference. This dynamic deserves explicit ethical scrutiny as a structural tension in how the Code protects (or fails to protect) engineers who comply with its own overruled-judgment provision.

The Board treats the faithful agent duty and the paramountcy of public welfare as compatible once notification occurs, but does not address how ABC Engineers' financial dependency on City M as a major client may have shaped the intensity, timing, or framing of Engineer B's original risk communications even before discharge. A fuller ethical analysis would examine whether the faithful agent duty to ABC Engineers, given this dependency, created pressure that could have tempered how forcefully the risk was initially presented to the MWC, independent of the question of what obligations exist after discharge.

The Board's second conclusion permits further action as a matter of personal conscience but does not resolve whether such action, if taken, could create new conflicts with the faithful agent duty Engineer B still owes to ABC Engineers as an ongoing employer, even though the MWC project itself has ended. Continued public advocacy or renewed correspondence with the regulatory agency could affect ABC Engineers' broader relationship with City M across other public works engagements, meaning Engineer B's 'personal choice as a citizen' is not ethically cost-free to the firm and should be weighed against ABC's other institutional interests, not just the public interest.

The discharge of Engineer B and ABC Engineers immediately after Engineer B raised safety concerns at a public meeting and in writing raises a distinct ethical concern about retaliation against engineers who fulfill their duty to hold public safety paramount. While the Board's conclusions focus on whether Engineer B's reporting duty was satisfied, they do not address whether MWC's termination decision itself was an improper response that could discourage future engineers from candidly disclosing public health risks, which is a matter separate from, but related to, Engineer B's own obligations under Section II.1.

XYZ Consultants' conclusion that insufficient information existed to predict the severity of the risk does not automatically negate Engineer B's prior clearly documented findings; rather, it creates a professional obligation for XYZ to engage with and reconcile the discrepancy with the existing record before advising the Water Commission, since silently superseding a predecessor's safety findings without addressing them risks undermining the reliability of public safety determinations relied upon by regulators and the public.

ABC Engineers' substantial financial dependence on City M as a client, spanning multiple public works relationships beyond the MWC project, plausibly created an institutional conflict of interest that could have constrained how forcefully Engineer B was able or expected to advocate for public safety, independent of Engineer B's personal ethical commitment. This dependency does not excuse a diminished disclosure but is relevant context for understanding the pressures surrounding Engineer B's decision-making and eventual discharge.

Once Engineer B was discharged from the project, the faithful agent duty owed to ABC Engineers and, through it, to the MWC as client effectively terminated with respect to that specific engagement. Any further action Engineer B might take afterward is therefore not constrained by an ongoing agency relationship, which supports the Board's characterization of continued advocacy as a matter of personal conscience rather than a residual professional duty in conflict with agency obligations.

From a deontological standpoint centered on Section II.1.a., Engineer B's duty was procedural and was discharged in full once the risk was clearly reported through the proper channels: the public meeting disclosure, the written letter to the Water Commissioners, and the subsequent report to the State Department of the Environment. The persistence of the underlying risk after regulatory approval of a phased treatment plan does not reopen this discharged duty, because the duty as codified is one of notification to appropriate authorities, not one of guaranteeing a particular outcome.

From a consequentialist perspective, Engineer B's escalation to the regulatory agency plausibly improved public health outcomes relative to silence, since it produced a documented five-year phase-in of corrective water treatment rather than an indefinite delay with no oversight commitment. However, the outcome remains only a partial mitigation of the identified lead exposure risk during the interim period, so the consequentialist assessment of Engineer B's actions is one of harm reduction rather than harm elimination.

Viewed through a virtue-ethics lens, Engineer B's persistence across multiple escalating channels of disclosure, public meeting remarks, a formal letter, and a regulatory report despite facing professional and financial risk from a major client relationship, reflects the character trait of professional integrity and courage that the Code implicitly seeks to cultivate, independent of whether a further formal obligation existed.

Had Engineer B never sent the original report and letter to the State Department of the Environment's water supply division, the Board would likely not conclude that the reporting obligation had been satisfied, since disclosure to the Water Commissioners alone would leave the overruling client as the sole recipient of the safety warning, without escalation to an external appropriate authority as contemplated by Section II.1.a. The regulatory notification is the critical act that completes the discharge of duty.

If MWC had not discharged Engineer B and ABC Engineers from the project, the Board's characterization of further advocacy as purely a personal choice would likely still hold, provided the initial notification obligations had already been met, because the faithful agent duty under Section II.4. does not extend to overriding a client's business decision once the safety risk has been properly disclosed to appropriate authorities. Continued employment would not, by itself, convert further advocacy into a professional obligation rather than a personal one.

Had XYZ Consultants confirmed rather than contradicted the severity of the lead-contamination risk, the Board's conclusion that Engineer B's reporting obligation was already satisfied would remain unchanged, since that obligation rests on what Engineer B disclosed and to whom at the time, not on how subsequent consultants characterized the risk. However, such confirmation would have strengthened the case for regulatory intervention and may have reduced the ambiguity that allowed the phased five-year approval to proceed.

The Board resolves the tension between 'public welfare paramount' (II.1) and 'faithful agent' duty (II.4) not by weighing them against each other in substance, but by treating II.1.a's notification requirement as a procedural bright-line that discharges the paramountcy obligation entirely. Once Engineer B reported the unresolved risk to the Water Commissioners and the State regulator, the faithful agent duty to ABC Engineers (and its dependency on City M as a client) no longer needed to be balanced against public welfare, because the public welfare obligation itself was treated as satisfied. This shows that in NSPE's framework, 'paramount' does not mean 'overriding without limit' but rather 'triggering a specific, boundable disclosure obligation' that can be fully satisfied even while the underlying danger persists.

The case reveals an asymmetry in how the two competing principles are temporally bounded: the faithful agent duty (II.4) is explicitly terminated by an external event (MWC's discharge of Engineer B and ABC Engineers), while the public welfare paramountcy principle (II.1) has no analogous termination point tied to employment status. Rather than allowing public welfare's open-endedness to generate a continuing professional obligation after discharge, the Board re-classifies any further action as personal conscience rather than professional duty. This effectively imports the faithful agent principle's termination logic into the public welfare principle by the back door, capping the professional obligation at the same point the client relationship ends, even though the hazard to public health continues independently of the engineer's employment status.

By locating the resolution of the public-welfare/faithful-agent tension in procedural disclosure (reporting to appropriate authorities) rather than in verified outcomes (actual mitigation of the lead risk), the Board implicitly prioritizes a deontological reading of II.1 over a consequentialist one. The five-year phase-in approved by the regulator, and XYZ Consultants' contradictory finding of 'insufficient information,' demonstrate that the underlying risk to public health was not resolved by Engineer B's reporting -- yet the Board still treats the paramountcy obligation as fulfilled. This suggests that in NSPE's institutional ethics, principle prioritization is determined by the completion of a professional duty-act (disclosure to competent authority) rather than by whether the paramount value (public safety) is actually secured in fact.

Engineer B ethically obligated to take further action to protect public health, safety and welfare?

If Engineer B wishes to take further action to continue to correspond with the MWC or the regulatory agency regarding the public health and safety risk, or to notify the public, what are the ethical considerations in doing so?

Did MWC's decision to discharge Engineer B and ABC Engineers after Engineer B raised safety concerns constitute retaliation, and does this raise a separate ethical issue about protecting engineers who report public health risks?

Does XYZ Consultants' report, which claimed insufficient information existed to predict risk severity, create an ethical obligation for XYZ to reconcile its conclusions with Engineer B's clearly documented risk findings before advising the MWC?

Does the State Department of the Environment's approval of the water source change with a five-year treatment implementation plan discharge all downstream public safety concerns, or does it leave an unresolved risk during the interim period that engineers should still consider?

Given ABC Engineers' significant financial dependency on City M as a client, did this dependency create a conflict of interest that could have influenced how forcefully Engineer B was permitted or expected to advocate for public safety?

How should Engineer B balance the duty to hold public welfare paramount against the faithful agent duty owed to ABC Engineers, given ABC's business dependency on City M as a client?

Is taking further action beyond regulatory notification actually required by the principle of public welfare being paramount, or is it correctly categorized as merely a matter of personal conscience?

Does the faithful agent duty Engineer B owes to ABC Engineers as an employer conflict with Engineer B's personal conscience-driven desire, as a citizen of City M, to continue pressing the issue after being discharged from the project?

How should the obligation to hold public welfare paramount in the water source change be weighed against the code's provision that engineers whose judgment is overruled should notify authorities, once that notification has already occurred but the underlying risk remains unresolved?

From a deontological perspective, did Engineer B fully discharge the duty to protect public health, safety, and welfare once the risk was reported to the Water Commissioners and the State Department of the Environment, regardless of whether corrective action followed?

From a consequentialist perspective, given that the state regulator ultimately approved a five-year phase-in of treatment despite the known lead risk, did Engineer B's escalation to the regulatory agency actually produce a better public health outcome than remaining silent after discharge would have?

Did Engineer B act with professional integrity, in the virtue-ethical sense, by continuing to raise the lead-risk concern through successive channels (public meeting, written letter, regulatory report) even after being discharged by a major client?

If Engineer B had never sent the original report and letter to the State Department of the Environment's water supply division, would the Board still conclude that Engineer B's obligation to protect public health and safety had been satisfied?

If the Metropolitan Water Commission had not discharged Engineer B and ABC Engineers from the project, would the Board still characterize any further advocacy by Engineer B as a purely personal choice as a citizen rather than as part of a continuing professional obligation?

If XYZ Consultants had instead confirmed the severity of the lead-contamination risk rather than reporting insufficient information to predict it, would the Board's conclusion that Engineer B's reporting obligation was already fulfilled still stand without requiring further action?

Although no fulfills or violates edge is recorded for the Risk Deferral Decision, it is the causal origin of both the Public Health Risk Onset and Engineer B's subsequent Public Meeting Disclosure, so its normative weight lies in triggering the safety concern that the rest of the case is organized around resolving.

The Engineer Discharge carries no direct normative label itself, but because it is MWC's causal response to Engineer B's Regulatory Escalation and in turn produces both the Engagement Termination and the Consultant Risk Report, it functions as the point where the employer's reaction to a safety escalation removes the very oversight that raised the concern.

The Consultant Risk Report has no normative edges of its own, yet since it is generated only after Engineer Discharge and stands as the retained record of the risk assessment, its significance is evidentiary, shaping whether the underlying public health concern is later validated or dismissed.

Regulatory Approval lacks explicit fulfill or violate designation, but because it follows directly from Engineer B's Regulatory Escalation and its later Approval Discovery reopens the ethical question for Engineer B, it matters as the fact that ultimately reactivates the safety versus loyalty tension the case turns on.

Further Action Deliberation is explicitly guided by the Paramount Duty to Public Health and Safety and the Faithful Agent Obligation to Employer, and because it arises only after Approval Discovery reveals that regulatory sign-off occurred despite the unresolved risk, this deliberation is where Engineer B must weigh continuing loyalty to a former employer against the deeper duty to protect the public from the risk set in motion since the original Risk Deferral Decision.

Advisory Recommendation fulfills Engineer B's obligation to warn the client of risk, but because MWC's downstream Risk Deferral Decision ignored that warning and led to Public Health Risk Onset, the action's normative weight lies in discharging the engineer's duty while exposing that fulfillment alone cannot prevent harm once responsibility passes to a non-compliant client.

Public Meeting Disclosure carries no formal fulfillment or violation label but is guided by the paramount duty to public safety, and its causal role in prompting the more formal Written Risk Notification shows it functioning as an escalating good-faith step taken after the client's deferral failed to address the danger.

Written Risk Notification fulfills the obligation to report risks to the client and, by creating a documented record, causally enables the subsequent Regulatory Escalation, making it the evidentiary bridge between private disclosure and formal external action once informal warnings proved insufficient.

Regulatory Escalation fulfills the obligation to report risks to appropriate authorities under the paramount safety duty, and its causal chain into both Engineer Discharge and Regulatory Approval shows that honoring this obligation triggered professional retaliation from MWC while simultaneously validating the engineer's judgment through official confirmation of the risk.

The question arises because Engineer B fulfilled his formal reporting obligations before losing his role, yet the underlying public health risk remained unresolved, creating ambiguity about whether his professional duty extends beyond employment and reporting into ongoing personal responsibility.

The question arises because the formal reporting chain (report to client, notify regulator) has been completed and approved, yet Engineer B's personal knowledge of an unresolved public health risk creates tension between his discharged professional role and his ongoing duty and right as an individual engineer or citizen to act further.

The question emerged because the temporal proximity between Engineer B's lead risk finding and the subsequent discharge suggests possible retaliation, prompting scrutiny of whether professional protections for public health reporting were violated.

The question arises because two professional reports reached seemingly incompatible conclusions about the same public health risk, and it is unclear whether the paramount duty to public welfare requires XYZ to actively reconcile this discrepancy or whether its duty is discharged simply by reporting within its own engagement's terms.

The question arises because a regulatory approval event and an engineering risk finding point in different directions, one toward institutional closure and the other toward continued professional responsibility, leaving it unclear whether formal approval overrides substantive risk during the phase in period.

The question arises because the structural financial dependency between ABC Engineers and City M creates a plausible but unproven link between economic incentive and the forcefulness of safety advocacy, making it unclear which warrant actually governed Engineer B's conduct.

The question emerged because Engineer B's professional relationship to ABC and ABC's economic dependence on City M created institutional pressure that could conflict with the unresolved lead risk finding, forcing a choice between organizational loyalty and independent public protection.

The question arose because Engineer B's formal obligations ended with regulatory reporting and termination from the project, yet the unresolved public health risk leaves ambiguous whether professional duty extends further or whether continued involvement is now a matter of individual ethical choice rather than codified obligation.

The question arises because discharge from ABC Engineers severs the employment tie that grounds the faithful agent duty, leaving open whether Engineer B's continuing personal concern about public safety can or should override that now-terminated obligation.

This question arose because the NSPE Code offers two plausible stopping points, formal notification versus resolved risk, and the persistence of Lead Exposure Risk in City M after Engineer B State Reporting Duty was fulfilled exposes the ambiguity between procedural compliance and substantive outcome responsibility.

The question arises because reporting to authorities and inaction on the risk both occurred, creating a gap between procedural compliance and substantive protection of public welfare that a strict deontological reading must resolve.

The question arises because the facts create a gap between the deontic justification for escalation, which required reporting regardless of result, and an empirical uncertainty about whether that reporting causally changed the regulatory outcome, since the same lead risk exposure was ultimately approved anyway.

The question arises because the sequence of discharge followed by repeated disclosure actions blurs the line between duty-bound reporting and voluntary virtuous conduct, leaving open whether Engineer B's persistence reflects professional integrity or oversteps the bounds of a terminated engagement.

The question arises because the Board's conditional fulfillment finding seems to hinge on the specific act of state notification, so asking what would happen absent that act tests whether the ethical conclusion was about the action performed or the underlying obligation it represented.

The question arises because the discharge event severs the formal employer-client relationship (Engineer B Employment With ABC, ABC Post Discharge Phase) that normally anchors the faithful agent warrant, forcing the Board to decide whether the paramount public safety warrant can operate independently of that relationship or whether it collapses into mere personal conscience once the professional bond ends.

The question emerges because the Board's finding of fulfilled obligation was contingent on XYZ's inconclusive risk assessment, and altering that data point tests whether the warrant justifying 'no further action' still holds once the severity of harm becomes certain rather than speculative.

Given that Engineer B documented the risk in writing and escalated it to both the client body and the state regulator before being overruled and discharged, the Board concluded that this act of clear notification itself satisfies the duty to hold public safety paramount, treating the duty as procedural (an act of disclosure) rather than outcome-contingent.

Given that Engineer B had already notified appropriate authorities and had been discharged from the project, the Board reasoned that any further correspondence, public notification, or continued pressing of the issue falls outside the bounds of professional obligation and instead becomes a discretionary act of citizenship, to be weighed against competing duties such as confidentiality and stakeholder interests.

Because the five-year delayed approval and XYZ's inconclusive report followed Engineer B's warning and reached the same regulator, the reasoning suggests the Board's assumption that notification alone discharges the duty needs qualification: adequacy should also depend on whether the notification was substantively considered rather than effectively neutralized by a later, weaker analysis.

Given that Engineer B's discharge closely followed the exercise of the Code-mandated duty to notify authorities when overruled, the analysis suggests the Board's characterization of further action as 'personal choice' understates how termination itself may be a foreseeable structural consequence of following the Code, effectively forcing the issue into the citizen domain regardless of the engineer's preference.

Because ABC Engineers' dependence on City M as a client existed at the time Engineer B first raised the lead-risk concern, the analysis suggests the Board should have examined whether this dependency shaped how forcefully or promptly the risk was initially communicated, rather than treating the faithful agent duty and public welfare paramountcy as automatically compatible once notification occurred.

Given that the MWC engagement ended but Engineer B's employment with ABC continued, and ABC still depends on City M for other work, the board recognized that its own characterization of further advocacy as cost-free personal conscience leaves an unresolved tension with Engineer B's ongoing obligations to ABC as employer.

Given that the discharge followed directly on Engineer B's public and written safety disclosures, the board recognized a distinct retaliation concern that its own conclusions about Engineer B's reporting duty do not resolve.

Given that Engineer B's findings were clearly documented and XYZ's later report reached a different conclusion without addressing them, the board concluded that XYZ bears an obligation to reconcile the discrepancy before the Water Commission relies on it.

Given ABC's broad financial reliance on City M across several projects, the board found this dependency a plausible source of institutional pressure on Engineer B's advocacy, while still holding that it cannot excuse any lessening of the public safety disclosure duty.

Given that Engineer B's faithful agent duty was tied specifically to the MWC engagement, and that engagement ended with the discharge, the board concluded that further advocacy afterward is no longer constrained by an agency obligation and can be treated as personal conscience.

Given that Engineer B disclosed the lead risk through three escalating channels culminating in a report to the state regulator, the board concluded the deontological notification duty under II.1.a. was fully discharged, because that duty is defined by the act of reporting to appropriate authorities rather than by achieving a particular remedial outcome.

Given that Engineer B's regulatory report is credited with prompting a five-year treatment phase-in rather than indefinite inaction, the board concluded the escalation was consequentially beneficial as harm reduction, while still recognizing that the interim lead exposure risk remained only partially mitigated.

Given that Engineer B kept escalating the lead-risk warning through successive channels even after losing a major client relationship, the board concluded this pattern exemplifies the professional integrity and courage the Code seeks to cultivate, independent of any further formal obligation.

Given that disclosure limited to the Water Commissioners would leave the overruling client as the only party aware of the risk, the board concluded that without the report to the State Department of the Environment, it would not find the II.1.a. reporting obligation satisfied.

Given that Engineer B had already completed the required notifications before any hypothetical continued employment, the board concluded that even without discharge, further advocacy would remain a personal choice rather than a professional duty, since the faithful agent obligation does not compel overriding a client's decision once safety has been properly reported.

Given that Engineer B's disclosure to the Water Commissioners and State regulator occurred before XYZ Consultants' report existed, the Board reasoned that a later confirmation by XYZ would not retroactively change whether that earlier disclosure satisfied the reporting duty, even though such confirmation might have prompted stronger regulatory action.

Given that Engineer B's judgment was overruled and Engineer B then notified the Water Commissioners and the State regulator, the Board concluded that this act of notification discharged the paramountcy obligation in full, removing any need to further weigh it against the faithful agent duty to ABC Engineers despite ABC's dependency on City M.

Given that MWC discharged Engineer B and ABC Engineers, the Board treated the faithful agent duty as ended by that event and, rather than letting public welfare's open ended nature generate a continuing professional obligation, classified any further action by Engineer B as personal conscience tied to citizenship in City M.

Given that the five year phase in and XYZ's contradictory finding show the lead risk was not actually resolved, yet Engineer B had already reported it to the Water Commissioners and State regulator, the Board still treated the paramountcy obligation as satisfied, revealing that its institutional test for principle priority is the completion of a disclosure act rather than confirmed real world safety.

Should Engineer B clearly disclose the lead exposure risk to the Water Commissioners and, once overruled, escalate to the state regulator, or withhold or soften the disclosure out of deference to the client relationship?

Should Engineer B pursue further advocacy on the lead risk only as a personal citizen with ABC Engineers' full knowledge and concurrence, or continue pressing the issue independently as an ongoing professional obligation?

Should Engineer B communicate the full severity of the lead risk to MWC regardless of ABC's business dependency on City M, or moderate the communication to help preserve the client relationship?

Should Engineer B proactively reassess and clarify the earlier verbal and written risk reports in light of XYZ Consultants' differing characterization, or rely on the original documentation as sufficiently clear?

Should Engineer B escalate the documented lead risk to the state water supply division after being discharged from the project, or refrain from further reporting since the client engagement had ended?