Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Excess Stormwater Runoff
Step 4 of 5

202

Entities

7

Provisions

4

Precedents

16

Questions

18

Conclusions

Phase Lag

Transformation
Phase Lag Delayed consequences reveal obligations not initially apparent
The subdivision was designed and approved under one set of assumed conditions (pre-construction modeling), but the consequences of the design (flooding, insufficient culvert capacity, excess runoff) only surfaced years later through complaints and IBM's independent post-hoc analysis, creating a retrospective obligation for Engineer R to reconfirm and potentially correct the original design. Simultaneously, City Engineer J's conflict-of-interest exposure is evaluated through a temporal lens ('not recent'), treating elapsed time as dispositive of reduced ethical risk rather than triggering renewed scrutiny.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (7)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

I.1 board + analysis Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 28)
Obligation
Engineer R Design Standard Compliance
Public safety requires the subdivision design to properly manage stormwater runoff.
Action
Subdivision Design
Original design must safeguard public safety and welfare regarding stormwater management
State
Vicinity Property Flooding Hazard
Public safety and welfare is impacted by flooding of neighboring properties
Obligation (2)
  • Engineer R Design Standard Compliance
    Public safety requires the subdivision design to properly manage stormwater runoff.
  • Firm BWJ Corrective Design Duty
    Correcting the runoff problem is necessary to protect public welfare and safety.
Action (4)
  • Subdivision Design
    Original design must safeguard public safety and welfare regarding stormwater management
  • Plan Review Approval
    Approval of plans must ensure public safety and welfare are protected
  • Independent Review Engagement
    Review of stormwater issue must prioritize public safety and welfare
  • Property Modification Construction
    Construction modifications must not endanger public safety through runoff issues
State (5)
  • Vicinity Property Flooding Hazard
    Public safety and welfare is impacted by flooding of neighboring properties
  • Post-Development Runoff Noncompliance
    Failure to meet runoff standards threatens public welfare
  • Insufficient Driveway Culvert Capacity
    Inadequate culvert capacity poses a safety hazard from flooding
  • Owner Construction Flood Exacerbation
    Construction that worsens flooding endangers public welfare
  • Subdivision Runoff Problem Confirmed
    Confirmed runoff problem directly threatens public safety and welfare
Constraint (1)
  • Engineer R Stormwater Runoff Limit
    Limiting stormwater runoff directly protects public safety, health, and welfare
Principle (2)
  • Public Welfare in Corrective Design
    Holding safety and welfare paramount requires a workable corrected design for the stormwater problem
  • Professional Accountability in Runoff Error
    Acknowledging the runoff error protects public safety and welfare
Role (3)
  • Principal Engineer R Design Engineer
    Responsible for stormwater design that affected public safety and property
  • City Engineer J Municipal Engineer
    Responsible for reviewing plans to protect public welfare before approval
  • Firm IBM Reviewing Consultant Engineer
    Engaged to independently verify public safety after flooding complaints
Event (4)
  • Property Flooding
    Flooding endangers public safety and welfare
  • Excess Runoff Finding
    Excess runoff threatens public welfare
  • Culvert Insufficiency Finding
    Insufficient culvert design endangers public safety
  • Exacerbation Finding
    Worsening conditions harm public safety and welfare
Resource (3)
  • City C Stormwater Regulations
    This regulation protects public safety by limiting flood risk from excess runoff
  • City C Subdivision Regulations
    This regulation limits peak flow to protect public safety and welfare
  • IBM Runoff Analysis
    This analysis determines whether public safety from flooding is protected
Capability (4)
  • Engineer R Subdivision Design
    The subdivision design must protect public safety and welfare from flooding risks.
  • City Engineer J Plan Review
    Plan review approval implicates public safety by allowing construction to proceed.
  • Firm IBM Independent Analysis
    Independent analysis of flooding directly concerns public safety and welfare.
  • Firm BWJ Corrective Design
    A corrective design is required to protect public safety from ongoing flooding harm.
I.4 board + analysis Act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 16)
Obligation
Engineer R Professional Accountability Duty
Engineer R acted as an agent for Developer G in directing the design work.
Action
Firm Retention
Engineer must act as faithful agent when retained by new firm or client
State
BWJ Subdivision Design Engagement
Engineer must act as faithful agent to the client in the design engagement
Obligation (2)
  • Engineer R Professional Accountability Duty
    Engineer R acted as an agent for Developer G in directing the design work.
  • City Engineer J Plan Review Duty
    City Engineer J serves as a faithful agent for City C by reviewing plans for compliance.
Action (2)
  • Firm Retention
    Engineer must act as faithful agent when retained by new firm or client
  • Independent Review Engagement
    Reviewing engineer must act faithfully on behalf of the client
State (2)
  • BWJ Subdivision Design Engagement
    Engineer must act as faithful agent to the client in the design engagement
  • Approved Plans Released For Construction
    Releasing approved plans relates to faithful service obligations to client
