Step 4: Review

Issue public statements only in an objective and truthful manner.

Avoid deceptive acts.

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.

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.

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.

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

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

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

It was unethical for Engineer A to not include the information about the threat to the bird species in a written report that will be submitted to a public authority that is considering the developer’s proposal. Engineer A should have included it in the written report and advised the client of its inclusion.

The Board's conclusion implies that verbal disclosure to the developer client, while satisfying an internal advisement duty, does not discharge Engineer A's separate and independent obligation to the public authority under Section II.3.a. The two disclosure duties are not interchangeable: informing the client privately manages the client relationship, but only inclusion in the written report ensures the regulatory body reviewing the proposal has the information needed to make an informed public-interest decision. Treating verbal disclosure as sufficient risks conflating client management with public accountability.

The Board's reasoning does not hinge on the bird species being classified as 'threatened' rather than 'endangered,' and this suggests the regulatory label itself is not the ethical trigger. What matters is that a qualified professional within the firm (the biologist) reached an unambiguous risk conclusion relevant to the project's impact on a protected habitat. Had the Board made disclosure duties turn on the severity of the regulatory classification, it would create a troubling sliding scale of honesty in reporting, where lesser-protected species risks could be selectively omitted. The Board's implicit position is that the duty of objective and complete reporting applies regardless of where a species falls on the regulatory spectrum, so long as the risk is scientifically identified and material to the authority's decision.

The case reveals an unresolved tension the Board's conclusion only implicitly settles: when a client's commercial interest in project approval conflicts with an engineer's duty of complete and objective reporting to a public authority, the latter must prevail. Even if the developer client had explicitly instructed Engineer A to omit the biologist's finding, this would not create a valid ethical exception, because Section II.3.a's objectivity requirement in professional reports submitted to public bodies functions as a non-waivable public-protection duty, not a negotiable term of the client engagement that can be modified by client consent or preference.

Verbal disclosure to the developer client (Q101) does not discharge Engineer A's ethical obligation because the public authority, not the client, is the ultimate decision-maker relying on the written report. Informing the client privately may satisfy an internal duty of transparency but does not ensure the regulator has the information needed for an objective review, effectively shifting risk-bearing responsibility onto the public without their knowledge.

The classification of the species as 'threatened' rather than 'endangered' (Q103) does not lower Engineer A's disclosure obligation. The Board's reasoning rests on the objectivity and completeness required of professional reports under Section II.3.a, not on the severity tier of regulatory classification. Because the biologist's finding created a genuine, identifiable risk to protected habitat, the ethical duty to disclose attaches regardless of whether the species is legally 'threatened' or 'endangered.'

If the developer client had instructed Engineer A to omit the species risk after verbal disclosure (Q104), compliance would cross an ethical boundary irrespective of client consent, because Section II.3.a's duty of objectivity and truthfulness in reports submitted to a public authority is a professional obligation owed to the public, not one that can be waived by private client instruction. Client consent cannot cure a violation of a duty owed to third parties relying on the report's completeness.

From a deontological standpoint (Q301), Engineer A failed to fulfill the duty of objective and truthful reporting under Section II.3.a. The duty is not conditional on client preference or commercial consequence; it is a categorical obligation attaching to any report submitted for public reliance. Omission of a known, professionally identified risk constitutes a failure of this duty regardless of Engineer A's intent to be forthright with the client.

A consequentialist analysis (Q302) supports the Board's conclusion: the localized commercial benefit to the developer from omitting the finding is outweighed by the diffuse but significant harm of impaired regulatory decision-making, potential habitat degradation, and erosion of public trust in engineering reports submitted for approval processes. The asymmetry between concentrated private gain and dispersed public harm favors disclosure as the ethically superior outcome.

Under a virtue-ethics lens (Q303), Engineer A's conduct reflects a divided professional character: candor toward the client but concealment toward the public authority. True professional integrity requires consistency of disclosure across all parties relying on the engineer's expertise; selectively sharing material findings undermines the virtue of honesty that the profession's Code is meant to embody.

Had the species been federally 'endangered' rather than 'threatened' (Q401), the Board's conclusion would likely have been even more unambiguous, as endangered species protections typically trigger stricter statutory disclosure and mitigation requirements. The ethical duty to disclose, already grounded in professional objectivity, would be reinforced by a stronger overlapping legal mandate, leaving even less room for professional discretion in omission.

If Engineer A had failed to disclose the concern even verbally to the developer client (Q402), the ethics violation would extend beyond the reporting omission to a breach of the client advisement duty itself, compounding the violation. The Board's actual finding treats the written report omission as the core violation; without any client disclosure at all, Engineer A would additionally fail the professional duty to keep the client informed of material findings affecting the project's risk profile.

