Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Duty to Report Misconduct
Step 4 of 5

199

Entities

6

Provisions

2

Precedents

16

Questions

18

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's obligation evolves from an ambiguous ethical question ('is this misleading?') into a clear, jurisdiction-triggered reporting duty; once that duty is discharged by reporting to State Z, responsibility for adjudicating and enforcing the misconduct standard transfers entirely to the State Z Licensing Board. The Code-level ethical assessment (no violation) and the jurisdiction-level legal assessment (violation, reportable) operate on separate tracks, but the Board resolves the case by having jurisdictional rules take precedence for reporting purposes, cleanly reassigning enforcement responsibility away from Engineer A.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (6)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

II.5 board + analysis Engineers shall avoid deceptive acts.
How this applies in the case (showing 3 of 17)
Obligation
Engineer B Prior Project Attribution Duty
Failing to properly attribute prior project roles constitutes a deceptive act.
Action
Qualification Statement Presentation
This provision prohibits deceptive acts in presenting qualifications
State
State Z Presentation Misconduct
Misleading presentation of facts constitutes a deceptive act
Obligation (3)
  • Engineer B Prior Project Attribution Duty
    Failing to properly attribute prior project roles constitutes a deceptive act.
  • Engineer B State Z Attribution Duty
    Misrepresenting project responsibility without proper attribution is a deceptive act.
  • XYZ Engineers State Z Attribution Duty
    Presenting projects without naming Engineer B's actual role is a deceptive act by the firm.
Action (2)
  • Qualification Statement Presentation
    This provision prohibits deceptive acts in presenting qualifications
  • Disclosure Omission
    Omitting information can constitute a deceptive act
State (2)
  • State Z Presentation Misconduct
    Misleading presentation of facts constitutes a deceptive act
  • XYZ Partial Attribution Disclosure
    Partial attribution can be a deceptive act by omission
Principle (3)
  • Honesty in Qualifications Marketing
    This provision bars deceptive acts which directly relates to whether marketing prior work is misleading
  • Honesty in Qualifications Presentation
    Deceptive acts prohibition governs whether stating responsible charge status is honest
  • Transparency in Prior-Project Disclosure
    Avoiding deception requires transparent disclosure of prior employer projects
Role (2)
  • XYZ Engineers Provider Firm
    Its marketing practice is scrutinized for deceptive acts in soliciting clients
  • Engineer B Project Manager
    As the individual whose credentials are presented, deceptive presentation of qualifications governs their conduct
Event (1)
  • Misconduct Constitution
    Deceptive acts by an engineer would constitute the misconduct in question
Resource (2)
  • State Q Licensing Board Rules
    This resource addresses misrepresentation which is a form of deceptive act covered by this provision
  • State Q Rules of Professional Conduct
    This resource addresses misrepresentation which is a form of deceptive act covered by this provision
Capability (2)
  • XYZ Engineers Qualification Representation
    This provision prohibits deceptive presentation of qualifications which relates directly to how XYZ represented Engineer B's prior work
  • Engineer A Misleading Practice Recognition
    Engineer A perceives the marketing practice as potentially deceptive under this provision
II.5.a board + analysis 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.
How this applies in the case (showing 3 of 25)
Obligation
Engineer B Prior Project Attribution Duty
This provision directly prohibits misrepresenting or exaggerating responsibility for prior assignments.
Action
Qualification Statement Presentation
This provision directly governs how qualifications are presented and prohibits misrepresentation
State
State Z Presentation Misconduct
Misrepresenting past accomplishments in presentations directly violates this provision
Obligation (3)
  • Engineer B Prior Project Attribution Duty
    This provision directly prohibits misrepresenting or exaggerating responsibility for prior assignments.
  • Engineer B State Z Attribution Duty
    The duty to describe specific roles corresponds to the prohibition on misrepresenting responsibility in prior work.
  • XYZ Engineers State Z Attribution Duty
    The firm's brochures must not misrepresent facts about past accomplishments or associates' roles.
Action (2)
  • Qualification Statement Presentation
    This provision directly governs how qualifications are presented and prohibits misrepresentation
  • Disclosure Omission
    Omitting responsibility details in qualification statements misrepresents pertinent facts
State (3)
  • State Z Presentation Misconduct
    Misrepresenting past accomplishments in presentations directly violates this provision
  • Engineer B Prior Project Competence
    Exaggerating responsibility for prior assignments relates to misrepresented competence claims
  • XYZ Partial Attribution Disclosure
    Failing to fully attribute past work misrepresents accomplishments
Constraint (2)
  • Engineer B State Z Attribution Boundary
    Prohibits Engineer B from misrepresenting responsibility for prior employer projects without naming actual contributors
  • XYZ Engineers State Z Attribution Boundary
    Prohibits XYZ from misrepresenting past accomplishments in solicitation materials without proper attribution
Principle (4)
  • Honesty in Qualifications Marketing
    This provision specifically prohibits misrepresenting responsibility in prior assignments in marketing materials
  • Honesty in Qualifications Presentation
    Directly addresses misrepresenting responsibility for subject matter of prior assignments
  • Transparency in Prior-Project Disclosure
    Requires accurate disclosure of facts about prior employers and past accomplishments
  • Clarity in Firm Responsibility Differentiation
    Prohibits exaggerating responsibility which requires clear differentiation between firms' roles
Role (2)
  • XYZ Engineers Provider Firm
    Issues qualifications statements that must not misrepresent prior accomplishments of associates
  • Engineer B Project Manager
    Must not permit misrepresentation of their responsibility for prior firm projects
Event (1)
  • Misconduct Constitution
    Misrepresentation of qualifications or responsibility could form the basis of the misconduct
Resource (3)
  • State Q Licensing Board Rules
    This resource directly covers misrepresentation of facts in employment solicitation presentations
  • State Q Rules of Professional Conduct
    This resource directly addresses misrepresentation of past accomplishments in employment solicitations
  • NSPE Code of Ethics
    This resource concerns ethical standards for proposal and marketing practices matching this provisions scope
Capability (5)
  • XYZ Engineers Qualification Representation
    This provision governs whether qualifications statements misrepresent responsibility for prior assignments
  • Engineer B Responsible Charge
    The provision addresses misrepresentation of responsibility which relates to Engineer B's claimed responsible charge experience
  • Engineer B Areas of Expertise
    The provision concerns accurate representation of expertise and prior accomplishments
  • Board of Ethical Review Misrepresentation Threshold Judgment
    The Board applies this provision to judge whether the presentation crossed into misrepresentation
  • Engineer A Misleading Practice Recognition
    Engineer A evaluates XYZ's practice against this misrepresentation standard
