Step 4: Full View

Entities, provisions, decisions, and narrative

Balancing Client Directives and Public Welfare: Stormwater Management Dilemma
Step 4 of 5

214

Entities

7

Provisions

11

Precedents

17

Questions

17

Conclusions

Phase Lag

Transformation
Phase Lag Delayed consequences reveal obligations not initially apparent
Engineer L's duty to disclose runoff risk was dormant during the suspension because the risk was unquantified 'speculative concern' rather than a Code-defined 'fact'; the historic rainfall event and subsequent risk study created a temporal gap after which the same underlying risk crystallized into a disclosable, paramount-safety-triggering fact, retroactively reframing what was ethically required in the earlier period (as explored in Q14/C4/C13) without actually changing what occurred at the time.
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 32)
Obligation
Engineer L Watershed Safety Duty
This obligation directly reflects the duty to hold public safety and welfare paramount by protecting the drinking water source
Action
Work Suspension Request
Requesting suspension protects public safety and welfare
State
Drinking Water Source Runoff Risk
Public health is endangered by runoff reaching a drinking water source
Obligation (2)
  • Engineer L Watershed Safety Duty
    This obligation directly reflects the duty to hold public safety and welfare paramount by protecting the drinking water source
  • Engineer L Risk Disclosure Duty
    Disclosing risks to the watershed is necessary to uphold public health and safety as paramount
Action (7)
  • Work Suspension Request
    Requesting suspension protects public safety and welfare
  • Risk Notification
    Notifying of risk upholds paramount duty to public welfare
  • Risk Study Conduct
    Conducting a risk study serves to protect public safety
  • Safeguard Refusal
    Refusing safeguards endangers public welfare violating this duty
  • Refusal to Acquiesce
    Refusing to acquiesce to unsafe directives upholds public welfare
  • Nondisclosure at Suspension
    Failing to disclose risk information endangers public welfare
  • Work Resumption
    Resuming work without addressing risk endangers public safety
State (5)
  • Drinking Water Source Runoff Risk
    Public health is endangered by runoff reaching a drinking water source
  • Confirmed Runoff Risk Finding
    A confirmed risk to public welfare must be held paramount
  • Unquantified Runoff Risk Awareness
    Awareness of potential public risk triggers the paramount safety duty
  • Unsafeguarded Project Failure Risk
    Project failure risk threatens public safety and welfare
  • Public Safety Faithful Agent Conflict
    Public safety must override client loyalty when they conflict
Constraint (2)
  • Engineer L Acquiescence Prohibition
    Public welfare must be held paramount over Client X's insistence to skip protective measures
  • Engineer L Faithful Agent Limit
    Paramount duty to public safety limits how far Engineer L can act as agent for Client X
Principle (2)
  • Public Welfare in Watershed Protection
    Engineer L's concern for the drinking water source directly reflects holding public welfare paramount
  • Public Welfare in Stormwater Design
    Once the risk is confirmed, public welfare must override client acquiescence per this provision
Role (2)
  • Engineer L Public Responsibility
    This role directly embodies the duty to protect public health through the drinking water source
  • Engineer L Design Engineer
    As the engineer of record he must prioritize public safety and welfare in the stormwater design
Event (4)
  • Risk Concern Emergence
    Public safety concern arises when stormwater risk is first identified
  • Historic Heavy Rainfall
    Extreme rainfall event tests public welfare protections
  • Stormwater Accumulation Increase
    Increased accumulation directly threatens public safety and property
  • Risk Established as Fact
    Confirmed risk requires paramount attention to public welfare
Resource (3)
  • NSPE Code of Ethics
    This resource directly covers the engineers paramount duty to public safety health and welfare
  • BER Case 22-5
    This case emphasizes primary responsibility to public health safety and welfare regarding safe drinking water
  • BER Case 76-4
    This case serves as foundational precedent for environmental ethics tied to public welfare
Capability (5)
  • Engineer L Risk Assessment
    Assessing public water risk directly serves the paramount duty to protect public health and safety.
  • Engineer L Work Refusal Judgment
    Refusing to proceed without protective measures upholds public welfare over client wishes.
  • Engineer L Risk Disclosure
    Disclosing risk to drinking water protects public health as paramount duty requires.
  • Engineer L Protective Measures Advisory
    Advising added protections safeguards public welfare against runoff risk.
  • Engineer L Standards Assessment
    Applying environmental standards to protect water sources reflects the duty to public welfare.
I.4 board + analysis Act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 15)
Obligation
Engineer L Faithful Agent Duty
This obligation is a direct statement of the faithful agent or trustee duty owed to the client
Action
Contract Acceptance
Accepting the contract establishes the agent-client relationship
State
Client X Budget Constraint
Engineer must still act faithfully despite client budget pressures
Obligation (1)
  • Engineer L Faithful Agent Duty
    This obligation is a direct statement of the faithful agent or trustee duty owed to the client
Action (2)
  • Contract Acceptance
    Accepting the contract establishes the agent-client relationship
  • Work Suspension Request
    Acting as faithful agent includes advising client of concerns
State (3)
  • Client X Budget Constraint
    Engineer must still act faithfully despite client budget pressures
  • Public Safety Faithful Agent Conflict
    Directly addresses tension between faithful agency and public welfare
  • Stormwater Contract Work Suspension
    Suspension decisions affect the engineer's faithful agent duties to client
Constraint (1)
  • Engineer L Faithful Agent Limit
    Defines the faithful agent duty that is being limited by public welfare concerns
Principle (1)
  • Loyalty to Client X
    Acting as a faithful agent supports honoring Client X's request during the first phase
Role (2)
  • Engineer L Faithful Agent
    This role explicitly frames Engineer L's obligations as a faithful agent or trustee to Client X
  • Client X Development Client
    The client relationship defines the trust and agency duties owed by Engineer L
Event (2)
  • Client Financial Setback
    Faithful agency duty is tested when client faces financial hardship
  • Client Financial Recovery
    Engineer must balance client interests as agent during recovery phase
Resource (1)
  • NSPE Code of Ethics
    This resource covers faithful agency to the client as a core ethical duty
Capability (2)
  • Engineer L Stormwater Design
    Engineer L acts as a faithful agent by fulfilling the contracted design responsibility for the client.
  • Engineer L Risk Disclosure
    Notifying the client of risk fulfills the duty of faithful agency while balancing public interest.
II.1.a board + analysis If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
How this applies in the case (showing 3 of 18)
Obligation
Engineer L Risk Disclosure Duty
If judgment on watershed risk is overruled the engineer must notify the client and other appropriate authority
Action
Risk Notification
Notifying employer or authority when judgment is overruled is required
State
Confirmed Runoff Risk Finding
Overruled judgment on a confirmed risk requires notifying appropriate authorities
Obligation (2)
  • Engineer L Risk Disclosure Duty
    If judgment on watershed risk is overruled the engineer must notify the client and other appropriate authority
  • Engineer L Watershed Safety Duty
    Endangerment of the public water source requires notification to appropriate parties if overruled
