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.

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.

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.

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.

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.

Beyond 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.

The 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.

The 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.

The 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.

Engineer 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

In 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.

The 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.

The 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.

The 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.

The 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.

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 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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

Accepting the engagement initiates the client relationship and triggers all downstream professional obligations, including faithful agency bounded by public welfare, environmental stewardship, and regulatory compliance, but does not itself violate any obligation as long as Engineer A intends to perform the work ethically.

Integrating the biologist's confirmed threatened species finding into the written report fulfills the core cluster of completeness, public welfare, and environmental stewardship obligations, and is mandated by the domain-competence-confirmed-finding constraint that distinguishes this case from the speculative BER 97-13 structural observation.

Verbal disclosure to the client is a necessary but wholly insufficient step - it satisfies the client-first confrontation principle and faithful agency courtesy but violates the cluster of obligations requiring written inclusion in the public authority report, because verbal mention to the client cannot substitute for the written regulatory disclosure obligation.

Omitting the confirmed threatened species finding from the written report is the central ethical violation in this case - it fulfills no legitimate obligation, violates the entire cluster of public welfare, completeness, environmental stewardship, and regulatory disclosure obligations, and is prohibited by every relevant constraint including the client-instruction-omission prohibition and the domain-competence-confirmed-finding mandate.

This question emerged because Engineer A's omission of the biologist's finding from the written public authority report created a direct collision between the faithful agent obligation to the developer client and the paramount public welfare and report completeness obligations under the NSPE Code. The act of submitting an incomplete report to a regulatory body - rather than merely declining to volunteer information - forced the question of whether omission in a formal public submission constitutes an affirmative ethical violation.

This question arose because Engineer A performed two distinct communicative acts - verbal disclosure to the client and written omission in the public report - which operate in different ethical registers. The question isolates whether the verbal act provides any ethical credit, or whether the written report's incompleteness constitutes a freestanding violation irrespective of what was communicated privately, forcing analysis of whether the public authority report obligation is independently grounded.

This question emerged because the BER 97-13 precedent established that speculative observations outside an engineer's competence need not appear in formal reports, creating an argument by analogy that Engineer A might apply a similar exclusion to the biologist's finding. The question forces resolution of whether the biologist's domain competence and the nature of a threatened species identification elevate the finding to confirmed-fact status, thereby collapsing the speculation-based exclusion defense.

This question arose because the ethical framework contains both a client-loyalty norm - requiring engineers to work through client relationships before escalating externally - and a public welfare paramount norm that overrides client instructions when public safety or regulatory integrity is at stake. The question isolates the procedural sequence: whether advance client notification is itself an ethical obligation, and what the required response is if the client then directs omission, forcing analysis of the boundary between faithful agency and ethical non-compliance.

This question emerged because the regulatory distinction between 'threatened' and 'endangered' species carries legal significance under federal and state frameworks, creating an argument that Engineer A's ethical obligations might track that legal gradient. The question forces resolution of whether the NSPE Code's completeness and public welfare obligations are independent of regulatory classification severity, or whether the 'threatened' designation - combined with the encouraged rather than mandatory language of Section III.2.d. - creates a reduced or discretionary disclosure standard that Engineer A could invoke to justify omission.

This question emerged because Engineer A's action of omitting a biologist-confirmed finding from a regulatory report, while verbally informing only the client, sits exactly at the boundary where client-service obligations and public-protection obligations diverge. The question forces articulation of the precise crossing-point at which faithful agency ends and public-welfare violation begins, a line the data make contestable but do not resolve.

This question arose because the factual record contains a silence - no confidentiality instruction was given - and two competing warrant structures assign opposite legal and ethical significance to that silence. The question is necessary to determine whether Engineer A can invoke confidentiality as a defense for omission or whether the absence of invocation itself forecloses that defense.