III.7 board + analysis 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.
How this applies in the case (showing 3 of 20)
Obligation
Engineer A Violation Reporting Duty
Engineers who believe others are guilty of unethical practice must report to proper authorities.
Action
Ethics Questioning
This provision requires engineers to report believed unethical conduct to proper authorities
State
Mandatory Violation Reporting Requirement
This provision establishes the duty to report unethical conduct to proper authorities
Obligation (3)
  • Engineer A Violation Reporting Duty
    Engineers who believe others are guilty of unethical practice must report to proper authorities.
  • Engineer A State Z Reporting Duty
    This provision requires reporting known unethical or illegal practices to the proper licensing authority.
  • Engineer A Jurisdictional Rules Review Duty
    Determining proper authority for reporting requires understanding jurisdictional rules referenced by this provision.
Action (3)
  • Ethics Questioning
    This provision requires engineers to report believed unethical conduct to proper authorities
  • Reporting Deliberation
    This provision governs the duty to present information about unethical practice to proper authority
  • Board Determination
    The board determination addresses whether the duty to report was fulfilled
State (3)
  • Mandatory Violation Reporting Requirement
    This provision establishes the duty to report unethical conduct to proper authorities
  • Engineer A Ethical Uncertainty
    Engineer A must decide whether to report perceived misconduct under this rule
  • State Q Reporting Obligation Absence
    Addresses whether a reporting obligation exists absent explicit state rules
Principle (1)
  • Jurisdictional Rules Deference in Reporting
    This provision establishes the duty to report unethical practice to proper authorities as applied differently across jurisdictions
Role (2)
  • Engineer A Design Engineer
    Must present belief of unethical practice by another engineer to the proper authority rather than injure reputation directly
  • ABC Consultants Employer
    As Engineer A's employer and competitor it must not maliciously injure a competing firm's reputation
Event (3)
  • Misconduct Constitution
    This provision defines what constitutes unethical or illegal practice by an engineer
  • Reporting Duty Activation
    The provision requires presenting evidence of unethical practice to proper authorities once discovered
  • Reporting Obligation Confirmation
    The provision confirms the affirmative duty to report unethical practice to proper authorities
Resource (2)
  • State Q Licensing Board Rules
    This resource covers reporting of rule violations as required by this provision
  • State Z Licensing Board Rules
    This resource covers reporting of rule violations as required by this provision
Capability (3)
  • Engineer A Board Reporting
    This provision requires reporting believed unethical practice to proper authorities matching Engineer A's reporting capability
  • Engineer A Misleading Practice Recognition
    This provision triggers the duty to report once unethical practice is perceived
  • Engineer A Rules Review
    Engineer A reviews rules to determine if this provision requires reporting action
III.8.a board + analysis Engineers shall conform with state registration laws in the practice of engineering.
How this applies in the case (showing 3 of 14)
Obligation
Engineer A Violation Reporting Duty
This duty stems from the requirement to conform with state registration and licensure laws.
State
Two State Attribution Rules In Force
Requires conformity with applicable state registration and practice laws
Principle
Jurisdictional Rules Deference in Reporting
Requires conformance with state registration laws which vary by jurisdiction
Obligation (2)
  • Engineer A Violation Reporting Duty
    This duty stems from the requirement to conform with state registration and licensure laws.
  • Engineer A State Z Reporting Duty
    Reporting to the state board relates to conformance with state registration laws.
State (2)
  • Two State Attribution Rules In Force
    Requires conformity with applicable state registration and practice laws
  • State Rule Specificity Variation
    Engineers must conform to varying state-specific rules on registration and practice
Principle (1)
  • Jurisdictional Rules Deference in Reporting
    Requires conformance with state registration laws which vary by jurisdiction
Role (2)
  • XYZ Engineers Provider Firm
    Must conform to state registration laws in both states where it practices engineering
  • Engineer B Project Manager
    Must conform with state registration laws in the practice of engineering
Event (2)
  • Rule Divergence Discovery
    Discovering a divergence from registration laws relates to conformance with state licensing requirements
  • Misconduct Constitution
    Failure to conform with state registration laws could constitute the misconduct discovered
Resource (3)
  • State Q Licensing Board Rules
    This resource represents state registration law that engineers must conform to
  • State Z Licensing Board Rules
    This resource represents state registration law that engineers must conform to
  • NCEES Model Rules
    This resource provides model rules for state licensure boards relevant to registration law conformance
Capability (2)
  • Engineer A Board Reporting
    This provision on conforming to state registration laws underlies Engineer A's obligation to report to licensing boards
  • Engineer A Jurisdictional Rules Assessment
    This provision requires conformance with each state's registration laws which Engineer A must assess
III.9 board + analysis Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.
How this applies in the case (showing 3 of 19)
Obligation
Engineer B Prior Project Attribution Duty
Giving credit for engineering work directly relates to proper project attribution.
Action
Qualification Statement Presentation
This provision requires giving credit for engineering work to those responsible
State
XYZ Partial Attribution Disclosure
Directly relates to giving proper credit for engineering work
Obligation (3)
  • Engineer B Prior Project Attribution Duty
    Giving credit for engineering work directly relates to proper project attribution.
  • Engineer B State Z Attribution Duty
    This duty reflects the obligation to recognize proprietary interests and give proper credit.
  • XYZ Engineers State Z Attribution Duty
    The firm must recognize Engineer B's proprietary interest in his prior work.
Action (3)
  • Qualification Statement Presentation
    This provision requires giving credit for engineering work to those responsible
  • Prior Project Execution
    Credit for work performed on prior projects must be properly recognized
  • Disclosure Omission
    Failing to disclose proper credit violates recognition of proprietary interests
State (2)
  • XYZ Partial Attribution Disclosure
    Directly relates to giving proper credit for engineering work
  • Two State Attribution Rules In Force
    Concerns recognition of proprietary interests under differing state attribution rules
Constraint (2)
  • Engineer B State Z Attribution Boundary
    Requires Engineer B to recognize proprietary interests of prior employer and give credit where due
  • XYZ Engineers State Z Attribution Boundary
    Requires XYZ to recognize proprietary interests of the prior employer regarding those projects
Principle (2)
  • Transparency in Prior-Project Disclosure
    Giving proper credit relates to disclosing who did the work and recognizing proprietary interests
  • Clarity in Firm Responsibility Differentiation
    Recognizing proprietary interests of others requires clearly differentiating firm responsibilities
Role (2)
  • XYZ Engineers Provider Firm
    Must give credit for engineering work to those to whom credit is due including the previous firm
  • Engineer B Project Manager
    Must recognize the proprietary interests of the previous employer in prior project credit