Constraint (1)
  • Engineer R Stormwater Runoff Limit
    Engineer R must faithfully serve the public interest while directing the subdivision design for the client
Principle (2)
  • Conflict of Interest in Plan Approval
    Acting as a faithful agent requires avoiding compromised judgment when approving former employer's plans
  • Conflict of Interest in Review Timing
    Faithful agency duties are implicated by the timing of transition from BWJ to city employment
Role (2)
  • Principal Engineer R Design Engineer
    Acted as faithful agent for client Developer G in preparing subdivision plans
  • City Engineer J Municipal Engineer
    Acted as faithful agent for employer City C in reviewing plans
Event (2)
  • Plan Release
    Engineer must act faithfully for client when releasing plans
  • Subdivision Completion
    Completion reflects faithful agency to client during design and construction
Resource (1)
  • City C Policy
    Engineers must act as faithful agents when navigating municipal approval requirements for clients
Capability (2)
  • Engineer R Subdivision Design
    Engineer R acted as a faithful agent for Developer G in directing the design.
  • City Engineer J Plan Review
    City Engineer J served as a faithful agent for City C in reviewing and approving plans.
I.6 board + analysis Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.
How this applies in the case (showing 3 of 15)
Obligation
Engineer R Error Acknowledgment Duty
Acknowledging the design flaw upholds honorable and responsible professional conduct.
Action
Error Acknowledgment Remediation
Honorable conduct requires addressing errors to protect profession reputation
State
City Engineer J Prior Employment Conflict
Prior employment relationship raises questions about honorable conduct
Obligation (2)
  • Engineer R Error Acknowledgment Duty
    Acknowledging the design flaw upholds honorable and responsible professional conduct.
  • City Engineer J Conflict Disclosure Duty
    Disclosing the conflict of interest maintains honorable and lawful conduct.
Action (2)
  • Error Acknowledgment Remediation
    Honorable conduct requires addressing errors to protect profession reputation
  • Employment Transition
    Ethical conduct during employment change reflects on professional reputation
State (2)
  • City Engineer J Prior Employment Conflict
    Prior employment relationship raises questions about honorable conduct
  • Engineer J No Conflict Finding
    Determining no conflict relates to maintaining professional honor and reputation
Constraint (1)
  • Engineer J Recent Transition Review Limit
    Reviewing former employer's plans could compromise honorable and ethical conduct expected of the profession
Principle (2)
  • Professional Accountability in Runoff Error
    Acting honorably and responsibly requires acknowledging the runoff error
  • Conflict of Interest in Plan Approval
    Ethical conduct requires avoiding the appearance of impropriety in plan approval
Role (2)
  • Principal Engineer R Design Engineer
    Must conduct design work honorably and responsibly to uphold profession's reputation
  • City Engineer J Municipal Engineer
    Must act honorably given prior employment ties to the design firm
Event (2)
  • Flooding Complaints
    Complaints reflect on professional reputation and conduct
  • Conflict Allegation
    Allegation of conflict impacts honor and reputation of profession
Capability (2)
  • Engineer R Professional Accountability
    Acknowledging error and acting responsibly upholds the honor and reputation of the profession.
  • Engineer R Normative Assessment
    Applying ethical obligations reflects honorable and responsible professional conduct.
II.4.a board + analysis 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.
How this applies in the case (showing 3 of 12)
Obligation
City Engineer J Conflict Disclosure Duty
City Engineer J must disclose his prior employment with Firm BWJ as a potential conflict of interest.
Action
Employment Transition
Potential conflicts from prior employer relationship must be disclosed in new role
State
City Engineer J Prior Employment Conflict
Prior employment with the city could be a conflict of interest requiring disclosure
Obligation (1)
  • City Engineer J Conflict Disclosure Duty
    City Engineer J must disclose his prior employment with Firm BWJ as a potential conflict of interest.
Action (2)
  • Employment Transition
    Potential conflicts from prior employer relationship must be disclosed in new role
  • Independent Review Engagement
    Conflicts of interest from prior involvement in original design must be disclosed
State (3)
  • City Engineer J Prior Employment Conflict
    Prior employment with the city could be a conflict of interest requiring disclosure
  • Engineer J Transition Timing Uncertainty
    Uncertain timing of transition from city employment raises potential conflict of interest concerns
  • Engineer J No Conflict Finding
    Finding of no conflict directly relates to the conflict of interest disclosure requirement
Constraint (1)
  • Engineer J Recent Transition Review Limit
    Engineer J's recent transition creates a potential conflict of interest that must be disclosed
Principle (2)
  • Conflict of Interest in Plan Approval
    Disclosure of potential conflicts is directly relevant to the allegation that Engineer J approved plans from his former firm
  • Conflict of Interest in Review Timing
    The timing of disclosure of prior employment relates to whether a conflict of interest existed
Role (1)
  • City Engineer J Municipal Engineer
    Former employment with Firm BWJ created a potential conflict of interest requiring disclosure
Event (1)
  • Conflict Allegation
    Directly addresses disclosure of conflicts of interest