This question emerged because BER 97-13 established a two-condition precedent for permissible omission, and the present case satisfies only one of those conditions, forcing analysis of whether the precedent's logic is divisible or whether the presence of in-house expertise fundamentally changes the ethical calculus and renders the scope-limitation defense unavailable.

This question emerged because the NSPE Code contains two provisions of different normative weight that both bear on the omission, and selecting the weaker aspirational provision as the primary basis for an ethical violation conclusion creates a structural vulnerability in the argument that the stronger mandatory provision would eliminate - the question forces the Board to anchor its reasoning in the correct normative tier.

This question emerged because Engineer A performed a disclosure act (verbal client notification) that satisfies one conception of the truthfulness duty while simultaneously failing to perform the disclosure act (written report inclusion) that satisfies a broader deontological conception, and the gap between these two conceptions is precisely what the question asks the deontological framework to resolve.

This question emerged because the omission of a confirmed environmental finding from a regulatory submission created a three-way harm structure - to a species, an ecosystem, and a public institution - that cannot be resolved by any single consequentialist metric, requiring explicit weighting across incommensurable harm categories. The data of a technically confirmed finding being withheld from the very authority empowered to act on it forces the question of whether the client benefit of avoiding regulatory scrutiny could ever outweigh harms distributed across ecological and institutional domains simultaneously.

This question emerged because the virtue ethics framework demands an assessment of character rather than merely conduct, and Engineer A's partial disclosure - verbal to client, silent in the written report - creates an ambiguous character signal that neither clearly demonstrates integrity nor clearly demonstrates its absence. The role of environmental firm principal carries heightened stewardship expectations that make the gap between what was disclosed verbally and what was omitted in writing a direct test of whether Engineer A's professional character meets the standard the role demands.

This question emerged because the NSPE Code's internal architecture distinguishes mandatory from encouraged provisions, and Engineer A's omission sits at the intersection of both tiers, making it impossible to characterize the violation without first resolving whether the Code's tiered structure creates a hierarchy of obligations or whether a single act can simultaneously breach a strict duty and fall short of an aspirational standard. The enactment of Section III.2.d. after the precedent cases of BER 89-7 and 97-13 further destabilizes the deontological analysis by introducing a new normative layer whose relationship to pre-existing mandatory duties has not been authoritatively resolved.

This question emerged because the omission creates a counterfactual gap: the actual regulatory outcome was shaped by incomplete information, and the question of whether inclusion would have changed the authority's decision is both practically significant and ethically loaded, since if inclusion would have been outcome-determinative, the harm of omission is concrete rather than speculative. The client notification sub-question arose because Engineer A's verbal disclosure to the client - but not to the authority - raises the structural issue of whether the client relationship creates any legitimate procedural rights over the content of a public regulatory submission.

This question emerged because the threatened-versus-endangered regulatory distinction introduced a gradient into what might otherwise be treated as a binary disclosure obligation, forcing the question of whether legal classification categories should map directly onto ethical obligation strength or whether the engineer's duty is grounded in the confirmed materiality of the finding independent of its regulatory label. The question is structurally necessary because if the distinction carries moral weight, it could partially justify Engineer A's omission as a calibrated professional judgment; if it carries no moral weight, the omission is equally unjustifiable regardless of the species' precise regulatory status.

This question arose because BER 97-13 established a precedent in which a written confidentiality instruction from a client/prime consultant provided Engineer A with an ethical defense for omitting a speculative structural observation from a final report, and the present case involves a structurally analogous written-instruction scenario but with a critically different data profile - a biologist-confirmed, domain-competence-verified threatened species finding submitted into a public regulatory process rather than a speculative out-of-competence observation in a private project context. The question emerges from the contested transferability of the BER 97-13 confidentiality warrant across these factual distinctions, forcing analysis of whether the public-safety and regulatory-disclosure obligations that override confidentiality in environmental contexts are categorically stronger than those present in the structural observation context where confidentiality was permitted.

