Step 4: Review

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

Act for each employer or client as faithful agents or trustees.

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

Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.

Engineers shall acknowledge their errors and shall not distort or alter the facts.

Engineers are encouraged to adhere to the principles of sustainable development1in order to protect the environment for future generations.Footnote 1"Sustainable development" is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development.

Engineers shall accept personal responsibility for their professional activities, provided, however, that engineers may seek indemnification for services arising out of their practice for other than gross negligence, where the engineer's interests cannot otherwise be protected.

Cited to provide background on conflict of interest issues arising when an engineer transitions employment during an active matter, then distinguished from the present case because the timing of the transition differs.

Cited for guidance on an engineer's obligation to disclose newly discovered inaccurate data and revised conclusions to a client, applied to Principal Engineer R's situation regarding the stormwater error.

Cited alongside Case 16-7 as a similar fact pattern supporting the conclusion that engineers must disclose discovered inaccuracies and updated conclusions to their clients.

Cited to support the principle that engineers must accept responsibility for their professional work and acknowledge errors, even though the original case dealt with a different issue (indemnification clauses).

Given the facts, the Board interprets that Engineer J’s transition from the private sector to the public sector was not recent and there does not appear to be a conflict between J’s former work at BWJ and their current work for City C.

Although flood damage and independent consultant Firm IBM’s analysis show larger flows, Principal Engineer R and Principal Engineers R’s firm should confirm whether an error exists – essentially, they should re-review Firm IBM’s analysis.  If Firm BWJ determines they made a mistake, Principal Engineer R is responsible to acknowledge errors.

The Board's finding of 'no conflict' addresses only the substantive conflict-of-interest question, not the independent, standalone disclosure obligation in Code II.4.a, which is triggered by anything that could merely 'appear' to influence professional judgment. Even where the Board concludes timing eliminates a substantive conflict, City Engineer J arguably still had a duty to disclose his prior BWJ principalship to City C at the time of review, since the appearance standard is not contingent on how much time has passed. The Board's timing-based reasoning therefore resolves the conflict-of-interest question but leaves the separate disclosure question largely unaddressed.

The Board's no-conflict conclusion is reinforced by the limited, administrative nature of City Engineer J's review, which was confined to conformance with City C policy rather than independent technical verification of BWJ's stormwater calculations. This distinction matters because it means J's approval carried no engineering judgment about the adequacy of the runoff analysis; the technical responsibility for compliance with the 25-year peak-flow standard remained solely with Firm BWJ and Principal Engineer R. Had J's review instead involved substantive technical evaluation, the appearance of influence from his prior BWJ affiliation would carry substantially greater ethical weight.

The Board's directive that Principal Engineer R re-review Firm IBM's analysis does not resolve, and should not be read to diminish, R's independent duty under III.8 to accept personal responsibility for the original design regardless of contributory causes. Even if the property owner's paved areas and outbuilding construction exacerbated flooding, this does not excuse BWJ from verifying that its own design met the City's strict pre/post-development flow standard; contributory factors may mitigate the magnitude of harm attributable to BWJ but do not eliminate R's obligation to confirm and, if necessary, correct any underlying design deficiency.

The Board's sequencing—first verify whether an error exists, then acknowledge it if confirmed—reflects a professional-accountability norm but leaves unaddressed the more immediate public welfare obligation under Code I.1. Given that flooding damage has already occurred and Firm IBM's independent modeling shows substantially larger post-development flows, Principal Engineer R and Firm BWJ arguably have an ethical obligation to recommend or support interim protective measures for affected properties while the technical re-review is underway, rather than allowing the verification process alone to delay any public safety response.

Because City Engineer J's role was limited to administrative conformance review rather than independent technical verification of the stormwater calculations, primary engineering responsibility for the runoff design deficiency rests with Principal Engineer R and Firm BWJ, not with City C or Engineer J. The administrative nature of the review also reinforces the Board's finding that no substantive conflict existed, since J was not exercising independent technical judgment that could be biased by his former employment.

Even absent an actual conflict of interest, Code provision II.4.a covers conflicts that merely 'appear' to influence judgment. Best practice under this appearance standard would have been for City Engineer J to disclose his prior BWJ employment to City C at the outset of his review, regardless of how much time had passed, in order to preserve public trust and preempt the kind of complaint that in fact arose.