Event (1)
  • Misconduct Constitution
    Failing to give proper credit for engineering work could constitute the misconduct at issue
Resource (2)
  • State Z Licensing Board Rules
    This resource addresses credit claims for design projects tied to recognizing proprietary interests
  • State Z Rules of Professional Conduct
    This resource requires attribution of previous firm work reflecting proprietary interest recognition
Capability (2)
  • XYZ Engineers Qualification Representation
    This provision requires giving credit for work which relates to how XYZ credited Engineer B's prior projects
  • Engineer B Prior Firm Credit
    This provision directly requires recognizing proprietary interests which Engineer B fulfilled by crediting the prior firm
III.9.a board + analysis Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments.
How this applies in the case (showing 3 of 17)
Obligation
Engineer B Prior Project Attribution Duty
This provision requires naming individuals responsible for specific designs or work.
Action
Qualification Statement Presentation
This provision requires naming individuals responsible for designs or accomplishments in such statements
State
XYZ Partial Attribution Disclosure
Requires naming individuals responsible for specific work whenever possible
Obligation (3)
  • Engineer B Prior Project Attribution Duty
    This provision requires naming individuals responsible for specific designs or work.
  • Engineer B State Z Attribution Duty
    Naming Engineer B's specific role aligns with the duty to identify individually responsible parties.
  • XYZ Engineers State Z Attribution Duty
    The firm must name Engineer B as individually responsible for his specific contributions.
Action (2)
  • Qualification Statement Presentation
    This provision requires naming individuals responsible for designs or accomplishments in such statements
  • Disclosure Omission
    Omitting the name of the responsible individual violates this naming requirement
State (2)
  • XYZ Partial Attribution Disclosure
    Requires naming individuals responsible for specific work whenever possible
  • State Rule Specificity Variation
    Different states may specify varying levels of required individual attribution
Constraint (2)
  • Engineer B State Z Attribution Boundary
    Requires naming individuals responsible for designs whenever possible, directly establishing the attribution boundary
  • XYZ Engineers State Z Attribution Boundary
    Requires XYZ to name the person individually responsible for prior designs in its listings
Principle (2)
  • Clarity in Firm Responsibility Differentiation
    Naming individually responsible persons directly supports clear differentiation of project responsibility
  • Transparency in Prior-Project Disclosure
    Naming the person responsible for designs relates to transparent disclosure of prior project ownership
Role (1)
  • XYZ Engineers Provider Firm
    Should name the person individually responsible for prior designs whenever possible in its statements
Event (1)
  • Misconduct Constitution
    Not naming those responsible for engineering work could constitute the misconduct identified
Resource (2)
  • State Z Licensing Board Rules
    This resource addresses credit claims for design projects requiring naming of responsible persons
  • State Z Rules of Professional Conduct
    This resource requires attribution of specific roles and previous firm in project listings
Capability (2)
  • XYZ Engineers Qualification Representation
    This provision requires naming individuals responsible for accomplishments relevant to how XYZ presented Engineer B's role
  • Engineer B Prior Firm Credit
    This provision requires naming responsible persons which Engineer B satisfied by crediting his prior firm and clients
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 2 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

An engineer has an obligation to report observations of likely regulatory violations (e.g., failure to meet minimum standards) to the applicable regulatory authority, even when the client objects.

Citation Context:

Cited to establish the general principle that engineers have an obligation to report likely violations or dangers to appropriate regulatory authorities, supporting the broader duty to report analysis.

Relevant Excerpts
discussion: "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."
discussion: "The BER concluded that Doe had an obligation to report Doe's observations to the applicable regulatory authority."

Principle Established:

An engineer has a clear obligation to report information on misconduct to the engineering licensing board, and even an anonymous complaint is ethical and preferable to no report at all, though a signed complaint is better.

Citation Context:

Cited to support the principle that engineers have a clear obligation to report known misconduct to the licensing board, informing the analysis of Engineer A's reporting obligations in the current case.

Relevant Excerpts
discussion: "In BER Case 02-11, Engineer A had provided an anonymous complaint to the engineering licensing board regarding the misconduct of Engineer B."
discussion: "The BER concluded that Engineer A had a clear obligation to report information on misconduct to the engineering licensing board."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 58% Facts Similarity 58% Discussion Similarity 46% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: III.8.a, III.9 Same outcome unethical View Synthesis
Component Similarity 58% Facts Similarity 50% Discussion Similarity 56% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 17% Principle Overlap 72%
Shared provisions: III.7 Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 60% Discussion Similarity 64% Provision Overlap 11% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 67%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 50% Facts Similarity 53% Discussion Similarity 63% Provision Overlap 9% Outcome Alignment 100% Tag Overlap 30% Principle Overlap 72%
Shared provisions: III.8.a Same outcome unethical View Synthesis
Component Similarity 50% Facts Similarity 50% Discussion Similarity 63% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 52%
Shared provisions: III.9 Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 58% Discussion Similarity 55% Provision Overlap 10% Outcome Alignment 100% Tag Overlap 10% Principle Overlap 66%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 57% Facts Similarity 62% Discussion Similarity 51% Outcome Alignment 100% Tag Overlap 27% Principle Overlap 64%
Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 53% Discussion Similarity 57% Provision Overlap 10% Outcome Alignment 100% Tag Overlap 10% Principle Overlap 65%
Shared provisions: III.8.a Same outcome unethical View Synthesis
Component Similarity 61% Facts Similarity 52% Discussion Similarity 59% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 50%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 60% Discussion Similarity 53% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 9% Principle Overlap 62%
Shared provisions: III.7 Same outcome unethical View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Are the proposal techniques of Engineer B ethical with respect to the NSPE Code of Ethics?

Board conclusion The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.
Resolved by: The general duty to give credit and avoid deceptive acts (III.9, II.5) was satisfied by the section-level disclosure, so no competing obligation was actually triggered under the Code's broader threshold. (confidence 0.75)
II.5. II.5.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative
Also discussed in: C101
Implicit (3)

Does the fact that Engineer B's disclosure notice appears only at the beginning of each individual project section, rather than in every paragraph, create a meaningful risk that a reader skimming later paragraphs would be misled about which firm performed the work?

