Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section II. Rules of Practice 3 154 entities
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 shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments.
Section III. Professional Obligations 1 68 entities
Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 2 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
It is not unethical for an engineering firm to continue to represent a departing employee as a current employee when the employee is not highlighted as a 'key employee' and the totality of circumstances does not constitute an overt misrepresentation of an important fact about the firm's makeup.
Citation Context:
The Board cited this case as a follow-up to Case No. 83-1 to further refine the standard for when continued representation of an employee's affiliation with a firm becomes an ethical violation, and to distinguish the present case from situations involving misrepresentation of positive qualifications.
Principle Established:
It is unethical for an engineering firm to distribute promotional brochures listing a former employee as a key employee after that employee's actual termination, as this constitutes a misrepresentation of pertinent facts with intent to enhance the firm's qualifications.
Citation Context:
The Board cited this case to establish the principle that including misleading information about firm qualifications in promotional materials constitutes a misrepresentation of pertinent facts. It was used to analyze whether omitting negative information about an engineer's qualifications similarly misleads a client.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionWas it unethical for Engineer A to not report to Client B the ethics complaint filed against Engineer A by Client C?
It was ethical for Engineer A not to report to Client B the ethics complaint filed against Engineer A by Client C.
Does the fact that Client C's competence allegation involves services similar in nature to those Engineer A is currently performing for Client B heighten the materiality of the complaint to Client B's engagement, and should that similarity have independently triggered a disclosure obligation even if a generic pending complaint would not?
The Board's conclusion that non-disclosure was ethical rests on the allegation-adjudication distinction - the principle that an unproven complaint does not carry the evidentiary weight necessary to compel disclosure. However, this distinction, while defensible as a general rule, is strained in the present case by a critical contextual variable: the services at issue in Client C's competence complaint are similar in nature to those Engineer A is actively performing for Client B. This domain similarity elevates the materiality of the complaint beyond what would be expected of a generic or unrelated allegation. A pending competence challenge in an identical or closely analogous service domain is not merely background noise about Engineer A's professional history - it is directly probative of the quality and reliability of the very work Client B is currently receiving. The Board's reasoning does not adequately grapple with this similarity as an independent variable that could shift the disclosure calculus. Even accepting that an adjudicated finding would be required before disclosure becomes obligatory in the general case, the domain-specific relevance of Client C's complaint creates a heightened materiality threshold that the allegation-adjudication distinction alone cannot fully neutralize. A more complete analysis would have required the Board to address whether the similar-services context independently amplifies Engineer A's faithful agent obligation toward Client B, and whether that amplification pushes the disclosure question closer to the boundary of ethical requirement rather than mere prudential recommendation.
The domain similarity between Client C's competence allegation and the services Engineer A is actively performing for Client B materially heightens the relevance of the complaint to Client B's engagement. A generic pending complaint in an unrelated engineering discipline would carry minimal informational weight for Client B; by contrast, a competence challenge arising from services nearly identical in nature to those currently being rendered directly implicates the quality and reliability of what Client B is receiving. This similarity does not automatically convert a non-disclosure into an ethical violation under the Board's allegation-adjudication framework, but it does represent the critical variable that most strains the Board's conclusion. The domain-specific relevance of the complaint means that Client B's ability to make an informed decision about the engagement is more directly affected than it would be in a dissimilar-services scenario. Accordingly, the similar-services context independently amplifies the prudential case for disclosure and brings the non-disclosure closer to the boundary of the faithful agent obligation under Section III.3.a, even if it does not cross that boundary under the Board's chosen threshold.
The counterfactual scenario in which the ethics complaint involved services in a completely different engineering domain from those being performed for Client B would have made the Board's conclusion of ethical non-disclosure substantially more defensible. In that scenario, the complaint's relevance to Client B's engagement would be attenuated - a competence challenge in, say, structural engineering would carry little informational weight for a client receiving CPM scheduling services. The domain similarity in the actual case is therefore the critical variable that most strains the Board's reasoning, because it transforms the complaint from a background professional matter into a directly relevant signal about the quality of services Client B is currently receiving. This analysis suggests that the Board's allegation-adjudication distinction, while sound as a general principle, requires a domain-relevance modifier: the closer the subject matter of the pending complaint to the services being rendered to the current client, the stronger the case for disclosure even at the allegation stage. The Board's failure to articulate this modifier leaves its conclusion underspecified and potentially misleading as precedent for cases where domain similarity is even more pronounced.
Does Engineer A have an ongoing obligation to proactively assess his own competence in light of the pending complaint, and if that self-assessment reveals genuine doubt about his qualifications, does that create a separate and independent duty to disclose to Client B beyond the mere existence of the complaint?
Engineer A bears an independent and ongoing obligation to assess his own competence in light of the pending complaint, and this obligation exists entirely separately from the question of whether the complaint must be disclosed to Client B. If Engineer A's honest self-assessment reveals genuine doubt about his qualifications to perform the services currently being rendered - the very services that Client C's complaint calls into question - then a separate and independent duty to disclose arises, grounded not in the existence of the complaint itself but in the professional competence standard and the faithful agent obligation. Under this analysis, the complaint functions as a trigger for self-examination rather than as the primary disclosure event. Should that self-examination produce a conclusion that Engineer A is not fully competent to perform the services for Client B, the Code's competence provisions would require Engineer A to either disclose that limitation or decline to continue the engagement. The Board's analysis does not address this competence self-assessment dimension, leaving open the possibility that Engineer A's non-disclosure was ethically permissible with respect to the complaint's existence but potentially impermissible if Engineer A harbored genuine competence doubts that were not surfaced.
Given that Client B ultimately learned of the complaint through a third party and expressed that trust was undermined, should the Board's ethical analysis account for the foreseeable relational harm of non-disclosure as a factor weighing against the conclusion that non-disclosure was ethical, even if not strictly required by code provisions?
The Board's conclusion that non-disclosure was ethical does not adequately account for the foreseeable relational harm that materialized when Client B discovered the complaint through a third party. The fact that Client B's trust was undermined was not an unforeseeable consequence - it was a predictable outcome of Engineer A's decision to remain silent about a matter that Client B would reasonably regard as material to the engagement. A complete ethical analysis should treat the foreseeability of relational harm as a factor weighing against the ethical adequacy of non-disclosure, even if that harm does not independently compel a different legal or code-based conclusion. The Board's prudential recommendation that disclosure would have been the wiser course implicitly acknowledges this harm but stops short of integrating it into the ethical calculus. A more robust analysis would recognize that the faithful agent obligation encompasses not only the transmission of technically required information but also the preservation of the trust relationship that makes professional engagement possible. Engineer A's non-disclosure, while not adjudicated as a code violation, produced a foreseeable erosion of that trust that a genuinely faithful agent would have sought to prevent.
At what point, if any, does a pending ethics complaint become sufficiently adjudicated or substantiated that Engineer A would be obligated to disclose it to Client B, and what procedural threshold triggers that obligation?
In response to the implicit question about the procedural threshold that would trigger a mandatory disclosure obligation, the Board's reasoning implies a graduated model rather than a binary one. At the stage of a mere unsubstantiated allegation - as in the present case - no disclosure obligation is compelled. However, the threshold shifts meaningfully at several identifiable procedural milestones: first, when a licensing board formally finds probable cause sufficient to advance the complaint to a hearing; second, when a formal disciplinary hearing is convened and Engineer A is required to appear; and third, when any adverse finding, consent agreement, or sanction is issued. Each of these stages represents a qualitative increase in the substantiation of the allegation that progressively erodes the privacy interest Engineer A holds in the unresolved complaint and correspondingly strengthens Client B's claim to material information. A formal adverse finding would almost certainly cross the threshold into mandatory disclosure under the faithful agent obligation and the honesty provisions of the Code, because at that point the allegation has been adjudicated and is no longer merely an accusation. The Board's silence on this graduated model represents a gap in its analysis that practitioners need to navigate carefully.
Does the Allegation-Adjudication Distinction - which holds that an unproven complaint does not compel disclosure - conflict with the Faithful Agent Obligation, which requires Engineer A to act in Client B's best interest by ensuring Client B has all information material to the engagement, including information that might affect Client B's confidence in Engineer A's competence?
There is a genuine and unresolved tension between the Allegation-Adjudication Distinction and the Faithful Agent Obligation that the Board's conclusion does not fully reconcile. The Allegation-Adjudication Distinction holds that an unproven complaint does not compel disclosure because it lacks the evidentiary weight of an adjudicated finding. The Faithful Agent Obligation, however, requires Engineer A to act in Client B's best interest by ensuring Client B possesses all information material to the engagement. These two principles point in opposite directions when the pending complaint involves services similar to those being performed for Client B, because the complaint's domain relevance makes it potentially material to Client B's decision-making regardless of its adjudication status. The Board resolves this tension in favor of the Allegation-Adjudication Distinction without fully explaining why the materiality of the complaint to the current engagement does not override the privacy interest in an unresolved allegation. This gap in reasoning leaves the conclusion vulnerable to the critique that the Board has privileged Engineer A's interest in avoiding reputational harm from an unproven allegation over Client B's interest in making a fully informed decision about the engagement.
The Board resolved the tension between the Allegation-Adjudication Distinction and the Faithful Agent Obligation by treating adjudication status as a threshold gate rather than a balancing factor. Under this resolution, the Faithful Agent Obligation does not independently compel disclosure of information that has not been substantiated through a formal proceeding, even when that information is materially relevant to the current engagement. The practical effect is that the Faithful Agent Obligation is subordinated to the Allegation-Adjudication Distinction whenever the underlying information consists solely of an unproven allegation. This prioritization reflects a structural judgment that premature disclosure of unresolved complaints would expose engineers to reputational harm disproportionate to the informational benefit provided to clients, and that the integrity of the adjudicative process itself is a value the Code implicitly protects. However, this resolution leaves unaddressed the scenario where the allegation is domain-specific and directly mirrors the services being rendered to the current client, a factual configuration present in this case that the Board did not treat as independently dispositive. The case therefore teaches that the Faithful Agent Obligation has a ceiling defined by allegation status, but does not clarify whether domain-specific similarity to current services constitutes an exception to that ceiling.
Does the principle of Informed Decision-Making Enablement - which holds that Client B has a right to know information that could affect his decision to retain Engineer A - conflict with the Privacy Right vs. Material Omission principle, which recognizes that engineers retain some privacy interest in unresolved allegations that have not been adjudicated against them?
The tension between Informed Decision-Making Enablement and the Privacy Right versus Material Omission principle reflects a deeper structural ambiguity in the Board's framework: it simultaneously acknowledges that Client B has a legitimate interest in information that could affect his decision to retain Engineer A, and that Engineer A retains a privacy interest in unresolved allegations. The Board resolves this tension by treating the allegation's unproven status as dispositive, but this resolution is incomplete because it does not specify what makes an omission 'material' under Section III.3.a independently of whether the underlying allegation has been proven. If materiality is assessed from Client B's perspective - as a reasonable client who would want to know about a pending competence challenge involving similar services - then the omission is material regardless of adjudication status. If materiality is assessed from the perspective of established fact, then the Board's conclusion follows more naturally. The Board implicitly adopts the latter standard without defending it, and this choice deserves explicit justification given that the Code's non-deception provisions do not expressly limit materiality to adjudicated facts.
The tension between Informed Decision-Making Enablement and the Privacy Right versus Material Omission principle was resolved in favor of the engineer's privacy interest in unresolved allegations, but only partially and conditionally. The Board's simultaneous conclusion that non-disclosure was ethical and its prudential recommendation that disclosure would have been wiser reveals that these two principles were not fully reconciled - they were instead assigned to different normative registers. The Privacy Right versus Material Omission principle governed the ethical compliance question, while Informed Decision-Making Enablement was relegated to the domain of prudential wisdom. This bifurcation is analytically significant because it implies that the NSPE Code's honesty and non-deception provisions, specifically Section III.3.a, do not treat silence about an unresolved allegation as a material omission sufficient to constitute deception, even when the client would have found the information decision-relevant. The case therefore teaches that materiality under Section III.3.a is not determined solely by the client's subjective interest in the information, but is filtered through the allegation-adjudication threshold. A pending, unproven complaint does not achieve the status of a 'material fact' for disclosure purposes regardless of how relevant the client would consider it. This principle prioritization, however, creates a structural gap: the Code as interpreted provides no mechanism for clients to obtain complaint information that is simultaneously unproven and highly relevant to their engagement, leaving them dependent on third-party discovery as the only practical pathway to that information.
Does the Valence-Neutral Standard - which holds that omissions of negative information can be just as deceptive as omissions of positive information - conflict with the Pending Competence Complaint Disclosure Obligation Negated by Allegation Status, creating an unresolved tension about whether Engineer A's silence constitutes a misleading omission under Section III.3.a even if no affirmative misrepresentation was made?
The Board's conclusion that non-disclosure was ethical does not resolve - and in fact creates - an internal tension between the allegation-adjudication distinction and the valence-neutral standard for deception articulated in the Board's own reasoning. The valence-neutral standard holds that omissions of negative information can be just as deceptive as omissions of positive information, and that the ethical character of an omission is not determined by whether the withheld information is favorable or unfavorable to the omitting party. Applying this standard to Engineer A's conduct, the question becomes whether Engineer A's silence about the pending competence complaint constituted a misleading omission under Section III.3.a - not because the complaint was adjudicated, but because a reasonable client in Client B's position would regard the existence of a pending competence challenge involving similar services as information material to the decision to continue the engagement. The Board's conclusion that no disclosure obligation arose effectively treats the allegation-adjudication distinction as a categorical override of the valence-neutral standard, but this override is not explicitly justified in the Board's reasoning. A more rigorous analysis would have required the Board to explain why the allegation-adjudication distinction takes precedence over the valence-neutral deception standard when the omitted information is directly relevant to the current engagement - or alternatively, to acknowledge that the two principles exist in genuine tension that the present case does not fully resolve. Furthermore, the scenario in which Client B explicitly asks Engineer A about pending complaints at the outset of the engagement reveals the clearest expression of this tension: in that scenario, Engineer A's silence or evasion would almost certainly constitute a violation of the honesty and non-deception provisions of the NSPE Code, demonstrating that passive non-disclosure is an ethically adequate standard only in the absence of direct inquiry, and that the adequacy of that standard is more fragile than the Board's conclusion suggests.
The counterfactual scenario in which Client B explicitly asked Engineer A at the outset of the engagement whether any ethics complaints or competence challenges had been filed against Engineer A reveals a critical asymmetry in the Board's framework: passive non-disclosure and active deception in response to a direct inquiry are treated as categorically different ethical acts, and rightly so. Had Client B posed such a direct question and Engineer A denied or concealed the existence of the pending complaint, that conduct would constitute a clear violation of the honesty and non-deception provisions of the Code, regardless of the complaint's adjudication status. This scenario demonstrates that the Board's conclusion of ethical non-disclosure is contingent on the absence of a direct inquiry - a contingency the Board does not make explicit. The adequacy of passive non-disclosure as an ethical standard is therefore limited to situations where the client has not affirmatively sought the information. This analysis also reveals that engineers in Engineer A's position bear a heightened obligation to ensure that their silence does not function as an implicit representation that no such complaints exist, particularly when clients might reasonably assume that a retained professional would volunteer such information.
The Board's simultaneous conclusion that non-disclosure was ethical and recommendation that disclosure would have been the prudent course reveals an internal tension that the Board does not resolve. If Engineer A's conduct was fully ethical, the prudential recommendation is difficult to explain except as a practical observation about relationship management. However, if the prudential recommendation reflects a genuine ethical judgment that Engineer A's conduct, while not a code violation, fell short of the ideal standard of professional conduct, then the Board is implicitly acknowledging a sub-threshold ethical deficiency - a zone of conduct that is technically permissible but not fully consonant with the values the Code is designed to promote. This distinction between 'not unethical' and 'fully ethical' is meaningful and the Board's framing collapses it. A more precise conclusion would have been that Engineer A's non-disclosure did not constitute a code violation but that the faithful agent obligation and the honesty norm together counsel a higher standard of proactive transparency that Engineer A failed to meet. The Valence-Neutral Standard further complicates the Board's position: if omissions of negative information can be as deceptive as omissions of positive information, then Engineer A's silence about a domain-relevant competence complaint is at minimum a borderline case under Section III.3.a that the Board treats too confidently as resolved.
The most significant unresolved principle tension in this case is the internal inconsistency between the Valence-Neutral Standard and the Pending Competence Complaint Disclosure Obligation Negated by Allegation Status. The Board invoked the Valence-Neutral Standard to confirm that omissions of negative information can be as deceptive as omissions of positive information, yet simultaneously concluded that Engineer A's silence did not constitute a misleading omission under Section III.3.a. These two positions can only be reconciled if the Board implicitly adopted a secondary filter: that the Valence-Neutral Standard applies only to information that has crossed the adjudication threshold, such that unproven allegations are categorically excluded from the class of omissions that can be 'material' under the Code regardless of their valence. The Board did not state this secondary filter explicitly, leaving the Valence-Neutral Standard effectively inoperative in the pending-complaint context. Furthermore, the Prudential Disclosure Recommendation - advising Engineer A that voluntary disclosure would have been the wiser course - implicitly acknowledges that the omission carried relational and reputational consequences that a prudent engineer should have foreseen. This acknowledgment, when read alongside the Valence-Neutral Standard, suggests that the Board recognized a sub-threshold ethical deficiency in Engineer A's conduct that it was unwilling to characterize as a Code violation. The case therefore teaches that principle tensions are sometimes resolved not by genuine synthesis but by assigning competing principles to different normative tiers - ethical compliance versus prudential wisdom - a resolution that preserves doctrinal coherence at the cost of practical clarity for engineers navigating similar disclosure decisions in the future.
Does the Prudential Disclosure Recommendation - which advises Engineer A that proactively informing Client B would have been the wiser course - conflict with the Allegation-Adjudication Distinction principle in a way that reveals an internal inconsistency in the Board's conclusion: if non-disclosure was fully ethical, why does the Board simultaneously recommend disclosure as the prudent course, and does that recommendation implicitly acknowledge a sub-threshold ethical deficiency in Engineer A's conduct?
The Board's simultaneous conclusion that non-disclosure was ethical and recommendation that disclosure would have been the prudent course reveals an internal tension that the Board does not resolve. If Engineer A's conduct was fully ethical, the prudential recommendation is difficult to explain except as a practical observation about relationship management. However, if the prudential recommendation reflects a genuine ethical judgment that Engineer A's conduct, while not a code violation, fell short of the ideal standard of professional conduct, then the Board is implicitly acknowledging a sub-threshold ethical deficiency - a zone of conduct that is technically permissible but not fully consonant with the values the Code is designed to promote. This distinction between 'not unethical' and 'fully ethical' is meaningful and the Board's framing collapses it. A more precise conclusion would have been that Engineer A's non-disclosure did not constitute a code violation but that the faithful agent obligation and the honesty norm together counsel a higher standard of proactive transparency that Engineer A failed to meet. The Valence-Neutral Standard further complicates the Board's position: if omissions of negative information can be as deceptive as omissions of positive information, then Engineer A's silence about a domain-relevant competence complaint is at minimum a borderline case under Section III.3.a that the Board treats too confidently as resolved.
The most significant unresolved principle tension in this case is the internal inconsistency between the Valence-Neutral Standard and the Pending Competence Complaint Disclosure Obligation Negated by Allegation Status. The Board invoked the Valence-Neutral Standard to confirm that omissions of negative information can be as deceptive as omissions of positive information, yet simultaneously concluded that Engineer A's silence did not constitute a misleading omission under Section III.3.a. These two positions can only be reconciled if the Board implicitly adopted a secondary filter: that the Valence-Neutral Standard applies only to information that has crossed the adjudication threshold, such that unproven allegations are categorically excluded from the class of omissions that can be 'material' under the Code regardless of their valence. The Board did not state this secondary filter explicitly, leaving the Valence-Neutral Standard effectively inoperative in the pending-complaint context. Furthermore, the Prudential Disclosure Recommendation - advising Engineer A that voluntary disclosure would have been the wiser course - implicitly acknowledges that the omission carried relational and reputational consequences that a prudent engineer should have foreseen. This acknowledgment, when read alongside the Valence-Neutral Standard, suggests that the Board recognized a sub-threshold ethical deficiency in Engineer A's conduct that it was unwilling to characterize as a Code violation. The case therefore teaches that principle tensions are sometimes resolved not by genuine synthesis but by assigning competing principles to different normative tiers - ethical compliance versus prudential wisdom - a resolution that preserves doctrinal coherence at the cost of practical clarity for engineers navigating similar disclosure decisions in the future.
From a deontological perspective, did Engineer A fulfill their duty as a faithful agent to Client B by withholding knowledge of a pending competence complaint involving services nearly identical to those being performed for Client B, regardless of whether that complaint had been adjudicated?
From a deontological perspective, Engineer A's non-disclosure is difficult to fully justify under the faithful agent duty when the pending complaint involves services nearly identical to those being performed for Client B. The categorical nature of the faithful agent obligation - which requires Engineer A to act as Client B's trusted representative with full transparency about matters material to the engagement - does not easily accommodate a carve-out for unproven allegations when those allegations directly concern the competence being applied to Client B's project. A strict deontological reading would hold that the duty to act in Client B's best interest is not contingent on the outcome of the complaint but on the relevance of the information to Client B's decision-making. Under this reading, Engineer A's non-disclosure represents a failure of the faithful agent duty regardless of the allegation's adjudication status, because the duty is owed at the time of the engagement, not retrospectively after the complaint is resolved. The Board's conclusion is more consistent with a rule-based deontological framework that sets the disclosure threshold at adjudication in order to protect engineers from reputational harm caused by unproven allegations - a defensible policy choice, but one that should be acknowledged as a policy choice rather than presented as the only ethically coherent outcome.
The Board resolved the tension between the Allegation-Adjudication Distinction and the Faithful Agent Obligation by treating adjudication status as a threshold gate rather than a balancing factor. Under this resolution, the Faithful Agent Obligation does not independently compel disclosure of information that has not been substantiated through a formal proceeding, even when that information is materially relevant to the current engagement. The practical effect is that the Faithful Agent Obligation is subordinated to the Allegation-Adjudication Distinction whenever the underlying information consists solely of an unproven allegation. This prioritization reflects a structural judgment that premature disclosure of unresolved complaints would expose engineers to reputational harm disproportionate to the informational benefit provided to clients, and that the integrity of the adjudicative process itself is a value the Code implicitly protects. However, this resolution leaves unaddressed the scenario where the allegation is domain-specific and directly mirrors the services being rendered to the current client, a factual configuration present in this case that the Board did not treat as independently dispositive. The case therefore teaches that the Faithful Agent Obligation has a ceiling defined by allegation status, but does not clarify whether domain-specific similarity to current services constitutes an exception to that ceiling.
From a consequentialist perspective, did the outcome of Client B discovering the ethics complaint through a third party - resulting in damaged trust and relational harm - demonstrate that Engineer A's decision not to disclose produced worse aggregate consequences than voluntary disclosure would have, thereby undermining the Board's conclusion that non-disclosure was ethical?
From a consequentialist perspective, the outcome in this case - Client B discovering the complaint through a third party and experiencing damaged trust - provides empirical evidence that Engineer A's non-disclosure produced worse aggregate consequences than voluntary disclosure would have. Had Engineer A proactively disclosed the complaint with appropriate context, Client B would have received the information from a trusted source, with Engineer A's framing and assurances, rather than from an unknown third party without context or mitigation. The consequentialist calculus strongly favors disclosure: the costs of voluntary disclosure (potential client concern, temporary awkwardness) are substantially lower than the costs of third-party discovery (damaged trust, loss of relational confidence, reputational harm to Engineer A). The Board's conclusion that non-disclosure was ethical is difficult to sustain under a consequentialist framework precisely because the foreseeable and actual consequences of non-disclosure were worse than the foreseeable consequences of disclosure. This does not mean the Board's conclusion is wrong under a code-based analysis, but it does mean that the Board's ethical framework is not consequentialist in character - a point that should be made explicit rather than left implicit.
From a virtue ethics perspective, did Engineer A demonstrate the professional integrity and honesty expected of a virtuous engineer by remaining silent about a pending competence allegation involving similar services, or does the act of non-disclosure - even if technically permissible - reflect a failure of the character trait of transparency that clients are entitled to expect from their professional advisors?
From a virtue ethics perspective, Engineer A's non-disclosure - even if technically permissible under the Board's allegation-adjudication framework - reflects a failure of the character trait of transparency that clients are entitled to expect from professional advisors. A virtuous engineer, characterized by integrity, honesty, and genuine concern for the client's interests, would not remain silent about a pending competence challenge involving services nearly identical to those being rendered, particularly when the foreseeable consequence of silence is that the client will discover the complaint through a third party and feel betrayed. The virtue ethics critique of the Board's conclusion is not that Engineer A violated a specific code provision, but that the decision to remain silent reflects a disposition toward self-protection over client service - a disposition that falls short of the professional character the engineering profession aspires to cultivate. The Board's prudential recommendation that disclosure would have been the wiser course is, in virtue ethics terms, an acknowledgment that the virtuous engineer would have disclosed, which implicitly concedes that Engineer A's conduct, while not a code violation, was not the conduct of a fully virtuous professional.
From a deontological perspective, does the fact that the pending competence complaint by Client C involved services similar in nature to those being performed for Client B create a heightened categorical duty to disclose - one that transcends the general allegation-versus-adjudication distinction - because the domain-specific relevance of the complaint directly implicates Client B's ability to make an informed decision about the engagement?
From a deontological perspective, Engineer A's non-disclosure is difficult to fully justify under the faithful agent duty when the pending complaint involves services nearly identical to those being performed for Client B. The categorical nature of the faithful agent obligation - which requires Engineer A to act as Client B's trusted representative with full transparency about matters material to the engagement - does not easily accommodate a carve-out for unproven allegations when those allegations directly concern the competence being applied to Client B's project. A strict deontological reading would hold that the duty to act in Client B's best interest is not contingent on the outcome of the complaint but on the relevance of the information to Client B's decision-making. Under this reading, Engineer A's non-disclosure represents a failure of the faithful agent duty regardless of the allegation's adjudication status, because the duty is owed at the time of the engagement, not retrospectively after the complaint is resolved. The Board's conclusion is more consistent with a rule-based deontological framework that sets the disclosure threshold at adjudication in order to protect engineers from reputational harm caused by unproven allegations - a defensible policy choice, but one that should be acknowledged as a policy choice rather than presented as the only ethically coherent outcome.
The Board resolved the tension between the Allegation-Adjudication Distinction and the Faithful Agent Obligation by treating adjudication status as a threshold gate rather than a balancing factor. Under this resolution, the Faithful Agent Obligation does not independently compel disclosure of information that has not been substantiated through a formal proceeding, even when that information is materially relevant to the current engagement. The practical effect is that the Faithful Agent Obligation is subordinated to the Allegation-Adjudication Distinction whenever the underlying information consists solely of an unproven allegation. This prioritization reflects a structural judgment that premature disclosure of unresolved complaints would expose engineers to reputational harm disproportionate to the informational benefit provided to clients, and that the integrity of the adjudicative process itself is a value the Code implicitly protects. However, this resolution leaves unaddressed the scenario where the allegation is domain-specific and directly mirrors the services being rendered to the current client, a factual configuration present in this case that the Board did not treat as independently dispositive. The case therefore teaches that the Faithful Agent Obligation has a ceiling defined by allegation status, but does not clarify whether domain-specific similarity to current services constitutes an exception to that ceiling.
What if Engineer A had proactively provided Client B with limited background information about the pending complaint - framing it as an unresolved allegation while affirming confidence in the competence being applied to Client B's project - would this intermediate disclosure approach have satisfied both the allegation-adjudication distinction and the faithful agent obligation simultaneously, representing a superior ethical path that the Board's binary framing of the question obscured?
The Board's conclusion that non-disclosure was ethical implicitly treats the ethical question as binary - either Engineer A was obligated to disclose the complaint in full, or he was not obligated to disclose at all. This framing obscures a viable intermediate path that the Board's own prudential recommendation gestures toward without fully articulating. Engineer A possessed the capability to provide Client B with limited background information about the pending complaint - framing it as an unresolved allegation, affirming his confidence in the competence being applied to Client B's project, and preserving Client B's ability to make an informed decision about the engagement - without conceding the validity of Client C's allegation or prejudging the outcome of the state board's review. This intermediate disclosure approach would have simultaneously honored the allegation-adjudication distinction (by not treating the complaint as an adjudicated finding) and satisfied the faithful agent obligation (by ensuring Client B had access to information material to the engagement). The fact that Client B later expressed that trust was undermined when he learned of the complaint through a third party demonstrates that the relational harm Engineer A sought to avoid through silence was not avoided - it was merely deferred and compounded by the manner of discovery. The Board's prudential recommendation that disclosure would have been the wiser course implicitly acknowledges this intermediate path as superior, but the Board stops short of recognizing that the availability of a clearly superior ethical path - one that satisfies multiple competing obligations simultaneously - itself constitutes evidence that Engineer A's chosen course of pure non-disclosure, while not categorically unethical, was ethically suboptimal in a manner that the Board's binary framing of the question obscures.
The intermediate disclosure approach - in which Engineer A proactively provides Client B with limited background information about the pending complaint, framing it as an unresolved allegation while affirming confidence in the competence being applied to Client B's project - represents a superior ethical path that the Board's binary framing of the question obscures. This approach would have simultaneously honored the allegation-adjudication distinction (by making clear that the complaint is unproven and contested), satisfied the faithful agent obligation (by ensuring Client B had access to relevant information), and preserved the trust relationship (by ensuring Client B received the information from Engineer A rather than a third party). The Board's analysis treats the question as a binary choice between full disclosure and complete silence, but the ethical landscape between those poles is rich and practically navigable. Engineer A's failure to consider or adopt this intermediate approach represents a missed opportunity to reconcile the competing principles at stake. The Board's prudential recommendation implicitly endorses something like this intermediate approach without naming it, and a more complete analysis would have articulated it explicitly as the ethically optimal course.
If Engineer A had voluntarily disclosed the pending ethics complaint to Client B at the time it was received from the state licensing board, would Client B's trust have been preserved rather than damaged, and would that outcome have changed the Board's prudential recommendation that disclosure - while not required - would have been the wiser course of action?
The tension between Informed Decision-Making Enablement and the Privacy Right versus Material Omission principle was resolved in favor of the engineer's privacy interest in unresolved allegations, but only partially and conditionally. The Board's simultaneous conclusion that non-disclosure was ethical and its prudential recommendation that disclosure would have been wiser reveals that these two principles were not fully reconciled - they were instead assigned to different normative registers. The Privacy Right versus Material Omission principle governed the ethical compliance question, while Informed Decision-Making Enablement was relegated to the domain of prudential wisdom. This bifurcation is analytically significant because it implies that the NSPE Code's honesty and non-deception provisions, specifically Section III.3.a, do not treat silence about an unresolved allegation as a material omission sufficient to constitute deception, even when the client would have found the information decision-relevant. The case therefore teaches that materiality under Section III.3.a is not determined solely by the client's subjective interest in the information, but is filtered through the allegation-adjudication threshold. A pending, unproven complaint does not achieve the status of a 'material fact' for disclosure purposes regardless of how relevant the client would consider it. This principle prioritization, however, creates a structural gap: the Code as interpreted provides no mechanism for clients to obtain complaint information that is simultaneously unproven and highly relevant to their engagement, leaving them dependent on third-party discovery as the only practical pathway to that information.
What if the ethics complaint filed by Client C had involved services in a completely different engineering domain from those being performed for Client B - would the Board's conclusion of ethical non-disclosure have been more clearly justified, and does the domain similarity in the actual case represent the critical variable that most strains the Board's reasoning?
The Board's conclusion that non-disclosure was ethical rests on the allegation-adjudication distinction - the principle that an unproven complaint does not carry the evidentiary weight necessary to compel disclosure. However, this distinction, while defensible as a general rule, is strained in the present case by a critical contextual variable: the services at issue in Client C's competence complaint are similar in nature to those Engineer A is actively performing for Client B. This domain similarity elevates the materiality of the complaint beyond what would be expected of a generic or unrelated allegation. A pending competence challenge in an identical or closely analogous service domain is not merely background noise about Engineer A's professional history - it is directly probative of the quality and reliability of the very work Client B is currently receiving. The Board's reasoning does not adequately grapple with this similarity as an independent variable that could shift the disclosure calculus. Even accepting that an adjudicated finding would be required before disclosure becomes obligatory in the general case, the domain-specific relevance of Client C's complaint creates a heightened materiality threshold that the allegation-adjudication distinction alone cannot fully neutralize. A more complete analysis would have required the Board to address whether the similar-services context independently amplifies Engineer A's faithful agent obligation toward Client B, and whether that amplification pushes the disclosure question closer to the boundary of ethical requirement rather than mere prudential recommendation.
The domain similarity between Client C's competence allegation and the services Engineer A is actively performing for Client B materially heightens the relevance of the complaint to Client B's engagement. A generic pending complaint in an unrelated engineering discipline would carry minimal informational weight for Client B; by contrast, a competence challenge arising from services nearly identical in nature to those currently being rendered directly implicates the quality and reliability of what Client B is receiving. This similarity does not automatically convert a non-disclosure into an ethical violation under the Board's allegation-adjudication framework, but it does represent the critical variable that most strains the Board's conclusion. The domain-specific relevance of the complaint means that Client B's ability to make an informed decision about the engagement is more directly affected than it would be in a dissimilar-services scenario. Accordingly, the similar-services context independently amplifies the prudential case for disclosure and brings the non-disclosure closer to the boundary of the faithful agent obligation under Section III.3.a, even if it does not cross that boundary under the Board's chosen threshold.
The counterfactual scenario in which the ethics complaint involved services in a completely different engineering domain from those being performed for Client B would have made the Board's conclusion of ethical non-disclosure substantially more defensible. In that scenario, the complaint's relevance to Client B's engagement would be attenuated - a competence challenge in, say, structural engineering would carry little informational weight for a client receiving CPM scheduling services. The domain similarity in the actual case is therefore the critical variable that most strains the Board's reasoning, because it transforms the complaint from a background professional matter into a directly relevant signal about the quality of services Client B is currently receiving. This analysis suggests that the Board's allegation-adjudication distinction, while sound as a general principle, requires a domain-relevance modifier: the closer the subject matter of the pending complaint to the services being rendered to the current client, the stronger the case for disclosure even at the allegation stage. The Board's failure to articulate this modifier leaves its conclusion underspecified and potentially misleading as precedent for cases where domain similarity is even more pronounced.
What if Client B had explicitly asked Engineer A at the outset of the engagement whether any ethics complaints or competence challenges had ever been filed against Engineer A - would Engineer A's obligation to disclose the pending complaint have shifted from a matter of prudential judgment to a categorical ethical requirement under the honesty and non-deception provisions of the NSPE Code, and what does this scenario reveal about the adequacy of passive non-disclosure as an ethical standard?
The Board's conclusion that non-disclosure was ethical implicitly treats the ethical question as binary - either Engineer A was obligated to disclose the complaint in full, or he was not obligated to disclose at all. This framing obscures a viable intermediate path that the Board's own prudential recommendation gestures toward without fully articulating. Engineer A possessed the capability to provide Client B with limited background information about the pending complaint - framing it as an unresolved allegation, affirming his confidence in the competence being applied to Client B's project, and preserving Client B's ability to make an informed decision about the engagement - without conceding the validity of Client C's allegation or prejudging the outcome of the state board's review. This intermediate disclosure approach would have simultaneously honored the allegation-adjudication distinction (by not treating the complaint as an adjudicated finding) and satisfied the faithful agent obligation (by ensuring Client B had access to information material to the engagement). The fact that Client B later expressed that trust was undermined when he learned of the complaint through a third party demonstrates that the relational harm Engineer A sought to avoid through silence was not avoided - it was merely deferred and compounded by the manner of discovery. The Board's prudential recommendation that disclosure would have been the wiser course implicitly acknowledges this intermediate path as superior, but the Board stops short of recognizing that the availability of a clearly superior ethical path - one that satisfies multiple competing obligations simultaneously - itself constitutes evidence that Engineer A's chosen course of pure non-disclosure, while not categorically unethical, was ethically suboptimal in a manner that the Board's binary framing of the question obscures.
The Board's conclusion that non-disclosure was ethical does not resolve - and in fact creates - an internal tension between the allegation-adjudication distinction and the valence-neutral standard for deception articulated in the Board's own reasoning. The valence-neutral standard holds that omissions of negative information can be just as deceptive as omissions of positive information, and that the ethical character of an omission is not determined by whether the withheld information is favorable or unfavorable to the omitting party. Applying this standard to Engineer A's conduct, the question becomes whether Engineer A's silence about the pending competence complaint constituted a misleading omission under Section III.3.a - not because the complaint was adjudicated, but because a reasonable client in Client B's position would regard the existence of a pending competence challenge involving similar services as information material to the decision to continue the engagement. The Board's conclusion that no disclosure obligation arose effectively treats the allegation-adjudication distinction as a categorical override of the valence-neutral standard, but this override is not explicitly justified in the Board's reasoning. A more rigorous analysis would have required the Board to explain why the allegation-adjudication distinction takes precedence over the valence-neutral deception standard when the omitted information is directly relevant to the current engagement - or alternatively, to acknowledge that the two principles exist in genuine tension that the present case does not fully resolve. Furthermore, the scenario in which Client B explicitly asks Engineer A about pending complaints at the outset of the engagement reveals the clearest expression of this tension: in that scenario, Engineer A's silence or evasion would almost certainly constitute a violation of the honesty and non-deception provisions of the NSPE Code, demonstrating that passive non-disclosure is an ethically adequate standard only in the absence of direct inquiry, and that the adequacy of that standard is more fragile than the Board's conclusion suggests.
The counterfactual scenario in which Client B explicitly asked Engineer A at the outset of the engagement whether any ethics complaints or competence challenges had been filed against Engineer A reveals a critical asymmetry in the Board's framework: passive non-disclosure and active deception in response to a direct inquiry are treated as categorically different ethical acts, and rightly so. Had Client B posed such a direct question and Engineer A denied or concealed the existence of the pending complaint, that conduct would constitute a clear violation of the honesty and non-deception provisions of the Code, regardless of the complaint's adjudication status. This scenario demonstrates that the Board's conclusion of ethical non-disclosure is contingent on the absence of a direct inquiry - a contingency the Board does not make explicit. The adequacy of passive non-disclosure as an ethical standard is therefore limited to situations where the client has not affirmatively sought the information. This analysis also reveals that engineers in Engineer A's position bear a heightened obligation to ensure that their silence does not function as an implicit representation that no such complaints exist, particularly when clients might reasonably assume that a retained professional would volunteer such information.
Decisions & Arguments
View ExtractionCausal-Normative Links 7
- Engineer_A_Competence_Self-Assessment_Obligation_Under_Pending_Complaint
- Engineer_A_Faithful_Agent_Transparency_Obligation_Toward_Client_B
- Engineer A Faithful Agent Obligation Toward Client B Complaint Context
- Engineer_A_Faithful_Agent_Transparency_Obligation_Toward_Client_B
- Engineer A Faithful Agent Obligation Toward Client B Complaint Context
- Engineer_A_Competence_Self-Assessment_Obligation_Under_Pending_Complaint
- Engineer A Pending Competence Complaint Disclosure Obligation to Client B
- Pending Competence Complaint Disclosure Obligation to Current Client
- Engineer A Pending Complaint Limited Background Information Provision Client B
- Engineer_A_Allegation-Adjudication_Distinction_Invocation_in_Non-Disclosure_Decision
- Engineer A Valence-Neutral Misleading Omission Non-Disclosure Pending Complaint
- Engineer A Allegation Non-Equivalence Disclosure Calibration Client B
- Pending Competence Complaint Disclosure Obligation Negated by Allegation Status
- Engineer A Pending Competence Complaint Disclosure Obligation to Client B
- Engineer A Pending Complaint Limited Background Information Provision Client B
- Engineer_A_Faithful_Agent_Transparency_Obligation_Toward_Client_B
- Pending Competence Complaint Disclosure Obligation to Current Client
- Engineer A Faithful Agent Obligation Toward Client B Complaint Context
- Engineer_A_Competence_Self-Assessment_Obligation_Under_Pending_Complaint
- Engineer_A_Faithful_Agent_Transparency_Obligation_Toward_Client_B
- Engineer A Pending Competence Complaint Disclosure Obligation to Client B
- Engineer A Pending Allegation Prudential Disclosure Weighing Client B
- Engineer B Post-Termination Notice Brochure Personnel Disclosure Case 83-1 Notice Period
- Post-Termination Notice Brochure Personnel Disclosure Obligation
- Engineer_B_Truthful_Non-Deceptive_Advertising_Obligation_Regarding_Personnel
- Engineer B Key Employee Brochure Listing Prospective Client Reliance Non-Misleading Case 83-1
- Engineer B Truthful Non-Deceptive Advertising Brochure Distribution Case 83-1
- Pertinent Fact Dual-Element Misrepresentation Test Compliance Obligation
- Key Employee Brochure Listing Prospective Client Reliance Non-Misleading Obligation
- Non-Key-Employee Departed Engineer Brochure Listing Contextual Permissibility Obligation
- Engineer Z Non-Key-Employee Departed Engineer Brochure Listing Case 90-4
- Engineer_Z_Firm_Brochure_Post-Departure_Personnel_Listing_Correction_Obligation_Case_90-4
- Firm Principal Post-Departure Personnel Listing Correction Obligation
- Post-Actual-Departure Brochure Personnel Listing Prohibition Obligation
- Engineer_B_Firm_Brochure_Post-Departure_Personnel_Listing_Correction_Obligation
- Engineer_B_Truthful_Non-Deceptive_Advertising_Obligation_Regarding_Personnel
- Engineer B Key Employee Brochure Listing Prospective Client Reliance Non-Misleading Case 83-1
- Engineer B Truthful Non-Deceptive Advertising Brochure Distribution Case 83-1
- Engineer B Pertinent Fact Dual-Element Test Violation Case 83-1 Post-Termination
- Post-Actual-Departure Brochure Personnel Listing Prohibition Obligation
- Pertinent Fact Dual-Element Misrepresentation Test Compliance Obligation
- Firm Principal Post-Departure Personnel Listing Correction Obligation
- Key Employee Brochure Listing Prospective Client Reliance Non-Misleading Obligation
- Engineer B Post-Actual-Departure Brochure Listing Prohibition Case 83-1
Decision Points 6
Should Engineer A disclose the pending ethics complaint to Client B, or withhold it on the basis that an unproven allegation does not compel disclosure?
The Faithful Agent Obligation requires Engineer A to act in Client B's best interest and ensure Client B has information material to the engagement. The Allegation-Adjudication Distinction holds that a complaint is a mere allegation — not a finding of fact or conclusion of law — and does not automatically compel disclosure. The Pending Competence Complaint Disclosure Obligation recognizes that the complaint bears on Client B's ability to make an informed decision about the engagement.
Uncertainty is created by the domain similarity between Client C's complaint and the services being rendered to Client B: when the allegation directly concerns competence in the very type of work being performed, the allegation-adjudication distinction loses some of its insulating force. Additionally, the foreseeable relational harm of third-party discovery — which materialized — suggests that the practical case for disclosure was stronger than the Board's framework fully acknowledges.
Engineer A receives a pending ethics complaint from Client C alleging incompetence in services similar in nature to those currently being performed for Client B. Engineer A decides not to notify Client B. Client B later learns of the complaint through a third party and expresses that trust has been undermined and that Engineer A should have disclosed the matter.
Should Engineer A treat the domain similarity between Client C's complaint and Client B's active services as a materiality-elevating factor that independently strengthens the case for disclosure, or apply the allegation-adjudication distinction uniformly regardless of subject-matter overlap?
The Similar-Services Disclosure Heightening Constraint establishes that domain overlap between a pending complaint and active services heightens — though does not automatically compel — the prudential case for disclosure. The Faithful Agent Transparency Obligation requires Engineer A to be transparent about material professional circumstances affecting Client B's ability to make informed decisions. The Allegation-Adjudication Distinction holds that adjudication status governs disclosure threshold regardless of subject-matter relevance.
Uncertainty arises because no codified rule specifies when subject-matter similarity between a complaint's allegations and an active engagement is sufficient to override the allegation-adjudication distinction. The Board did not treat domain similarity as independently dispositive, leaving open whether similar-services overlap constitutes a separate materiality trigger or merely a prudential amplifier within the existing framework.
Client C's ethics complaint alleges incompetence in services that are similar in nature to the design services and CPM scheduling Engineer A is actively performing for Client B. The overlap between the subject matter of the complaint and the active engagement means the complaint is directly probative of the quality of work Client B is currently receiving, not merely a background professional matter.
Should Engineer A adopt an intermediate disclosure approach — providing Client B with limited, dispassionate background information framing the complaint as an unresolved allegation — or treat the allegation-adjudication distinction as a complete shield justifying total silence?
The Prudential Disclosure Recommendation advises that voluntary disclosure of limited background information would have been the wiser course. The Faithful Agent Obligation requires Engineer A to act in Client B's best interest, including enabling informed decision-making. The Allegation-Adjudication Distinction holds that an unproven complaint does not compel full disclosure. The Pending Complaint Voluntary Background Disclosure Opportunity State recognizes that a professional not compelled to disclose may nonetheless have a prudential opportunity to provide limited, dispassionate context.
Uncertainty arises because the Board's binary framing — either full disclosure or complete silence — obscures the intermediate path. If a clearly superior ethical path exists that satisfies multiple competing obligations simultaneously, the availability of that path itself constitutes evidence that Engineer A's chosen course of pure non-disclosure, while not categorically unethical, was ethically suboptimal. The Board's prudential recommendation may implicitly acknowledge a sub-threshold ethical deficiency without characterizing it as a code violation.
Engineer A chose complete silence about the pending complaint. Client B subsequently discovered the complaint through a third party, expressed that trust was undermined, and stated that Engineer A should have disclosed the matter. The Board recommended that Engineer A should have weighed providing limited background information in a dispassionate and nonprejudicial manner, implicitly endorsing an intermediate path without naming it.
Should Engineer A conduct an honest self-assessment of competence in light of the pending complaint and take appropriate action if that assessment reveals genuine doubt, or continue rendering services to Client B without independently evaluating whether the complaint raises legitimate competence concerns?
The Professional Competence Standard requires engineers to perform services only in areas of their competence. The Faithful Agent Obligation requires Engineer A to act in Client B's best interest, which includes ensuring that the services being rendered meet the required standard of care. The Allegation-Adjudication Distinction addresses whether the complaint must be disclosed, but does not address whether the complaint should trigger an independent competence self-assessment. The Engineer A Competence Self-Assessment Obligation establishes that the complaint functions as a trigger for self-examination rather than solely as a potential disclosure event.
Uncertainty arises because the Board's analysis focuses entirely on the disclosure question and does not address the competence self-assessment dimension. If Engineer A harbored genuine competence doubts that were not surfaced, the non-disclosure may have been ethically permissible with respect to the complaint's existence but independently impermissible under the competence provisions of the Code. The compound ethical failure doctrine suggests that silence following an unexamined competence concern is more serious than silence following a self-assessment that confirms adequate competence.
Client C alleges that Engineer A lacked the competence to perform services similar in nature to those currently being performed for Client B. Engineer A receives notice of the complaint and continues rendering services to Client B without any documented self-assessment of whether the competence concerns raised by Client C have substantive merit. The Board's analysis does not address whether Engineer A evaluated his own competence in light of the complaint.
Should Engineer A treat the honesty and non-deception obligation as requiring disclosure of the pending complaint because its omission creates a false impression of an unblemished professional record, or apply the allegation-adjudication distinction as a categorical override of the valence-neutral deception standard?
The Valence-Neutral Misleading Information Standard establishes that omissions of negative information are evaluated by the same standard as omissions of positive information — whether the omission creates a false impression. The Honesty and Non-Deception Obligation requires engineers to avoid acts that might be viewed as misleading and deceptive. The Allegation-Adjudication Distinction holds that an unproven complaint does not carry the moral weight of an adjudicated finding and therefore does not constitute a 'material fact' for disclosure purposes. The Engineer A Valence-Neutral Misleading Omission obligation requires Engineer A to apply the same honesty standard to the pending complaint as to any other material information.
Uncertainty arises because the Board did not explicitly justify why the allegation-adjudication distinction takes precedence over the valence-neutral deception standard when the omitted information is directly relevant to the current engagement. If materiality is assessed from Client B's perspective — as a reasonable client who would want to know about a pending competence challenge involving similar services — the omission is material regardless of adjudication status. The scenario in which Client B explicitly asks Engineer A about pending complaints at the outset of the engagement reveals the clearest expression of this tension: in that scenario, silence or evasion would almost certainly constitute a violation of the honesty provisions regardless of adjudication status.
Engineer A remains silent about the pending competence complaint while continuing to render services to Client B. The Valence-Neutral Standard holds that the ethical character of an omission is determined by whether it creates a false impression, not by whether the withheld information is favorable or unfavorable. Client B, upon learning of the complaint through a third party, expressed that trust was undermined — suggesting that Client B regarded the information as material and would have expected it to be volunteered.
Should Engineer A treat the allegation-adjudication distinction as a binary gate requiring no disclosure until a final adverse finding is issued, or recognize a graduated disclosure obligation that strengthens as the complaint advances through formal procedural milestones toward adjudication?
The Allegation-Adjudication Distinction holds that a complaint is a mere allegation that does not amount to a finding of fact or conclusion of law, and therefore does not compel disclosure. The Faithful Agent Obligation requires Engineer A to act in Client B's best interest, including ensuring Client B has information material to the engagement. The Honesty and Non-Deception Obligation requires engineers to avoid misleading conduct. A graduated model would recognize that probable cause determinations, formal hearings, and adverse findings each represent qualitatively different levels of substantiation that progressively strengthen the disclosure case.
Uncertainty arises because the Board did not articulate a graduated model or specify the procedural threshold at which disclosure becomes obligatory, leaving practitioners without clear guidance for cases where the complaint has advanced beyond initial filing but has not yet produced a final adverse finding. The absence of a codified threshold creates a structural gap in which engineers must navigate disclosure decisions without clear benchmarks, potentially leading to inconsistent outcomes across similar cases.
Engineer A receives notice of a pending ethics complaint at the initial filing stage — before any probable cause determination, formal hearing, or adverse finding. The complaint has not been adjudicated. Engineer A must determine whether the current procedural stage of the complaint is sufficient to trigger any disclosure obligation, or whether silence is appropriate until a formal adverse finding is issued.
Event Timeline
View ExtractionCausal Flow
- Prepare Plans and CPM Schedule Decide Against Disclosing Ethics Complaint
- Decide Against Disclosing Ethics Complaint Continue_Rendering_Services_Post-Complaint
- Continue_Rendering_Services_Post-Complaint Engineer_B_Distributes_Brochure_Pre-Termination
- Engineer_B_Distributes_Brochure_Pre-Termination Engineer_B_Distributes_Brochure_Post-Termination
- Engineer_B_Distributes_Brochure_Post-Termination Engineer Z Continues Listing Departed Engineer X
- Engineer Z Continues Listing Departed Engineer X Accept Client B Engagement
- Accept Client B Engagement Ethics Complaint Filed
Opening Context
View ExtractionYou are Engineer A, currently under contract with Client B to perform design services and provide a Critical Path Method (CPM) schedule for a manufacturing facility. You have prepared the plans, specifications, and CPM schedule as part of that engagement. The state board of professional engineers has recently contacted you regarding an ethics complaint filed by Client C, who alleges you lacked the competence to perform services on a prior project similar in nature to the work you are now doing for Client B. Client B is unaware of this complaint. The decisions ahead concern how you handle your obligations to Client B given this pending matter.
Characters (6)
A firm principal who continued listing a departing engineer in firm brochures during her notice period, though the Board found this permissible given the limited and non-prominent nature of her representation.
- Motivated by a desire to maintain the firm's perceived technical breadth during a transitional staffing period, Engineer Z operated in a gray area but avoided the more egregious misrepresentation found in Case 83-1.
- Driven by competitive self-interest and a desire to win contracts, Engineer B prioritized short-term business gain over ethical transparency, likely rationalizing the misrepresentation as a minor administrative oversight.
A specialized hydrology engineer who gave proper notice of departure but found herself still listed in firm materials during her two-week notice period without explicit disclosure of her impending exit.
- Motivated by professional honesty and a clean transition to her new employer, Engineer X's primary interest was in ensuring her credentials and expertise were accurately and fairly represented during the departure process.
- Likely motivated by professional integrity and concern for his own reputation, Engineer A had an interest in ensuring his credentials were not used to mislead prospective clients after his employment ended.
Continued to distribute brochures identifying Engineer X as an employee of Firm Y after Engineer X gave two weeks notice of departure. Board found this not unethical given that Engineer X was not highlighted as a 'key employee' and the firm's hydrology work was not a significant percentage of its practice.
One of few engineers in Firm Y with hydrology expertise; gave two weeks notice of intent to move to another firm, after which Engineer Z continued to list her in firm brochures and resumes.
Current client receiving engineering services from Engineer A while Engineer A is subject to a pending ethics complaint filed by Client C. The Board analyzed whether Engineer A owed Client B a disclosure obligation regarding the complaint, concluding that prudential (not mandatory) disclosure of background information was advisable.
Prospective clients who read and relied upon engineering firm brochures listing personnel qualifications, reasonably assuming that named individuals (especially 'key employees') were currently available to the firm, and who were potentially misled by continued listing of departed engineers.
Tension between Pending Competence Complaint Disclosure Obligation to Current Client and Allegation-Adjudication Distinction Applied to Complaint Non-Disclosure
Tension between Pending Competence Allegation Similar-Services Disclosure Heightening Constraint and Pending Competence Complaint Disclosure Obligation Negated by Allegation Status
Tension between Faithful Agent Obligation Invoked by Engineer A Toward Client B and Allegation-Adjudication Distinction Applied to Complaint Non-Disclosure
Tension between Engineer A Competence Self-Assessment Obligation Under Pending Complaint and Allegation-Adjudication Distinction Applied to Complaint Non-Disclosure
Tension between Honesty and Non-Deception Obligation Invoked as Baseline Framework and Valence-Neutral Misleading Information Standard in Professional Disclosure
Tension between Allegation-Adjudication Distinction Applied to Complaint Non-Disclosure and Pending Competence Complaint Disclosure Obligation to Current Client
Engineer A's duty to act as a faithful agent and protect Client B's interests arguably requires disclosing a pending competence complaint that directly bears on the quality of services being rendered. However, the allegation-vs-adjudication constraint holds that an unresolved, unproven complaint does not rise to the level of a material fact requiring mandatory disclosure. Fulfilling the disclosure obligation risks prejudicing Engineer A based on unproven allegations; suppressing it risks leaving Client B uninformed about a potentially material professional risk. The dilemma is genuine because both paths carry ethical costs: disclosure may violate fairness to the accused engineer, while non-disclosure may compromise the client's informed consent.
The faithful agent obligation demands that Engineer A prioritize Client B's interests, which could include proactively surfacing any information that might affect the client's confidence in or reliance on the engineer's competence. The privacy-right constraint, however, recognizes that an engineer retains a legitimate interest in not having unresolved, potentially unfounded allegations broadcast to clients, since doing so could cause irreparable reputational harm before any adjudication occurs. These two principles pull in opposite directions: full fidelity to the client's informational interests collides with the engineer's right not to have private, unresolved professional proceedings used against them prematurely.
There is an obligation to provide at least limited background information to Client B so that the client is not entirely in the dark about circumstances that could affect the professional relationship. Yet the prudential constraint cautions that volunteering background information about a pending complaint — even in a limited, contextualized form — risks framing an unresolved allegation in ways that are either self-serving (if minimized) or unduly alarming (if fully disclosed). The tension is between the duty to inform and the practical constraint that any partial disclosure may itself be misleading or strategically distorted, making it difficult to satisfy the honesty norm while also respecting the allegation-adjudication boundary.
Opening States (10)
Key Takeaways
- The allegation-adjudication distinction creates a genuine ethical stalemate where neither full disclosure nor complete silence fully satisfies competing professional obligations to clients and to fair process.
- When an engineer is engaged for services similar to those underlying a pending competence complaint, the faithful agent duty to the current client intensifies the disclosure pressure beyond what baseline professional ethics alone would require.
- An intermediate disclosure approach — acknowledging the complaint's existence while contextualizing its unresolved status — represents a pragmatic but inherently unstable resolution that satisfies no single principle completely.