Resource (1)
  • BER Case 14-8
    This case directly addresses conflicts of interest during employment transitions
III.1.a board + analysis Engineers shall acknowledge their errors and shall not distort or alter the facts.
How this applies in the case (showing 3 of 15)
Obligation
Engineer R Error Acknowledgment Duty
Engineer R must acknowledge the stormwater design error rather than distort the facts.
Action
Error Acknowledgment Remediation
Engineers must acknowledge errors and not distort facts about the runoff issue
State
Subdivision Runoff Problem Confirmed
Engineer must acknowledge the confirmed runoff problem rather than distort facts
Obligation (1)
  • Engineer R Error Acknowledgment Duty
    Engineer R must acknowledge the stormwater design error rather than distort the facts.
Action (2)
  • Error Acknowledgment Remediation
    Engineers must acknowledge errors and not distort facts about the runoff issue
  • Independent Review Engagement
    Reviewing engineer must accurately report facts without distortion
State (2)
  • Subdivision Runoff Problem Confirmed
    Engineer must acknowledge the confirmed runoff problem rather than distort facts
  • Post-Development Runoff Noncompliance
    Facts about noncompliance with runoff standards must be acknowledged accurately
Principle (1)
  • Professional Accountability in Runoff Error
    Acknowledging errors and not distorting facts directly reflects this principle of accountability
Role (1)
  • Principal Engineer R Design Engineer
    Must acknowledge design errors found in the stormwater analysis rather than distort facts
Event (3)
  • Excess Runoff Finding
    Engineer must acknowledge error found in runoff analysis
  • Culvert Insufficiency Finding
    Engineer must acknowledge culvert design error
  • Exacerbation Finding
    Engineer must not distort facts about exacerbation of flooding
Resource (2)
  • NSPE Code of Ethics
    This code provision directly requires acknowledging errors and not distorting facts
  • IBM Runoff Analysis
    Errors found in this runoff analysis must be acknowledged rather than concealed
Capability (3)
  • Engineer R Professional Accountability
    This capability directly involves acknowledging the runoff error without distorting facts.
  • Engineer R Analysis Verification
    Verifying IBM's analysis before acknowledging error relates to truthful acknowledgment of facts.
  • Engineer R Normative Assessment
    This capability explicitly presupposes application of III.1.a to Engineer R's conduct.
III.2.d board + analysis 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.
How this applies in the case (showing 3 of 14)
Obligation
Engineer R Design Standard Compliance
Designing for proper stormwater management aligns with sustainable development principles.
Action
Subdivision Design
Design should incorporate sustainable stormwater management principles
State
City C Stormwater Regulation In Force
Stormwater regulations relate to sustainable development principles for environmental protection
Obligation (2)
  • Engineer R Design Standard Compliance
    Designing for proper stormwater management aligns with sustainable development principles.
  • Firm BWJ Corrective Design Duty
    The corrected design should protect environmental quality for future development.
Action (2)
  • Subdivision Design
    Design should incorporate sustainable stormwater management principles
  • Property Modification Construction
    Remediation construction should follow sustainable development principles
State (2)
  • City C Stormwater Regulation In Force
    Stormwater regulations relate to sustainable development principles for environmental protection
  • Post-Development Runoff Noncompliance
    Noncompliance with runoff standards conflicts with sustainable development principles
Constraint (1)
  • Engineer R Stormwater Runoff Limit
    Limiting post-development runoff supports sustainable development principles protecting environmental quality
Principle (1)
  • Public Welfare in Corrective Design
    Sustainable stormwater management principles support designing a workable corrective solution
Role (1)
  • Principal Engineer R Design Engineer
    Responsible for sustainable stormwater management design protecting environmental quality
Event (2)
  • Excess Runoff Finding
    Runoff management relates to sustainable development principles
  • Property Flooding
    Flooding impacts environmental quality addressed by sustainability
Resource (2)
  • City C Stormwater Regulations
    Limiting post-development runoff supports sustainable environmental protection
  • City C Subdivision Regulations
    Peak flow limits support sustainable stormwater management
Capability (1)
  • Firm BWJ Corrective Design
    Designing a workable stormwater solution reflects sustainable development principles protecting environmental quality.
III.8 board + analysis 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.
How this applies in the case (showing 3 of 20)
Obligation
Engineer R Professional Accountability Duty
Engineer R must accept personal responsibility for the subdivision design he directed.
Action
Subdivision Design
Original engineer bears personal responsibility for design errors causing runoff
State
BWJ Subdivision Design Engagement
Engineer must accept personal responsibility for the subdivision design work performed
Obligation (2)
  • Engineer R Professional Accountability Duty
    Engineer R must accept personal responsibility for the subdivision design he directed.
  • Engineer R Design Standard Compliance
    Engineer R is responsible for ensuring the design meets required stormwater standards.
Action (2)
  • Subdivision Design
    Original engineer bears personal responsibility for design errors causing runoff
  • Error Acknowledgment Remediation
    Engineer must accept personal responsibility for correcting professional errors