Action (3)
  • Risk Notification
    Notifying employer or authority when judgment is overruled is required
  • Refusal to Acquiesce
    Refusing to accept overruled judgment aligns with notification duty
  • Work Resumption
    Resuming despite overruled safety judgment triggers notification obligation
State (4)
  • Confirmed Runoff Risk Finding
    Overruled judgment on a confirmed risk requires notifying appropriate authorities
  • Risk Nondisclosure During Suspension
    Failure to disclose risk during suspension conflicts with duty to notify authorities
  • Stormwater Contract Work Suspension
    Suspension without addressing risk may require notification to other authorities
  • Deferred Environmental Compliance
    Deferred compliance endangering property may require notification
Constraint (2)
  • Engineer L Acquiescence Prohibition
    Requires notification of appropriate authority rather than acquiescing when judgment is overruled endangering property
  • Engineer L Faithful Agent Limit
    Overruled judgment on protective measures requires escalation rather than compliance
Principle (1)
  • Public Welfare in Stormwater Design
    This provision requires notification when judgment is overruled and public safety is endangered
Role (2)
  • Engineer L Design Engineer
    He must notify the client and appropriate authority if his judgment on public risk is overruled
  • Client X Development Client
    The client is the party who must be notified when the engineer's professional judgment is overruled
Event (2)
  • Risk Concern Emergence
    Engineer must notify appropriate parties when judgment about risk is overruled
  • Risk Established as Fact
    Confirmed danger to property requires notification to client or authority
Capability (2)
  • Engineer L Work Refusal Judgment
    This provision requires notifying appropriate authorities when judgment is overruled and safety is endangered.
  • Engineer L Risk Disclosure
    Notifying the client of danger aligns with the requirement to alert relevant parties when risk exists.
II.3.a board + analysis Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.
How this applies in the case (showing 3 of 19)
Obligation
Engineer L Risk Disclosure Duty
Disclosure of risk must be objective truthful and include all relevant information
Action
Risk Study Conduct
Objective and truthful reporting is required in conducting the risk study
State
Risk Nondisclosure During Suspension
Withholding relevant risk information violates truthful and complete reporting duty
Obligation (1)
  • Engineer L Risk Disclosure Duty
    Disclosure of risk must be objective truthful and include all relevant information
Action (2)
  • Risk Study Conduct
    Objective and truthful reporting is required in conducting the risk study
  • Nondisclosure at Suspension
    Omitting relevant information at suspension violates truthful reporting duty
State (3)
  • Risk Nondisclosure During Suspension
    Withholding relevant risk information violates truthful and complete reporting duty
  • Unquantified Runoff Risk Awareness
    Known but unquantified risks must be included in reports for completeness
  • Confirmed Runoff Risk Finding
    Confirmed findings must be objectively and fully reported
Principle (2)
  • Transparency in Risk Disclosure
    Objective and truthful reporting requires disclosing the increased risk once known
  • Transparency of Risk to Client
    This provision defines when disclosure of risk information becomes mandatory versus prudent
Role (1)
  • Engineer L Design Engineer
    He must ensure his professional reports on the stormwater system are objective and complete
Event (2)
  • Risk Concern Emergence
    Reports must objectively include the emerging risk information
  • Risk Established as Fact
    Truthful reporting requires disclosure of confirmed risk facts
Resource (6)
  • BER Case 89-7
    This case addresses disclosure of safety violations confided by the client as relevant facts
  • BER Case 99-8
    This case addresses disclosure of incomplete drawings and specifications as relevant facts
  • BER Case 04-8
    This case addresses disclosure of violations of laws and regulations as relevant facts
  • BER Case 18-9
    This case addresses disclosure of future public safety risks from surge level rise as relevant facts
  • BER Case 21-2
    This case addresses disclosure of climate change effects on sea level and precipitation as relevant facts
  • BER Case 07-6
    This case addresses disclosure of threats to a bird species as a relevant fact
Capability (2)
  • Engineer L Risk Assessment
    Objective and truthful reporting is required when quantifying and presenting rainfall and runoff risk.
  • BER Concern Versus Fact Distinction
    This provision underlies the Board's distinction between preliminary concern and factually substantiated risk in reports.
II.3.b board + analysis Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter.
How this applies in the case (showing 3 of 7)
Action
Risk Notification
Publicly expressing technical risk opinions must be founded on facts and competence
State
Confirmed Runoff Risk Finding
Engineer may publicly express technical opinion based on confirmed facts
Principle
Fact-Based Opinion by Engineer L
This provision establishes the fact-founded standard applied to evaluate Engineer L's evolving concern
Action (1)
  • Risk Notification
    Publicly expressing technical risk opinions must be founded on facts and competence
State (2)
  • Confirmed Runoff Risk Finding
    Engineer may publicly express technical opinion based on confirmed facts
  • Drinking Water Source Runoff Risk
    Public technical opinion may be warranted given risk to drinking water
Principle (1)
  • Fact-Based Opinion by Engineer L
    This provision establishes the fact-founded standard applied to evaluate Engineer L's evolving concern
Role (1)
  • Engineer L Public Responsibility
    He may publicly express technical opinions on the risk to the water source based on his expertise
Capability (2)
  • Engineer L Standards Assessment
    Engineer L's technical opinion on environmental standards is grounded in factual competence as this provision requires.
  • Engineer L Protective Measures Advisory
    Advising on protective measures reflects a technical opinion based on factual knowledge and competence.
III.1.b board + analysis Engineers shall advise their clients or employers when they believe a project will not be successful.
How this applies in the case (showing 3 of 17)
Obligation
Engineer L Unsuccessful Project Advisory Duty
This obligation directly mirrors the duty to advise clients when a project will not be successful
Action
Work Suspension Request
Advising client of unsuccessful project aligns with suspension request
State
Unsafeguarded Project Failure Risk
Engineer must advise client if project risks failure
Obligation (1)
  • Engineer L Unsuccessful Project Advisory Duty
    This obligation directly mirrors the duty to advise clients when a project will not be successful
Action (2)
  • Work Suspension Request
    Advising client of unsuccessful project aligns with suspension request
  • Risk Notification
    Advising client of risks that threaten project success
State (3)
  • Unsafeguarded Project Failure Risk
    Engineer must advise client if project risks failure
  • Client X Budget Constraint
    Engineer should advise client if budget constraints threaten project success
  • Deferred Environmental Compliance
    Deferring compliance may render the project unsuccessful and should be disclosed
Constraint (2)
  • Engineer L Acquiescence Prohibition
    Engineer L must advise client the project will not succeed without proper protective measures instead of acquiescing
  • Engineer L Faithful Agent Limit
    Faithful agency requires advising client of project failure risk rather than silent compliance
Principle (2)
  • Public Welfare in Stormwater Design
    Engineer L must advise the client that the project poses unacceptable risk once the concern is confirmed
  • Transparency of Risk to Client
    This provision underlies the duty to advise clients once risks become material
