Step 4: Full View

Entities, provisions, decisions, and narrative

Public Contracting Practices
Step 4 of 5

198

Entities

7

Provisions

7

Precedents

18

Questions

20

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
The obligation cascades along an escalation chain rather than looping (oscillation) or freezing (stalemate): Engineer B's reporting duty transfers responsibility to Engineer A (investigation), whose findings transfer accountability to City D's Engineer (internal correction), and upon refusal, transfer again to the State Licensure Board (external enforcement) as codified in C8. Each shift relieves the prior party of exclusive responsibility once the next actor assumes it, consistent with a one-directional 'clean handoff' rather than recurring back-and-forth movement.
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 (7)
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.

I.4 board + analysis Act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 15)
Obligation
Engineer A Faithful Agent Duty
This provision directly requires engineers to act as faithful agents or trustees for their clients
Action
Non-Compliant Contract Award
Awarding a contract improperly violates the duty to act as a faithful agent or trustee
State
City Engineer Acknowledged Noncompliance
The City Engineer failed to act as a faithful agent by allowing noncompliant contracts to proceed
Obligation (1)
  • Engineer A Faithful Agent Duty
    This provision directly requires engineers to act as faithful agents or trustees for their clients
Action (2)
  • Non-Compliant Contract Award
    Awarding a contract improperly violates the duty to act as a faithful agent or trustee
  • Corrective Action Refusal
    Refusing to correct improper actions breaches the duty of faithful agency to the public client
State (2)
  • City Engineer Acknowledged Noncompliance
    The City Engineer failed to act as a faithful agent by allowing noncompliant contracts to proceed
  • Firm Z Relationship Favoritism
    Favoritism toward Firm Z breaches the duty of faithful agency owed to City D
Constraint (1)
  • City Engineer Contract Award Boundary
    City Engineer must act as faithful trustee by not exceeding contract award authority
Principle (1)
  • Loyalty as Faithful Agent to City D
    This provision directly requires Engineer A to act as a faithful agent or trustee to City D
Role (4)
  • Engineer A Assistant City Engineer
    As a City employee engineer he must act as a faithful agent to City D
  • Engineer A Faithful Agent
    This role explicitly embodies the faithful agent obligation under the Code
  • City D Engineer City Engineer
    As City D's engineer he must act as a faithful agent or trustee for the City
  • Firm Z Employed Engineers
    As engineers serving a client they owe faithful agency duties to City D
Event (2)
  • Procurement Law Violation
    Faithful agency duty is breached when procurement laws are violated on behalf of a client
  • Competitive Exclusion
    Excluding competitors improperly conflicts with faithful agent obligations to the public and process
Capability (2)
  • Engineer A Fact Gathering Diligence
    Faithful agency requires thorough fact gathering before advising a client or public body
  • Engineer A Stakeholder Consultation
    Acting as a faithful agent requires consulting relevant stakeholders to serve the client properly
I.6 board + analysis Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.
How this applies in the case (showing 3 of 16)
Obligation
Engineer A Appropriate Action Duty
Acting honorably and responsibly requires taking appropriate action when violations are known
Action
Non-Compliant Contract Award
An unlawful contract award damages the honor and reputation of the profession
State
Firm Z Contracts RFQ Noncompliance
Noncompliant contracting practices fail to enhance the honor and reputation of the profession
Obligation (2)
  • Engineer A Appropriate Action Duty
    Acting honorably and responsibly requires taking appropriate action when violations are known
  • City D Engineer Registration Law Duty
    Failing to conduct oneself lawfully undermines the honor and reputation of the profession
Action (2)
  • Non-Compliant Contract Award
    An unlawful contract award damages the honor and reputation of the profession
  • Corrective Action Refusal
    Refusing to correct known violations fails to uphold professional honor and reputation
State (3)
  • Firm Z Contracts RFQ Noncompliance
    Noncompliant contracting practices fail to enhance the honor and reputation of the profession
  • City Engineer Refusal Firm Z Contracts
    Refusal to follow lawful procurement standards is dishonorable conduct
  • Firm Z Relationship Favoritism
    Favoritism undermines the ethical standing of the profession
Principle (1)
  • Integrity in Procurement Conduct
    This provision mandates honorable and responsible conduct to enhance the profession's reputation in procurement matters
Role (4)
  • Engineer A Assistant City Engineer
    Must act honorably and lawfully to uphold the profession's reputation
  • Engineer B Civil Engineering Firm Owner
    As a licensed engineer he must conduct himself honorably in raising concerns
  • City D Engineer City Engineer
    Must act honorably and lawfully in approving contracts
  • Firm Z Employed Engineers
    Must conduct themselves honorably and lawfully as professional engineers
Event (2)
  • Procurement Law Violation
    Violating procurement laws harms the honor and reputation of the profession
  • Noncompliance Persistence
    Continued noncompliance further damages the profession's reputation and lawful conduct standard
Capability (2)
  • Engineer A Compliance Findings Disclosure
    Honorable and responsible conduct requires disclosing compliance findings to enhance the profession's reputation
  • City D Engineer Noncompliance Recognition
    Recognizing noncompliance relates to conducting oneself lawfully and enhancing the profession's reputation
II.1.e board + analysis Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
How this applies in the case (showing 3 of 9)
Obligation
Engineer A Appropriate Action Duty
Engineer A must avoid aiding unlawful practice by taking action against the improper arrangement
Action
Non-Compliant Contract Award
Awarding a contract that bypasses qualification rules may aid unlawful engineering practice
Constraint
Engineer A Aid Abet Prohibition
This provision directly creates the prohibition against aiding or abetting unlawful practice
Obligation (2)
  • Engineer A Appropriate Action Duty
    Engineer A must avoid aiding unlawful practice by taking action against the improper arrangement
  • Firm Z Engineers Registration Law Duty
    This provision prohibits aiding unlawful engineering practice which relates to Firm Z's registration compliance
Action (1)
  • Non-Compliant Contract Award
    Awarding a contract that bypasses qualification rules may aid unlawful engineering practice
Constraint (1)
  • Engineer A Aid Abet Prohibition
    This provision directly creates the prohibition against aiding or abetting unlawful practice
Role (3)
  • Engineer A Faithful Agent
    Once aware of unlawful practices Engineer A must not aid or abet them
  • City D Engineer City Engineer
    By approving contracts outside procurement law he may be aiding unlawful practice
  • Firm Z Employed Engineers
    Continuing to accept contracts obtained unlawfully implicates aiding unlawful practice
Event (1)
  • Procurement Law Violation
    Aiding unlawful practices through procurement violations conflicts with this provision
Capability (1)
  • City D Engineer Noncompliance Recognition
    Recognizing unlawful practice by City D's engineer relates to not aiding unlawful engineering practice
