Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Sustainable Development—Threatened Species
Step 4 of 5

188

Entities

5

Provisions

3

Precedents

16

Questions

16

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A attempted a one-way shift of the disclosure obligation from the public-facing written-report channel to the private client-facing verbal channel, treating client notification as functionally equivalent to regulatory disclosure. The Board blocked this shift, ruling the two obligations are non-interchangeable and that the non-delegable duty to the public authority remains fixed on Engineer A until fulfilled through the written report itself—an invalid or 'failed' transfer rather than a completed one.
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 (5)
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.3 board + analysis Issue public statements only in an objective and truthful manner.
How this applies in the case (showing 3 of 16)
Obligation
Engineer A Report Inclusion Duty
Requires objective and truthful public statements consistent with including all relevant information in the report
Action
Written Report Omission
Omitting relevant information violates the duty to be objective and truthful in public statements
State
Report Omission Of Species Concern
Omitting species concern from the report violates objective and truthful public statements
Obligation (1)
  • Engineer A Report Inclusion Duty
    Requires objective and truthful public statements consistent with including all relevant information in the report
Action (2)
  • Written Report Omission
    Omitting relevant information violates the duty to be objective and truthful in public statements
  • Species Threat Reporting
    Reporting on species threats must be objective and truthful
State (3)
  • Report Omission Of Species Concern
    Omitting species concern from the report violates objective and truthful public statements
  • Unambiguous Risk Conclusions
    Conclusions must be stated truthfully and objectively
  • Condominium Wetlands Species Risk
    Public statements about the wetlands risk must be truthful and objective
Constraint (2)
  • Engineer A Report Omission Prohibition
    Requires objective and truthful public statements which prohibits omitting material findings
  • Engineer A Report Omission Boundary
    Truthful reporting standard bounds what information can be excluded
Principle (2)
  • Objectivity in Written Report
    Requires public statements including reports to be objective and truthful
  • Complete Reporting in Written Report
    Omitting relevant information violates the duty to be truthful in public statements
Role (1)
  • Engineer A Environmental Engineer
    Engineer A must issue the written report to the public authority in an objective and truthful manner
Event (2)
  • Wall Defect Discovery
    Public statements about the wall defect must be objective and truthful
  • Illegal Fill Discovery
    Public statements about illegal fill must be truthful and objective
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code addressing truthfulness in public statements
Capability (2)
  • Engineer A Risk Disclosure
    Verbal disclosure of the species risk must be objective and truthful
  • BER Board Code Application
    Board applies objectivity and truthfulness requirements to evaluate Engineer A's statements
I.5 board + analysis Avoid deceptive acts.
How this applies in the case (showing 3 of 15)
Obligation
Engineer A Complete Report Duty
Omitting the threatened species information would be a deceptive act by omission
Action
Written Report Omission
Omitting known threatened species information is a deceptive act
State
Report Omission Of Species Concern
Omitting known species risk is a deceptive act
Obligation (2)
  • Engineer A Complete Report Duty
    Omitting the threatened species information would be a deceptive act by omission
  • Engineer A Client Advisement Duty
    Failing to advise the client of the inclusion would risk deceptive concealment from the client
Action (1)
  • Written Report Omission
    Omitting known threatened species information is a deceptive act
State (2)
  • Report Omission Of Species Concern
    Omitting known species risk is a deceptive act
  • Biologist Bird Threat Awareness
    Ignoring the biologist's known threat awareness would be deceptive
Constraint (2)
  • Engineer A Report Omission Prohibition
    Omitting the biologist's opinion would be a deceptive act by omission
  • Engineer A Report Omission Boundary
    Avoiding deception limits the boundary of permissible omissions in the report
Principle (2)
  • Complete Reporting in Written Report
    Omitting known threatened species information is a deceptive act by omission
  • Transparency in Client Disclosure
    Verbal disclosure to client contrasts with deceptive omission in public report
Role (1)
  • Engineer A Environmental Engineer
    Engineer A must avoid deceptive acts such as omitting known threatened species information from the report
Event (2)
  • Wall Defect Discovery
    Engineers must avoid deceptive acts when disclosing wall defect information
  • Illegal Fill Discovery
    Engineers must avoid deceptive acts regarding illegal fill discovery
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code prohibiting deceptive acts
Capability (2)
  • Engineer A Risk Disclosure
    Informal verbal disclosure rather than formal reporting could be seen as a deceptive act by omission
  • BER Board Code Application
    Board considers whether Engineer A's conduct constituted a deceptive act
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 25)
Obligation
Engineer A Report Inclusion Duty
Directly requires objectivity truthfulness and inclusion of all relevant information in professional reports
Action
Written Report Omission
Failing to include all relevant and pertinent information in a professional report violates this provision
State
Report Omission Of Species Concern
Reports must include all relevant and pertinent information including species concerns
Obligation (2)
  • Engineer A Report Inclusion Duty
    Directly requires objectivity truthfulness and inclusion of all relevant information in professional reports
  • Engineer A Complete Report Duty
    Mandates that all pertinent information including the biologist's findings be included in the report
Action (3)
  • Written Report Omission
    Failing to include all relevant and pertinent information in a professional report violates this provision
  • Species Threat Reporting
    Reports on species threats must be complete and current per this provision
  • Environmental Analysis Undertaking
    Conducting the environmental analysis is the basis for objective and truthful reporting required here