Role (2)
  • Engineer L Design Engineer
    He must advise the client if the stormwater project poses risks that could cause it to fail
  • Client X Development Client
    The client must be advised by the engineer regarding project viability and risks
Event (2)
  • Risk Concern Emergence
    Engineer should advise client when project risk emerges threatening success
  • Risk Established as Fact
    Confirmed risk means engineer must advise client project may fail
Resource (1)
  • BER Case 84-5
    This case directly addresses engineers advising clients when a project will be unsuccessful
Capability (2)
  • Engineer L Risk Disclosure
    Advising the client of risk aligns with the duty to warn when a project may not succeed safely.
  • Engineer L Work Refusal Judgment
    Refusing to continue without safeguards reflects the duty to advise against an unsuccessful or unsafe project.
III.3.a board + analysis Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
How this applies in the case (showing 3 of 16)
Obligation
Engineer L Risk Disclosure Duty
Failing to disclose the stormwater risk would constitute omission of a material fact
Action
Nondisclosure at Suspension
Omitting material facts at suspension is a material misrepresentation
State
Risk Nondisclosure During Suspension
Omitting known risk during suspension is a material misrepresentation by omission
Obligation (1)
  • Engineer L Risk Disclosure Duty
    Failing to disclose the stormwater risk would constitute omission of a material fact
Action (1)
  • Nondisclosure at Suspension
    Omitting material facts at suspension is a material misrepresentation
State (2)
  • Risk Nondisclosure During Suspension
    Omitting known risk during suspension is a material misrepresentation by omission
  • Deferred Environmental Compliance
    Deferring compliance without disclosure omits a material fact
Principle (1)
  • Transparency in Risk Disclosure
    Omitting the known risk during communications constitutes a material omission under this provision
Role (1)
  • Engineer L Design Engineer
    He must avoid omitting material facts about the water source risk in his statements
Event (2)
  • Risk Concern Emergence
    Omitting known risk concerns would misrepresent material facts
  • Risk Established as Fact
    Withholding established risk fact constitutes material misrepresentation
Resource (6)
  • BER Case 89-7
    This case involves omission of safety violation facts constituting material misrepresentation
  • BER Case 99-8
    This case involves omission of incomplete drawings and specifications as material facts
  • BER Case 04-8
    This case involves omission of legal violations as material facts
  • BER Case 18-9
    This case involves omission of future surge risk as a material fact
  • BER Case 21-2
    This case involves omission of climate change effects as material facts
  • BER Case 07-6
    This case involves omission of bird species threat as a material fact
Capability (2)
  • Engineer L Risk Assessment
    Avoiding omission of material facts applies to the thorough risk quantification process.
  • BER Concern Versus Fact Distinction
    This provision informs how the Board differentiates unsubstantiated concern from material fact misrepresentation.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 11 Lineage Graph

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

Principle Established:

An engineer's duty to protect public safety, health, and welfare is paramount and can require disclosure to authorities even against a client's wishes, once facts establishing risk are known.

Citation Context:

Used as a foundational case establishing that an engineer's duty to the public is paramount, even when it conflicts with client instructions; the Board reviews its facts and conclusions as the starting point for the present analysis.

Relevant Excerpts
discussion: "BER Case 76-4 provides a foundation that other BER cases have built upon, and it is appropriate to review the facts and conclusions of that case as we start our analysis."
discussion: "In BER Case 76-4, the BER concluded that Doe had an obligation to report his findings to the Pollution Control Authority"

Principle Established:

It is basic to the entire concept of a profession that its members devote their interests to the public welfare, as required by the Code's ethics sections.

Citation Context:

Quoted within the discussion of Case 76-4 to reinforce the foundational principle that professional engineers must devote their interests to public welfare as required by the Code.

Relevant Excerpts
discussion: "they quoted BER Case 67-10 which stated, "[i]t is basic to the entire concept of a profession that its members will devote their interests to the public welfare...""

Principle Established:

Engineers must include all relevant and pertinent facts, including known risks, in reports submitted to public authorities under Code section II.3.a; disclosure is required once information rises to the level of established fact.

Citation Context:

Discussed as a classic disclosure case where an engineer failed to include known material facts (threat to a species) in a written report; later contrasted with Engineer L's situation because Engineer L's initial concern was not yet an established 'fact.'

Relevant Excerpts
discussion: "A classic example of "the disclosure question" forms the crux of BER Case 07-6."
discussion: "In contrast to these prior cases, the present case states that Engineer L is concerned about increased risk over time, but has not developed their work to a point where they can assess risks..."

Principle Established:

Code section III.1.b requires engineers to inform clients when they believe a project will not be successful, including from a safety standpoint; continuing to work despite a client's refusal to fund necessary safety measures violates the engineer's paramount obligation to public welfare under section II.1.a.

Citation Context:

Cited and discussed in detail as a direct parallel case where an engineer notified a client of a safety concern (need for an on-site representative) that the client resisted funding due to cost, and the engineer improperly continued work; the Board applies this precedent to conclude Engineer L cannot ethically continue without proper safeguards.

Relevant Excerpts
discussion: "BER Case 84-5 is one such case."
discussion: "We note a direct parallel between the 1984 case and the facts under consideration."

Principle Established:

Known safety violations confided by a client constitute facts that may require disclosure under the Code.

Citation Context:

Listed as an example of similar facts requiring disclosure (safety violations confided by the client), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Relevant Excerpts
discussion: "Similar facts requiring disclosure appear in BER Case 89-7 (safety violations confided by the Client)"

Principle Established:

Engineers have a primary responsibility to protect public health, safety and welfare, with particular emphasis on safe drinking water.

Citation Context:

Cited alongside Case 22-5 to establish the Board's recent emphasis on an engineer's primary responsibility to public health, safety and welfare, particularly regarding safe drinking water.

Relevant Excerpts
discussion: "Several recent cases, including BER Case 22-5 and BER Case 20-4, emphasize an engineer's primary responsibility to public health, safety and welfare with an emphasis on safe drinking water."

Principle Established:

Engineers have a primary responsibility to protect public health, safety and welfare, with particular emphasis on safe drinking water.

Citation Context:

Cited alongside Case 20-4 to establish the Board's recent emphasis on an engineer's primary responsibility to public health, safety and welfare, particularly regarding safe drinking water.

Relevant Excerpts
discussion: "Several recent cases, including BER Case 22-5 and BER Case 20-4, emphasize an engineer's primary responsibility to public health, safety and welfare with an emphasis on safe drinking water."

Principle Established:

Incomplete drawings and specifications constitute facts that may require disclosure under the Code.

Citation Context:

Listed as an example of similar facts requiring disclosure (incomplete drawings and specifications), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Relevant Excerpts
discussion: "BER Case 99-8 (incomplete drawings and specifications)"

Principle Established:

Violations of federal and state laws and regulations constitute facts that may require disclosure under the Code.

Citation Context:

Listed as an example of similar facts requiring disclosure (violation of federal and state laws and regulations), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Relevant Excerpts
discussion: "BER Case 04-8 (violation of federal and state laws and regulations)"

Principle Established:

A known public safety risk from future surge level rise constitutes a fact that may require disclosure under the Code.

Citation Context:

Listed as an example of similar facts requiring disclosure (public safety risk of future surge level rise), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Relevant Excerpts
discussion: "BER Case 18-9 (public safety risk of future surge level rise)"

Principle Established:

Known effects of sea level rise and changing precipitation patterns due to climate change constitute facts that may require disclosure under the Code.

Citation Context:

Listed as an example of similar facts requiring disclosure (effects of sea level rise and changes in precipitation from climate change), then contrasted with Engineer L's situation where the risk was not yet a confirmed fact.

Relevant Excerpts
discussion: "BER Case 21-2 (effects of sea level rise and changes in precipitation intensities and recurrence intervals effected by on-going climate change.)"
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 67% Facts Similarity 56% Discussion Similarity 60% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 44% Principle Overlap 77%
Shared provisions: I.1, I.4, II.3.A, III.1.B Same outcome ethical View Synthesis
Component Similarity 56% Facts Similarity 51% Discussion Similarity 80% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 57% Principle Overlap 73%
Shared provisions: I.1, I.4, III.1.B Same outcome ethical View Synthesis
Component Similarity 53% Facts Similarity 36% Discussion Similarity 45% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 61%
Shared provisions: I.1, I.4, II.3.A, III.3.A Same outcome ethical View Synthesis
Component Similarity 56% Facts Similarity 46% Discussion Similarity 61% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 11% Principle Overlap 60%
Shared provisions: I.1 Same outcome ethical View Synthesis
Component Similarity 53% Facts Similarity 47% Discussion Similarity 48% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 71%
Shared provisions: I.4 Same outcome ethical View Synthesis
Component Similarity 51% Facts Similarity 48% Discussion Similarity 33% Outcome Alignment 100% Tag Overlap 50% Principle Overlap 64%
Same outcome ethical View Synthesis
Component Similarity 53% Facts Similarity 56% Discussion Similarity 47% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 75%
Same outcome ethical 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 50% Facts Similarity 35% Discussion Similarity 53% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 77%
Same outcome ethical View Synthesis
Component Similarity 47% Facts Similarity 45% Discussion Similarity 55% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 67%
Shared provisions: I.4 Same outcome ethical View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Was it ethical for Engineer L to cease work when requested by Client X, without voicing concern about increased risk?

Board conclusion It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk. Later, Engineer L did comply with Code provisions that require engineers to notify their employers or clients if a project will not be successful.
Resolved by: Faithful agency toward Client X's suspension request was allowed to prevail over disclosure obligations because the underlying concern had not yet matured into a founded, fact-based determination. (confidence 0.82)
II.3.a. II.3.b. III.1.b. 3 principles 3 facts Conditions Narrative
Implicit (1)

Did Engineer L have an ethical duty to at least flag the existence of an unquantified but plausible increased risk to Client X at the time of suspension, even without full quantification, given the paramount duty to public health and safety?

AnalyticalThe Board's finding that Engineer L acted ethically in staying silent during suspension rests on a critical distinction between a speculative, unquantified concern and a verified fact. Under II.3.a and II.3.b, engineers are only obligated to disclose founded, evidence-based determinations, not preliminary hunches. Since Engineer L had not yet completed the risk assessment, the concern did not yet rise to the level of a 'fact' requiring disclosure under III.3.a. This suggests the Board's conclusion is contingent on the epistemic status of the risk at the time of suspension, not simply on the act of ceasing work itself.
Resolved by: The obligation to disclose was subordinated to the requirement that disclosed opinions be fact-based, since an unverified concern does not yet trigger the truthfulness and non-omission duties. (confidence 0.80)
II.3.a. II.3.b. III.3.a. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, the Board's own distinction between a 'concern' and a 'fact' (as reflected in cases like BER Case 89-7, BER Case 99-8, and BER Case 04-8) implies that Engineer L had no strict ethical duty to disclose the unquantified risk at the time of suspension. Code provisions II.3.a and II.3.b require engineers to be objective and to found opinions on known facts; since the risk had not yet been quantified or established, it remained speculative rather than a disclosable fact. However, this does not foreclose the possibility that prudent practice would have counseled at least a general mention of an emerging concern, even without full quantification, to keep the client informed as the paramount public welfare obligation in I.1 looms in the background.
Resolved by: The objectivity and fact-based opinion duty under II.3.a and II.3.b is weighed against the paramount public welfare duty of I.1, with the former prevailing because the risk had not yet crystallized into a verifiable fact. (confidence 0.80)
II.3.a. II.3.b. 3 principles 3 facts Conditions Narrative
Principle tension (2)

Does Transparency in Risk Disclosure conflict with Loyalty to Client X in the period before suspension, when Engineer L withheld mention of a still-unquantified risk rather than raising it despite the client's financial distress?

AnalyticalDuring the suspension period, the apparent tension between Transparency in Risk Disclosure and Loyalty to Client X was resolved not by subordinating one principle to the other, but by a prior gating principle: Fact-Based Opinion. Because Engineer L's concern was still qualitative and unquantified, it did not yet rise to the level of a 'fact' that Code provisions II.3.a and II.3.b require engineers to disclose. This meant Loyalty to Client X and the duty to avoid speculative or unfounded statements pointed in the same direction, dissolving what might otherwise look like a conflict between candor and client fidelity. The case shows that Transparency obligations are epistemically triggered, not automatically weighed against loyalty at all times.
Resolved by: The board used the fact-based opinion requirement as a gating principle, finding that because the risk was not yet an established fact, transparency and loyalty pointed in the same direction rather than conflicting. (confidence 0.83)
II.3.a. II.3.b. 3 principles 3 facts Conditions Narrative

How does Fact-Based Opinion by Engineer L constrain Transparency of Risk to Client, given that engineers are expected to voice only founded, evidence-based concerns rather than speculative ones during the suspension period?

Also discussed in: C301
Theoretical (1)

From a deontological perspective, did Engineer L fulfill the duty of faithful agency to Client X by ceasing work without raising the unquantified risk, given the competing paramount duty to public health and safety?

AnalyticalRegarding Q301, from a deontological perspective Engineer L's duty of faithful agency to Client X (I.4) was not violated by ceasing work without voicing the unquantified concern, because faithful agency duties do not require disclosure of speculative, unverified risks. The paramount duty to public health and safety under I.1 only becomes operative as a competing duty once the risk is sufficiently established as fact; prior to that point, no genuine deontological conflict existed between the two duties.
Resolved by: The deontological analysis treats faithful agency and paramount public welfare as sequential rather than conflicting duties, so no actual clash arose while the risk remained unestablished. (confidence 0.78)
I.4. I.1. II.3.a. 3 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer L had already quantified the increased runoff risk before Client X requested the work suspension, would the Board still have concluded that ceasing work without voicing concern was not unethical?

