Step 4: Review

Engineers shall avoid deceptive acts.

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.

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.

Engineers shall conform with state registration laws in the practice of engineering.

Engineers shall give credit for engineering work to those to whom credit is due, and will recognize the proprietary interests of others.

Engineers shall, whenever possible, name the person or persons who may be individually responsible for designs, inventions, writings, or other accomplishments.

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.

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.

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.

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

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

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

Q101: 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.

Q104: 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.

Q201: 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.

Q301: 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.

Q302: 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.

Q401: 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.

Q402: 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.

Q403: 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.

Q103: 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.

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

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

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

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

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

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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.

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.

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.

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.

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.

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.

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.

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.

The question emerged because Engineer B's proposal technique sits at the intersection of two state rule regimes with different attribution requirements, making it unclear whether the omission constitutes ethical marketing or a misrepresentation of qualifications under the NSPE Code.

The question arose because Engineer A practices under two different regulatory regimes with State Rule Specificity Variation, creating doubt about whether a single act of nondisclosure obligates reporting in both, one, or neither jurisdiction.

The question arises because the format of disclosure (once per section) creates an ambiguity between formal compliance with attribution rules and the practical goal of preventing misleading impressions, and reasonable readers might behave in ways that undermine the latter.

The question arises because the entity capable of correcting or being held liable for the disclosure omission is ambiguous, XYZ Engineers benefits from and controls the proposal while Engineer B is the named credentialed individual, creating uncertainty over whether organizational or individual accountability warrants should govern compliance.

The question arises because Engineer A's professional affiliation with a market rival to Engineer B's firm introduces an appearance of self interest that sits uneasily alongside an otherwise clear, rule based duty to report observed misconduct in State Z.

The question arises because Engineer A discovers that identical conduct is judged permissible by one authoritative standard (NSPE Code) and impermissible by another (State Z Rules), forcing scrutiny of whether the Code's generality is a structural weakness in handling nuanced credit-attribution cases.

The question emerged because Engineer A discovered that Engineer B and XYZ Engineers' proposal practice, though defensible under the NSPE Code's broad honesty principle, violates State Z's narrower attribution rule, forcing a choice between deferring to the general professional code or the binding jurisdictional rule when deciding whether a reportable violation occurred.

The question arises because the same disclosure practice can be read as both compliant transparency and as an incomplete differentiation of firm responsibility, depending on how far a reader's memory of the initial notice is presumed to extend through a lengthy description.

