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 chainNode Types & Relationships
→ Question answered by Conclusion
→ Provision applies to Entity
NSPE Code Provisions Referenced
View ExtractionII.5. II.5.
Full Text:
Engineers shall avoid deceptive acts.
Applies To:
III.8.a. III.8.a.
Full Text:
Engineers shall conform with state registration laws in the practice of engineering.
Applies To:
III.9.a. III.9.a.
Full Text:
Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments.
Applies To:
II.5.a. II.5.a.
Full Text:
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.
Relevant Case Excerpts:
"Under the NSPE Code of Ethics, did this constitute “misrepresentation…of qualifications” as referenced in II.5.a? That might be dependent upon how noticeable the “in previous employment” description was in the body of the proposal."
Confidence: 95.0%
Applies To:
III.7. III.7.
Full Text:
Engineers shall not attempt to injure, maliciously or falsely, directly or indirectly, the professional reputation, prospects, practice, or employment of other engineers. Engineers who believe others are guilty of unethical or illegal practice shall present such information to the proper authority for action.
Applies To:
III.9. III.9.
Full Text:
Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.
Relevant Case Excerpts:
"With respect to giving credit to proprietary interests as referenced in Professional Obligation III.9, Engineer B’s previous projects were not technically proprietary and Engineer B gave credit to both the previous firm and the clients."
Confidence: 95.0%
Applies To:
Cited Precedent Cases
View ExtractionBER Case 76-4 supporting linked
Principle Established:
Engineers have an obligation to report observations or findings of potential violations or harm to the applicable regulatory authority, even when a client has terminated the contract and requested silence.
Citation Context:
The Board cited this case to establish the precedent that engineers have an obligation to report their findings to applicable regulatory authorities, supporting the discussion of Engineer A's reporting obligations.
Relevant Excerpts:
"BER Case 76-4 addressed the duty to report likely environmental damage to appropriate regulatory authorities. Engineer Doe was retained by an industry to evaluate whether a proposed change in their manufacturing process would result in meeting minimum water quality standards."
"The BER concluded that Doe had an obligation to report Doe's observations to the applicable regulatory authority."
BER Case 02-11 supporting linked
Principle Established:
Engineers have a clear obligation to report information on misconduct to the engineering licensing board; while a signed complaint is preferable, an anonymous complaint is better than no complaint at all and can be ethical.
Citation Context:
The Board cited this case to reinforce that engineers have a clear obligation to report misconduct to engineering licensing boards, and to address the manner in which such reports may be made.
Relevant Excerpts:
"In BER Case 02-11, Engineer A had provided an anonymous complaint to the engineering licensing board regarding the misconduct of Engineer B. The BER was tasked with evaluating whether filing the complaint anonymously was unethical."
"The BER concluded that Engineer A had a clear obligation to report information on misconduct to the engineering licensing board. On the matter of an anonymous complaint, the BER considered that a signed complaint would have been better to facilitate the licensing board's investigation, and fairer to the complainant, but concluded in this case that an anonymous letter was better than no letter at all and was ethical."
Questions & Conclusions
View ExtractionQuestion 1 Board Question
Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q?
While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension introduced by Engineer A's status as a direct commercial competitor of XYZ Engineers. Both states' licensing rules impose a mandatory reporting obligation on licensees who have knowledge or reason to believe a violation has occurred, and the NSPE Code similarly supports reporting of unethical or illegal practice. However, the mandatory character of this obligation does not eliminate the ethical significance of the reporter's motivation. From a virtue ethics perspective, the legitimacy of Engineer A's reporting action depends in part on whether it was motivated by genuine concern for client protection and professional integrity rather than competitive self-interest. The Board's analysis would have been more complete had it acknowledged this tension and clarified that the mandatory reporting obligation remains valid and must be fulfilled regardless of the reporter's competitive position - but that Engineer A should be transparent about the competitive relationship when filing the report, and should confine the report strictly to documented rule violations rather than using the reporting mechanism to cast broader reputational doubt on XYZ Engineers. This framing preserves the integrity of the licensing enforcement system while acknowledging that competitive motivation, though it does not void the reporting duty, is an ethically relevant factor that the reporting engineer should consciously examine.
The Board's analysis of Engineer A's reporting obligation appropriately distinguished between State Q and State Z based on the differing specificity of each state's licensing rules, concluding that a violation was established in State Z but not in State Q. This jurisdiction-differentiated outcome carries an important practical implication that the Board did not make explicit: Engineer A's obligation to report to the State Z board is mandatory under both states' rules once Engineer A has knowledge or reason to believe a violation occurred, and that threshold was met by Engineer A's own review of the State Z rules. The Board's reasoning therefore implicitly confirms that Engineer A's decision to report to the State Z board was not merely permissible but obligatory - and that declining to report after identifying a clear rule violation would itself have constituted a breach of Engineer A's professional obligations. Conversely, the absence of a comparable violation under State Q's more permissive standard means that reporting to the State Q board would have been unsupported by the factual record and potentially inconsistent with Section III.7's prohibition on conduct that injures the professional reputation of another engineer without factual basis. This asymmetry - mandatory reporting in State Z, inappropriate reporting in State Q - illustrates that the reporting obligation is not a blanket duty triggered by competitive suspicion but a jurisdiction-specific, evidence-calibrated professional responsibility.
Question 2 Board Question
Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?
The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.
Question 3 Implicit
Does Engineer A's status as a direct competitor of XYZ Engineers create a conflict of interest that should have been disclosed or weighed before initiating any reporting action, and does that competitive motivation undermine the legitimacy or objectivity of the reporting obligation?
While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension introduced by Engineer A's status as a direct commercial competitor of XYZ Engineers. Both states' licensing rules impose a mandatory reporting obligation on licensees who have knowledge or reason to believe a violation has occurred, and the NSPE Code similarly supports reporting of unethical or illegal practice. However, the mandatory character of this obligation does not eliminate the ethical significance of the reporter's motivation. From a virtue ethics perspective, the legitimacy of Engineer A's reporting action depends in part on whether it was motivated by genuine concern for client protection and professional integrity rather than competitive self-interest. The Board's analysis would have been more complete had it acknowledged this tension and clarified that the mandatory reporting obligation remains valid and must be fulfilled regardless of the reporter's competitive position - but that Engineer A should be transparent about the competitive relationship when filing the report, and should confine the report strictly to documented rule violations rather than using the reporting mechanism to cast broader reputational doubt on XYZ Engineers. This framing preserves the integrity of the licensing enforcement system while acknowledging that competitive motivation, though it does not void the reporting duty, is an ethically relevant factor that the reporting engineer should consciously examine.
Engineer A's status as a direct competitor of XYZ Engineers does create a potential conflict of interest that warrants careful self-examination before initiating any reporting action. However, that competitive relationship does not nullify the legitimacy of the reporting obligation itself. The NSPE Code and the licensing rules of both states impose a mandatory reporting duty on any licensee who has knowledge or reason to believe a violation has occurred - the rules do not carve out an exception for competitors, nor do they require the reporting engineer to be a disinterested party. The competitive motivation is ethically relevant to the question of motivational integrity (see Q306), but it does not transform a genuine violation into a non-violation, nor does it relieve Engineer A of the duty to report. What the conflict of interest does require is that Engineer A act with scrupulous accuracy - neither overstating the violation nor selectively reporting only in jurisdictions where it benefits ABC Consultants competitively. The fact that Engineer A declined to report to the State Q board, where no clear rule violation was found, and reported only to the State Z board, where a specific rule was clearly breached, is consistent with good-faith application of the reporting obligation rather than weaponization of the licensing system. The conflict of interest concern is real but does not override the mandatory reporting duty when the underlying violation is genuine.
Question 4 Implicit
To what extent does XYZ Engineers bear institutional ethical responsibility for Engineer B's attribution practices in qualification proposals, and should the Board's analysis have separately evaluated the firm's culpability distinct from Engineer B's individual conduct?
The Board's finding that XYZ Engineers' practices were not unethical under the NSPE Code does not fully address the institutional dimension of the firm's responsibility. Engineer B is an individual licensee, but XYZ Engineers as a firm made the deliberate organizational decision to structure its qualifications proposals in the manner described. Section III.9 and Section III.9.a impose credit-attribution obligations that apply to the professional conduct of engineers, and when a firm systematically deploys a proposal format that concentrates attribution disclosure in a single prefatory location while allowing project-level descriptions to stand without attribution, the firm bears independent institutional responsibility for that structural choice. The Board's analysis focused primarily on Engineer B's individual conduct without separately evaluating whether XYZ Engineers, as the entity submitting the proposals and controlling their format, bore a distinct and potentially higher obligation to ensure that attribution was unambiguous at every level of the document. This omission is significant because it leaves open the question of whether firms can insulate themselves from ethical scrutiny by delegating attribution decisions to individual engineers while retaining control over proposal architecture.
The Board's analysis focused primarily on Engineer B's individual conduct and did not separately evaluate XYZ Engineers' institutional culpability. This omission is analytically significant. XYZ Engineers, as the firm that prepared, reviewed, and submitted the qualifications proposals, bears independent institutional responsibility for the attribution practices embedded in those documents. A firm that knowingly structures proposal documents in a way that places attribution notices only in prefatory sections - while allowing lengthy individual project descriptions to function without any attribution reminder - has made an organizational decision about disclosure architecture. That decision cannot be attributed solely to Engineer B. Under NSPE Code Section II.5.a, the prohibition against permitting misrepresentation of qualifications applies to the firm as well as the individual engineer. The Board's conclusion that XYZ Engineers' practices were not unethical under the NSPE Code is defensible for State Q purposes, but the analysis would have been more complete had it separately assessed whether XYZ Engineers, as an institution, exercised adequate supervisory oversight to ensure that the prefatory attribution notice was sufficient to prevent a misleading overall impression - particularly given that the State Z rules imposed a stricter standard that the firm's proposal structure failed to meet.
Question 5 Implicit
Does the prefatory notice of prior-employer attribution placed only at the beginning of Engineer B's individual qualification section - but not repeated within each project description - satisfy the spirit of honesty and transparency required by the NSPE Code of Ethics, even if it technically avoids outright falsification?
The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution notice existed somewhere in the proposal, the overall presentation did not constitute falsification or misrepresentation. However, this reasoning leaves unresolved a meaningful gap between technical compliance and the spirit of honesty required by Section II.5.a. A single prefatory notice in a lengthy qualifications document does not guarantee that evaluators - who routinely focus on individual project descriptions when scoring proposals - will connect that notice to each project listed. The Board's analysis would have been strengthened by acknowledging that the adequacy of a disclosure is a function not only of its presence but of its placement, prominence, and the realistic reading behavior of the intended audience. Government procurement evaluators using scoring rubrics are likely to assess individual project entries in isolation, meaning that a prefatory notice, however well-intentioned, may functionally fail to inform the evaluation of each project. The Board's silence on this point leaves a normative gap: the NSPE Code's honesty standard, as applied here, appears to treat disclosure as a binary condition rather than a graduated obligation calibrated to the risk of actual misunderstanding.
The prefatory attribution notice placed only at the beginning of Engineer B's individual qualification section - but not repeated within each project description - occupies an ethically ambiguous middle ground. It technically avoids outright falsification under the NSPE Code and satisfies the less specific State Q rules, but it does not fully satisfy the spirit of honesty and transparency that the Code's Section II.5.a demands. Sophisticated government procurement evaluators reading a lengthy qualifications proposal are most likely to focus their substantive evaluation on the detailed project descriptions themselves, not on a prefatory notice that may be several pages removed from the specific project narratives. A disclosure architecture that places the attribution caveat where it is least likely to be operationally noticed by evaluators - while allowing project descriptions to read as if they represent Engineer B's independent work product - creates a structural risk of misleading impressions even without any single false statement. The Board's conclusion that this practice was not unethical under the NSPE Code is defensible as a minimum compliance determination, but it should not be read as an endorsement of the practice as aspirationally ethical. The more transparent and professionally sound approach would have been to include attribution information adjacent to each project description, as State Z's rules explicitly require and as the intellectual integrity principle underlying Section III.9.a would support.
The most significant principle interaction in this case is the divergence between the Jurisdiction-Specific Ethics Compliance Obligation and the Honesty in Professional Representations principle as operationalized across two regulatory environments. The Board's analysis demonstrates that a single course of conduct - Engineer B's prefatory-only attribution practice - can simultaneously satisfy the NSPE Code's honesty standard and State Q's misrepresentation prohibition while violating State Z's more granular project-level attribution rule. This divergence reveals that the NSPE Code functions as a floor, not a ceiling, for professional honesty, and that jurisdiction-specific rules can impose materially higher standards without creating a logical contradiction with the Code. The practical teaching for multi-jurisdictional practitioners is that compliance with the NSPE Code does not guarantee compliance with all applicable state rules, and that the Jurisdiction-Specific Ethics Compliance Obligation requires independent rule-by-rule analysis in each state of practice. Firms operating across state lines must therefore treat the most demanding applicable jurisdiction's attribution standard as the operative benchmark for proposal preparation, not the most permissive one, if they wish to avoid selective non-compliance. This case also implicitly suggests that the NSPE Code's honesty provisions may benefit from revision to incorporate more explicit guidance on multi-jurisdictional attribution practices, closing the gap between the Code's general standard and the more specific requirements that some states have found necessary to protect clients and competitors alike.
Question 6 Implicit
What standard of client sophistication should be assumed when evaluating whether a proposal practice is misleading - are government procurement clients expected to read prefatory attribution notices carefully, and does that assumption affect the ethical analysis of Engineer B's disclosure approach?
The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution notice existed somewhere in the proposal, the overall presentation did not constitute falsification or misrepresentation. However, this reasoning leaves unresolved a meaningful gap between technical compliance and the spirit of honesty required by Section II.5.a. A single prefatory notice in a lengthy qualifications document does not guarantee that evaluators - who routinely focus on individual project descriptions when scoring proposals - will connect that notice to each project listed. The Board's analysis would have been strengthened by acknowledging that the adequacy of a disclosure is a function not only of its presence but of its placement, prominence, and the realistic reading behavior of the intended audience. Government procurement evaluators using scoring rubrics are likely to assess individual project entries in isolation, meaning that a prefatory notice, however well-intentioned, may functionally fail to inform the evaluation of each project. The Board's silence on this point leaves a normative gap: the NSPE Code's honesty standard, as applied here, appears to treat disclosure as a binary condition rather than a graduated obligation calibrated to the risk of actual misunderstanding.
Question 7 Principle Tension
Does the Transparency Principle invoked by XYZ Engineers' prefatory notice conflict with the Qualification Proposal Attribution Integrity principle, given that a single prefatory disclosure may create an appearance of transparency while still allowing individual project descriptions to function as misleading representations of Engineer B's independent authorship?
The Board resolved the tension between the Transparency Principle and Qualification Proposal Attribution Integrity by treating document-level disclosure as sufficient to satisfy the NSPE Code's honesty standard, even when that disclosure was not repeated at the project-description level where evaluators are most likely to focus. This resolution effectively privileges formal transparency - the existence of a prefatory notice - over functional transparency - the practical likelihood that a reader will connect that notice to each individual project description in a lengthy proposal body. The case thereby teaches that the NSPE Code's minimum compliance threshold for honesty in professional representations is calibrated to the document as a whole rather than to the reader's likely cognitive path through it. While this outcome avoids finding a violation under the Code, it leaves an unresolved gap between the aspirational standard of intellectual integrity in authorship, which would demand granular attribution, and the minimum standard the Board was willing to enforce. Practitioners and firms should treat this gap as a reason to adopt project-level attribution as a best practice rather than as a ceiling set by the Board's finding.
Question 8 Principle Tension
Does the Mandatory Competitor Misconduct Reporting Obligation conflict with the Fairness in Professional Competition principle when the engineer initiating the report stands to gain a competitive advantage from the investigation, and how should the ethics framework resolve the risk that a legitimate reporting duty becomes an instrument of competitive harm?
While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension introduced by Engineer A's status as a direct commercial competitor of XYZ Engineers. Both states' licensing rules impose a mandatory reporting obligation on licensees who have knowledge or reason to believe a violation has occurred, and the NSPE Code similarly supports reporting of unethical or illegal practice. However, the mandatory character of this obligation does not eliminate the ethical significance of the reporter's motivation. From a virtue ethics perspective, the legitimacy of Engineer A's reporting action depends in part on whether it was motivated by genuine concern for client protection and professional integrity rather than competitive self-interest. The Board's analysis would have been more complete had it acknowledged this tension and clarified that the mandatory reporting obligation remains valid and must be fulfilled regardless of the reporter's competitive position - but that Engineer A should be transparent about the competitive relationship when filing the report, and should confine the report strictly to documented rule violations rather than using the reporting mechanism to cast broader reputational doubt on XYZ Engineers. This framing preserves the integrity of the licensing enforcement system while acknowledging that competitive motivation, though it does not void the reporting duty, is an ethically relevant factor that the reporting engineer should consciously examine.
Engineer A's status as a direct competitor of XYZ Engineers does create a potential conflict of interest that warrants careful self-examination before initiating any reporting action. However, that competitive relationship does not nullify the legitimacy of the reporting obligation itself. The NSPE Code and the licensing rules of both states impose a mandatory reporting duty on any licensee who has knowledge or reason to believe a violation has occurred - the rules do not carve out an exception for competitors, nor do they require the reporting engineer to be a disinterested party. The competitive motivation is ethically relevant to the question of motivational integrity (see Q306), but it does not transform a genuine violation into a non-violation, nor does it relieve Engineer A of the duty to report. What the conflict of interest does require is that Engineer A act with scrupulous accuracy - neither overstating the violation nor selectively reporting only in jurisdictions where it benefits ABC Consultants competitively. The fact that Engineer A declined to report to the State Q board, where no clear rule violation was found, and reported only to the State Z board, where a specific rule was clearly breached, is consistent with good-faith application of the reporting obligation rather than weaponization of the licensing system. The conflict of interest concern is real but does not override the mandatory reporting duty when the underlying violation is genuine.
The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By affirming Engineer A's obligation to report to the State Z board without separately examining whether Engineer A's competitive motivation compromised the integrity of that reporting decision, the Board implicitly treated the reporting duty as categorical - that is, the obligation to report a genuine licensing violation is not diminished or tainted by the reporter's competitive interest in the outcome. This resolution is consistent with a deontological reading of the reporting obligation: if a violation exists, it must be reported regardless of the reporter's motivation. However, the Board's silence on the conflict-of-interest dimension leaves open the consequentialist concern that mandatory reporting rules, when exercised by direct competitors, can function as instruments of competitive harm even when the underlying violation is real. The case teaches that the NSPE Code and state licensing rules prioritize public protection and regulatory integrity over the risk of competitive misuse, but that this prioritization is most defensible when the reported violation is clear and material - as it was under State Z's specific attribution rules - rather than marginal or ambiguous.
Question 9 Principle Tension
Does the Jurisdiction-Specific Ethics Compliance Obligation conflict with the Honesty in Professional Representations principle when conduct that is insufficiently transparent to satisfy a stricter state rule (State Z) is simultaneously deemed not unethical under the NSPE Code - and does this divergence suggest that the NSPE Code's honesty standard is inadequately calibrated to multi-jurisdictional practice?
The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution notice existed somewhere in the proposal, the overall presentation did not constitute falsification or misrepresentation. However, this reasoning leaves unresolved a meaningful gap between technical compliance and the spirit of honesty required by Section II.5.a. A single prefatory notice in a lengthy qualifications document does not guarantee that evaluators - who routinely focus on individual project descriptions when scoring proposals - will connect that notice to each project listed. The Board's analysis would have been strengthened by acknowledging that the adequacy of a disclosure is a function not only of its presence but of its placement, prominence, and the realistic reading behavior of the intended audience. Government procurement evaluators using scoring rubrics are likely to assess individual project entries in isolation, meaning that a prefatory notice, however well-intentioned, may functionally fail to inform the evaluation of each project. The Board's silence on this point leaves a normative gap: the NSPE Code's honesty standard, as applied here, appears to treat disclosure as a binary condition rather than a graduated obligation calibrated to the risk of actual misunderstanding.
The Board's conclusion that Engineer B's practices were not unethical under the NSPE Code, when read alongside the finding that State Z's rules were violated, exposes a structural tension in the relationship between the NSPE Code and jurisdiction-specific licensing rules. The NSPE Code's honesty standard under Section II.5.a prohibits misrepresentation of qualifications but does not specify the granularity of attribution required in multi-employer proposal contexts. State Z's rules, by contrast, impose a precise project-level attribution requirement. The fact that conduct deemed compliant under the NSPE Code can simultaneously violate a state licensing rule suggests that the NSPE Code functions as a floor - not a ceiling - for professional honesty obligations, and that engineers practicing across multiple jurisdictions cannot rely solely on NSPE Code compliance to satisfy their full ethical and legal obligations. This divergence also raises a calibration concern: if the NSPE Code's honesty standard is consistently less demanding than jurisdiction-specific rules in states with detailed attribution requirements, the Code may systematically underprotect clients and competing firms in those jurisdictions. Engineers and firms operating in multi-state markets should therefore treat the most stringent applicable jurisdiction's rules as the operative standard for proposal preparation, rather than defaulting to the NSPE Code's more general formulation.
The divergence between State Q's general misrepresentation prohibition and State Z's granular project-level attribution requirement reveals that the NSPE Code's honesty standard under Section II.5.a is insufficiently calibrated to address the specific risks of cross-employer project credit attribution in multi-jurisdictional practice. The Code prohibits falsification and misrepresentation but does not specify the structural requirements for attribution disclosures - leaving engineers and firms free to adopt disclosure architectures that are technically non-false but practically obscure. State Z's legislature and licensing board identified this gap and addressed it through specific rules requiring attribution information to appear adjacent to each project listing. The NSPE Code has not made a parallel adjustment. This divergence suggests that the Code's honesty standard, while adequate for clear cases of falsification, is not adequate to govern the more subtle forms of misleading representation that arise from disclosure architecture choices. The Board's conclusion that XYZ Engineers' practice was not unethical under the NSPE Code, while correct as a matter of minimum compliance, should prompt the NSPE to consider whether the Code's attribution provisions need to be updated to reflect the more specific standards that state licensing bodies have found necessary to protect the integrity of the qualification proposal process.
The most significant principle interaction in this case is the divergence between the Jurisdiction-Specific Ethics Compliance Obligation and the Honesty in Professional Representations principle as operationalized across two regulatory environments. The Board's analysis demonstrates that a single course of conduct - Engineer B's prefatory-only attribution practice - can simultaneously satisfy the NSPE Code's honesty standard and State Q's misrepresentation prohibition while violating State Z's more granular project-level attribution rule. This divergence reveals that the NSPE Code functions as a floor, not a ceiling, for professional honesty, and that jurisdiction-specific rules can impose materially higher standards without creating a logical contradiction with the Code. The practical teaching for multi-jurisdictional practitioners is that compliance with the NSPE Code does not guarantee compliance with all applicable state rules, and that the Jurisdiction-Specific Ethics Compliance Obligation requires independent rule-by-rule analysis in each state of practice. Firms operating across state lines must therefore treat the most demanding applicable jurisdiction's attribution standard as the operative benchmark for proposal preparation, not the most permissive one, if they wish to avoid selective non-compliance. This case also implicitly suggests that the NSPE Code's honesty provisions may benefit from revision to incorporate more explicit guidance on multi-jurisdictional attribution practices, closing the gap between the Code's general standard and the more specific requirements that some states have found necessary to protect clients and competitors alike.
Question 10 Principle Tension
Does the Intellectual Integrity in Authorship principle - which would favor granular, project-level attribution of Engineer B's prior-employer work - conflict with the Proportionality Analysis applied to the State Q proposal, where the Board found the partial disclosure sufficient to avoid an ethical violation, and does this tension reveal an unresolved gap between aspirational professional norms and minimum compliance thresholds?
The Board's conclusion that XYZ Engineers' proposal practices were not unethical under the NSPE Code rests implicitly on a document-level reading of transparency: because the prefatory attribution notice existed somewhere in the proposal, the overall presentation did not constitute falsification or misrepresentation. However, this reasoning leaves unresolved a meaningful gap between technical compliance and the spirit of honesty required by Section II.5.a. A single prefatory notice in a lengthy qualifications document does not guarantee that evaluators - who routinely focus on individual project descriptions when scoring proposals - will connect that notice to each project listed. The Board's analysis would have been strengthened by acknowledging that the adequacy of a disclosure is a function not only of its presence but of its placement, prominence, and the realistic reading behavior of the intended audience. Government procurement evaluators using scoring rubrics are likely to assess individual project entries in isolation, meaning that a prefatory notice, however well-intentioned, may functionally fail to inform the evaluation of each project. The Board's silence on this point leaves a normative gap: the NSPE Code's honesty standard, as applied here, appears to treat disclosure as a binary condition rather than a graduated obligation calibrated to the risk of actual misunderstanding.
The divergence between State Q's general misrepresentation prohibition and State Z's granular project-level attribution requirement reveals that the NSPE Code's honesty standard under Section II.5.a is insufficiently calibrated to address the specific risks of cross-employer project credit attribution in multi-jurisdictional practice. The Code prohibits falsification and misrepresentation but does not specify the structural requirements for attribution disclosures - leaving engineers and firms free to adopt disclosure architectures that are technically non-false but practically obscure. State Z's legislature and licensing board identified this gap and addressed it through specific rules requiring attribution information to appear adjacent to each project listing. The NSPE Code has not made a parallel adjustment. This divergence suggests that the Code's honesty standard, while adequate for clear cases of falsification, is not adequate to govern the more subtle forms of misleading representation that arise from disclosure architecture choices. The Board's conclusion that XYZ Engineers' practice was not unethical under the NSPE Code, while correct as a matter of minimum compliance, should prompt the NSPE to consider whether the Code's attribution provisions need to be updated to reflect the more specific standards that state licensing bodies have found necessary to protect the integrity of the qualification proposal process.
The Board resolved the tension between the Transparency Principle and Qualification Proposal Attribution Integrity by treating document-level disclosure as sufficient to satisfy the NSPE Code's honesty standard, even when that disclosure was not repeated at the project-description level where evaluators are most likely to focus. This resolution effectively privileges formal transparency - the existence of a prefatory notice - over functional transparency - the practical likelihood that a reader will connect that notice to each individual project description in a lengthy proposal body. The case thereby teaches that the NSPE Code's minimum compliance threshold for honesty in professional representations is calibrated to the document as a whole rather than to the reader's likely cognitive path through it. While this outcome avoids finding a violation under the Code, it leaves an unresolved gap between the aspirational standard of intellectual integrity in authorship, which would demand granular attribution, and the minimum standard the Board was willing to enforce. Practitioners and firms should treat this gap as a reason to adopt project-level attribution as a best practice rather than as a ceiling set by the Board's finding.
From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of a licensed engineer when structuring qualifications proposals in a way that was technically transparent at the document level but potentially obscure at the project-description level where clients are most likely to focus their evaluation?
From a virtue ethics perspective, Engineer B did not fully demonstrate the professional integrity and intellectual honesty expected of a licensed engineer. A virtuous engineer - one who has internalized the character traits of honesty, transparency, and respect for clients as rational decision-makers - would not structure a qualifications proposal in a way that is technically transparent at the document level but practically obscure at the project-description level where evaluators focus their attention. The virtue ethics standard asks not merely whether Engineer B avoided lying, but whether Engineer B acted as a person of good professional character would act. A person of good professional character, aware that clients reading lengthy proposal narratives may not carry forward a prefatory attribution notice into their evaluation of each project, would take affirmative steps to ensure that the attribution was visible at the point of evaluation. Engineer B's approach reflects a compliance-minimizing orientation rather than a virtue-maximizing one, and while it may satisfy the minimum threshold for avoiding an NSPE Code violation, it falls short of the aspirational standard of professional integrity that the Code is designed to cultivate.
From a consequentialist perspective, does the mandatory reporting obligation imposed on Engineer A by both states' licensing rules produce better aggregate outcomes for the profession and the public when enforced even in cases where the reporting engineer is a direct commercial competitor, or does it risk weaponizing the licensing system against legitimate competitive behavior?
The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By affirming Engineer A's obligation to report to the State Z board without separately examining whether Engineer A's competitive motivation compromised the integrity of that reporting decision, the Board implicitly treated the reporting duty as categorical - that is, the obligation to report a genuine licensing violation is not diminished or tainted by the reporter's competitive interest in the outcome. This resolution is consistent with a deontological reading of the reporting obligation: if a violation exists, it must be reported regardless of the reporter's motivation. However, the Board's silence on the conflict-of-interest dimension leaves open the consequentialist concern that mandatory reporting rules, when exercised by direct competitors, can function as instruments of competitive harm even when the underlying violation is real. The case teaches that the NSPE Code and state licensing rules prioritize public protection and regulatory integrity over the risk of competitive misuse, but that this prioritization is most defensible when the reported violation is clear and material - as it was under State Z's specific attribution rules - rather than marginal or ambiguous.
From a deontological perspective, did Engineer B fulfill a categorical duty of honesty in professional representations by disclosing prior-employer attribution only in prefatory sections of qualifications proposals rather than at the project-description level, regardless of whether clients were actually misled?
From a deontological perspective, Engineer B's prefatory-only attribution disclosure does not fully satisfy a categorical duty of honesty in professional representations. A Kantian analysis would ask whether the disclosure practice could be universalized - that is, whether a world in which all engineers disclosed prior-employer project credits only in prefatory sections, while allowing detailed project narratives to stand without attribution, would be consistent with a rational system of professional trust. It would not. The categorical duty of honesty requires that representations be structured so that the audience receives accurate information at the point of decision, not merely at a point in the document where the information is technically present but practically obscured. Engineer B's disclosure satisfies a weak non-falsification duty but falls short of the stronger duty of affirmative transparency that deontological ethics demands of licensed professionals whose representations directly affect client procurement decisions. The Board's finding of no NSPE Code violation reflects a minimum compliance threshold, not a deontological endorsement of the practice.
From a consequentialist perspective, did the partial attribution disclosure practice adopted by XYZ Engineers produce net harm to clients, competing firms, and the profession - even if it technically avoided outright misrepresentation under State Q rules - when weighed against the competitive advantage gained?
From a consequentialist perspective, the partial attribution disclosure practice adopted by XYZ Engineers produces a net harm to the competitive fairness of the procurement process and to the integrity of the profession, even if it does not rise to the level of an NSPE Code violation under the State Q standard. The competitive advantage gained by XYZ Engineers through a proposal structure that allows Engineer B's prior-employer projects to function as apparent independent credentials - without per-project attribution reminders - is an advantage that competing firms who provide more granular attribution do not enjoy. Firms that fully comply with the spirit of attribution requirements bear a disclosure cost (potential client skepticism about the depth of in-house experience) that XYZ Engineers partially avoids through its disclosure architecture. Over time, if this practice were normalized, it would create a race-to-minimum-disclosure dynamic that degrades the informational quality of qualification proposals across the profession. The consequentialist calculus therefore supports the stricter State Z approach as producing better aggregate outcomes for clients, competing firms, and the profession - and suggests that the NSPE Code's current standard may be insufficiently calibrated to prevent this form of structural misleading.
From a deontological perspective, does Engineer A's status as a direct competitor of XYZ Engineers create a conflicting duty - between the obligation to report known or suspected licensing violations and the duty to avoid using the reporting mechanism as an instrument of competitive self-interest - and how should that tension be resolved when the underlying violation is genuine?
While the Board implicitly affirmed Engineer A's reporting obligation to the State Z board by framing the State Z violation as established, the Board did not address the conflict-of-interest dimension introduced by Engineer A's status as a direct commercial competitor of XYZ Engineers. Both states' licensing rules impose a mandatory reporting obligation on licensees who have knowledge or reason to believe a violation has occurred, and the NSPE Code similarly supports reporting of unethical or illegal practice. However, the mandatory character of this obligation does not eliminate the ethical significance of the reporter's motivation. From a virtue ethics perspective, the legitimacy of Engineer A's reporting action depends in part on whether it was motivated by genuine concern for client protection and professional integrity rather than competitive self-interest. The Board's analysis would have been more complete had it acknowledged this tension and clarified that the mandatory reporting obligation remains valid and must be fulfilled regardless of the reporter's competitive position - but that Engineer A should be transparent about the competitive relationship when filing the report, and should confine the report strictly to documented rule violations rather than using the reporting mechanism to cast broader reputational doubt on XYZ Engineers. This framing preserves the integrity of the licensing enforcement system while acknowledging that competitive motivation, though it does not void the reporting duty, is an ethically relevant factor that the reporting engineer should consciously examine.
The case reveals a structural tension between the Mandatory Competitor Misconduct Reporting Obligation and the Fairness in Professional Competition principle that the Board did not fully resolve. By affirming Engineer A's obligation to report to the State Z board without separately examining whether Engineer A's competitive motivation compromised the integrity of that reporting decision, the Board implicitly treated the reporting duty as categorical - that is, the obligation to report a genuine licensing violation is not diminished or tainted by the reporter's competitive interest in the outcome. This resolution is consistent with a deontological reading of the reporting obligation: if a violation exists, it must be reported regardless of the reporter's motivation. However, the Board's silence on the conflict-of-interest dimension leaves open the consequentialist concern that mandatory reporting rules, when exercised by direct competitors, can function as instruments of competitive harm even when the underlying violation is real. The case teaches that the NSPE Code and state licensing rules prioritize public protection and regulatory integrity over the risk of competitive misuse, but that this prioritization is most defensible when the reported violation is clear and material - as it was under State Z's specific attribution rules - rather than marginal or ambiguous.
From a virtue ethics perspective, does a licensing regime that requires engineers to report competitors' violations cultivate or undermine the virtue of professional solidarity, and did Engineer A act with the appropriate motivational integrity - concern for public protection rather than competitive advantage - when deciding to report to the State Z board?
From a virtue ethics perspective, the licensing regime's mandatory competitor-reporting obligation presents a genuine tension between professional solidarity and public protection, but that tension does not undermine the obligation's legitimacy. The virtue of professional solidarity - which would counsel engineers to resolve ambiguous situations in favor of colleagues rather than reporting them to regulatory authorities - is a real professional virtue, but it is subordinate to the more fundamental virtues of honesty and public protection when a genuine violation is at stake. Engineer A's decision to report to the State Z board, where a specific and clear rule violation existed, reflects appropriate motivational integrity only if Engineer A's primary concern was the integrity of the qualification proposal process and the protection of clients from misleading representations - not the elimination of a competitor. The case facts suggest that Engineer A conducted a careful, jurisdiction-specific analysis and declined to report where no clear violation existed (State Q), which is consistent with good-faith application of the reporting obligation. However, the virtue ethics framework would require Engineer A to honestly examine whether the decision to report was driven by genuine concern for professional standards or by competitive self-interest - and to refrain from reporting if the honest answer is the latter. The licensing system is not designed to be an instrument of competitive strategy, and a virtuous engineer would use it only when the public protection rationale is genuine and primary.
Question 17 Counterfactual
If XYZ Engineers had included the prior-employer attribution notice not only in the prefatory individual qualification section but also immediately adjacent to each project description throughout the proposal body, would the Board have reached the same conclusion that no NSPE Code violation occurred, or would that level of disclosure have been required to satisfy the honesty standard under Section II.5.a?
The counterfactual in which XYZ Engineers had included attribution notices adjacent to each project description throughout the proposal body would almost certainly have led the Board to the same conclusion of no NSPE Code violation - and indeed would have represented a more clearly compliant practice. The Board's conclusion that the prefatory notice was sufficient to avoid a violation under the NSPE Code and State Q rules rested on the finding that the notice was present and identifiable, not that it was optimally placed. Had the attribution appeared at the project-description level, the case for compliance would have been even stronger, and the ambiguity that gave rise to Engineer A's concern would have been eliminated. This counterfactual therefore confirms that the Board's conclusion was a minimum-threshold determination: the prefatory notice was just sufficient to avoid a violation, but project-level attribution would have been the clearly preferable practice. The counterfactual also reveals that the NSPE Code's honesty standard under Section II.5.a does not affirmatively require project-level attribution - it only prohibits misrepresentation - which is the gap that State Z's more specific rules were designed to close.
Question 18 Counterfactual
If Engineer A had chosen not to review the specific licensing board rules of either state and had relied solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, would Engineer A have correctly identified the State Z violation, and does this scenario reveal a gap in the NSPE Code's ability to capture jurisdiction-specific professional misconduct?
The counterfactual in which Engineer A had relied solely on the NSPE Code of Ethics - without reviewing the jurisdiction-specific licensing rules of State Q and State Z - reveals a critical gap in the Code's ability to capture jurisdiction-specific professional misconduct. Under the NSPE Code alone, the analysis of XYZ Engineers' proposal practice would have been inconclusive: the prefatory attribution notice arguably avoids outright falsification under Section II.5.a, and the Code does not specify the granularity of attribution required. Engineer A would likely have concluded that the practice was ethically questionable but not clearly prohibited - and would not have identified the specific State Z rule violation that triggered the mandatory reporting obligation. This scenario confirms that the NSPE Code functions as a floor of general ethical principles, not as a comprehensive substitute for jurisdiction-specific licensing rules. Engineers practicing across multiple jurisdictions have an affirmative obligation to identify and apply the specific rules of each jurisdiction - an obligation that the Code itself acknowledges through Section III.8.a's requirement to conform with state registration laws. The case therefore stands as a practical illustration of why multi-jurisdictional practice requires jurisdiction-specific rule review, and why reliance on the NSPE Code alone is insufficient for compliance purposes.
Question 19 Counterfactual
What if Engineer B's prior projects had involved proprietary design concepts owned by the previous employer - would the Board's analysis under NSPE Code Section III.9 have shifted, and would XYZ Engineers' proposal practice have been found unethical even under the more permissive State Q standard?
Question 20 Counterfactual
If State Q's licensing rules had been as specific as State Z's - requiring attribution information to appear next to each individual project listing rather than only in a prefatory section - would Engineer A have had a clear obligation to report XYZ Engineers' conduct to the State Q board as well, and would the Board's conclusion on Question 2 have been reversed?
The Board's analysis of Engineer A's reporting obligation appropriately distinguished between State Q and State Z based on the differing specificity of each state's licensing rules, concluding that a violation was established in State Z but not in State Q. This jurisdiction-differentiated outcome carries an important practical implication that the Board did not make explicit: Engineer A's obligation to report to the State Z board is mandatory under both states' rules once Engineer A has knowledge or reason to believe a violation occurred, and that threshold was met by Engineer A's own review of the State Z rules. The Board's reasoning therefore implicitly confirms that Engineer A's decision to report to the State Z board was not merely permissible but obligatory - and that declining to report after identifying a clear rule violation would itself have constituted a breach of Engineer A's professional obligations. Conversely, the absence of a comparable violation under State Q's more permissive standard means that reporting to the State Q board would have been unsupported by the factual record and potentially inconsistent with Section III.7's prohibition on conduct that injures the professional reputation of another engineer without factual basis. This asymmetry - mandatory reporting in State Z, inappropriate reporting in State Q - illustrates that the reporting obligation is not a blanket duty triggered by competitive suspicion but a jurisdiction-specific, evidence-calibrated professional responsibility.
The counterfactual in which State Q's licensing rules were as specific as State Z's - requiring attribution information to appear next to each individual project listing - would have reversed the Board's conclusion on Question 2 with respect to State Q. Under that scenario, XYZ Engineers' prefatory-only attribution structure would have constituted a clear violation of State Q rules, and Engineer A would have had an obligation to report to the State Q board as well. This counterfactual is analytically important because it demonstrates that the Board's conclusion on the reporting obligation is entirely dependent on the jurisdiction-specific content of the applicable licensing rules, not on the NSPE Code of Ethics alone. The NSPE Code's general prohibition on misrepresentation of qualifications was insufficient to establish a clear violation in State Q; it was only the specific, granular language of State Z's rules that created the unambiguous violation triggering the mandatory reporting obligation. This reveals a structural gap: engineers practicing in jurisdictions with less specific rules receive less protection from the kind of partial-disclosure practices at issue here, and the NSPE Code does not fill that gap.
Question 21 Counterfactual
What if Engineer A had filed the report to the State Z board anonymously rather than under their own name - would the mandatory reporting obligation still be considered fulfilled, and would the competitive-interest neutrality concern be mitigated or exacerbated by anonymous filing?
Rich Analysis Results
View ExtractionCausal-Normative Links 7
XYZ Hires Engineer B
Engineer A Investigates Marketing Practice
- Multi-Jurisdiction Ethics Review Obligation Engineer A Both States
- Proportionate Misrepresentation Characterization Before Reporting Obligation
- Engineer A Multi-Jurisdiction Ethics Review State Q State Z
- Engineer A Proportionate Characterization State Q Proposal Analysis
- Engineer A Jurisdiction-Specific Threshold Analysis State Q No Reporting
- Engineer A Jurisdiction-Specific Threshold Analysis State Z Reporting Required
Engineer A Reviews Applicable Rules
- Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation
- Multi-Jurisdiction Ethics Review Obligation Engineer A Both States
- Engineer A Multi-Jurisdiction Ethics Review State Q State Z
- Engineer A Jurisdiction-Specific Threshold Analysis State Q No Reporting
- Engineer A Jurisdiction-Specific Threshold Analysis State Z Reporting Required
Engineer A Reports to State Z Board
- Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Z
- Engineer A Competitor Misconduct Reporting State Z Licensing Board
- Multi-Jurisdiction Ethics Review Obligation Engineer A Both States
- Engineer A Multi-Jurisdiction Ethics Review State Q State Z
- Jurisdiction-Specific Misconduct Reporting Threshold Compliance Obligation
- Engineer A Jurisdiction-Specific Threshold Analysis State Z Reporting Required
Engineer A Declines State Q Report
- Engineer A Jurisdiction-Specific Threshold Analysis State Q No Reporting
- Engineer A Proportionate Characterization State Q Proposal Analysis
- Proportionate Misrepresentation Characterization Before Reporting Obligation
- Multi-Jurisdiction Ethics Review Obligation Engineer A Both States
- Engineer A Multi-Jurisdiction Ethics Review State Q State Z
- Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q
Engineer B Completes Prior Projects
- Prior-Employer Project Credit Scope Limitation Obligation
- Engineer B Prior Employer Credit Scope Limitation State Q State Z
Partial Attribution Disclosure in Proposals
- Project-Level Attribution in Qualification Proposals Obligation
- Qualification Proposal Misrepresentation Non-Commission Obligation
- Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation
- Prior-Employer Project Credit Scope Limitation Obligation
- Project-Level Attribution Obligation XYZ Engineers Engineer B State Z Proposals
- Qualification Proposal Misrepresentation Non-Commission Obligation XYZ Engineers State Q
- Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
- Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
- Maximum Clarity Attribution in Qualification Proposals Obligation
- Engineer B Maximum Clarity Attribution State Q Proposal
- Engineer B Project-Level Attribution State Z Proposal
- XYZ Engineers Qualification Proposal Misrepresentation State Z
Question Emergence 21
Triggering Events
- Engineer B Gains Experience
- XYZ Market Entry Occurs
- Attribution Ambiguity Created
Triggering Actions
- Engineer B Completes Prior Projects
- XYZ Hires Engineer B
- Partial Attribution Disclosure in Proposals
Competing Warrants
- Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
- Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q Qualification Proposal Misrepresentation Non-Commission Obligation XYZ Engineers State Q
Triggering Events
- Competitor Awareness Triggered
- Differential State Rules Discovered
- State Z Violation Established
- BER Precedent Applied
Triggering Actions
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
- Engineer A Declines State Q Report
Competing Warrants
- Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q Proportionate Misrepresentation Characterization Before Reporting Obligation
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q
Triggering Events
- Competitor Awareness Triggered
- State Z Violation Established
- BER Precedent Applied
Triggering Actions
- Engineer A Investigates Marketing Practice
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
Competing Warrants
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Fairness in Professional Competition Invoked By Engineer A ABC Consultants
- Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting Public Welfare Paramount Through Licensing Board Reporting
Triggering Events
- Attribution Ambiguity Created
- BER Precedent Applied
- State Z Violation Established
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer B Completes Prior Projects
- Engineer A Investigates Marketing Practice
Competing Warrants
- Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects Proportionality Analysis Applied to State Q Proposal
- Project-Level Attribution in Qualification Proposals Obligation Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
Triggering Events
- Attribution Ambiguity Created
- XYZ Market Entry Occurs
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer B Completes Prior Projects
- XYZ Hires Engineer B
Competing Warrants
- Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects Transparency Principle Invoked By XYZ Engineers Prefatory Notice
- Maximum Clarity Attribution in Qualification Proposals Obligation Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
Triggering Events
- Competitor Awareness Triggered
- Differential State Rules Discovered
- State Z Violation Established
Triggering Actions
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
Competing Warrants
- Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q Conflict of Interest Avoidance Constraint Engineer A Competitor Reporting Decision
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Proportionate Misrepresentation Characterization Before Reporting Obligation
Triggering Events
- Competitor Awareness Triggered
- Differential State Rules Discovered
- State Z Violation Established
- BER Precedent Applied
Triggering Actions
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
Competing Warrants
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Public Welfare Paramount Through Licensing Board Reporting
- Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting Proportionality in Misconduct Characterization
Triggering Events
- State Z Violation Established
- Competitor Awareness Triggered
- BER Precedent Applied
Triggering Actions
- Engineer A Reports to State Z Board
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
Competing Warrants
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Fairness in Professional Competition Invoked By Engineer A ABC Consultants
- Public Welfare Paramount Through Licensing Board Reporting Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting
Triggering Events
- Engineer B Gains Experience
- XYZ Market Entry Occurs
- Attribution Ambiguity Created
Triggering Actions
- Engineer B Completes Prior Projects
- XYZ Hires Engineer B
- Partial Attribution Disclosure in Proposals
Competing Warrants
- NSPE Code of Ethics - Professional Obligation III.9 (Credit for Proprietary Interests) Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
- Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects Prior-Employer Project Credit Scope Limitation Obligation Engineer B XYZ Engineers State Z
Triggering Events
- State Z Violation Established
- Competitor Awareness Triggered
- BER Precedent Applied
Triggering Actions
- Engineer A Reports to State Z Board
- Engineer A Investigates Marketing Practice
Competing Warrants
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Anonymous Reporting Precedent Invoked from BER Case 02-11
- Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting Public Welfare Paramount Through Licensing Board Reporting
Triggering Events
- Attribution Ambiguity Created
- XYZ Market Entry Occurs
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer B Completes Prior Projects
Competing Warrants
- Transparency Principle Invoked By XYZ Engineers Prefatory Notice Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
- Honesty in Professional Representations Invoked By XYZ Engineers Qualification Proposals Intellectual Integrity in Authorship Invoked By Engineer B Prior Employer Projects
Triggering Events
- Differential State Rules Discovered
- State Z Violation Established
- Attribution Ambiguity Created
Triggering Actions
- Engineer A Reviews Applicable Rules
- Engineer A Declines State Q Report
- Engineer A Reports to State Z Board
Competing Warrants
- Jurisdiction-Specific Reporting Threshold Applied by Engineer A in State Q Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States
- Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q
Triggering Events
- Differential State Rules Discovered
- State Z Violation Established
- BER Precedent Applied
Triggering Actions
- Engineer A Reviews Applicable Rules
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
Competing Warrants
- Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review Honesty in Professional Representations Applied to Engineer B Attribution
- Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation Qualification Proposal Misrepresentation Non-Commission Obligation
Triggering Events
- Attribution Ambiguity Created
- Competitor Awareness Triggered
- Differential State Rules Discovered
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
Competing Warrants
- Qualification Proposal Misrepresentation Non-Commission Obligation XYZ Engineers State Q Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation
- Fairness in Professional Competition Invoked By Engineer A ABC Consultants Proportionate Misrepresentation Characterization Before Reporting Obligation
Triggering Events
- Engineer B Gains Experience
- XYZ Market Entry Occurs
- Attribution Ambiguity Created
Triggering Actions
- Engineer B Completes Prior Projects
- XYZ Hires Engineer B
- Partial Attribution Disclosure in Proposals
Competing Warrants
- Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Maximum Clarity Attribution in Qualification Proposals Obligation
- Qualification Proposal Misrepresentation Non-Commission Obligation Prior-Employer Project Credit Scope Limitation Obligation
Triggering Events
- Competitor Awareness Triggered
- Attribution Ambiguity Created
- State Z Violation Established
Triggering Actions
- Engineer A Investigates Marketing Practice
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
Competing Warrants
- Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Q Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting
- Mandatory Competitor Misconduct Reporting Obligation Invoked By Engineer A Both States Fairness in Professional Competition Invoked By Engineer A ABC Consultants
Triggering Events
- XYZ Market Entry Occurs
- Attribution Ambiguity Created
- State Z Violation Established
Triggering Actions
- XYZ Hires Engineer B
- Partial Attribution Disclosure in Proposals
Competing Warrants
- Qualification Proposal Misrepresentation Non-Commission Obligation XYZ Engineers State Q Project-Level Attribution Obligation XYZ Engineers Engineer B State Z Proposals
- Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Jurisdiction-Specific Licensing Rule Compliance Obligation XYZ Engineers Engineer B Both States
Triggering Events
- Attribution Ambiguity Created
- Differential State Rules Discovered
- BER Precedent Applied
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer A Investigates Marketing Practice
- Engineer A Reviews Applicable Rules
Competing Warrants
- Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Maximum Clarity Attribution in Qualification Proposals Obligation
- Transparency Principle Invoked By XYZ Engineers Prefatory Notice Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
Triggering Events
- Attribution Ambiguity Created
- XYZ Market Entry Occurs
- Competitor Awareness Triggered
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer A Investigates Marketing Practice
Competing Warrants
- Honesty in Professional Representations Obligation XYZ Engineers Qualification Proposals Both States Qualification Proposal Misrepresentation Non-Commission Obligation XYZ Engineers State Q
- Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q Proportionate Misrepresentation Threshold Assessment Constraint Engineer A State Q No Reporting
Triggering Events
- Differential State Rules Discovered
- State Z Violation Established
- BER Precedent Applied
- Attribution Ambiguity Created
Triggering Actions
- Engineer A Reviews Applicable Rules
- Engineer A Reports to State Z Board
- Engineer A Declines State Q Report
- Partial Attribution Disclosure in Proposals
Competing Warrants
- Jurisdiction-Specific Ethics Compliance Obligation Invoked By Engineer A Multi-State Review Honesty in Professional Representations Invoked By XYZ Engineers Qualification Proposals
- Jurisdiction-Specific Licensing Rule Compliance in Qualification Proposals Obligation Qualification Proposal Misrepresentation Non-Commission Obligation
- Multi-Jurisdiction Ethics Review Obligation Engineer A Both States Competitor Qualification Proposal Misconduct Reporting Obligation Engineer A State Z
Triggering Events
- Attribution Ambiguity Created
- XYZ Market Entry Occurs
Triggering Actions
- Partial Attribution Disclosure in Proposals
- Engineer B Completes Prior Projects
- XYZ Hires Engineer B
Competing Warrants
- Honesty in Professional Representations Invoked By XYZ Engineers Qualification Proposals Transparency Principle Invoked By XYZ Engineers Prefatory Notice
- Maximum Clarity Attribution in Qualification Proposals Obligation Qualification Proposal Attribution Integrity Invoked By Engineer B XYZ Engineers State Q
Resolution Patterns 20
Determinative Principles
- Transparency through document-level disclosure satisfies honesty obligations
- Jurisdiction-specific rule compliance determines reporting obligations
- Prefatory attribution notice avoids falsification under NSPE Code
Determinative Facts
- Engineer B and XYZ Engineers included a prefatory attribution notice in the qualifications proposal identifying prior-employer projects
- State Q's licensing rules did not require project-level attribution, so no violation occurred there
- State Z's rules were violated, triggering Engineer A's reporting obligation to the State Z board but not the State Q board
Determinative Principles
- Individual licensee responsibility as the primary unit of ethical analysis under the NSPE Code
- Institutional responsibility of firms for structural proposal architecture decisions
- Credit attribution obligations under Section III.9 apply to professional conduct broadly
Determinative Facts
- XYZ Engineers as a firm made the deliberate organizational decision to structure qualifications proposals with attribution concentrated in a single prefatory location
- The Board's analysis focused primarily on Engineer B's individual conduct without separately evaluating the firm's institutional responsibility
- XYZ Engineers controlled the proposal format and architecture while Engineer B executed within that structure
Determinative Principles
- Jurisdiction-specific ethics compliance: reporting obligations are calibrated to the specificity of each state's licensing rules
- Evidence-calibrated professional responsibility: the duty to report is triggered only when a clear rule violation is identifiable on the facts
- Prohibition on injuring professional reputation without factual basis: reporting where no clear violation exists is itself a breach
Determinative Facts
- State Z's licensing rules specifically required attribution information to appear adjacent to each individual project listing, a standard XYZ Engineers' prefatory-only notice failed to meet
- State Q's licensing rules were more permissive and did not impose the same granular attribution requirement, meaning no clear violation was identifiable under State Q's standard
- Engineer A personally reviewed the licensing rules of both states, establishing actual knowledge of the State Z violation and the absence of a comparable State Q violation
Determinative Principles
- Mandatory reporting duty is not nullified by the reporter's competitive interest: the obligation attaches to any licensee with knowledge of a violation regardless of their relationship to the violator
- Motivational integrity: the competitive relationship is ethically relevant to the quality of the reporter's conduct but not to the existence of the underlying violation
- Scrupulous accuracy as the operative constraint on a conflicted reporter: the conflict of interest demands precision, not abstention
Determinative Facts
- Engineer A is a direct commercial competitor of XYZ Engineers, creating a structural conflict of interest that could color the motivation for reporting
- Engineer A reported only to the State Z board where a specific rule was clearly breached, and declined to report to the State Q board where no clear violation was found, demonstrating selective restraint consistent with good faith
- Both states' licensing rules impose a mandatory reporting duty on any licensee with knowledge or reason to believe a violation occurred, without carving out an exception for competitors
Determinative Principles
- Categorical duty of honesty: deontological analysis requires that representations be structured so the audience receives accurate information at the point of decision, not merely at a technically present but practically obscured location
- Universalizability test: a disclosure practice that could not be universalized without undermining rational professional trust fails the Kantian standard regardless of whether it produces actual harm in a specific case
- Distinction between weak non-falsification duty and stronger affirmative transparency duty: Engineer B satisfied the former but not the latter
Determinative Facts
- Engineer B disclosed prior-employer attribution only in prefatory sections, not at the project-description level where procurement evaluators are most likely to make substantive credentialing judgments
- A world in which all engineers disclosed prior-employer project credits only in prefatory sections while allowing detailed project narratives to stand without attribution would be inconsistent with a rational system of professional trust, failing the universalizability test
- The Board's finding of no NSPE Code violation reflects a minimum compliance threshold calibrated to State Q's permissive rules, not a deontological assessment of whether the categorical duty of honesty was fulfilled
Determinative Principles
- Consequentialist net harm analysis: competitive fairness and informational integrity of the procurement process
- Race-to-minimum-disclosure dynamic as a systemic harm to the profession
- Asymmetric disclosure cost borne by fully compliant firms versus partially disclosing firms
Determinative Facts
- XYZ Engineers placed attribution only in a prefatory notice, not adjacent to each project description, allowing prior-employer projects to function as apparent independent credentials in the body of the proposal
- Competing firms that provide more granular attribution bear a disclosure cost (client skepticism about in-house experience depth) that XYZ Engineers partially avoids through its disclosure architecture
- The Board found no NSPE Code violation under the State Q standard, yet still identified a net harm through the consequentialist lens, revealing a gap between minimum compliance and ethical optimality
Determinative Principles
- Professional solidarity as a real but subordinate virtue when a genuine violation is at stake
- Motivational integrity: the reporting engineer's primary concern must be public protection, not competitive elimination
- The licensing system's public protection rationale as the legitimate and exclusive basis for invoking mandatory reporting
Determinative Facts
- Engineer A conducted a careful, jurisdiction-specific analysis and declined to report to the State Q board where no clear violation existed, which is consistent with good-faith application of the reporting obligation rather than indiscriminate competitive weaponization
- Engineer A reported only to the State Z board where a specific and clear rule violation existed, suggesting the report was calibrated to genuine violations rather than used as a broad competitive strategy
- The virtue ethics framework requires Engineer A to honestly examine whether the decision to report was driven by genuine concern for professional standards or by competitive self-interest, and to refrain from reporting if the honest answer is the latter
Determinative Principles
- Minimum-threshold versus clearly preferable practice distinction: the prefatory notice was just sufficient, not optimal
- The NSPE Code's honesty standard under Section II.5.a prohibits misrepresentation but does not affirmatively require project-level attribution
- Counterfactual analysis as a tool for identifying the gap between minimum compliance and best practice
Determinative Facts
- The Board's finding of no NSPE Code violation rested on the prefatory notice being present and identifiable, not on it being optimally placed — confirming the conclusion was a minimum-threshold determination
- Had attribution appeared at the project-description level, the ambiguity that gave rise to Engineer A's concern would have been eliminated entirely, and the case for compliance would have been unambiguously stronger
- State Z's more specific rules were designed precisely to close the gap that the NSPE Code's general prohibition on misrepresentation leaves open by not requiring project-level attribution
Determinative Principles
- Jurisdiction-specific rule content as the determinative variable for whether a mandatory reporting obligation is triggered
- The NSPE Code's general misrepresentation prohibition as insufficient alone to establish a clear violation requiring mandatory reporting
- Structural gap in engineer protection: jurisdictions with less specific rules provide less protection from partial-disclosure practices
Determinative Facts
- Under the counterfactual State Q rules (as specific as State Z's), XYZ Engineers' prefatory-only attribution structure would have constituted a clear violation, reversing the Board's conclusion on Question 2 for State Q
- The Board's actual conclusion on the reporting obligation was entirely dependent on the jurisdiction-specific content of State Q's licensing rules, not on the NSPE Code of Ethics alone, demonstrating that the Code does not fill the gap left by less specific state rules
- Only the specific, granular language of State Z's rules created the unambiguous violation that triggered the mandatory reporting obligation — the NSPE Code's general prohibition was insufficient to do so independently
Determinative Principles
- NSPE Code as floor of general ethical principles, not comprehensive substitute for jurisdiction-specific rules
- Affirmative obligation of multi-jurisdictional practitioners to identify and apply jurisdiction-specific rules
- Jurisdiction-Specific Ethics Compliance Obligation
Determinative Facts
- Engineer A's hypothetical reliance solely on the NSPE Code would have rendered the analysis of XYZ Engineers' practice inconclusive rather than clearly prohibited
- The prefatory attribution notice arguably avoids outright falsification under Section II.5.a when evaluated under the Code alone, leaving no clear violation identifiable
- The specific State Z rule violation — which triggered the mandatory reporting obligation — would not have been identified without reviewing jurisdiction-specific licensing rules
Determinative Principles
- NSPE Code honesty standard as minimum floor, not ceiling, for professional representation
- Jurisdiction-Specific Ethics Compliance Obligation requiring independent rule-by-rule analysis per state
- Structural inadequacy of the Code's attribution provisions relative to state-level granularity requirements
Determinative Facts
- State Z's licensing rules require attribution information to appear adjacent to each individual project listing, a specificity the NSPE Code does not replicate
- State Q's general misrepresentation prohibition was satisfied by the prefatory notice, while State Z's granular rule was violated by the same practice
- The NSPE Code prohibits falsification and misrepresentation but does not specify structural requirements for attribution disclosure architecture
Determinative Principles
- Formal transparency (existence of prefatory notice) privileged over functional transparency (reader's likely cognitive path)
- Intellectual Integrity in Authorship as an aspirational norm distinct from the minimum compliance threshold the Code enforces
- Proportionality Analysis calibrating the Code's honesty standard to the document as a whole rather than to individual project descriptions
Determinative Facts
- XYZ Engineers placed the prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, not adjacent to each project description
- The board found no NSPE Code violation despite the disclosure's placement being remote from the project descriptions where evaluators are most likely to focus
- The gap between aspirational intellectual integrity norms and the minimum compliance threshold the board was willing to enforce was left explicitly unresolved
Determinative Principles
- Deontological categorical reporting obligation: a genuine licensing violation must be reported regardless of the reporter's competitive motivation
- Public protection and regulatory integrity prioritized over the risk of competitive misuse of the reporting mechanism
- Fairness in Professional Competition as a competing but subordinate consideration when the underlying violation is clear and material
Determinative Facts
- Engineer A is a direct competitor of XYZ Engineers and stands to gain a competitive advantage from the investigation triggered by the report
- The State Z violation was clear and material — a specific, identifiable breach of the project-level attribution rule — rather than marginal or ambiguous
- The board affirmed the reporting obligation without separately examining whether Engineer A's competitive motivation compromised the integrity of the reporting decision
Determinative Principles
- Minimum compliance versus aspirational ethics: satisfying the technical floor of the NSPE Code does not constitute endorsement of the practice as consistent with the Code's spirit of honesty and transparency
- Structural risk of misleading impressions: a disclosure architecture that places attribution where it is least likely to be operationally noticed creates ethical risk even without any single false statement
- Intellectual integrity in authorship: the principle underlying Section III.9.a supports project-level attribution as the more transparent and professionally sound approach
Determinative Facts
- The prefatory attribution notice appeared only at the beginning of Engineer B's individual qualification section and was not repeated within each project description, creating physical and cognitive distance between the caveat and the narratives it qualified
- Government procurement evaluators conducting substantive review are most likely to focus on detailed project descriptions rather than prefatory notices that may be several pages removed from the specific narratives
- State Z's rules explicitly required attribution information adjacent to each project listing, confirming that the prefatory-only approach was recognized by at least one jurisdiction as insufficient to prevent misleading impressions
Determinative Principles
- NSPE Code as floor, not ceiling, for professional honesty — jurisdiction-specific rules can impose materially higher standards without logical contradiction
- Jurisdiction-Specific Ethics Compliance Obligation requiring independent rule-by-rule analysis in each state of practice
- Honesty in Professional Representations as operationalized differently across regulatory environments, producing divergent compliance outcomes from a single course of conduct
Determinative Facts
- Engineer B's prefatory-only attribution practice simultaneously satisfied the NSPE Code's honesty standard and State Q's misrepresentation prohibition while violating State Z's more granular project-level attribution rule
- The NSPE Code does not specify the structural granularity required for attribution disclosures, leaving firms free to adopt disclosure architectures that are technically non-false but practically obscure
- Firms operating across state lines must treat the most demanding applicable jurisdiction's attribution standard as the operative benchmark to avoid selective non-compliance
Determinative Principles
- Disclosure adequacy is a function of presence rather than placement or prominence under the Board's implicit reading
- Document-level transparency as a binary condition rather than a graduated obligation
- Spirit of honesty under Section II.5.a requires more than technical non-falsification
Determinative Facts
- The prefatory attribution notice appeared only once at the beginning of Engineer B's individual qualification section, not adjacent to each project description
- Government procurement evaluators routinely use scoring rubrics and assess individual project entries in isolation
- The Board treated the existence of the notice as sufficient without analyzing whether its placement ensured actual comprehension by the intended audience
Determinative Principles
- Institutional culpability: a firm that designs the disclosure architecture of its proposals bears independent responsibility for the misleading impressions that architecture creates
- Prohibition on permitting misrepresentation of qualifications applies to the firm as an entity, not only to the individual engineer who signed the proposal
- Supervisory adequacy: a firm operating across multiple jurisdictions must exercise oversight sufficient to ensure its standard proposal structure meets the most demanding applicable standard
Determinative Facts
- XYZ Engineers, as the firm that prepared, reviewed, and submitted the qualifications proposals, made the organizational decision to place attribution notices only in prefatory sections rather than adjacent to individual project descriptions
- The State Z rules imposed a stricter attribution standard that XYZ Engineers' standard proposal structure failed to meet, indicating the firm's disclosure architecture was inadequate for multi-jurisdictional use
- The Board's analysis focused on Engineer B's individual conduct and did not separately evaluate XYZ Engineers' institutional responsibility for the proposal structure it institutionalized
Determinative Principles
- Virtue ethics standard of aspirational professional integrity, not merely minimum compliance
- Honesty and transparency as internalized character traits requiring affirmative action at the point of client evaluation
- Compliance-minimizing orientation versus virtue-maximizing orientation as distinguishable professional stances
Determinative Facts
- Engineer B placed the attribution notice only in a prefatory section, not within each project description, creating practical obscurity at the level where evaluators focus their attention despite technical document-level transparency
- Clients reading lengthy proposal narratives may not carry forward a prefatory attribution notice into their evaluation of each individual project, making the single prefatory disclosure functionally insufficient for informed evaluation
- Engineer B's approach satisfied the minimum threshold for avoiding an NSPE Code violation but did not reflect the affirmative transparency steps a person of good professional character would take
Determinative Principles
- Mandatory reporting obligation is valid and must be fulfilled regardless of the reporter's competitive position
- Competitive motivation is an ethically relevant factor that does not void the reporting duty but warrants conscious examination
- Transparency about competitive relationship and confinement of report to documented violations preserves enforcement system integrity
Determinative Facts
- Engineer A is a direct commercial competitor of XYZ Engineers, creating a potential conflict of interest in the reporting decision
- Both states' licensing rules impose a mandatory reporting obligation on licensees with knowledge or reason to believe a violation has occurred
- The Board framed the State Z violation as established but did not address whether Engineer A's competitive motivation affected the legitimacy of the reporting action
Determinative Principles
- NSPE Code functions as a floor rather than a ceiling for professional honesty obligations
- Jurisdiction-specific licensing rules impose more granular attribution requirements than the NSPE Code
- Engineers in multi-jurisdictional practice must apply the most stringent applicable standard
Determinative Facts
- Conduct deemed compliant under the NSPE Code simultaneously violated State Z's specific project-level attribution rules
- State Z's rules imposed a precise project-level attribution requirement that the NSPE Code's honesty standard does not specify
- Engineer B and XYZ Engineers operated across multiple jurisdictions with differing attribution rule specificity
Decision Points
View ExtractionShould Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by placing prior-employer attribution only in a prefatory notice at the start of the qualification section, by repeating attribution adjacent to each individual project description, or by omitting attribution altogether?
- Attribute Only in Prefatory Notice
- Attribute Adjacent to Each Project Description
- Omit Attribution and Rely on Evaluator Knowledge
Should Engineer A report XYZ Engineers' attribution practices to both state licensing boards, to State Z's board only, or withhold the report entirely due to the competitor relationship?
- Report to State Z Only in Writing
- Withhold Report Due to Competitor Conflict
- Report to Both Boards Using NSPE Standard
Should Engineer B and XYZ Engineers tailor their qualification proposal format to meet each state's specific attribution requirements — including State Z's more stringent project-level rule — or apply a single uniform format based on the less demanding State Q standard?
- Apply Uniform State Q Standard Across Proposals
- Tailor Format to Each Jurisdiction's Requirements
- Apply NSPE Code Standard Uniformly Instead
Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project description to satisfy the NSPE Code's honesty and transparency obligations?
- Attribute Only in Prefatory Section
- Attribute Adjacent to Each Project Description
Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification proposals, or is it ethically permissible to calibrate disclosure architecture to each state's minimum rule, accepting that the same proposal structure may comply in State Q while violating State Z?
- Calibrate Attribution to Each State's Minimum
- Adopt Strictest Jurisdiction as Universal Standard
Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content of each state's rules — reporting only where a clear rule violation is identifiable and declining to report where the applicable rules do not independently prohibit the practice?
- Report to State Z Only, Decline State Q
- Report to Both Boards via NSPE Standard
- Decline All Reporting Due to Conflict
Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project description throughout the proposal body?
- Attribute Only in Prefatory Section
- Attribute Adjacent to Each Project Description
Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated?
- Report to State Z Only After Confirming Violation
- Report to Both Boards via NSPE Prohibition
- Decline Reporting Due to Competitor Conflict
Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmark for all proposals, or calibrate disclosure architecture separately to each jurisdiction's minimum rule requirements?
- Apply Strictest Jurisdiction's Standard Universally
- Calibrate Disclosure To Each Jurisdiction Separately
Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project description in order to satisfy the NSPE Code's honesty standard and applicable state licensing rules?
- Attribute Only in Prefatory Section
- Attribute Adjacent to Each Project Description
Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial competitor of XYZ Engineers create a conflict of interest that modifies or voids the mandatory reporting obligation?
- Report to State Z Only After Rule Review
- Report to Both Boards via NSPE Standard
- Decline Reporting Due to Competitor Conflict
When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's project-level attribution standard to all proposals, or may they calibrate disclosure granularity to the minimum required by each individual state's rules?
- Match Each State's Minimum Disclosure Standard
- Apply Strictest Jurisdiction's Standard Universally
Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description throughout the proposal body?
- Disclose Only in Prefatory Section
- Include Attribution Beside Each Project
Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear rule violation is identifiable under State Q's standard?
- Decline to Report to State Q Board
- Report to State Q Using NSPE Standard
Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to report, rather than relying solely on the NSPE Code of Ethics to assess the conduct?
- Review Each Jurisdiction's Rules Independently
- Assess Against NSPE Code Only
Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule violation is identifiable there but not under State Q's more permissive standard?
- Report to State Z Only After Review
- Rely Solely on NSPE Code, Skip Reporting
- Report to Both Boards Without Differentiating
Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a single prefatory section of Engineer B's qualifications, in order to satisfy both the NSPE Code's honesty standard and the more specific attribution requirements of State Z?
- Attribute Adjacent to Each Project Description
- Disclose Only in Single Prefatory Section
Case Narrative
Phase 4 narrative construction results for Case 19
Opening Context
You are Engineer B, a project manager recently hired by XYZ Engineers to lead bridge and culvert design work in State Q and State Z. Your prior projects, completed under a different employer, did not involve proprietary design concepts, and your previous team members worked within your areas of expertise. XYZ Engineers' qualification proposals identify those earlier projects in a prefatory section at the start of your individual qualifications, naming the prior employer and associated client for each. However, that attribution does not appear within the detailed descriptions of each individual project throughout the proposal body. Engineer A, a licensed engineer at competing firm ABC Consultants, has raised questions about whether this practice complies with the licensing board rules of both states and satisfies the honesty obligations of the NSPE Code of Ethics. The decisions ahead involve how attribution should be structured in multi-jurisdiction proposals and what obligations, if any, arise from the current practice.
Characters (12)
An ABC Consultants bridge and culvert engineer who has identified potentially improper qualification proposal practices by competitor XYZ Engineers across two state jurisdictions.
- To protect fair competitive integrity in the procurement process and fulfill any professional and legal obligations to report misconduct, while also potentially benefiting from a competitor's disqualification.
- To win public contracts by showcasing the strongest possible portfolio of relevant project experience while navigating the fine line between permissible attribution and misrepresentation.
A careful ethical analyst applying both the NSPE Code and the distinct licensing board rules of State Q and State Z to determine whether XYZ Engineers' proposal practices constitute a reportable violation.
- To reach a proportionate, jurisdiction-accurate determination of misconduct that justifies or declines mandatory reporting without overreaching or understating the ethical breach.
Reviews NSPE Code and state licensing board rules of both State Q and State Z to assess whether XYZ Engineers' qualification proposal practices are unethical and whether a mandatory written reporting obligation to both licensing boards has been triggered
A newly hired XYZ Engineers project manager who incorporated prior-employer project experience into multi-state qualification proposals with section-level but inconsistent paragraph-level attribution.
- To demonstrate professional value to a new employer by leveraging a strong prior project record while believing that section-level disclosure constitutes sufficient and honest attribution.
An engineering consulting firm whose competitive standing in State Q and State Z procurement may be directly disadvantaged by XYZ Engineers' potentially improper qualification proposal representations.
- To maintain a level competitive playing field in public contract solicitations and support any legitimate ethical or regulatory action that corrects unfair advantages gained through misrepresentation.
State licensing board in State Q whose rules (patterned after NCEES Model Rules) prohibit misrepresentation of facts in solicitation presentations and require licensees to report known or believed violations in writing; potential recipient of Engineer A's mandatory report
State licensing board in State Z whose rules have a unique legislative history and impose more specific attribution requirements, prohibiting unconditional credit claims for prior-employer projects and requiring detailed attribution next to each specific project listing; potential recipient of Engineer A's mandatory report
Engineer A identified that Engineer B and XYZ Engineers may have misrepresented qualifications in proposals submitted in State Q and State Z, evaluated the applicable rules in each jurisdiction, and bears a reporting obligation to the State Z licensing board but not to the State Q licensing board based on the specificity of each jurisdiction's rules.
Engineer B, now employed at XYZ Engineers, included projects completed under a prior employer in qualification proposals submitted in State Q and State Z, providing a general qualifier about prior employment but failing to repeat the attribution adjacent to each specific project listing as required by State Z's rules, constituting misconduct under State Z's licensing board rules.
XYZ Engineers submitted qualification proposals in State Q and State Z that included prior-firm projects of Engineer B without meeting State Z's specific attribution requirements, constituting misconduct by the firm under State Z's licensing board rules.
Engineer Doe was retained to evaluate a manufacturing process change, concluded it would not meet minimum water quality standards, was terminated by the client and asked not to write a report, but bore an obligation to report findings to the applicable regulatory authority regardless of client instructions.
The industry client retained Engineer Doe to evaluate a manufacturing process change, received an unfavorable conclusion, terminated Doe's contract, and instructed Doe not to write a report, thereby triggering Doe's overriding public reporting obligation.
States (10)
Event Timeline (35)
| # | Event | Type |
|---|---|---|
| 1 | The case originates in a professional environment where engineering firms are only partially disclosing the original authors of prior work in their marketing proposals, raising questions about attribution ethics across multiple jurisdictions with differing regulatory standards. | state |
| 2 | Engineer B successfully completes a series of engineering projects, producing a body of professional work and documented experience that will later become central to a dispute over how that work is credited and represented to prospective clients. | action |
| 3 | Engineering firm XYZ brings Engineer B on board as a new hire, gaining access to Engineer B's professional background and prior project portfolio, which the firm subsequently incorporates into its client-facing marketing and proposal materials. | action |
| 4 | XYZ begins submitting proposals to potential clients that reference Engineer B's prior projects without fully or accurately disclosing the context in which that work was performed, creating a misleading impression of the firm's collective experience and capabilities. | action |
| 5 | Engineer A, upon becoming aware of XYZ's proposal practices, undertakes a deliberate review of the firm's marketing materials to determine whether the attribution of prior work meets the ethical and professional standards required of licensed engineers. | action |
| 6 | Engineer A carefully examines the applicable codes of professional conduct, licensing board regulations, and NSPE ethical guidelines to establish a clear framework for evaluating whether XYZ's disclosure practices constitute a violation of professional standards. | action |
| 7 | Concluding that a reportable ethical violation has occurred, Engineer A formally files a complaint with the State Z licensing board, the jurisdiction where the questionable proposals were submitted, initiating an official review of XYZ's marketing conduct. | action |
| 8 | Engineer A makes a deliberate and reasoned decision not to file a parallel complaint with the State Q licensing board, likely determining that State Q lacks sufficient jurisdictional authority or connection to the conduct in question to warrant a separate regulatory action. | action |
| 9 | Engineer B Gains Experience | automatic |
| 10 | XYZ Market Entry Occurs | automatic |
| 11 | Attribution Ambiguity Created | automatic |
| 12 | Competitor Awareness Triggered | automatic |
| 13 | Differential State Rules Discovered | automatic |
| 14 | State Z Violation Established | automatic |
| 15 | BER Precedent Applied | automatic |
| 16 | Tension between Qualification Proposal Misrepresentation Non-Commission Obligation and Maximum Clarity Attribution Constraint Engineer B XYZ Engineers State Q | automatic |
| 17 | Tension between Competitor Qualification Proposal Misconduct Reporting Obligation and Competitor Misconduct Reporting Competitive Interest Neutrality Constraint Engineer A State Z Reporting | automatic |
| 18 | Should Engineer B and XYZ Engineers satisfy their honesty and non-misrepresentation obligations by including prior-employer attribution only in a prefatory notice at the beginning of the qualification section, or by repeating attribution information adjacent to each individual project description throughout the proposal? | decision |
| 19 | Should Engineer A fulfill the mandatory competitor misconduct reporting obligation by reporting XYZ Engineers' attribution practices to the licensing board of State Z — where a specific rule violation is established — while declining to report to the State Q board where no clear rule violation is found, notwithstanding Engineer A's status as a direct commercial competitor? | decision |
| 20 | Should Engineer B and XYZ Engineers fulfill their jurisdiction-specific licensing rule compliance obligation by identifying and applying the specific attribution requirements of each state — including State Z's more stringent project-level attribution rule — when preparing qualification proposals for submission in those jurisdictions, rather than applying a uniform format that satisfies only the less specific State Q standard? | decision |
| 21 | Should Engineer B and XYZ Engineers structure qualification proposals to include prior-employer attribution only in a prefatory section, or must attribution appear adjacent to each individual project description to satisfy the NSPE Code's honesty and transparency obligations? | decision |
| 22 | Should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's attribution standard — State Z's project-level requirement — as the operative benchmark for all qualification proposals, or is it ethically permissible to calibrate disclosure architecture to each state's minimum rule, accepting that the same proposal structure may comply in State Q while violating State Z? | decision |
| 23 | Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or should the reporting obligation be calibrated to the jurisdiction-specific content of each state's rules — reporting only where a clear rule violation is identifiable and declining to report where the applicable rules do not independently prohibit the practice? | decision |
| 24 | Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or include attribution adjacent to each individual project description throughout the proposal body? | decision |
| 25 | Should Engineer A report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z, or limit reporting to only the jurisdiction whose specific rules were clearly violated? | decision |
| 26 | Should XYZ Engineers, as the firm controlling the structure and submission of qualification proposals, adopt the most stringent applicable jurisdiction's attribution standard as the operative benchmark for all proposals, or calibrate disclosure architecture separately to each jurisdiction's minimum rule requirements? | decision |
| 27 | Should Engineer B and XYZ Engineers disclose prior-employer project attribution only in a prefatory section of qualification proposals, or must attribution appear adjacent to each individual project description in order to satisfy the NSPE Code's honesty standard and applicable state licensing rules? | decision |
| 28 | Should Engineer A report XYZ Engineers' attribution practices to the licensing boards of both State Z and State Q, only State Z, or neither — and does Engineer A's status as a direct commercial competitor of XYZ Engineers create a conflict of interest that modifies or voids the mandatory reporting obligation? | decision |
| 29 | When preparing qualification proposals for submission in multiple states with differing attribution specificity requirements, should Engineer B and XYZ Engineers apply the most stringent applicable jurisdiction's project-level attribution standard to all proposals, or may they calibrate disclosure granularity to the minimum required by each individual state's rules? | decision |
| 30 | Should Engineer B and XYZ Engineers include prior-employer project attribution only in a prefatory section of qualification proposals, or repeat it adjacent to each individual project description throughout the proposal body? | decision |
| 31 | Should Engineer A report XYZ Engineers' attribution practice to the licensing board in State Q, given that State Q's rules do not specifically require project-level attribution placement and no clear rule violation is identifiable under State Q's standard? | decision |
| 32 | Should Engineer A conduct an independent, jurisdiction-specific review of the licensing rules of each state in which XYZ Engineers' attribution practice occurred before deciding whether and where to report, rather than relying solely on the NSPE Code of Ethics to assess the conduct? | decision |
| 33 | Should Engineer A review the jurisdiction-specific licensing rules of both State Q and State Z, and report XYZ Engineers' attribution practice to the State Z licensing board given that a specific rule violation is identifiable there but not under State Q's more permissive standard? | decision |
| 34 | Should Engineer B and XYZ Engineers include prior-employer attribution information adjacent to each individual project description in qualification proposals, rather than disclosing it only in a single prefatory section of Engineer B's qualifications, in order to satisfy both the NSPE Code's honesty standard and the more specific attribution requirements of State Z? | decision |
| 35 | The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics. | outcome |
Decision Moments (17)
- Include prior-employer attribution only in a prefatory notice at the beginning of the individual qualification section without repeating it within each project description Actual outcome
- Include prior-employer attribution information adjacent to each individual project description throughout the proposal body in addition to any prefatory notice
- Report XYZ Engineers' attribution practices to the State Z licensing board in writing while declining to report to the State Q board, based on jurisdiction-specific rule analysis Actual outcome
- Refrain from reporting to either state's licensing board on the grounds that Engineer A's status as a direct commercial competitor creates a conflict of interest that undermines the legitimacy of any reporting action
- Report XYZ Engineers' attribution practices to the licensing boards of both State Q and State Z in writing, treating the NSPE Code's general misrepresentation prohibition as sufficient to establish a violation in both jurisdictions
- Apply a uniform proposal format calibrated to the less specific State Q standard, placing prior-employer attribution only in a prefatory notice without reviewing whether State Z imposes more granular requirements
- Identify and apply the specific attribution rules of each jurisdiction before preparing qualification proposals, tailoring proposal format to meet the most stringent applicable state requirement including State Z's project-level attribution rule Actual outcome
- Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description Actual outcome
- Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
- Calibrate proposal attribution architecture to each state's minimum licensing rule, using prefatory-only disclosure where state rules permit it and project-level attribution only where explicitly required Actual outcome
- Adopt the most stringent applicable jurisdiction's attribution standard — project-level attribution adjacent to each project description — as the universal benchmark for all qualification proposals regardless of which state they are submitted in
- Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation under State Z's project-level attribution requirement, while declining to report to the State Q board where no clear rule violation is identifiable Actual outcome
- Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z on the basis that the NSPE Code's general honesty standard is sufficient to establish a violation in both jurisdictions without separately reviewing each state's specific licensing rules
- Decline to report XYZ Engineers' attribution practice to any licensing board, citing Engineer A's status as a direct commercial competitor and the risk that the reporting mechanism would function as an instrument of competitive harm rather than genuine public protection
- Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description Actual outcome
- Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
- Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation, while declining to report to State Q where no equivalent rule violation is established Actual outcome
- Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z on the basis that the NSPE Code's general misrepresentation prohibition applies in both jurisdictions regardless of rule-specific granularity
- Decline to report to either state licensing board on the grounds that Engineer A's status as a direct commercial competitor creates a conflict of interest that disqualifies the reporting action
- Adopt the most stringent applicable jurisdiction's attribution standard — project-level attribution adjacent to each individual project description — as the uniform benchmark for all qualification proposals submitted across all states of practice
- Calibrate the proposal attribution architecture separately to each jurisdiction's minimum rule requirements, using a prefatory-only notice in states with general misrepresentation prohibitions and project-level attribution only in states with explicit granularity requirements Actual outcome
- Include prior-employer attribution notice only in the prefatory section of Engineer B's individual qualification section, without repeating attribution within each project description Actual outcome
- Include prior-employer attribution information immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice
- Report XYZ Engineers' attribution practice to the State Z licensing board only, after reviewing and confirming a specific rule violation under State Z's project-level attribution requirement, and decline to report to State Q where no clear rule violation is established Actual outcome
- Report XYZ Engineers' attribution practice to the licensing boards of both State Z and State Q, treating the NSPE Code's general honesty standard as sufficient to establish a reportable violation in both jurisdictions regardless of the differential specificity of each state's rules
- Decline to report XYZ Engineers' attribution practice to either state licensing board, on the grounds that Engineer A's status as a direct commercial competitor creates a disqualifying conflict of interest that voids the reporting obligation
- Calibrate attribution disclosure granularity to the minimum required by each individual state's licensing rules, using a prefatory-only notice in states with general misrepresentation prohibitions and project-level attribution only where explicitly required by state rules Actual outcome
- Apply the most stringent applicable jurisdiction's project-level attribution requirement as the uniform standard for all qualification proposals submitted across all states, regardless of whether each individual state's rules require that level of specificity
- Disclose prior-employer attribution only in a prefatory section of Engineer B's individual qualification section, without repeating attribution adjacent to each project description Actual outcome
- Include prior-employer attribution notice immediately adjacent to each individual project description throughout the proposal body, in addition to any prefatory section notice
- Decline to report XYZ Engineers' attribution practice to the State Q licensing board after determining that State Q's rules do not specifically prohibit the prefatory-only disclosure structure Actual outcome
- Report XYZ Engineers' attribution practice to the State Q licensing board on the basis that the NSPE Code's general misrepresentation prohibition is sufficient to establish a reportable violation regardless of State Q's rule specificity
- Conduct an independent, jurisdiction-specific review of the licensing board rules of each state in which XYZ Engineers' practice occurred before determining whether and where to report Actual outcome
- Assess XYZ Engineers' attribution practice solely against the NSPE Code of Ethics without separately reviewing the jurisdiction-specific licensing rules of State Q and State Z
- Review the jurisdiction-specific licensing rules of both State Q and State Z, report the identified violation to the State Z licensing board, and decline to report to the State Q board where no specific rule violation is established Actual outcome
- Refrain from reviewing jurisdiction-specific rules and rely solely on the NSPE Code of Ethics to assess XYZ Engineers' conduct, taking no reporting action in either state
- Report XYZ Engineers' attribution practice to the licensing boards of both State Q and State Z without differentiating between the specificity of each state's applicable rules
- Include prior-employer attribution information adjacent to each individual project description throughout the proposal body, in addition to any prefatory notice, to satisfy both the NSPE Code's spirit of honesty and State Z's specific per-project attribution requirement
- Disclose prior-employer attribution only in a single prefatory section of Engineer B's individual qualifications without repeating attribution adjacent to each project description in the proposal body Actual outcome
Sequential action-event relationships. See Analysis tab for action-obligation links.
- Engineer B Completes Prior Projects XYZ Hires Engineer B
- XYZ Hires Engineer B Partial Attribution Disclosure in Proposals
- Partial Attribution Disclosure in Proposals Engineer A Investigates Marketing Practice
- Engineer A Investigates Marketing Practice Engineer A Reviews Applicable Rules
- Engineer A Reviews Applicable Rules Engineer A Reports to State Z Board
- Engineer A Reports to State Z Board Engineer A Declines State Q Report
- Engineer A Declines State Q Report Engineer B Gains Experience
- conflict_1 decision_1
- conflict_1 decision_2
- conflict_1 decision_3
- conflict_1 decision_4
- conflict_1 decision_5
- conflict_1 decision_6
- conflict_1 decision_7
- conflict_1 decision_8
- conflict_1 decision_9
- conflict_1 decision_10
- conflict_1 decision_11
- conflict_1 decision_12
- conflict_1 decision_13
- conflict_1 decision_14
- conflict_1 decision_15
- conflict_1 decision_16
- conflict_1 decision_17
- conflict_2 decision_1
- conflict_2 decision_2
- conflict_2 decision_3
- conflict_2 decision_4
- conflict_2 decision_5
- conflict_2 decision_6
- conflict_2 decision_7
- conflict_2 decision_8
- conflict_2 decision_9
- conflict_2 decision_10
- conflict_2 decision_11
- conflict_2 decision_12
- conflict_2 decision_13
- conflict_2 decision_14
- conflict_2 decision_15
- conflict_2 decision_16
- conflict_2 decision_17
Key Takeaways
- Omitting jurisdiction-specific licensing details in qualification proposals does not automatically constitute misrepresentation if the omission does not materially mislead the client about the firm's ability to perform the work.
- The obligation to report competitor misconduct is complicated when the alleged misconduct is ambiguous or falls below a clear ethical threshold, creating a stalemate between reporting duty and competitive neutrality concerns.
- Engineers operating across multiple jurisdictions must navigate varying licensing disclosure requirements, and a single proposal standard may not satisfy all state-specific rules simultaneously without creating apparent but non-actionable inconsistencies.