Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Sustainable Development—Threatened Species
Step 4 of 5
Entity Review

315

Entities

5

Provisions

3

Precedents

17

Questions

26

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
The ethical obligation to disclose the threatened species finding transferred from a contested space — where Engineer A had treated it as a matter of client-service discretion resolved by verbal mention — to a fixed, non-negotiable duty owed directly to the public authority as the party relying on the written report for regulatory decision-making. The Board's conclusions collectively stripped Engineer A of every potential defense (scope limitation, competence gap, confidentiality, regulatory classification threshold, verbal substitution) and transferred full disclosure responsibility to Engineer A in the engineer's capacity as author of a quasi-public regulatory document, with the public authority as the rightful and sole adequate recipient of the material finding.
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
I.3. Issue public statements only in an objective and truthful manner.
How this applies in the case (showing 3 of 26)
Obligation
Engineer A Threatened Species Written Report Inclusion Obligation Instance
I.3 requires objective and truthful public statements, directly requiring inclusion of the threatened species finding in the report.
Action
Omit Finding from Written Report
Omitting the threatened species finding from the written report violates the duty to issue public statements only in an objective and truthful manner.
State
Verbal-Only Threatened Species Advisory Without Written Record
Communicating the finding only verbally without a written record undermines the objectivity and truthfulness required in public statements.
Obligation (5)
  • Engineer A Threatened Species Written Report Inclusion Obligation Instance
    I.3 requires objective and truthful public statements, directly requiring inclusion of the threatened species finding in the report.
  • Engineer A Non-Endangered Threatened Species Written Report Completeness Obligation Instance
    I.3 requires truthful public statements, supporting the obligation to include environmental risk findings in reports to public authorities.
  • Engineer A Verbal-Only Disclosure Insufficiency Obligation Instance
    I.3 requires objective and truthful public statements, meaning verbal-only disclosure is insufficient to satisfy the obligation.
  • Engineer A Objective Complete Reporting Public Authority Obligation Instance
    I.3 directly requires objectivity and truthfulness in statements issued to public bodies.
  • Engineer A Environmental Principal Objective Completeness Written Report Current Case
    I.3 requires objective and truthful public statements, directly underpinning the obligation to produce a complete written report.
Action (2)
  • Omit Finding from Written Report
    Omitting the threatened species finding from the written report violates the duty to issue public statements only in an objective and truthful manner.
  • Verbally Disclose Concern to Client
    Verbally disclosing the concern supports objectivity and truthfulness in communicating relevant findings.
State (4)
  • Verbal-Only Threatened Species Advisory Without Written Record
    Communicating the finding only verbally without a written record undermines the objectivity and truthfulness required in public statements.
  • Undisclosed Threatened Species Risk in Public Authority Report
    Omitting the threatened species finding from the public authority report violates the obligation to issue public statements in an objective and truthful manner.
  • Client-Interest vs. Public-Interest Conflict. Environmental Finding Omission
    The conflict over omitting the finding directly implicates the duty to be objective and truthful in statements affecting the public.
  • Engineer A Technically Confirmed Environmental Finding. Omission Instruction
    An instruction to omit a confirmed finding from a report contradicts the requirement to issue only objective and truthful public statements.
Constraint (6)
  • Incomplete Risk Disclosure Prohibition. Engineer A Threatened Species Written Report
    I.3 requires truthful public statements, directly creating the prohibition against omitting the known threatened species risk from the written report.
  • Threatened Species Non-Endangered Written Report Inclusion Constraint. Engineer A Condominium Development Case
    I.3 requires objective and truthful public statements, directly mandating inclusion of the biologist's threatened species finding in the report.
  • Verbal Client Mention Non-Substitution Written Public Authority Report Constraint. Engineer A
    I.3 requires truthful public statements, meaning a private verbal mention cannot substitute for truthful written disclosure to the public authority.
  • Written Report Completeness Constraint. Engineer A Threatened Species Omission
    I.3 requires truthful and objective public statements, directly mandating that all relevant factual information including the threatened species finding be included.
  • Competence-Confirmed Environmental Finding Omission Prohibition. Engineer A Biologist Report
    I.3 requires truthful public statements, prohibiting omission of a technically confirmed finding from the written report.
  • Engineer A Domain Competence Confirmed Finding Written Report Inclusion. Threatened Species Current Case
    I.3 requires objective and truthful public statements, mandating inclusion of the confirmed threatened species habitat finding in the report.
Principle (4)
  • Honesty in Professional Representations Violated by Written Report Omission
    I.3 requires objective and truthful public statements, which Engineer A violated by omitting the threatened species finding from the report.
  • Objective Completeness in Public Authority Reports Violated by Engineer A
    I.3 directly requires objectivity and truthfulness in public statements, which Engineer A failed by submitting an incomplete report to the public authority.
  • Threatened Species Environmental Reporting Obligation Violated by Engineer A
    I.3 obligates truthful public statements, and Engineer A's omission of the biologist's material finding violates this standard.
  • Objective Completeness Obligation Under NSPE Code Section II.3.a.
    I.3 parallels the objectivity and truthfulness requirement that underpins Engineer A's completeness obligation in public reporting.
Event (1)
  • Written Report Submitted to Authority
    The report submitted must be objective and truthful as required by this provision.
Capability (4)
  • Engineer A Objective Complete Environmental Report Submission Capability Instance
    I.3 requires public statements be objective and truthful, directly relating to Engineer A's failure to submit a complete and objective report to the public authority.
  • Engineer A Environmental Firm Principal Objective Complete Report Public Authority
    I.3 requires objectivity and truthfulness in public statements, which applies to the obligation to submit a complete environmental assessment report to the public authority.
  • Engineer A Environmental Firm Principal Verbal Mention Non-Substitution Recognition
    I.3 requires truthful public statements, meaning a verbal mention to the developer cannot substitute for an objective written report to the public authority.
  • Engineer A Verbal Mention Non-Substitution Capability Instance
    I.3 requires objective and truthful public statements, directly relating to the failure to recognize that verbal mention to the client does not satisfy the obligation to report truthfully to the public authority.
I.5. Avoid deceptive acts.
How this applies in the case (showing 3 of 28)
Obligation
Engineer A Threatened Species Written Report Inclusion Obligation Instance
I.5 prohibits deceptive acts, and omitting the threatened species finding from the written report would constitute a deceptive act.
Action
Omit Finding from Written Report
Omitting a material finding from the written report constitutes a deceptive act that this provision directly prohibits.
State
Undisclosed Threatened Species Risk in Public Authority Report
Omitting a confirmed threatened species finding from the submitted report constitutes a deceptive act toward the public authority.
Obligation (5)
  • Engineer A Threatened Species Written Report Inclusion Obligation Instance
    I.5 prohibits deceptive acts, and omitting the threatened species finding from the written report would constitute a deceptive act.
  • Engineer A Verbal-Only Disclosure Insufficiency Obligation Instance
    I.5 prohibits deceptive acts, and relying solely on verbal mention while omitting findings from the written report would be deceptive.
  • Engineer A Client Verbal Mention Non-Substitution Obligation Instance
    I.5 prohibits deceptive acts, meaning treating a verbal mention as a substitute for written disclosure would be deceptive.
  • Engineer A Public Welfare Paramount Threatened Species Omission Obligation Instance
    I.5 prohibits deceptive acts, and omitting the threatened species finding from the report to protect client interests would be deceptive.
  • Engineer A Environmental Principal Client Confidentiality Non-Invocation Disclosure Facilitation Current Case
    I.5 prohibits deceptive acts, supporting the obligation not to invoke confidentiality as a pretext to omit material findings.
Action (1)
  • Omit Finding from Written Report
    Omitting a material finding from the written report constitutes a deceptive act that this provision directly prohibits.
State (5)
  • Undisclosed Threatened Species Risk in Public Authority Report
    Omitting a confirmed threatened species finding from the submitted report constitutes a deceptive act toward the public authority.
  • Engineer A Technically Confirmed Environmental Finding. Omission Instruction
    Following an instruction to omit a confirmed finding would be a deceptive act by Engineer A.
  • Verbal-Only Threatened Species Advisory Without Written Record
    Limiting disclosure to a verbal-only advisory while submitting an incomplete written report to the public authority is a deceptive act.
  • Client-Interest vs. Public-Interest Conflict. Environmental Finding Omission
    Choosing client interest over truthful disclosure by omitting the finding constitutes a deceptive act toward the public authority.
  • BER 97-13 Confidentiality Instruction Suppressing Structural Observation
    The analogous instruction to suppress a material observation from a final report parallels the deceptive act concern in the present case.
Constraint (6)
  • Incomplete Risk Disclosure Prohibition. Engineer A Threatened Species Written Report
    I.5 prohibits deceptive acts, directly creating the prohibition against omitting the known threatened species risk from the written report.
  • Threatened Species Non-Endangered Written Report Inclusion Constraint. Engineer A Condominium Development Case
    I.5 prohibits deceptive acts, making omission of the biologist's threatened species finding from the report a deceptive act.
  • Verbal Client Mention Non-Substitution Written Public Authority Report Constraint. Engineer A
    I.5 prohibits deceptive acts, meaning substituting a private verbal mention for written public disclosure would constitute a deceptive omission.
  • Written Report Completeness Constraint. Engineer A Threatened Species Omission
    I.5 prohibits deceptive acts, directly requiring that the written report not omit the confirmed threatened species finding.
  • Faithful Agent Boundary Constraint. Engineer A Post-Confirmed Environmental Finding
    I.5 prohibits deceptive acts, establishing that suppressing a confirmed finding from the written report on behalf of a client constitutes a deceptive act.
  • Competence-Confirmed Environmental Finding Omission Prohibition. Engineer A Biologist Report
    I.5 prohibits deceptive acts, making omission of a technically confirmed finding from the public report deceptive.
Principle (4)
  • Honesty in Professional Representations Violated by Written Report Omission
    I.5 prohibits deceptive acts, and omitting a material finding from a professional report constitutes a deceptive act.
  • Objective Completeness in Public Authority Reports Violated by Engineer A
    I.5 forbids deception, and submitting a report that omits a known material environmental finding to a public authority is deceptive.
  • Threatened Species Environmental Reporting Obligation Violated by Engineer A
    I.5 bars deceptive acts, and Engineer A's suppression of the threatened species finding from the written report is a deceptive omission.
  • Faithful Agent Obligation Bounded by Public Welfare in Environmental Assessment
    I.5 sets an ethical limit on faithful agent conduct by prohibiting deceptive acts even when serving a client's interests.
Event (1)
  • Written Report Submitted to Authority
    Submitting the report must avoid any deceptive acts or omissions regarding the threatened species findings.
Capability (6)
  • Engineer A Objective Complete Environmental Report Submission Capability Instance
    I.5 requires avoiding deceptive acts, and omitting the threatened species finding from the written report constitutes a deceptive act.
  • Engineer A Environmental Firm Principal Objective Complete Report Public Authority
    I.5 prohibits deceptive acts, directly applying to the obligation to not omit material findings from the environmental report submitted to the public authority.
  • Engineer A Verbal Mention Non-Substitution Capability Instance
    I.5 prohibits deceptive acts, and substituting a verbal mention for written disclosure of a material finding is a form of deception.
  • Engineer A Environmental Firm Principal Verbal Mention Non-Substitution Recognition
    I.5 prohibits deceptive acts, meaning Engineer A was required to recognize that omitting the finding from the written report while only verbally mentioning it was deceptive.
  • Engineer A Non-Endangered Threatened Species Classification Knowledge Instance
    I.5 prohibits deceptive acts, and misclassifying a threatened species as non-endangered to justify omission would constitute a deceptive act.
  • Engineer A Environmental Firm Principal Non-Endangered Threatened Species Classification Knowledge
    I.5 prohibits deceptive acts, requiring Engineer A to correctly apply species classification knowledge rather than use misclassification to justify omitting the finding.