II.1.f board + analysis Engineers having knowledge of any alleged violation of this Code shall report thereon to appropriate professional bodies and, when relevant, also to public authorities, and cooperate with the proper authorities in furnishing such information or assistance as may be required.
How this applies in the case (showing 3 of 19)
Obligation
Engineer B Code Violation Reporting Duty
This provision directly establishes the duty to report known Code violations
Action
Violation Reporting
This action directly implements the duty to report known code violations to authorities
State
Engineer A Noncompliance Knowledge
Engineer A had knowledge of the violation and had a duty to report it
Obligation (3)
  • Engineer B Code Violation Reporting Duty
    This provision directly establishes the duty to report known Code violations
  • Engineer A Appropriate Action Duty
    This provision requires reporting alleged violations to appropriate authorities
  • Engineer A Licensure Board Reporting Consideration
    This provision requires reporting violations to appropriate professional bodies like licensure boards
Action (4)
  • Violation Reporting
    This action directly implements the duty to report known code violations to authorities
  • Compliance Investigation
    Investigating compliance is part of cooperating with authorities on alleged violations
  • Findings Reporting
    Reporting findings fulfills the obligation to inform proper bodies of violations
  • Corrective Action Refusal
    Refusing corrective action after a violation is found contradicts the duty to report and cooperate
State (2)
  • Engineer A Noncompliance Knowledge
    Engineer A had knowledge of the violation and had a duty to report it
  • Engineer B Report Made
    Engineer B's report reflects the obligation to report known Code violations
Principle (2)
  • QBS Compliance in City D Contracting
    This provision requires reporting known violations of procurement law to appropriate authorities
  • Registration Law Compliance in City D Procurement
    This provision obligates engineers to report known violations of registration or procurement law to proper bodies
Role (3)
  • Engineer A Assistant City Engineer
    Having knowledge of alleged violations he must report to proper authorities
  • Engineer B Civil Engineering Firm Owner
    Having alleged violations he must report them to appropriate professional bodies or authorities
  • City D Engineer City Engineer
    Aware of procurement violations he must report and cooperate with authorities
Event (2)
  • Violation Discovery
    Discovering a violation triggers the duty to report it to proper authorities
  • Noncompliance Persistence
    Continued noncompliance after discovery obligates further reporting and cooperation
Resource (1)
  • NSPE Code of Ethics
    This provision requires reporting violations to appropriate professional bodies that reference the NSPE Code
Capability (2)
  • Engineer A Compliance Findings Disclosure
    Knowledge of code violations requires reporting findings to appropriate authorities
  • City D Engineer Noncompliance Recognition
    Recognized noncompliance must be reported to appropriate professional bodies or authorities
III.6 board + analysis Engineers shall not attempt to obtain employment or advancement or professional engagements by untruthfully criticizing other engineers, or by other improper or questionable methods.
How this applies in the case (showing 3 of 4)
Action
Non-Compliant Contract Award
Improperly awarding a contract may involve obtaining engagement through questionable methods
Role
Engineer B Civil Engineering Firm Owner
His allegations against Firm X and Firm Z could implicate improper methods of seeking work
Event
Competitive Exclusion
Improper exclusion of competitors to gain advantage violates fair competition standards
Action (1)
  • Non-Compliant Contract Award
    Improperly awarding a contract may involve obtaining engagement through questionable methods
Role (1)
  • Engineer B Civil Engineering Firm Owner
    His allegations against Firm X and Firm Z could implicate improper methods of seeking work
Event (1)
  • Competitive Exclusion
    Improper exclusion of competitors to gain advantage violates fair competition standards
Capability (1)
  • Engineer B Exclusionary Practice Recognition
    Exclusionary practices to gain advancement relate to improper methods of obtaining professional engagements
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 13)
Obligation
Engineer A Appropriate Action Duty
This provision requires presenting information about believed unethical or illegal practice to proper authorities
Action
Violation Reporting
This provision requires presenting evidence of unethical practice to proper authorities
State
Engineer B Report Made
Reporting to the proper authority aligns with the duty to present evidence of unethical practice rather than harm reputations improperly
Obligation (1)
  • Engineer A Appropriate Action Duty
    This provision requires presenting information about believed unethical or illegal practice to proper authorities
Action (2)
  • Violation Reporting
    This provision requires presenting evidence of unethical practice to proper authorities
  • Findings Reporting
    Reporting findings of violations aligns with presenting information to proper authority
State (1)
  • Engineer B Report Made
    Reporting to the proper authority aligns with the duty to present evidence of unethical practice rather than harm reputations improperly
Principle (2)
  • QBS Compliance in City D Contracting
    This provision requires presenting evidence of illegal practice to proper authorities rather than acting improperly
  • Registration Law Compliance in City D Procurement
    This provision requires reporting suspected illegal procurement practices to the proper authority for action
Role (2)
  • Engineer B Civil Engineering Firm Owner
    Must present his belief of unethical or illegal practice to the proper authority rather than injure reputations improperly
  • Engineer A Assistant City Engineer
    Must present findings of possible violations to proper authority rather than act unilaterally
Event (2)
  • Competitive Exclusion
    Excluding competitors unfairly can injure their professional reputation or practice
  • Violation Discovery
    Knowledge of unethical conduct must be reported to proper authorities rather than acted on unilaterally
Resource (1)
  • NSPE Code of Ethics
    This provision requires presenting evidence of unethical practice to proper authorities as defined under the NSPE Code
Capability (2)
  • Engineer B Exclusionary Practice Recognition
    Recognizing exclusionary practice relates to not injuring other engineers professional prospects improperly
  • City D Engineer Noncompliance Recognition
    Belief of illegal practice must be presented to proper authority rather than acted upon informally
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 17)
Obligation
City D Engineer Registration Law Duty
This provision directly requires conformance with state registration laws including procurement requirements
Action
Non-Compliant Contract Award
A non-compliant award likely violates state registration and licensing requirements
State
QBS Procurement Laws In Force
Engineers must conform to state procurement and registration laws such as QBS requirements
Obligation (3)
  • City D Engineer Registration Law Duty
    This provision directly requires conformance with state registration laws including procurement requirements
  • Firm Z Engineers Registration Law Duty
    This provision directly requires conformance with state registration laws including procurement requirements
  • City Engineer QBS Compliance Duty
    QBS procurement compliance is part of conforming with state registration laws
Action (3)
  • Non-Compliant Contract Award
    A non-compliant award likely violates state registration and licensing requirements
  • Compliant RFQ Contract Award
    This action demonstrates conformance with state registration laws in contracting
  • Compliant Contract Awards
    These awards reflect adherence to state registration laws governing engineering practice
