Step 4: Review

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

Engineers shall be guided in all their relations by the highest standards of honesty and integrity.

Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.

The Board cited this case as an example of the tension between client confidentiality and public safety obligations, where an engineer learned of non-structural safety violations from a client under a confidentiality agreement, but ultimately distinguished it because the engineer lacked expertise in the relevant discipline and the client had confided in him expecting confidentiality.

The Board cited this case involving a bridge inspection engineer who noted a possible pre-existing defect outside his scope of work but did not include it in his final report or report it to authorities, ultimately distinguishing it because the engineer's observation was mere speculation based on visual inspection and he lacked structural engineering expertise, unlike the clear legal violation in the present case.

Engineer A should contact the client and inquire about the actions the client has taken and point out the action is a violation of the law and that steps need to be take to remedy the violation or obtain a variance from the proper authorities. In this connection, the engineer should advise that the remedial actions should be in full compliance with all applicable environmental laws and regulations, which may include the review of a licensed engineer. If appropriate steps are not taken by the client, Engineer A has an obligation to bring this matter to the attention of the appropriate authorities.

The Board's conclusion establishes a staged or conditional obligation rather than an absolute duty: Engineer A's initial duty is limited to client notification and advisory action, and only escalates to a reporting obligation to authorities if the client fails to take appropriate remedial steps. This tiered structure implies that Engineer A must exercise professional judgment about what constitutes a reasonable period or adequate response from the client before the reporting duty is triggered, but the Board does not specify how long Engineer A should wait or what evidence of client inaction would be sufficient to establish that 'appropriate steps' have not been taken.

Although Engineer A's formal wetland delineation engagement had concluded months before he observed the violation, the Board implicitly treats his ethical obligations as surviving the termination of the client relationship. This suggests that an engineer's duty to hold paramount the safety, health, and welfare of the public is not contingent on an active contractual relationship, but arises from the engineer's professional knowledge and expertise regardless of whether he is currently retained. This extends the Board's reasoning by clarifying that the public welfare obligation operates independently of, and can outlast, the client-engineer relationship.

The Board's conclusion implicitly resolves the tension between confidentiality obligations (II.1.c. and III.4.) and the duty to report known Code violations (II.1.f.) by sequencing them rather than treating them as mutually exclusive: Engineer A first engages the client privately, which respects confidentiality and the faithful agent relationship, and only moves to public disclosure if the client's inaction leaves no alternative. This sequencing approach, rather than an outright hierarchy where public welfare always immediately overrides confidentiality, allows Engineer A to fulfill his duty to the public without unnecessarily breaching client trust prematurely, but it leaves open how much weight should be given to confidentiality once the reporting threshold is reached.

Regarding Q101, Engineer A's duty does not depend on the continuation of the contractual wetland delineation engagement. Under Code provision I.1, the paramount obligation to protect public safety, health, and welfare is a standing professional duty that survives the termination of a specific client engagement. Because the violation directly implicates protected wetlands and public environmental interests, Engineer A retains an ethical obligation to act even though the formal delineation project had concluded months earlier.

Regarding Q102, Engineer A's obligation is best understood as a conditional, staged duty rather than an open-ended monitoring responsibility. He must notify the client, advise on legal compliance, and remain attentive to whether remedial steps are taken; however, he is not ethically required to conduct ongoing surveillance or verification of the client's remediation progress indefinitely. His duty escalates to reporting to authorities only if it becomes apparent that the client has failed to take appropriate corrective action.

Regarding Q103, the manner in which Engineer A acquired knowledge of the violation—incidentally, while driving by—does not diminish the strength of his ethical obligation. The Code's reporting duty under II.1.f is triggered by possession of knowledge of a violation, not by the professional context in which that knowledge was obtained. Once Engineer A possesses reliable knowledge of a substantial legal violation, his obligation to act arises regardless of whether it was discovered through his engagement or by chance.

Regarding Q201 and Q202, the tension between client loyalty/confidentiality (II.4, II.1.c, III.4) and the duty to report violations (II.1.f) is resolved by the Code's own hierarchy: the paramount duty to protect public health, safety, and welfare (I.1) takes precedence over confidentiality obligations. The Code does not treat these duties as irreconcilable; rather, II.1.f functions as an explicit exception to confidentiality when a violation of the Code or law is at stake, permitting disclosure to authorities without breaching the spirit of loyalty to the client.

Regarding Q301, from a deontological standpoint Engineer A satisfies his duty under I.1 by first contacting the client rather than immediately reporting to authorities, because the environmental violation—while serious—does not present an immediate threat to life analogous to a structural safety hazard. The graduated response of notify-then-report honors both his duty to hold public welfare paramount and his duty of good faith dealing with the client, provided the notification step does not become an indefinite delay tactic.