State (6)
  • Report Omission Of Species Concern
    Reports must include all relevant and pertinent information including species concerns
  • Biologist Bird Threat Awareness
    Known biologist threat information is relevant and must be included in reports
  • Unambiguous Risk Conclusions
    Conclusions in reports must be objective and complete
  • Threatened Species Regulatory Status
    Regulatory status of species is pertinent information required in reports
  • Condominium Wetlands Species Risk
    Wetlands species risk is pertinent information required in the engineering report
  • Engineer A Technical Competence
    Technical competence relates to producing truthful and complete reports
Constraint (2)
  • Engineer A Report Omission Prohibition
    Mandates inclusion of all relevant and pertinent information such as the biologist's opinion
  • Engineer A Report Omission Boundary
    Directly defines the requirement to include relevant and pertinent information in reports
Principle (3)
  • Objectivity in Written Report
    Directly requires objective truthful reports with all relevant and pertinent information
  • Complete Reporting in Written Report
    Omission of biologist's findings violates requirement to include all relevant information
  • Environmental Stewardship in Wetlands Analysis
    Biologist's environmental findings are relevant information that must be included per this provision
Role (1)
  • Engineer A Environmental Engineer
    Engineer A must include all relevant and pertinent information such as the biologist's threatened species finding in the professional report to the public authority
Event (3)
  • Wall Defect Discovery
    Engineers must objectively report all findings including discovered defects
  • Illegal Fill Discovery
    Engineers must truthfully report illegal fill findings in professional statements
  • Species Threat Identification
    Engineers must include all relevant information about threatened species in reports
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code requiring objectivity and completeness in professional reports
Capability (4)
  • Engineer A Site Analysis
    The professional analysis and report must be objective, truthful, and include all relevant information
  • Engineer A Risk Disclosure
    Disclosure of the threatened species risk should have been included in formal reporting rather than only verbal mention
  • Firm Biologist Species Risk Assessment
    The biologist's risk assessment findings are relevant and pertinent information that should be included in reports
  • BER Board Code Application
    Board applies the requirement for complete and truthful reporting to assess Engineer A's conduct
III.2.d board + analysis Engineers are encouraged to adhere to the principles of sustainable development1in order to protect the environment for future generations.Footnote 1"Sustainable development" is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development.
How this applies in the case (showing 3 of 21)
Obligation
Engineer A Complete Report Duty
Encourages consideration of sustainable development factors like threatened species in reporting
Action
Environmental Analysis Undertaking
Analyzing environmental impact directly relates to sustainable development principles
State
Condominium Wetlands Species Risk
Sustainable development principles relate directly to wetlands and species protection
Obligation (2)
  • Engineer A Complete Report Duty
    Encourages consideration of sustainable development factors like threatened species in reporting
  • Engineer A Client Risk Disclosure Duty
    Relates to protecting environmental quality by disclosing threatened species risk to the client
Action (2)
  • Environmental Analysis Undertaking
    Analyzing environmental impact directly relates to sustainable development principles
  • Species Threat Reporting
    Reporting threatened species supports sustainable development and environmental protection
State (5)
  • Condominium Wetlands Species Risk
    Sustainable development principles relate directly to wetlands and species protection
  • Threatened Species Regulatory Status
    Protecting threatened species aligns with sustainable development encouragement
  • Section III.2.d First Impression
    This entity directly represents the first application of this sustainable development provision
  • Section III.2.d In Force
    This entity represents whether the sustainable development provision was in effect
  • Developer Client Engagement
    Encourages engineers to consider sustainability even when engaged by a developer client
Constraint (2)
  • Engineer A Report Omission Prohibition
    Sustainable development principles support disclosing threats to species for environmental protection
  • Engineer A Report Omission Boundary
    Protecting environmental quality supports including threatened species information
Principle (2)
  • Environmental Stewardship in Wetlands Analysis
    Directly relates to sustainable development principles protecting wildlife and environment
  • Public Welfare in Wetlands Case
    Sustainable development encourages protecting environment for future generations aligning with public interest
Role (1)
  • Engineer A Environmental Engineer
    Engineer A is encouraged to adhere to sustainable development principles that protect environmental quality including the threatened bird species habitat
Event (2)
  • Species Threat Identification
    This provision directly addresses environmental protection and sustainable development concerns raised by threatened species
  • Illegal Fill Discovery
    Illegal fill relates to environmental protection and sustainable development principles
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code encouraging sustainable development principles
Capability (4)
  • Firm Biologist Species Risk Assessment
    The identification of threatened species risk directly relates to sustainable development and environmental protection
  • Engineer A Site Analysis
    The site analysis for the condominium project implicates sustainable development principles regarding protected wetlands
  • BER Board Precedent Reasoning
    Board reasons through the new sustainable development provision as a matter of first impression
  • BER Board Code Application
    Board directly applies the new sustainable development language to the facts of the case
III.4 board + analysis Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
How this applies in the case (showing 3 of 16)
Obligation
Engineer A Client Advisement Duty
Concerns balancing confidentiality of client business affairs with the duty to advise about report content
Action
Verbal Concern Disclosure
Disclosing concerns verbally may involve confidential client or employer information
State
Absent Confidential Treatment
Relates directly to whether confidential client information was properly protected
Obligation (1)
  • Engineer A Client Advisement Duty
    Concerns balancing confidentiality of client business affairs with the duty to advise about report content
Action (1)
  • Verbal Concern Disclosure
    Disclosing concerns verbally may involve confidential client or employer information