II.3.a. 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 52)
Obligation
Engineer A Threatened Species Written Report Inclusion Obligation Instance
II.3.a. directly requires inclusion of all relevant and pertinent information in professional reports, mandating inclusion of the threatened species finding.
Action
Integrate Biologist's Threatened Species Finding
Including the biologist's finding in the report fulfills the obligation to include all relevant and pertinent information in professional reports.
State
Undisclosed Threatened Species Risk in Public Authority Report
The written report submitted to the public authority omits relevant and pertinent information, violating the duty to include all such information in professional reports.
Obligation (10)
  • Engineer A Threatened Species Written Report Inclusion Obligation Instance
    II.3.a. directly requires inclusion of all relevant and pertinent information in professional reports, mandating inclusion of the threatened species finding.
  • Engineer A Non-Endangered Threatened Species Written Report Completeness Obligation Instance
    II.3.a. requires completeness in professional reports submitted to public authorities, directly supporting this obligation.
  • Engineer A Verbal-Only Disclosure Insufficiency Obligation Instance
    II.3.a. requires that all relevant information appear in written reports, making verbal-only disclosure insufficient.
  • Engineer A Client Verbal Mention Non-Substitution Obligation Instance
    II.3.a. requires written reports to contain all pertinent information, so verbal mention cannot substitute for written inclusion.
  • Engineer A Objective Complete Reporting Public Authority Obligation Instance
    II.3.a. directly mandates objectivity, truthfulness, and completeness in reports submitted to public authorities.
  • Engineer A Environmental Principal Expertise-Calibrated Disclosure BER Current Case
    II.3.a. requires inclusion of all relevant findings in professional reports, directly supporting the obligation to include the biologist-informed threatened species finding.
  • Engineer A Environmental Principal Objective Completeness Written Report Current Case
    II.3.a. is explicitly cited as the basis for the obligation to be objective and complete in the written environmental assessment report.
  • Engineer A Environmental Principal Client Notification of Inclusion Current Case
    II.3.a. requires complete reporting, which supports the obligation to advise the client that the finding will be included in the report.
  • Engineer A Faithful Agent Within Ethical Limits Developer Client Obligation Instance
    II.3.a. bounds the faithful agent role by requiring objective and complete professional reporting regardless of client preferences.
  • Engineer A Environmental Principal Faithful Agent Bounded by Public Welfare Current Case
    II.3.a. establishes the objective completeness reporting duty that bounds the faithful agent obligation to the developer client.
Action (3)
  • Integrate Biologist's Threatened Species Finding
    Including the biologist's finding in the report fulfills the obligation to include all relevant and pertinent information in professional reports.
  • Omit Finding from Written Report
    Omitting the threatened species finding from the written report directly violates the requirement to include all relevant information in professional reports.
  • Verbally Disclose Concern to Client
    Verbal disclosure alone without written documentation falls short of the obligation to provide complete and truthful professional reports.
State (8)
  • Undisclosed Threatened Species Risk in Public Authority Report
    The written report submitted to the public authority omits relevant and pertinent information, violating the duty to include all such information in professional reports.
  • Engineer A Technically Confirmed Environmental Finding. Omission Instruction
    A confirmed finding is relevant and pertinent information that must be included in the professional report per this provision.
  • Client-Interest vs. Public-Interest Conflict. Environmental Finding Omission
    This provision directly governs the obligation to include the threatened species finding in the report regardless of client preference.
  • Verbal-Only Threatened Species Advisory Without Written Record
    Conveying the finding only verbally rather than in the written report fails the requirement to include all relevant information in professional reports.
  • BER 97-13 Confidentiality Instruction Suppressing Structural Observation
    The analogous suppression of a material observation from a final report in BER 97-13 directly parallels the II.3.a. obligation at issue here.
  • Present Case Engineer A, Competence-Confirmed Environmental Finding
    A technically confirmed finding within Engineer A's competence is precisely the kind of pertinent information II.3.a. requires to be included in professional reports.
  • Engineer A Faithful Agent Boundary. Post-Confirmed Finding
    This provision defines the boundary of faithful agency by requiring inclusion of confirmed pertinent findings in professional reports.
  • Regulatory Compliance State for Public Authority Development Review
    The report is a submitted document in a public authority review process, making the completeness requirement of II.3.a. directly applicable.
Constraint (10)
  • Incomplete Risk Disclosure Prohibition. Engineer A Threatened Species Written Report
    II.3.a requires inclusion of all relevant and pertinent information in reports, directly prohibiting omission of the known threatened species risk.
  • Threatened Species Non-Endangered Written Report Inclusion Constraint. Engineer A Condominium Development Case
    II.3.a requires all relevant information in professional reports, directly mandating inclusion of the biologist's threatened species finding.
  • Verbal Client Mention Non-Substitution Written Public Authority Report Constraint. Engineer A
    II.3.a requires complete written reports to public authorities, directly establishing that a verbal client mention cannot substitute for written disclosure.
  • Written Report Completeness Constraint. Engineer A Threatened Species Omission
    II.3.a explicitly requires all relevant and pertinent information in reports, directly creating the written report completeness constraint.
  • Competence-Confirmed Environmental Finding Omission Prohibition. Engineer A Biologist Report
    II.3.a requires inclusion of all relevant information in reports, prohibiting omission of a domain-competence-confirmed finding.
  • Engineer A Domain Competence Confirmed Finding Written Report Inclusion. Threatened Species Current Case
    II.3.a directly mandates inclusion of all relevant pertinent information in professional reports, requiring the threatened species habitat finding be included.
  • Engineer A BER 97-13 Speculative Structural Observation. Scope Limitation and Competence Omission Permissibility
    II.3.a's requirement for objective and pertinent reporting informed the BER 97-13 determination that speculative out-of-scope observations outside competence need not be included.
  • Engineer A BER 97-13 Field Notes Preservation Non-Alteration. Structural Observation
    II.3.a's truthfulness and objectivity requirement supports the constraint against altering or destroying field notes documenting observed conditions.
  • Faithful Agent Boundary Constraint. Engineer A Post-Confirmed Environmental Finding
    II.3.a requires objective and complete professional reports, establishing that faithful agent duty does not extend to suppressing confirmed findings from written reports.
  • Engineer A Specialist Consultation Competence Elevation. Biologist Confirmed Threatened Species Finding
    II.3.a requires inclusion of all relevant information, meaning that specialist-confirmed findings within the report scope cannot be omitted on grounds of personal lack of expertise.
Principle (8)
  • Honesty in Professional Representations Violated by Written Report Omission
    II.3.a. requires all relevant information in professional reports, and Engineer A's omission of the threatened species finding directly violates this provision.
  • Objective Completeness in Public Authority Reports Violated by Engineer A
    II.3.a. explicitly mandates objective and truthful professional reports including all pertinent information, which Engineer A's incomplete report violated.
  • Written Report Completeness Obligation Applied to Threatened Species Finding
    II.3.a. is the direct source of the obligation to include all relevant findings in the written report submitted to the public authority.
  • Objective Completeness Obligation Under NSPE Code Section II.3.a.
    II.3.a. is the exact provision establishing the objectivity and completeness standard applied to Engineer A's report.
  • Threatened Species Environmental Reporting Obligation Violated by Engineer A
    II.3.a. requires inclusion of all relevant information in professional reports, making the omission of the biologist's threatened species finding a direct violation.
  • Incidental Observation Disclosure Obligation Applied to Threatened Species
    II.3.a. requires that all relevant and pertinent information be included in professional reports, encompassing incidental but material observations like the threatened species finding.
  • Scope Limitation Defense Rejected for Environmental Finding
    II.3.a. requires inclusion of all relevant information regardless of scope, supporting rejection of a scope limitation defense for omitting material findings.
  • Factual Certainty Calibration Present Case vs BER 97-13
    II.3.a. requires inclusion of pertinent information in reports, and the factual certainty of the threatened species finding strengthens the obligation to include it under this provision.
Event (3)
  • Written Report Submitted to Authority
    This provision directly governs the objectivity and completeness of professional reports submitted to authorities.
  • Threatened Species Risk Identified
    All relevant information about the threatened species risk must be included in professional reports per this provision.
  • Public Authority Review Initiated
    The authority review relies on truthful and complete professional statements and reports as required by this provision.
Capability (10)
  • Engineer A Objective Complete Environmental Report Submission Capability Instance
    II.3.a requires objective, truthful, and complete professional reports, directly applying to Engineer A's failure to include the threatened species finding in the written report.
  • Engineer A Environmental Firm Principal Objective Complete Report Public Authority
    II.3.a requires that professional reports include all relevant and pertinent information, directly obligating Engineer A to include the threatened species finding in the environmental assessment report.
  • Engineer A Threatened Species Written Report Inclusion Capability Instance
    II.3.a requires inclusion of all relevant information in professional reports, directly relating to Engineer A's failure to include the biologist's threatened species observation in the written report.
  • Engineer A Environmental Firm Principal Threatened Species Written Report Inclusion
    II.3.a requires that all relevant and pertinent information be included in professional reports, directly obligating inclusion of the threatened species finding.
  • Engineer A Verbal Mention Non-Substitution Capability Instance
    II.3.a requires complete written professional reports, meaning a verbal mention cannot substitute for written inclusion of a material finding.
  • Engineer A Environmental Firm Principal Verbal Mention Non-Substitution Recognition
    II.3.a requires complete and truthful written reports, directly supporting the requirement that verbal mention to the client does not satisfy the written reporting obligation.
  • Firm Biologist Upward Reporting Capability Instance
    II.3.a requires complete and truthful professional reports, which depends on the biologist fully reporting the threatened species observation to Engineer A without filtering.
  • Firm Biologist Epistemic Humility Upward Reporting
    II.3.a requires complete inclusion of all relevant information in reports, which requires the biologist to report the observation completely and without independent filtering to Engineer A.
  • Engineer A Environmental Firm Principal Expertise-Calibrated Disclosure Determination
    II.3.a requires objective and complete professional reports, and Engineer A's domain expertise obligated a determination that the threatened species finding was relevant and pertinent information requiring inclusion.
  • Engineer A Environmental Firm Principal BER Precedent Triangulation
    II.3.a is the core reporting obligation that BER precedent triangulation confirmed applies to an environmental engineer with domain expertise who omits a material finding from a professional report.