The question emerged because a single act of qualifications presentation was evaluated as ethical under one authority (the Board applying the general Code) but as a reportable violation under another (State Z's specific rules), forcing Engineer A to choose between deferring to the Board's honesty finding or fulfilling a jurisdiction-specific reporting duty.

The question arose because XYZ Partial Attribution Disclosure created an ambiguous factual record where formal Code language demands explicit individual credit but the actual document only partially delivered it, leaving deontological compliance contestable.

This question arose because the qualification statement technically satisfied outcome-based sufficiency (clients could discern the truth) while falling short of a stricter transparency norm, creating a genuine tension between judging the act by its results versus by its adherence to disclosure rules.

The question arose because Engineer B disclosed prior-employer attribution for some projects but not others within the same qualification statement, prompting scrutiny of whether this selective transparency reflects a genuine virtue of honesty or a strategic, self-serving presentation.

The question arises because Engineer A applied a single duty, deference to licensure rules, to two states with differing rule specificity, producing inconsistent reporting conclusions from identical facts and raising doubt about whether the duty was genuinely fulfilled or merely used to justify selective non-reporting.

The question arises because the Board's ethical conclusion appears contingent on a specific factual absence (no proprietary design concepts), making it natural to ask whether reversing that fact would flip the warrant that governs whether crediting practices count as honest qualification marketing or as misrepresentation.

This question arose because the Board's finding of misconduct depended on an implicit judgment about how much repetition of attribution is enough, and altering the frequency of the notice tests whether the underlying warrant is about formal presence of disclosure or about actual reader comprehension.

The question arises because the Board's finding of a clear reporting obligation was grounded in State Z's specific attribution requirement, so removing that specificity exposes how much of the obligation's clarity depended on rule wording rather than on the underlying ethical principle of honesty in qualifications presentation.

Given that Engineer B disclosed prior-employer attribution at the outset of each project section and the described work fell within Engineer B's genuine expertise without proprietary complications, the Board concluded a reasonably attentive reader would not be deceived, satisfying the Code's general honesty and credit-giving standards.

Given that State Q's rules track the general NCEES misrepresentation standard and Engineer B's disclosure practice satisfied that broad threshold, the Board found no underlying violation and therefore no reporting obligation in State Q.

Given State Z's specific requirement that attribution appear beside each project listing and the fact that Engineer B's notice only appeared once per section, the Board concluded the practice violated State Z law and triggered Engineer A's clear, non-discretionary duty to report.

Because the Board reached divergent conclusions for State Q and State Z from the exact same facts, it inferred that satisfying the NSPE Code's general deceptive-acts standard is necessary but not sufficient wherever a state has enacted more precise attribution rules.

Given that Engineer B's notice appeared at least once per section rather than nowhere, the Board treated the incompleteness as a partial shortfall in transparency rather than a wholesale ethical failure, even though this framing leaves unaddressed the paragraph-level misreading risk that State Z's rule specifically targets.

Given that Engineer A's knowledge of the violation was factual rather than fabricated, the Board concluded the reporting duty to State Z remains intact despite Engineer A's competitor employment, though it did not resolve the practical concern that State Z's board might view the complaint as competitively motivated.

Because Engineer B's qualifications statement disclosed the prior employer and client at the outset of each project section, the Board treated the lack of repeated attribution in later paragraphs as a formatting weakness rather than a deceptive act rising to a Code violation.

Given that State Z's rule demands attribution next to each specific project listing while the Code only requires general credit language, the Board concluded that the case exposes a structural gap where the Code cannot substitute for jurisdiction-specific technical compliance.

Because the same proposal practice satisfied the Code's general honesty principle but failed State Z's stricter attribution rule, the Board concluded the two principles are complementary rather than conflicting, with jurisdictional deference supplementing the Code's baseline.

Given that Engineer B identified the prior employer and client only at the start of each project's description, the Board concluded this satisfies a minimal reading of the III.9.a. naming duty, even though the recurring omission in later paragraphs falls short of the provision's full intended spirit.

Given that the disclosure appeared at the outset of each project section and a diligent reader could still discern Engineer B's true role, the Board concluded that the outcome was acceptable under the NSPE Code's general standard, even though this same conduct fails State Z's stricter, comprehension-independent attribution rule.

Because the prior projects Engineer B described did not involve proprietary design concepts, the Board found no confidentiality or competitive injury to the previous employer, but it signaled that presence of such proprietary content would likely have produced a different, adverse conclusion under the Code.

Because the deficiency triggering misconduct was specifically the inconsistent, paragraph-by-paragraph placement of the attribution notice rather than the underlying practice of citing prior work, the Board reasoned that had the notice appeared in every paragraph, State Z's specific rule would have been satisfied and no reporting duty would have arisen.

Because the Board's finding of a clear State Z reporting duty rested specifically on that jurisdiction's granular attribution language, the Board reasoned that if State Z's rules had instead mirrored State Q's general NCEES-style standard, the same no-clear-duty outcome reached for State Q would likely have applied to State Z too.

Given that the State Z reporting duty derives from mandatory licensing board rules rather than personal motive, the Board concluded that Engineer A's employment by a competitor does not negate the duty, though it cautioned that the report must be based strictly on the documented violation to preserve its integrity.

Because State Z's licensing rules impose a specific technical attribution requirement beyond the Code's general non-deception language, the Board concluded Engineer B's identical conduct could pass the looser ethical bar while failing the stricter legal one, showing the two frameworks must be applied separately.

Given that Engineer B disclosed attribution only once per section in long project descriptions, the Board found this adequate under the Code's general transparency standard but insufficient under State Z's itemized clarity rule, showing that jurisdictional specificity, not the Code alone, decides the outcome.

Because State Z's rule independently defines Engineer B's conduct as misconduct even though the Board judged it ethically acceptable under the Code, the Board concluded Engineer A's reporting duty runs on a separate, rule-based track that does not depend on the underlying ethical verdict.

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?

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?

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?

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?

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?