State (3)
  • BWJ Subdivision Design Engagement
    Engineer must accept personal responsibility for the subdivision design work performed
  • Insufficient Driveway Culvert Capacity
    Engineer bears responsibility for design deficiencies causing culvert inadequacy
  • Subdivision Runoff Problem Confirmed
    Engineer must accept responsibility for the confirmed runoff problem resulting from the design
Constraint (1)
  • Engineer R Stormwater Runoff Limit
    Engineer R must accept personal responsibility for ensuring the stormwater design meets required limits
Principle (2)
  • Professional Accountability in Runoff Error
    Accepting personal responsibility for professional activities aligns with acknowledging the runoff error
  • Public Welfare in Corrective Design
    Personal responsibility extends to ensuring a workable corrected design is implemented
Role (2)
  • Principal Engineer R Design Engineer
    Must accept personal responsibility for the professional design errors identified
  • Firm BWJ Risk Management Team
    Tasked with addressing responsibility and remediation for the firm's design errors
Event (2)
  • Culvert Insufficiency Finding
    Engineer accepts personal responsibility for design deficiency
  • Excess Runoff Finding
    Engineer accountable for professional runoff analysis error
Resource (2)
  • NSPE Code of Ethics
    This code provision directly addresses personal responsibility for professional activities
  • IBM Runoff Analysis
    The engineer must accept personal responsibility for the accuracy of this analysis
Capability (4)
  • Engineer R Professional Accountability
    This capability directly involves taking personal responsibility for the design he directed.
  • Engineer R Team Convening
    Convening the team to allocate fault relates to accepting personal responsibility for professional activities.
  • Engineer R Normative Assessment
    This capability explicitly presupposes application of III.8 to Engineer R's responsibilities.
  • Firm BWJ Corrective Design
    The firm's duty to correct the design reflects accepting responsibility for professional activities.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 4 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

An engineer transitioning employment during the pendency of a related matter has an ongoing duty to former and current employers/clients and must obtain consent before disclosing or participating in matters implicating the former employer's interests.

Citation Context:

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.

Relevant Excerpts
discussion: "BER Case 14-8 provides a backdrop to consider City Engineer J's situation. In Case 14-8, Engineer A worked for a private company and stamped a water rights analysis for a client..."
discussion: "Unlike Case 14-8 where the transition literally happened in the midst of the project for which the Board was rendering an opinion, in the present case the transition is implied to have been earlier..."

Principle Established:

Engineers, as members of a learned profession, have a basic ethical obligation to accept responsibility for their professional services and to use their skill and expertise for the betterment of society.

Citation Context:

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).

Relevant Excerpts
discussion: "Although dealing with unethical use of an overbroad indemnification clause, BER Case 93-8 provides context for addressing errors: A basic tenet of ethical conduct relates to the obligation of the engineer to accept responsibility..."

Principle Established:

Engineers have an affirmative duty to disclose discovered inaccuracies in underlying data and resulting changes in conclusions to their clients.

Citation Context:

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.

Relevant Excerpts
discussion: "The Board reviewed these facts, and used them, in conjunction with a similar fact set in BER Case 95-5 to conclude that once Engineer A discovered that the data upon which the report was based was inaccurate, there is an affirmative obligation to step forward..."

Principle Established:

An engineer who discovers that data underlying prior work was inaccurate, leading to different conclusions, has an affirmative obligation to inform the client of the inaccuracy and the revised conclusions.

Citation Context:

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.

Relevant Excerpts
discussion: "We turn to BER Case 16-7 for guidance; the case discusses Engineer A's work providing forensic engineering services for attorneys in connection with pending litigation."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 47% Facts Similarity 28% Discussion Similarity 48% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 36% Principle Overlap 50%
Shared provisions: I.1, I.4, I.6, III.1.a Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 67% Discussion Similarity 60% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 53%
Shared provisions: III.2.d Same outcome unclear View Synthesis
Component Similarity 59% Facts Similarity 70% Discussion Similarity 66% Provision Overlap 17% Outcome Alignment 50% Tag Overlap 56% Principle Overlap 59%
Shared provisions: I.1, I.4 View Synthesis
Component Similarity 53% Facts Similarity 53% Discussion Similarity 65% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 53%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 52% Discussion Similarity 65% Provision Overlap 15% Outcome Alignment 50% Tag Overlap 36% Principle Overlap 58%
Shared provisions: I.1, I.4 View Synthesis
Component Similarity 49% Facts Similarity 42% Discussion Similarity 50% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 10% Principle Overlap 60%
Shared provisions: I.1 Same outcome unclear View Synthesis
Component Similarity 53% Facts Similarity 61% Discussion Similarity 53% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 56%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 50% Discussion Similarity 64% Provision Overlap 23% Outcome Alignment 50% Tag Overlap 27% Principle Overlap 60%
Shared provisions: I.4, I.6, II.4.a View Synthesis
Component Similarity 50% Facts Similarity 45% Discussion Similarity 73% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 56%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 52% Discussion Similarity 63% Provision Overlap 22% Outcome Alignment 50% Tag Overlap 33% Principle Overlap 39%
Shared provisions: I.4, I.6 View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

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?

