Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (7)
View Extraction-
Principal Engineer R Error Acknowledgment Stormwater Runoff Exceedance
Acknowledging the stormwater error is necessary to protect public safety and welfare from flooding hazards.
-
Principal Engineer R Proactive Risk Disclosure Client Post-Error Discovery
Promptly disclosing the inaccurate calculations to the client protects public health and welfare by enabling timely corrective action.
-
Firm BWJ Regulatory Stormwater Compliance Remediation City C Subdivision
Designing a corrective stormwater system directly protects the public from excess runoff hazards.
-
Principal Engineer R Watershed Protection Design BWJ Subdivision Stormwater
Ensuring adequate stormwater management protects surrounding communities and the public from drainage harm.
-
Principal Engineer R Regulatory Compliance Verification Stormwater Design
Verifying regulatory compliance through adequate modeling is essential to safeguarding public safety and welfare.
-
R Designs Stormwater Plans
R must design stormwater plans with public safety and welfare paramount to prevent flooding hazards.
-
J Reviews and Approves BWJ Plans
J's review and approval of plans directly governs whether public safety is protected from excess runoff.
-
R Acknowledges Error and Remediates
Remediating the stormwater error is required to restore protection of public safety and welfare.
-
Subdivision Stormwater Regulatory Non-Compliance
Non-compliant stormwater design directly threatens public safety and welfare of neighboring residents.
-
Post-Subdivision Flooding Harm to Neighboring Properties
Flooding of neighboring properties represents a realized harm to public health and welfare.
-
Public Safety Risk from Stormwater Design Deficiency
Neighboring properties and residents face direct safety and welfare risks from the deficient stormwater design.
-
Engineer R Regulatory Standard Exceedance Confirmed
Confirmed exceedance of runoff standards demonstrates a failure to hold public safety paramount.
-
Engineer R Public Safety Paramount Constraint. Stormwater Design Deficiency
I.1 directly creates the paramount public safety obligation that constrains Engineer R to ensure the stormwater design does not create unmitigated flood risk.
-
Engineer R Regulatory Compliance Constraint. City C 25-Year Stormwater Standard
Compliance with the 25-year stormwater standard is grounded in protecting public safety from flood hazards, which I.1 mandates as paramount.
-
Engineer R Post-Approval Error Correction Constraint. IBM Independent Analysis
I.1 requires Engineer R to act on confirmed design deficiencies that threaten public safety once IBM's analysis reveals excess runoff.
-
Temporal Disclosure Urgency Constraint. Engineer R Post-IBM Analysis
I.1 creates urgency for Engineer R to promptly disclose the stormwater deficiency because ongoing public safety risk demands timely action.
-
Firm BWJ Workable Corrective Stormwater Design Implementation City C
I.1 obligates Firm BWJ and Engineer R to move beyond acknowledgment to actual corrective design to protect the public from continued flood risk.
-
Environmental Regulatory Compliance Constraint BWJ Subdivision Stormwater City C
I.1 underpins the obligation to meet stormwater runoff limits because exceeding pre-development levels endangers public health and welfare.
-
Public Welfare Paramount Invoked By BWJ Subdivision Design
The provision directly mandates holding public safety and welfare paramount, which is the core principle violated when the stormwater design caused flooding and property damage.
-
Regulatory Compliance Verification Invoked By BWJ Stormwater Design
Verifying compliance with runoff regulations is a direct mechanism for protecting public welfare from flooding hazards.
-
Principal Engineer R
As the engineer who directed the stormwater design, R had a paramount duty to protect public safety from foreseeable flooding hazards.
-
Principal Engineer R Subdivision Design Engineer
The subdivision stormwater design that allegedly caused flooding directly implicates R's duty to hold public safety paramount.
-
Firm BWJ Subdivision Design Firm
The firm produced a design alleged to cause excess runoff and flooding, implicating the firm's duty to protect public welfare.
-
City Engineer J Municipal Plan Review Engineer
J approved plans despite potential errors, failing the duty to hold public safety paramount in the plan review role.
-
City Engineer J
J's approval of deficient stormwater plans directly implicates the obligation to protect the health and welfare of the public.
-
Neighboring Properties Flood
Flooding of neighboring properties directly threatens the safety, health, and welfare of the public.
-
Property Owners Lodge Complaints
Complaints from property owners signal a failure to protect public welfare, which engineers are obligated to hold paramount.
-
IBM Independent Stormwater Modeling and Analysis
IBM's independent analysis directly assessed whether the public was exposed to flooding risk from the deficient subdivision design.
-
Qualitative Risk Assessment - Flooding Causation Analysis
The risk assessment evaluated flooding hazards affecting public safety, directly implicating the paramount obligation to protect public welfare.
-
Stormwater Management Regulation - City C Peak Flow Requirement
The peak flow regulation exists to protect public safety from flooding, and failure to meet it directly threatens public health and welfare.
-
Independent Engineering Review - IBM Analysis
IBM's independent review identified design deficiencies causing flooding that endangered public safety, invoking the paramount public welfare obligation.
-
Principal Engineer R Proactive Risk Disclosure Client
Holding public safety paramount requires promptly disclosing inaccurate stormwater calculations that pose flood risk to the public.
-
Principal Engineer R Stormwater Risk Assessment
Assessing stormwater runoff risks is directly required to protect public safety and welfare from flooding.
-
Principal Engineer R Stormwater Regulatory Compliance
Verifying regulatory compliance ensures the design protects public safety from excess stormwater runoff.
-
Firm BWJ Stormwater Regulatory Compliance
Organizational compliance verification is necessary to ensure the public is protected from flood hazards.
-
City Engineer J Stormwater Regulatory Compliance Review
Municipal plan review for stormwater compliance directly serves the safety and welfare of the public.
-
Firm IBM Watershed Protection Design Review
Evaluating stormwater systems for adequacy in protecting downstream properties directly serves public safety and welfare.
-
Firm BWJ Corrective Stormwater Remediation Design
Designing corrective stormwater remediation is required to eliminate ongoing flood risk to the public.
-
Principal Engineer R Stormwater Regulatory Compliance Verification
Verifying compliance with post-development stormwater standards is essential to protecting public safety from flooding.
-
Principal Engineer R Professional Seal Competence Verification
Sealing documents only after verifying design adequacy protects the public from unsafe stormwater designs.
-
Principal Engineer R Proactive Risk Disclosure Client Post-Error Discovery
Acting as a faithful agent requires promptly informing the client of the discovered stormwater calculation errors.
-
City Engineer J Former Employer Loyalty Boundary BWJ Transition
Honoring loyalty duties to a former employer and its clients reflects the faithful agent obligation during professional transitions.
-
Firm IBM Objective Complete Reporting Stormwater Independent Review
IBM must report all findings accurately and completely to serve its client faithfully as a trusted agent.
-
R Designs Stormwater Plans
R must act as a faithful agent to the client when designing the stormwater plans.
-
J Reviews and Approves BWJ Plans
J must act as a faithful agent to the city when reviewing and approving the plans.
-
J Departs BWJ for City
J's move from BWJ to the city creates a duty to act as a faithful agent to the new employer.
-
Regulatory Compliance State. City C Subdivision Stormwater
Firm BWJ's obligation to faithfully serve the client includes meeting all applicable regulatory design standards.
-
Engineer J Prior Employment Conflict
City Engineer J's duty as a faithful agent to City C is compromised by approving plans from a former employer.
-
Conflict of Interest State. City Engineer J
Acting as a faithful trustee to City C requires Engineer J to avoid approvals influenced by prior employment ties.
-
Principal Engineer R Post-Approval Error Correction Stormwater Design
I.4 requires Engineer R to act as a faithful agent to the client and employer, which includes correcting design errors rather than defending flawed work.
-
Principal Engineer R Post-Error Risk Management Team Convening BWJ Stormwater
Acting as a faithful agent under I.4 requires Engineer R to engage Firm BWJ's risk management team to address the confirmed error responsibly.
-
City Engineer J Former Employer Loyalty Boundary BWJ Public Role
I.4 defines the faithful agent duty, which constrains City Engineer J from allowing residual loyalty to former employer BWJ to compromise his public role.
-
Loyalty to Former Employer and Client Invoked By City Engineer J via BER 14-8
The provision requires acting as a faithful agent or trustee, which directly relates to the ongoing loyalty duties an engineer retains toward former employers and current public clients.
-
Objectivity Invoked By City Engineer J Plan Review
Acting as a faithful agent or trustee for the city requires objective and impartial plan review free from bias toward a former employer.
-
Principal Engineer R
R owed faithful agency to Developer G as client, requiring honest and competent delivery of the stormwater design services.
-
Principal Engineer R Subdivision Design Engineer
R directed subdivision plans for Developer G and was obligated to act as a faithful agent in executing that work.
-
Firm BWJ Subdivision Design Firm
Firm BWJ was retained by Developer G and owed faithful agency in delivering accurate and code-compliant subdivision plans.
-
City Engineer J Municipal Plan Review Engineer
J served City C as a municipal engineer and owed faithful agency to the city in conducting objective plan reviews.
-
City Engineer J
J's dual history with Firm BWJ and current role with City C raises questions about whether J acted as a faithful agent to City C.
-
Firm IBM Independent Reviewer
IBM was engaged by City C to conduct an objective review and owed faithful agency to City C as its client.
-
Firm IBM Third-Party Engineering Reviewer
IBM was retained by City C to provide independent technical review, obligating it to act as a faithful agent to the city.
-
IBM Confirms Design Non-Compliance
Non-compliance with design standards indicates a failure to act as a faithful agent or trustee for the client.
-
IBM Identifies Contributing Factors
Identifying contributing factors reflects the engineer's duty to act faithfully and transparently on behalf of the client.
-
City C Subdivision Stormwater Regulation - 25-Year Recurrence Interval Standard
Firm BWJ's obligation as faithful agent required designing the subdivision to meet the client city's binding stormwater standard.
-
Stormwater Management Regulation - City C Peak Flow Requirement
Acting as faithful agents, BWJ and Principal Engineer R were obligated to satisfy the regulatory peak flow requirements established by City C.
-
Principal Engineer R Proactive Risk Disclosure Client
Acting as a faithful agent requires promptly advising Developer G and City C of known design errors affecting their interests.
-
Principal Engineer R Risk Management Team Convening
Faithfully serving the client requires convening the risk management team to address confirmed design errors affecting the client.
-
City Engineer J Former Employer Ongoing Duty Recognition
Recognizing ongoing loyalty duties to former employer and clients reflects the faithful agent obligation owed to those parties.
-
Principal Engineer R Fault Allocation Multi-Party Responsibility
Faithfully serving clients requires accurately apportioning responsibility rather than deflecting blame inappropriately.
-
Firm IBM Objective Complete Reporting Independent Review
Providing complete and objective reporting serves the client as a faithful agent by ensuring accurate information for decision-making.
-
Principal Engineer R Error Acknowledgment Stormwater Runoff Exceedance
Acknowledging errors honorably and responsibly upholds the profession's reputation and ethical standards.
-
Principal Engineer R Professional Accountability Directed Stormwater Design
Accepting full professional accountability for work done under one's direction reflects honorable and responsible conduct.
-
City Engineer J Objectivity Plan Review BWJ Subdivision
Conducting an impartial and objective plan review reflects honorable and ethical professional conduct.
-
R Acknowledges Error and Remediates
Acknowledging and remediating the error reflects honorable and responsible professional conduct.
-
J Reviews and Approves BWJ Plans
J must conduct the review responsibly and ethically to uphold the honor of the profession.
-
Engineer R Error Acknowledgment Obligation
Honorable and responsible professional conduct requires Engineer R to acknowledge the design deficiency when credible evidence emerges.
-
Engineer J Prior Employment Conflict Assessment
Engineer J's professional reputation and the honor of the profession are at stake when approving a former employer's work without disclosure.
-
Subdivision Causation Complexity
Responsible and ethical conduct requires honest engagement with causal complexity rather than deflecting accountability.
-
Fact-Grounded Opinion Constraint. Engineer R Defense of Stormwater Design
I.6 requires honorable and responsible conduct, which prohibits Engineer R from publicly defending a design known to be non-compliant.
-
Non-Deception Constraint. City Engineer J Approval Without Recusal Disclosure
I.6 requires honorable and lawful conduct, which is violated when City Engineer J approves work without disclosing his conflict of interest.
-
Principal Engineer R Post-Error Independent Verification Before Acknowledgment IBM
I.6 requires responsible professional conduct, which includes independently verifying IBM's findings before making formal acknowledgments.
-
Professional Accountability Invoked By Principal Engineer R
Conducting oneself honorably and responsibly directly embodies the professional accountability Engineer R must bear for the flawed stormwater design.
-
Objectivity Invoked By City Engineer J Plan Review
Conducting oneself honorably and ethically requires that City Engineer J perform an impartial review untainted by prior employment relationships.
-
Principal Engineer R
R's conduct in producing an allegedly erroneous design and any subsequent response implicates the duty to act honorably and ethically.
-
City Engineer J
J's approval of plans from a former employer without disclosing the prior relationship reflects on the honorable and ethical conduct required of engineers.
-
City Engineer J Municipal Plan Review Engineer
Approving plans with potential errors while having a prior employment relationship with the submitting firm undermines the honor and reputation of the profession.
-
Firm BWJ Subdivision Design Firm
The firm's delivery of a design that allegedly caused public harm implicates its responsibility to conduct itself honorably and ethically.
-
IBM Confirms Design Non-Compliance
Confirming design non-compliance reflects on the honorable and responsible conduct expected of engineers in the profession.
-
NSPE Code of Ethics for Engineers
The NSPE Code is the primary authority defining honorable, responsible, and ethical conduct that upholds the profession's reputation.
-
BER Case 93-8
BER Case 93-8 supports the principle that accepting professional responsibility is foundational to conducting oneself honorably and ethically.
-
Principal Engineer R Professional Accountability Acceptance
Accepting full professional accountability for design errors reflects honorable and responsible conduct that upholds the profession.
-
Principal Engineer R Precedent-Based Ethical Reasoning BER Cases
Applying established ethical precedents to guide conduct reflects responsible and ethical behavior that enhances the profession.
-
Principal Engineer R Error Acknowledgment Obligation Recognition
Recognizing the obligation to acknowledge errors when evidence demands it reflects honorable and ethical professional conduct.
-
City Engineer J Objectivity Plan Review Capability
Conducting impartial plan review free from bias upholds the honorable and ethical conduct expected of the profession.
-
City Engineer J Conflict of Interest Recusal Former Employer BWJ Review
Recusing from reviewing former employer BWJ's plans directly addresses the obligation to disclose and avoid conflicts of interest.
-
City Engineer J Former Employer Loyalty Boundary BWJ Transition
Refraining from participation due to prior loyalty ties is a direct response to the conflict of interest disclosure requirement.
-
City Engineer J Objectivity Plan Review BWJ Subdivision
Maintaining objectivity free from bias arising from prior employment relationships is required by the conflict of interest provision.
-
J Departs BWJ for City
J's prior employment at BWJ creates a potential conflict of interest that must be disclosed when reviewing BWJ plans for the city.
-
J Reviews and Approves BWJ Plans
J reviewing plans from a former employer represents a conflict of interest that must be disclosed.
-
City Engineer J Prior Employment Conflict
Engineer J must disclose the prior employment relationship with Firm BWJ as a known conflict of interest before approving their plans.
-
Conflict of Interest State. City Engineer J
The conflict of interest arising from Engineer J's former employment directly triggers the disclosure obligation under this provision.
-
Engineer J Prior Employment Conflict Assessment
Assessing Engineer J's authority to approve former employer's documents requires evaluating whether the conflict was properly disclosed.
-
Engineer J Temporal Gap Mitigation
The elapsed time since Engineer J's departure from Firm BWJ is relevant to determining whether a disclosable conflict of interest still exists.
-
Non-Deception Constraint. City Engineer J Approval Without Recusal Disclosure
II.4.a directly requires disclosure of conflicts of interest, which City Engineer J violated by approving BWJ's plans without disclosing his prior employment.
-
City Engineer J Prior Employment Recusal Constraint
II.4.a creates the obligation to disclose conflicts that underlies the recusal constraint on City Engineer J regarding his former employer's work.
-
Conflict of Interest Avoidance. City Engineer J Approval of Former Employer
II.4.a directly prohibits exercising approval authority where a conflict of interest from prior employment could influence judgment.
-
City Engineer J Temporal Recency Conflict Assessment BWJ Transition
II.4.a requires assessment and disclosure of conflicts, making temporal proximity of J's transition from BWJ directly relevant to his disclosure obligation.
-
City Engineer J Prior Employment Recusal BWJ Subdivision Plans
II.4.a mandates that City Engineer J evaluate and disclose the potential conflict before reviewing plans submitted by his former employer.
-
Conflict of Interest Recusal Invoked By City Engineer J
The provision explicitly requires disclosure of known or potential conflicts of interest, directly applicable to J reviewing plans from a former employer.
-
Objectivity Invoked By City Engineer J Plan Review
Disclosing conflicts of interest is a prerequisite for ensuring the objectivity and impartiality required in J's plan review role.
-
City Engineer J
J had a prior employment relationship with Firm BWJ and was required to disclose this potential conflict of interest before reviewing their submitted plans.
-
City Engineer J Municipal Plan Review Engineer
J's prior work at Firm BWJ constitutes a known potential conflict of interest that should have been disclosed when reviewing BWJ's subdivision plans.
-
Conflict of Interest Disqualification Standard - City Engineer J Review
This standard directly governs whether City Engineer J was required to disclose and recuse due to a conflict of interest from prior employment with BWJ.
-
Conflict of Interest Disqualification Standard - City Engineer J
This standard applies the disclosure obligation to evaluate whether City Engineer J's prior relationship with BWJ required disclosure or disqualification.
-
BER Case 14-8
BER Case 14-8 provides precedential reasoning establishing that City Engineer J's prior employment with BWJ constitutes a conflict requiring disclosure.
-
City Engineer J Conflict of Interest Recognition
Recognizing that prior employment at Firm BWJ creates a conflict of interest is directly required by the duty to disclose conflicts.
-
City Engineer J Revolving Door Recusal Assessment
Assessing whether recusal is required due to prior employment is necessary to fulfill the conflict disclosure and avoidance obligation.
-
City Engineer J Procurement Conflict Awareness
Perceiving the ethical salience of the revolving-door situation is prerequisite to disclosing the conflict of interest.
-
City Engineer J Causal Reasoning Conflict
Tracing the causal link between prior employment and compromised judgment is required to properly disclose the conflict.
-
City Engineer J Revolving Door Conflict Temporal Assessment
Assessing whether elapsed time extinguishes conflict obligations is necessary to determine what must be disclosed.
-
City Engineer J Conflict of Interest Recognition BWJ Plan Review
Recognizing the conflict when reviewing BWJ plans is directly required by the duty to disclose conflicts that could influence judgment.
-
City Engineer J Objectivity Plan Review Capability
Conducting objective review is required to avoid the appearance of conflict influencing the quality of services.
-
Principal Engineer R Error Acknowledgment Stormwater Runoff Exceedance
This provision directly requires engineers to acknowledge errors rather than distort or conceal them.
-
Principal Engineer R Post-Error Independent Verification IBM Analysis
Independently verifying IBM's analysis before responding ensures facts are not distorted or dismissed without basis.
-
Firm IBM Objective Complete Reporting Stormwater Independent Review
IBM must report all findings accurately without distorting or altering facts in its independent analysis.
-
Principal Engineer R Proactive Risk Disclosure Client Post-Error Discovery
Promptly and accurately disclosing the inaccurate calculations to the client aligns with not distorting or altering the facts.
-
R Acknowledges Error and Remediates
This provision directly governs R's obligation to acknowledge the design error without distorting the facts.
-
Engineer R Error Acknowledgment Obligation
This provision directly requires Engineer R to acknowledge the design error confirmed by IBM's independent analysis rather than distorting the facts.
-
Engineer R Regulatory Standard Exceedance Confirmed
Independent confirmation of the design deficiency creates a factual record that Engineer R must not distort or deny.
-
Subdivision Causation Complexity
Engineer R must not manipulate causal complexity to obscure or alter facts about the design's contribution to flooding.
-
Third-Party Property Owner Actions Complicating Flood Causation
Engineer R must not distort facts by improperly attributing all causation to third parties to avoid acknowledging design errors.
-
Fact-Grounded Opinion Constraint. Engineer R Defense of Stormwater Design
III.1.a prohibits distorting or altering facts, which directly constrains Engineer R from defending the design as compliant when facts show otherwise.
-
Principal Engineer R Post-Approval Error Correction Stormwater Design
III.1.a requires acknowledging errors, which directly creates the constraint on Engineer R to stop defending and instead acknowledge the stormwater calculation error.
-
IBM Causation Complexity Disclosure Constraint. Third-Party Contributing Factors
III.1.a requires that facts not be distorted, obligating IBM to disclose all contributing factors rather than presenting a simplified or misleading causal account.
-
Written Report Completeness Constraint. IBM Independent Review Report
III.1.a requires accurate and complete factual reporting, directly grounding the constraint that IBM's written report must include all relevant findings.
-
Principal Engineer R Causation Complexity Disclosure IBM Analysis Stormwater
III.1.a prohibits distorting facts, requiring Engineer R to disclose all contributing causal factors rather than selectively presenting information.
-
Principal Engineer R Post-Error Independent Verification Before Acknowledgment IBM
III.1.a requires that acknowledgment of errors be grounded in verified facts, supporting the constraint that Engineer R independently verify IBM's analysis first.
-
Error Acknowledgment Obligation Invoked By Principal Engineer R
The provision directly obligates engineers to acknowledge errors and not distort facts, which applies to R's obligation upon discovering the runoff exceedance.
-
Proactive Risk Disclosure Invoked By Principal Engineer R Post-Error Discovery
Acknowledging errors and not distorting facts requires R to proactively disclose the stormwater design deficiency upon being confronted with independent analysis.
-
Principal Engineer R
R is obligated to acknowledge any errors in the stormwater design rather than distorting or concealing the facts about the design deficiencies.
-
Principal Engineer R Subdivision Design Engineer
Upon findings of design errors by IBM, R must acknowledge those errors honestly rather than alter or distort the technical facts.
-
City Engineer J
J must acknowledge any errors in the plan review process and not distort facts regarding the approval of the allegedly deficient plans.
-
Firm BWJ Subdivision Design Firm
The firm is obligated to acknowledge errors identified in its stormwater design rather than disputing or distorting the technical findings.
-
IBM Confirms Design Non-Compliance
Confirming non-compliance requires engineers to acknowledge errors rather than distort or alter the facts.
-
IBM Identifies Contributing Factors
Identifying contributing factors requires honest acknowledgment of the facts without distortion.
-
NSPE Code of Ethics Professional Obligation III.1.a
This entity is the direct normative basis requiring Principal Engineer R to acknowledge and not distort the stormwater calculation errors.
-
IBM Independent Stormwater Modeling and Analysis
IBM's analysis identified the calculation errors that Principal Engineer R is obligated to acknowledge under III.1.a.
-
Independent Engineering Review - IBM Analysis
IBM's independent review provides the technical evidence of errors that triggers Principal Engineer R's obligation to acknowledge those errors.
-
BER Case 16-7
BER Case 16-7 establishes precedential reasoning for the obligation to acknowledge and disclose inaccurate data under III.1.a.
-
BER Case 95-5
BER Case 95-5 reinforces the affirmative obligation to disclose inaccurate data and revise conclusions, directly supporting III.1.a application.
-
Principal Engineer R Design Error Acknowledgment
Identifying and accurately attributing the design error directly fulfills the obligation to acknowledge errors and not distort facts.
-
Principal Engineer R Error Acknowledgment Obligation Recognition
Recognizing the affirmative obligation to acknowledge errors when flooding evidence exists is the core of this provision.
-
Principal Engineer R Professional Accountability Acceptance
Accepting accountability for the design error requires acknowledging it honestly without distorting or altering the facts.
-
Principal Engineer R Independent Verification IBM Analysis
Independently verifying IBM's analysis ensures the engineer accurately understands and does not distort the facts of the design error.
-
Firm IBM Objective Complete Reporting Independent Review
Providing objective and complete reporting ensures facts are not distorted or altered in the independent analysis.
-
Principal Engineer R Fault Allocation Multi-Party Responsibility
Accurately apportioning responsibility among parties requires not distorting facts about who contributed to the design error.
-
Principal Engineer R Watershed Protection Design BWJ Subdivision Stormwater
Protecting the surrounding drainage watershed aligns directly with the sustainable development principle of preserving environmental quality.
-
Firm BWJ Regulatory Stormwater Compliance Remediation City C Subdivision
Implementing a corrective stormwater system supports sustainable development by managing waste water and protecting the natural resource base.
-
Principal Engineer R Regulatory Compliance Verification Stormwater Design
Verifying stormwater design compliance through adequate modeling supports environmental protection consistent with sustainable development principles.
-
R Designs Stormwater Plans
R's stormwater design should adhere to sustainable development principles to protect the environment.
-
R Acknowledges Error and Remediates
Remediation of excess stormwater runoff aligns with the duty to protect environmental quality.
-
Subdivision Stormwater Regulatory Non-Compliance
Non-compliant stormwater design that increases runoff conflicts with the principle of sustainable development and environmental protection.
-
Regulatory Compliance State. City C Subdivision Stormwater
Adhering to stormwater regulations aligns with sustainable development principles to protect the natural environment for future generations.
-
Engineer R Regulatory Standard Exceedance Confirmed
Exceeding pre-development peak flow standards directly contradicts sustainable development principles by degrading environmental quality.
-
Environmental Regulatory Compliance Constraint BWJ Subdivision Stormwater City C
III.2.d encourages sustainable development and environmental protection, directly supporting the constraint to limit post-development runoff to pre-development levels.
-
Engineer R Regulatory Compliance Constraint. City C 25-Year Stormwater Standard
III.2.d's sustainable development principle aligns with and reinforces compliance with stormwater standards designed to protect the natural environment.
-
Firm BWJ Workable Corrective Stormwater Design Implementation City C
III.2.d encourages engineers to protect the environment, supporting the obligation to implement a corrective design that achieves sustainable stormwater management.
-
Environmental Stewardship Invoked By BWJ Subdivision Stormwater Design
The provision directly encourages adherence to sustainable development principles to protect the environment, which is the core obligation implicated by the subdivision stormwater design affecting drainage patterns.
-
Principal Engineer R
R's stormwater design should have adhered to sustainable development principles to protect the natural environment and downstream properties.
-
Principal Engineer R Subdivision Design Engineer
The subdivision stormwater design directly implicates sustainable development principles by affecting runoff, drainage, and environmental quality.
-
Firm BWJ Subdivision Design Firm
As the firm responsible for the stormwater design, BWJ was encouraged to apply sustainable development principles to protect the environment.
-
Developer G Developer Client
Developer G bears authority over project scope and is encouraged to support sustainable development practices in the subdivision's design.
-
Subdivision Construction Completed
The completed subdivision construction should have adhered to sustainable development principles to protect the surrounding environment.
-
Neighboring Properties Flood
Excess stormwater runoff causing flooding reflects a failure to protect environmental quality consistent with sustainable development principles.
-
City C Subdivision Stormwater Regulation - 25-Year Recurrence Interval Standard
The stormwater recurrence interval standard reflects sustainable development principles by regulating environmental impacts of development on drainage systems.
-
Stormwater Management Regulation - City C Peak Flow Requirement
The peak flow requirement directly addresses managing environmental impacts of development, aligning with sustainable development obligations.
-
Qualitative Risk Assessment - Flooding Causation Analysis
The flooding causation analysis assessed environmental consequences of the design deficiency, relevant to the obligation to protect the environment under sustainable development principles.
-
Principal Engineer R Stormwater Regulatory Compliance
Verifying stormwater design compliance directly supports sustainable development by protecting environmental quality and downstream resources.
-
Firm BWJ Stormwater Regulatory Compliance
Organizational stormwater compliance capability is required to protect the environment and natural resources per sustainable development principles.
-
Firm IBM Watershed Protection Design Review
Evaluating stormwater systems for watershed protection directly implements sustainable development principles for future generations.
-
Firm IBM Multi-Causal Flood Attribution
Identifying multiple causes of flooding supports sustainable development by enabling comprehensive environmental protection measures.
-
Firm BWJ Corrective Stormwater Remediation Design
Designing corrective stormwater remediation protects the environment and downstream watershed consistent with sustainable development.
-
Principal Engineer R Stormwater Regulatory Compliance Verification
Verifying post-development stormwater compliance protects environmental quality and natural resources for future generations.
-
Principal Engineer R Professional Accountability Directed Stormwater Design
This provision directly requires engineers to accept personal responsibility for their professional activities, including designs prepared under their direction.
-
Principal Engineer R Post-Error Risk Management Team Convening BWJ
Convening a risk management team to address the error reflects taking personal responsibility for the professional consequences of the design failure.
-
Principal Engineer R Error Acknowledgment Stormwater Runoff Exceedance
Acknowledging the stormwater error is a direct expression of accepting personal responsibility for one's professional activities.
-
R Designs Stormwater Plans
R bears personal professional responsibility for the stormwater design work performed.
-
R Acknowledges Error and Remediates
R must accept personal responsibility for the design error and its consequences.
-
Engineer R Post-Project Harm Materialized
Engineer R must accept personal professional responsibility for the flooding harm resulting from the deficient subdivision design.
-
Engineer R Error Acknowledgment Obligation
Accepting personal responsibility for professional activities requires Engineer R to own the design deficiency identified by independent analysis.
-
Subdivision Causation Complexity
Engineer R cannot deflect personal responsibility by hiding behind causal complexity involving third-party contributions.
-
Post-Subdivision Flooding Harm to Neighboring Properties
The materialized flooding harm to neighbors flows from Engineer R's professional activities for which personal responsibility must be accepted.
-
Principal Engineer R Professional Accountability Stormwater Directed Work
III.8 directly creates the personal responsibility obligation that constrains Engineer R from deflecting accountability for the stormwater design work.
-
Principal Engineer R Post-Approval Error Correction Stormwater Design
III.8 requires accepting personal responsibility for professional activities, which includes owning and correcting the identified stormwater design error.
-
Principal Engineer R Post-Error Risk Management Team Convening BWJ Stormwater
III.8 grounds the obligation for Engineer R to take personal responsibility by actively convening the risk management team to address the error.
-
Professional Accountability Invoked By Principal Engineer R
The provision directly requires engineers to accept personal responsibility for their professional activities, which applies to R's accountability for the stormwater design prepared under R's direction.
-
Error Acknowledgment Obligation Invoked By Principal Engineer R
Accepting personal responsibility for professional activities encompasses owning the errors in the stormwater design rather than deflecting accountability.
-
Principal Engineer R
R must accept personal responsibility for the professional stormwater design work that is alleged to have caused flooding and property damage.
-
Principal Engineer R Subdivision Design Engineer
As the directing engineer on the subdivision design, R bears personal professional responsibility for the alleged design errors.
-
Firm BWJ Subdivision Design Firm
Firm BWJ must accept responsibility for the professional services it rendered in producing the subdivision stormwater design.
-
City Engineer J Municipal Plan Review Engineer
J must accept personal responsibility for the professional decision to approve the subdivision plans in the municipal review role.
-
IBM Confirms Design Non-Compliance
Confirming design non-compliance requires the engineer to accept personal responsibility for the professional activities that led to the deficiency.
-
IBM Identifies Contributing Factors
Identifying contributing factors is part of accepting personal responsibility for the professional activities involved in the project.
-
NSPE Code of Ethics Professional Obligation III.8
This entity is the direct normative basis affirming that Principal Engineer R must accept personal responsibility for the stormwater design errors.
-
BER Case 93-8
BER Case 93-8 is cited to establish the foundational principle that engineers must accept responsibility for their professional services under III.8.
-
Independent Engineering Review - IBM Analysis
IBM's analysis identified the professional errors for which Principal Engineer R bears personal responsibility under III.8.
Cross-Case Connections
View ExtractionExplicit 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:
Engineers have an affirmative obligation to disclose inaccurate data and revised conclusions when errors are discovered in their professional work.
Citation Context:
The Board cited this case alongside BER Case 16-7 as a parallel fact set supporting the principle that engineers must disclose discovered inaccuracies in their work.
Principle Established:
A basic tenet of ethical conduct requires engineers to accept responsibility for the professional services they render, as members of a learned profession possessing skill, knowledge, and expertise expected to be used for the betterment of mankind.
Citation Context:
The Board cited this case to provide context for the fundamental ethical tenet that engineers must accept responsibility for their professional services, even though the case itself dealt with overbroad indemnification clauses.
Principle Established:
Once an engineer discovers that data or analysis upon which a report or design was based is inaccurate, there is an affirmative obligation to advise their client about the inaccurate data and revised conclusions.
Citation Context:
The Board cited this case to establish Principal Engineer R's affirmative obligation to acknowledge and disclose errors in their stormwater design work once inaccuracies are discovered.
Principle Established:
An engineer who transitions from a private firm to a public agency retains ongoing duties to their former employer and client, and cannot participate in matters involving that former employer without obtaining prior consent, particularly when the transition occurs in the midst of a relevant project.
Citation Context:
The Board cited this case to analyze whether City Engineer J faces a conflict of interest due to former employment with Firm BWJ, examining obligations to former employers when transitioning to a new role.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (2 board)
View ExtractionWas 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?
Implicit (4)
Did City Engineer J have an affirmative obligation to proactively disclose his prior employment relationship with Firm BWJ to City C decision-makers before reviewing and approving the subdivision plans, even if the elapsed time since his departure was substantial?
To what extent does the flooding harm to neighboring property owners create an independent ethical obligation for Principal Engineer R to proactively notify affected third parties - not merely the client or City C - of the potential design deficiency, even before a formal error determination is made?
Given that third-party property owner construction - including paved areas and a large outbuilding - contributed to the flooding, does Principal Engineer R bear any ethical responsibility to ensure that the multi-causal nature of the harm is accurately and completely communicated to City C and affected parties, rather than allowing the design deficiency to be treated as the sole cause?
Does the Board's conclusion that Engineer J's transition was 'not recent' rely on an unstated factual assumption about the elapsed time, and if so, what temporal threshold should govern when a former private-sector employment relationship no longer creates an appearance of conflict for a public-sector engineer reviewing that former employer's work?
What are Principal Engineer R's ethical responsibilities under the facts?
Principle tension (4)
Does the principle of Objectivity in City Engineer J's plan review conflict with the principle of Loyalty to Former Employer, in that J's prior professional and financial ties to Firm BWJ may have created - consciously or not - a disposition toward approving rather than rigorously scrutinizing the subdivision plans, even absent any demonstrable bias?
How should Principal Engineer R balance the Error Acknowledgment Obligation - which calls for prompt and honest admission of mistakes - against the principle of Professional Accountability, which may require R to first independently verify Firm IBM's analysis before accepting findings that could expose Firm BWJ to significant legal and professional liability?
Does the principle of Public Welfare Paramount conflict with the principle of Regulatory Compliance Verification in this case, in that strict adherence to the City C 25-year recurrence interval standard may have been technically satisfied on paper while the actual design failed to protect neighboring residents from foreseeable flooding harm - suggesting that regulatory compliance alone is an insufficient proxy for the public welfare obligation?
Does the principle of Conflict of Interest Recusal - which would counsel City Engineer J to step aside from reviewing Firm BWJ's plans - conflict with the principle of Objectivity in plan review, in the sense that recusal itself could be seen as an implicit acknowledgment of bias, while proceeding with review while disclosing the prior relationship might better serve transparency and the public interest if no actual bias exists?
Cross-cutting analytical questions (8)
These questions consider the case as a whole rather than a specific board question above.
Show 8 cross-cutting questionsTheoretical (4)
From a deontological perspective, did City Engineer J fulfill his duty of impartiality by reviewing and approving plans submitted by his former employer Firm BWJ without disclosing his prior employment relationship to affected stakeholders, regardless of whether the elapsed time since his departure was substantial?
From a consequentialist perspective, did the downstream harm of flooding to neighboring properties - confirmed by Firm IBM's independent analysis - demonstrate that City Engineer J's approval of Firm BWJ's stormwater plans produced net negative outcomes that a more rigorous or recused review process might have prevented, thereby undermining the justification for his approval?
From a virtue ethics perspective, did Principal Engineer R demonstrate professional integrity and intellectual honesty by waiting to confirm Firm IBM's findings before acknowledging any error, or does the virtue of candor require a more proactive and immediate response upon learning that post-development stormwater flows substantially exceeded the regulatory standard?
From a deontological perspective, does Principal Engineer R bear an unconditional professional duty to acknowledge the stormwater design error and notify affected parties - including Developer G, City C, and neighboring property owners - independent of whether third-party actions by property owners contributed to the flooding, given that the regulatory non-compliance in the design is a necessary condition of the harm?
Counterfactual (4)
If City Engineer J had formally disclosed his prior employment at Firm BWJ to City C and recused himself from reviewing the subdivision plans - delegating approval authority to an independent municipal reviewer - would the stormwater design deficiency have been identified before construction, and would the flooding harm to neighboring properties have been avoided?
If the temporal gap between City Engineer J's departure from Firm BWJ and his approval of the subdivision plans had been very recent - say, less than one year - would the Board's conclusion that no conflict of interest existed have changed, and what threshold of elapsed time should ethically trigger mandatory recusal in revolving-door scenarios?
If Principal Engineer R had proactively commissioned an independent post-construction stormwater verification study immediately after subdivision completion - before any flooding occurred - would the regulatory non-compliance have been discovered and remediated in time to prevent property damage, and would such proactive verification constitute a best-practice ethical obligation for engineers directing stormwater-sensitive subdivision designs?
If the property owners who constructed extensive paved areas and a large outbuilding had not made those modifications - thereby eliminating the third-party contributing factors identified by Firm IBM - would Firm BWJ's stormwater design alone have been sufficient to cause the observed flooding, and how should Principal Engineer R's error acknowledgment obligation be calibrated when causation is genuinely shared between design deficiency and third-party actions?
Decisions & Arguments (5)
View ExtractionShould City Engineer J recuse himself from reviewing and approving Firm BWJ's subdivision plans, or at minimum proactively disclose his prior employment relationship to City C decision-makers, given that his transition from BWJ to City C may create an appearance of conflict of interest under NSPE Code Section II.4.a?
The Conflict of Interest Recusal obligation (II.4.a) requires J to disclose all known or potential conflicts that could appear to influence his judgment, and to recuse himself if the transition was recent. The Objectivity in Plan Review obligation requires J to conduct a technically substantive, impartial review. The Temporal Recency Conflict Assessment Constraint establishes that transitions of less than one year carry heightened ethical weight requiring recusal or disclosure, while greater temporal distance may sufficiently mitigate the conflict. The Former Employer Loyalty Boundary obligation recognizes that ongoing loyalty duties to BWJ may constrain J's ability to act adversely to BWJ's interests without consent.
The Board found that J's transition was 'not recent,' which under the Temporal Recency Conflict Assessment Constraint substantially diminishes the conflict presumption. If sufficient time elapsed, the financial entanglements and loyalty obligations to BWJ would be attenuated enough to permit objective review. However, the Board's 'not recent' finding rests on an unstated temporal threshold, and Code Section II.4.a's appearance-based standard is not automatically extinguished by elapsed time alone: depth of prior financial stake, absence of ongoing ties, and whether J's prior work directly informed the design methodology are independently relevant variables. The absence of proactive disclosure denied City C the opportunity to make its own informed judgment about reviewer assignment, which is a procedural ethical deficiency independent of whether actual bias existed.
City Engineer J formerly held a principal or ownership role at Firm BWJ before transitioning to City C. Developer G retained Firm BWJ to design a subdivision. J reviewed and approved BWJ's subdivision plans in his capacity as City Engineer without disclosing his prior employment relationship to City C decision-makers. Post-construction, neighboring properties flooded and Firm IBM's independent analysis confirmed the stormwater design was non-compliant. Property owners lodged complaints alleging that J's former employment with BWJ presented a conflict of interest.
Should Principal Engineer R independently verify IBM's findings against BWJ's original calculations before disclosing any design error to Developer G, City C, and affected neighbors, or disclose immediately by accepting IBM's report as dispositive without conducting that independent check?
The Post-Error Independent Verification Before Acknowledgment Obligation requires R to independently review IBM's analysis against R's own original calculations before formally acknowledging error, grounding any acknowledgment in R's own professional judgment rather than uncritical acceptance of external findings. The Error Acknowledgment Obligation (III.1.a) requires R not to distort or suppress facts once errors are known, and to acknowledge the runoff problem confirmed by both empirical flooding evidence and IBM's modeling. The Professional Accountability Obligation (III.8) requires R to accept personal responsibility for the directed stormwater design. The Proactive Risk Disclosure Obligation requires R to promptly advise Developer G and City C once the error is confirmed. The Public Welfare Paramount Obligation (I.1) requires R to ensure affected third parties are not left without timely information necessary to protect themselves from ongoing harm. The Causation Complexity Disclosure Obligation requires R to ensure the multi-causal nature of the flooding, including third-party contributing factors, is accurately and completely communicated, so that neither the design deficiency nor the third-party contributions are overstated or understated.
Uncertainty arises because IBM's identification of third-party contributing factors complicates both the causation analysis and the scope of R's acknowledgment obligation. If third-party property modifications were sufficiently substantial to constitute a concurrent or superseding cause, premature acknowledgment of sole design responsibility could misrepresent the causal picture and expose BWJ to disproportionate liability. The verification process is therefore not merely a delay tactic but a legitimate professional obligation. However, the rebuttal to indefinite deferral is that actual flooding harm has already materialized, making the Public Welfare Paramount principle a temporal constraint: verification must be conducted with urgency, and interim risk disclosure to City C cannot await the conclusion of internal review. Additionally, the regulatory non-compliance in the design is a necessary condition of the harm regardless of third-party contributions, meaning R's acknowledgment duty is not extinguished by shared causation, it is contextualised by it.
Principal Engineer R directed the stormwater design for the BWJ subdivision. Post-construction, neighboring properties flooded. City C engaged Firm IBM for an independent stormwater review. IBM's analysis showed post-development runoff flows exceeded pre-development conditions, in violation of City C's regulatory requirement. IBM also identified third-party contributing factors: an undersized driveway culvert belonging to one property owner, and extensive paved areas and a large outbuilding constructed by another property owner. R subsequently acknowledged the error and undertook remediation. Property owners lodged complaints. The flooding constituted actual, material harm to identifiable third parties.
Should City Engineer J review and approve subdivision plans prepared by Firm BWJ, his former employer, without disclosing his prior employment relationship to City C decision-makers, given that his departure was not recent?
Two competing obligations are in tension: (1) the Objectivity Plan Review obligation. J's duty as City Engineer to conduct rigorous, impartial technical review of submitted plans in his public-sector role; and (2) the Conflict of Interest Recusal obligation, J's duty under Code Section II.4.a to disclose all known or potential conflicts that could appear to influence his judgment, including prior principal-level employment at the firm whose plans he is reviewing. A secondary tension exists between the Former Employer Loyalty Boundary obligation (which recognizes that prior professional and financial ties can create unconscious dispositional bias) and the Temporal Recency Conflict Assessment constraint (which holds that sufficient elapsed time attenuates the conflict to a level where objectivity can be presumed intact).
Uncertainty arises from two directions: First, the Board's 'not recent' finding rests on an unstated temporal assumption: no bright-line threshold is articulated in the NSPE Code or BER precedents, so the rebuttal condition (that elapsed time was long enough to dissolve the conflict) is itself unverifiable without knowing the actual gap. Second, even if elapsed time eliminates substantive conflict, the appearance-of-conflict standard under II.4.a is not automatically extinguished by time alone, other variables including depth of prior financial stake, ongoing professional ties, and project magnitude remain relevant. The impossibility of proving the absence of unconscious bias further complicates the objectivity claim.
City Engineer J formerly worked as a principal at Firm BWJ before transitioning to his public-sector role at City C. Developer G retained Firm BWJ to design a subdivision, and J reviewed and approved the stormwater plans without disclosing his prior employment relationship to City C decision-makers. Post-construction, Firm IBM's independent analysis confirmed the stormwater design was non-compliant with City C's 25-year recurrence interval standard, neighboring properties flooded, and property owners lodged complaints alleging J's review was ethically compromised.
Should Principal Engineer R immediately acknowledge the stormwater design error and proactively communicate the multi-causal nature of the flooding harm to City C and affected parties, or should R first independently verify Firm IBM's analysis before making any acknowledgment, and in either case, how must R handle the third-party contributing factors identified by IBM?
Three interlocking obligations compete: (1) the Error Acknowledgment obligation under Code Section III.1.a, R must not distort or suppress facts once errors are known, and must accept personal responsibility for directed professional activities under III.8; (2) the Post-Error Independent Verification obligation, professional accountability requires R to re-review IBM's analysis and confirm whether an error exists before formally conceding findings that carry significant legal and reputational consequences; and (3) the Causation Complexity Disclosure obligation. Code Section III.1.a's prohibition on distorting facts runs in both directions, requiring R to ensure that the multi-causal nature of the flooding (design deficiency plus third-party modifications) is accurately and completely communicated, neither overstating nor understating R's causal contribution. Overlaying all three is the Public Welfare Paramount obligation under Code Section I.1, which creates an independent proactive duty to ensure affected third-party property owners receive timely information necessary to protect themselves from ongoing harm.
Uncertainty is created by the Contributing Third-Party Action Complicating Causation State: if third-party property owner modifications were sufficiently substantial and independent to constitute a concurrent or superseding cause, R's acknowledgment obligation may be calibrated differently, though not eliminated. A further rebuttal arises from the Fact-Grounded Opinion Constraint: if IBM's analysis is itself methodologically incomplete or attributionally flawed, premature acknowledgment based on IBM's findings alone could expose Firm BWJ to disproportionate liability. The temporal dimension also creates tension: the verification process is legitimate, but the Public Welfare Paramount principle prevents it from becoming an indefinite deferral mechanism when harm has already materialized and affected parties are waiting for remediation.
Principal Engineer R directed Firm BWJ's stormwater design for the City C subdivision. After construction was completed and neighboring properties flooded, property owners lodged complaints. City C engaged Firm IBM for an independent review; IBM confirmed the design was non-compliant with the 25-year recurrence interval standard and identified contributing third-party factors, including a property owner's undersized driveway culvert and extensive paved areas and a large outbuilding constructed by another property owner. R subsequently acknowledged the error and undertook remediation.
Should Principal Engineer R design the stormwater system to meet only City C's 25-year recurrence interval standard and treat regulatory approval as fully discharging the public welfare obligation, or independently assess whether the minimum standard adequately protects neighboring downstream properties given site-specific conditions?
Two foundational obligations are in structural tension: (1) the Regulatory Compliance Verification obligation. R's duty to design the stormwater system in conformance with City C's applicable regulatory standard (25-year recurrence interval), which, if satisfied, constitutes legal compliance and presumptive professional adequacy; and (2) the Public Welfare Paramount obligation under Code Section I.1, R's overriding duty to hold paramount the safety, health, and welfare of the public, which is not fully discharged by demonstrating regulatory compliance when site-specific conditions (proximity to vulnerable downstream properties, foreseeable post-development land use changes) suggest the minimum standard may be inadequate to prevent foreseeable harm. A subsidiary obligation, Watershed Protection Design, reinforces the public welfare warrant by requiring engineers to consider downstream impacts of stormwater design decisions beyond the project boundary.
Uncertainty is generated by the factual ambiguity introduced by IBM's identification of third-party contributing factors: if the flooding resulted partly or primarily from post-construction modifications by neighboring property owners rather than from the design deficiency alone, then the design may have been adequate for the conditions it was designed to address, and the public welfare obligation may have been discharged by regulatory compliance. A further rebuttal arises from the professional standard-of-care question: if the 25-year standard represents the accepted engineering standard of care for this class of subdivision design in City C's jurisdiction, then requiring R to independently assess whether the standard is adequate imposes a supererogatory obligation not grounded in the Code's explicit requirements.
Principal Engineer R designed the stormwater system for the City C subdivision to satisfy the City's 25-year recurrence interval standard. After construction was completed, post-development stormwater flows were found by Firm IBM's independent analysis to substantially exceed pre-development conditions, causing flooding to neighboring properties. IBM also identified third-party contributing factors, including an undersized driveway culvert and extensive impervious surfaces added by neighboring property owners, that exacerbated runoff beyond what the design had anticipated.
Event Timeline (11)
Case timeline
- Prospective duty to avoid situations creating conflicts of interest (NSPE Code III.2. Engineers shall not accept outside employment to the detriment of their regular work or that may impair their judgment)
- Duty to proactively plan for recusal from matters involving former employer (NSPE Code III.2.a, Engineers shall not be influenced by conflicting outside interests)
- Lawful career transition
- No specific NSPE canon prohibits changing employers per se
- Contractual right to select engineering firm of choice
- Obligation to retain licensed engineer for design work
- Implicit duty not to exploit or encourage conflict-of-interest relationships in regulatory review processes
- NSPE Code II.2. Engineers shall perform services only in areas of their competence (if hydrologic methodology was misapplied)
- NSPE Code III.1.a, Engineers shall promptly acknowledge and correct errors (anticipatory obligation; failure materialized post-construction)
- NSPE Code III.8. Engineers shall accept responsibility for their professional activities
- Duty to produce technically accurate work product protective of public safety (NSPE Code I.1)
- Formal production of stormwater calculations and plans as required by City C
- Submission of sealed engineering documents
- Formal administrative completion of plan review function
- Nominal compliance with municipal approval process timeline
- NSPE Code III.2. Engineers shall not be influenced by conflicting interests; shall disclose all known or potential conflicts
- NSPE Code III.2.a, Engineers in public service shall not participate in decisions with respect to services solicited or provided by them or their organizations in private engineering practice
- NSPE Code II.4. Engineers shall act as faithful agents of their employer (City C) by ensuring impartial review
- NSPE Code I.4. Engineers shall act in a manner that upholds and enhances the honor, integrity, and dignity of the profession
- Duty to disclose prior employment relationship to City C supervisors or governing body
- Duty to recuse from review or arrange independent review of BWJ submissions
- Public duty to investigate citizen complaints about infrastructure performance
- Obligation to ensure municipal infrastructure meets adopted standards
- NSPE-aligned principle of seeking competent independent review when internal conflict exists
- Transparency and accountability to affected property owners
- NSPE Code III.1.a, Engineers shall promptly acknowledge errors and omissions and shall make no misrepresentations or omit material facts
- NSPE Code III.8. Engineers shall accept personal responsibility for all professional activities
- BER Case 16-7 and 95-5. Obligation to disclose errors and inaccurate data to clients and the public
- NSPE Code I.1. Protection of public safety and welfare through corrective action
- If acknowledgment is withheld: NSPE Code III.1.a, III.8, and I.1 would all be violated
- Withholding findings under litigation pressure would violate NSPE Code II.3. Engineers shall not attempt to injure the professional reputation of other engineers
Narrative (6 main characters)
View ExtractionOpening 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 Principal Engineer R, the lead engineer at Firm BWJ, an engineering and surveying firm retained by Developer G to design a new residential subdivision in City C, State Q. Your firm prepared stormwater management plans for the subdivision, which were reviewed and approved by City Engineer J before being released for bidding and construction. City C's subdivision regulations require that post-development peak stormwater flows for a 25-year recurrence interval must not exceed pre-development conditions. Following completion of the subdivision, nearby property owners have reported flooding and water damage to their homes, prompting City C to retain Firm IBM as an independent reviewer. Firm IBM's analysis has found that post-development runoff flows for the 25-year, two-hour storm event are substantially larger than pre-development conditions, though investigators also identified a property owner's undersized driveway culvert and unpermitted paved areas and outbuilding as contributing factors. A series of technical, professional, and disclosure decisions now require your attention.
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.
Engineer R bears an obligation to proactively disclose risks to the client immediately upon discovering the stormwater error, consistent with duties of candor and public safety protection. However, the causation complexity disclosure constraint cautions against premature attribution of fault before IBM's independent review has assessed third-party contributing factors (e.g., upstream development, changed watershed conditions). Disclosing the error as solely BWJ's fault before causation is established could be misleading, yet withholding disclosure pending full analysis delays client decision-making and prolongs harm to affected property owners. This tension pits timely transparency against factual accuracy.
Engineer R bears an obligation to proactively disclose risks to the client immediately upon discovering the stormwater error, consistent with duties of candor and public safety protection. However, the causation complexity disclosure constraint cautions against premature attribution of fault before IBM's independent review has assessed third-party contributing factors (e.g., upstream development, changed watershed conditions). Disclosing the error as solely BWJ's fault before causation is established could be misleading, yet withholding disclosure pending full analysis delays client decision-making and prolongs harm to affected property owners. This tension pits timely transparency against factual accuracy.
Engineer R has a professional and ethical obligation to promptly acknowledge the stormwater runoff calculation error once discovered, yet the post-approval correction constraint requires that any error acknowledgment be deferred or conditioned upon completion of IBM's independent analysis. Premature acknowledgment without IBM verification could expose the firm to unwarranted liability if contributing factors (e.g., third-party upstream changes) are later identified, while delayed acknowledgment risks ongoing harm to property owners and regulatory non-compliance. This creates a genuine dilemma between the duty of candor and the procedural integrity of independent verification.
Engineer R bears an obligation to proactively disclose risks to the client immediately upon discovering the stormwater error, consistent with duties of candor and public safety protection. However, the causation complexity disclosure constraint cautions against premature attribution of fault before IBM's independent review has assessed third-party contributing factors (e.g., upstream development, changed watershed conditions). Disclosing the error as solely BWJ's fault before causation is established could be misleading, yet withholding disclosure pending full analysis delays client decision-making and prolongs harm to affected property owners. This tension pits timely transparency against factual accuracy.
Engineer R has a professional and ethical obligation to promptly acknowledge the stormwater runoff calculation error once discovered, yet the post-approval correction constraint requires that any error acknowledgment be deferred or conditioned upon completion of IBM's independent analysis. Premature acknowledgment without IBM verification could expose the firm to unwarranted liability if contributing factors (e.g., third-party upstream changes) are later identified, while delayed acknowledgment risks ongoing harm to property owners and regulatory non-compliance. This creates a genuine dilemma between the duty of candor and the procedural integrity of independent verification.
Tension between Principal Engineer R Error Acknowledgment Stormwater Runoff Exceedance and Principal Engineer R Post-Error Independent Verification IBM Analysis
Tension between Principal Engineer R Post-Error Independent Verification IBM Analysis and Prior Employment Recusal Constraint
Tension between Principal Engineer R Regulatory Compliance Verification Stormwater Design and Principal Engineer R Watershed Protection Design BWJ Subdivision Stormwater
Engineer R bears an obligation to proactively disclose risks to the client immediately upon discovering the stormwater error, consistent with duties of candor and public safety protection. However, the causation complexity disclosure constraint cautions against premature attribution of fault before IBM's independent review has assessed third-party contributing factors (e.g., upstream development, changed watershed conditions). Disclosing the error as solely BWJ's fault before causation is established could be misleading, yet withholding disclosure pending full analysis delays client decision-making and prolongs harm to affected property owners. This tension pits timely transparency against factual accuracy.
Engineer R has a professional and ethical obligation to promptly acknowledge the stormwater runoff calculation error once discovered, yet the post-approval correction constraint requires that any error acknowledgment be deferred or conditioned upon completion of IBM's independent analysis. Premature acknowledgment without IBM verification could expose the firm to unwarranted liability if contributing factors (e.g., third-party upstream changes) are later identified, while delayed acknowledgment risks ongoing harm to property owners and regulatory non-compliance. This creates a genuine dilemma between the duty of candor and the procedural integrity of independent verification.
Tension between City Engineer J Objectivity Plan Review BWJ Subdivision and City Engineer J Conflict of Interest Recusal Former Employer BWJ Review
Tension between City Engineer J Conflict of Interest Recusal Former Employer BWJ Review and Temporal Recency Conflict Assessment Constraint
Other people involved in the case but not central to the opening narrative.
Engineer R has a professional and ethical obligation to promptly acknowledge the stormwater runoff calculation error once discovered, yet the post-approval correction constraint requires that any error acknowledgment be deferred or conditioned upon completion of IBM's independent analysis. Premature acknowledgment without IBM verification could expose the firm to unwarranted liability if contributing factors (e.g., third-party upstream changes) are later identified, while delayed acknowledgment risks ongoing harm to property owners and regulatory non-compliance. This creates a genuine dilemma between the duty of candor and the procedural integrity of independent verification.
Engineer R bears an obligation to proactively disclose risks to the client immediately upon discovering the stormwater error, consistent with duties of candor and public safety protection. However, the causation complexity disclosure constraint cautions against premature attribution of fault before IBM's independent review has assessed third-party contributing factors (e.g., upstream development, changed watershed conditions). Disclosing the error as solely BWJ's fault before causation is established could be misleading, yet withholding disclosure pending full analysis delays client decision-making and prolongs harm to affected property owners. This tension pits timely transparency against factual accuracy.
Opening States (10)
Summary
- The passage of sufficient time between private-sector employment and public-sector roles can neutralize conflict-of-interest concerns, though 'sufficient time' remains contextually defined rather than categorically fixed.
- A stalemate resolution in ethics cases signals that competing obligations are roughly balanced, requiring engineers to exercise professional judgment rather than rely on bright-line rules.
- Post-error independent verification obligations do not automatically dissolve prior-employment recusal constraints, meaning engineers must navigate both duties simultaneously rather than treating one as overriding the other.