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 ExtractionAll 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.
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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.
-
Engineer L Faithful Agent Duty
This obligation is a direct statement of the faithful agent or trustee duty owed to the client
-
Contract Acceptance
Accepting the contract establishes the agent-client relationship
-
Work Suspension Request
Acting as faithful agent includes advising client of concerns
-
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
-
Engineer L Faithful Agent Limit
Defines the faithful agent duty that is being limited by public welfare concerns
-
Loyalty to Client X
Acting as a faithful agent supports honoring Client X's request during the first phase
-
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
-
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
-
NSPE Code of Ethics
This resource covers faithful agency to the client as a core ethical duty
-
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.
-
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
-
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
-
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
-
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
-
Public Welfare in Stormwater Design
This provision requires notification when judgment is overruled and public safety is endangered
-
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
-
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
-
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.
-
Engineer L Risk Disclosure Duty
Disclosure of risk must be objective truthful and include all relevant information
-
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
-
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
-
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
-
Engineer L Design Engineer
He must ensure his professional reports on the stormwater system are objective and complete
-
Risk Concern Emergence
Reports must objectively include the emerging risk information
-
Risk Established as Fact
Truthful reporting requires disclosure of confirmed risk facts
-
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
-
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.
-
Risk Notification
Publicly expressing technical risk opinions must be founded on facts and competence
-
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
-
Fact-Based Opinion by Engineer L
This provision establishes the fact-founded standard applied to evaluate Engineer L's evolving concern
-
Engineer L Public Responsibility
He may publicly express technical opinions on the risk to the water source based on his expertise
-
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.
-
Engineer L Unsuccessful Project Advisory Duty
This obligation directly mirrors the duty to advise clients when a project will not be successful
-
Work Suspension Request
Advising client of unsuccessful project aligns with suspension request
-
Risk Notification
Advising client of risks that threaten project success
-
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
-
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
-
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
-
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
-
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
-
BER Case 84-5
This case directly addresses engineers advising clients when a project will be unsuccessful
-
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.
-
Engineer L Risk Disclosure Duty
Failing to disclose the stormwater risk would constitute omission of a material fact
-
Nondisclosure at Suspension
Omitting material facts at suspension is a material misrepresentation
-
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
-
Transparency in Risk Disclosure
Omitting the known risk during communications constitutes a material omission under this provision
-
Engineer L Design Engineer
He must avoid omitting material facts about the water source risk in his statements
-
Risk Concern Emergence
Omitting known risk concerns would misrepresent material facts
-
Risk Established as Fact
Withholding established risk fact constitutes material misrepresentation
-
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
-
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 ExtractionExplicit 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.
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.
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.'
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.
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.
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.
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.
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.
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.
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.
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.
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 Engineer L to cease work when requested by Client X, without voicing concern about increased risk?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
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?
Did Engineer L act with professional integrity in refusing to continue the project once Client X declined to invest in the identified protective measures?
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?
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.
Show 2 analytical questionsImplicit (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?
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?
Decisions & Arguments (5)
View ExtractionShould Engineer L disclose the preliminary, unquantified runoff concern before ceasing work, or comply silently with Client X's suspension request?
Engineer L was permitted to cease work without voicing the still-unquantified runoff concern when Client X requested suspension.
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.
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.
NSPE Code II.3.a, II.3.b, I.4
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.
Should Engineer L continue working on the project without the identified protective measures, or refuse to proceed until Client X funds those safeguards?
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.
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.
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.
NSPE Code I.1, II.1.a, I.4
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.
Should Engineer L notify regulatory authorities or a successor engineer about the unaddressed risk after withdrawing, or limit the ethical response to withdrawal alone?
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.
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.
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).
NSPE Code I.1, II.1.a, II.1.f
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.
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?
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.
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.
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).
NSPE Code II.2.a, I.1
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.
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?
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.
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.
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).
NSPE Code I.1, I.4
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.
Event Timeline (14)
Case timeline
- Faithful Agent Obligation
- began: Unquantified Runoff Risk Awareness
- began: Client X Budget Constraint
- began: Stormwater Contract Work Suspension
- Faithful Agent Obligation
- Opinions Founded on Facts Obligation
- began: Risk Nondisclosure During Suspension
- began: Unquantified Runoff Risk Awareness
- ended: Client X Budget Constraint
- Faithful Agent Obligation
- ended: Risk Nondisclosure During Suspension
- ended: Stormwater Contract Work Suspension
- began: Unquantified Runoff Risk Awareness
- began: Drinking Water Source Runoff Risk
- Public Safety Paramountcy Obligation
- Opinions Founded on Facts Obligation
- began: Confirmed Runoff Risk Finding
- began: Confirmed Runoff Risk Finding
- ended: Unquantified Runoff Risk Awareness
- Public Safety Paramountcy Obligation
- Project Success Advisement Obligation
- Faithful Agent Obligation
- Opinions Founded on Facts Obligation
- ended: Unquantified Runoff Risk Awareness
- began: Public Safety Faithful Agent Conflict
- began: Unsafeguarded Project Failure Risk
- Public Safety Paramountcy Obligation
- Project Success Advisement Obligation
Narrative (2 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 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.
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.
Tension between Engineer L Risk Disclosure Duty and Engineer L Faithful Agent Duty
Tension between Engineer L Watershed Safety Duty and Engineer L Faithful Agent Limit
Tension between Engineer L Watershed Safety Duty and Engineer L Faithful Agent Duty
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.
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.
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.