State (3)
  • Absent Confidential Treatment
    Relates directly to whether confidential client information was properly protected
  • Developer Client Engagement
    Confidentiality obligations arise from the client engagement relationship
  • Client Public Interest Conflict
    Balancing confidentiality against public interest disclosure is directly relevant
Principle (2)
  • Confidentiality of Client Information
    Directly addresses whether disclosure of client information without consent is prohibited
  • Loyalty to Developer Client
    Relates to engineer's duty of confidentiality and trust as agent to client
Role (1)
  • Engineer A Environmental Engineer
    Engineer A must weigh the client's confidentiality interests against the duty to disclose relevant threatened species information to the public authority
Event (2)
  • Illegal Fill Discovery
    Confidential client information about illegal fill must not be disclosed without consent
  • Wall Defect Discovery
    Confidential information about the wall defect may be protected under client confidentiality
Resource (4)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code governing confidentiality of client information
  • BER Case No. 89-7
    This case directly interprets rationales for nondisclosure under Section III.4
  • BER Case No. 97-13
    This case applies III.4 by balancing confidentiality against public safety concerns
  • BER Case No. 04-8
    This case applies III.4 in the context of a client's environmental law violation on a wetland site
Capability (2)
  • Engineer A Risk Disclosure
    Disclosure of client-related technical findings raises confidentiality concerns under this provision
  • BER Board Code Application
    Board weighs confidentiality obligations against disclosure of environmental risk
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 3 Lineage Graph

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

Principle Established:

Engineers act as agents or trustees for clients and are expected to maintain confidentiality of client information, especially where the client has confided information and the engineer lacks specific technical expertise in the relevant discipline.

Citation Context:

Cited to explain the underlying rationale for the nondisclosure provisions in NSPE Code Section III.4., emphasizing engineers' role as agents/trustees who must protect client confidences.

Relevant Excerpts
discussion: "At the same time, as noted in BER Case No. 89-7, there are various rationales for the nondisclosure language contained in NSPE Code Section III.4.."
discussion: "in Case No. 89-7, the facts revealed that the client had confided in the engineer and may have relied upon the engineer to maintain the information in confidence. In addition, the engineer in BER Case No. 89-7 did not have any particular expertise in the technical areas (mechanical/electrical) involved in the matter at issue."

Principle Established:

An engineer who lacks expertise in the relevant technical area and whose conclusions are based on mere surmise or speculation should act cautiously, verbally report concerns to the client, and refrain from including unverified information in a final report, but should follow up to ensure corrective action is taken.

Citation Context:

Cited at length as a parallel case involving a conflict between client loyalty and public safety obligations, where an engineer discovered a possible structural defect outside his scope of work; the Board used this case's reasoning about speculation and expertise to reach a different conclusion in the present case.

Relevant Excerpts
discussion: "BER Case No. 97-13 appears to present this ethical dilemma starkly. There, a public agency retained the services of VWX Architects and Engineers to perform a major scheduled overhaul of a bridge."
discussion: "Similarly, in BER Case No. 97-13, the engineer's evaluation was based upon general surmise and speculation about the cause of the structural failure of the wall, based entirely upon a visual inspection without anything more."
discussion: "Further, unlike BER Case No. 97-13, there is nothing in the facts that the conclusions reached are based upon surmise or speculation."

Principle Established:

An engineer who discovers a client's violation of environmental laws/regulations has an obligation to inform the client of the violation and necessary remedial steps, and to report the matter to appropriate authorities if the client fails to take corrective action.

Citation Context:

Cited as a more recent precedent involving an environmental engineer who discovered a client's unpermitted violation of wetlands regulations, establishing a course of action requiring the engineer to notify the client and, if unremedied, report to authorities.

Relevant Excerpts
discussion: "More recently in BER Case No. 04-8, Engineer A, an environmental engineer, performed wetland delineation services on the client's wetland site."
discussion: "It should be noted that these cases were decided prior to the addition of the language contained in NSPE Code Section III.2.d. quoted above."
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 42% Facts Similarity 49% Discussion Similarity 26% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 55%
Shared provisions: II.3.a Same outcome unethical View Synthesis
Component Similarity 49% Facts Similarity 41% Discussion Similarity 37% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 53%
Shared provisions: III.2.d Same outcome unethical View Synthesis
Component Similarity 50% Facts Similarity 47% Discussion Similarity 38% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 11% Principle Overlap 65%
Shared provisions: III.4 Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 48% Discussion Similarity 49% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 70%
Same outcome unethical View Synthesis
Component Similarity 47% Facts Similarity 38% Discussion Similarity 49% Outcome Alignment 100% Tag Overlap 57% Principle Overlap 60%
Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 59% Discussion Similarity 50% Outcome Alignment 100% Tag Overlap 27% Principle Overlap 54%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 56% Discussion Similarity 30% Outcome Alignment 100% Tag Overlap 30% Principle Overlap 62%
Same outcome unethical View Synthesis
Component Similarity 49% Facts Similarity 34% Discussion Similarity 22% Provision Overlap 25% Outcome Alignment 50% Tag Overlap 50% Principle Overlap 51%
Shared provisions: III.4 View Synthesis
Component Similarity 50% Facts Similarity 50% Discussion Similarity 33% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.3.a Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 58% Discussion Similarity 41% Provision Overlap 33% Outcome Alignment 50% Tag Overlap 11% Principle Overlap 56%
Shared provisions: III.2.d View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Was it ethical for Engineer A not to include the information about the threat to the bird species in a written report that will be submitted to a public authority that is considering the developer’s proposal?