Regarding Q302, from a consequentialist perspective, giving the client a reasonable opportunity to remediate the violation without immediate involvement of regulators is more likely to produce a better overall outcome than immediate disclosure, since it can restore the wetland with less adversarial delay, cost, and potential defensive obstruction by the client. However, this reasoning holds only if the delay is brief and results in true remediation; if it enables continued environmental degradation, the consequentialist calculus would favor prompt authority reporting.

Regarding Q303, viewed through virtue ethics, Engineer A's approach—first engaging the client honestly and constructively before escalating to authorities—reflects the character traits of practical wisdom, integrity, and fidelity expected of a professional. A virtuous engineer neither rushes to report out of self-protection nor conceals the violation out of loyalty; genuine integrity requires that if the client fails to act, Engineer A must follow through with reporting, since failing to do so would betray the public trust central to professional virtue.

Regarding Q401, had Engineer A's wetland delineation engagement still been active when he discovered the fill violation, the Board would likely have framed his obligation more directly as a professional duty tied to his role as engineer of record—potentially requiring him to refuse further certification of the site's compliance or withdraw from the engagement under II.1.a—rather than the more attenuated 'outsider' duty to notify and monitor that applies once the professional relationship has ended.

Regarding Q402, the Board's emphasis on the fill exceeding half an acre and constituting a 'substantial' violation suggests that severity is a relevant factor in triggering the reporting obligation. Had the encroachment been minimal or arguably de minimis, the Board may have found that informal advisory action alone satisfied Engineer A's ethical duty, without necessarily requiring escalation to formal authority reporting absent client noncompliance.

Regarding Q403, if Engineer A had learned of the fill installation only through secondhand information rather than personal observation, the Board would likely require some degree of independent verification before treating the report as sufficient 'knowledge' to trigger the reporting duty under II.1.f, since ethical obligations to report violations presuppose a reliable factual basis rather than mere rumor or unverified third-party claims.

The tension between Loyalty to Client in Wetland Case and Public Welfare in Wetland Violation is not resolved through a binary choice but through a sequential, staged framework: the engineer must first honor client loyalty by giving private notification and an opportunity to remediate, and only escalate to public disclosure if that loyalty-based channel fails. This staged approach allows both principles to be honored in turn rather than forcing an immediate override of one by the other, reflecting the Code's structure where II.4 (faithful agency) and II.1.c/III.4 (nondisclosure) operate as a first-order constraint that yields to I.1 (paramount public welfare) and II.1.f (reporting known violations) only conditionally, upon client non-responsiveness.

The case demonstrates that public welfare (I.1) functions as the paramount principle in the Code's hierarchy, but its paramountcy is expressed procedurally rather than temporally immediate: the engineer satisfies the paramount duty by ensuring the violation is eventually addressed, whether by the client's voluntary remediation or by regulatory intervention, rather than by personally and instantly reporting to authorities. This shows that 'paramount' does not mean 'first-acting' in all cases, but rather 'ultimately controlling' if lesser channels fail, meaning client loyalty and confidentiality can operate as legitimate intermediate steps without violating the spirit of I.1.

Corrective Action Monitoring in Remediation emerges as a bridging principle that reconciles the tension between the engineer's concluded professional engagement and his continuing ethical exposure to the violation: because the Code ties reporting obligations to knowledge rather than to active client relationships, the engineer's duty to monitor whether remedial steps are taken is grounded not in his former contractual role but in his ongoing possession of knowledge of an alleged Code and legal violation, which independently triggers II.1.f regardless of the state of the underlying engagement.

What are Engineer A’s ethical obligations under these facts?

Since Engineer A's wetland delineation engagement had already ended when the violation was discovered, does he still owe an ongoing duty to the former client or to the public regarding conditions on that property?

Does Engineer A have an obligation to independently verify or monitor whether the client actually completes remediation, or does his duty end once he has notified the client and advised on compliance?

Because Engineer A observed the violation incidentally (while driving by) rather than through his professional engagement, does this change the nature or strength of his ethical obligation to act compared to violations discovered during active service?

What threshold of severity or client non-responsiveness should trigger Engineer A's move from private notification to formal reporting to authorities?

How should Engineer A balance his duty of loyalty and confidentiality to the client against the paramount obligation to protect public welfare when the client has committed a substantial environmental violation?

Does the constraint against disclosing confidential client information conflict with Engineer A's obligation to report known code violations to appropriate authorities?

How should Engineer A's ongoing corrective action monitoring role be reconciled with the fact that his professional engagement with the client has already concluded?

From a deontological perspective, did Engineer A fulfill his duty to hold paramount the safety, health, and welfare of the public by first approaching the client rather than immediately reporting the unpermitted fill to environmental authorities?