If the written report had been intended solely for the developer's internal use rather than submission to a public authority (Q404), the ethical calculus would shift substantially. The Board's conclusion is expressly tied to the report's function as a document relied upon by a public authority in a regulatory proceeding; absent that public reliance, the omission might fall instead under confidentiality and client-disclosure considerations rather than the duty of objective public reporting under Section II.3.a.

The case resolves the apparent tension between Confidentiality of Client Information and Objectivity in Written Report by treating them as operating on different planes rather than as truly competing obligations: confidentiality protects a client's proprietary business information, but it cannot be invoked to justify omitting a material technical finding from a report submitted to a public authority for regulatory decision-making. Once Engineer A's written report entered the public regulatory process, the duty of objectivity and truthfulness under Section II.3.a effectively superseded any claim that the species-threat information was protected client information, since the finding concerned public environmental welfare rather than the developer's private business affairs.

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

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

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?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Because Engineer A undertook the environmental analysis out of faithfulness to the client, this action set in motion the causal chain that surfaced the species threat, meaning the client-serving intent of A1 is what ultimately generated the environmental information that later obligations required to be disclosed.

The verbal disclosure, guided jointly by faithfulness to client and sustainable development, partially discharged Engineer A's duty to communicate the species threat but did not itself complete the causal path to a proper record, leaving the more consequential written omission to follow and eventually trigger board review.

The written report omission violates the duty to include all pertinent information and to protect the environment precisely because it suppressed the species threat that had already been identified and verbally acknowledged, and this suppression directly caused the NSPE Board of Ethical Review to evaluate Engineer A's conduct as a breach of public and environmental responsibility despite being guided by loyalty to the client.

Adding a new code section in the name of sustainable development created the normative material that would later be modified and applied, showing that the profession's institutional response to environmental harm was itself causally necessary for the subsequent evaluative framework used in the ethical determination.

Modifying the code language, still guided by sustainable development, refined the environmental obligations that the Board of Ethical Review ultimately relied upon, so this action's normative significance lies in supplying the very standard against which Engineer A's earlier written omission was judged.

A1, the Board's determination on Engineer A's written report omission, is guided by Sustainable Development, Objectivity and Truthfulness in Reports, and Public Health and Safety Paramountcy because it retrospectively judges whether omitting the species threat from the formal record undermined the accuracy and completeness owed to the public and environment, and this determination only arises because the earlier omission (via Written Report Omission and Code Language Modification) created the ethical question the Board had to resolve.

A2, the Species Threat Reporting, is guided by Sustainable Development since it represents the point at which the firm's biologist translated the identified ecological threat into a formal communication, setting in motion both the verbal disclosure and the later written omission that ultimately became the subject of the Board's ethical scrutiny.

The question arises because Engineer A's technical competence allowed identification of a threatened species risk that is directly relevant to a public authority's decision, yet the engineer chose selective disclosure, exposing an unresolved conflict between transparency obligations to the public and loyalty obligations to the client under NSPE Code Section III.2.d.

The question arises because Engineer A's action split the disclosure between an informal verbal channel to the client and a formal written channel to the authority, creating ambiguity about which channel actually fulfills the engineer's professional duty of complete and truthful reporting.

The question emerges because the biologist's assessment of threatened species risk was never elevated beyond an internal, informal exchange despite its regulatory significance, exposing a gap in the case entities between technical competence and independent verification obligations.

The question arises because the case data conflates a legal classification distinction with an ethical obligation question, exposing uncertainty about whether professional disclosure duties should track regulatory labels or substantive risk.

The question arises because verbal disclosure to the client does not resolve whether the engineer's written report, submitted to a public authority, can legally and ethically exclude material risk information simply because the client consents to or demands the omission.

The question arises because Engineer A's report was submitted for use in a public regulatory proceeding while containing information the client would prefer kept confidential, forcing a direct clash between the duty of client confidentiality and the duty of objective, complete reporting to a relying public authority.

The question arises because Engineer A's written report omitted the biologist's species concern while mentioning it only verbally to the client, creating an unresolved conflict between fidelity to the client who commissioned the report and the professional obligation to protect public and environmental interests through complete and truthful reporting.

The question emerges because Engineer A's choice to split disclosure across two channels, verbal to the client and silent in the report, exposes a gap between what satisfies transparency toward the client and what satisfies completeness toward all readers of the written record, including the public authority reviewing the proposal.

The question arose because Engineer A's written report omitted the biologist's species concern while only verbally raising it with the client, creating a visible gap between the engineer's environmental stewardship obligation and loyalty to the client that the Board must resolve using an untested Code provision.

The question arises because Engineer A's written report omitted information that a strict reading of Section II.3.a treats as pertinent, while the engineer's verbal disclosure to the client suggests an alternative, less formal fulfillment of duty, creating ambiguity about whether written completeness or client-directed disclosure satisfies the deontological standard.