III.2.d. 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 34)
Obligation
Engineer A Sustainable Development Threatened Species Advocacy Obligation Instance
III.2.d. directly encourages adherence to sustainable development principles, including protection of threatened species.
Action
Accept Development Analysis Engagement
Accepting the engagement carries a responsibility to adhere to sustainable development principles, including protecting threatened species.
State
Environmental Hazard from Condominium Development Adjacent to Protected Wetlands
The proposed development adjacent to protected wetlands containing a threatened species is precisely the environmental protection scenario addressed by the sustainable development provision.
Obligation (5)
  • Engineer A Sustainable Development Threatened Species Advocacy Obligation Instance
    III.2.d. directly encourages adherence to sustainable development principles, including protection of threatened species.
  • Engineer A Environmental Stewardship Wetlands Adjacent Assessment Obligation Instance
    III.2.d. encourages sustainable development and environmental stewardship, directly supporting the obligation to assess wetland-adjacent impacts.
  • Engineer A Public Welfare Paramount Threatened Species Omission Obligation Instance
    III.2.d. supports holding ecological welfare paramount by encouraging protection of the environment for future generations.
  • Engineer A Environmental Principal Sustainable Development Code Calibration Current Case
    III.2.d. is explicitly identified as the provision establishing the sustainable development encouragement obligation being calibrated in this case.
  • Engineer A Wetland Delineation Incidental Post-Contract Environmental Escalation BER 04-8
    III.2.d. encourages environmental protection, supporting the obligation to escalate unauthorized wetland fill violations.
Action (3)
  • Accept Development Analysis Engagement
    Accepting the engagement carries a responsibility to adhere to sustainable development principles, including protecting threatened species.
  • Integrate Biologist's Threatened Species Finding
    Integrating the threatened species finding aligns with the principle of sustainable development by protecting the natural resource base and environment.
  • Omit Finding from Written Report
    Omitting the finding undermines sustainable development principles by concealing environmental impacts relevant to future generations.
State (6)
  • Environmental Hazard from Condominium Development Adjacent to Protected Wetlands
    The proposed development adjacent to protected wetlands containing a threatened species is precisely the environmental protection scenario addressed by the sustainable development provision.
  • Threatened Species Habitat Risk from Condominium Development
    Engineer A's environmental analysis engagement directly involves assessing risks to natural resources and environmental quality as contemplated by III.2.d.
  • Present Case Threatened Species Habitat Proximity Development
    The discovery of threatened species habitat adjacent to the development site is a core sustainable development concern requiring protection of environmental quality.
  • NSPE Code Section III.2.d. Encouraged Language Ambiguity
    This entity directly concerns the scope and interpretation of the III.2.d. sustainable development provision itself.
  • Undisclosed Threatened Species Risk in Public Authority Report
    Omitting the threatened species finding undermines the sustainable development obligation to protect environmental quality and natural resources for future generations.
  • Client-Interest vs. Public Interest Conflict Over Environmental Disclosure
    The tension between serving the developer client and protecting the environment reflects the sustainable development obligation under III.2.d.
Constraint (6)
  • Sustainable Development Threatened Species Advocacy Constraint. Engineer A NSPE Code III.2.d
    III.2.d is the direct source provision creating the sustainable development constraint requiring Engineer A to consider and include threatened species findings.
  • Engineer A Sustainable Development Encouraged Provision. Threatened Species Report Inclusion Reinforcement
    III.2.d is explicitly cited as the reinforcing provision that strengthens the obligation to include the threatened species finding in the written report.
  • Public Safety Paramount Constraint. Engineer A Threatened Species Wetlands Development
    III.2.d's sustainable development principle directly supports the paramount obligation to protect ecological welfare of the wetlands and threatened species.
  • Environmental Stewardship Wetlands Adjacent Development Constraint. Engineer A
    III.2.d's sustainable development provision directly relates to the environmental stewardship constraint governing analysis of property adjacent to protected wetlands.
  • Engineer A Pre-Code-Addition Precedent Inapplicability. BER 89-7 and 97-13 Post-Section III.2.d. Cases
    III.2.d is the provision whose post-2007 addition renders prior BER cases incomplete authority, directly creating the precedent inapplicability constraint.
  • Engineer A BER 04-8 Unpermitted Wetland Fill. Client Contact and Remediation Direction
    III.2.d's sustainable development and environmental protection principle directly supports the constraint to address unpermitted wetland fill and direct remediation.
Principle (6)
  • Sustainable Development Obligation Applied to Threatened Species Finding
    III.2.d. directly imposes the sustainable development obligation that Engineer A must apply when the threatened species finding implicates environmental protection.
  • Sustainable Development Obligation Invoked in Environmental Assessment
    III.2.d. is the exact provision cited as placing a sustainable development obligation on Engineer A as an environmental engineer conducting the assessment.
  • Environmental Stewardship Invoked in Wetlands Adjacent Development Assessment
    III.2.d. encourages adherence to sustainable development principles, which encompasses environmental stewardship in assessments adjacent to protected wetlands.
  • Environmental Stewardship Obligation Applied to Threatened Species Reporting
    III.2.d. grounds the environmental stewardship obligation requiring Engineer A to report findings that could threaten species and adjacent wetlands.
  • Public Welfare Paramount Invoked in Engineer-Client Conflict
    III.2.d. supports the public welfare paramount principle by requiring protection of environmental quality and natural resources over client preferences.
  • Faithful Agent Obligation Bounded by Public Welfare in Environmental Assessment
    III.2.d. provides the sustainable development basis for bounding the faithful agent obligation when environmental protection is at stake.
Event (3)
  • Threatened Species Risk Identified
    Identifying threatened species risk directly relates to the sustainable development principle of protecting environmental quality.
  • NSPE Code Section III.2.d Enacted
    This event represents the direct enactment of this specific sustainable development provision.
  • BER Ethical Violation Conclusion Reached
    The BER conclusion on ethical violations is grounded in whether sustainable development principles were upheld.
Capability (5)
  • Engineer A Sustainable Development Threatened Species Advocacy Capability Instance
    III.2.d encourages adherence to sustainable development principles, directly applying to Engineer A's obligation to identify and advocate for inclusion of the threatened species finding.
  • Engineer A Environmental Firm Principal Sustainable Development Code Calibration
    III.2.d is the specific provision whose normative force Engineer A was required to correctly calibrate, recognizing it as an affirmative obligation in the context of an environmental engineering firm.
  • Engineer A Environmental Stewardship Wetlands Assessment Capability Instance
    III.2.d encourages sustainable development and environmental protection, directly relating to Engineer A's capability to conduct environmental stewardship assessment of property adjacent to protected wetlands.
  • Engineer A Environmental Firm Principal Environmental Stewardship Wetlands Assessment
    III.2.d encourages protection of the environment for future generations, directly applying to the obligation to conduct a thorough environmental stewardship assessment near protected wetlands.
  • Engineer A Public Welfare Paramountcy Threatened Species Omission Capability Instance
    III.2.d encourages sustainable development and environmental protection, supporting the obligation to recognize that ecological public welfare requires disclosure of the threatened species finding.
III.4. 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 18)
Obligation
Engineer A Environmental Principal Client Confidentiality Non-Invocation Disclosure Facilitation Current Case
III.4. governs confidentiality of client information, and this obligation directly addresses whether confidentiality was invoked to justify omitting the threatened species finding.
State
Client-Interest vs. Public-Interest Conflict. Environmental Finding Omission
The confidentiality obligation to the developer client is one side of the conflict Engineer A faces when deciding whether to disclose the finding in the public report.
Constraint
Confidential Client Information Constraint. Engineer A Developer Environmental Analysis
III.4 is the direct source of the general confidentiality duty to the developer client that was operative but overridden in this case.
Obligation (3)
  • Engineer A Environmental Principal Client Confidentiality Non-Invocation Disclosure Facilitation Current Case
    III.4. governs confidentiality of client information, and this obligation directly addresses whether confidentiality was invoked to justify omitting the threatened species finding.
  • Engineer A Faithful Agent Within Ethical Limits Developer Client Obligation Instance
    III.4. defines the scope of confidentiality owed to clients, which bounds how faithfully Engineer A can act on the client's behalf regarding disclosure.
  • Engineer A Environmental Principal Faithful Agent Bounded by Public Welfare Current Case
    III.4. is relevant because the faithful agent obligation must be reconciled with the limits of confidentiality when public welfare is at stake.
State (6)
  • Client-Interest vs. Public-Interest Conflict. Environmental Finding Omission
    The confidentiality obligation to the developer client is one side of the conflict Engineer A faces when deciding whether to disclose the finding in the public report.
  • Engineer A Faithful Agent Boundary. Post-Confirmed Finding
    III.4. defines the confidentiality boundary within which Engineer A must act as faithful agent, relevant to determining what information may be withheld from the public report.
  • BER 97-13 Confidentiality Instruction Suppressing Structural Observation
    The confidentiality instruction in BER 97-13 directly invokes III.4. as the basis for suppressing the structural observation from the final report.
  • Client Relationship Established Between Engineer A and Developer
    The existence of a client relationship with the developer triggers the confidentiality obligations under III.4.
  • BER 04-8 Post-Service Environmental Violation Discovery
    The post-service discovery scenario in BER 04-8 raises the question of whether confidentiality obligations under III.4. limit disclosure of client violations.
  • Client Interest vs. Public Interest Conflict Over Environmental Disclosure
    III.4. is directly implicated when weighing whether the developer's preference for omission constitutes a confidentiality interest that limits Engineer A's disclosure obligations.
Constraint (4)
  • Confidential Client Information Constraint. Engineer A Developer Environmental Analysis
    III.4 is the direct source of the general confidentiality duty to the developer client that was operative but overridden in this case.
  • Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint. Engineer A Threatened Species
    III.4 establishes the confidentiality duty whose limits are defined by this constraint, confirming it does not bar inclusion of the threatened species finding in the public report.
  • Engineer A Affirmative Confidentiality Invocation Absence. Threatened Species Finding Current Case
    III.4 is the confidentiality provision that Engineer A was constrained from invoking to treat the threatened species habitat finding as confidential.
  • Faithful Agent Boundary Constraint. Engineer A Post-Confirmed Environmental Finding
    III.4's confidentiality provision is related to the faithful agent boundary, as both duties to the client are overridden by the obligation to disclose confirmed findings in public reports.
Principle (2)
  • Confidentiality Non-Invocation by Client Removes Confidentiality Defense
    III.4. is the confidentiality provision whose applicability is negated because the client never requested confidentiality regarding the threatened species finding.
  • Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship
    III.4. defines the confidentiality duty owed to clients, which is one component of the faithful agent relationship that must be weighed against other ethical obligations.
Capability (3)
  • Engineer A Environmental Firm Principal Confidentiality Non-Invocation Recognition
    III.4 governs confidentiality of client information, and Engineer A was required to recognize that the developer had not invoked confidentiality over the threatened species finding, so III.4 did not bar disclosure.
  • Engineer A Faithful Agent Within Ethical Limits Capability Instance
    III.4 defines the scope of confidentiality obligations to clients, directly relating to whether faithful agent duties to the developer extended to withholding the threatened species finding from the public authority.
  • Engineer A Environmental Firm Principal Expertise-Calibrated Disclosure Determination
    III.4 sets the boundary of confidentiality obligations, and Engineer A's expertise-calibrated determination required recognizing that III.4 did not justify omitting the threatened species finding from the public report.
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:

An environmental engineer who discovers a client's violation of environmental laws must contact the client, point out the violation, advise remedial action in compliance with applicable laws, and if appropriate steps are not taken, bring the matter to the attention of appropriate authorities.

Citation Context:

The Board cited this case as a more recent precedent involving an environmental engineer who discovered a client's illegal wetland fill, establishing that engineers must advise clients of violations and, if corrective action is not taken, report to appropriate 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. A few months after Engineer A completed the services, he drove by his client's property"
discussion: "In its decision, the Board set forth an appropriate course of action for Engineer A concluding that Engineer A should contact the client and inquire about the actions the client had taken and point out the actions were a violation of the law"