Board conclusion It was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority that is considering the developer’s proposal. Engineer A should have included it in the written report and advised the client of its inclusion.
Resolved by: The board weighed the developer's interest in a favorable report against the public authority's need for complete, objective information and found the latter controlling because the report's audience was a regulatory decision maker, not just the client. (confidence 0.85)
II.3.a. III.2.d. 3 principles 3 facts Conditions Narrative
Implicit (4)

Does verbally informing the developer client about the threatened species risk, without including it in the written report, satisfy Engineer A's professional obligations, or does it merely shift responsibility without ensuring the public authority is informed?

AnalyticalThe Board's conclusion implies that verbal disclosure to the developer client, while satisfying an internal advisement duty, does not discharge Engineer A's separate and independent obligation to the public authority under Section II.3.a. The two disclosure duties are not interchangeable: informing the client privately manages the client relationship, but only inclusion in the written report ensures the regulatory body reviewing the proposal has the information needed to make an informed public-interest decision. Treating verbal disclosure as sufficient risks conflating client management with public accountability.
Resolved by: The board treated client advisement and public reporting as two separate obligations, holding that satisfying the former (verbal disclosure to client) cannot substitute for or discharge the latter (written disclosure to the public authority). (confidence 0.80)
II.3.a. 3 principles 3 facts Conditions Narrative
AnalyticalVerbal disclosure to the developer client (Q101) does not discharge Engineer A's ethical obligation because the public authority, not the client, is the ultimate decision-maker relying on the written report. Informing the client privately may satisfy an internal duty of transparency but does not ensure the regulator has the information needed for an objective review, effectively shifting risk-bearing responsibility onto the public without their knowledge.
Resolved by: The board weighed internal client transparency against public accountability and found that only inclusion in the written report satisfies the latter, since the public authority cannot access private verbal communications. (confidence 0.80)
II.3.a. 3 principles 3 facts Conditions Narrative

Should the firm biologist's professional opinion on species risk have been independently verified or elevated to a formal finding requiring mandatory disclosure, given that the biologist is part of Engineer A's firm rather than an independent third party?

Does the fact that the bird species is 'threatened' rather than 'endangered' create a lower threshold of disclosure obligation, and if so, is that distinction ethically defensible when the underlying risk to habitat is the same?

AnalyticalThe Board's reasoning does not hinge on the bird species being classified as 'threatened' rather than 'endangered,' and this suggests the regulatory label itself is not the ethical trigger. What matters is that a qualified professional within the firm (the biologist) reached an unambiguous risk conclusion relevant to the project's impact on a protected habitat. Had the Board made disclosure duties turn on the severity of the regulatory classification, it would create a troubling sliding scale of honesty in reporting, where lesser-protected species risks could be selectively omitted. The Board's implicit position is that the duty of objective and complete reporting applies regardless of where a species falls on the regulatory spectrum, so long as the risk is scientifically identified and material to the authority's decision.
Resolved by: The board implicitly weighed regulatory classification against the materiality of the biologist's finding and concluded that classification severity does not diminish the disclosure duty when the underlying risk to habitat is clear. (confidence 0.75)
II.3.a. III.2.d. 3 principles 3 facts Conditions Narrative
AnalyticalThe classification of the species as 'threatened' rather than 'endangered' (Q103) does not lower Engineer A's disclosure obligation. The Board's reasoning rests on the objectivity and completeness required of professional reports under Section II.3.a, not on the severity tier of regulatory classification. Because the biologist's finding created a genuine, identifiable risk to protected habitat, the ethical duty to disclose attaches regardless of whether the species is legally 'threatened' or 'endangered.'
Resolved by: The Board treated the objectivity and completeness duty under II.3.a as controlling regardless of regulatory severity tier, so the lesser classification could not diminish the disclosure obligation. (confidence 0.82)
II.3.a. 3 principles 3 facts Conditions Narrative

What is Engineer A's obligation if the developer client, after being verbally informed, instructs Engineer A to omit the species risk from the written report — does compliance with that instruction cross an ethical boundary regardless of client consent?

AnalyticalThe case reveals an unresolved tension the Board's conclusion only implicitly settles: when a client's commercial interest in project approval conflicts with an engineer's duty of complete and objective reporting to a public authority, the latter must prevail. Even if the developer client had explicitly instructed Engineer A to omit the biologist's finding, this would not create a valid ethical exception, because Section II.3.a's objectivity requirement in professional reports submitted to public bodies functions as a non-waivable public-protection duty, not a negotiable term of the client engagement that can be modified by client consent or preference.
Resolved by: The board's logic subordinates the client's commercial interest and explicit instruction to the non-waivable public-protection duty of objective reporting under Section II.3.a. (confidence 0.75)
II.3.a. 3 principles 3 facts Conditions Narrative
AnalyticalIf the developer client had instructed Engineer A to omit the species risk after verbal disclosure (Q104), compliance would cross an ethical boundary irrespective of client consent, because Section II.3.a's duty of objectivity and truthfulness in reports submitted to a public authority is a professional obligation owed to the public, not one that can be waived by private client instruction. Client consent cannot cure a violation of a duty owed to third parties relying on the report's completeness.
Resolved by: The Board subordinated client instruction and confidentiality interests to the objectivity duty owed to the public authority, holding that a duty owed to third-party reliance cannot be waived by private client consent. (confidence 0.80)
II.3.a. 3 principles 3 facts Conditions Narrative
Principle tension (4)