There is a tension between the Board's timing-based reasoning (transition 'not recent' negates conflict) and the plain text of II.4.a, which conditions disclosure on the existence of a conflict that 'could influence or appear to influence' judgment, without any temporal qualifier. A stricter reading of the Code would require disclosure of any prior employment relationship with a firm under review, irrespective of elapsed time, leaving the ultimate determination of materiality to the reviewing body rather than to the engineer's own assessment of remoteness.

The Board's approach of directing Principal Engineer R to first re-review Firm IBM's analysis before acknowledging error reflects a reasonable sequencing: I.1's paramount duty to public welfare is not undermined by requiring verification before corrective action, because a hasty, unverified redesign could itself introduce new errors. However, this process should not be used to delay urgent interim safety measures (e.g., temporary drainage mitigation) that could protect the public while the technical dispute is resolved.

From a deontological standpoint, Engineer J's duty under II.4.a is a duty to disclose, which is procedurally distinct from a duty to recuse. Even if the Board correctly concludes no conflict existed in substance, J may not have fully discharged the disclosure duty simply by relying on the passage of time as a self-assessment; the deontological obligation arguably required an affirmative statement to City C at the time of review, letting the employer/client determine whether recusal was warranted.

From a consequentialist perspective, the actual harm suffered by property owners (flooding damage) is causally linked to the technical adequacy of Firm BWJ's stormwater design, not to whether a conflict of interest existed in Engineer J's administrative review. Thus the occurrence of damage does not undermine the Board's procedural conclusion on conflict of interest; the two issues are analytically separable, and consequentialist harm should instead inform the evaluation of Engineer R's design and accountability duties rather than J's disclosure conduct.

Principal Engineer R's willingness to re-review Firm IBM's independent findings rather than immediately dispute them demonstrates professional integrity consistent with III.1.a's mandate not to distort facts. This measured response also models appropriate professional accountability under III.8, since accepting personal responsibility does not require immediate self-incrimination, but does require good-faith engagement with credible contrary evidence before reaching a conclusion.

If City Engineer J's transition from Firm BWJ to City C had occurred immediately before his review of BWJ's plans, the Board would likely have found a disqualifying conflict of interest, consistent with the reasoning in BER Case 14-8 regarding employment transitions during active projects. The temporal proximity would create both an actual and an appearance-based conflict, since J's recent loyalty to BWJ and potential residual financial or professional interest would be difficult to separate from his municipal review function.

Had Firm IBM's independent modeling shown post-development flows consistent with pre-development conditions, the Board would likely not have directed any re-review, since there would be no credible basis to question Firm BWJ's compliance with City C's stormwater regulations. The Board's directive to re-review is therefore contingent specifically on the existence of a substantive, credible technical discrepancy, not a general obligation to second-guess every third-party analysis.

The Board resolved the tension between 'Conflict of Interest in Plan Approval' and 'Conflict of Interest in Review Timing' by treating temporal remoteness as effectively dispositive, rather than applying II.4.a's broader 'could influence or appear to influence' standard on its own terms. This subordinates the appearance-based disclosure duty to a factual judgment about how much time had passed since Engineer J left Firm BWJ, without articulating why passage of time alone eliminates the appearance of partiality that II.4.a is designed to prevent regardless of actual influence.

The case reveals an implicit prioritization: 'Professional Accountability in Runoff Error' is treated as a precondition to 'Public Welfare in Corrective Design' rather than a competing value to be balanced against it. The Board directs Engineer R to first verify whether Firm IBM's findings reveal an actual design error before any corrective action or public acknowledgment is required. This sequencing privileges evidentiary accuracy and professional due process (consistent with III.1.a's prohibition on distorting facts) over the more immediate public-welfare imperative of I.1, even though flooding has already occurred and independent third-party analysis already exists showing excess runoff.

The Board's handling of City Engineer J's role shows that 'Conflict of Interest in Plan Approval' was implicitly diluted by an unstated assumption about review depth: because J's review was administrative (conformance with policy) rather than substantive technical evaluation, the stakes of any residual conflict were treated as low enough not to require disclosure. This merges what should be two distinct principles - the nature/scope of the reviewer's authority and the existence of a disqualifying relationship - into a single conclusory finding of 'no conflict,' leaving unresolved whether disclosure obligations depend on the type of review being performed.

Was it ethical for City Engineer J to review and approve plans prepared by Firm BWJ, given that City Engineer J formerly worked for Firm BWJ?

What are Principal Engineer R's ethical responsibilities under the facts?

Does the fact that City Engineer J's review was only 'administrative' (for conformance with policy) rather than an independent technical/engineering review affect who bears responsibility for the stormwater design deficiency?