Principle Established:

Engineers acting as agents or trustees to clients are expected to maintain confidentiality of information revealed during professional services, particularly when the client has confided in the engineer and the engineer lacks expertise in the technical area involved.

Citation Context:

The Board cited this case to explain the rationale for nondisclosure of confidential client information, noting that engineers act as 'agents' or 'trustees' to their clients and must maintain confidentiality of business affairs.

Relevant Excerpts
discussion: "as noted in BER Case No. 89-7, there are various rationales for the nondisclosure language contained in NSPE Code Section III.4.. Engineers, in the performance of their professional services, act as "agents" or "trustees""
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."

Principle Established:

When an engineer's findings are based on mere surmise and speculation without technical expertise in the relevant discipline, it may be appropriate to verbally report concerns to the client rather than include them in a final written report, provided corrective action is taken within a reasonable time.

Citation Context:

The Board cited this case as a prior example of balancing client confidentiality against public safety obligations, where an engineer verbally reported a potential defect but was asked not to include it in a final report, and the Board found this ethical under the circumstances.

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: "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."
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 52% Facts Similarity 34% Discussion Similarity 22% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 61% Facts Similarity 62% Discussion Similarity 45% Provision Overlap 23% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 55% Discussion Similarity 36% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 44% Facts Similarity 33% Discussion Similarity 54% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 45% Facts Similarity 48% Discussion Similarity 35% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 62%
Shared provisions: I.1, II.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 55% Discussion Similarity 32% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1.a Same outcome True View Synthesis
Component Similarity 47% Facts Similarity 45% Discussion Similarity 59% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1.a Same outcome True View Synthesis
Component Similarity 48% Facts Similarity 38% Discussion Similarity 44% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 40% Facts Similarity 29% Discussion Similarity 27% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 71%
Shared provisions: I.1, III.3.a Same outcome True View Synthesis
Component Similarity 45% Facts Similarity 43% Discussion Similarity 49% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1.a Same outcome True 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.
Implicit (4)

Does Engineer A's verbal disclosure to the developer client satisfy any portion of the ethical obligation to report the threatened species finding, or does the submission of an incomplete written report to a public authority independently constitute an ethical violation regardless of what was communicated privately?

AnalyticalBeyond the Board's finding that omitting the threatened species information from the written report was unethical, the verbal disclosure to the developer client alone was categorically insufficient to satisfy Engineer A's professional obligations to the public authority. The public authority is an independent decision-making body that relies on the written report as its primary evidentiary basis for evaluating the development proposal. A private verbal communication to the client - who has an obvious financial interest in a favorable outcome - cannot substitute for written disclosure in the official record, because the client has no obligation to relay that information to the authority and every incentive not to do so. Engineer A's verbal mention therefore did not discharge any portion of the reporting obligation owed to the public authority; it merely created a private acknowledgment between parties with aligned commercial interests while leaving the regulatory decision-maker uninformed. The ethical violation is thus not merely one of omission from a document but of structural misdirection: the only party who received the material finding was the one party whose interest was served by its suppression.
AnalyticalIn response to Q101: Engineer A's verbal disclosure to the developer client does not satisfy, even in part, the ethical obligation to report the threatened species finding to the public authority. The two communications serve entirely different functions and reach entirely different audiences. The verbal mention to the developer client is a client-service communication; the written report submitted to the public authority is a professional representation on which a regulatory body will rely to make a decision affecting the public. NSPE Code Section II.3.a. requires that engineers be objective and truthful in professional reports submitted to public authorities - an obligation that runs directly to the integrity of the report itself, not merely to whether the engineer has privately acknowledged the finding to someone. The omission from the written report is therefore an independent ethical violation that stands regardless of what was communicated privately. Verbal-only disclosure to the client cannot cure an incomplete written submission to a public authority, because the public authority never receives the benefit of that verbal communication. The ethical obligation is not discharged by telling the party with the strongest interest in suppressing the information; it is discharged only by ensuring the party responsible for protecting the public interest actually receives it in the document on which it will rely.

To what extent does the biologist's finding constitute a confirmed technical fact versus a professional opinion, and does that distinction affect Engineer A's obligation to include it in the written report submitted to the public authority?

AnalyticalIn response to Q102: The biologist's finding occupies a position closer to a confirmed technical fact than to a mere speculative opinion, and that characterization materially strengthens Engineer A's obligation to include it in the written report. The biologist is a credentialed specialist within Engineer A's own firm, reporting through proper internal channels on a matter squarely within his domain competence. His conclusion - that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands - is a professional judgment grounded in direct field observation and biological expertise, not a layperson's guess. This distinguishes the present case sharply from BER Case No. 97-13, where Engineer A's structural observation was a speculative visual impression made outside the engineer's area of competence. Here, the firm has in-house biological expertise, the biologist applied that expertise to the specific site, and the finding is corroborated by the federal and state regulatory classification of the species as 'threatened.' The fact that the biologist used the word 'could' introduces some epistemic qualification, but professional environmental assessments routinely express risk in probabilistic terms; that framing does not reduce a competence-confirmed finding to mere conjecture. Under NSPE Code Section II.3.a., Engineer A is obligated to report findings objectively and completely, and a competence-confirmed risk finding from an in-house specialist is precisely the kind of material information that a public authority needs to make an informed regulatory decision.

Was Engineer A obligated to advise the developer client in advance that the threatened species finding would be included in the written report, and if the client then instructed Engineer A to omit it, what course of action would be ethically required?

AnalyticalIn response to Q103: Engineer A was ethically obligated to advise the developer client that the threatened species finding would be included in the written report before submission, as a matter of professional courtesy and faithful agency - but that obligation to notify the client does not give the client veto power over the report's content. If the developer client, upon being so advised, had explicitly instructed Engineer A to omit the finding, that instruction would not have provided an ethical defense for omission. The NSPE Code's faithful agent obligation operates within ethical limits; it does not authorize an engineer to falsify or materially incomplete a professional report submitted to a public authority at a client's direction. In that scenario, Engineer A would have faced a clear conflict between client instruction and the paramount obligation to protect the public under NSPE Code Sections II.3.a. and I.3. The ethically required course of action would have been to include the finding over the client's objection, to withdraw from the engagement if the client made inclusion a condition of continued service, or - at minimum - to refuse to submit an incomplete report to the public authority. The absence of any explicit confidentiality instruction in the present case, as noted under the Confidentiality Non-Invocation by Client Removes Confidentiality Defense principle, actually makes Engineer A's omission harder to justify, not easier: there was no client instruction to resist, only Engineer A's own choice to omit material information.

Does the fact that the bird species is classified as 'threatened' rather than 'endangered' under federal and state regulatory frameworks materially reduce Engineer A's ethical obligation to disclose the finding in the written report, or is the regulatory classification threshold irrelevant to the completeness obligation under the NSPE Code?

AnalyticalThe threatened-versus-endangered regulatory classification of the bird species is ethically irrelevant to Engineer A's completeness obligation under Section II.3.a. The NSPE Code's truthfulness and objectivity standard does not condition the duty to report material findings on whether those findings meet a particular regulatory severity threshold. A threatened species designation under federal and state environmental law is itself a formal regulatory classification that triggers specific legal protections and is precisely the kind of information a public authority evaluating a development proposal adjacent to protected wetlands would need to make an informed decision. To treat the threatened classification as a lesser concern warranting omission would be to substitute Engineer A's own policy judgment - or the client's commercial preference - for the public authority's right to evaluate all material environmental information. Furthermore, the ethical obligation to be objective and truthful in reports submitted to public authorities is not calibrated to the degree of harm; it is a categorical duty of completeness. The fact that the species had not yet crossed the threshold to endangered status does not diminish the materiality of the finding to the regulatory review process.
AnalyticalIn response to Q104: The 'threatened' rather than 'endangered' regulatory classification does not materially reduce Engineer A's ethical obligation to disclose the finding in the written report, and the regulatory classification threshold is largely irrelevant to the completeness obligation under NSPE Code Section II.3.a. The Code's requirement that engineers be objective and truthful in professional reports does not contain a carve-out for findings that fall below a particular regulatory severity threshold. The relevant question under Section II.3.a. is whether the omitted information is material to the public authority's decision - and a finding that a proposed development could threaten a bird species inhabiting adjacent protected wetlands is plainly material to a regulatory body reviewing that development proposal, regardless of whether the species is classified as threatened or endangered. The threatened classification is itself a formal federal and state regulatory determination that the species faces a significant risk of harm; it is not a finding of minimal concern. Moreover, the ethical obligation to report is grounded in the engineer's duty of objective completeness to the public authority, not in the engineer's independent assessment of whether the regulatory stakes are high enough to warrant disclosure. Allowing engineers to filter material environmental findings based on their own judgment about regulatory classification thresholds would undermine the integrity of the public review process that the reporting obligation is designed to protect.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship conflict with the Public Welfare Paramount Invoked Against Engineer A Omission, and at what point does serving the client's interest in a favorable report cross the line into a violation of the paramount obligation to protect the public?

AnalyticalIn response to Q201: The faithful agent obligation and the public welfare paramount obligation do not conflict in this case in any way that would justify Engineer A's omission - rather, the faithful agent obligation simply reaches its ethical boundary at the point where serving the client's interest requires submitting a materially incomplete professional report to a public authority. The NSPE Code has never treated faithful agency as an unlimited duty; it is explicitly bounded by the engineer's overriding obligation to hold public safety and welfare paramount. The line is crossed when the engineer's report to a public authority omits information that is material to that authority's regulatory decision and that the authority would need in order to protect the public interest. In the present case, the threatened species finding is precisely such information: it is material, it is competence-confirmed, it is directly relevant to the development proposal under review, and its omission leaves the public authority unable to fully evaluate the environmental consequences of approving the project. At that point, the faithful agent obligation does not compete with the public welfare obligation - it simply yields to it. Engineer A could have served the developer client faithfully in many ways: by advising the client of the finding, by explaining the regulatory implications, by helping the client develop a mitigation strategy. What Engineer A could not ethically do was submit an incomplete report to the public authority in order to improve the client's prospects for approval.
AnalyticalThe tension between the Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship and the Public Welfare Paramount Invoked Against Engineer A Omission was resolved decisively in favor of public welfare, but the resolution was not absolute. Engineer A retained a legitimate duty to serve the developer client's interests - including, for example, framing the threatened species finding accurately rather than alarmingly, and advising the client before submission so the client could respond to the finding. What Engineer A could not do was suppress a material environmental finding from a written report submitted to a public authority whose decision-making depended on that report's completeness. The case teaches that the faithful agent obligation functions as a bounded duty: it governs how an engineer serves a client, not whether the engineer may omit safety-relevant or environmentally significant facts from official documents. The boundary is crossed not when the engineer discloses an unfavorable finding, but when the engineer withholds it from a party - here, the public authority - whose legitimate regulatory function requires access to it. Client loyalty, in other words, cannot be exercised at the expense of the integrity of a public regulatory process.

Does the Confidentiality Non-Invocation by Client Removes Confidentiality Defense principle conflict with the Confidential Client Information Constraint, and how should Engineer A determine whether the threatened species finding constitutes confidential business information when no explicit confidentiality instruction was given?

