Step 4: Review

Hold paramount the safety, health, and welfare of the public.

Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.

Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required.

Engineers shall at all times strive to serve the public interest.

Cited as an early example exploring the scope of engineers' obligation to public health and safety, establishing that engineers may ethically refuse to participate in work they believe unsafe, even at risk of job loss.

Cited to illustrate that an engineer who reports concerns internally has no further ethical obligation to continue pushing the issue or report externally, but may do so as a matter of personal conscience; also distinguished as not involving public safety.

Cited as a case where the engineer failed her ethical obligations by not reporting a known ongoing legal violation to proper (state) authorities, distinguished from the present case because the safety issue there was within the engineer's professional scope of responsibility.

Engineer A should bring this potential safety issue to the attention of Engineer A’s supervisor and ES Consulting. The Board assumes that the potential safety issues do not pose an imminent danger; therefore, Engineer A does not have an obligation to report this issue beyond his superiors in ES Consulting.

The Board's conclusion rests on an unexamined assumption that the potential safety issues do not pose imminent danger, but the Board does not specify who is qualified to make that determination or what criteria should apply. Because Engineer A has no direct involvement with the subcontractor's work and only incidental visual observation from an adjacent site, his ability to accurately assess the severity or imminence of the risk is inherently limited. This raises a question of whether ES Consulting, upon internal notification, bears responsibility for further investigating the severity of the hazard rather than relying on Engineer A's initial threshold judgment alone.

The Board's finding that Engineer A's obligation is bounded to internal notification leaves unresolved what happens if ES Consulting, after being informed, elects to take no further action. The Board's reasoning implicitly treats internal notification as a complete discharge of Engineer A's ethical duty, but this does not address the scenario where the firm's inaction leaves a genuine safety risk unaddressed for a third party who has no relationship with ES Consulting or Client X and therefore no independent means of learning about the hazard.

The Board's conclusion frames Engineer A's duty narrowly by reference to the absence of a contractual relationship with Owner Y and the subcontractor, effectively treating Bounded Responsibility for Adjacent Hazard as controlling over the more expansive language of holding public safety paramount. This reflects an implicit prioritization of professional and organizational boundaries over the broader public welfare language in the Code, a tension the Board does not explicitly reconcile beyond asserting that no imminent danger exists.

Regarding Q101, the determination of whether an observed hazard constitutes 'imminent danger' cannot rest solely on Engineer A's individual assessment, given his lack of direct involvement with the subcontractor's operations. The appropriate criteria should draw on general engineering safety standards (e.g., severity of potential injury, likelihood of occurrence, and time-sensitivity of the hazard) rather than site-specific technical authority Engineer A does not possess. Because Engineer A's vantage point is incidental and external, his judgment should be treated as a preliminary flag requiring confirmation and escalation through ES Consulting's supervisory chain, rather than a final determination.

Regarding Q103, although Engineer A has no contractual privity with Owner Y or the subcontractor, the Code's paramount public safety obligation under I.1. is not limited by contractual boundaries. This creates a moral (though not contractual) duty to ensure that a genuinely observed hazard is communicated to someone capable of acting on it—here, satisfied by notifying ES Consulting and the supervisor—rather than a direct duty of warning owed personally by Engineer A to Owner Y or the subcontractor's workers.

Regarding Q104, the construction observation engagement with Client X does not implicitly extend to monitoring adjacent properties; Engineer A's awareness of the adjacent hazard is best characterized as incidental knowledge acquired during, but not part of, the scope of services. Nonetheless, once such knowledge is acquired, the paramountcy duty under I.1. attaches independently of the engagement's contractual scope, obligating Engineer A to act on what he has learned even though he was never tasked with observing it.

Regarding Q201, the tension between Public Safety in Adjacent Project Observation and Bounded Responsibility for Adjacent Hazard is real but not irreconcilable: the Board's resolution channels the public safety duty through an internal reporting mechanism rather than direct external action, allowing Engineer A to discharge his paramount safety obligation without assuming a legal or professional responsibility for a project outside his engagement. This approach treats the duty as one of diligent internal escalation rather than independent external intervention.