To what extent should the affected property owner's own construction of extensive paved areas and a large outbuilding reduce Firm BWJ's or Engineer R's responsibility for the flooding damage?

Even if no actual conflict of interest exists, should City Engineer J have disclosed his prior employment at Firm BWJ to City C when reviewing BWJ's plans, given the Code's language covering conflicts that could merely 'appear' to influence judgment?

What ethical duty, if any, does Principal Engineer R owe directly to the non-client property owners harmed by the subdivision's stormwater design, as distinct from R's contractual duty to Developer G?

How should the timing-based reasoning that excuses City Engineer J's conflict (transition 'not recent') be reconciled with the general conflict-of-interest disclosure standard that governs plan approval regardless of when employment ended?

Should Principal Engineer R's duty to protect public welfare through prompt corrective design action be balanced against, or take priority over, the professional accountability process of first re-reviewing Firm IBM's analysis to confirm an error occurred?

From a deontological perspective, did City Engineer J fulfill the duty to disclose known or potential conflicts of interest before reviewing and approving plans prepared by his former firm, Firm BWJ?

From a consequentialist standpoint, does the fact that actual flooding damage occurred to nearby properties outweigh the Board's procedural conclusion that no conflict of interest existed in City Engineer J's approval of the plans?

Did Principal Engineer R act with professional integrity by committing to re-review Firm IBM's independent analysis rather than immediately disputing or dismissing its findings of higher post-development runoff?

Did Principal Engineer R fulfill the duty to accept personal responsibility for professional activities by agreeing to confirm whether an error exists in Firm BWJ's stormwater design, even though property owner modifications also contributed to the flooding?

If City Engineer J's move from Firm BWJ to City C had occurred shortly before he reviewed and approved BWJ's subdivision plans, rather than well in the past, would the Board still have concluded that no conflict of interest existed?

If City Engineer J's review of BWJ's plans had involved substantive technical evaluation of stormwater calculations rather than administrative conformance review, would the Board still find no conflict of interest in his approval?

If the property owner's paved areas and outbuilding construction had not contributed to the flooding, would the Board's directive that Principal Engineer R merely 'confirm whether an error exists' instead become an outright finding that Firm BWJ's design was deficient?

If Firm IBM's independent modeling had shown post-development flows consistent with pre-development conditions rather than substantially larger flows, would the Board still direct Principal Engineer R to re-review the analysis for errors?

Although Employment Transition carries no committed fulfills or violates edge, its causal link to the Conflict Allegation raised by City Engineer J shows that a seemingly routine career move became the trigger for questioning Principal Engineer R's independence and the propriety of the later plan approval, making its normative status significant even without a formal designation.

Firm Retention lacks any recorded normative edge, yet as the action that keeps Principal Engineer R attached to Firm BWJ during the events leading to Subdivision Design and its flooding consequences, it forms the structural backdrop against which any later obligation of care or disclosure must be assessed.

Plan Review Approval has no committed fulfills or violates edge, but because it directly causes Plan Release and thereby Subdivision Completion, and because the underlying Subdivision Design causes Property Flooding, City Engineer J's approval is the pivotal act whose adequacy in checking the design determines whether the resulting harm to property owners could have been prevented.

Property Modification Construction carries no formal normative edge, yet its causal role in producing the Exacerbation Finding attributed to the complaining property owner shows that actions taken by parties outside the original design and review chain can still complicate assessment of who bears responsibility for the flooding's severity.

Independent Review Engagement is not marked as fulfilling or violating any duty, but as the City's response to Flooding Complaints it causally produces the Excess Runoff Finding that both validates Firm IBM's independent assessment and exposes the underlying design condition attributable to Principal Engineer R, making it the key mechanism for surfacing accountability.

A1, the Subdivision Design by Principal Engineer R, carries no explicit fulfillment or violation label yet it is the causal root of Property Flooding, Flooding Complaints, the Independent Review, and the Excess Runoff Finding, meaning the design's adequacy is the substantive engineering question that all subsequent normative judgments about responsibility ultimately trace back to.

A2, the Error Acknowledgment Remediation, fulfills the duty to acknowledge errors (III.1.a) and the duty of responsibility for professional activities (III.8) precisely because it responds to the Excess Runoff Finding that traced flooding back to R's own design, so the remediation matters ethically as the corrective act that closes the causal chain from faulty design to harm with professional accountability rather than denial.