How should Engineer A balance the duty of Confidentiality of Client Information against the duty of Objectivity in Written Report when a public authority is relying on the report to make a regulatory decision?

AnalyticalThe case resolves the apparent tension between Confidentiality of Client Information and Objectivity in Written Report by treating them as operating on different planes rather than as truly competing obligations: confidentiality protects a client's proprietary business information, but it cannot be invoked to justify omitting a material technical finding from a report submitted to a public authority for regulatory decision-making. Once Engineer A's written report entered the public regulatory process, the duty of objectivity and truthfulness under Section II.3.a effectively superseded any claim that the species-threat information was protected client information, since the finding concerned public environmental welfare rather than the developer's private business affairs.
Resolved by: The board resolves the apparent conflict not by balancing the two duties against each other but by declaring confidentiality inapplicable once the report enters public regulatory use, so objectivity operates without a genuine competing claim. (confidence 0.85)
II.3.a. III.4. 3 principles 3 facts Conditions Narrative

Does Loyalty to Developer Client conflict with Public Welfare in Wetlands Case when the developer's commercial interest in project approval is undermined by disclosure of a threat to a protected species?

Also discussed in: C303

How should Complete Reporting in Written Report be balanced against Transparency in Client Disclosure when the engineer chooses to satisfy the latter through verbal communication rather than formal documentation?

AnalyticalVerbal disclosure to the developer client (Transparency in Client Disclosure) and complete written disclosure to the public authority (Complete Reporting in Written Report) are not interchangeable or substitutable obligations, even though Engineer A treated them as such. The Board's conclusion implies a layered structure of duties: an engineer must first advise the client fully, but that private advisement does not discharge the separate, non-delegable duty to ensure the same material information reaches the public body relying on the report. Prioritizing client-facing transparency over public-facing completeness inverts the hierarchy the Code intends, since the public authority's decision-making need is the higher-order concern when a report is prepared for submission to it.
Resolved by: The board layers the two obligations hierarchically rather than treating them as substitutable, holding that satisfying the client-facing duty does not discharge the separate public-facing completeness duty. (confidence 0.80)
II.3.a. I.3. 3 principles 3 facts Conditions Narrative

Is there an inherent tension between Environmental Stewardship in Wetlands Analysis and Loyalty to Developer Client that the NSPE Code's sustainable development provision is meant to resolve in favor of environmental disclosure?

AnalyticalRather than existing in true conflict, Environmental Stewardship in Wetlands Analysis and the engineer's objectivity/reporting duties are mutually reinforcing in this case: the sustainable development encouragement in Section III.2.d supports, rather than competes with, the mandatory truthfulness requirement of Section II.3.a. This shows that when an aspirational environmental principle and a binding reporting obligation point in the same direction, the Board treats the binding duty (complete and objective reporting) as the operative basis for a violation finding, while the environmental principle serves as contextual reinforcement rather than an independent source of the violation. Loyalty to Developer Client is subordinated in this alignment, not because it is unimportant, but because it cannot justify withholding information the public authority needs for an accurate regulatory determination.
Resolved by: The Board treated the mandatory objectivity and truthfulness duty as controlling the violation finding, used the aspirational environmental stewardship provision only as reinforcing context, and subordinated loyalty to the developer client because it could not justify withholding information the public authority needed. (confidence 0.50)
II.3.a. III.2.d. 3 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill the professional duty of objective and truthful reporting under Section II.3.a by omitting the biologist's threatened species finding from the written report submitted to the public authority?

AnalyticalFrom a deontological standpoint (Q301), Engineer A failed to fulfill the duty of objective and truthful reporting under Section II.3.a. The duty is not conditional on client preference or commercial consequence; it is a categorical obligation attaching to any report submitted for public reliance. Omission of a known, professionally identified risk constitutes a failure of this duty regardless of Engineer A's intent to be forthright with the client.
Resolved by: The deontological analysis treated the II.3.a duty as categorical, so client-directed intent or commercial consequence could not offset the failure to disclose a known risk in the report itself. (confidence 0.80)
II.3.a. I.3. I.5. 3 principles 3 facts Conditions Narrative

From a consequentialist perspective, did the potential benefit to the developer client of omitting the threatened species information from the public report outweigh the potential harm to the wetlands ecosystem and to informed public decision-making?

AnalyticalA consequentialist analysis (Q302) supports the Board's conclusion: the localized commercial benefit to the developer from omitting the finding is outweighed by the diffuse but significant harm of impaired regulatory decision-making, potential habitat degradation, and erosion of public trust in engineering reports submitted for approval processes. The asymmetry between concentrated private gain and dispersed public harm favors disclosure as the ethically superior outcome.
Resolved by: The consequentialist weighing set concentrated private commercial gain against diffuse but significant public and environmental harms, finding the latter to outweigh the former. (confidence 0.78)
II.3.a. III.2.d. 3 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity, as a virtue-ethics analysis would require, by disclosing the threatened species concern verbally to the client while withholding it from the formal written report relied upon by the public authority?

AnalyticalUnder a virtue-ethics lens (Q303), Engineer A's conduct reflects a divided professional character: candor toward the client but concealment toward the public authority. True professional integrity requires consistency of disclosure across all parties relying on the engineer's expertise; selectively sharing material findings undermines the virtue of honesty that the profession's Code is meant to embody.
Resolved by: The virtue-ethics analysis weighed candor toward the client against concealment toward the public authority, finding that selective honesty undermines the unified virtue of integrity the Code presupposes. (confidence 0.75)
II.3.a. I.3. 3 principles 3 facts Conditions Narrative
Counterfactual (4)