Regarding Q202, Engineer A's Personal Judgment Response Option should not operate as an unchecked individual determination given the paramount nature of the public safety duty; rather, it functions as an initial triggering judgment that must be validated by ES Consulting's supervisory review. This balances individual professional autonomy against the risk that a single engineer's threshold assessment could either overreact beyond his authority or underreact and leave a genuine hazard unaddressed.

Regarding Q203, limiting Engineer A's obligation to internal notification risks under-protecting public safety only if ES Consulting fails to follow up or verify whether the hazard is addressed. The Unreasonable Duty Imposition Limit justifiably prevents imposing an open-ended external reporting duty on Engineer A personally, but this bounded responsibility is ethically sound only if paired with an implicit expectation that ES Consulting will take the notification seriously and monitor the situation, rather than treating the notification as a terminal act.

Regarding Q301, from a deontological standpoint, Engineer A's duty to hold paramount the safety, health, and welfare of the public is a categorical duty attaching to the individual regardless of contractual relationships. Strictly applied, this duty would seem to require more than internal notification if the hazard were serious. The Board's conclusion effectively narrows the categorical force of this duty by conditioning broader action on an 'imminent danger' threshold, which is a pragmatic limitation not fully derivable from a pure deontological reading of I.1.

Regarding Q302, a consequentialist analysis raises concern that internal notification alone may not produce a sufficient outcome, since ES Consulting has no established relationship with Owner Y or the subcontractor and may take no further action. The ethical sufficiency of Engineer A's response therefore depends heavily on whether ES Consulting follows through, meaning the outcome-based justification for the Board's conclusion is contingent rather than guaranteed.

Regarding Q303, Engineer A's voluntary recognition and reporting of a hazard entirely outside the scope of his engagement reflects the exercise of professional virtue—specifically vigilance, integrity, and civic-mindedness—that exceeds the minimal requirements of his contract with Client X, even though the Board frames his ultimate obligation narrowly.

Regarding Q401, had the observed hazard posed imminent danger, the Board's own reasoning implies that Engineer A's obligation would extend beyond internal notification, invoking II.1.f.'s duty to report Code violations to appropriate authorities and I.1.'s paramountcy duty, thereby requiring escalation to external authorities such as safety regulators rather than remaining confined to ES Consulting.

Regarding Q402, if Client X had a direct contractual or business relationship with Owner Y, this would not necessarily broaden Engineer A's personal ethical obligation but would create a more direct organizational channel—via Client X—for the hazard information to reach Owner Y. Engineer A's individual duty would likely remain the same (notify supervisor and ES Consulting), while the practical effectiveness of that notification in reaching Owner Y would improve due to the pre-existing relationship.

The Board resolves the apparent tension between Public Safety in Adjacent Project Observation and Bounded Responsibility for Adjacent Hazard not by ranking one principle categorically above the other, but by making the resolution conditional on severity: where no imminent danger is present, Bounded Responsibility for Adjacent Hazard controls and internal notification suffices, but the case's framing implies that if imminent danger were present, Public Safety in Adjacent Project Observation would override the boundedness of the engagement and demand broader action. This shows the two principles are not truly in conflict but operate on a sliding scale calibrated to risk severity, with Engineer A's lack of direct relationship to Owner Y or the subcontractor limiting the mode of discharge (internal escalation) rather than eliminating the underlying safety duty.