State (3)
  • QBS Procurement Laws In Force
    Engineers must conform to state procurement and registration laws such as QBS requirements
  • Firm Z Contracts RFQ Noncompliance
    Noncompliance with RFQ and QBS laws directly violates state registration and procurement law conformity
  • Firm X Contract Compliance
    Compliance with state contracting laws demonstrates adherence to this provision
Constraint (1)
  • City Engineer Contract Award Boundary
    City Engineer must conform to registration and procurement laws limiting contract award authority
Principle (1)
  • Registration Law Compliance in City D Procurement
    This provision requires engineers to conform with state registration laws, which were violated in the Firm Z contract awards
Role (2)
  • Firm Z Employed Engineers
    The Board finds these engineers violated procurement law and this registration conformity provision
  • City D Engineer City Engineer
    The Board holds the City D Engineer violated procurement law and this provision by bypassing RFQ requirements
Event (3)
  • Procurement Law Violation
    Failure to conform to state registration and procurement laws directly violates this provision
  • Threshold Exceedance
    Exceeding legal thresholds without proper registration or compliance violates state law conformance
  • Compliance Verification
    Verifying compliance relates directly to conforming with state registration laws
Capability (1)
  • City D Engineer Noncompliance Recognition
    Noncompliance recognition directly concerns conformity with state registration laws
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 6 Lineage Graph

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

Principle Established:

An engineer may ethically present as a non-engineer consultant-expert without disclosing licensure status, but claiming professional engineering-related credentials (e.g., Board Certified Diplomate) without disclosing licensure status becomes unethical.

Citation Context:

Cited as a third example regarding compliance with licensure law, addressing when self-presentation as a non-engineer expert becomes unethical if licensure-related credentials are invoked.

Relevant Excerpts
discussion: "A third example is BER Case 21-9, where Engineer A was a licensed professional engineer in three states... There the BER concluded that if Engineer A qualified as an expert without relying on engineering qualifications... Engineer A's self-presentation became unethical."

Principle Established:

Lodging a public protest against a questionable contract award based on public safety/interest concerns is not an unfair competitive act under the Code, though such protests must be made carefully to avoid crossing ethical lines.

Citation Context:

Cited to show that engineers may ethically challenge or protest procurement/selection practices that could compromise public interest, such as an unsafe low-cost bid.

Relevant Excerpts
discussion: "For example, BER Case 80-1 examined a state agency's selection method that mixed qualifications screening with a post-scoping meeting price proposal... The BER held that lodging such a protest was not an unfair competitive act under the Code."

Principle Established:

Federal, state, and local laws governing procurement of engineering services remain in full force and effect notwithstanding antitrust-related changes to the NSPE Code of Ethics.

Citation Context:

Cited to establish that despite antitrust-driven removal of Code provisions on competitive bidding and related practices, procurement laws requiring QBS processes remain fully enforceable and engineers must comply with them.

Relevant Excerpts
discussion: "The Board of Ethical Review (BER) Case 08-8 provides helpful precedent... BER Case 08-8 concluded that one of the most fundamental outcomes of these antitrust actions and rules was the basic principle that federal, state, and local laws governing procedures to procure engineering services are not affected and remain in full force and effect."

Principle Established:

Absence of an explicit contractual prohibition does not excuse an engineer from ethical obligations grounded in the spirit of the Code and Fundamental Canon 1.6.

Citation Context:

Cited to illustrate that engineers must consider the spirit, not just the letter, of the ethics code even absent explicit contractual prohibitions (e.g., revolving door provisions).

Relevant Excerpts
discussion: "BER Case 23-3 discussed Engineer D, a licensed professional engineer, who worked as the City Engineer in a mid-sized municipality... In their analysis of BER Case 23-3, the BER acknowledged..."

Principle Established:

Engineers must avoid conduct that brings dishonor to the profession and must uphold the purity of the enterprise, considering both the letter and spirit of the ethics code.

Citation Context:

Quoted within the discussion of BER Case 23-3 to emphasize that engineers must uphold the 'purity of the enterprise' and avoid 'dishonor to the profession,' considering both letter and spirit of the ethics code.

Relevant Excerpts
discussion: "BER Case 58-1 speaks of the 'purity of the enterprise, of avoiding 'dishonor to the profession, and how engineers must consider not only the letter but the spirit of the ethics code."

Principle Established:

It is unlawful and unethical for an unlicensed individual to engage in activities constituting the practice of engineering, and an engineer who discovers this has an obligation to report the unlicensed practice.

Citation Context:

Cited as a recent example demonstrating that careful compliance with licensure law is expected, and that engineers must report unlicensed practice of engineering when discovered.

Relevant Excerpts
discussion: "For example, BER Case 22-1 introduced Engineer A, a consulting engineer, who presented signed and sealed design contract documents to the State Agency manager... the BER found it was unlawful and therefore not ethical for 'Transportation Engineer' B to engage in the practice of engineering without having fulfilled the requirements for licensure."

Principle Established:

The Supreme Court's antitrust ruling required removal of Code provisions restricting competitive bidding, but did not affect the enforceability of procurement laws.

Citation Context:

Cited as background to BER Case 08-8, referencing the Supreme Court ruling that led to removal of anti-competitive Code provisions while preserving procurement laws.

Relevant Excerpts
discussion: "This case discussed actions by the US Justice Department, in 1977... and the U.S. Supreme Court's ruling in National Soc'y of Prof. Engineers v. United States, 435 U.S. 679 (1978)."
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 60% Facts Similarity 72% Discussion Similarity 61% Provision Overlap 23% Outcome Alignment 100% Principle Overlap 76%
Shared provisions: I.4, I.6, III.6 Same outcome ethical View Synthesis
Component Similarity 56% Facts Similarity 53% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 70%
Same outcome ethical View Synthesis
Component Similarity 45% Facts Similarity 46% Discussion Similarity 59% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 43% Principle Overlap 49%
Shared provisions: I.4, II.1.F Same outcome ethical View Synthesis
Component Similarity 47% Facts Similarity 45% Discussion Similarity 55% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 67%
Shared provisions: I.4 Same outcome ethical View Synthesis
Component Similarity 51% Facts Similarity 35% Discussion Similarity 56% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 60%
Shared provisions: I.4 Same outcome ethical View Synthesis
Component Similarity 50% Facts Similarity 23% Discussion Similarity 59% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 69%
Shared provisions: I.4 Same outcome ethical View Synthesis
Component Similarity 52% Facts Similarity 59% Discussion Similarity 50% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 71%
Same outcome ethical View Synthesis
Component Similarity 60% Facts Similarity 55% Discussion Similarity 80% Outcome Alignment 100% Principle Overlap 59%
Same outcome ethical View Synthesis
Component Similarity 54% Facts Similarity 53% Discussion Similarity 57% Outcome Alignment 100% Principle Overlap 70%
Same outcome ethical View Synthesis
Component Similarity 52% Facts Similarity 64% Discussion Similarity 62% Outcome Alignment 100% Principle Overlap 74%
Same outcome ethical View Synthesis
Questions & Conclusions (3 board)
View Extraction
Board Board question 1