The question arises because Engineer A's written omission of a known species risk, despite verbally mentioning it to the client, creates an unresolved gap between measurable client benefit and speculative but potentially serious public and environmental harm, forcing an outcome-based weighing that the facts do not clearly settle.

The question arises because Engineer A's split disclosure, verbal to the client but absent from the formal report, exposes an unresolved conflict between virtue-based professional integrity and duties of client confidentiality versus public transparency, making it unclear which warrant should govern the ethical evaluation.

This question emerged because the Board's decision rested on a specific regulatory status (threatened) that sits on a spectrum of protection levels, prompting speculation about whether the ethical obligation is categorical or proportional to legal severity.

The question emerges because removing the verbal disclosure act would test whether the written omission was judged in isolation or was implicitly considered less severe due to the informal communication, revealing an unresolved layering of obligations in the Board's reasoning.

This question arises because the case facts intertwine the duty to report with the fact of actual risk discovery, and removing that fact forces clarification of whether the obligation is fact-dependent or a standing professional duty independent of specific findings.

The question arises because the Board's original conclusion relied on the report's function as an input to a public regulatory decision, so changing the intended audience alters which warrant, public protection or client confidentiality, governs the ethical evaluation of the same omission.

Given that the biologist had reached a clear conclusion about threat to the species and the report was headed to a public authority deciding on the proposal, the board concluded that omitting this material information breached the duty of objective and complete reporting.

Because the developer client and the public authority occupy distinct roles with distinct information needs, the board reasoned that Engineer A's private verbal disclosure to the client, however well intentioned, left the regulatory decision maker uninformed and therefore did not satisfy the separate duty owed to the public authority.

Since the board did not premise its determination on the species being endangered rather than threatened, it treated the biologist's unambiguous, material risk finding, not the regulatory label, as the true trigger for the reporting obligation.

Even if the developer client had directly instructed omission, the board's reasoning treats the objectivity requirement as a public-protection duty that client consent cannot waive, so compliance with such an instruction would still cross an ethical boundary.

Because the public authority makes its regulatory decision based on the written report alone, the board concluded that verbal disclosure to the client, while meeting an internal transparency duty, effectively shifts risk onto the public without their knowledge and does not satisfy Engineer A's obligation to the reviewing authority.

Given that the biologist's finding constituted a real risk to protected habitat, the Board concluded that the 'threatened' versus 'endangered' distinction was legally and ethically irrelevant to the disclosure duty, since the duty derives from professional objectivity standards rather than regulatory classification tiers.

Because the written report was destined for a public authority's regulatory reliance, the Board reasoned that even an explicit client instruction to omit the disclosed risk could not excuse Engineer A from the objectivity duty, since that duty exists for the benefit of the public rather than the client.

Since Engineer A knowingly omitted the biologist's finding from a report meant for public authority review, the Board concluded under a deontological framework that the categorical duty of truthful reporting was violated irrespective of the engineer's good intentions toward the client.

Weighing the asymmetry between the developer's narrow commercial gain and the broader, dispersed harms to habitat and public decisionmaking, the Board concluded that disclosure produced the ethically superior outcome under consequentialist reasoning.

Because Engineer A was forthright with the client yet silent toward the public authority on the same material finding, the Board concluded that this divided conduct reflected a lack of consistent professional integrity as required by a virtue-ethics reading of the Code.

Given that the actual case involved a 'threatened' species and the board still found nondisclosure unethical, the board reasons that had the species been 'endangered' the same professional objectivity duty would be reinforced by stricter legal disclosure requirements, making the violation even less debatable.

Because Engineer A did verbally inform the developer client in the actual case, the board's finding centers only on the written report omission, but had that verbal disclosure never happened, the board indicates the violation would extend to a breach of the duty to keep the client informed, compounding the ethical failure.

Since in the actual case the report was submitted to a public authority making a regulatory decision, the board grounds its unethical-omission finding in that public reliance, and reasons that absent such public submission, the omission would raise different (weaker) ethical stakes tied to confidentiality rather than public truthfulness.

Because the species-threat finding concerned environmental welfare rather than the developer's private business affairs, and because the report was destined for public regulatory reliance, the board concludes confidentiality cannot be invoked to justify the omission, so the objectivity and truthfulness duty under II.3.a controls.

Given that Engineer A verbally informed the client but omitted the same information from the report submitted to the public authority, the board concludes that private advisement and public disclosure serve different functions, so verbal transparency to the client cannot substitute for complete written disclosure to the body actually making the regulatory decision.

Given that the firm's own biologist produced an unambiguous finding of threat to the species and the written report was destined for a public authority's regulatory decision, the Board concluded that the mandatory objectivity and truthfulness duty of II.3.a, not the aspirational stewardship language of III.2.d, was the operative basis for finding a violation, with the stewardship provision simply reinforcing that outcome and client loyalty yielding because it could not override the public authority's need for complete information.

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

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

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

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

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