AnalyticalHad Engineer L already quantified the increased runoff risk before Client X requested suspension, the ethical calculus would likely have shifted: the concern would then constitute a material fact under III.3.a and I.1, obligating disclosure regardless of the client's financial distress or the inconvenience of the timing. This indicates the Board's first conclusion is time- and knowledge-dependent, not a general license for engineers to withhold known risks during contract suspensions.
Resolved by: If the risk were already a material fact, the disclosure obligation under III.3.a and the paramount public safety duty under I.1 would override any deference to the client's financial hardship or scheduling convenience. (confidence 0.75)
III.3.a. I.1. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q401, had Engineer L already quantified the increased runoff risk before Client X requested suspension, the Board would likely have reached a different conclusion on ceasing work silently, since III.3.a prohibits omission of material facts and II.3.a requires truthful, objective communication. A quantified risk would constitute an established fact requiring disclosure regardless of the client's request to suspend work, unlike the unquantified concern that existed in the actual case.
Resolved by: The board reasoned that quantification converts a mere concern into an established fact, which shifts the balance so that transparency obligations override the client's request to suspend work silently. (confidence 0.78)
III.3.a. II.3.a. 3 principles 3 facts Conditions Narrative

If Client X's financial setback had not occurred and work had never been suspended, would Engineer L's later notification of quantified risk still have satisfied the Code's requirement to advise on an unsuccessful project, or would earlier disclosure have been required?

Board Board question 2

Would it be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by Engineer L?

Board conclusion It would not be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by Engineer L. Continuing to work on the project after concerns about runoff were quantified would in effect mean Engineer L was placing the clients’ financial interest above the engineer’s paramount obligation to the public health, safety, and welfare. This, the engineer cannot ethically do.
Resolved by: Once the risk was confirmed, the paramount duty to public health and safety was weighed as categorically superior to loyalty to the client's financial interests, foreclosing continued work absent safeguards. (confidence 0.85)
I.1. I.4. 3 principles 3 facts Conditions Narrative
Implicit (1)

If Client X proceeds with construction without adopting the protective measures Engineer L identified, does Engineer L have any further ethical obligation beyond withdrawing from the project, such as notifying regulatory authorities or the affected community?

AnalyticalThe Board's second conclusion establishes that Engineer L cannot ethically continue work absent adequate safeguards, but it does not resolve whether Engineer L's obligations end with withdrawal. Given the paramount public safety duty under I.1 and the precedent in BER Case 18-9 regarding disclosure of future risk to third parties, Engineer L may have a further obligation to notify relevant regulatory or environmental authorities if Client X proceeds without safeguards, since simple withdrawal may not adequately protect the community's drinking water source once the risk has been confirmed as fact.
Resolved by: The Board left open whether the paramount public safety duty extends beyond withdrawal to affirmative notification of regulators, suggesting withdrawal alone may not fully discharge the obligation once the risk is confirmed and community welfare remains at stake. (confidence 0.70)
I.1. 3 principles 3 facts Conditions Narrative
Principle tension (2)

How should Loyalty to Client X be balanced against Public Welfare in Watershed Protection when Client X's financial constraints directly conflict with the protective measures needed to safeguard the community's drinking water source?

AnalyticalThe case illustrates that Fact-Based Opinion functions as a temporal hinge between two otherwise competing regimes of obligation: a client-protective regime governing engineers' communications about unconfirmed risks, and a public-protective regime governing confirmed ones. Engineer L's conduct across the two phases of the case—remaining silent while the risk was speculative, then disclosing and ultimately refusing to continue once the risk was established—shows that the Code does not ask engineers to choose once and for all between client loyalty and public welfare, but to recalibrate that choice continuously as factual certainty about risk develops.
Resolved by: The Board treated Fact-Based Opinion as the pivot that first favored Loyalty to Client X (justifying silence about a speculative risk) and later favored public-protective transparency (once the risk became evidentially confirmed), so the same provision governed opposite behaviors at different points in time rather than fixing one obligation as permanently dominant. (confidence 0.80)
I.4. II.3.a. II.3.b. 3 principles 3 facts Conditions Narrative

How should Public Welfare in Stormwater Design be weighed against Loyalty to Client X once the risk of runoff into the drinking water source has been quantified and Client X still declines to invest in safeguards?

AnalyticalOnce the runoff risk moved from an unquantified concern to a confirmed, qualitatively-estimated finding, the same two principles—Public Welfare in Stormwater Design and Loyalty to Client X—that had been reconcilable earlier became genuinely and irreconcilably opposed. The Board resolved this later-stage tension by invoking the lexical priority the Code assigns to the paramount duty to public health, safety, and welfare (I.1.) over faithful agency to the client (I.4.). This demonstrates that principle prioritization in engineering ethics is not fixed in the abstract but activates hierarchically once risk crosses an evidentiary threshold: below that threshold, loyalty and restraint from speculation can coexist; above it, public welfare categorically overrides client financial interest, even to the point of requiring withdrawal from the project.
Resolved by: Once the runoff risk was quantified, the Board treated Public Welfare in Stormwater Design and Loyalty to Client X as irreconcilable and resolved the conflict by giving I.1 lexical priority over I.4, so client financial interest could not outweigh confirmed danger to the public water supply. (confidence 0.82)
I.1. I.4. III.1.b. 3 principles 3 facts Conditions Narrative
Theoretical (2)

From a consequentialist perspective, did the outcome of Engineer L's disclosure of the quantified runoff risk justify the potential harm to Client X's financial interests and the project's continuation?

AnalyticalRegarding Q302, from a consequentialist standpoint, Engineer L's decision to disclose the quantified runoff risk to Client X, despite the likelihood of straining the client relationship or jeopardizing the project's continuation, produces a better aggregate outcome than silence would have, because the potential harm of contaminated drinking water to an entire community vastly outweighs the financial harm to a single private developer. The disclosure thus satisfies a consequentialist justification even though it imposes near-term costs on Client X.
Resolved by: The board compared aggregate harms and found that community-wide contamination risk vastly outweighs the financial and relational harm to a single client, favoring disclosure. (confidence 0.82)
I.1. 3 principles 3 facts Conditions Narrative

Did Engineer L act with professional integrity in refusing to continue the project once Client X declined to invest in the identified protective measures?

AnalyticalRegarding Q303, Engineer L's refusal to continue the project without the identified protective measures reflects professional integrity consistent with II.1.a, which protects engineers who decline to have their judgment overridden under circumstances endangering public health or property. By refusing to acquiesce to Client X's insistence on proceeding without safeguards, Engineer L demonstrated fidelity to the profession's ethical core rather than mere compliance with client wishes.
Resolved by: The board subordinated client loyalty to the engineer's paramount duty not to have professional judgment overridden where public health or property is endangered. (confidence 0.85)
II.1.a. 3 principles 3 facts Conditions Narrative
Counterfactual (2)