AnalyticalThe Board's reasoning implicitly treats the disclosure notice's placement 'at the beginning of an individual qualification section' as adequate to establish overall intent toward transparency, even though it is absent from many paragraphs of the lengthy project descriptions. This suggests the Board views the omission as a matter of degree rather than kind: a partial or front-loaded disclosure is ethically distinguishable from a complete absence of disclosure, even if it falls short of the specific completeness required by State Z. A reader skimming only later paragraphs of a long project description could reasonably come away believing XYZ Engineers, rather than Engineer B's prior employer, performed the work — a risk the Board's ethics analysis does not explicitly weigh, even though it is precisely the risk State Z's rule is designed to foreclose.
Resolved by: The Board implicitly weighed the presence of any disclosure more heavily than the specific misreading risk in later paragraphs, treating the shortfall as a matter of degree rather than outright deception. (confidence 0.70)
II.5. II.5.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative
AnalyticalQ101: There is a genuine practical risk that a reader who skims past the introductory notice in each project section could lose track of which firm actually performed the work, since the lengthy paragraph-by-paragraph descriptions do not repeat the attribution. However, because the qualifications statement as a whole clearly discloses Engineer B's prior employer and client at the point where each project is introduced, the Board evidently viewed this as a design/formatting weakness rather than a deceptive act rising to the level of an NSPE Code violation. The risk is real but was judged insufficient, standing alone, to constitute unethical misrepresentation under the Code's general standard.
Resolved by: The Board weighed the real risk of a skimming reader losing track of attribution against the sufficiency of a clear disclosure at the point of introduction, and found the latter controlling under the Code's general honesty standard. (confidence 0.75)
II.5. II.5.a. III.9.a. 3 principles 3 facts Conditions Narrative

Should organizational responsibility for the proposal's compliance rest with XYZ Engineers as a firm, rather than solely with Engineer B as the individual whose credentials are described?

Also discussed in: C102

Given that identical conduct is ethically acceptable under the general NSPE Code language but constitutes reportable misconduct under State Z's specific rules, does this reveal a gap in the NSPE Code's ability to address nuanced credit-attribution practices?

AnalyticalThe Board's divergent conclusions for State Q and State Z reveal an important structural point: satisfying the general NSPE Code standard against deceptive acts and misrepresentation (II.5, II.5.a) does not guarantee compliance with more granular, jurisdiction-specific attribution rules. Engineer B's practice of disclosing prior-employer attribution only at the start of each project section arguably meets the Code's broader 'avoid deceptive acts' threshold and even State Q's NCEES-style general misrepresentation standard, because a reasonably attentive reader encountering the section header would not be deceived about overall authorship. However, State Z's rule requires attribution information to appear specifically 'next to the specific project listing,' a paragraph-level granularity that front-loaded disclosure does not satisfy. This shows that ethical sufficiency under a principles-based code is a necessary but not sufficient condition for regulatory compliance where a jurisdiction has codified more precise disclosure mechanics.
Resolved by: The Board treated Code compliance and jurisdiction-specific compliance as layered rather than competing requirements, meaning satisfying one does not discharge the other. (confidence 0.75)
II.5. II.5.a. III.8.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative
AnalyticalQ104: The case does expose a structural gap in the NSPE Code of Ethics. The Code's provisions on credit and honesty (II.5.a., III.9., III.9.a.) are framed in general terms that a section-level attribution notice can satisfy, whereas State Z's licensure rules impose a specific, granular requirement (attribution 'next to the specific project listing'). Because identical conduct can be Code-compliant yet independently constitute reportable misconduct under a jurisdiction's more detailed rules, the Code functions as a floor of general ethical practice rather than a substitute for jurisdiction-specific technical compliance standards.
Resolved by: The Board resolved the apparent tension by ranking the norms hierarchically, treating the Code as a general floor and jurisdiction-specific rules as an independent, stricter layer that must also be satisfied. (confidence 0.78)
II.5.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative
Principle tension (2)

How should Honesty in Qualifications Marketing under the NSPE Code be reconciled with Jurisdictional Rules Deference in Reporting, given that the same proposal practice is judged ethical under the Code yet constitutes misconduct under State Z's specific licensing rules?

AnalyticalQ201: Honesty in Qualifications Marketing and Jurisdictional Rules Deference in Reporting are not in true conflict; they operate at different normative levels. The NSPE Code sets a general honesty benchmark that XYZ Engineers' proposal practice met, while State Z's rules impose an additional, more exacting technical requirement tied to licensure law rather than general ethics. Jurisdictional deference does not undermine the Code's honesty principle; it supplements it, requiring engineers to comply with whichever standard is stricter within a given jurisdiction, even where the Code alone would not find fault.
Resolved by: The Board reconciled the two principles not as competitors but as operating at different normative levels, requiring compliance with the stricter of the two rather than treating satisfaction of one as excusing failure of the other. (confidence 0.76)
II.5.a. III.8.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe case demonstrates that Jurisdictional Rules Deference in Reporting ultimately takes priority over Honesty in Qualifications Marketing once a specific jurisdictional rule exists, because the reporting obligation is triggered by rule violation rather than by an independent ethical judgment of deception. Engineer A's duty to report in State Z, despite the Board's finding that the marketing practice was not unethical under the Code, shows that reporting obligations are procedurally derivative of positive law, not of the reviewer's own ethical assessment. This suggests a broader lesson: NSPE Code principles govern the ethics of the underlying conduct, while separate reporting duties are governed strictly by the letter of applicable licensure rules, and the two must be evaluated on independent tracks rather than merged into a single ethical determination.
Resolved by: The Board subordinated the ethical assessment of the marketing conduct to the procedural reporting obligation, holding that the duty to report is activated by positive law rather than by the reviewer's own ethical conclusion. (confidence 0.77)
III.8.a. III.9.a. 2 principles 3 facts Conditions Narrative

Does Transparency in Prior-Project Disclosure conflict with Clarity in Firm Responsibility Differentiation when a disclosure notice is placed only at the start of a lengthy project description rather than repeated throughout, potentially leaving parts of the description unclear as to attribution?

AnalyticalTransparency in Prior-Project Disclosure and Clarity in Firm Responsibility Differentiation were only partially reconciled by Engineer B's practice: placing an attribution notice at the start of each project section provided enough transparency to avoid outright deception under the Code's general 'avoid deceptive acts' standard, but did not achieve full clarity of responsibility throughout the lengthy descriptions. The Board's differing outcomes for State Q and State Z suggest that where a jurisdiction has not codified a specific clarity requirement, partial disclosure is ethically tolerable, but where a jurisdiction (State Z) has elevated clarity of firm responsibility into an explicit, itemized rule, the same partial disclosure becomes noncompliant. Principle prioritization here is context-dependent: transparency principles yield to whatever specificity the governing rule structure demands.
Resolved by: The Board balanced general transparency (satisfied by an upfront disclosure) against a jurisdiction-specific clarity rule, letting the specificity of the governing rule determine which principle controls in each state. (confidence 0.75)
II.5. III.9. III.9.a. III.8.a. 2 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer B fulfill the duty under Code provision III.9.a to name the person or persons individually responsible for prior project work, given that the attribution notice was omitted from many paragraphs of the lengthy project descriptions?