Was it ethical for Engineer B to complain to Engineer A?

Board conclusion It was not only ethical for Engineer B to complain to Engineer A, it was ethically required that Engineer B report his belief that statutory obligations were not being followed.
Resolved by: The Board treated the Code's mandatory reporting duty as outweighing any concern that Engineer B's complaint might be self-serving or disruptive to City D's practices. (confidence 0.85)
II.1.f. III.8.a. 3 principles 3 facts Conditions Narrative
Theoretical (1)

From a deontological perspective, was Engineer B obligated under the Code to report suspected procurement violations to Engineer A even though Engineer B, as a competing firm owner, stood to gain professionally from increased competitive bidding opportunities?

AnalyticalThe Board's finding that Engineer B was ethically required to report under Code II.1.f is not undermined by the fact that Engineer B, as a competing firm owner, stood to benefit professionally from increased competitive bidding. The Code's reporting duty is triggered by knowledge of an alleged violation, not by the reporter's motive; a self-interested reporter can still fulfill a genuine ethical obligation, provided the underlying allegation is factually grounded, which Engineer A's subsequent investigation confirmed it was.
Resolved by: The Board weighed the objective factual basis of the allegation as controlling, treating the reporter's competitive self-interest as immaterial so long as it did not corrupt or fabricate the underlying claim. (confidence 0.80)
II.1.f. III.7. 3 principles 3 facts Conditions Narrative
AnalyticalEngineer B's status as a competing firm owner does not undermine the ethicality of the report. The Code's reporting obligation under II.1.f is duty-based rather than motive-based; even if Engineer B stood to gain from increased competitive bidding, this self-interest does not disqualify the legitimacy or necessity of reporting suspected procurement violations.
Resolved by: The Board weighed Engineer B's potential self-interest against the duty-based nature of the reporting obligation and concluded that motive does not negate a legitimate duty to report suspected violations. (confidence 0.50)
II.1.f. 2 principles 3 facts Conditions Narrative
AnalyticalEngineer B's duty to report suspected violations (II.1.f) was treated by the Board as independent of Engineer B's competitive self-interest as a rival firm owner, showing that the Code's reporting obligation operates on a deontological basis rather than being contingent on the reporter's motives or potential to benefit. This resolves a potential tension between self-interested motive and duty-based reporting obligation in favor of the latter: the validity of a Code-based duty to report is not diminished by the reporter's simultaneous financial interest in the outcome.
Resolved by: The board weighed the deontological reporting duty against the potential taint of self-interested motive and found the duty binding regardless of any competitive benefit to the reporter. (confidence 0.80)
II.1.f. 1 principle 3 facts Conditions Narrative
Board Board question 2

Were Engineer A’s actions in investigating City D’s contracting practices ethical?

Board conclusion It was ethical for Engineer A to investigate City D’s contracting practices, both as a part of A’s own familiarization process and to follow up on Engineer B’s complaints.
Resolved by: The Board found no real conflict between loyalty to City D and investigating its practices, since faithful agency to an employer is best served by ensuring lawful, compliant operations rather than ignoring credible complaints. (confidence 0.85)
I.4. II.1.e. II.1.f. 3 principles 3 facts Conditions Narrative
Principle tension (1)

Does the City Engineer's justification of 'convenience and longstanding relationship' with Firm Z represent a conflict between Integrity in Procurement Conduct and an informal loyalty to a favored contractor that undermines QBS Compliance?

AnalyticalCity D Engineer's justification of 'convenience and longstanding relationship' represents an informal loyalty to a favored contractor that directly conflicts with Integrity in Procurement Conduct and QBS Compliance. The Board's implicit rejection of this justification establishes that administrative convenience is never a valid substitute for compliance with codified procurement law.
Resolved by: The Board weighed informal loyalty to a favored contractor against codified procurement integrity and found the former categorically insufficient to override the latter. (confidence 0.50)
III.8.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe City Engineer's invocation of 'convenience and longstanding relationship' as justification for bypassing RFQ requirements reveals a direct clash between Integrity in Procurement Conduct and an informal, relationship-based loyalty to a favored contractor. The Board's implicit rejection of this justification -- by finding Engineer A obligated to take further action -- establishes that administrative convenience and vendor familiarity cannot override codified procurement law, even when the noncompliance is acknowledged rather than concealed. This indicates that Integrity in Procurement Conduct is treated as a near-absolute constraint rather than one to be balanced against organizational efficiency.
Resolved by: The board weighed administrative convenience and vendor familiarity against codified procurement law and found the former cannot override the latter, even when offered as an open rather than concealed justification. (confidence 0.75)
III.8.a. II.1.f. 2 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill the duty of a faithful agent to City D by investigating and reporting the Firm Z contracting noncompliance rather than remaining silent to preserve workplace harmony?

AnalyticalFrom a deontological standpoint, Engineer A fulfilled rather than violated the duty of faithful agency by investigating and reporting the noncompliance. Faithful agency under I.4 is conditioned on lawful conduct; an agent who conceals known illegality to preserve workplace harmony fails the duty rather than fulfilling it. Engineer A's actions therefore represent the correct discharge of a faithful agent's obligations.
Resolved by: The Board treated the duty to investigate and report as constitutive of, not in tension with, faithful agency, so no genuine competition existed once illegality was confirmed. (confidence 0.50)
I.4. II.1.f. II.1.e. 3 principles 3 facts Conditions Narrative

Did the outcome of Engineer A's investigation -- exposing seven years of exclusive, partly noncompliant contracting with Firm X and Firm Z -- justify the disruption to City D's longstanding vendor relationships and administrative convenience?

AnalyticalThe disruption to City D's longstanding vendor relationships is ethically justified by the outcome of Engineer A's investigation. Seven years of exclusive contracting, part of which was unlawful, represents a sustained deprivation of competitive opportunity to qualified firms and a violation of codified QBS law; exposing this outweighs the administrative convenience the City Engineer sought to preserve.
Resolved by: The Board weighed the disruption to longstanding vendor relationships and administrative convenience against the harm of sustained unlawful exclusion of qualified firms, finding the latter outweighed the former. (confidence 0.50)
III.8.a. 3 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity by pursuing a thorough compliance investigation shortly after joining City D, despite having no prior history with Engineer B and facing potential friction with a superior, City D's Engineer, over the findings?