From a consequentialist standpoint, does giving the client an opportunity to remediate the wetland violation before reporting to authorities produce a better overall outcome than immediate disclosure, given the ongoing environmental harm from the unpermitted fill?

Did Engineer A act with professional integrity when balancing his loyalty to a former client against his obligation to protect the public interest in the wetland environment, as a virtue-ethics inquiry into character rather than rule-following?

If Engineer A's wetland delineation engagement had still been active and ongoing (rather than completed months earlier) when he discovered the fill violation, would the Board still have framed his primary obligation as an outsider's conditional duty to notify and monitor rather than an immediate professional duty to halt or correct the work as the client's engineer of record?

If the fill installation had covered only a small, arguably de minimis area rather than more than half an acre in substantial violation of federal and state law, would the Board still conclude that Engineer A has an obligation to report the matter to appropriate authorities if the client fails to act?

If Engineer A had learned of the fill installation only through secondhand information from a third party rather than through his own direct observation while driving by the property, would the Board still hold that he possesses sufficient knowledge under the Code to trigger a reporting obligation?

By monitoring the client's remediation after notification, Engineer A fulfills the paramount duty to protect public health and safety, since this monitoring is the causal link that leads to the subsequent duty-bound step of authority reporting rather than letting the unpermitted fill's environmental harm go unaddressed.

The wetland delineation services, guided solely by faithfulness to the client, are the professional context within which the client later installs unpermitted fill, so this action carries no fulfillment or violation itself but sets up the relationship in which the client's later noncompliance becomes Engineer A's concern.

The client's unpermitted fill installation violates compliance with environmental laws and regulations and is the root causal act that generates both the environmental law violation and the discoverable condition that triggers Engineer A's entire subsequent chain of notification, monitoring, and reporting duties.

Notifying the client of the violation, guided by the duty to hold public health and safety paramount, is the necessary causal bridge between discovering the fill violation and initiating remediation monitoring, even though it does not itself complete or breach any obligation.

Authority reporting fulfills the paramount duty to protect public health and safety because it is the culminating act triggered by the client's failure to adequately remediate, ensuring that the unresolved environmental violation is escalated to those with power to enforce compliance.

The question arises because the fill violation was discovered incidentally to a narrowly scoped client engagement, forcing a choice between the paramount duty to public welfare and the duty of faithfulness and confidentiality to the client, a tension the Board has addressed differently in precedent cases like 89-7 and 97-13 depending on context.

The question arises because the temporal boundary of the engagement (Completed Wetland Delineation Engagement) creates ambiguity about whether obligations under the Code are engagement-bound or persist as a standing duty to the public, especially given precedent cases addressing confidentiality versus safety disclosure.

The question arises because the engagement was completed (wetland delineation), yet the discovered violation implicates ongoing public interest concerns, creating ambiguity about whether the engineer's ethical duty extends beyond his contractual scope into continuous oversight.

The question arises because the completed Wetland Delineation Engagement had already ended when Engineer A observed the fill violation while driving by, creating ambiguity about whether the same professional obligations that governed his prior client relationship extend to knowledge gained outside that relationship.

The question arises because the Wetland Context Precedent Gap leaves no clear standard, borrowed from building safety cases, for judging how much client delay or environmental severity is enough to convert Engineer A Client Notification Duty into Engineer A Reporting Duty.

The question arose because Engineer A's professional relationship as a paid consultant for wetland delineation put him in possession of information about an environmental violation, forcing a choice between two legitimate but conflicting professional obligations with no clear precedent for the wetland context.

The question emerged because Engineer A's dual role as confidential consultant and public safety guardian created a direct clash between the Client Nondisclosure Boundary and the Reporting Duty, with no settled precedent for wetland specific violations.

The question emerged because the engineer's professional role formally ended before the wetland violation's corrective action process began, forcing a reconciliation between contract-bounded duties and open-ended public welfare obligations tied to the same underlying violation.

The question arises because the Code of Ethics offers no explicit hierarchy for cases where client loyalty and public welfare obligations point to different first actions, leaving the sequencing of client notification versus authority reporting ethically contestable.

The question arose because the engineer's simultaneous obligations to protect public welfare and to respect client confidentiality point toward different immediate actions, forcing a comparison of outcomes under a consequentialist frame rather than a clear rule-based resolution.

The question arises because the case data places a completed, confidentiality-bound client relationship in direct contact with a discovered environmental violation, and no clear rule specifies whether virtue-based character judgment or duty-based reporting obligation should govern Engineer A's response given the ambiguous precedent from prior board cases.