If the historic heavy rainfall event had not occurred, and stormwater accumulation had not increased, would Engineer L's risk concerns have ever been established as a confirmed fact requiring disclosure, and would the Board's second conclusion still apply?

If local environmental standards had not explicitly required protective measures to safeguard public water sources, would the Board still have concluded that Engineer L could not ethically continue working without those safeguards?

AnalyticalRegarding Q403, even absent explicit local environmental standards requiring protective measures, the Board's second conclusion would likely remain unchanged, because Engineer L's obligation not to continue work while Client X refuses safeguards derives primarily from the paramount duty to public health, safety, and welfare under I.1, not merely from regulatory compliance requirements. The existence of local standards reinforces but is not the sole basis for the ethical obligation identified by the Board.
Resolved by: The board treated the paramount duty to public health under I.1 as the primary source of obligation, with regulatory standards serving only a reinforcing, not foundational, role. (confidence 0.75)
I.1. 3 principles 3 facts Conditions Narrative
Analytical questions (2)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (2)

Should the original scope of work and preliminary design have anticipated evolving climate-driven stormwater risk (as reflected in BER Case 21-2) rather than treating the increased risk as an unforeseen development discovered only later?

AnalyticalThe Board's reasoning treats the increased runoff risk as an emergent discovery tied to a historic rainfall event, but BER Case 21-2's treatment of climate-driven precipitation changes suggests that a reasonably prudent engineer with expertise in stormwater design might have been expected to anticipate evolving risk profiles at the preliminary design stage. This raises a nuance the Board did not explicitly address: whether Engineer L's original scope of work and risk assessment methodology were themselves adequate given foreseeable climate trends, independent of the specific rainfall event that ultimately triggered quantification.
Resolved by: The analysis weighs treating the rainfall event as a novel, unforeseeable trigger against treating evolving climate risk as a foreseeable design parameter, without the Board resolving which framing should control. (confidence 0.65)
3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q103, BER Case 21-2's treatment of climate-driven changes in precipitation intensity and recurrence intervals suggests that a forward-looking engineer with expertise in stormwater control design should treat evolving climate risk as a foreseeable design parameter rather than an unforeseen contingency. This implies that Engineer L's original scope of work, which included ensuring no impact to the drinking water source, should have anticipated the possibility of increasing heavy rainfall frequency during preliminary design, making the later risk discovery less a novel event and more the materialization of an anticipatable design consideration.
Resolved by: The professional standard of care expected of a stormwater design expert is weighed against the framing of the rainfall event as an unforeseen contingency, tipping toward the former given applicable precedent. (confidence 0.75)
3 principles 3 facts Conditions Narrative

Does Engineer L's acceptance of the contract with a stated duty to prevent watershed impact create a heightened, ongoing monitoring obligation that persists even during a suspension of paid work?

AnalyticalRegarding Q104, the combination of Engineer L's explicit contractual duty to prevent watershed impact and the Code's paramount public welfare obligation under I.1 suggests that even during a suspension of paid work, Engineer L retained a residual duty of awareness regarding developments that could affect public safety, such as the historic heavy rainfall event. This does not require unpaid active design work, but it does support the reasonableness of Engineer L conducting new risk studies promptly upon resumption rather than treating the suspension as a complete ethical hiatus.
Resolved by: The faithful agent limit on requiring unpaid labor is balanced against the paramount public welfare duty, yielding a residual awareness obligation that stops short of demanding unpaid design work. (confidence 0.75)
I.1. I.4. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer L disclose the preliminary, unquantified runoff concern before ceasing work, or comply silently with Client X's suspension request?

Options considered:
O1 Cease work as requested without mentioning the still-unquantified runoff concern, since it has not yet been established as fact. Board's choice
O2 Voice the emerging, unquantified concern to Client X before ceasing work, erring toward early transparency despite lacking full quantification.
O3 Ask Client X to allow time to complete the risk quantification before honoring the suspension, rather than stopping immediately.
Argument structure (Toulmin):
Claim Provided the risk remained a preliminary, unquantified concern rather than an established fact at the time of the suspension request.

Engineer L was permitted to cease work without voicing the still-unquantified runoff concern when Client X requested suspension.

Grounds

Engineer L had only an early, unstudied concern about increasing risk over time; Client X suffered a financial setback and requested a work stoppage; Engineer L complied without mentioning the concern; work later resumed.

Warrant

Engineers must base professional opinions and disclosures on established facts rather than speculation (II.3.a, II.3.b); engineers must act as faithful agents respecting a client's good faith directions absent countervailing facts (I.4). The fact-based opinion warrant prevails over the disclosure warrant because no fact yet existed to disclose.

Backing

NSPE Code II.3.a, II.3.b, I.4

Rebuttal

Would not apply if Engineer L already had sufficient basis to treat the risk as an established fact at that time, in which case silence would violate the disclosure duty under III.3.a regardless of the client's request.

Engineer L Risk Disclosure Duty Engineer L Faithful Agent Duty

Should Engineer L continue working on the project without the identified protective measures, or refuse to proceed until Client X funds those safeguards?

Options considered:
O1 Decline to proceed with the stormwater design work until Client X funds the protective measures identified as necessary to safeguard the drinking water source. Board's choice
O2 Proceed with the design as Client X directs, treating the funding decision as within the client's acceptable business risk tolerance.
O3 Offer a scaled-down protective measure that partially mitigates the confirmed risk within Client X's budget while continuing the project.
Argument structure (Toulmin):
Claim Once the risk is confirmed as fact and the client declines to fund the protective measures Engineer L identified as necessary.

Engineer L must refuse to continue the stormwater design work once the runoff risk was confirmed as fact and Client X declined to invest in the identified protective measures.

Grounds

A risk study conducted after historic heavy rainfall confirmed increased stormwater accumulation threatening the community's drinking water source; Engineer L notified Client X of the quantified risk; Client X, having financially recovered, refused to fund the identified safeguards and insisted work resume.

Warrant

Engineers must hold paramount the safety, health and welfare of the public (I.1); engineers must not permit client financial interests to override public welfare (II.1.a). This paramountcy warrant prevails over the faithful agent warrant once a public risk is confirmed as fact.

Backing

NSPE Code I.1, II.1.a, I.4

Rebuttal

Would not apply if reasonable alternative safeguards short of the client's rejected measures existed that adequately addressed the confirmed risk, or if the confirmed risk fell below a threshold recognized as a genuine threat to public health.

Engineer L Watershed Safety Duty Engineer L Faithful Agent Limit

Should Engineer L notify regulatory authorities or a successor engineer about the unaddressed risk after withdrawing, or limit the ethical response to withdrawal alone?

Options considered:
O1 After withdrawing, report the confirmed, unaddressed runoff risk to the appropriate regulatory or environmental agency overseeing the watershed.
O2 Cease involvement in the project without further notification, relying on Client X's own legal and regulatory compliance obligations.
O3 Inform any engineer who takes over the project of the identified risk and the safeguards Client X declined to fund, without contacting outside agencies.
Argument structure (Toulmin):
Claim Provided Client X actually proceeds with construction without adopting the identified safeguards after Engineer L's withdrawal.