Also discussed in: C102
Counterfactual (2)

If Firm X's ongoing work for City D had exceeded the original scope of its RFQ-awarded contract (rather than remaining aligned with it), would the Board still have treated the Firm X arrangement as compliant and outside the scope of Engineer A's corrective obligations?

AnalyticalBecause the noncompliance in this case is limited to two contracts with Firm Z that exceeded the Council-authorization threshold, and does not extend to Firm X's compliant arrangement, Engineer A's corrective obligations are properly scoped to the Firm Z contracts alone. This distinction matters for determining the proportional severity of any escalation or reporting action Engineer A ultimately takes.
Resolved by: The board weighs proportionality against overreach, limiting Engineer A's corrective obligation to the specific noncompliant contracts rather than extending it to all City D vendor arrangements. (confidence 0.70)
III.8.a. 2 principles 3 facts Conditions Narrative

If City D's jurisdiction lacked strong QBS procurement laws codified in state licensure statutes, would the Board still characterize City D Engineer's exclusive reliance on Firm Z as an ethical violation rather than a permissible administrative choice?

AnalyticalAbsent strong QBS procurement laws codified in state licensure statutes, City D Engineer's exclusive reliance on Firm Z might be characterized merely as questionable administrative judgment rather than an ethical or legal violation, since the Board's characterization of noncompliance hinges specifically on the breach of codified registration and procurement law rather than on favoritism alone.
Resolved by: The board distinguishes a codified legal violation from a merely questionable administrative judgment, weighting the presence of statutory QBS requirements as the deciding factor over the underlying favoritism itself. (confidence 0.80)
III.8.a. II.1.f. 3 principles 3 facts Conditions Narrative
Board Board question 3

Because City D’s Engineer refuses to change the contract arrangement with Firm Z, what steps must Engineer A take?

Board conclusion Since the City D Engineer indicated they have no plans to change the contract arrangement with Firm Z, Engineer A is obligated to take appropriate action.
Resolved by: The Board weighed Engineer A's obligation to uphold registration and procurement law more heavily than continued deference to a supervisor who had acknowledged noncompliance yet refused to correct it. (confidence 0.80)
I.4. II.1.f. III.8.a. 3 principles 3 facts Conditions Narrative
Also discussed in: C104
Implicit (3)

Does Engineer A have an independent duty to report the procurement law violations to the State Licensure Board, separate from raising the issue internally with City D's Engineer?

AnalyticalEngineer A's duty to report is not exhausted by raising the matter internally with City D's Engineer. Under II.1.f, Engineer A has an independent obligation to report the alleged Code and registration law violation to the appropriate authority, which here includes the State Licensure Board, once internal correction was refused. This obligation exists separately from, and continues beyond, the internal escalation to City D's Engineer.
Resolved by: The board subordinates the completeness of internal escalation to the independent, code-based reporting obligation, treating II.1.f as a distinct duty not discharged by internal raising alone. (confidence 0.75)
II.1.f. III.8.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C103

Because City D's Engineer is Engineer A's direct supervisor, does this reporting relationship create a power imbalance that could deter Engineer A from pursuing further corrective action or escalation?

AnalyticalEngineer A's willingness to investigate and disclose findings that implicated a direct supervisor, City D's Engineer, demonstrates that faithful agency under I.4 is bounded by lawful and ethical conduct; faithful agency cannot be invoked to justify concealing or excusing a supervisor's noncompliance with registration and procurement law. The Board's endorsement of Engineer A's investigation implicitly resolves the tension between hierarchical deference and compliance duties in favor of compliance.
Resolved by: The Board resolved the tension between hierarchical deference and compliance duties by subordinating faithful agency to lawful conduct, finding that deference cannot excuse concealment of a supervisor's registration law violations. (confidence 0.75)
I.4. II.1.f. III.8.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe supervisory relationship between Engineer A and City D's Engineer does create a structural power imbalance, but the Code does not permit this imbalance to excuse inaction. Because faithful agency (I.4) is bounded by lawful conduct requirements (I.6, III.8.a), Engineer A's ethical obligation to pursue further corrective action or escalate the matter persists despite the risk of friction with a superior.
Resolved by: The board weighs the risk of supervisory friction against the non-negotiable requirement of lawful conduct, concluding that faithful agency cannot excuse continued inaction on a known violation. (confidence 0.70)
I.4. I.6. III.8.a. 3 principles 3 facts Conditions Narrative

Should City D's City Attorney or City Manager have been engaged earlier as stakeholders once Engineer A confirmed noncompliance, rather than relying solely on the City Engineer's discretion?

AnalyticalThe Board's conclusion that Engineer A must take further appropriate action once City D's Engineer refused corrective measures implies a graduated escalation duty: Engineer A should first exhaust internal remedies (e.g., engaging the City Attorney or City Manager as stakeholders) before considering external reporting to the State Licensure Board. The Board's language of 'appropriate action' suggests proportionality rather than an automatic mandate to report externally.
Resolved by: The board balances the duty to correct a known violation against the faithful-agent obligation to work within the organization first, favoring graduated internal escalation over immediate external reporting. (confidence 0.65)
I.4. II.1.f. III.8.a. 3 principles 3 facts Conditions Narrative
Principle tension (2)