Personal Judgment Response Option is subordinated to Public Safety in Adjacent Project Observation as a matter of process rather than substance: Engineer A's individual assessment of severity is not treated as the final word, but as a threshold trigger for escalation. The Board's reliance on ES Consulting as the appropriate next-level decision-maker suggests that personal judgment is meant to operate only at the initial recognition stage, after which institutional judgment (the firm's) takes over responsibility for calibrating the response, thereby diffusing the risk of an individual engineer either under- or over-reacting to ambiguous adjacent-site hazards.

Bounded Responsibility for Adjacent Hazard and the Unreasonable Duty Imposition Limit work together to prevent the paramountcy of public safety from being read as an unlimited roving duty to police all hazards an engineer might incidentally observe outside the scope of engagement. This case teaches that principle prioritization in NSPE ethics is not simply hierarchical (safety always trumps all) but scope-sensitive: the paramount safety duty is satisfied through proportionate action (internal escalation) rather than maximal action (external reporting), unless a severity threshold (imminent danger) is crossed, at which point the Unreasonable Duty Imposition Limit no longer shields the engineer from broader reporting obligations under II.1.f.

What are Engineer A’s ethical obligations under the circumstances?

Who determines whether the observed safety issue on the adjacent project rises to the level of 'imminent danger,' and what criteria should guide that judgment given Engineer A lacks direct involvement with the subcontractor's work?

What should Engineer A or ES Consulting do if, after internal notification, the firm decides to take no further action on a potential safety issue affecting a third party like Owner Y or the subcontractor's workers?

Does Engineer A owe any direct duty of care or warning to Owner Y or the subcontractor's workers, despite having no contractual relationship with them, given that the observation occurred incidentally during work for Client X?

Should the scope of construction observation services performed for Client X be understood to implicitly include a duty to notice and act on hazards visible on neighboring sites, or is this purely incidental knowledge outside the engagement's scope?

Does the principle of Public Safety in Adjacent Project Observation conflict with Bounded Responsibility for Adjacent Hazard, given that Engineer A has no direct relationship with Owner Y or the subcontractor yet has observed a genuine safety risk?

How should Personal Judgment Response Option be balanced against the paramount duty expressed in Public Safety in Adjacent Project Observation, when Engineer A alone must assess whether a hazard is serious enough to escalate beyond internal reporting?

Is Bounded Responsibility for Adjacent Hazard consistent with the Unreasonable Duty Imposition Limit, or does limiting Engineer A's obligation to internal notification risk under-protecting public safety when no imminent danger threshold is clearly met?

From a deontological perspective, did Engineer A fulfill the duty to hold paramount the safety, health, and welfare of the public by limiting escalation to his supervisor and ES Consulting, even though the hazard involved a party outside his firm's direct engagement?

From a consequentialist perspective, does internal notification to ES Consulting alone produce an ethically sufficient outcome for public safety, given that the subcontractor and Owner Y have no direct relationship with Engineer A's firm and may never learn of the observed hazard?

Did Engineer A act with professional integrity and virtue by proactively recognizing and raising a safety issue on a project outside the scope of his formal engagement with Client X, even though he was under no contractual obligation to observe the adjacent site?

If the potential safety issue observed by Engineer A had instead posed an imminent danger to the public, would the Board still have concluded that Engineer A's obligation ends with notifying his supervisor and ES Consulting, or would broader reporting under II.1.f. be required?

If Client X had a direct contractual or business relationship with Owner Y, rather than no relationship at all, would the Board still find that Engineer A's ethical obligation is bounded to internal notification within ES Consulting?

A1 is guided solely by the paramount duty to protect public health, safety, and welfare, which matters because it arises directly from Engineer A's observation of a safety hazard during construction and represents the critical step of escalating that hazard so it can be addressed before it causes harm, meaning any failure at this stage would let the underlying hazard persist unaddressed.

A2 fulfills the duty to perform contracted professional services for Client X while also being guided by the paramount safety obligation, which matters because this routine observation activity is precisely what causes the discovery of the safety hazard, so properly fulfilling the contractual duty is what enables the safety concern to surface and subsequently be escalated in A1.

The question arises because Engineer A witnessed a potential safety issue on a project it was not contracted to oversee, creating tension between the profession's overriding public welfare mandate and the practical constraints of a limited engineering engagement.

The question emerges because the Safety Hazard Observation event places Engineer A in a position where the paramount public safety obligation seems to demand action, yet the lack of a defined role or authority regarding the adjacent project makes it unclear who should judge the severity of the risk and by what criteria.

This question arose because internal notification followed by firm inaction leaves an unresolved gap between the paramount duty to public safety and the bounded, contract-based scope of Engineer A's actual responsibility, forcing a choice about what further personal action, if any, is ethically required.

The question arises because Engineer A's role limits formal obligations to Client X, yet the NSPE Code's paramount safety obligation is not bounded by contract, creating an unresolved conflict between contractual scope and professional ethical duty.

The question arises because incidental discovery of a hazard outside one's contracted scope creates a genuine conflict between the profession's broad public welfare mandate and the narrower principle that engineers are only bound by the terms of their specific engagement.

The question arises because Engineer A occupies a liminal position, having the Capability to recognize a safety issue on a project outside the Engagement Limited To Client X, which creates genuine ambiguity about whether professional safety obligations extend beyond contractual privity.

The question arises because a single engineer, without formal authority over the adjacent project, must weigh a subjective severity judgment against an absolute professional duty, and no clear rule specifies where his personal discretion ends and his paramount obligation begins.

The question arises because Engineer A's role is defined narrowly around Client X's project, yet the observed hazard concerns a different owner's site, creating a gap between the reach of the public safety obligation and the boundaries of the engineering engagement.

The question arises because Engineer A faced a genuine hazard involving a party outside his firm's direct engagement, creating uncertainty about whether internal escalation satisfies the paramount public safety duty or whether that duty demands action beyond his contractual role.

The question arises because the consequentialist focus on actual safety outcomes exposes a gap between the formal completion of an internal reporting obligation and the practical uncertainty of whether the hazard will ever reach the people at risk.

The question arises because Engineer A's voluntary act of raising a safety concern outside his defined engagement creates ambiguity about whether this was a supererogatory act of virtue or something ethically required, since the NSPE Code's paramount safety obligation seems to conflict with the bounded nature of his contractual duty to Client X.

The question arises because the Board's original conclusion rested on the hazard being a potential, non-imminent issue, and altering that factual severity threatens to shift which competing warrant, contractual boundary or paramount public safety duty, should control the outcome.

The question arises because the Board's original finding relied on the fact of no direct relationship between Client X and Owner Y as a rebuttal condition narrowing Engineer A's duty, so altering that fact tests whether the bounded-responsibility warrant still applies or whether the paramount safety warrant would then dominate.

Given that the Board assumed no imminent danger existed and that Engineer A's relationship to the hazard was purely incidental to his work for Client X, the Board concluded that notifying his supervisor and ES Consulting discharges his ethical obligation without requiring escalation to Owner Y, the subcontractor, or external authorities.

Because Engineer A's ability to assess severity is inherently limited by his incidental and external vantage point, the Board's unexamined assumption about imminent danger is treated as leaving open whether ES Consulting bears a further duty to investigate rather than defer to Engineer A's initial judgment.

Given that the Board's reasoning implicitly treats internal notification as sufficient, this leaves unresolved what recourse exists if ES Consulting subsequently does nothing, since Owner Y and the subcontractor's workers have no other channel to learn of the danger.

Because the Board treats the absence of imminent danger and the lack of contractual privity with Owner Y and the subcontractor as sufficient to bound Engineer A's duty, it prioritizes professional and organizational limits over the more expansive public welfare provisions, without explicitly reconciling that tension.

Since Engineer A's vantage point is incidental and he lacks direct involvement with the subcontractor's operations, the Board concludes that the imminent danger determination should rely on general engineering safety criteria applied through ES Consulting's supervisory chain rather than on Engineer A's judgment alone.

Given that Engineer A lacked any contractual relationship with Owner Y or the subcontractor but did have access to ES Consulting and a supervisor capable of acting, the board concluded that his moral duty under I.1. was discharged through internal notification rather than requiring him to personally warn the affected third parties.

Given that Engineer A's contract with Client X was limited to observation of that project and did not task him with monitoring neighboring sites, the board concluded the adjacent hazard awareness was incidental to the scope, but because he actually acquired that knowledge, the paramount safety duty under I.1. attached independently of the contractual boundary.

Given that ES Consulting and a supervisor were available to receive and act on the hazard information, the board concluded that the apparent conflict between public safety and bounded responsibility is reconciled by treating internal escalation as the vehicle for discharging the safety duty, rather than requiring Engineer A to independently intervene in a project outside his engagement.

Given that Engineer A's assessment of the hazard was only the first step in a process that included ES Consulting's supervisory review, the board concluded that his personal judgment functions as a triggering mechanism rather than an unchecked individual determination, thereby guarding against both overreaction and underreaction.

Given that Engineer A's duty was bounded to internal notification without a clearly established imminent danger, the board concluded this limitation is ethically sound only on the implicit condition that ES Consulting treats the notification as an ongoing matter to monitor rather than a terminal act, since otherwise public safety could be under protected.

Given that the hazard was not established as imminent and Engineer A lacked any contractual tie to Owner Y or the subcontractor, the board concluded that internal notification satisfied the paramount duty, effectively narrowing the deontological reading of I.1. to a pragmatic, threshold-based obligation.

Given that ES Consulting has no direct channel to Owner Y or the subcontractor, the board's endorsement of internal notification as sufficient rests on the unproven assumption that the firm will follow through, making the consequentialist justification conditional rather than assured.

Given that Engineer A owed no contractual duty to monitor the adjacent site, the board framed his voluntary reporting as an exercise of professional virtue exceeding minimal requirements, even while keeping his formal obligation narrowly defined.

Had the hazard been imminent, the board's own reasoning implies that I.1. and II.1.f. would compel Engineer A to escalate beyond ES Consulting to external safety authorities, reversing the bounded scope applied in the non-imminent actual case.

Given the hypothetical of a direct Client X-Owner Y relationship, the board reasoned that Engineer A's individual obligation to notify his supervisor and ES Consulting would remain unchanged, though the existing organizational channel would likely make that notification more effective in practice.

Given that Engineer A observed a hazard on an adjacent site with no direct relationship to the affected parties, and that the hazard was not imminent, the Board concluded that internal notification satisfies the paramount safety duty at this severity level, while implying the calculus would shift entirely if imminence were present.

Because Engineer A had a firm structure available to receive and further assess the report, the Board concluded that his ethical responsibility was to recognize and escalate the hazard, leaving the firm to exercise institutional judgment on subsequent action rather than requiring Engineer A to unilaterally decide the ultimate response.

Because Engineer A's contractual scope was confined to Client X's project and the observed hazard lacked imminence, the Board concluded that the paramount safety duty is satisfied through proportionate internal action rather than an open-ended obligation to police all adjacent hazards, while signaling that a closer relationship between Client X and Owner Y or a more severe hazard would change this calculus.

Should Engineer A limit his response to notifying his supervisor and ES Consulting internally, take direct action toward the adjacent site's parties, or decide the matter is entirely outside his professional responsibility and take no action?

Should Engineer A's own assessment of the hazard's severity be treated as final, or should ES Consulting be required to independently investigate and confirm the level of danger before deciding whether further action is warranted?

Should Engineer A attempt to warn Owner Y or the subcontractor's workers directly, or discharge his safety duty solely by ensuring the information reaches someone within his own organizational chain capable of acting on it?

Should Engineer A treat awareness of the adjacent hazard as falling within an implicit duty created by his observation engagement, as purely incidental knowledge that nonetheless triggers an independent paramount safety duty, or as entirely outside any obligation because it was never part of his contracted scope?

If ES Consulting takes no further action after internal notification, or the hazard proves more severe than assumed, should Engineer A escalate to external safety authorities, or treat his internal notification as a complete and final discharge of his ethical duty?