Engineer L's ethical duty extends beyond withdrawal to notifying appropriate regulatory or environmental authorities if Client X proceeds with construction without the identified protective measures.

Grounds

Client X refused to fund the identified safeguards after the runoff risk was confirmed by study and communicated to Client X; Engineer L had already withdrawn from continuing the stormwater work.

Warrant

Engineers must hold paramount public health, safety and welfare, including notifying proper authorities when professional judgment on a safety matter is overridden (I.1, II.1.a, II.1.f).

Backing

NSPE Code I.1, II.1.a, II.1.f

Rebuttal

Would not apply if Client X abandons or modifies the project to incorporate the safeguards, or if a successor engineer of record independently ensures the safeguards are implemented, removing the unaddressed risk to the community's water source.

Engineer L Watershed Safety Duty Engineer L Faithful Agent Limit

Should Engineer L's original design scope have incorporated projected climate-driven precipitation increases, or was reliance on historical rainfall data at the time of design sufficient?

Options considered:
O1 Incorporate a range of projected future precipitation scenarios into the original stormwater design rather than relying solely on historical data.
O2 Base the original design on then-current historical rainfall data and standard practice, treating subsequent extreme events as new contingencies to be studied as they arise.
O3 Note in the original scope of work that climate-related risk would be monitored and reassessed if conditions changed, without fully designing for it upfront.
Argument structure (Toulmin):
Claim To the extent that climate-driven precipitation change was a recognized, foreseeable design parameter for a stormwater specialist at the time of contracting.

Engineer L's original scope of work and preliminary design should have anticipated evolving climate-driven stormwater risk rather than treating it as a later, unforeseen discovery.

Grounds

Engineer L accepted the contract with an explicit duty to prevent watershed impact; a historic heavy rainfall event later occurred, followed by increased stormwater accumulation, prompting a risk study and notification.

Warrant

Engineers must perform services only in areas of competence and apply the knowledge and skill ordinarily exercised by qualified engineers, including foreseeable design conditions (II.2.a); engineers must hold paramount public welfare in design choices (I.1).

Backing

NSPE Code II.2.a, I.1

Rebuttal

Would not apply if climate-driven stormwater risk was not yet a recognized or foreseeable standard of practice at the time of the original design, making anticipatory action outside the ordinary standard of care.

Engineer L Watershed Safety Duty

Should Engineer L maintain reasonable awareness of watershed-relevant developments during the suspension without performing unpaid design work, or treat the suspension as a complete pause in professional attention?

Options considered:
O1 Remain attentive to significant public developments affecting watershed risk during the suspension without performing unpaid design tasks, then promptly reassess upon resumption. Board's choice
O2 Treat the suspension as a full stop of all professional attention to the project until paid work resumes, with no interim monitoring.
O3 Proactively track rainfall and watershed conditions during the suspension even without compensation, in case the risk profile changes.
Argument structure (Toulmin):
Claim Provided the suspension is genuinely temporary and no new risk-relevant facts reasonably come to the engineer's attention during the pause.

Engineer L's contractual watershed protection duty does not require unpaid active design work during the suspension, but supports maintaining reasonable awareness of relevant developments and promptly reassessing risk upon resumption.

Grounds

Engineer L's contract explicitly assigned a duty to prevent watershed impact; Client X requested suspension of paid work after a financial setback; a historic heavy rainfall event occurred during this period; Engineer L conducted a risk study and notified Client X upon resumption.

Warrant

Engineers must hold paramount public health, safety and welfare even absent active compensation for services (I.1); faithful agency duties do not require an engineer to perform unpaid work during a client-directed suspension (I.4).

Backing

NSPE Code I.1, I.4

Rebuttal

Would not apply if the suspension were genuinely temporary and no new risk-relevant facts arose during the pause, in which case no heightened monitoring obligation would attach beyond the original assessment.

Engineer L Watershed Safety Duty Engineer L Faithful Agent Duty
14 sequenced 8 actions 6 events
Case timeline
Engineer L accepts a contract with Client X to design a stormwater management system for a large development, with a scope that includes ensuring stormwater will not impact the community drinking water source.
Fulfills (1)
  • Faithful Agent Obligation
Causal-normative reasoning(confidence 0.70)
By accepting the contract Engineer L fulfilled the Faithful Agent Obligation to Client X, but this same acceptance set in motion the causal chain toward Risk Concern Emergence, meaning the loyalty owed to the client from the outset was already in latent tension with the public safety risks that would later surface from stormwater accumulation.
During the preliminary design phase, Engineer L becomes concerned that risk of impact to the community drinking water source will potentially increase over time, before the risk can be quantified.
State changes (1)
  • began: Unquantified Runoff Risk Awareness
Client X encounters unexpected financial setbacks before Engineer L can quantify the increased risk, prompting the request to suspend work under the original contract.
State changes (1)
  • began: Client X Budget Constraint
Client X, facing unexpected financial setbacks, requests that Engineer L suspend the work identified in the original contract.
Causal-normative reasoning(confidence 0.60)
Although the Work Suspension Request itself carries no direct fulfills or violates tags, it is the causal trigger for the Nondisclosure at Suspension, meaning its normative weight lies in setting up a context where Engineer L's later silence about risk becomes ethically consequential.
State changes (1)
  • began: Stormwater Contract Work Suspension
In communications about the suspension, Engineer L does not mention to Client X the potential increased risk of impact to the community drinking water source, complying with the suspension request without disclosing the unquantified concern. The BER finds this disclosure was not required because the concern had not risen to the level of fact.
Fulfills (2)
  • Faithful Agent Obligation
  • Opinions Founded on Facts Obligation
Causal-normative reasoning(confidence 0.65)
Nondisclosure at Suspension fulfilled the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because at that point the risk had not yet been established through study, so withholding a still-unverified concern was consistent with client loyalty and factual restraint even though it delayed information that would later prove critical once Risk Established as Fact emerged from the Risk Study Conduct.
State changes (2)
  • began: Risk Nondisclosure During Suspension
  • began: Unquantified Runoff Risk Awareness
Several months after the suspension, Client X's financial situation improves, enabling the request that Engineer L resume work on the stormwater management system.
State changes (1)
  • ended: Client X Budget Constraint
When Client X's financial situation improves, Engineer L agrees to resume work on the stormwater management system.
Fulfills (1)
  • Faithful Agent Obligation
Causal-normative reasoning(confidence 0.70)
Work Resumption fulfilled the Faithful Agent Obligation by honoring the client's renewed instructions after Client Financial Recovery, but this resumption reactivated the underlying conditions of Stormwater Accumulation Increase, making the engineer's subsequent Risk Study Conduct and Risk Notification necessary once the natural rainfall event exposed the danger that loyalty alone could no longer justify concealing.
State changes (2)
  • ended: Risk Nondisclosure During Suspension
  • ended: Stormwater Contract Work Suspension