How should Engineer A balance loyalty as a faithful agent to City D (and by extension to City D's Engineer as supervisor) against the duty to ensure QBS and registration law compliance when the City Engineer refuses corrective action?

AnalyticalThe principle of Loyalty as Faithful Agent to City D cannot be read to require concealment of unlawful procurement practices. Where City D's Engineer refuses corrective action, faithful agency must be understood as loyalty to the lawful mission and public interest of the employer, not personal deference to a supervisor's preferences, meaning Registration Law Compliance and QBS Compliance take precedence over supervisory comfort.
Resolved by: The Board subordinated personal deference to the supervisor's comfort to the statutory duties of registration and QBS compliance, redefining faithful agency as loyalty to lawful mission rather than to the individual supervisor. (confidence 0.50)
I.4. III.8.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe case demonstrates that 'faithful agency' is not owed unconditionally to an immediate supervisor or employer's convenience, but ultimately to lawful, publicly-accountable processes. Engineer A's loyalty to City D's Engineer as a direct supervisor was subordinated to the higher-order obligations of Registration Law Compliance and QBS Compliance once the City Engineer acknowledged noncompliance but refused correction. This suggests a layered model of faithful agency: engineers owe their most fundamental loyalty to lawful process and the public interest embedded in procurement statutes, with organizational deference operating only within the bounds of legal compliance.
Resolved by: The board subordinated loyalty to the immediate supervisor to the higher-order obligations of lawful process once acknowledgment without correction occurred, establishing a layered rather than absolute conception of faithful agency. (confidence 0.80)
I.4. III.8.a. II.1.f. 3 principles 3 facts Conditions Narrative

When Engineer A's duty of Registration Law Compliance in City D Procurement conflicts with the City Engineer's authority and expectation of deference, which principle should take precedence, and what does this imply about the limits of faithful agency?

Also discussed in: C102 C204 C301
Counterfactual (2)

If the two most recent Firm Z contracts had fallen below the dollar threshold requiring Council authorization and an RFQ process (rather than exceeding it), would the Board still have concluded that Engineer A is obligated to take further appropriate action against City D Engineer's noncompliance?

AnalyticalIf the two most recent Firm Z contracts had fallen below the dollar threshold requiring Council authorization and an RFQ process, no procurement law violation would have occurred, and the Board's conclusion that Engineer A is obligated to take further action would likely not apply, since the ethical breach in this case is specifically tied to threshold-triggered legal requirements being bypassed.
Resolved by: The board treated legal threshold breach, not favoritism alone, as the trigger for Engineer A's duty, so the obligation to act further is conditioned entirely on that legal fact rather than on a general anti-favoritism principle. (confidence 0.85)
III.8.a. II.1.e. 3 principles 3 facts Conditions Narrative

If City D's Engineer had agreed to correct the Firm Z contracting arrangement instead of refusing corrective action, would Engineer A still be obligated to consider reporting the matter to the state licensure board?

Analytical questions (1)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (1)

Did Firm Z's engineers have their own ethical obligation under registration and Code provisions to question or decline contracts awarded to them outside the required RFQ process, even though City D initiated the noncompliance?

AnalyticalFirm Z's engineers bear their own registration law compliance duty under III.8.a and cannot be entirely absolved simply because City D initiated the noncompliant awards. If Firm Z's engineers knew or should have known the two most recent contracts bypassed the required RFQ process, their acceptance of that work without objection raises a secondary, though less culpable, ethical question distinct from City D Engineer's primary responsibility.
Resolved by: The board weighs City D Engineer's primary culpability for initiating noncompliant awards against Firm Z engineers' own registration law duty, assigning the latter a secondary but non-trivial responsibility contingent on their knowledge. (confidence 0.65)
II.1.e. III.8.a. 2 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer B report the suspected Firm Z/Firm X procurement violations to Engineer A, or refrain from reporting given his competing commercial interest?

Options considered:
O1 Engineer B raises his good faith concern about City D's exclusive noncompliant contracting practice directly with Engineer A. Board's choice
O2 Engineer B declines to raise the issue because, as a competing firm owner, doing so could appear self-serving.
O3 Engineer B bypasses Engineer A and reports the suspected violation straight to the state licensure board instead of raising it internally with City D first.
Argument structure (Toulmin):
Claim Provided the belief is genuinely held and factually grounded rather than fabricated to harass a competitor.

Engineer B should report his good faith belief that City D's exclusive Firm Z/Firm X contracting violated the procurement law and Code to Engineer A.

Grounds

City D exclusively awarded contracts to Firm X and Firm Z without an RFQ process, excluding other qualified firms including Engineer B's, over a period of years.

Warrant

Code II.1.f requires engineers to report any alleged violation of the Code to appropriate authorities once they have knowledge or reasonable belief of it, regardless of the reporter's personal interest in the outcome.

Backing

NSPE Code II.1.f

Rebuttal

Would not apply if Engineer B's allegation were groundless or asserted in bad faith solely to gain competitive advantage rather than reflecting an actual suspected violation.

Engineer B Code Violation Reporting Duty

Should Engineer A conduct a thorough compliance investigation into City D's contracting practices, or defer to the City Engineer's existing arrangements without inquiry?

Options considered:
O1 Engineer A reviews contracting records and RFQ/QBS procedures for both Firm X and Firm Z to verify or refute Engineer B's allegations. Board's choice
O2 Engineer A declines to investigate, trusting that the City Engineer's longstanding contracting arrangements are proper and within his supervisor's authority.
O3 Engineer A raises the topic casually with the City Engineer without conducting a documented compliance review of contract files.
Argument structure (Toulmin):
Claim As a proper exercise of diligence appropriate to a newly hired engineer reviewing existing procedures.

Engineer A should conduct a compliance investigation into City D's contracting procedures, both as part of his onboarding and to follow up on Engineer B's complaint.

Grounds

Engineer A was newly employed by City D and received a specific complaint from Engineer B alleging City D exclusively awarded contracts to Firm X and Firm Z without the RFQ process.

Warrant

A faithful agent to the City must review contracting procedures and verify compliance with registration and procurement law rather than assume compliance; Code II.1.f obligates follow-up on reported concerns.

Backing

NSPE Code I.4, II.1.f

Rebuttal

Would not apply if Engineer A lacked authority or mandate within his position to review contracting practices outside his assigned duties, or if the investigation were pursued outside proper channels.

Engineer A Faithful Agent Duty

Should Engineer A escalate internally to the City Attorney and City Manager and consider reporting to the State Licensure Board, or accept the City Engineer's refusal and take no further action?

Options considered:
O1 Engineer A raises the confirmed noncompliance with the City Attorney and City Manager, and if correction is still refused, reports the violation to the State Licensure Board. Board's choice
O2 Engineer A defers to the City Engineer's decision not to change the Firm Z arrangement and does not pursue the matter further to preserve workplace harmony.
O3 Engineer A bypasses further internal stakeholders and reports the confirmed violation directly to the State Licensure Board immediately after the City Engineer's refusal.
Argument structure (Toulmin):
Claim Proceeding carefully and sensitively, with facts verified, ideally exhausting internal channels including the City Attorney and City Manager before external reporting to the licensure board.

Engineer A must take further appropriate action, proceeding advisedly and through approved channels, escalating to stakeholders such as the City Attorney or City Manager and considering a report to the State Licensure Board if internal correction is not achieved.

Grounds

City D's Engineer acknowledged the two most recent Firm Z contracts were awarded without an RFQ despite exceeding the Council authorization threshold, and stated no plans to change the arrangement.

Warrant

Faithful agency (I.4) is bounded by lawful conduct and cannot excuse concealment of a supervisor's known registration law violation; II.1.f and III.8.a require reporting of alleged Code and registration law violations to appropriate authorities when internal correction fails; engineers must not aid or abet unlawful practice by acquiescing once aware.

Backing

NSPE Code II.1.e, II.1.f, III.8.a, I.4, I.6

Rebuttal

Would not apply if the City Engineer's authority over contract awards were legitimate discretion within the law, or if internal escalation channels remained unexhausted and could still yield correction without external reporting.

Engineer A Appropriate Action Duty

Should Firm Z's engineers have questioned or declined the two contracts awarded outside the RFQ process, or accepted the contracts as offered by City D's Engineer?

Options considered:
O1 Firm Z's engineers raise concerns about the missing RFQ process with City D or decline to accept the contract until the process is corrected. Board's choice
O2 Firm Z's engineers accept the awarded contracts as presented by the City Engineer without inquiring into the procurement process used.
O3 Firm Z's engineers accept the contracts but first request written confirmation from City D that Council authorization and RFQ requirements were satisfied.
Argument structure (Toulmin):
Claim Conditioned on Firm Z's engineers having actual or constructive knowledge that the RFQ requirement was bypassed.

Firm Z's engineers should have questioned or declined the two contracts once they knew or should have known the awards bypassed the required RFQ process, rather than accepting the work without objection.

Grounds

The two most recent Firm Z contracts exceeded the dollar threshold requiring Council authorization and an RFQ process, yet were awarded solely on the City Engineer's approval, and Firm Z's engineers accepted the work.

Warrant

Registration law and Code III.8.a require engineers to conform with state registration and procurement laws in their practice, and this duty is not extinguished merely because the noncompliance was initiated by the client rather than the firm itself.

Backing

NSPE Code III.8.a

Rebuttal

Would not apply if Firm Z's engineers lacked knowledge of the RFQ requirement violation or had no practical means to verify City D's internal procurement compliance before accepting the award.

Firm Z Engineers Registration Law Duty

Should City D's Engineer conduct an RFQ process and obtain Council authorization for the Firm Z contracts exceeding the threshold, or continue awarding them based on convenience and longstanding relationship?

Options considered:
O1 The City Engineer initiates the required RFQ process and secures Council authorization before awarding contracts that exceed the statutory threshold. Board's choice
O2 The City Engineer continues to award contracts to Firm Z above the threshold on his own approval, citing administrative convenience and an established relationship.
O3 The City Engineer awards the contract without an RFQ but subsequently seeks Council ratification of the award after the fact.
Argument structure (Toulmin):
Claim Applies whenever the contract's dollar amount exceeds the Council-authorization threshold established by City D's procurement law.

City D's Engineer must conduct an RFQ process and obtain Council authorization before approving Firm Z contracts whose dollar amounts exceed the statutory threshold, rather than awarding them on his own approval alone.

Grounds

The two most recent Firm Z contracts exceeded the dollar threshold requiring Council authorization, but the City Engineer approved them without an RFQ, citing convenience and a longstanding relationship with Firm Z.

Warrant

Registration and procurement law (III.8.a) require qualifications-based selection through RFQ and Council authorization above the statutory threshold; administrative convenience or vendor familiarity does not create an exception to codified procurement requirements.

Backing

NSPE Code III.8.a, I.1

Rebuttal

Would not apply if the contract amounts fell below the threshold requiring Council authorization and an RFQ, in which case the City Engineer's independent approval would be lawful.

City Engineer QBS Compliance Duty City Engineer Contract Award Boundary
13 sequenced 7 actions 6 events
Case timeline
City D hired Firm X through a competitive RFQ process to maintain the citywide traffic model and review developer traffic studies, under a contract with annual extension options for up to 10 years.
Fulfills (1)
  • Conform with State Registration Laws in the Practice of Engineering
Causal-normative reasoning(confidence 0.70)
By awarding contracts through a qualifications-based process, A1 fulfills the registration-law conformance obligation and stands as the compliant baseline against which the downstream harms of the non-compliant award (procurement violation, competitive exclusion) are measured.
State changes (1)
  • began: Firm X Contract Compliance
City D awarded the first three of five contracts to Firm Z through competitive RFQ processes that attracted on average four submissions per advertisement.
Fulfills (1)
  • Conform with State Registration Laws in the Practice of Engineering
Causal-normative reasoning(confidence 0.70)
A2 reinforces the same fair, qualifications-based standard as A1, showing that lawful procurement practice is achievable and making City D's later deviation into non-compliance clearly a matter of choice rather than necessity.
The dollar amounts of the two most recent Firm Z contracts exceeded the threshold that automatically triggers the requirement for City Council authorization and an RFQ process under the procurement rules.
The City Engineer awarded the two most recent contracts to Firm Z solely on personal approval, without an RFQ process or City Council authorization, despite dollar amounts exceeding the thresholds requiring both.
Violates (1)
  • Conform with State Registration Laws in the Practice of Engineering
Causal-normative reasoning(confidence 0.85)
A3 violates the registration-law conformance obligation and is the causal root of both the procurement law violation and the competitive exclusion of qualified firms, so its wrongfulness lies precisely in setting off the chain that ultimately required reporting and investigation.
State changes (1)
  • began: Firm Z Contracts RFQ Noncompliance
The two most recent contracts with Firm Z were awarded without the required RFQ process and Council authorization, resulting in a violation of state and local procurement law and Code section III.8.a.
State changes (1)
  • began: Firm Z Contracts RFQ Noncompliance
Other qualified engineering firms were shut out of competing for City D contracts as a consequence of the exclusive awarding of contracts to Firm X and Firm Z without an RFQ process.
Engineer B approached Engineer A alleging that City D exclusively awards traffic engineering contracts to Firm X and civil engineering contracts to Firm Z without utilizing the RFQ process, excluding other qualified firms.
Fulfills (1)
  • Report Any Alleged Violation of the Code
Causal-normative reasoning(confidence 0.80)
A4 fulfills the duty to report code violations and is the direct response to the competitive exclusion caused by A3, converting a private harm into a matter subject to institutional review through the ensuing compliance investigation.
Engineer A committed to investigating Engineer B's concerns and reviewed seven years of City D contracting records, finding Firm X compliant and discovering that Firm Z's two most recent contracts bypassed required processes.
Fulfills (2)
  • Not Aid or Abet the Unlawful Practice of Engineering
  • Act as Faithful Agent or Trustee
Causal-normative reasoning(confidence 0.80)
A5 fulfills the faithful-agent and anti-aiding-unlawful-practice obligations by turning the report into concrete violation discovery and findings, and although this leads to City D's refusal of corrective action, the investigation itself upholds professional integrity by exposing the persistent noncompliance.
State changes (1)
  • began: Engineer A Noncompliance Knowledge
Through the investigation, Engineer A discovers the seven-year pattern of exclusive contract awards and confirms that the two most recent Firm Z contracts bypassed the required RFQ process and Council authorization.
State changes (1)
  • began: Engineer A Noncompliance Knowledge
The investigation establishes that Firm X's contract and the first three Firm Z contracts complied with the RFQ process, clearing those arrangements of the alleged wrongdoing.
State changes (1)
  • began: Firm X Contract Compliance
Engineer A brought the investigation findings to the City Engineer and recommended improvements to address compliance concerns with the contracting process.
Fulfills (3)
  • Act as Faithful Agent or Trustee
  • Not Aid or Abet the Unlawful Practice of Engineering
  • Report Any Alleged Violation of the Code
Causal-normative reasoning(confidence 0.80)
Because Engineer A's compliance investigation uncovered a genuine procurement violation, reporting those findings fulfills the duties to act as a faithful trustee, to avoid aiding unlawful engineering practice, and to report code violations, and this disclosure is precisely what triggers City D's Engineer to face a decision on corrective action.
State changes (1)
  • began: City Engineer Acknowledged Noncompliance
The City Engineer acknowledged that the two most recent Firm Z contracts did not comply with contracting requirements but refused to take corrective action, citing convenience and the longstanding relationship with Firm Z. This omission of required correction is treated as the City Engineer's conduct.
Violates (1)
  • Conform with State Registration Laws in the Practice of Engineering
Causal-normative reasoning(confidence 0.80)
By rejecting the corrective action that Findings Reporting called for, City D's Engineer violates the duty to conform with state registration laws, and this refusal directly causes the noncompliance to persist, showing how failing to act on a properly reported violation perpetuates the very harm the reporting obligation was meant to prevent.
State changes (1)
  • began: City Engineer Acknowledged Noncompliance
After the City Engineer dismissed the need for corrective action, the noncompliant contract arrangement with Firm Z remains unaddressed, leaving the violation in place and requiring further action by Engineer A.
State changes (1)
  • began: Firm Z Contracts RFQ Noncompliance
Narrative (5 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, recently hired as Assistant City Engineer for City D, where your duties include overseeing department staff, managing capital improvement programs, and supervising private development review. Engineer B, owner of a local civil engineering firm with no prior relationship to you, approaches you with concerns that City D has been awarding traffic engineering contracts exclusively to Firm X and civil engineering contracts exclusively to Firm Z without using the required request for qualifications process. State and local law establishes strong qualification based selection procurement requirements as part of the professional engineering licensure code, and City D's own procurement rules require RFQs and City Council authorization for contracts above a certain threshold. Your review confirms that Firm X was originally hired seven years ago through a proper RFQ to maintain the citywide traffic model and review private development traffic studies, but subsequent contracts, including those awarded to Firm Z, appear to have bypassed that process entirely. You now face a set of decisions about how thoroughly to investigate, whether to escalate the matter within City D or to outside authorities, and how to weigh your findings against the City Engineer's existing arrangements with these firms.

Main characters (5)

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.

Firm Z Roles in this case: Civil ConsultantEmployed Engineers

Guided by: Loyalty as Faithful Agent to City D, Integrity in Procurement Conduct, QBS Compliance in City D Contracting

If Firm Z's employed engineers are not properly registered as required by law, Engineer A's continued reliance on or approval of their work for City D could constitute aiding or abetting unlicensed practice, even though Engineer A has no direct control over Firm Z's internal registration compliance. This creates tension between accepting Firm Z's deliverables to keep city projects moving and the constraint against facilitating a registration law violation.

Attaches to role: Civil Consultant
Engineer A Roles in this case: Assistant City EngineerFaithful Agent

Engineer A must decide whether taking informal or internal corrective action within the organization satisfies the duty to act appropriately, or whether the severity of the violation obligates escalation to the state licensure board. Choosing the lighter internal response risks under-addressing a serious violation, while escalating immediately to the board risks disproportionate consequences for Engineer B if the matter could have been resolved internally.

Attaches to role: Assistant City Engineer

Engineer A owes loyalty and discretion to City D as employer while also carrying a professional duty to report code violations discovered in Engineer B's work. Acting on the reporting duty could strain or complicate the employer relationship, create friction with Engineer B, or expose City D to scrutiny, while suppressing it to preserve smooth working relations would breach the profession's reporting expectations.

Attaches to role: Assistant City Engineer

If Firm Z's employed engineers are not properly registered as required by law, Engineer A's continued reliance on or approval of their work for City D could constitute aiding or abetting unlicensed practice, even though Engineer A has no direct control over Firm Z's internal registration compliance. This creates tension between accepting Firm Z's deliverables to keep city projects moving and the constraint against facilitating a registration law violation.

Attaches to role: Assistant City Engineer
Engineer B Roles in this case: Civil Engineering Firm Owner

Engineer A must decide whether taking informal or internal corrective action within the organization satisfies the duty to act appropriately, or whether the severity of the violation obligates escalation to the state licensure board. Choosing the lighter internal response risks under-addressing a serious violation, while escalating immediately to the board risks disproportionate consequences for Engineer B if the matter could have been resolved internally.

Engineer A owes loyalty and discretion to City D as employer while also carrying a professional duty to report code violations discovered in Engineer B's work. Acting on the reporting duty could strain or complicate the employer relationship, create friction with Engineer B, or expose City D to scrutiny, while suppressing it to preserve smooth working relations would breach the profession's reporting expectations.

City D Roles in this case: Engineer City EngineerEmployerContracting Client

Engineer A owes loyalty and discretion to City D as employer while also carrying a professional duty to report code violations discovered in Engineer B's work. Acting on the reporting duty could strain or complicate the employer relationship, create friction with Engineer B, or expose City D to scrutiny, while suppressing it to preserve smooth working relations would breach the profession's reporting expectations.

Attaches to role: Employer
Firm X Roles in this case: Traffic ConsultantTraffic Engineering Consultant

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


These tensions did not map cleanly to a single character.

Tension between City Engineer QBS Compliance Duty and City Engineer Contract Award Boundary

The Board’s deliberation

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

It was not only ethical for Engineer B to complain to Engineer A, it was ethically required that Engineer B report his belief that statutory obligations were not being followed.
It was ethical for Engineer A to investigate City D’s contracting practices, both as a part of A’s own familiarization process and to follow up on Engineer B’s complaints.
Since the City D Engineer indicated they have no plans to change the contract arrangement with Firm Z, Engineer A is obligated to take appropriate action.
Opening States (3)
City Engineer Refusal Firm Z Contracts QBS Procurement Laws In Force Firm Z Relationship Favoritism
Summary
  • Professional obligations to report suspected code violations or statutory noncompliance take precedence over organizational loyalty or the desire to preserve smooth working relationships.
  • Engineers who discover potential violations in a colleague's work have both the standing and the duty to raise those concerns through appropriate channels rather than remaining silent.
  • The choice between informal correction and formal escalation to a licensure board should be guided by the severity and public safety implications of the violation, not by a desire to minimize interpersonal friction.