This question arose because the sequential structure of Engineer A's decisions - first accepting the engagement, then discovering the threatened species finding, then omitting it from the public authority report - creates a logical fork at the acceptance decision point: if refusal at the outset would have better served the public interest by preventing the misleading regulatory submission, then the acceptance itself may constitute the primary ethical failure rather than the subsequent omission, fundamentally reframing where Engineer A's obligation was breached. The question is further sharpened by the tension between the Sustainable Development Encouraged Provision Non-Mandatory Task Refusal Boundary Constraint - which limits how far NSPE Code Section III.2.d. can compel affirmative action - and the Incidental Observation Disclosure Obligation and Written Report Completeness Obligation, which together suggest that once engagement is accepted and a material finding is confirmed, the obligation to disclose becomes absolute and the pre-acceptance refusal option becomes ethically irrelevant to the post-acceptance reporting duty.

The Board resolved the conflict between mandatory and aspirational code provisions by anchoring its conclusion exclusively in Section II.3.a.'s strict 'shall' duty, reasoning that relying primarily on the encouraged sustainable development provision would misrepresent the violation as merely aspirational when it is in fact a categorical breach of a mandatory reporting standard.

The Board resolved the tension between scope-limitation precedent and the present engagement's circumstances by conducting a point-by-point comparison with BER 97-13, concluding that because all three conditions that justified omission in that case are absent here, the precedent affirmatively supports rather than excuses Engineer A's obligation to include the biologist's finding.

The Board resolved the regulatory classification question by treating the completeness duty as binary rather than graduated, reasoning that allowing the threatened-versus-endangered distinction to affect disclosure would impermissibly delegate to the engineer or client the public authority's prerogative to weigh environmental risk, which is precisely what the objective truthfulness standard is designed to prevent.

The Board concluded that Engineer A's client relationship did not authorize selective omission because the engagement's regulatory purpose - producing a report on which a public authority would rely - activated both the paramount public welfare obligation and the Section II.3.a. truthfulness duty simultaneously, and that the ethically consistent alternative to compliance was declining or withdrawing from the engagement rather than submitting an incomplete document.

The Board resolved Q2 by treating the omission from the written report as a self-standing ethical violation, reasoning that the duty of objective and truthful professional reporting is discharged only when the party responsible for protecting the public interest - the public authority - actually receives the material finding in the document on which it will rely, and that verbal-only disclosure to the client cannot cure that deficiency.

The board resolved Q3 and Q8 by distinguishing the present case from BER 97-13 on the axis of in-house specialist competence: because Engineer A's own firm employed a credentialed biologist who applied domain expertise directly to the site, the finding carried the weight of a professional technical judgment rather than an outside-competence guess, and that characterization materially strengthened - rather than left optional - the obligation to include it in the written report.

The board reached the core ethical determination - that omission was unethical - by applying the mandatory completeness standard of II.3.a. directly: a public authority relying on a professional engineering report is entitled to all material findings, and Engineer A's choice to omit a competence-confirmed threatened species risk constituted a straightforward violation of that duty regardless of client interest or regulatory severity gradations.

The board resolved Q2 and Q10 by analyzing the structural relationship between the parties: because the public authority - not the client - is the party whose decision depends on the report's completeness, and because the client had every incentive to suppress the finding, verbal disclosure to the client was categorically incapable of discharging any part of the reporting obligation, making the submission of the incomplete written report an independent and complete ethical violation.

The board resolved Q4, Q6, and Q16 by disaggregating the client relationship into two distinct obligations - the courtesy duty to notify in advance and the substantive duty to report completely - and finding that only the first is owed to the client, while the second is owed to the public authority and cannot be overridden by client instruction, making the absence of any confidentiality instruction in the actual case an aggravating rather than mitigating circumstance.