An historic heavy rainfall occurs in the region around the time work resumes, a natural occurrence outside any case agent's control.
The historic rainfall leads to increased stormwater accumulation on the development site, which raises the risk of runoff into the watershed that serves as the community drinking water source.
State changes (2)
  • began: Unquantified Runoff Risk Awareness
  • began: Drinking Water Source Runoff Risk
Following the historic heavy rainfall, Engineer L conducts additional studies and qualitatively estimates the risk that stormwater runoff from the development could reach the nearby watershed and community drinking water source.
At stake (1)
  • Public Safety Paramountcy Obligation
Fulfills (1)
  • Opinions Founded on Facts Obligation
Causal-normative reasoning(confidence 0.85)
Risk Study Conduct fulfills the Opinions Founded on Facts Obligation because it transforms the observed Stormwater Accumulation Increase into a factually grounded Risk Established as Fact, which is the necessary evidentiary basis for the engineer's subsequent duty to notify the client.
State changes (1)
  • began: Confirmed Runoff Risk Finding
Following Engineer L's additional studies and qualitative estimate, the identified runoff risk attains the status of fact within the case, triggering the disclosure obligations the Board discusses.
State changes (2)
  • began: Confirmed Runoff Risk Finding
  • ended: Unquantified Runoff Risk Awareness
Engineer L notifies Client X of the identified runoff risk and advises that additional protective measures should be considered, noting that local environmental standards require steps to safeguard public water sources.
At stake (2)
  • Public Safety Paramountcy Obligation
  • Project Success Advisement Obligation
Fulfills (2)
  • Faithful Agent Obligation
  • Opinions Founded on Facts Obligation
Causal-normative reasoning(confidence 0.85)
Risk Notification fulfills the Faithful Agent Obligation and the Opinions Founded on Facts Obligation because it is the direct downstream act of the Risk Study having established the risk as fact, so the engineer discharges the duty to inform the client honestly and factually, even though this notification then precipitates the client's Safeguard Refusal.
State changes (1)
  • ended: Unquantified Runoff Risk Awareness
Client X, citing continuing budget limitations, refuses to invest in additional protective measures and insists on proceeding without added safeguards, stating that compliance issues will be addressed later, if needed.
Causal-normative reasoning(confidence 0.60)
Safeguard Refusal carries no fulfills or violates tags for the client, but it is the pivotal causal link that forces Engineer L into the Refusal to Acquiesce, showing that the client's rejection of safety measures directly generates the engineer's obligation to stand firm on public safety.
State changes (2)
  • began: Public Safety Faithful Agent Conflict
  • began: Unsafeguarded Project Failure Risk
Per the BER's conclusion, Engineer L must not continue work on the project while Client X refuses to invest in the protective measures Engineer L identified. Ethically acquiescing to the client's insistence is treated as impermissible conduct.
Fulfills (2)
  • Public Safety Paramountcy Obligation
  • Project Success Advisement Obligation
Causal-normative reasoning(confidence 0.85)
Refusal to Acquiesce fulfills the Public Safety Paramountcy Obligation and Project Success Advisement Obligation because, in response to the client's Safeguard Refusal, Engineer L prioritizes public welfare over compliance with the client's wishes, completing the causal chain from risk discovery to a firm ethical stand.
Narrative (2 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 L, a licensed professional engineer with extensive experience in stormwater control design. Client X, a private development entity, has contracted you to design a stormwater management system for a large residential and commercial development located near a small community that draws its primary drinking water from a nearby surface water watershed. Your scope of work explicitly requires you to ensure that stormwater from the development does not impact this drinking water source. During preliminary design, you become concerned that the probability of heavy stormwater flows affecting the watershed will increase over time, though you have not yet quantified this risk. Before you can complete that analysis, Client X suspends the contract due to financial setbacks, and you do not raise the runoff concern in your suspension communications. Months later, work resumes, and an historic regional rainfall event increases on-site stormwater accumulation, prompting you to conduct further studies that yield a qualitative risk estimate. You now face a series of decisions about disclosure, continued work, and professional responsibility going forward.

Main characters (2)

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 L Roles in this case: Design EngineerPublic ResponsibilityFaithful Agent

Guided by: Public Welfare in Watershed Protection, Transparency in Risk Disclosure, Public Welfare in Stormwater Design

Advising the client that the project as designed will not succeed or should be reconsidered can push the engineer beyond the narrow technical scope implied by the faithful agent limit, creating tension between candid professional advice and staying within the bounds of the agent role.

Attaches to role: Design Engineer

Tension between Engineer L Risk Disclosure Duty and Engineer L Faithful Agent Duty

Attaches to role: Design Engineer

Tension between Engineer L Watershed Safety Duty and Engineer L Faithful Agent Limit

Attaches to role: Design Engineer

Tension between Engineer L Watershed Safety Duty and Engineer L Faithful Agent Duty

Attaches to role: Design Engineer

Serving the client loyally as a faithful agent can pull the engineer toward going along with the client's preferred course of action, but the prohibition on acquiescence bars the engineer from silently accepting a plan that endangers the watershed, even when the client insists on it.

Attaches to role: Faithful Agent

The engineer's expectation that the client will meet environmental compliance obligations can clash with the engineer's duty to serve the client's business interests, especially when compliance measures raise costs or delay the project the client wants delivered quickly.

Attaches to role: Design Engineer
Client X Roles in this case: Development Client

Advising the client that the project as designed will not succeed or should be reconsidered can push the engineer beyond the narrow technical scope implied by the faithful agent limit, creating tension between candid professional advice and staying within the bounds of the agent role.

Serving the client loyally as a faithful agent can pull the engineer toward going along with the client's preferred course of action, but the prohibition on acquiescence bars the engineer from silently accepting a plan that endangers the watershed, even when the client insists on it.

The engineer's expectation that the client will meet environmental compliance obligations can clash with the engineer's duty to serve the client's business interests, especially when compliance measures raise costs or delay the project the client wants delivered quickly.

The Board’s deliberation

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

It was not unethical for Engineer L to cease work when requested by Client X, without voicing concern about unquantified increased risk. Later, Engineer L did comply with Code provisions that require engineers to notify their employers or clients if a project will not be successful.
It would not be ethical for Engineer L to continue working on Client X’s project when Client X refuses to invest in the protective measures identified by Engineer L. Continuing to work on the project after concerns about runoff were quantified would in effect mean Engineer L was placing the clients’ financial interest above the engineer’s paramount obligation to the public health, safety, and welfare. This, the engineer cannot ethically do.
Summary
  • An engineer who stops work at a client's direction is not automatically unethical for staying silent about risks that have not yet been quantified or confirmed.
  • The duty to act as a faithful agent to a client has limits, and those limits are reached once public health, safety, or watershed impacts become reasonably knowable or certain.
  • Ethical obligations can be phase dependent, meaning what is permissible at an early or preliminary stage of work may become impermissible once the engineer has enough information to recognize a genuine public safety concern.