AnalyticalIn response to Q202: The confidentiality constraint under NSPE Code Section III.4. does not provide Engineer A with a defense for the omission in the present case, because no confidentiality instruction was given by the developer client. The Confidentiality Non-Invocation by Client Removes Confidentiality Defense principle is dispositive on this point: confidentiality is a protection that must be affirmatively invoked by the client; it is not a default shield that engineers may apply unilaterally to suppress inconvenient findings. Even if the developer client had invoked confidentiality, the more difficult question would arise of whether a threatened species finding - a matter of direct relevance to a public regulatory proceeding - constitutes the kind of 'confidential business information' that Section III.4. is designed to protect. The better view is that it does not, because the confidentiality provision is aimed at protecting proprietary business information, trade secrets, and sensitive commercial data, not at enabling clients to conceal material environmental risks from the regulatory bodies charged with protecting the public. Where a finding is both material to a public authority's decision and relevant to the protection of a regulated natural resource, the public safety and regulatory disclosure obligations override any confidentiality claim the client might assert. The absence of any confidentiality instruction in the present case makes this analysis straightforward: Engineer A had no confidentiality basis whatsoever for the omission.
AnalyticalThe interaction between the Confidentiality Non-Invocation by Client Removes Confidentiality Defense principle and the Confidential Client Information Constraint reveals an important asymmetry in how confidentiality operates in engineering ethics: confidentiality is a shield the client must affirmatively raise, not a default protection that engineers may invoke on the client's behalf to justify omissions from public documents. Because the developer client gave no explicit confidentiality instruction regarding the threatened species finding, Engineer A had no ethical basis to treat the finding as protected information. More fundamentally, even if confidentiality had been invoked, the Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint would have substantially limited its force in this context: the written report was destined for a public authority conducting a regulatory review, and the threatened species finding was directly material to that review. The case therefore teaches that confidentiality and completeness obligations are not symmetrical - confidentiality requires an affirmative client act to be operative, while the completeness obligation under Section II.3.a. is self-executing and applies to every professional report submitted to a public body, regardless of client preference.

Does the Scope Limitation Defense Rejected for Environmental Finding principle conflict with the Expertise Calibration Applied to Present Case vs BER 97-13 principle, given that in BER 97-13 a scope limitation and competence gap together justified omission of a structural observation, while in the present case Engineer A's firm has domain-competent biologist support - and how should the presence or absence of in-house specialist expertise determine whether an incidental environmental finding must be included in a written report?

AnalyticalIn response to Q203: The scope limitation defense that was accepted in BER Case No. 97-13 does not transfer to the present case, and the critical distinguishing variable is the presence of in-house specialist expertise. In BER 97-13, Engineer A was a bridge sub-consultant who made a speculative visual observation about a potential wall defect that fell outside the scope of the engagement and outside Engineer A's own structural engineering competence. The combination of scope limitation and competence gap together justified the conclusion that Engineer A was not obligated to include that observation in the final report. In the present case, neither condition is met. The threatened species finding was made by a biologist who is a member of Engineer A's own firm, working within the scope of an environmental analysis engagement for a site adjacent to protected wetlands - an environmental assessment is precisely the kind of engagement where biological habitat findings are within scope. The firm's in-house biological expertise means that the finding is not a speculative observation by an unqualified observer but a professional judgment by a domain-competent specialist. The Expertise Calibration Applied to Present Case vs BER 97-13 principle correctly identifies that the presence of in-house specialist expertise eliminates the competence gap that justified omission in BER 97-13. When an engineer's own firm has the expertise to make a finding and that finding is made within the scope of the engagement, the scope limitation defense is unavailable and the completeness obligation under Section II.3.a. applies in full.
AnalyticalThe apparent conflict between the Scope Limitation Defense Rejected for Environmental Finding principle and the Expertise Calibration Applied to Present Case vs BER 97-13 principle is resolved by recognizing that these two principles operate on different axes and are not genuinely in tension when properly understood. In BER Case No. 97-13, two independent factors combined to justify omission of the structural wall observation: the finding was speculative and outside the engineer's domain competence, and a confidentiality instruction had been given. In the present case, neither factor is present. The biologist's threatened species finding was made within the firm's domain competence - Engineer A's own firm employed the biologist - and no confidentiality instruction was given. The Expertise Calibration principle therefore does not create a defense for Engineer A; rather, it confirms that the BER 97-13 precedent is inapplicable precisely because the competence gap that justified omission there does not exist here. The case teaches that scope limitation and competence-based omission defenses are narrow and fact-specific: they require both a genuine competence gap and, ideally, an absence of in-house specialist support. When an engineer's firm has the relevant expertise and the finding is confirmed rather than speculative, the completeness obligation under Section II.3.a. applies with full force, and no scope limitation argument can override it.
AnalyticalThe presence of a domain-competent biologist within Engineer A's own firm is a decisive factor that distinguishes this case from BER Case No. 97-13 and forecloses any scope-limitation or competence-gap defense. In BER 97-13, the engineer's speculative visual observation of a potential structural defect was made outside the engineer's area of competence and outside the defined scope of the sub-consultancy engagement, and a confidentiality instruction had been explicitly issued by the client. In the present case, none of those mitigating conditions exist: the threatened species finding was produced by a qualified biologist employed within Engineer A's firm, it falls squarely within the subject matter of an environmental analysis engagement, and no confidentiality instruction was given. The finding is therefore not speculative or outside competence - it is a professionally grounded opinion from an in-house specialist acting within the scope of the engagement. Because the competence gap and scope limitation that justified omission in BER 97-13 are both absent here, Engineer A had an affirmative obligation to include the biologist's finding in the written report. The absence of an explicit confidentiality instruction further removes the only remaining defense that was available in BER 97-13, leaving Engineer A without any principled basis for the omission.

Does the Sustainable Development Obligation Applied to Threatened Species Finding - an encouraged rather than mandatory provision under NSPE Code Section III.2.d. - conflict with the Objective Completeness Obligation Under NSPE Code Section II.3.a., which is mandatory, in the sense that relying solely on the encouraged sustainable development provision might understate the strength of Engineer A's reporting obligation, and should the Board's conclusion rest primarily on the mandatory completeness standard rather than the aspirational sustainability language?

AnalyticalThe Board's conclusion is most securely grounded in the mandatory completeness and truthfulness standard of NSPE Code Section II.3.a. rather than in the encouraged sustainable development provision of Section III.2.d. This distinction carries significant analytical weight. Section III.2.d., as amended in July 2007, uses aspirational language - engineers 'are encouraged' to adhere to sustainable development principles - and therefore creates a reinforcing but non-binding obligation. Section II.3.a., by contrast, imposes a strict duty: engineers 'shall be objective and truthful in professional reports.' A written report submitted to a public authority that omits a material environmental finding identified by a domain-competent biologist within the same firm is not objective and truthful in the sense required by Section II.3.a., regardless of whether sustainable development principles are separately invoked. Relying primarily on Section III.2.d. would understate the strength of the violation and create a misleading impression that the reporting obligation is merely aspirational. The Board's conclusion should therefore be understood as resting on a mandatory duty, with Section III.2.d. serving only as a secondary, reinforcing consideration that underscores the environmental significance of the omitted finding.
AnalyticalIn response to Q204: The Board's conclusion rests most securely on the mandatory completeness standard under NSPE Code Section II.3.a. rather than on the encouraged sustainable development provision under Section III.2.d., and the distinction between these two provisions matters significantly for the strength and clarity of the ethical analysis. Section II.3.a. imposes a mandatory duty: engineers shall be objective and truthful in professional reports. The omission of a competence-confirmed threatened species finding from a written report submitted to a public authority is a direct violation of that mandatory standard, regardless of any other provision. Section III.2.d., by contrast, uses the word 'encouraged' - it is an aspirational provision that reinforces the reporting obligation but does not independently create a mandatory duty. Relying primarily on Section III.2.d. to ground the violation conclusion would understate the strength of Engineer A's obligation and could suggest that the duty to report environmental findings is merely aspirational rather than mandatory. The correct analytical structure is to treat Section II.3.a. as the primary and sufficient basis for the violation finding, with Section III.2.d. serving as a reinforcing consideration that reflects the Code's broader commitment to environmental stewardship. This tiered structure - mandatory duty violated, aspirational provision also implicated - produces a stronger and more defensible conclusion than one that blends the two provisions without distinguishing their normative weight.
AnalyticalThe relationship between the Sustainable Development Obligation Applied to Threatened Species Finding under NSPE Code Section III.2.d. and the Objective Completeness Obligation Under NSPE Code Section II.3.a. reveals a critical structural feature of the NSPE Code's tiered obligation architecture: mandatory duties and encouraged aspirations can point in the same direction, but they carry different normative weights and should not be conflated in ethical analysis. The Board's conclusion that Engineer A acted unethically rests most securely on the mandatory completeness and truthfulness standard of Section II.3.a., which admits no exception for client preference or report scope. The sustainable development provision of Section III.2.d., while reinforcing the conclusion, is an encouraged rather than mandatory standard and therefore cannot independently sustain a finding of ethical violation. The case teaches that when a mandatory provision and an encouraged provision both support the same conclusion, the ethical analysis should be anchored to the mandatory provision and the encouraged provision treated as corroborating context. Relying primarily on the aspirational provision would both overstate its normative force and understate the strength of the mandatory duty, potentially creating a misleading precedent that the sustainable development obligation carries the same obligatory weight as the truthfulness and completeness requirements.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill their categorical duty of truthfulness and completeness to the public authority by verbally disclosing the threatened species risk to the developer client alone, or does the duty of objective and truthful professional reporting require written disclosure to every party relying on the report regardless of client preference?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A did not fulfill the categorical duty of truthfulness and completeness by verbally disclosing the threatened species risk to the developer client alone. A deontological analysis grounded in Kantian ethics would ask whether Engineer A's conduct could be universalized as a maxim: if all engineers preparing reports for public authorities were permitted to omit material findings from written submissions so long as they mentioned those findings verbally to the client, the institution of professional reporting to public authorities would be rendered meaningless. The public authority's reliance on the written report is not incidental - it is the entire purpose of the submission. The duty of objective and truthful professional reporting under Section II.3.a. is owed to every party who relies on the report in their official capacity, not merely to the party who commissioned it. A deontological framework would further recognize that the developer client and the public authority are not interchangeable recipients: the client has a direct financial interest in the outcome of the regulatory review, while the public authority is the institutional representative of the public interest. Disclosing only to the party with the strongest incentive to suppress the information, while withholding it from the party charged with protecting the public, inverts the engineer's duty structure. The categorical duty of truthfulness in professional representations requires written disclosure to the public authority as an independent and non-delegable obligation.

From a consequentialist perspective, did the aggregate harm to the threatened bird species, the protected wetlands ecosystem, and the integrity of the public authority's decision-making process outweigh any benefit Engineer A provided to the developer client by omitting the threatened species finding from the written report, and how should those harms be weighted against each other?