The board resolved Q5, Q9, and Q15 by anchoring the reporting obligation firmly in the mandatory II.3.a. completeness standard and applying a materiality test - whether the finding matters to the public authority's decision - rather than a regulatory classification test, concluding that a formally designated threatened species in adjacent protected wetlands is unambiguously material regardless of whether it sits one tier below endangered status.

The board concluded that no genuine conflict exists between faithful agency and public welfare in this case because faithful agency never extended to omitting material findings from public authority submissions; the two obligations do not compete at equal weight but rather the public welfare obligation sets the outer limit of permissible client service, and Engineer A crossed that limit by submitting an incomplete report.

The board concluded that confidentiality provided Engineer A with no defense because the client never invoked it, and further determined that even a hypothetical confidentiality instruction would not have shielded the omission because the provision targets proprietary business information rather than material environmental findings relevant to regulatory decisions protecting the public.

The board concluded that BER 97-13 does not transfer to the present case because the scope limitation defense depends on the conjunction of a scope gap and a competence gap, and here the in-house biologist's finding falls squarely within both the scope of an environmental engagement and the firm's demonstrated domain expertise, making the mandatory completeness obligation under Section II.3.a. fully applicable.

The board concluded that the violation finding rests most securely on the mandatory duty under Section II.3.a. rather than the encouraged provision under Section III.2.d., because blending the two without distinguishing their normative weight would risk misrepresenting the omission as a failure of aspiration rather than a breach of a strict professional duty.

The board concluded from a deontological perspective that verbal disclosure to the developer client did not satisfy Engineer A's categorical duty of truthfulness to the public authority, because the written report is the instrument through which the public authority exercises its regulatory function and the duty of completeness attaches independently to that instrument regardless of what was communicated privately to the client.

The board resolved Q11 by applying a consequentialist calculus that identified three distinct categories of harm - ecological, procedural, and systemic - and found that none of the harms to the developer from inclusion constituted unjust injury, since regulatory delay or denial is the designed outcome of a functioning review process, making Engineer A's omission unethical on consequentialist grounds.

The board resolved Q12 by identifying three specific virtues - integrity, courage, and stewardship - that Engineer A's conduct failed to demonstrate, and concluded that a trustworthy environmental professional would have included the finding in the written report and helped the client navigate regulatory implications rather than shielding the client from them through selective omission.

The board resolved Q9 and Q13 by establishing that Engineer A's omission simultaneously violated a strict mandatory duty and fell short of an encouraged aspiration, but anchored the ethical finding exclusively on the Section II.3.a. violation to prevent any argument that the 'encouraged' language of Section III.2.d. rendered the overall obligation merely optional.

The board resolved Q14 by working through the counterfactual in two steps: first establishing that the client would have had no legitimate basis to object to inclusion, and then tracing how inclusion would have triggered the regulatory body's obligation to consider the finding, demonstrating that Engineer A's omission was not merely a technical violation but a material impairment of the public authority's decision-making capacity.

The board resolved Q5 and Q15 by decoupling the NSPE Code's disclosure obligation from the ESA's regulatory severity framework, concluding that the threatened classification already constitutes a formal determination of significant risk sufficient to satisfy the materiality threshold, and that importing the endangered-versus-threatened distinction into the ethical analysis would substitute an unauthorized regulatory proxy for the Code's actual standard.

The board concluded that a written confidentiality instruction would not have provided Engineer A an ethical defense because the present case lacks the two factors that justified omission in BER 97-13 - speculative finding and competence gap - and because the NSPE Code's confidentiality provision under Section III.4. does not extend to suppressing material, competence-confirmed environmental findings from public regulatory submissions; Engineer A would have been required to include the finding, withdraw, or refuse to submit the incomplete report.

The board concluded that declining the engagement would not have better served the public interest than accepting it and reporting completely, because the public authority's ability to make informed regulatory decisions depends on competent engineers accepting such engagements and honoring the completeness obligation that acceptance entails under Section II.3.a.; the ethical failure was Engineer A's omission of the threatened species finding, not the decision to take the engagement.