AnalyticalQ301: Viewed deontologically, Engineer B arguably discharged the duty in III.9.a. at a minimal level by naming the prior employer and client at the outset of each project's description, thereby identifying who was 'individually responsible' for that work. However, the duty's spirit implies consistent, unambiguous attribution throughout a description, not merely at its start. The repeated omission in later paragraphs represents an incomplete fulfillment of the duty's full intent, even though the Board found this incompleteness did not breach the Code's general honesty standard.
Resolved by: The Board weighed minimal, literal compliance with III.9.a.'s naming duty against the provision's fuller spirit of continuous unambiguous attribution, and let the minimal literal compliance control for Code-violation purposes. (confidence 0.74)
III.9.a. III.9. II.5.a. 3 principles 3 facts Conditions Narrative

From a consequentialist perspective, did the fact that clients could still discern Engineer B's true role (because attribution appeared at the start of each project section) justify the incomplete paragraph-by-paragraph disclosure, even though it fell short of full transparency?

AnalyticalQ302: From a consequentialist standpoint, the placement of the attribution notice at the start of each project section produced an acceptable outcome: a reasonably attentive client would still be informed of Engineer B's true role and prior employer before reading the detailed narrative. Because the practical effect was that clients could discern the truth despite imperfect repetition, the outcome-based reasoning supports the Board's conclusion that the practice was not unethical under the NSPE Code, even though a stricter transparency standard (as applied in State Z) treats the same incomplete disclosure as misconduct regardless of ultimate client comprehension.
Resolved by: The Board weighed the practical sufficiency of client comprehension (consequentialist outcome) against the stricter formal completeness demanded by State Z, and let the NSPE Code determination rest on outcome adequacy while treating the State Z violation as a separate jurisdictional matter. (confidence 0.75)
II.5. II.5.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative

Did Engineer B act with professional integrity, in the virtue-ethical sense, by only partially and inconsistently disclosing prior-employer attribution across the qualification statement, rather than adopting a uniformly transparent presentation style?

Counterfactual (1)

If Engineer B's prior projects had involved proprietary design concepts (rather than not involving them), would the Board still have concluded that Engineer B's proposal practices were not unethical under the NSPE Code of Ethics?

AnalyticalQ401: Had Engineer B's prior projects involved proprietary design concepts, the Board would likely have reached a different result under the NSPE Code itself. Marketing proprietary content developed for a previous employer without clear limitation could implicate additional confidentiality and fair competition concerns beyond mere credit attribution, potentially violating provisions safeguarding a firm's exclusive design work and injuring the previous employer's professional interests. The absence of proprietary content in this case was a material fact supporting the Board's no-violation conclusion.
Resolved by: The Board balanced the individual's interest in marketing legitimate prior experience against the previous employer's proprietary and competitive interests, finding no conflict only because proprietary content was factually absent. (confidence 0.80)
III.7. III.9. II.5.a. 2 principles 3 facts Conditions Narrative
Board Board question 2

Does Engineer A have an obligation to report a violation to the Engineering Licensing Board in State Q? In State Z?

Board conclusion Engineer B’s proposal/marketing practices would constitute professional misconduct per licensure law in State Z, and Engineer A has a clear obligation to report to the engineering licensing board in State Z.
Resolved by: The obligation to conform to State Z's specific registration law (III.8.a) overrode the fact that the same conduct satisfied the Code's general standard, making the mandatory reporting duty controlling. (confidence 0.85)
III.8.a. III.9. III.9.a. 3 principles 3 facts Conditions Narrative
Board conclusion Engineer A does not have an obligation to report Engineer B’s proposal/marketing practices to the engineering licensing board in State Q.
Resolved by: Because no violation existed under State Q's general standard, the mandatory reporting obligation was never activated, so there was no competing duty to weigh. (confidence 0.80)
II.5. II.5.a. III.8.a. 2 principles 3 facts Conditions Narrative
Implicit (1)

Does Engineer A's position as an employee of a direct competitor (ABC Consultants) raise a question about motive or conflict of interest in reviewing and potentially reporting on Engineer B's marketing practices, even though it does not negate the reporting duty in State Z?

AnalyticalThe Board's conclusion that Engineer A has a clear reporting obligation to State Z does not address the potential appearance of self-interest arising from Engineer A's employment at ABC Consultants, a direct competitor of XYZ Engineers. While the Code's reporting duty is triggered by objective knowledge of a rule violation and is not negated by the reporter's competitive position, the Board's silence on this point leaves open a practical concern: Engineer A's report could be perceived as competitively motivated, which may affect how the State Z Board weighs or investigates the complaint, even though it does not affect whether Engineer A is ethically obligated to report.
Resolved by: The Board treated the objective, fact-based duty to report as controlling and did not let the subjective appearance of competitive motive negate it, while leaving the perception issue as an unresolved practical concern for the receiving board. (confidence 0.72)
III.7. 1 principle 3 facts Conditions Narrative
AnalyticalQ103: Engineer A's employment by a direct competitor does not negate the reporting duty established for State Z, since that duty is grounded in the mandatory reporting rules of the licensing board rather than in Engineer A's personal interest. Nonetheless, the competitive relationship is a relevant contextual factor that underscores the importance of Engineer A basing any report strictly on the documented rule violation rather than on competitive motive, preserving the integrity and credibility of the report to the Board of Licensure.
Resolved by: The Board weighed the risk that competitive motive could taint the report against the independent, rule-based origin of the reporting duty, concluding the duty stands but must be exercised with care to preserve credibility. (confidence 0.85)
III.7. III.8.a. 2 principles 3 facts Conditions Narrative
Principle tension (1)

How should Honesty in Qualifications Presentation, which the Board found satisfied under the general NSPE Code, be balanced against Jurisdictional Rules Deference in Reporting, which requires Engineer A to report the same conduct as misconduct in State Z?