AnalyticalIn response to Q302: From a consequentialist perspective, the aggregate harm produced by Engineer A's omission substantially outweighs any benefit conferred on the developer client. The harms are multiple and compound: the threatened bird species and its protected wetlands habitat face development pressure without the regulatory protection that a complete disclosure would have triggered; the public authority is deprived of material information needed to make an informed regulatory decision, corrupting the integrity of the public review process; and the broader public interest in accurate environmental assessment of development proposals adjacent to protected areas is undermined. The benefit to the developer client - an improved prospect of regulatory approval in the short term - is both narrow in scope and ethically tainted, because it is achieved by withholding information from the regulatory body rather than by demonstrating that the project can proceed without unacceptable environmental harm. A consequentialist analysis would also account for systemic effects: if engineers routinely omitted inconvenient environmental findings from public authority reports, the cumulative harm to protected ecosystems and to the integrity of environmental regulation would be severe. The harm to the threatened species and the wetlands ecosystem is not easily reversible once development proceeds, while the harm to the developer client from inclusion of the finding - delay, redesign, or denial - is a legitimate regulatory consequence rather than an unjust harm. The consequentialist calculus therefore strongly supports the conclusion that Engineer A's omission was unethical.

From a virtue ethics perspective, did Engineer A demonstrate the professional integrity, courage, and environmental stewardship expected of a principal in an environmental engineering firm when they chose verbal-only disclosure to the client rather than written disclosure in the public authority report, and does this conduct reflect the character of a trustworthy environmental professional?

AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A's conduct falls short of the professional character expected of a principal in an environmental engineering firm. Virtue ethics asks not merely whether a rule was violated but whether the agent demonstrated the character traits - integrity, courage, honesty, and stewardship - that define a trustworthy professional. A principal in an environmental engineering firm occupies a position of particular responsibility: the firm's entire professional purpose is to provide objective environmental analysis that informs decisions affecting natural resources and the public. Choosing verbal-only disclosure to the client, while submitting a written report to a public authority that omits a material environmental finding, reflects a failure of professional courage - the willingness to deliver unwelcome findings to clients and to stand behind those findings in official submissions. It also reflects a failure of environmental stewardship, which is a core virtue for professionals in this field. The virtue of integrity requires consistency between what the engineer knows, what the engineer says privately, and what the engineer represents officially. Engineer A knew of the threatened species risk, mentioned it privately to the client, and then omitted it from the official record - a pattern that is inconsistent with the integrated professional character that virtue ethics demands. A trustworthy environmental professional would have included the finding in the written report, advised the client of its inclusion, and helped the client navigate the regulatory implications rather than shielding the client from them.

From a deontological perspective, does the NSPE Code's distinction between mandatory duties such as objective and truthful reporting under Section II.3.a. and encouraged provisions such as sustainable development under Section III.2.d. create a tiered obligation structure, and if so, is Engineer A's omission a violation of a strict duty, an encouraged aspiration, or both simultaneously?

AnalyticalIn response to Q304: The NSPE Code does create a tiered obligation structure distinguishing mandatory duties from encouraged provisions, and Engineer A's omission constitutes a violation of both tiers simultaneously - though the violation of the mandatory duty under Section II.3.a. is the primary and sufficient basis for the ethical finding. Section II.3.a.'s requirement that engineers be objective and truthful in professional reports is a strict duty: it admits no exception based on client preference, scope limitation, or regulatory classification of the subject matter. Engineer A's omission of the threatened species finding from the written report submitted to the public authority is a direct and unambiguous violation of this mandatory standard. Section III.2.d.'s encouraged provision on sustainable development operates at a different normative level: it reflects the Code's aspirational commitment to environmental stewardship and reinforces the reporting obligation in the environmental context, but it does not independently create a mandatory reporting duty. The significance of the tiered structure is that it prevents the ethical analysis from being weakened by the argument that Section III.2.d.'s 'encouraged' language renders the sustainable development obligation merely optional. That argument would be correct as applied to Section III.2.d. in isolation, but it is irrelevant to the Section II.3.a. violation, which is mandatory and independently sufficient. Engineer A's omission is therefore simultaneously a violation of a strict duty and a failure to meet an encouraged aspiration - but the strict duty violation is what makes the conduct unethical, and the encouraged provision adds contextual reinforcement rather than independent normative weight.
Counterfactual (4)

If Engineer A had included the threatened species finding in the written report and proactively notified the developer client of its inclusion before submission, would the client have had a legitimate basis to object, and would that inclusion have altered the public authority's decision on the condominium development proposal?

AnalyticalIn response to Q401: If Engineer A had included the threatened species finding in the written report and proactively notified the developer client before submission, the developer client would have had no legitimate basis to object to the inclusion. The client's interest in a favorable regulatory outcome does not create a right to control the content of a professional report submitted to a public authority; the engineer's obligation of objective completeness under Section II.3.a. runs to the integrity of the report itself, not to the client's preferences about its contents. The client could legitimately have requested that Engineer A explain the finding, contextualize its significance, or identify potential mitigation measures - but not that the finding be omitted. As to the effect on the public authority's decision: inclusion of the finding would have placed the threatened species risk squarely before the regulatory body, which would then have been obligated to consider it under applicable federal and state environmental regulatory frameworks. The public authority might have required additional environmental review, imposed conditions on approval, required mitigation measures, or denied the proposal. Any of those outcomes would have been a legitimate exercise of the regulatory process functioning as designed - which is precisely the outcome that Engineer A's omission prevented. The counterfactual therefore illustrates that Engineer A's omission did not merely violate a professional standard in the abstract; it materially impaired the public authority's ability to exercise its regulatory function.

If the bird species at risk had been classified as an endangered species rather than merely a threatened species, would Engineer A's ethical obligation to include the finding in the written report have been stronger, and does the threatened-versus-endangered distinction carry any legitimate moral weight in determining the scope of the disclosure duty?

AnalyticalIn response to Q402: If the bird species had been classified as endangered rather than threatened, Engineer A's ethical obligation to include the finding in the written report would not have been meaningfully stronger under the NSPE Code, because the Code's completeness obligation does not scale with regulatory severity classifications. The obligation under Section II.3.a. to be objective and truthful in professional reports is binary - it either applies or it does not - and it applies whenever a material finding exists that a public authority would need to make an informed decision. A threatened species finding satisfies that materiality threshold. The endangered-versus-threatened distinction carries significant weight in the regulatory and legal context - it triggers different statutory protections and enforcement mechanisms under the Endangered Species Act and analogous state frameworks - but it does not carry legitimate moral weight in determining the scope of the engineer's disclosure duty under the NSPE Code. An engineer who would include an endangered species finding but omit a threatened species finding is applying a regulatory classification threshold as a proxy for the completeness obligation, which the Code does not authorize. The ethical obligation to report material environmental findings to public authorities is grounded in the engineer's duty of objective completeness and public welfare paramountcy, not in the regulatory severity of the finding. The threatened classification is itself a formal determination of significant risk; treating it as below the disclosure threshold would be inconsistent with both the letter and the spirit of the Code.

If the developer client had explicitly invoked confidentiality and instructed Engineer A in writing not to include the threatened species finding in the public authority report - mirroring the confidentiality instruction given in BER Case No. 97-13 - would that instruction have provided Engineer A with an ethical defense for the omission, or would the public safety and regulatory disclosure obligations have overridden client confidentiality in this environmental context?

AnalyticalIn response to Q403: If the developer client had explicitly instructed Engineer A in writing not to include the threatened species finding in the public authority report - mirroring the confidentiality instruction in BER Case No. 97-13 - that instruction would not have provided Engineer A with an ethical defense for the omission in the present environmental context, and the analysis differs from BER 97-13 in a critical respect. In BER 97-13, the confidentiality instruction was given in the context of a speculative structural observation made outside the engineer's competence, and the finding was not independently confirmed by a domain-competent specialist within the firm. In the present case, the finding is competence-confirmed by an in-house biologist, it is directly relevant to the subject matter of the engagement, and it concerns a regulated natural resource - a threatened species in adjacent protected wetlands - that is the subject of federal and state environmental regulatory frameworks. A confidentiality instruction cannot ethically authorize an engineer to submit a materially incomplete report to a public authority on a matter of direct regulatory concern. The NSPE Code's confidentiality provision under Section III.4. protects legitimate business information; it does not authorize the suppression of material environmental findings from regulatory submissions. Where the finding is both within the scope of the engagement and relevant to the protection of a regulated natural resource, the public safety and regulatory disclosure obligations override the client's confidentiality instruction. Engineer A would have been required to include the finding, withdraw from the engagement, or - at minimum - refuse to submit the incomplete report.

If Engineer A had declined the engagement entirely upon learning that the proposed development site was adjacent to protected wetlands containing a threatened species, would that refusal have better served the public interest than accepting the engagement and subsequently omitting the critical environmental finding, and does the acceptance of the engagement itself create an affirmative obligation to report all material environmental findings regardless of client preference?

AnalyticalEngineer A's acceptance of an environmental analysis engagement for a site adjacent to protected wetlands itself created an affirmative and non-waivable obligation to report all material environmental findings in the written deliverable submitted to the public authority, regardless of client preference. An environmental engineering firm principal who accepts an engagement whose explicit purpose is to inform a regulatory body's decision about a development proposal cannot subsequently treat that report as a client advocacy document from which inconvenient findings may be selectively omitted. The engagement's regulatory context - a written report submitted to a public authority considering a developer's proposal - transforms the report from a private client deliverable into a quasi-public document on which a governmental decision-maker will rely. This context activates the paramount public welfare obligation under the NSPE Code and the objective truthfulness duty under Section II.3.a. simultaneously. Engineer A's role as a faithful agent of the developer client is bounded by these obligations and does not extend to curating the evidentiary record presented to a regulatory authority. Had Engineer A been unwilling to include all material findings, the ethically consistent course would have been to decline the engagement or to withdraw upon receiving the biologist's report rather than to submit an incomplete document to the public authority.
AnalyticalIn response to Q404: Engineer A's acceptance of the engagement to prepare an environmental analysis of a site adjacent to protected wetlands did create an affirmative obligation to report all material environmental findings regardless of client preference, and declining the engagement would not have better served the public interest than accepting it and reporting completely. The engagement itself - an environmental analysis for a development proposal adjacent to protected wetlands - is precisely the kind of professional service that the public interest requires to be performed competently and completely. The public authority's ability to make an informed regulatory decision depends on engineers accepting such engagements and performing them with integrity. If Engineer A had declined the engagement, the developer might have retained a less scrupulous firm, or might have proceeded without a thorough environmental analysis at all. The public interest is better served by a competent environmental engineer accepting the engagement and reporting all material findings than by that engineer declining and leaving the field to others. However, acceptance of the engagement carries with it the full weight of the completeness obligation under Section II.3.a.: by agreeing to prepare an environmental analysis for submission to a public authority, Engineer A implicitly represented that the analysis would be objective and complete. The acceptance of the engagement therefore did not merely permit Engineer A to report the threatened species finding - it obligated Engineer A to do so. The ethical failure was not in accepting the engagement but in failing to honor the completeness obligation that acceptance entailed.
Decisions & Arguments (3)
View Extraction

Should Engineer A include the biologist's threatened species finding in the written report and advise the client before submission, omit it by citing the species' 'threatened' classification and the probabilistic framing of the finding, or omit it on scope-limitation grounds while recommending an independent assessment?

Options considered:
O1 Include the biologist's threatened species finding in the written report as a material environmental risk, advise the developer client of its inclusion before submission, and frame the finding objectively to satisfy the completeness obligation under Section II.3.a. Board's choice
O2 Omit the threatened species finding from the written report on the basis that the species is classified as 'threatened' rather than 'endangered' and the biologist's opinion is probabilistic, treating these factors as reducing the finding's materiality below the threshold requiring written inclusion.
O3 Omit the threatened species finding from the written report on scope-limitation grounds, treating it as an incidental observation outside the contracted environmental analysis, while recommending in the report that the public authority commission an independent biological assessment.
Argument structure:
Warrants