Board conclusion 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.
Resolved by: The Board weighed the abstract possibility of lingering loyalty to a former employer against the concrete evidence of temporal distance and found the latter controlling. (confidence 0.75)
I.4. II.4.a. 2 principles 2 facts Conditions Narrative
Implicit (2)

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?

AnalyticalThe 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.
Resolved by: The Board weighed the nature and scope of J's actual duties against the abstract appearance-of-influence concern, finding that a purely administrative function carries little weight to trigger heightened conflict scrutiny. (confidence 0.75)
I.4. II.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalBecause 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.
Resolved by: The Board weighed the nature of J's review (administrative, non-technical) against the substantive design responsibility held by R and BWJ, concluding responsibility for the deficiency tracks the technical decision-maker rather than the administrative reviewer. (confidence 0.50)
I.4. II.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe 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.
Resolved by: The Board conflated the narrow scope of J's administrative authority with the separate question of whether a disqualifying relationship existed, letting the low-stakes nature of the review substitute for an independent conflict analysis. (confidence 0.70)
II.4.a. 1 principle 3 facts Conditions Narrative

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?

AnalyticalThe 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.
Resolved by: The reviewer treats the appearance-based disclosure duty as analytically independent of the substantive conflict finding, refusing to let the timing rationale that defeats the conflict claim also extinguish the separate disclosure obligation. (confidence 0.75)
II.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalEven 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.
Resolved by: The Board's underlying reasoning weighs the low likelihood of actual bias against the appearance standard in II.4.a, concluding that disclosure would have been the better practice even without an actual conflict, in order to preserve public trust over strict technical compliance. (confidence 0.50)
II.4.a. 2 principles 3 facts Conditions Narrative
Principle tension (1)

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?

AnalyticalThere 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.
Resolved by: The analysis weighs the Board's practical, materiality-based timing reasoning against a textualist reading of II.4.a that would require disclosure irrespective of elapsed time, favoring letting the reviewing body rather than the engineer determine materiality. (confidence 0.50)
II.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe 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.
Resolved by: The appearance-based disclosure duty of II.4.a was effectively displaced by a factual finding that enough time had passed since the employment ended, so temporal remoteness functioned as a substitute for, rather than an application of, the appearance standard. (confidence 0.75)
II.4.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101
Theoretical (2)

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?

AnalyticalFrom 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.
Resolved by: The Board treats the procedural duty to disclose as independent of and prior to any substantive determination of conflict, so a correct no-conflict outcome does not retroactively satisfy an unfulfilled disclosure obligation. (confidence 0.75)
II.4.a. 2 principles 3 facts Conditions Narrative

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?

AnalyticalFrom 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.
Resolved by: The Board separates the consequentialist harm inquiry from the deontic conflict-of-interest inquiry, assigning harm-based accountability to the design function (R) rather than letting it contaminate the procedural conflict finding regarding J. (confidence 0.70)
2 principles 3 facts Conditions Narrative
Counterfactual (2)

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?

AnalyticalIf 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.
Resolved by: The Board weighs actual/appearance-based conflict risk against the reviewer's institutional role, concluding that temporal proximity tips the balance decisively toward disqualification regardless of the review's administrative character. (confidence 0.75)
II.4.a. 2 principles 3 facts Conditions Narrative

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?

Also discussed in: C102 C303
Board Board question 2

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

Board conclusion 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.
Resolved by: The Board subordinated an immediate admission of fault to a prior verification step, treating accurate self-assessment as a precondition for honoring both the error-acknowledgment and public-welfare duties rather than as competing with them. (confidence 0.80)
III.1.a. III.8. 2 principles 3 facts Conditions Narrative
Implicit (2)

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?

AnalyticalThe 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.
Resolved by: The Board balanced the mitigating effect of third-party contributory causation against R's non-delegable design-responsibility duty, concluding that the former can only reduce the magnitude of attributable harm, not eliminate the duty itself. (confidence 0.78)
III.8. III.1.a. 2 principles 3 facts Conditions Narrative

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?

AnalyticalThe 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.
Resolved by: The Board favored the professional-accountability sequence of verify-then-acknowledge but the analysis flags that this sequencing subordinates the immediate public welfare duty under I.1 to a slower verification process. (confidence 0.50)
I.1. III.1.a. III.8. 2 principles 3 facts Conditions Narrative
Principle tension (1)

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?

AnalyticalThe 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.
Resolved by: The Board balanced the duty to hold public welfare paramount (I.1) against the risk that unverified corrective action could itself cause harm, concluding that verification-first is reasonable but should not be allowed to delay urgent interim safety measures. (confidence 0.50)
I.1. III.1.a. III.8. 2 principles 3 facts Conditions Narrative
AnalyticalThe 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.
Resolved by: The Board sequenced professional due process (verifying an actual error before acting) ahead of the immediate public-welfare imperative, treating accurate fact-finding as a precondition for, rather than a competitor to, corrective public-welfare action. (confidence 0.70)
III.1.a. I.1. III.8. 2 principles 3 facts Conditions Narrative
Also discussed in: C104
Theoretical (2)

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?