The question arises because the Board's ethical framing hinges on the completed status of the engagement, and altering that single fact (an active versus completed engagement) shifts which warrant, outsider notification versus engineer of record correction, governs Engineer A's obligation.

This question arose because the Board's original conclusion rested on the violation being large and substantial, and altering that scale factually tests whether the reporting obligation is triggered by any illegality or only by illegality causing significant public harm.

The question arises because the original case involved direct observation, so the Board's holding leaves open whether the same duty extends to less certain, indirect forms of knowledge acquisition.

Given a substantial but non-emergency wetland violation and an existing (though concluded) client relationship, the board concluded that Engineer A's obligations begin with client engagement and escalate to authority reporting only if remedial steps are not taken, balancing agent loyalty against the paramount public welfare duty.

Because the board articulated only a conditional escalation without specifying triggering criteria, its conclusion implies that Engineer A must exercise discretion in determining when client inaction converts an advisory duty into a reporting obligation.

Because Engineer A's wetland expertise allowed him to recognize the violation notwithstanding the engagement's conclusion, the board reasoned that his I.1 duty survives independent of the contractual relationship.

Since the fill violation, while substantial, was not described as causing imminent escalating harm, the board could resolve the confidentiality/reporting tension by sequencing private engagement before public disclosure rather than treating public welfare as automatically overriding confidentiality.

Given that the fill violation touched protected wetlands and public environmental interests within Engineer A's area of expertise, the board concluded that the paramount I.1 obligation persisted despite the delineation engagement having concluded months earlier.

Given that Engineer A's engagement had ended and he had already notified the client and advised on compliance, the board concluded his duty is staged and conditional rather than an open-ended monitoring obligation, escalating only if nonresponsiveness becomes apparent.

Because Engineer A directly observed a substantial violation, even though incidentally while driving by, the board concluded that the manner of discovery does not diminish his obligation under II.1.f, since the Code's trigger is possession of knowledge, not the professional context of acquiring it.

Given that the client's fill violation was substantial and implicated public and environmental welfare, the board concluded that the Code's own hierarchy resolves the apparent tension, with I.1's paramountcy and II.1.f's reporting duty permitting disclosure without violating the spirit of client loyalty.

Because the wetland violation, though serious, did not pose an immediate life-safety threat comparable to a structural hazard, the board concluded that Engineer A's graduated notify-then-report approach satisfies his deontological duty under I.1, provided the notification does not become indefinite delay.

Given that a short remediation window could restore the wetland with less adversarial delay and cost than immediate regulatory involvement, the board concluded that consequentialist reasoning favors giving the client that opportunity, but only conditionally, reversing in favor of prompt reporting if the delay instead permits ongoing degradation.

Given that Engineer A chose to raise the issue with the client before considering formal reporting, the board concluded this reflects practical wisdom and integrity rather than either extreme of self-protection or complicity, and that true integrity obligates him to follow through with reporting if the client does not act.

Given that Engineer A's role had already ended when he found the violation, the board framed his obligation as an external notify-and-monitor duty, but reasoned that had he still been the client's engineer of record, his professional status would instead compel a more direct duty to refuse continued certification or withdraw from the engagement.

Because the fill in this case exceeded half an acre and clearly violated federal and state law, the board treated the violation as substantial enough to require reporting if the client failed to act, but reasoned that a smaller, de minimis encroachment might not necessarily trigger that same escalation duty.

Since Engineer A directly observed the unpermitted fill himself while driving by, the board treated this as sufficient 'knowledge' to trigger the reporting duty, but reasoned that mere secondhand or rumored information would first require independent verification before it could ground the same obligation.

Given that the wetland violation, though substantial, allowed time for private client engagement without imminent public harm, the board concluded that faithful agency and nondisclosure obligations could be honored first, with the paramount public welfare and reporting duties activating only if the client failed to remediate.

Given that the wetland fill was a substantial but non-emergency violation and the client still had the capacity to remediate, the board concluded that Engineer A satisfied his paramount duty by first notifying the client and reserving formal reporting as a fallback, treating 'paramount' as ultimately controlling rather than temporally first-acting.

Because Engineer A's contractual role had concluded but he still knew of an unresolved, alleged violation, the board reasoned that his duty to monitor and eventually report is anchored in that knowledge under II.1.f, creating a bridging obligation that survives the end of the formal engagement.

Should Engineer A first notify the client of the violation and advise on compliance, or report the unpermitted fill directly to authorities without prior client contact?

Must Engineer A act on the discovered violation even though his contractual engagement with the client had already ended?

Should Engineer A escalate to authority reporting only after the client fails to take appropriate remedial steps, or should he monitor indefinitely or report immediately without waiting?

Does Engineer A's duty to report known code and legal violations to authorities override his confidentiality obligations to the client once remediation proves inadequate?