The question arises because City Engineer J occupied dual roles over time (former BWJ employee, then municipal reviewer) and the record shows no explicit conflict finding, leaving open whether her institutional review duty was compromised by her prior firm loyalty.

The question emerges because the independent runoff analysis and flooding events establish that harm occurred, but it is unclear whether Engineer R's ethical duty is retrospective (owning the error) or prospective (fixing the hazard), and how much responsibility is shared with owner construction activity.

The question arises because the scope of City Engineer J's review is ambiguous, being labeled 'administrative' yet still resulting in approval of a plan with a technical deficiency, leaving unclear whether procedural approval implies technical endorsement.

The question arises because the flooding damage resulted from an intervening cause (owner construction) layered on top of a preexisting design deficiency (Post-Development Runoff Noncompliance), making it unclear how to apportion causal and moral responsibility between the original engineering error and the property owner's subsequent choices.

The question arises because the Code's language extends conflict of interest concerns beyond actual bias to mere appearance, creating ambiguity about whether disclosure is required even when Engineer J No Conflict Finding shows no substantive impropriety occurred.

This question arose because the harm fell on parties who never contracted with R, creating a gap between the narrow scope of R's formal engagement with Developer G and the wider scope of professional obligations to public safety, and it is left uncertain by the intervening role of the property owner's own construction in worsening the flooding.

The question emerges because BER Case 14-8 applies a timing based exception to conflict of interest rules, but City C Policy and general conflict of interest norms for plan approval do not explicitly recognize a temporal cutoff, creating a mismatch between case specific and general standards.

The question arises because the data create urgency (ongoing flooding harm to property owners) that pulls toward immediate action, while professional norms around acknowledging errors responsibly pull toward confirming the analysis first, and no clear priority rule resolves which obligation governs when time is of the essence.

The question arose because the timing and nature of Engineer J's move from Firm BWJ to City C created an ambiguous conflict of interest situation that was only scrutinized after flooding complaints and runoff findings revealed problems with the approved plans, prompting retrospective examination of whether disclosure obligations were met.

The question arises because the Board evaluated J's conduct against a procedural rule (Conflict of Interest in Plan Approval) while the actual harm to Property Owners Affected Public and confirmed Excess Runoff Finding invite evaluation under a harm-based, consequentialist standard instead, leaving open which framework should govern moral responsibility.

The question arises because the same data, a third-party analysis contradicting the engineer's prior work, can be read either as evidence demanding immediate accountability or as an unverified claim demanding careful technical scrutiny before action, leaving Engineer R's chosen response open to competing normative interpretations.

The question arises because a verified design deficiency (excess runoff, culvert insufficiency) coexists with an independent, non-engineering cause (owner construction), creating ambiguity about whether Engineer R's agreement to investigate and potentially acknowledge error fulfills or exceeds the NSPE duty of accepting responsibility only for one's own professional activities.

The question arises because the Board's conclusion hinged on timing as an implicit rebuttal to the conflict of interest warrant, and altering that timing variable tests whether the warrant excluding conflict still holds or whether the competing disclosure/recusal warrant takes over.

The question arises because the Board's conclusion depends entirely on characterizing the nature of J's review, and the case facts leave open whether his approval involved genuine technical evaluation of stormwater calculations or mere procedural sign off, making the conflict of interest determination contingent on an unresolved factual premise.

The question arises because the Board's cautious phrasing (confirm whether an error exists) signals unresolved uncertainty about causal attribution between BWJ's original design and the owner's subsequent site modifications, making the appropriate normative conclusion (mere verification versus definitive fault-finding) contingent on facts not yet settled.

This question emerges because Toulmin's warrant for requiring re-review is ambiguous between a result-contingent standard (only for actual noncompliance) and a process-contingent standard (for any credible challenge to the analysis), and the hypothetical alters the data (compliant flows) to test which warrant the Board is actually relying upon.

Given that J's move from BWJ to City C had occurred long before his review of BWJ's subdivision plans, the Board concluded that the passage of time dissolved any realistic conflict, treating temporal remoteness as dispositive of the conflict-of-interest question.

Because IBM's analysis conflicted with BWJ's original modeling but the source of the discrepancy remained unconfirmed, the Board directed R to re-review the analysis first, reasoning that responsible acknowledgment of error under III.8 and III.1.a presupposes verification rather than immediate concession.

Even though the Board found timing sufficient to dispel an actual conflict, the appearance standard in II.4.a does not reference elapsed time, so J's failure to disclose his prior BWJ principalship remains an open, unresolved obligation that the Board's timing-based reasoning does not address.