If the bird species had been classified as federally 'endangered' rather than merely 'threatened,' would the Board still have reached the same conclusion regarding Engineer A's duty to include the information in the written report, or would the duty have been considered even more clearly mandatory?

AnalyticalHad the species been federally 'endangered' rather than 'threatened' (Q401), the Board's conclusion would likely have been even more unambiguous, as endangered species protections typically trigger stricter statutory disclosure and mitigation requirements. The ethical duty to disclose, already grounded in professional objectivity, would be reinforced by a stronger overlapping legal mandate, leaving even less room for professional discretion in omission.
Resolved by: The board treats statutory classification as reinforcing rather than altering the underlying professional duty, so a stronger legal mandate simply narrows the space in which client loyalty or discretion could compete with disclosure. (confidence 0.75)
II.3.a. I.3. 3 principles 3 facts Conditions Narrative

If Engineer A had not even verbally disclosed the biologist's concern to the developer client, would the Board's finding of an ethics violation regarding the written report omission still stand, or would it be considered a more severe breach of the client advisement duty?

AnalyticalIf Engineer A had failed to disclose the concern even verbally to the developer client (Q402), the ethics violation would extend beyond the reporting omission to a breach of the client advisement duty itself, compounding the violation. The Board's actual finding treats the written report omission as the core violation; without any client disclosure at all, Engineer A would additionally fail the professional duty to keep the client informed of material findings affecting the project's risk profile.
Resolved by: The board separates the client advisement duty from the public reporting duty, so failing both compounds rather than substitutes for a single violation. (confidence 0.80)
II.3.a. I.5. 3 principles 3 facts Conditions Narrative

If the firm's biologist had not identified any threat to the bird species during the analysis, would the Board still have found any duty on Engineer A's part to investigate or report on the species' risk in the written submission?

If the written report had been intended solely for the developer client's internal use and not for submission to a public authority considering the proposal, would the Board still have concluded that omitting the species threat information was unethical?

AnalyticalIf the written report had been intended solely for the developer's internal use rather than submission to a public authority (Q404), the ethical calculus would shift substantially. The Board's conclusion is expressly tied to the report's function as a document relied upon by a public authority in a regulatory proceeding; absent that public reliance, the omission might fall instead under confidentiality and client-disclosure considerations rather than the duty of objective public reporting under Section II.3.a.
Resolved by: The board conditions the applicability of the public objectivity duty on the report's function, so when public reliance is absent the balance shifts toward confidentiality and client-disclosure norms instead. (confidence 0.80)
II.3.a. III.4. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A include the biologist's threatened species finding in the written report submitted to the public authority, or omit it and rely on other forms of disclosure?

Options considered:
O1 Include the biologist's threatened species finding in the written report submitted to the public authority, ensuring the regulator has complete and objective information. Board's choice
O2 Omit the finding from the written report while verbally informing the developer client, treating the private disclosure as sufficient professional diligence.
O3 Omit the finding from the written report on the basis that it constitutes confidential client business information not subject to public disclosure.
Argument structure (Toulmin):
Grounds

The firm's biologist concluded that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species considered threatened by federal and state regulators; Engineer A omitted this finding from the written report while only informing the developer client verbally.

Warrant

Engineers must be objective and truthful and include all relevant and pertinent information in reports submitted for public reliance (Section II.3.a); Section III.2.d encourages engineers to consider environmental protection in their professional work. These duties are not displaced by client loyalty or confidentiality when a public authority relies on the report.

Rebuttal

The warrant would not apply if the finding fell outside the defined scope of the engineering assignment, if the information were legitimately confidential business data unrelated to public welfare, or if the report were intended solely for the client's internal use rather than for public authority reliance.

Engineer A Report Inclusion Duty

Should Engineer A disclose the species risk to the developer client and advise that it will be included in the written report, or disclose the risk verbally while omitting it from the report without further advisement?

Options considered:
O1 Verbally disclose the species risk to the client and explicitly advise that the finding will be included in the written report submitted to the public authority. Board's choice
O2 Verbally inform the client of the risk but do not advise that it will be excluded from the written report, treating verbal notice as adequate client management.
O3 Do not disclose the biologist's finding to the client at all, treating it as an internal technical matter not requiring client notification.
Argument structure (Toulmin):
Grounds

Engineer A verbally informed the developer client of the biologist's opinion but did not advise the client that the finding would appear in the written report, and the finding was in fact omitted from that report.

Warrant

Engineers owe clients a duty of transparency regarding material findings affecting their project (Client Advisement Duty), but this private duty is separate from, and does not substitute for, the non-delegable duty of complete and objective public reporting under Section II.3.a.

Rebuttal

The warrant would not apply if the client relationship were the sole audience for the report and no public authority would ever rely on it, in which case client advisement alone might suffice.

Engineer A Client Advisement Duty

Should Engineer A apply the same disclosure standard regardless of the species' 'threatened' versus 'endangered' classification, or calibrate the level of disclosure to the regulatory severity of that classification?

Options considered:
O1 Disclose the finding based on the materiality of the biologist's risk conclusion, treating 'threatened' and 'endangered' classifications as equally triggering the reporting duty. Board's choice
O2 Treat 'threatened' classification as warranting a lesser disclosure obligation than 'endangered' classification would require.
O3 Seek independent third-party verification of the biologist's in-house finding before determining whether disclosure is warranted, given the biologist's employment within the firm.
Argument structure (Toulmin):
Grounds