AnalyticalPrincipal 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.
Resolved by: The Board balances the duty to acknowledge errors promptly against the duty to verify facts before self-incriminating, finding that good-faith re-examination satisfies both without requiring instant admission of fault. (confidence 0.80)
III.1.a. III.8. 2 principles 3 facts Conditions Narrative

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?

Also discussed in: C103
Counterfactual (2)

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?

AnalyticalHad 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.
Resolved by: The Board weighs the general duty to accept independent third-party review against the burden of requiring engineers to re-verify every analysis, resolving in favor of re-review only when a credible discrepancy actually exists. (confidence 0.75)
III.1.a. III.8. 2 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

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?

Options considered:
O1 Affirmatively disclose the prior BWJ principalship to City C at the outset of the review so the client, not the engineer alone, can assess whether recusal is warranted.
O2 Proceed with the review without disclosure, reasoning that the employment transition occurred long ago and therefore poses no realistic conflict. Board's choice
O3 Withhold proactive disclosure but be prepared to disclose the prior employment if City C or affected parties specifically raise the question.
Argument structure (Toulmin):
Grounds

City Engineer J was formerly a principal at Firm BWJ; he later became City Engineer for City C; in that role he administratively reviewed and approved BWJ's subdivision plans; property owners later alleged a conflict of interest based on this employment history.

Warrant

Engineers must disclose to their employer or client all known or potential conflicts of interest, including facts that could merely appear to influence professional judgment (II.4.a); this disclosure duty is independent of whether an actual conflict is later found to exist.

Rebuttal

The duty to disclose would not apply if the employment transition were so remote in time and so unrelated to the specific project that no reasonable observer could perceive influence, and if City C's policy did not require formal disclosure for administrative-only reviews.

City Engineer J Conflict Disclosure Duty

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?

Options considered:
O1 Verify Firm IBM's findings against BWJ's own modeling and design records before making any determination of fault or committing to a corrective design. Board's choice
O2 Accept Firm IBM's findings at face value and immediately acknowledge that the original design was deficient, without independently re-verifying the analysis.
O3 Begin the technical re-review of IBM's analysis while simultaneously recommending interim drainage mitigation for affected properties pending the outcome.
Argument structure (Toulmin):
Grounds

Nearby properties flooded after the subdivision was built; Firm IBM's independent modeling found post-development peak flows larger than pre-development conditions; Engineer R's original design was based on his own runoff calculations; complaints and flooding continued after construction.

Warrant

Engineers must hold paramount the safety and welfare of the public (I.1), but must also avoid distorting facts or reaching conclusions without adequate verification (III.1.a); confirming an error before acting on it protects against corrective measures based on a false premise.

Rebuttal

The verification-first approach would not be justified if Firm IBM's modeling assumptions were known to be materially flawed, or if delay in the face of already-occurring flooding itself created an unacceptable risk to public safety.

Engineer R Error Acknowledgment Duty

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?

Options considered:
O1 Treat the duty to confirm design compliance with the 25-year peak-flow standard as unaffected by the owner's later construction, while separately assessing the owner's contribution to actual damages. Board's choice
O2 Conclude that the owner's paved areas and outbuilding are the dominant cause of the flooding, minimizing BWJ's obligation to re-examine its original design.
O3 Conduct a joint technical assessment to separate the flooding attributable to the original design deficiency from that attributable to the owner's later construction, and calibrate remedial obligations accordingly.
Argument structure (Toulmin):
Grounds

The affected property owner constructed extensive paved areas and a large outbuilding after the subdivision was built; findings show culvert insufficiency and excess runoff; flooding occurred and complaints followed; Engineer R directed the original subdivision design for Developer G.

Warrant

Engineers are responsible for their professional activities and the designs they direct (III.8); this personal responsibility is not discharged merely because other, later-occurring factors also contributed to the harm.

Rebuttal

Engineer R's accountability would not extend to harms shown to result solely from the owner's construction exceeding the capacity the original design was obligated to accommodate, if BWJ's design is independently verified as compliant with the 25-year standard.

Engineer R Professional Accountability Duty

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?

Options considered:
O1 Begin identifying and designing a workable corrective solution for the runoff problem without waiting for a final allocation of fault among the parties.
O2 Delay corrective design work until the risk management team and involved parties have fully determined and allocated fault for the flooding.
O3 Convene the risk management team to work on fault determination and corrective design in parallel so that a workable solution reaches affected citizens without unnecessary delay. Board's choice
Argument structure (Toulmin):
Grounds

Flooding complaints and actual property flooding have occurred; Firm IBM's independent analysis and Engineer R's own review are being used to assess the runoff problem; Firm BWJ directed the original subdivision design for Developer G and continues to serve City C's citizens in that area.