The board concluded that the faithful agent obligation functions as a bounded duty that governs the manner of client service but cannot authorize omission of environmentally significant facts from public regulatory submissions, and that the boundary is crossed not when an 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.

The board concluded that because no confidentiality instruction was given, Engineer A had no ethical basis to treat the threatened species finding as protected information, and that the completeness obligation under Section II.3.a. applied automatically and fully; the case further teaches that confidentiality and completeness are not symmetrical obligations, with confidentiality requiring affirmative client invocation while completeness is self-executing in every public regulatory submission.

The board concluded that the Scope Limitation Defense and Expertise Calibration principles are not genuinely in tension because they operate on different axes, and that both defenses fail in the present case since the biologist's finding was made within the firm's domain competence and was confirmed rather than speculative, meaning the completeness obligation under Section II.3.a. applied with full force and no scope limitation argument could override it.

The Board concluded that Engineer A acted unethically primarily because the mandatory standard of Section II.3.a. - requiring objective and truthful professional reports with no carve-out for client preference - was violated by the omission of the threatened species finding; the Board further concluded that while Section III.2.d.'s sustainable development language pointed in the same direction, it could not independently sustain the violation finding because it is an encouraged aspiration rather than a strict duty, and relying on it as the primary basis would both overstate its normative force and understate the strength of the mandatory completeness obligation, potentially creating a misleading precedent for future cases.

Was Engineer A ethically required to include the biologist's threatened species finding in the written report submitted to the public authority, given that Engineer A verbally mentioned the concern to the developer client but omitted it from the official written submission?

Did Engineer A's verbal mention of the threatened species concern to the developer client discharge any part of the professional obligation to ensure the public authority received complete environmental information, or does the omission from the written report constitute a self-standing ethical violation independent of the private client communication?

Did Engineer A's faithful agent obligation to the developer client provide any legitimate basis for omitting the threatened species finding from the written report submitted to the public authority, or did the engagement's regulatory purpose and the public welfare paramount obligation render the faithful agent duty inapplicable to the content of the official submission?

Should Engineer A include the biologist's threatened species finding in the written report submitted to the public authority, given that Engineer A has already verbally disclosed the concern to the developer client who has not explicitly invoked confidentiality?

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?

Given that the developer client gave no explicit confidentiality instruction regarding the threatened species finding, and given that the written report is destined for a public authority conducting a regulatory review, should Engineer A treat the faithful agent obligation as authorizing selective omission of the finding in order to serve the client's interest in a favorable regulatory outcome?

Should Engineer A include the in-house biologist's threatened species finding in the written report submitted to the public authority, or is verbal disclosure to the developer client a sufficient discharge of the reporting obligation?

Given that the biologist used probabilistic language and the finding arose incidentally within an environmental analysis engagement, should Engineer A treat the threatened species finding as a confirmed professional judgment requiring written disclosure to the public authority, or apply the BER 97-13 scope-and-competence framework to justify its omission?

Given that the developer client gave no confidentiality instruction regarding the threatened species finding, should Engineer A treat the finding as unprotected information subject to the full completeness obligation - and would an explicit written confidentiality instruction have altered that analysis?

Should Engineer A include the in-house biologist's threatened species finding in the written report submitted to the public authority, given that Engineer A verbally disclosed the concern to the developer client but the client has not explicitly invoked confidentiality or instructed omission?

Does Engineer A's verbal disclosure to the developer client discharge any part of the reporting obligation owed to the public authority, and can Engineer A invoke the BER 97-13 scope-limitation or competence-gap precedent to justify omitting the biologist's finding from the written report?

When the developer client's commercial interest in a favorable regulatory outcome conflicts with Engineer A's obligation to submit a complete and truthful written report to the public authority, does the faithful agent obligation authorize Engineer A to omit the threatened species finding, and was Engineer A required to advise the client in advance that the finding would be included before submitting the report?