AnalyticalThis case reveals that Honesty in Qualifications Presentation and Jurisdictional Rules Deference in Reporting are not truly in conflict but operate on different normative levels: the NSPE Code sets a general, minimum threshold of non-deception, while State Z's rules impose a stricter, technical attribution standard. The Board resolved the apparent tension not by ranking one principle over the other, but by treating them as independently binding—Engineer B's conduct can simultaneously satisfy the looser Code standard and fail the stricter jurisdictional rule. This shows that jurisdictional compliance is not reducible to Code compliance, and that engineers (and reviewers) must apply both frameworks separately rather than assuming that clearing the ethical bar automatically clears every legal bar.
Resolved by: The Board treated the Code standard and the jurisdictional rule as independently binding norms operating at different levels of specificity rather than ranking one above the other. (confidence 0.78)
II.5. III.8.a. III.9.a. 2 principles 3 facts Conditions Narrative
Theoretical (1)

From a deontological perspective, did Engineer A fulfill the duty to defer to jurisdiction-specific licensure rules by reaching different reporting conclusions for State Q and State Z despite reviewing the same underlying marketing practice?

Also discussed in: C303
Counterfactual (2)

If Engineer B's attribution notice identifying the prior employer and client had appeared in every paragraph of the lengthy individual project descriptions (rather than only at the beginning of each section), would the Board still have found that the practice constituted professional misconduct requiring a report to the State Z Licensing Board?

AnalyticalQ402: If the attribution notice had appeared in every paragraph of each lengthy project description, Engineer B's practice would very likely have satisfied State Z's specific requirement that detailed attribution appear 'next to the specific project listing.' In that scenario, the factual predicate for the Board's misconduct finding would be absent, and Engineer A would have no clear obligation to report to the State Z Licensing Board, since the deficiency triggering reportability was precisely the inconsistency of disclosure across paragraphs rather than the underlying practice of listing prior-firm experience.
Resolved by: The Board weighed the formal textual requirement of State Z's rule against the practical adequacy of a single upfront disclosure, concluding that satisfying the literal repetition requirement would have removed the factual basis for any reporting obligation. (confidence 0.80)
III.9. III.9.a. 2 principles 3 facts Conditions Narrative