Warrant

Engineers must hold paramount the safety and welfare of the public affected by their work (I.1); a firm responsible for a design that may be deficient must ensure a workable corrected solution is ultimately identified, designed, and constructed to serve the affected citizens.

Rebuttal

Prompt corrective design would not be appropriate if the underlying cause of flooding remained genuinely disputed such that any redesign might target the wrong problem, for example if the owner's construction alone were later shown to be the dominant cause.

Firm BWJ Corrective Design Duty

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?

Options considered:
O1 Confine the review to checking the plans against City C's stated policy requirements, without independently verifying the stormwater engineering calculations. Board's choice
O2 Perform an independent technical evaluation of BWJ's stormwater calculations before approving the plans, treating the review as more than a policy conformance check.
O3 Engage an outside engineering reviewer to verify the stormwater calculations while City Engineer J retains responsibility for the administrative conformance check.
Argument structure (Toulmin):
Grounds

City C's process assigns City Engineer J an administrative review role for conformance with city policy before releasing plans for bidding and construction; Firm BWJ, directed by Engineer R, prepared the subdivision's stormwater design; the plans were subsequently approved and released.

Warrant

A municipal reviewer's authority and responsibility are defined by the scope of the role assigned; where that role is limited to administrative conformance rather than independent engineering verification, technical responsibility for compliance with design standards remains with the design professional of record.

Rebuttal

Limiting review to administrative conformance would not be adequate if City C's policy actually required or implied independent technical verification of stormwater calculations, or if the scope of J's review were ambiguous and interpreted to include substantive engineering judgment.

City Engineer J Plan Review Duty
Event Timeline (15)
15 sequenced 7 actions 8 events
Case timeline
Engineer J left his position as a principal at Firm BWJ to become City Engineer of City C, a transition the Board assumes occurred at least one year before the subdivision work was under contract.
Causal-normative reasoning(confidence 0.60)
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.
State changes (2)
  • began: City Engineer J Prior Employment Conflict
  • ended: BWJ Subdivision Design Engagement
Developer G retained Firm BWJ, under the direction of Principal Engineer R, to develop plans for the new subdivision in City C.
Causal-normative reasoning(confidence 0.50)
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.
State changes (1)
  • began: BWJ Subdivision Design Engagement
Principal Engineer R directed the development of the subdivision plans, including stormwater management design that independent analysis later suggested failed to keep post-development 25-year peak flows at or below pre-development conditions.
At stake (1)
  • Responsibility for Professional Activities (III.8)
Causal-normative reasoning(confidence 0.72)
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.
A property owner constructed extensive paved areas and a large outbuilding on their property, which was later determined to have exacerbated the flooding potential in the vicinity.
Causal-normative reasoning(confidence 0.60)
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.
State changes (1)
  • began: Owner Construction Flood Exacerbation
City Engineer J administratively reviewed the subdivision plans for conformance with City C policy and approved them, despite his former employment as a principal at Firm BWJ, releasing the plans for bidding and construction.
Causal-normative reasoning(confidence 0.70)
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.
State changes (1)
  • began: Approved Plans Released For Construction
Following administrative review and approval by City Engineer J, the subdivision plans are released for bidding and construction under City C procedure.
State changes (1)
  • began: Approved Plans Released For Construction
Construction of the new subdivision designed by Firm BWJ is finished, placing the post-development stormwater condition into effect.
State changes (1)
  • began: Post-Development Runoff Noncompliance
Properties in the vicinity of the completed subdivision experience flooding that causes water damage to homes, an outcome traced to the subdivision design.
State changes (2)
  • began: Subdivision Runoff Problem Confirmed
  • began: Vicinity Property Flooding Hazard
Property owners complain to City C that flooding damage from the subdivision caused water damage to their homes, prompting the city to engage a third-party reviewer.
Property owners complain that City Engineer J is ethically compromised because of his former employment with Firm BWJ, making their concerns broadly known through the community.
State changes (1)
  • began: City Engineer J Prior Employment Conflict
In response to property owner flooding complaints, City C engaged third-party engineering firm IBM to independently review the subdivision design.
Causal-normative reasoning(confidence 0.65)
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.
Firm IBM's independent modeling and analysis finds post-development storm runoff flows substantially larger for the 25-year, two-hour storm event, in conflict with City C's regulatory requirement.
IBM's review determines that one complaining property owner's driveway culvert has insufficient capacity for a 25-year storm event, a contributing factor to the flooding.
IBM's review determines that construction of extensive paved areas and a large outbuilding by one property owner exacerbated the flooding potential in the vicinity.
The Board prescribes that Engineer R should review and verify IBM's analysis against his own work, acknowledge the runoff problem, and convene BWJ's risk management team to address the runoff flow problem and reach a workable corrective design.
Fulfills (2)
  • Acknowledge Errors (III.1.a)
  • Responsibility for Professional Activities (III.8)