The mandatory completeness and truthfulness duty under NSPE Code Section II.3.a. requires that professional reports submitted to public authorities be objective and complete, with no carve-out for client preference or regulatory classification tier. The public welfare paramount obligation requires that the public authority, which relies on the written report as its primary evidentiary basis, receive all material environmental findings. Competing warrants include the faithful agent obligation to the developer client, the argument that the finding falls outside the contracted scope of work, and the argument that a 'threatened' (non-endangered) species classification reduces the materiality of the finding below the disclosure threshold.

Rebuttals

Uncertainty is created by: (1) whether the 'threatened' rather than 'endangered' classification legitimately reduces the materiality of the finding; (2) whether the probabilistic framing ('could threaten') renders the biologist's opinion too speculative to require written inclusion; (3) whether the finding falls outside the contracted scope of work, analogous to BER 97-13 where a scope limitation and competence gap together justified omission; and (4) whether the faithful agent obligation to the developer client permits selective omission of unfavorable findings from a report that is nominally prepared for the client.

Grounds

Engineer A, a principal in an environmental engineering firm, was retained to prepare an environmental analysis of a proposed condominium development site adjacent to protected wetlands. A biologist employed within Engineer A's own firm reported that the project could threaten a bird species classified as 'threatened' by federal and state regulators. Engineer A verbally mentioned this concern to the developer client but omitted the finding from the written report submitted to the public authority considering the development proposal. The species was not classified as 'endangered,' and the biologist's finding was framed in probabilistic terms ('could threaten').

Threatened Species Written Report Inclusion Obligation Scope Limitation Defense Rejected for Environmental Finding

Given that Engineer A's own firm employs the biologist who produced the threatened species finding within the scope of an environmental analysis engagement, should Engineer A treat the finding as a professionally grounded obligation to report rather than as an incidental observation outside the contracted scope?

Options considered:
O1 Integrate the biologist's threatened species finding into the written report as a professionally grounded environmental risk assessment, treating the in-house biologist's domain-competent judgment as within the scope of the environmental analysis engagement Board's choice
O2 Exclude the biologist's finding from the written report on the basis that the contracted scope covers physical site and infrastructure analysis rather than biological habitat assessment, and transmit the finding separately to the client as an advisory outside the formal deliverable
O3 Include a qualified reference to the biologist's finding in the written report using explicitly probabilistic language that characterizes it as a preliminary professional opinion requiring further specialist study, rather than as a confirmed finding, thereby preserving completeness while signaling epistemic uncertainty to the public authority
Argument structure:
Warrants

The Expertise Calibration principle holds that the presence of in-house specialist competence elevates a finding from a speculative observation to a reportable professional judgment, eliminating the competence-gap defense that justified omission in BER 97-13. The Scope Limitation Defense Rejected principle holds that when a finding is produced by a domain-competent specialist within the firm working within the subject matter of the engagement, scope limitation alone cannot justify omission. The Objective Completeness Obligation under Section II.3.a. applies with full force when the finding is confirmed rather than speculative. Competing against these is the BER 97-13 precedent, which could be read to establish a general norm that engineers are not obligated to include findings outside their contracted scope, and the argument that the biologist's use of probabilistic language ('could threaten') introduces sufficient epistemic qualification to treat the finding as non-reportable opinion rather than confirmed fact.

Rebuttals

Uncertainty is generated by the question of whether scope limitation alone, divorced from the competence gap that accompanied it in BER 97-13, is independently sufficient to justify omission, or whether the two factors must always appear together for the defense to succeed. Additional uncertainty arises from the biologist's probabilistic framing: if 'could threaten' is treated as insufficient certainty to trigger a mandatory reporting obligation, the finding might be characterized as a speculative professional opinion rather than a confirmed technical fact, potentially bringing it closer to the BER 97-13 structural observation. A further rebuttal condition exists if the engagement contract is construed narrowly as covering only physical site characteristics rather than biological habitat assessment, such that the biologist's work is treated as outside the contracted deliverable regardless of the firm's in-house capability.

Grounds

Engineer A is a principal in an environmental engineering firm engaged to prepare an environmental analysis of a proposed condominium development site adjacent to protected wetlands. A biologist employed within Engineer A's own firm, acting within the subject matter of the engagement, identified that the project could threaten a federally and state-classified 'threatened' bird species. The biologist's finding is a professional judgment grounded in direct field observation and domain expertise, not a speculative lay observation. No confidentiality instruction was given by the developer client. In BER Case No. 97-13, a comparable engineer was permitted to omit a structural wall observation from a report because the observation was speculative, outside the engineer's competence, and a confidentiality instruction had been explicitly issued.

Environmental Stewardship Wetlands Adjacent Development Assessment Obligation / Scope Limitation Defense Rejected for Environmental Finding / Expertise Calibration Applied to Present Case vs BER 97-13 Scope-of-Work Limitation as Incomplete Ethical Defense / BER 97-13 Confidentiality Instruction Suppressing Structural Observation

Should Engineer A notify the developer client and include the threatened species finding in the written report, give the client time to voluntarily disclose it first, or omit the finding to defer to the client's commercial interests?

Options considered:
O1 Notify the developer client in advance that the threatened species finding will be included in the written report, then include it in the submission to the public authority. Offer to assist the client in framing the finding constructively, but do not condition inclusion on the client's approval. Board's choice
O2 Treat the developer client as the primary principal whose commercial interests govern the report's scope, and omit the threatened species finding on the ground that the faithful agent obligation authorizes deference to the client's preference for a favorable regulatory outcome.
O3 Advise the developer client of the finding and give the client a defined period to voluntarily supplement the submission to the public authority with the threatened species information before Engineer A acts unilaterally, applying the BER 04-8 client-first confrontation norm.
Argument structure:
Warrants

The Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship requires Engineer A to serve the developer's interests, but only within the bounds of the engineer's overriding ethical duties. The Public Welfare Paramount obligation (NSPE Code Section I) and the mandatory completeness duty (Section II.3.a.) together establish that a written report submitted to a public authority is a quasi-public document, not a client advocacy instrument, and that acceptance of the engagement created an affirmative, non-waivable obligation to report all material environmental findings. The Client-First Confrontation Before External Reporting Obligation (BER 04-8) supports advising the client before submission, but does not give the client veto power over the report's content. The Faithful Agent Boundary Constraint confirms that client loyalty cannot be exercised at the expense of the integrity of a public regulatory process.

Rebuttals

Uncertainty arises from the BER 04-8 precedent establishing a client-first confrontation norm before external escalation, which could be read to require Engineer A to give the client an opportunity to include the finding voluntarily before Engineer A acts unilaterally, potentially shifting responsibility to the client if the client then suppresses it. The faithful agent obligation's internal limit ('within ethical limits') makes the conflict somewhat circular: the rebuttal condition that would defeat faithful agency is itself defined by the ethical limits whose content is in dispute. Additionally, if Engineer A had declined the engagement upon learning of the wetlands adjacency, the public interest might have been served differently, raising the question of whether acceptance itself was the ethically determinative act.

Grounds

Engineer A accepted an engagement to prepare an environmental analysis of a site adjacent to protected wetlands for a developer client, with the analysis to be submitted to a public authority reviewing the developer's condominium proposal. An in-house biologist identified a threatened species risk. Engineer A verbally disclosed the concern to the client but omitted it from the written report. The client gave no explicit instruction to omit the finding and invoked no confidentiality protection. The report was submitted to the public authority, which relied on it as the primary evidentiary basis for its regulatory decision.

Engineer A Environmental Principal Sustainable Development Code Calibration Current Case Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship
Event Timeline (9)
9 sequenced 4 actions 5 events
Case timeline
The NSPE Board of Ethical Review contextualizes Engineer A's conduct against the January 2006 addition (and July 2007 modification) of Section III.2.d to the NSPE Code of Ethics, which addresses sustainable development obligations. This code evolution establishes the formal professional standard against which Engineer A's omission is evaluated.
Engineer A, as principal of an environmental engineering firm, accepted a client request to prepare an analysis of property adjacent to a wetlands area for potential residential condominium development. This decision initiated Engineer A's professional obligations to both the developer client and the broader public interest.
Fulfills (2)
  • Provision of professional engineering services within area of competence (environmental engineering)
  • Responsiveness to client needs
A biologist on Engineer A's team identifies a potential threat to a 'threatened' bird species in the adjacent protected wetlands during the property analysis. This discovery transforms a routine development analysis into an environmentally sensitive situation with regulatory and ethical implications.
Upon receiving the biologist's report that the condominium project could threaten a 'threatened' bird species inhabiting the adjacent protected wetlands, Engineer A incorporated this finding into the firm's ongoing analysis rather than dismissing or disregarding it. This decision to treat the biologist's report as a material finding set the stage for subsequent disclosure decisions.
Fulfills (3)
  • Obligation to oversee and integrate work of subordinate team members
  • Obligation to consider all relevant and pertinent environmental information in the course of professional analysis
  • NSPE Code Section II.3.a., objectivity and truthfulness in professional reports
In subsequent discussions with the developer client, Engineer A chose to verbally mention the biologist's concern about the threatened bird species rather than formally documenting it or escalating it to a written recommendation. This oral disclosure was Engineer A's primary, and ultimately insufficient, mechanism for communicating a material environmental finding to the client.
At stake (4)
  • NSPE Code Section II.3.a., obligation to be objective and truthful in professional reports and to include all relevant and pertinent information
  • NSPE Code Section III.2.d., encouragement to adhere to sustainable development principles protecting the environment for future generations
  • Obligation to hold paramount public health, safety, and environmental welfare over client interests
  • Obligation to provide complete and accurate information to the public authority reviewing the development proposal
Fulfills (2)
  • Partial fulfillment of duty to inform client of material findings affecting the project
  • Faithful communication with client as agent/trustee
Engineer A made the deliberate decision not to include the biologist's threatened species concern in the written report submitted to the public authority considering the developer's proposal. This omission constituted the central ethical violation identified by the NSPE Board of Ethical Review, as it deprived the public authority of material environmental information relevant to its regulatory decision.
Fulfills (1)
  • Protection of developer client's immediate commercial interests (though not a recognized ethical justification under the circumstances)
Violates (5)
  • NSPE Code Section II.3.a.: obligation to be objective and truthful in professional reports, statements, or testimony and to include all relevant and pertinent information
  • NSPE Code Section III.2.d., obligation (or strong encouragement) to adhere to sustainable development principles to protect the environment for future generations
  • Fundamental obligation to hold paramount the safety, health, and welfare of the public
  • Obligation to provide complete and accurate information to a public authority conducting regulatory review
  • Obligation not to suppress material findings generated by qualified team members