If State Z's licensure rules had been as general as State Q's (patterned after the NCEES Model Rules' broad misrepresentation standard) rather than containing specific attribution requirements, would the Board still have concluded that Engineer A had a clear obligation to report to the State Z Licensing Board?

AnalyticalQ403: If State Z's rules had mirrored State Q's general NCEES-style misrepresentation standard rather than containing detailed attribution requirements, the Board would likely have reached the same conclusion for both states: no clear reporting obligation, mirroring its State Q determination. The Board's finding of a clear reporting duty in State Z depended specifically on the jurisdiction's unique, granular rule language mandating attribution 'next to the specific project listing,' a textual requirement that State Q's broader standard does not impose.
Resolved by: The Board weighed the specificity of the governing rule text against the general misrepresentation standard, concluding that the reporting obligation tracks the granularity of the jurisdiction's rule rather than the underlying conduct itself. (confidence 0.80)
III.8.a. II.5.a. 2 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer B repeat detailed attribution of the previous firm and his specific role next to every project listing throughout the qualifications statement, or provide a single disclosure notice at the start of each project section?

Options considered:
O1 Name the previous firm and Engineer B's specific role next to each individual project listing and throughout each lengthy project description, satisfying State Z's granular rule. Board's choice
O2 Disclose the prior employer and client once at the beginning of each project section, relying on that initial notice to carry through the rest of the description, as Engineer B actually did.
O3 Present the prior-firm projects as part of Engineer B's general experience without naming the previous firm or client at all.
Argument structure (Toulmin):
Grounds

The qualifications statement named Engineer B's prior employer and the associated client once at the beginning of each project section, but the lengthy paragraph-by-paragraph project descriptions that followed did not repeat that attribution.

Warrant

Engineers must give proper credit for engineering work and must not misrepresent facts concerning past accomplishments; State Z's rule specifically requires attribution to appear next to each specific project listing, which prevails over front-loaded disclosure once codified.

Rebuttal

The claim would not apply if the project sections were short enough that a reader naturally carried the initial disclosure through the entire section, or if the jurisdiction's rule (as in State Q) only required a general, non-itemized disclosure.

Engineer B State Z Attribution Duty

Should Engineer A report Engineer B and XYZ Engineers' proposal practices to the licensing boards in both State Q and State Z, to State Z only, or refrain from reporting to either?

Options considered:
O1 Report the qualifications practice to the State Z licensing board, where it constitutes a specific rule violation, while not reporting to State Q, where no violation was found. Board's choice
O2 Report the same conduct to both the State Q and State Z licensing boards regardless of the differing rule text in each jurisdiction.
O3 Decline to report the conduct to any licensing board, treating the front-loaded disclosure practice as ethically acceptable everywhere.
Argument structure (Toulmin):
Grounds

State Q's rules track the general NCEES misrepresentation standard, which Engineer B's disclosure practice satisfied; State Z's rules specifically require attribution next to each project listing, which the same practice did not satisfy.

Warrant

Engineers have a duty to report known violations of licensing board rules to the cognizant board, but that duty is triggered only where an actual rule violation exists in that jurisdiction; jurisdictional rules deference governs which board's rule applies.

Rebuttal

The claim would not apply if State Q's rules were shown to contain a specific attribution requirement comparable to State Z's, or if State Z's rule were as general as State Q's, in which case no clear reporting duty would arise there either.

Engineer A State Z Reporting Duty

Should Engineer A individually review the specific Rules of Professional Conduct in each jurisdiction where Engineer B and XYZ Engineers practice, or rely on a single uniform reading of the NSPE Code to decide whether to report?

Options considered:
O1 Examine the specific Rules of Professional Conduct in both State Q and State Z individually before forming any conclusion about reportability. Board's choice
O2 Judge the conduct solely against the general NSPE Code's honesty and misrepresentation provisions without separately checking each state's specific licensing rules.
O3 Presume that State Q's and State Z's rules are substantially equivalent and reach a single conclusion applicable to both without detailed comparison.
Argument structure (Toulmin):
Grounds

The same qualifications-statement practice was governed by materially different rule text in State Q and State Z, one general and one specific to attribution placement.

Warrant

Because licensing rules vary by jurisdiction, an engineer considering whether to report misconduct must consult the specific rules of each relevant jurisdiction rather than assume uniform standards; only a jurisdiction-specific review can correctly establish whether a violation exists.

Rebuttal

The claim would not apply if all relevant jurisdictions were known to share identical rule language, making a single uniform review sufficient.

Engineer A Jurisdictional Rules Review Duty

Should XYZ Engineers implement firm-wide review procedures to ensure attribution of prior-firm work is compliant in every qualifications statement it issues, or leave that responsibility to Engineer B alone as the credentialed individual?

Options considered:
O1 Adopt a firm-level review process ensuring every qualifications statement issued by XYZ Engineers meets each jurisdiction's attribution requirements before submission. Board's choice
O2 Leave attribution accuracy entirely to Engineer B's personal judgment about how to describe his own prior work, without separate firm-level oversight.
O3 Establish a shared review process where Engineer B drafts attribution language and a firm quality-assurance reviewer checks it against jurisdictional rules before the statement is issued.
Argument structure (Toulmin):
Grounds

The proposal was issued in XYZ Engineers' name and marketed Engineer B's prior-firm projects as part of the firm's collective qualifications to prospective clients.

Warrant

A firm that markets an employee's credentials to clients bears responsibility for the accuracy and completeness of that marketing material, just as the individual engineer bears responsibility for the underlying factual claims about his own role.

Rebuttal

The claim would not apply if XYZ Engineers had no supervisory or drafting role in the qualifications statement and Engineer B alone controlled its content and submission.

XYZ Engineers State Z Attribution Duty

Should Engineer A report the documented State Z rule violation directly to the licensing board, or first take steps to address the appearance of competitive motive, such as disclosing his employer relationship or declining to report?

Options considered:
O1 Submit the report to the State Z licensing board based strictly on the factual attribution deficiency, without altering the process due to Engineer A's competitive employment. Board's choice
O2 Refrain from reporting the violation because Engineer A's employment at a direct competitor could create an appearance of self-interested motive.
O3 Submit the report to the State Z board while proactively disclosing Engineer A's employment at a competing firm, to preserve the credibility and transparency of the complaint.
Argument structure (Toulmin):
Grounds

Engineer A works for ABC Consultants, a direct competitor of XYZ Engineers, and became aware of the attribution deficiency while reviewing XYZ Engineers' proposal against a competing bid.

Warrant

The duty to report known violations to a licensing board is grounded in objective knowledge of a rule violation and is not negated or created by the reporter's competitive position; engineers must act with fairness and avoid conduct that could improperly injure another's professional reputation through motive-based reporting.

Rebuttal

The claim would not apply if Engineer A were shown to have fabricated or distorted the facts to injure a competitor, rather than accurately relaying an objectively verifiable rule violation.

Engineer A State Z Reporting Duty
Event Timeline (12)
12 sequenced 8 actions 4 events
Case timeline
Engineer B, while in previous employment at another firm, completed non-proprietary bridge and culvert projects in responsible charge, projects that later became the basis of experience claims in XYZ's proposals.
Causal-normative reasoning(confidence 0.55)
Prior Project Execution establishes the track record and qualifications that XYZ Engineers later relied on when assembling its statement of qualifications, so although it carries no direct normative edges, it is the factual foundation whose selective use downstream becomes ethically fraught.
XYZ Engineers hired Engineer B as a new project manager and began marketing bridge and culvert designs in both State Q and State Z in competition with ABC Consultants.
Causal-normative reasoning(confidence 0.70)
Project Manager Hiring sets in motion the causal chain toward Qualification Statement Presentation and eventually Disclosure Omission, so even though it is not itself judged as fulfilling or violating a duty, its outcome (a new hire whose prior role is not disclosed) is what makes the later omission ethically significant.
XYZ Engineers and Engineer B presented qualification statements attributing Engineer B's prior projects to the previous employer at the beginning of the individual qualification section, identifying the prior employer and the associated client for each project.
Fulfills (1)
  • Credit to Proprietary Interests of Previous Employer
Causal-normative reasoning(confidence 0.70)
Although presenting the qualification statement fulfills the duty to credit the previous employer's proprietary interests and is guided by transparency, it is the direct causal precursor to the disclosure omission, showing that even a well-intentioned, obligation-fulfilling act can set up a later lapse in required disclosure.
XYZ Engineers and Engineer B did not repeat the prior-employer attribution notice within all paragraphs of the lengthy individual project descriptions, a non-performance the case treats as the conduct that violates State Z's specific rules.
Violates (2)
  • State Z Attribution Requirement
  • Avoidance of Misrepresentation of Qualifications
Causal-normative reasoning(confidence 0.85)
The disclosure omission violates both the State Z attribution requirement and the duty to avoid misrepresenting qualifications, and this violation is what causes Engineer A to question the ethics, review the code, discover the rule divergence, and ultimately activates the reporting duty that leads to the Board's confirmation, making it the pivotal wrongful act driving the entire causal chain.
State changes (1)
  • began: State Z Presentation Misconduct
Under State Z's specific rule requiring the previous firm and the licensee's role to appear next to each project listing, the qualification statement's noncompliance automatically constituted misconduct by both Engineer B and XYZ Engineers once the presentation failed to meet the rule's specifics.
State changes (1)
  • began: State Z Presentation Misconduct
Engineer A questioned whether XYZ's proposal and marketing practice was misleading to clients and unethical, initiating the ethical inquiry of the case.
Causal-normative reasoning(confidence 0.80)
Ethics Questioning is guided by Transparency because Engineer A's decision to interrogate the Disclosure Omission is what initiates the Code and Rules Review, showing that a commitment to openness is the normative driver that turns a suspected problem into a formal investigation.
State changes (1)
  • began: Engineer A Ethical Uncertainty
Engineer A decided to review the NSPE Code of Ethics and the engineering licensing board laws and rules of professional conduct in both State Q and State Z, finding State Q's rules general and State Z's rules highly specific.
Causal-normative reasoning(confidence 0.70)
Code and Rules Review has no explicit guiding principle recorded, yet it causally produces the Rule Divergence Discovery that reveals the gap between actual practice and code requirements, making it the evidentiary link between Engineer A's ethical suspicion and the eventual finding of misconduct.
State changes (1)
  • began: State Rule Specificity Variation
During the review of licensing rules, it emerges that State Q's rules are general and patterned after the NCEES Model Rules while State Z's rules are much more specific about crediting prior projects, creating awareness that the same practice may be treated differently in the two jurisdictions.
State changes (1)
  • began: State Rule Specificity Variation
Because the rules in both states require a licensee with knowledge or reason to believe a violation has occurred to report it in writing, Engineer A's acquired knowledge of the State Z rule violation automatically triggered the applicability of the written reporting requirement.
Engineer A considered whether the proposal and marketing practice was unethical under the NSPE Code of Ethics and whether there was an obligation to report to the two licensing jurisdictions, the pending decision the case poses.
Causal-normative reasoning(confidence 0.80)
Reporting Deliberation is guided by the Duty to Report Violations because it follows directly from the Reporting Duty Activation triggered by the Misconduct Constitution, so Engineer A's deliberation is the normative response required once the omission is established as a rule violation, ultimately validated by the Board's Reporting Obligation Confirmation.
The BER determined that Engineer A had no obligation to report to the State Q licensing board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to the State Z licensing board under that state's specific rules.
Causal-normative reasoning(confidence 0.75)
Because the Board's determination is guided by the Duty to Report Violations, it functions as the authoritative act that confirms the reporting obligation triggered earlier by the misconduct, giving downstream legitimacy to Engineer A's decision to report.
The BER's determination resulted in the conclusions that Engineer A had no obligation to report to State Q's board because the presentation did not rise to misrepresentation, but has a clear obligation to report the misconduct to State Z's licensing board.
State changes (2)
  • began: State Q Reporting Obligation Absence
  • ended: Engineer A Ethical Uncertainty
Narrative (6 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer A, an employee of ABC Consultants, where you design bridges and culverts in both State Q and State Z. A competing firm, XYZ Engineers, recently hired Engineer B as project manager, and XYZ has begun marketing bridge and culvert design services in both states using qualifications statements that include Engineer B's prior project experience. Those statements name Engineer B's previous employer and the associated clients at the start of each individual qualifications section, but this attribution is not repeated in every paragraph of the lengthy project descriptions that follow, even though the projects themselves are clearly listed in the body of the proposal. You have started reviewing the NSPE Code of Ethics along with the licensing board rules of both State Q and State Z, noting that State Q's rules follow the NCEES Model Rules while State Z's rules differ in some respects, and both states require licensees to report known violations of the rules of professional conduct. You must now work through how to interpret these rules and what steps, if any, to take regarding XYZ's proposal practices.

Main characters (6)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer A Roles in this case: Design Engineer

Guided by: Honesty in Qualifications Marketing, Transparency in Prior-Project Disclosure, Honesty in Qualifications Presentation

Engineer A's duty to report a suspected violation promptly can be in tension with the duty to first review the differing jurisdictional rules of the licensing boards involved. Acting quickly on a report risks misapplying rules from the wrong jurisdiction, while pausing to research jurisdictional nuances risks delaying a report that ethics codes generally expect to be made without undue delay.

Engineer B Roles in this case: Project Manager

Engineer B has an obligation to properly attribute prior project work performed under a previous employer, but is constrained by State Z rules limiting how that prior work can be represented or claimed when marketing new projects. This creates tension between giving full professional credit and staying within permitted bounds of attribution in a new jurisdiction.

XYZ Engineers Roles in this case: EmployerProvider Firm

Engineer B has an obligation to properly attribute prior project work performed under a previous employer, but is constrained by State Z rules limiting how that prior work can be represented or claimed when marketing new projects. This creates tension between giving full professional credit and staying within permitted bounds of attribution in a new jurisdiction.

Attaches to role: Employer

XYZ Engineers as a firm has an obligation to attribute prior work performed by its personnel in State Z to the correct firm and individuals, but is simultaneously bound by State Z rules constraining what can be claimed in promotional or qualification materials. This tension can lead to underclaiming legitimate experience or overstepping permitted representation, risking both misrepresentation to prospective clients and unfair loss of deserved credit.

Attaches to role: Employer
ABC Consultants Roles in this case: Employer
State Q Roles in this case: Licensing Board

Engineer A's duty to report a suspected violation promptly can be in tension with the duty to first review the differing jurisdictional rules of the licensing boards involved. Acting quickly on a report risks misapplying rules from the wrong jurisdiction, while pausing to research jurisdictional nuances risks delaying a report that ethics codes generally expect to be made without undue delay.

State Z Roles in this case: Licensing Board

Engineer A's duty to report a suspected violation promptly can be in tension with the duty to first review the differing jurisdictional rules of the licensing boards involved. Acting quickly on a report risks misapplying rules from the wrong jurisdiction, while pausing to research jurisdictional nuances risks delaying a report that ethics codes generally expect to be made without undue delay.

Engineer B has an obligation to properly attribute prior project work performed under a previous employer, but is constrained by State Z rules limiting how that prior work can be represented or claimed when marketing new projects. This creates tension between giving full professional credit and staying within permitted bounds of attribution in a new jurisdiction.

XYZ Engineers as a firm has an obligation to attribute prior work performed by its personnel in State Z to the correct firm and individuals, but is simultaneously bound by State Z rules constraining what can be claimed in promotional or qualification materials. This tension can lead to underclaiming legitimate experience or overstepping permitted representation, risking both misrepresentation to prospective clients and unfair loss of deserved credit.

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

Engineer B has an obligation to properly attribute prior project work performed under a previous employer, but is constrained by State Z rules limiting how that prior work can be represented or claimed when marketing new projects. This creates tension between giving full professional credit and staying within permitted bounds of attribution in a new jurisdiction.

XYZ Engineers as a firm has an obligation to attribute prior work performed by its personnel in State Z to the correct firm and individuals, but is simultaneously bound by State Z rules constraining what can be claimed in promotional or qualification materials. This tension can lead to underclaiming legitimate experience or overstepping permitted representation, risking both misrepresentation to prospective clients and unfair loss of deserved credit.

Engineer B has an obligation to properly attribute prior project work performed under a previous employer, but is constrained by State Z rules limiting how that prior work can be represented or claimed when marketing new projects. This creates tension between giving full professional credit and staying within permitted bounds of attribution in a new jurisdiction.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

The proposal practices of Engineer B and XYZ Engineers were not unethical from the perspective of the NSPE Code of Ethics.
Engineer A does not have an obligation to report Engineer B’s proposal/marketing practices to the engineering licensing board in State Q.
Engineer B’s proposal/marketing practices would constitute professional misconduct per licensure law in State Z, and Engineer A has a clear obligation to report to the engineering licensing board in State Z.
Opening States (8)
XYZ Partial Attribution Disclosure Two State Attribution Rules In Force Mandatory Violation Reporting Requirement Engineer A Ethical Uncertainty State Z Presentation Misconduct State Rule Specificity Variation Engineer B Prior Project Competence State Q Reporting Obligation Absence
Summary
  • Properly attributing prior project experience to the firm and individuals who actually performed it is generally permissible and can be ethical even when the individual has since changed employers or jurisdictions.
  • Jurisdictional licensing board rules can legitimately constrain how prior work experience is marketed or claimed, but such constraints do not automatically render truthful attribution unethical under the NSPE Code.
  • Firms and individuals can satisfy both the duty of honest representation of qualifications and jurisdiction specific marketing restrictions simultaneously, provided the claims remain accurate and appropriately bounded.

© Licensed under the GNU GPL v3