Because J's approval involved only a check against City C's administrative requirements rather than an independent technical assessment of BWJ's runoff calculations, the Board treated the appearance of influence as minimal and reinforced its no-conflict conclusion on that basis.

Although the owner's construction activity may have worsened the flooding, the Board reasoned that this contributory cause does not relieve R of the separate obligation to verify whether BWJ's original design itself complied with City C's strict flow standard, keeping the accountability duty intact alongside the re-review directive.

Given that flooding damage already occurred and an independent firm's modeling pointed to a likely design flaw, the Board's conclusion suggests Engineer R and Firm BWJ should not wait solely on verification but should consider interim protective measures to satisfy the paramount public welfare obligation under I.1 while the technical dispute is resolved.

Because City Engineer J's role was limited to checking conformance with policy rather than independently verifying the stormwater calculations, the Board placed primary engineering responsibility for the runoff design deficiency on Principal Engineer R and Firm BWJ, and treated the administrative nature of the review as also supporting the no-conflict finding for J.

Even though no actual conflict was found, the Board's analysis suggests that because II.4.a's language covers appearance of influence, best practice would have had City Engineer J disclose his prior BWJ employment to City C at the outset, since doing so would have preempted the complaint that arose and preserved public trust.

Given that the Board rested its no-conflict finding on the transition being 'not recent,' the analysis identifies a tension with the Code's plain text, which conditions disclosure on the possibility of appearing to influence judgment without any temporal limitation, suggesting a stricter reading would require disclosure regardless of how long ago the transition occurred.

Because Firm IBM's modeling raised a credible but not yet confirmed claim of design error, the Board found it reasonable for Engineer R to first re-review the analysis before acknowledging fault, since acting under I.1 does not require abandoning verification, but the Board's own qualification indicates this process must not be used to withhold interim safety measures while the dispute is resolved.

Given that J appears to have privately concluded the transition was too old to matter rather than telling City C about it, the Board reasons that II.4.a's disclosure duty is a distinct, front-loaded obligation that self-assessment cannot substitute for, even if the ultimate no-conflict conclusion is correct.

Because the flooding stems from BWJ's engineering design choices rather than from J's conformance-only review, the Board concludes that real-world damage, however serious, does not retroactively establish that J's approval was ethically compromised by conflict of interest.

Since R responded to IBM's credible contrary analysis by agreeing to re-review rather than reflexively rejecting it, the Board treats this as integrity-consistent conduct under III.1.a and an appropriate, non-evasive form of accountability under III.8.

Applying the reasoning of BER Case 14-8, the Board reasons that had J moved to City C shortly before reviewing BWJ's plans, the unresolved recency of his loyalty to BWJ would create both an actual and appearance-based conflict, making disqualification likely, in contrast to the actual facts where enough time had passed.

Because IBM's actual findings showed materially higher post-development runoff, the Board directed R to re-review, but reasons that absent such a credible discrepancy, as in the hypothetical of consistent flows, there would be no basis to question BWJ's compliance and thus no obligation to re-review.

Given that Engineer J's departure from Firm BWJ was temporally remote from his review of BWJ's plans, the Board concluded no conflict existed, reasoning from elapsed time rather than squarely applying II.4.a's 'could influence or appear to influence' test to the disclosure question itself.

Given that owner-caused modifications muddied the causal picture despite IBM's runoff findings and existing flooding, the Board directed Engineer R to first confirm an actual design error before any acknowledgment or corrective design, prioritizing III.1.a's accuracy norm over an immediate I.1 response.

Given that Engineer J's review was administrative rather than technical, the Board treated the residual conflict as low-stakes and found no conflict, without separately resolving whether disclosure duties should track the type of review performed.

Should City Engineer J disclose his former employment at Firm BWJ to City C before reviewing and approving BWJ's subdivision plans, or rely on the passage of time to excuse disclosure?

Should Engineer R re-review Firm IBM's analysis before acknowledging any design error, or immediately acknowledge the error and take corrective or interim protective action?

Should Engineer R accept full responsibility for verifying the original design's compliance regardless of the owner's contributory construction, or treat the owner's modifications as reducing his accountability?

Should Firm BWJ proceed to identify and design a corrective solution for the flooding promptly, or first complete fault determination and allocation among all involved parties before acting?

Should City Engineer J limit his review of BWJ's subdivision plans to administrative conformance with City C policy, or conduct an independent technical evaluation of the stormwater calculations before approving them?