The bird species is classified as 'threatened' rather than 'endangered' by federal and state regulators, yet the firm biologist reached an unambiguous conclusion of risk to the species' habitat from the project.

Warrant

The duty of objective and complete reporting under Section II.3.a applies whenever a qualified professional identifies a material risk relevant to a project's environmental impact, without regard to the severity tier of the regulatory classification.

Rebuttal

This warrant would not apply if the underlying ecological risk were shown to be negligible for lesser-protected species, or if applicable environmental statutes made disclosure obligations turn explicitly on classification tier.

Engineer A Client Risk Disclosure Duty

If instructed by the developer client to omit the species risk finding from the written report, should Engineer A refuse and include the finding, or comply with the client's instruction?

Options considered:
O1 Decline the client's instruction to omit the finding and include it in the written report submitted to the public authority. Board's choice
O2 Follow the client's instruction and exclude the species risk finding from the written report to preserve the client relationship.
O3 Decline to continue the engagement rather than either submitting a report the engineer believes is incomplete or directly defying the client's explicit instruction.
Argument structure (Toulmin):
Grounds

The scenario posits that after Engineer A verbally informs the client of the biologist's finding, the client instructs Engineer A to leave the finding out of the written report submitted to the public authority.

Warrant

Section II.3.a's objectivity and truthfulness requirement is a duty owed to the public authority relying on the report, not a negotiable term of the client engagement, so client consent or instruction cannot waive it; this public-protection warrant prevails over the competing warrant of client loyalty.

Rebuttal

This warrant would not apply if the omitted information were outside the report's defined scope of work or if no public authority were relying on the report for a regulatory decision.

Engineer A Report Inclusion Duty Loyalty to Developer Client

When preparing the report for public authority review, should Engineer A treat the species finding as material public-interest information requiring disclosure, or as confidential client information protected from disclosure?

Options considered:
O1 Treat the species risk finding as material public-interest information required to be included in the report submitted to the public authority. Board's choice
O2 Treat the species risk finding as confidential client business information exempt from inclusion in the public report absent client authorization.
O3 Ask the developer client for explicit consent to include the finding in the written report before proceeding, rather than unilaterally deciding its confidentiality status.
Argument structure (Toulmin):
Grounds

The developer client never requested that the biologist's finding be treated as confidential, and the finding concerns risk to a protected species and wetlands habitat relevant to the public authority's regulatory decision.

Warrant

Confidentiality protects a client's proprietary business information, but it cannot be invoked to justify omitting a material technical finding bearing on public environmental welfare from a report submitted for regulatory reliance under Section II.3.a; the objectivity duty supersedes confidentiality once the report enters the public regulatory process.

Rebuttal

This warrant would not apply if the client had affirmatively and legitimately designated the finding as confidential proprietary information unrelated to public safety or environmental welfare.

Engineer A Complete Report Duty Confidentiality of Client Information
Event Timeline (12)
12 sequenced 7 actions 5 events
Case timeline
In BER Case No. 97-13, while conducting the bridge inspection, Engineer A noticed an apparent preexisting defective condition in the wall close to where the fatal accident occurred, and surmised it may have contributed to the wall failure.
In BER Case No. 97-13, Police Officer B lost control of his patrol car while traveling across the bridge and crashed into the bridge wall.
In BER Case No. 97-13, the bridge wall failed to restrain the crashing patrol car, which fell to the river below, killing Police Officer B. An apparent preexisting defective condition may have been a contributing factor.
In BER Case No. 04-8, a few months after completing wetland delineation services, Engineer A drove by the client's property and noticed the client had installed substantial fill material across a portion of the wetlands without permits, variances, or permissions, a substantial violation of federal and state law.
Engineer A, a principal in an environmental engineering firm, undertakes an analysis for a developer client of a property adjacent to a protected wetlands area for potential residential condominium development.
Causal-normative reasoning(confidence 0.75)
Because Engineer A undertook the environmental analysis out of faithfulness to the client, this action set in motion the causal chain that surfaced the species threat, meaning the client-serving intent of A1 is what ultimately generated the environmental information that later obligations required to be disclosed.
State changes (1)
  • began: Developer Client Engagement
During the firm's analysis of the property in the present case, the firm's biologist forms the professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species considered threatened by federal and state environmental regulators.
State changes (1)
  • began: Condominium Wetlands Species Risk
The firm's biologist reports to Engineer A his professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species designated as threatened by federal and state regulators.
At stake (1)
  • Protect the Environment for Future Generations
Causal-normative reasoning(confidence 0.70)
A2, the Species Threat Reporting, is guided by Sustainable Development since it represents the point at which the firm's biologist translated the identified ecological threat into a formal communication, setting in motion both the verbal disclosure and the later written omission that ultimately became the subject of the Board's ethical scrutiny.
State changes (1)
  • began: Biologist Bird Threat Awareness
Engineer A verbally mentions the threatened species concern to the developer client during subsequent discussions.
Causal-normative reasoning(confidence 0.70)
The verbal disclosure, guided jointly by faithfulness to client and sustainable development, partially discharged Engineer A's duty to communicate the species threat but did not itself complete the causal path to a proper record, leaving the more consequential written omission to follow and eventually trigger board review.
Engineer A omits the threatened species information from the written report that will be submitted to the public authority considering the developer's proposal. The Board treats this non-performance as Engineer A's conduct and the central ethical decision.
Violates (2)
  • Include All Relevant and Pertinent Information in Reports
  • Protect the Environment for Future Generations