Causal-normative reasoning(confidence 0.80)
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.
State changes (1)
  • began: Subdivision Runoff Problem Confirmed
Narrative (6 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer J, the City Engineer for City C, where a new subdivision developed by Developer G was designed by Firm BWJ under Principal Engineer R and submitted for your administrative review against City C's subdivision regulations, which require that post-development 25-year recurrence interval peak stormwater flows not exceed pre-development levels. You reviewed and approved the plans for conformance with City C policy, and the project proceeded through bidding and construction. Before joining City C, you worked as a principal at Firm BWJ, the same firm that designed this subdivision's stormwater plans. After construction, nearby property owners reported flooding damage to their homes, prompting City C to hire Firm IBM to independently review the design. IBM's modeling found substantially larger runoff flows for the 25-year, two-hour storm event post-development, identified insufficient capacity in one property owner's driveway culvert, and noted that another owner's paved areas and outbuilding construction had exacerbated flooding conditions. Property owners have also raised concerns about your prior employment with Firm BWJ and whether it compromised your review of the plans. You now face a series of decisions about disclosure, technical review, and responsibility that will shape how this matter proceeds.

Main characters (6)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Principal Engineer R Roles in this case: Design Engineer

Guided by: Professional Accountability in Runoff Error, Public Welfare in Corrective Design, Conflict of Interest in Plan Approval

Engineer R is obligated to comply with established stormwater design standards, but site specific runoff limitations appear to have made full compliance difficult to achieve within the original design. This tension may explain the design deficiency at the root of the case and raises the question of whether R adequately addressed the constraint or simply proceeded despite it.

The firm's institutional duty to quietly correct the flawed design and manage risk may conflict with Engineer R's personal professional duty to openly acknowledge the original error. A firm-level fix without individual acknowledgment could protect the firm's reputation and liability position while leaving the ethical obligation of transparency to affected parties unmet.

City Engineer J Roles in this case: Municipal Engineer

City Engineer J is obligated to thoroughly review Engineer R's stormwater design plans before municipal approval, but J's recent transition into the role limits familiarity with prior projects, local drainage history, and established review protocols. This constraint may compromise the depth or accuracy of the review even though the duty to review remains in force.

Developer G Roles in this case: Client

Engineer R is obligated to comply with established stormwater design standards, but site specific runoff limitations appear to have made full compliance difficult to achieve within the original design. This tension may explain the design deficiency at the root of the case and raises the question of whether R adequately addressed the constraint or simply proceeded despite it.

City C Roles in this case: Municipality

City Engineer J is obligated to thoroughly review Engineer R's stormwater design plans before municipal approval, but J's recent transition into the role limits familiarity with prior projects, local drainage history, and established review protocols. This constraint may compromise the depth or accuracy of the review even though the duty to review remains in force.

Firm IBM Roles in this case: Reviewing Consultant Engineer
Firm BWJ Roles in this case: Risk Management Team

The firm's institutional duty to quietly correct the flawed design and manage risk may conflict with Engineer R's personal professional duty to openly acknowledge the original error. A firm-level fix without individual acknowledgment could protect the firm's reputation and liability position while leaving the ethical obligation of transparency to affected parties unmet.

Other people involved in the case but not central to the opening narrative.

Engineer R is obligated to comply with established stormwater design standards, but site specific runoff limitations appear to have made full compliance difficult to achieve within the original design. This tension may explain the design deficiency at the root of the case and raises the question of whether R adequately addressed the constraint or simply proceeded despite it.

The firm's institutional duty to quietly correct the flawed design and manage risk may conflict with Engineer R's personal professional duty to openly acknowledge the original error. A firm-level fix without individual acknowledgment could protect the firm's reputation and liability position while leaving the ethical obligation of transparency to affected parties unmet.

City Engineer J is obligated to thoroughly review Engineer R's stormwater design plans before municipal approval, but J's recent transition into the role limits familiarity with prior projects, local drainage history, and established review protocols. This constraint may compromise the depth or accuracy of the review even though the duty to review remains in force.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

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.
Opening States (10)
City Engineer J Prior Employment Conflict City C Stormwater Regulation In Force Vicinity Property Flooding Hazard Post-Development Runoff Noncompliance Insufficient Driveway Culvert Capacity Owner Construction Flood Exacerbation BWJ Subdivision Design Engagement Approved Plans Released For Construction Subdivision Runoff Problem Confirmed Engineer J Transition Timing Uncertainty
Summary
  • The Board's resolution addresses a narrow factual question about the timing of Engineer J's transition rather than engaging with whether J's review was substantively adequate.
  • Introducing J's prior private sector role at BWJ shifts the analysis from a competence concern (unfamiliarity with local protocols) to an unexamined conflict of interest question that the original conflict framing did not raise.
  • By resolving the case on a factual correction rather than an ethical judgment, the Board leaves the deeper tensions around R's compliance difficulty and the firm's transparency obligations unaddressed.

© Licensed under the GNU GPL v3