Engineer A's written report on the property analysis is formally submitted to the public authority reviewing the development proposal, without inclusion of the threatened species finding. This submission constitutes an official record that the public authority will rely upon in its regulatory decision-making.
The public authority begins its formal review of the development proposal based on the submitted materials, including Engineer A's incomplete written report. The regulatory process is now underway on a materially deficient information base.
The NSPE Board of Ethical Review concludes, after analyzing the facts against the Code of Ethics and prior BER cases, that Engineer A was obligated to include the environmental threat information in the written report submitted to the public authority. This conclusion constitutes an authoritative professional ethics judgment.
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 at an environmental engineering firm retained by a developer client to prepare a site analysis for a proposed residential condominium project on a parcel adjacent to a protected wetlands area. During the analysis, one of your firm's biologists reports that in his opinion the condominium project could threaten a bird species inhabiting the adjacent wetlands. The species is not classified as endangered, but federal and state environmental regulators recognize it as a threatened species. You have verbally mentioned the biologist's concern to the developer client, and a written report is being prepared for submission to a public authority that is evaluating the developer's proposal. The decisions you make about what the written report contains, and what obligations you owe to the public authority versus the developer client, will define how you proceed.

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 Firm PrincipalBridge Sub-ConsultantEnvironmental Threat Reporting EngineerWetland Delineation Engineer BER 04-8

Guided by: Honesty in Professional Representations Violated by Written Report Omission, Intern Epistemic Humility and Materiality Deference Applied to Biologist Reporting, Sustainable Development Obligation Applied to Threatened Species Finding

Tension between Client Verbal Mention Non-Substitution for Public Authority Written Disclosure Obligation / Confidentiality Non-Invocation by Client Removes Confidentiality Defense and Confidential Client Information Constraint — Engineer A Developer Environmental Analysis / Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Attaches to role: Environmental Firm Principal

Tension between Client Confidentiality Non-Invocation Disclosure Facilitation Obligation and Confidential Client Information Constraint — Engineer A Developer Environmental Analysis

Attaches to role: Environmental Firm Principal

Tension between Engineer A Environmental Principal Objective Completeness Written Report Current Case and Confidential Client Information Constraint — Engineer A Developer Environmental Analysis

Attaches to role: Environmental Firm Principal

Engineer A is obligated to include findings about threatened species in the written report submitted to the public authority, yet the developer client's interest in confidentiality over sensitive environmental findings creates pressure to suppress or omit that information. Fulfilling the written-report inclusion obligation risks breaching the client relationship and potentially exposing commercially sensitive development plans, while honoring confidentiality expectations risks producing an incomplete, misleading report to a regulatory body. The tension is genuine because both duties have legitimate grounding — professional loyalty to the client and professional integrity toward the public authority — but they point in opposite directions regarding the same piece of information.

Attaches to role: Environmental Firm Principal

Engineer A's obligation holds that verbal mention to the client cannot substitute for written disclosure to the public authority — the engineer must produce a complete written record regardless of what was said informally. However, the faithful-agent constraint pulls Engineer A toward deference to the client's direction and interests, especially after the biologist's finding was communicated verbally and the client may have indicated a preference not to escalate it in writing. Acting as a faithful agent post-confirmation of the environmental finding means the engineer faces pressure to treat the verbal exchange as sufficient, directly conflicting with the insufficiency-of-verbal-disclosure obligation. The dilemma is acute because the engineer cannot simultaneously treat verbal disclosure as adequate (faithful-agent deference) and treat it as inadequate (written-report obligation).

Attaches to role: Environmental Firm Principal

Tension between Engineer A Environmental Principal Faithful Agent Bounded by Public Welfare Current Case and Confidentiality Non-Invocation by Client Removes Confidentiality Defense

Attaches to role: Environmental Firm Principal

Tension between Engineer A Public Welfare Paramount Threatened Species Omission Obligation Instance and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Attaches to role: Environmental Firm Principal

The public-welfare-paramount obligation requires Engineer A to prioritize the broader public interest — including ecological and community welfare associated with threatened species habitat — over client preferences when the two conflict. The client-instruction omission prohibition reinforces this by barring the engineer from following client directives to exclude confirmed environmental findings. Yet the developer client's commercial interest in proceeding with the condominium project creates real-world pressure on Engineer A to comply with omission instructions. The tension is that acting on client instructions (a normal professional expectation) is precisely what the constraint prohibits once a competence-confirmed finding exists, forcing Engineer A to choose between contractual loyalty and paramount public-welfare duties.

Attaches to role: Environmental Firm Principal

Tension between Engineer A Environmental Principal Sustainable Development Code Calibration Current Case and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Attaches to role: Environmental Firm Principal

Tension between Engineer A Environmental Principal Client Confidentiality Non-Invocation Disclosure Facilitation Current Case and Engineer A Bridge Sub-Consultant Field Notes Preservation Non-Alteration BER 97-13

Attaches to role: Environmental Firm Principal

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

Tension between Client Verbal Mention Non-Substitution for Public Authority Written Disclosure Obligation / Confidentiality Non-Invocation by Client Removes Confidentiality Defense and Confidential Client Information Constraint — Engineer A Developer Environmental Analysis / Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Engineer A is obligated to include findings about threatened species in the written report submitted to the public authority, yet the developer client's interest in confidentiality over sensitive environmental findings creates pressure to suppress or omit that information. Fulfilling the written-report inclusion obligation risks breaching the client relationship and potentially exposing commercially sensitive development plans, while honoring confidentiality expectations risks producing an incomplete, misleading report to a regulatory body. The tension is genuine because both duties have legitimate grounding — professional loyalty to the client and professional integrity toward the public authority — but they point in opposite directions regarding the same piece of information.

Engineer A's obligation holds that verbal mention to the client cannot substitute for written disclosure to the public authority — the engineer must produce a complete written record regardless of what was said informally. However, the faithful-agent constraint pulls Engineer A toward deference to the client's direction and interests, especially after the biologist's finding was communicated verbally and the client may have indicated a preference not to escalate it in writing. Acting as a faithful agent post-confirmation of the environmental finding means the engineer faces pressure to treat the verbal exchange as sufficient, directly conflicting with the insufficiency-of-verbal-disclosure obligation. The dilemma is acute because the engineer cannot simultaneously treat verbal disclosure as adequate (faithful-agent deference) and treat it as inadequate (written-report obligation).

Tension between Objective Complete Reporting Public Authority Obligation / Verbal-Only Disclosure Insufficiency Obligation / Client Verbal Mention Non-Substitution for Public Authority Written Disclosure Obligation and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Tension between Engineer A Public Welfare Paramount Threatened Species Omission Obligation Instance and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

The public-welfare-paramount obligation requires Engineer A to prioritize the broader public interest — including ecological and community welfare associated with threatened species habitat — over client preferences when the two conflict. The client-instruction omission prohibition reinforces this by barring the engineer from following client directives to exclude confirmed environmental findings. Yet the developer client's commercial interest in proceeding with the condominium project creates real-world pressure on Engineer A to comply with omission instructions. The tension is that acting on client instructions (a normal professional expectation) is precisely what the constraint prohibits once a competence-confirmed finding exists, forcing Engineer A to choose between contractual loyalty and paramount public-welfare duties.

Tension between Engineer A Environmental Principal Sustainable Development Code Calibration Current Case and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Engineer A's obligation holds that verbal mention to the client cannot substitute for written disclosure to the public authority — the engineer must produce a complete written record regardless of what was said informally. However, the faithful-agent constraint pulls Engineer A toward deference to the client's direction and interests, especially after the biologist's finding was communicated verbally and the client may have indicated a preference not to escalate it in writing. Acting as a faithful agent post-confirmation of the environmental finding means the engineer faces pressure to treat the verbal exchange as sufficient, directly conflicting with the insufficiency-of-verbal-disclosure obligation. The dilemma is acute because the engineer cannot simultaneously treat verbal disclosure as adequate (faithful-agent deference) and treat it as inadequate (written-report obligation).

Tension between Client Verbal Mention Non-Substitution for Public Authority Written Disclosure Obligation / Confidentiality Non-Invocation by Client Removes Confidentiality Defense and Confidential Client Information Constraint — Engineer A Developer Environmental Analysis / Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

Engineer A is obligated to include findings about threatened species in the written report submitted to the public authority, yet the developer client's interest in confidentiality over sensitive environmental findings creates pressure to suppress or omit that information. Fulfilling the written-report inclusion obligation risks breaching the client relationship and potentially exposing commercially sensitive development plans, while honoring confidentiality expectations risks producing an incomplete, misleading report to a regulatory body. The tension is genuine because both duties have legitimate grounding — professional loyalty to the client and professional integrity toward the public authority — but they point in opposite directions regarding the same piece of information.

Engineer A's obligation holds that verbal mention to the client cannot substitute for written disclosure to the public authority — the engineer must produce a complete written record regardless of what was said informally. However, the faithful-agent constraint pulls Engineer A toward deference to the client's direction and interests, especially after the biologist's finding was communicated verbally and the client may have indicated a preference not to escalate it in writing. Acting as a faithful agent post-confirmation of the environmental finding means the engineer faces pressure to treat the verbal exchange as sufficient, directly conflicting with the insufficiency-of-verbal-disclosure obligation. The dilemma is acute because the engineer cannot simultaneously treat verbal disclosure as adequate (faithful-agent deference) and treat it as inadequate (written-report obligation).

Tension between Objective Complete Reporting Public Authority Obligation / Verbal-Only Disclosure Insufficiency Obligation / Client Verbal Mention Non-Substitution for Public Authority Written Disclosure Obligation and Faithful Agent Obligation Within Ethical Limits Applied to Developer Client Relationship

The public-welfare-paramount obligation requires Engineer A to prioritize the broader public interest — including ecological and community welfare associated with threatened species habitat — over client preferences when the two conflict. The client-instruction omission prohibition reinforces this by barring the engineer from following client directives to exclude confirmed environmental findings. Yet the developer client's commercial interest in proceeding with the condominium project creates real-world pressure on Engineer A to comply with omission instructions. The tension is that acting on client instructions (a normal professional expectation) is precisely what the constraint prohibits once a competence-confirmed finding exists, forcing Engineer A to choose between contractual loyalty and paramount public-welfare duties.

These tensions did not map cleanly to a single character.

Tension between Threatened Species Written Report Inclusion Obligation and Scope Limitation Defense Rejected for Environmental Finding

Tension between Environmental Stewardship Wetlands Adjacent Development Assessment Obligation / Scope Limitation Defense Rejected for Environmental Finding / Expertise Calibration Applied to Present Case vs BER 97-13 and Scope-of-Work Limitation as Incomplete Ethical Defense / BER 97-13 Confidentiality Instruction Suppressing Structural Observation

Tension between Expertise-Calibrated Disclosure Threshold Obligation and Scope Limitation Defense Rejected for Environmental Finding

Opening States (10)
NSPE Code Section III.2.d. Encouraged Language Ambiguity Client-Interest vs. Public-Interest Conflict - Environmental Finding Omission BER 97-13 Engineer A - Speculation-Based Structural Observation Outside Competence Threatened Species Habitat Proximity Development State Engineer A Technically Confirmed Environmental Finding - Omission Instruction BER 04-8 Post-Service Environmental Violation Discovery Threatened Species Habitat Risk from Condominium Development Verbal-Only Threatened Species Advisory Without Written Record Undisclosed Threatened Species Risk in Public Authority Report Client Interest vs. Public Interest Conflict Over Environmental Disclosure
Summary
  • An engineer's duty to report environmentally significant findings in writing to public authorities is mandatory and cannot be discharged by informal verbal disclosure to a client alone.
  • The absence of a client confidentiality invocation eliminates one potential defense, leaving the engineer fully exposed to the obligation of complete and truthful reporting under NSPE Code Section II.3.a.
  • Scope-of-work limitations defined by contract do not override an engineer's affirmative public welfare obligations when material environmental findings—such as threatened species presence—are discovered incidentally during a project.

© Licensed under the GNU GPL v3 | Report Issue