Causal-normative reasoning(confidence 0.85)
The written report omission violates the duty to include all pertinent information and to protect the environment precisely because it suppressed the species threat that had already been identified and verbally acknowledged, and this suppression directly caused the NSPE Board of Ethical Review to evaluate Engineer A's conduct as a breach of public and environmental responsibility despite being guided by loyalty to the client.
State changes (1)
  • began: Report Omission Of Species Concern
The NSPE Board of Directors approves adding Section III.2.d. on sustainable development to the NSPE Code of Ethics, together with a clarifying footnote defining the term.
Causal-normative reasoning(confidence 0.70)
Adding a new code section in the name of sustainable development created the normative material that would later be modified and applied, showing that the profession's institutional response to environmental harm was itself causally necessary for the subsequent evaluative framework used in the ethical determination.
The NSPE House of Delegates votes to modify Section III.2.d. so that engineers are encouraged, rather than shall strive, to adhere to the principles of sustainable development.
Causal-normative reasoning(confidence 0.75)
Modifying the code language, still guided by sustainable development, refined the environmental obligations that the Board of Ethical Review ultimately relied upon, so this action's normative significance lies in supplying the very standard against which Engineer A's earlier written omission was judged.
Applying new Code Section III.2.d. and Section II.3.a. as a matter of first impression, the Board concludes that Engineer A had an obligation to include the threatened species information in the written report and to advise the client of its inclusion.
Causal-normative reasoning(confidence 0.70)
A1, the Board's determination on Engineer A's written report omission, is guided by Sustainable Development, Objectivity and Truthfulness in Reports, and Public Health and Safety Paramountcy because it retrospectively judges whether omitting the species threat from the formal record undermined the accuracy and completeness owed to the public and environment, and this determination only arises because the earlier omission (via Written Report Omission and Code Language Modification) created the ethical question the Board had to resolve.
Narrative (1 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 A, a principal in an environmental engineering firm retained by a developer client to analyze a parcel of land adjacent to a protected wetlands area for a proposed residential condominium project. During your firm's site analysis, one of your staff biologists reports that, in his professional opinion, the condominium development could threaten a bird species inhabiting the adjacent wetlands. The species is classified as "threatened," not "endangered," under applicable federal and state regulations. You raise the biologist's concern verbally with the developer client, but the written report your firm is preparing for submission to the public authority reviewing the development proposal does not currently include this finding. That authority will rely on your firm's report to evaluate the project's environmental impact and permitting status. You must now determine how to handle the biologist's finding as you finalize the report and continue discussions with your client.

Main characters (1)

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 A Roles in this case: Environmental Engineer

Guided by: Transparency in Client Disclosure, Public Welfare in Wetlands Case, Confidentiality of Client Information

Tension between Engineer A Report Inclusion Duty and Loyalty to Developer Client

Engineer A's duty to privately advise the developer client of risks could tempt the engineer to treat that private disclosure as sufficient, leading to omission of the same risk information from the formal report submitted to the public authority, which the omission prohibition forbids.

Tension between Engineer A Complete Report Duty and Confidentiality of Client Information

The duty to include the biologist's environmental findings directly in the report to the public authority may conflict with the duty to first advise the client, since the client may prefer to be consulted or given an opportunity to respond before sensitive ecological findings become part of a public record.

The boundary defining what may permissibly be left out of the report may not match the scope of what the engineer owes the client in terms of risk disclosure, creating ambiguity about whether information withheld from the public report has been adequately communicated to the client instead.

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

Tension between Engineer A Report Inclusion Duty and Loyalty to Developer Client

Engineer A's duty to privately advise the developer client of risks could tempt the engineer to treat that private disclosure as sufficient, leading to omission of the same risk information from the formal report submitted to the public authority, which the omission prohibition forbids.

The duty to include the biologist's environmental findings directly in the report to the public authority may conflict with the duty to first advise the client, since the client may prefer to be consulted or given an opportunity to respond before sensitive ecological findings become part of a public record.

The boundary defining what may permissibly be left out of the report may not match the scope of what the engineer owes the client in terms of risk disclosure, creating ambiguity about whether information withheld from the public report has been adequately communicated to the client instead.

Engineer A's duty to privately advise the developer client of risks could tempt the engineer to treat that private disclosure as sufficient, leading to omission of the same risk information from the formal report submitted to the public authority, which the omission prohibition forbids.

The duty to include the biologist's environmental findings directly in the report to the public authority may conflict with the duty to first advise the client, since the client may prefer to be consulted or given an opportunity to respond before sensitive ecological findings become part of a public record.

The Board’s deliberation

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

It was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority that is considering the developer’s proposal. Engineer A should have included it in the written report and advised the client of its inclusion.
Opening States (10)
Biologist Bird Threat Awareness Report Omission Of Species Concern Developer Client Engagement Client Public Interest Conflict Engineer A Technical Competence Absent Confidential Treatment Unambiguous Risk Conclusions Section III.2.d First Impression Section III.2.d In Force Condominium Wetlands Species Risk
Summary
  • An engineer's duty to submit a complete and accurate report to a public authority overrides any private understanding or informal disclosure made to a paying client.
  • Privately advising a client of a risk does not satisfy an engineer's independent obligation to disclose that same risk in a formal report intended for public reliance.
  • When client loyalty and public welfare conflict over what information belongs in a submitted report, the engineer's paramount duty to protect the public must prevail.

© Licensed under the GNU GPL v3