Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Community Engagement for Infrastructure Projects
Step 4 of 5

215

Entities

9

Provisions

5

Precedents

19

Questions

18

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
A sequential chain of transfers: the duty to correct the deficient report initially rests with Firm DBA; upon Firm DBA's dismissal of concerns, the obligation to address the ethical breach transfers to Engineer M's escalation duty toward the City; if the City's role or Firm DBA's conduct remains unaddressed, the obligation transfers again to the state licensure board as the terminal authority. Each transfer relieves the prior party of exclusive responsibility once the next actor is engaged, consistent with the framework's definition of transfer as a shift to a new set of governing rules/actors.
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 (9)
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.1 board + analysis Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 15)
Obligation
Firm DBA Community Input Duty
Genuine public engagement protects community welfare regarding the infrastructure project
Action
Concern Expression
Raising safety or welfare concerns supports holding public welfare paramount
State
Highway Project Failure Risk
Public safety and welfare are directly threatened by potential project failure
Obligation (2)
  • Firm DBA Community Input Duty
    Genuine public engagement protects community welfare regarding the infrastructure project
  • Engineer M Project Failure Advisory Duty
    Advising on project failure safeguards public welfare when engagement is flawed
Action (3)
  • Concern Expression
    Raising safety or welfare concerns supports holding public welfare paramount
  • Concern Dismissal
    Dismissing valid concerns risks violating the duty to hold public welfare paramount
  • Escalation to Client
    Escalating unresolved welfare concerns to the client upholds public safety priority
State (3)
  • Highway Project Failure Risk
    Public safety and welfare are directly threatened by potential project failure
  • Community P Displacement Exposure
    Public welfare is implicated when community displacement risks are not properly addressed
  • Deficient Community P Outreach Process
    Inadequate outreach undermines the ability to protect public welfare
Principle (1)
  • Public Welfare Applying Code to DBA
    This principle directly invokes the paramount safety health and welfare canon as the basis for applying the Code to Firm DBA
Role (3)
  • Firm DBA Consultant Engineer
    As the engineer conducting outreach it must hold public welfare paramount by ensuring genuine access for affected communities
  • Engineer M Lead Engineer
    As lead engineer on the project he must prioritize the welfare of the public including Community P
  • Firm DBA Principal Engineers
    As licensed engineers overseeing the firm they are responsible for upholding public welfare in all firm activities
Event (1)
  • Displacement Concerns Voiced
    Public welfare is directly implicated when displacement impacts are raised
Capability (2)
  • Engineer M Situation Recognition
    Recognizing flawed outreach practices relates to holding public welfare paramount
  • Engineer M Stakeholder Engagement
    Escalating concerns to protect public interest reflects paramount duty to public welfare
I.3 board + analysis Issue public statements only in an objective and truthful manner.
How this applies in the case (showing 3 of 12)
Obligation
Firm DBA Honest Support Claim Duty
Public statements about community support must be objective and truthful
Action
Misleading Report Submission
Submitting a misleading report violates the duty to be objective and truthful in public statements
State
Carefully Framed Engagement Report Omissions
Omitting information in reports violates the duty to be truthful in public statements
Obligation (2)
  • Firm DBA Honest Support Claim Duty
    Public statements about community support must be objective and truthful
  • Firm DBA Complete Report Duty
    Complete and accurate reporting of engagement findings is an objective public statement
Action (2)
  • Misleading Report Submission
    Submitting a misleading report violates the duty to be objective and truthful in public statements
  • Outreach Method Directive
    Directing outreach methods must ensure truthful and objective public communication
State (2)
  • Carefully Framed Engagement Report Omissions
    Omitting information in reports violates the duty to be truthful in public statements
  • Deficient Community P Outreach Process
    Public statements about outreach must objectively reflect the actual process used
Constraint (1)
  • Firm DBA Deceptive Report Prohibition
    Requires public statements to be objective and truthful which bars a deceptive engagement report
Role (2)
  • Firm DBA Consultant Engineer
    Must issue truthful and objective public statements when conducting engagement sessions
  • Engineer M Lead Engineer
    Must ensure public statements about the project are objective and truthful
Resource (1)
  • Firm DBA Public Engagement Report
    The report must present public engagement results objectively and truthfully
Capability (2)
  • Firm DBA Report Disclosure Competence
    Preparing the engagement report requires objective and truthful public statements
  • Firm DBA Public Engagement Competence
    Conducting public outreach sessions requires truthful and objective communication
I.5 board + analysis Avoid deceptive acts.
How this applies in the case (showing 3 of 11)
Obligation
Firm DBA Honest Support Claim Duty
Claiming community support that does not exist is a deceptive act
Action
Misleading Report Submission
Submitting a misleading report is a deceptive act prohibited by this provision
State
Carefully Framed Engagement Report Omissions
Deliberately framing a report to omit deficiencies constitutes a deceptive act
Obligation (2)
  • Firm DBA Honest Support Claim Duty
    Claiming community support that does not exist is a deceptive act
  • Firm DBA Complete Report Duty
    Omitting details of when and where sessions were held is deceptive
Action (2)
  • Misleading Report Submission
    Submitting a misleading report is a deceptive act prohibited by this provision
  • Outreach Method Directive
    Directing deceptive outreach methods would violate the prohibition on deceptive acts
State (2)
  • Carefully Framed Engagement Report Omissions
    Deliberately framing a report to omit deficiencies constitutes a deceptive act
  • Engineer M Awareness Of Outreach Deficiencies
    Knowing about deficiencies yet not disclosing them is deceptive
Constraint (1)
  • Firm DBA Deceptive Report Prohibition
    Directly requires avoiding deceptive acts such as a misleading public report
Role (1)
  • Firm DBA Consultant Engineer
    Scheduling meetings at inaccessible times and locations for Community P may constitute a deceptive act
Resource (1)
  • Firm DBA Public Engagement Report
    The report must avoid deceptive representation of public engagement outcomes
Capability (2)
  • Engineer M Situation Recognition
    Identifying deceptive outreach practices relates to avoiding deceptive acts
  • Firm DBA Report Disclosure Competence
    The report's alleged fraudulent nature implicates avoidance of deceptive acts
II.1.d board + analysis Engineers shall not permit the use of their name or associate in business ventures with any person or firm that they believe is engaged in fraudulent or dishonest enterprise.
How this applies in the case (showing 3 of 10)
Obligation
Firm DBA Principals Ethical Practice Duty
Principals must not allow their names to be used in dishonest engagement practices
Action
Ethics Conference With Firm
Discussing association with a potentially dishonest firm relates to this provision
State
Engineer M Association With Firm DBA
Engineer M associating with a firm engaged in dishonest practices violates this provision
Obligation (2)
  • Firm DBA Principals Ethical Practice Duty
    Principals must not allow their names to be used in dishonest engagement practices
  • Engineer M Conditional Licensure Reporting Duty
    Engineer M must avoid association with a firm he believes is engaging in dishonest conduct
Action (1)
  • Ethics Conference With Firm
    Discussing association with a potentially dishonest firm relates to this provision
State (2)
  • Engineer M Association With Firm DBA
    Engineer M associating with a firm engaged in dishonest practices violates this provision
  • Firm DBA Report Code Violation
    Association with a firm shown to violate the code raises this provision directly
Constraint (2)
  • Engineer M Dishonest Association Boundary
    Prohibits associating in business ventures with a firm believed to be dishonest
  • Engineer M Dishonest Association Prohibition
    Directly matches the prohibition on permitting name use or association with a dishonest firm
Role (2)
  • Engineer M Firm Partner
    Partners with Firm DBA and must not associate with a firm believed to be engaged in dishonest practices
  • Engineer M Lead Engineer
    Must not permit continued association with Firm DBA if its outreach practices are dishonest
Capability (1)
  • Engineer M Work Refusal Judgment
    Deciding whether to remain associated with a potentially dishonest firm reflects this prohibition
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 10)
Obligation
Engineer M Conditional Licensure Reporting Duty
Engineer M must report alleged Code violations to the licensure board if the City fails to act
Action
Licensure Board Reporting Decision
Deciding whether to report violations to a licensure board directly reflects this reporting duty
State
Firm DBA Report Code Violation
Knowledge of a code violation requires reporting to appropriate authorities
Obligation (2)
  • Engineer M Conditional Licensure Reporting Duty
    Engineer M must report alleged Code violations to the licensure board if the City fails to act
  • Engineer M Escalation to City Duty
    Engineer M must escalate and report ethical violations to appropriate authorities
Action (2)
  • Licensure Board Reporting Decision
    Deciding whether to report violations to a licensure board directly reflects this reporting duty
  • Escalation to Client
    Escalating known violations to appropriate parties supports the duty to report misconduct
State (2)
  • Firm DBA Report Code Violation
    Knowledge of a code violation requires reporting to appropriate authorities
  • Engineer M Awareness Of Outreach Deficiencies
    Awareness of deficiencies that constitute violations should have been reported
Role (2)
  • Engineer M Lead Engineer
    Has knowledge of alleged Code violations by Firm DBA and must consider reporting to authorities
  • State Engineering Licensure Board
    Is the potential recipient of a report from Engineer M regarding alleged violations
Capability (2)
  • Engineer M Disclosure
    Deciding whether to report Firm DBA to authorities directly reflects this reporting duty
  • Engineer M Stakeholder Engagement
    Escalating the issue to appropriate parties aligns with reporting code violations
II.3.a board + analysis Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.
How this applies in the case (showing 3 of 11)
Obligation
Firm DBA Complete Report Duty
Reports must be objective, truthful, and include all relevant and pertinent information
Action
Misleading Report Submission
Submitting a misleading report violates the duty to be truthful and complete in professional reports
State
Carefully Framed Engagement Report Omissions
Reports must be objective, truthful, and include all relevant pertinent information
Obligation (2)
  • Firm DBA Complete Report Duty
    Reports must be objective, truthful, and include all relevant and pertinent information
  • Firm DBA Honest Support Claim Duty
    Statements about community support in reports must be objective and truthful
Action (1)
  • Misleading Report Submission
    Submitting a misleading report violates the duty to be truthful and complete in professional reports
State (2)
  • Carefully Framed Engagement Report Omissions
    Reports must be objective, truthful, and include all relevant pertinent information
  • Deficient Community P Outreach Process
    Reporting on the outreach process must include all pertinent facts about its deficiencies
Constraint (1)
  • Firm DBA Deceptive Report Prohibition
    Requires inclusion of all relevant facts in reports, barring omission of material engagement details
Role (2)
  • Firm DBA Consultant Engineer
    Must be objective and truthful and include all relevant information in outreach reports and statements
  • Engineer M Lead Engineer
    Must ensure professional reports and statements on the project are truthful and complete
Event (1)
  • Supportive Comments Reception
    Reports on community reception must objectively include all relevant feedback not just supportive comments
Resource (1)
  • Firm DBA Public Engagement Report
    The report is a professional statement that must be objective and include all relevant dated information
Capability (1)
  • Firm DBA Report Disclosure Competence
    The report must be objective, truthful, and include all relevant pertinent information
III.1.b board + analysis Engineers shall advise their clients or employers when they believe a project will not be successful.
How this applies in the case (showing 3 of 10)
Obligation
Engineer M Project Failure Advisory Duty
Engineer M must advise the City when he believes the project will not be successful
Action
Concern Expression
Expressing concerns about project viability aligns with advising employers of potential failure
State
Highway Project Failure Risk
Engineers must advise clients when a project is believed likely to fail
Obligation (1)
  • Engineer M Project Failure Advisory Duty
    Engineer M must advise the City when he believes the project will not be successful
Action (2)
  • Concern Expression
    Expressing concerns about project viability aligns with advising employers of potential failure
  • Escalation to Client
    Escalating concerns to the client fulfills the duty to advise when a project may not succeed
State (2)
  • Highway Project Failure Risk
    Engineers must advise clients when a project is believed likely to fail
  • Engineer M Awareness Of Outreach Deficiencies
    Awareness of deficiencies that could cause project failure should be disclosed to the client
Role (2)
  • Engineer M Lead Engineer
    Must advise the City if he believes the public engagement process will undermine project success or legitimacy
  • Firm DBA Consultant Engineer
    Should have advised the City or Engineer M if the outreach approach would not succeed in genuine engagement
Event (2)
  • Low Community Participation
    Engineer should advise client that low participation may threaten project success
  • Displacement Concerns Voiced
    Engineer should advise client that unresolved displacement concerns could jeopardize the project
Capability (1)
  • Engineer M Disclosure
    This provision directly requires advising the City if the project appears unlikely to succeed
III.3.a board + analysis Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
How this applies in the case (showing 3 of 12)
Obligation
Firm DBA Honest Support Claim Duty
Claiming unsupported community support is a material misrepresentation of fact
Action
Misleading Report Submission
Submitting a misleading report involves material misrepresentation or omission of facts
State
Carefully Framed Engagement Report Omissions
Omitting material facts in the engagement report is a direct misrepresentation
Obligation (2)
  • Firm DBA Honest Support Claim Duty
    Claiming unsupported community support is a material misrepresentation of fact
  • Firm DBA Complete Report Duty
    Omitting session times and locations constitutes omission of material facts
Action (2)
  • Misleading Report Submission
    Submitting a misleading report involves material misrepresentation or omission of facts
  • Outreach Method Directive
    Directing outreach that omits material facts violates this provision
State (2)
  • Carefully Framed Engagement Report Omissions
    Omitting material facts in the engagement report is a direct misrepresentation
  • Deficient Community P Outreach Process
    Failing to disclose the deficient outreach process omits a material fact
Constraint (1)
  • Firm DBA Deceptive Report Prohibition
    Prohibits statements that omit material facts such as location and timing of engagement sessions
Role (1)
  • Firm DBA Consultant Engineer
    Must avoid statements that misrepresent or omit material facts about the outreach process and its results
Event (1)
  • Supportive Comments Reception
    Selectively presenting supportive comments could omit material facts about opposition
Resource (1)
  • Firm DBA Public Engagement Report
    The report must avoid material misrepresentation or omission of facts about public engagement results
Capability (2)
  • Firm DBA Report Disclosure Competence
    The report's alleged omissions relate to avoiding material misrepresentation or omission
  • Engineer M Situation Recognition
    Recognizing omitted material facts about outreach sessions relates to this provision
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 9)
Obligation
Engineer M Escalation to City Duty
Engineer M must present evidence of unethical practice to proper authorities rather than act maliciously
Action
Licensure Board Reporting Decision
Reporting unethical conduct to proper authorities aligns with this provision
State
Firm DBA Report Code Violation
Reporting suspected unethical practice must go through proper authorities rather than false accusations
Obligation (2)
  • Engineer M Escalation to City Duty
    Engineer M must present evidence of unethical practice to proper authorities rather than act maliciously
  • Engineer M Conditional Licensure Reporting Duty
    Reporting suspected unethical practice to the licensure board follows the proper authority process
Action (2)
  • Licensure Board Reporting Decision
    Reporting unethical conduct to proper authorities aligns with this provision
  • Ethics Conference With Firm
    Discussing unethical practices internally before reporting aligns with presenting information to proper authority
State (1)
  • Firm DBA Report Code Violation
    Reporting suspected unethical practice must go through proper authorities rather than false accusations
Role (2)
  • Engineer M Lead Engineer
    Must present evidence of unethical practice by Firm DBA to proper authorities rather than remain silent
  • Firm DBA Principal Engineers
    As licensed engineers they bear responsibility for addressing unethical practices within their firm
Capability (2)
  • Engineer M Work Refusal Judgment
    Presenting concerns about Firm DBA's conduct to proper authorities reflects this obligation
  • Engineer M Normative Framework Assessment
    Identifying obligations regarding unethical practice by others relates to this provision
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 5 Lineage Graph

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

Principle Established:

A registered professional is obliged to include relevant and pertinent information in a report; omitting such information fails to help stakeholders make informed decisions and does not protect public safety, health, and welfare.

Citation Context:

Cited to support the principle that a registered professional's report must include relevant and pertinent information to protect public safety, health, and welfare, directly applicable to the omissions in Firm DBA's report.

Relevant Excerpts
discussion: "The BER found that as a registered professional, that Engineer was obliged to include relevant and pertinent information in a report to the organization... Likewise, in this case, pertinent information was missing from the report."

Principle Established:

An engineer who fails to act further after being sidelined from a public safety issue, despite knowledge of a risk, fails to fulfill the ethical obligation to hold paramount public safety, health, and welfare.

Citation Context:

Cited by analogy to establish that Engineer M, like the engineer in that case, has an ongoing duty to hold paramount the safety, health, and welfare of the public even when removed from direct responsibility or facing resistance.

Relevant Excerpts
discussion: "The BER found that Engineer A did not fulfill ethical obligations of holding paramount the safety, health, and welfare of the public. As in this case, Engineer M, therefore also has a duty to hold paramount the safety, health, and welfare of the public."

Principle Established:

The Code applies universally to NSPE members; it would be a major error to apply one standard of conduct to one set of members and another standard to another set of members.

Citation Context:

Cited to support the conclusion that the Code applies universally to all NSPE members regardless of differing circumstances, supporting the finding that Firm DBA (with PE ownership/supervision) must abide by the Code despite providing non-engineering services.

Relevant Excerpts
discussion: "BER Case 98-2 addressed the ethical concerns of an international NSPE member... it would be a major error for NSPE to apply one standard of conduct to one set of NSPE members and another standard of conduct to another set of NSPE members."

Principle Established:

When an engineer becomes aware of a potential ethical violation by another party, the engineer should first seek clarification, and if not satisfied, may be required to report the matter to the state engineering licensure board.

Citation Context:

Cited by analogy to support the recommended course of action for Engineer M, showing that an engineer should first seek clarification from the party in question and, if unsatisfied, report the matter to the state licensure board.

Relevant Excerpts
discussion: "The BER found that Engineer A should communicate with Engineer X to obtain clarification regarding the matter in question. The BER further found that if Engineer A was not sufficiently satisfied with Engineer X's explanation, Engineer A may be required to report this matter to the state engineering licensure board."

Principle Established:

An engineering firm providing sub-professional services was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct.

Citation Context:

Cited to explore whether the Code applies to firms providing sub-professional (non-engineering) services, as was the case with Firm DBA's public relations work.

Relevant Excerpts
discussion: "In BER Case 60-3, the facts indicated that an engineering firm was providing sub-professional services and, because of that, the firm was not required to abide by the provisions of the Canons of Ethics and Rules of Professional Conduct. The conclusion by the BER in BER Case 60-3 was that the Canons and Rules did not apply."
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 46% Facts Similarity 22% Discussion Similarity 60% Provision Overlap 40% Outcome Alignment 100% Tag Overlap 67% Principle Overlap 48%
Shared provisions: I.1, I.5, II.3.A, III.3.A Same outcome unethical View Synthesis
Component Similarity 48% Facts Similarity 30% Discussion Similarity 45% Provision Overlap 23% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 50%
Shared provisions: I.1, II.1.F, III.7 Same outcome unethical View Synthesis
Component Similarity 47% Facts Similarity 44% Discussion Similarity 39% Provision Overlap 15% Outcome Alignment 100% Tag Overlap 50% Principle Overlap 55%
Shared provisions: I.1, II.1.F Same outcome unethical View Synthesis
Component Similarity 46% Facts Similarity 35% Discussion Similarity 40% Provision Overlap 18% Outcome Alignment 100% Tag Overlap 30% Principle Overlap 51%
Shared provisions: I.3, I.5 Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 37% Discussion Similarity 65% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 56%
Same outcome unethical View Synthesis
Component Similarity 51% Facts Similarity 42% Discussion Similarity 60% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 55%
Shared provisions: III.7 Same outcome unethical View Synthesis
Component Similarity 45% Facts Similarity 43% Discussion Similarity 47% Provision Overlap 15% Outcome Alignment 100% Tag Overlap 10% Principle Overlap 54%
Shared provisions: I.1, I.3 Same outcome unethical View Synthesis
Component Similarity 43% Facts Similarity 40% Discussion Similarity 50% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 60%
Shared provisions: I.1 Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 44% Discussion Similarity 58% Outcome Alignment 100% Tag Overlap 8% Principle Overlap 55%
Same outcome unethical View Synthesis
Component Similarity 44% Facts Similarity 37% Discussion Similarity 45% Provision Overlap 9% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 53%
Shared provisions: I.1 Same outcome unethical View Synthesis
Questions & Conclusions (3 board)
View Extraction
Board Board question 1

Should Engineer M challenge the validity of Firm DBA’s report?

Board conclusion Engineer M should challenge the validity of Firm DBA’s report as Firm DBA did not abide by the Code in a number of instances.
Resolved by: Engineer M's duty to public welfare and objective reporting outweighs deference to the firm's finished work product and any interest in preserving a smooth professional relationship. (confidence 0.85)
I.3. I.5. II.3.a. III.3.a. 3 principles 3 facts Conditions Narrative
Implicit (1)

Should Engineer M have withdrawn from or refused continued association with Firm DBA once Firm DBA dismissed Engineer M's concerns and proceeded with a misleading report?

AnalyticalThe Board's recommendation that Engineer M first attempt correction with Firm DBA and only later consider licensure board reporting understates the significance of the sequence of events already completed: Engineer M raised concerns, Firm DBA dismissed them, and a misleading report was submitted despite that dismissal. This sequence arguably already satisfies the threshold for a mandatory reporting obligation under II.1.f, since Engineer M has actual knowledge of a Code violation that was not remedied through informal means before submission. The Board's phased approach may therefore understate the urgency of Engineer M's reporting duty, particularly given that the report has already been submitted to the City and may be relied upon in decisions affecting Community P's displacement risk.
Resolved by: The board weighed the courtesy of attempting further informal correction with Firm DBA against the mandatory reporting duty under II.1.f, and found the latter already triggered by the completed sequence of dismissal and submission. (confidence 0.72)
II.1.f. 3 principles 3 facts Conditions Narrative
Principle tension (2)

How should Honesty in Support Claim be balanced against Firm DBA's deference to the City's directive to conduct outreach sessions favoring an alternate route for economic and political reasons?

AnalyticalRegarding Q201: Firm DBA's deference to the City's political and economic preferences does not excuse the omission of material outreach details from its report. The Code's requirement of honesty in public statements (I.3, II.3.a) is not subordinate to a client's business or political preferences; even where a client directs the format or venue of outreach, the engineer's duty to truthfully report the process and its limitations remains independent and non-negotiable.
Resolved by: The board ruled that the Code's honesty and complete-reporting duties override client-driven business or political preferences, refusing to subordinate truthful reporting to client convenience. (confidence 0.77)
I.3. II.3.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe case demonstrates that client directives, even when framed as legitimate business, economic, or political considerations, cannot subordinate the engineering duties of objectivity and complete reporting. Firm DBA attempted to resolve the tension between satisfying the City's preferences and maintaining honest reporting by omitting material facts rather than either refusing the City's directive or accurately reporting the deficient process. This resolution was improper: the Code does not permit engineers to trade away truthful reporting for client satisfaction, meaning that when such tensions arise, the duty to the public and to honest documentation must prevail over accommodating a client's political or economic preferences.
Resolved by: The board weighed the City's economic and political preference for a favorable outreach narrative against the engineer's duty of objective and complete reporting, and held that the reporting duty must prevail rather than be traded away. (confidence 0.85)
I.3. I.5. II.3.a. III.3.a. 3 principles 3 facts Conditions Narrative

Does Complete Reporting in Engagement Report conflict with Firm DBA's apparent obligation to satisfy the City's business preferences and prior project practices?

Theoretical (1)

Did Engineer M act with professional integrity, in a virtue-ethics sense, by voicing concerns to Firm DBA about the outreach process even though the objection did not prevent the report's submission or change the outcome?

Counterfactual (2)

If Firm DBA's outreach notices had provided a method for written comment submission, would the Board still find the report's claim of Community P's support to be a material misrepresentation under III.3.a?

AnalyticalRegarding Q403: Even if Firm DBA's notices had included a method for written comment submission, the report's claim of Community P's support would likely still constitute a material misrepresentation under III.3.a, given that the sessions were held at inaccessible times and locations far from Community P, and no virtual option was offered. The core violation lies in the systemic barriers to genuine participation, not solely in the absence of a written-comment channel.
Resolved by: The board weighed the single proposed cure (a written-comment method) against the broader set of accessibility barriers and found the cure insufficient to offset the larger systemic problem. (confidence 0.75)
III.3.a. 3 principles 3 facts Conditions Narrative

If the public engagement sessions had been held in Community P at accessible times and locations rather than in Community Q, would the Board's conclusion that Firm DBA's report was invalid and non-objective still hold?

Also discussed in: C303
Board Board question 2

Should Engineer M raise any concerns with the City, as the client, and, if so, how?

Board conclusion Engineer M should first confer with Firm DBA to correct all discrepancies in the report. If no agreement can be made going forward, Engineer M should confer with the City to outline the ethical obligations. Engineer M should also consider any obligations they may have to report to the state licensure board.
Resolved by: The board balances collegial correction (attempting resolution with the firm first) against the escalating duty to protect the public and report violations, allowing escalation only after informal remedies fail. (confidence 0.80)
II.1.f. III.1.b. II.1.d. 3 principles 3 facts Conditions Narrative
Implicit (1)

Does the City's explicit directive to hold outreach sessions in a way that disadvantages Community P constitute an independent ethical violation by the City that Engineer M must address, separate from Firm DBA's report deficiencies?

AnalyticalThe Board's recommendation that Engineer M confer with the City about ethical obligations should be extended to recognize that the City itself may bear independent ethical responsibility. The City's explicit directive to conduct outreach sessions in a manner that disadvantaged Community P was not merely a business preference but effectively directed a violation of public welfare and objectivity principles. Engineer M's duty to escalate to the City therefore should not be framed only as informing a client of a consultant's Code violations, but as confronting the client's own role in causing those violations, which may require Engineer M to document the City's directive separately from Firm DBA's report failures.
Resolved by: The board extends the escalation duty by weighing the client relationship against the more fundamental public welfare obligation, concluding the latter requires confronting the client's own causal role rather than treating the client only as a recipient of the consultant's violations. (confidence 0.75)
I.1. II.1.f. III.1.b. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101: The City's directive to schedule outreach sessions in ways that disadvantage Community P raises a distinct ethical concern from Firm DBA's reporting deficiencies. While Firm DBA bears direct Code responsibility for executing and reporting on the sessions, the City's instruction—motivated by economic, political, and social considerations—suggests the client itself directed an inequitable process. Engineer M's obligation to hold paramount public welfare (I.1) means this should not be treated merely as an internal firm problem; Engineer M has an independent duty to raise this directly with the City as the client, separate from any corrective dialogue with Firm DBA.
Resolved by: The board separated the City's directive-driven inequity from Firm DBA's reporting failure, holding that Engineer M's paramount public welfare duty requires escalation to the City independently of any internal firm corrective dialogue. (confidence 0.75)
I.1. 2 principles 3 facts Conditions Narrative
Theoretical (1)

From a deontological standpoint, does Engineer M's duty under II.1.f to report known Code violations to the appropriate authorities take precedence over the professional courtesy owed to Firm DBA as a business partner, once informal correction attempts fail?

AnalyticalRegarding Q304: Once informal correction attempts with Firm DBA fail, Engineer M's duty under II.1.f to report known Code violations to appropriate authorities takes precedence over any professional courtesy or business relationship with Firm DBA. The Code does not permit collegial loyalty to override the obligation to protect the integrity of the profession and public welfare when a documented violation persists uncorrected.
Resolved by: The board ranked the duty to protect professional integrity and public welfare above the value of collegial or business loyalty once informal remedies were exhausted. (confidence 0.80)
II.1.f. 2 principles 3 facts Conditions Narrative
Board Board question 3

Are Firm DBA’s actions ethical? Even though Firm DBA is not providing engineering services, are they required to abide by NSPE’s Code of Ethics?

Board conclusion The actions of Firm DBA are not ethical under the Code as the services provided were under the supervision and ownership of licensed professional engineers.
Resolved by: The board weighs the firm's claim that outreach is a non-engineering service against the fact of engineer ownership and supervision, finding the latter controlling. (confidence 0.80)
I.1. II.3.a. 2 principles 3 facts Conditions Narrative
Implicit (1)

Does Firm DBA's use of a nominally non-engineering 'communications and public relations' department to conduct outreach represent a structural attempt to evade engineering ethics obligations, and should such organizational separations be permitted to shield licensed firms from Code accountability?

AnalyticalThe Board's conclusion that Firm DBA's actions are unethical because the firm is owned and supervised by licensed engineers should be extended to address the structural mechanism of evasion at issue: organizing outreach functions under a nominally non-engineering 'communications and public relations' department does not exempt those activities from Code scrutiny. Because licensed engineers retain supervisory and ownership control over that department, the Code's public welfare and objectivity obligations attach to the department's outputs as professional services performed under the firm's engineering practice, regardless of internal labeling. Permitting such organizational separations to shield outreach or communications work from ethical accountability would create an loophole undermining the Code's intent wherever firms diversify into adjacent service lines.
Resolved by: The board weighs the firm's structural argument that a nominally non-engineering department escapes Code scrutiny against the substantive fact of continued engineer ownership and supervision, finding substance controls over labeling. (confidence 0.75)
I.1. II.3.a. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q103: Firm DBA's structural placement of outreach activities within a nominally non-engineering 'communications and public relations' department does not shield the firm from Code obligations. Because licensed professional engineers supervise and own all departments, including this one, the substance of the activity—informing a professional engineering report used to justify a public infrastructure decision—triggers Code applicability regardless of internal departmental labels. Permitting such organizational separations to evade accountability would create an exploitable loophole undermining the Code's intent to protect public welfare wherever licensed engineers direct or control the underlying work product.
Resolved by: The board weighed the firm's structural/organizational labeling argument against the substantive fact of engineer ownership and control, finding substance over form controls Code applicability. (confidence 0.78)
I.1. 2 principles 3 facts Conditions Narrative
AnalyticalThe tension between Firm DBA's claim that its public relations department was not performing 'engineering services' and the Board's application of the Code to that department is resolved by anchoring accountability in firm structure rather than departmental labeling. Because licensed professional engineers held supervisory and ownership control over all departments, including the communications unit, the Public Welfare principle attaches to the firm's overall conduct rather than being confined to activities formally labeled as engineering. This establishes that organizational subdivision cannot be used to wall off non-technical functions from Code obligations when those functions are ultimately controlled by licensed engineers and materially affect public welfare outcomes like community displacement risk.
Resolved by: The board weighed Firm DBA's argument that non-technical departmental labeling exempts it from Code scrutiny against the reality of licensed-engineer control, and found firm-wide accountability outweighs departmental characterization. (confidence 0.85)
I.1. II.1.d. 3 principles 3 facts Conditions Narrative
Principle tension (1)

How should Public Welfare Applying Code to DBA be reconciled with Firm DBA's position that its public relations department is not itself performing 'engineering services' and thus arguably outside Code scrutiny?

AnalyticalRegarding Q203: Firm DBA cannot avoid Code scrutiny by asserting its public relations department was not performing 'engineering services.' Because the department's outreach data directly fed into and shaped an engineering report relied upon for infrastructure decision-making, and because licensed engineers supervised and owned the department, the activity falls within the scope of professional practice governed by the Code. The public welfare obligation in I.1 and objectivity requirement in II.3.a extend to all firm activities that materially inform engineering judgments, irrespective of internal departmental characterization.
Resolved by: The board weighed the firm's internal departmental labeling against the functional and structural connection between the PR activity and engineering judgment, and found the substantive connection controlling. (confidence 0.85)
I.1. II.3.a. 3 principles 3 facts Conditions Narrative
Also discussed in: C302
Theoretical (2)

From a deontological perspective, did Firm DBA fulfill its duty of complete and truthful reporting under Code provisions I.3, II.3.a, and III.3.a when it omitted the times, locations, and lack of a written-comment method from its public engagement report?

AnalyticalRegarding Q301: From a deontological standpoint, Firm DBA violated its duty of complete and truthful reporting under I.3, II.3.a, and III.3.a. These provisions impose a categorical obligation to disclose material facts regardless of consequences; omitting session times, locations, and the absence of a written-comment method constitutes a failure of duty independent of whether the omissions changed the ultimate outcome or were directed by the City.
Resolved by: The board treated the duty of truthful and complete disclosure as categorical, so it could not be offset by arguments about outcome-neutrality or client direction. (confidence 0.85)
I.3. II.3.a. III.3.a. 3 principles 3 facts Conditions Narrative
Also discussed in: C301

From a consequentialist perspective, does the outcome of securing City approval for the highway route through Community P justify Firm DBA's selective omission of scheduling and accessibility details in its report, given the resulting risk of displacement and disruption to an already overburdened community?

Also discussed in: C301
Counterfactual (2)

If the City had not specifically instructed Firm DBA to conduct the outreach sessions in that manner, would the Board still conclude that Firm DBA's actions were unethical, or would the City's directive have diluted Firm DBA's independent responsibility under the Code?

AnalyticalRegarding Q401: Even if the City had not specifically directed the manner of outreach, Firm DBA would still bear independent responsibility under the Code for the deficiencies in its public engagement process and report. The Code's objectivity and completeness requirements (I.3, II.3.a, III.3.a) attach to the engineer's own professional judgment and reporting conduct, not merely to client instructions; a client directive does not transfer or dilute the engineer's personal accountability for truthful representation.
Resolved by: The board weighed client deference against personal professional accountability and held that accountability for truthful reporting cannot be delegated to or excused by client instruction. (confidence 0.80)
I.3. II.3.a. III.3.a. 3 principles 3 facts Conditions Narrative

If Firm DBA's communications and public relations department had not been staffed by licensed professional engineers in supervisory and ownership roles, would the Board still find that Firm DBA was obligated to abide by the NSPE Code of Ethics for these outreach activities?

Also discussed in: C302
Analytical questions (2)

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)

What direct ethical obligations, if any, does Engineer M owe to Community P as an affected but non-client stakeholder, distinct from Engineer M's contractual obligations to the City?

AnalyticalRegarding Q104: Although Community P is not Engineer M's contractual client, Engineer M owes it an obligation grounded in the Code's paramount duty to public welfare (I.1). This obligation is not diminished by the absence of a direct contractual relationship; it requires Engineer M to ensure that decisions materially affecting Community P's displacement and economic disruption are based on an honest and complete factual record, and to escalate concerns when that record is compromised.
Resolved by: The board balanced the absence of contractual privity against the Code's paramount, non-contractual public welfare duty, finding the latter controls regardless of client relationship. (confidence 0.75)
I.1. 1 principle 3 facts Conditions Narrative
Principle tension (1)

How should Professional Dignity in Community P Outreach be balanced against Objectivity in DBA Report when accurately reporting the outreach process would itself reveal harm to Community P's dignity and interests?

AnalyticalProfessional Dignity in Community P Outreach and Objectivity in DBA Report were not actually in tension despite surface appearances; rather, honoring Community P's dignity required objective reporting, and it was only Firm DBA's choice to conceal outreach deficiencies that created an apparent conflict. Had Firm DBA disclosed the true scheduling, location, and comment-method limitations, the report would have simultaneously respected Community P's stake in the process and satisfied objectivity requirements. This suggests that in engagement-based engineering work, transparency about process limitations is not merely a reporting formality but a mechanism through which respect for an affected community's dignity and objective professional practice are jointly achieved.
Resolved by: The board treated the apparent conflict between honoring Community P's dignity and maintaining objectivity as resolvable rather than genuinely competing, since disclosure would have simultaneously satisfied both obligations. (confidence 0.80)
I.3. II.3.a. III.3.a. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (6)
View Extraction

Should Firm DBA issue a complete and honest report of the engagement process, or submit a report that omits session logistics and claims Community P's support?

Options considered:
O1 Disclose the actual times and locations of sessions, note that written comments were not accepted, and refrain from claiming community support not established by the input gathered. Board's choice
O2 Leave out scheduling and location details but stop short of asserting that Community P supports the project, limiting the misrepresentation.
O3 Submit the report as actually issued: omitting session times, locations, and comment-method details while claiming Community P's support for the project.
Argument structure (Toulmin):
Claim Unconditionally, once the omitted facts are material to the report's conclusions.

Firm DBA should have issued a complete, objective report disclosing session times, locations, and the absence of a written-comment method, and should not have claimed Community P's support without evidentiary basis.

Grounds

The engagement sessions were held in Community Q at inaccessible times, no written-comment method was provided, participation from Community P was low, displacement concerns were voiced, and the submitted report omitted these facts while stating community support for the project.

Warrant

Engineers and firms performing professional services must issue public statements objectively and truthfully and must not omit material facts that qualify a report's conclusions; this duty is not suspended because the client prefers a favorable outcome.

Backing

NSPE Code I.3, II.3.a, III.3.a

Rebuttal

Would not apply if the omitted scheduling and comment-method details were genuinely immaterial to the report's stated purpose, or if Firm DBA reasonably believed such logistical disclosures fell outside the scope of the requested report.

Firm DBA Complete Report Duty Firm DBA Deceptive Report Prohibition

Should Engineer M challenge the validity of Firm DBA's report given its material omissions, or accept the report as issued?

Options considered:
O1 Formally raise the report's omissions and unsupported claims as a Code violation requiring correction before it is relied upon. Board's choice
O2 Treat the report's content as within Firm DBA's discretion as a communications matter, deferring to their judgment without objection.
O3 Mention discomfort with the report informally but stop short of formally disputing its validity or demanding correction.
Argument structure (Toulmin):
Claim Given Engineer M's actual knowledge of the omissions and their materiality to the report's conclusions.

Engineer M should challenge the validity of Firm DBA's report because it fails the Code's standards of complete and objective reporting.

Grounds

Firm DBA's report omitted where and when sessions were held, did not disclose that written comments were not accepted, and claimed Community P's support despite low participation and voiced displacement concerns.

Warrant

An engineer must not permit his name to be associated with work he believes is fraudulent or dishonest, and must act to ensure reports meet the Code's objectivity and completeness requirements.

Backing

NSPE Code I.3, II.3.a, III.3.a

Rebuttal

Would not apply if the omissions were merely stylistic choices rather than material misrepresentations, or if Engineer M lacked direct knowledge that the omissions were intentional rather than incidental.

Engineer M Escalation to City Duty Engineer M Dishonest Association Prohibition

When Firm DBA dismisses Engineer M's concerns, should Engineer M escalate stepwise from the firm to the City and then to the licensure board, or report to the licensure board immediately?

Options considered:
O1 Confer with Firm DBA first to correct discrepancies, escalate to the City if uncorrected, and consider licensure board reporting only if the City does nothing. Board's choice
O2 Bypass further internal or client-level correction attempts and report Firm DBA's actions to the state engineering licensure board immediately given the dismissed concerns.
O3 Raise the issue once with Firm DBA and, having been dismissed, take no further escalatory steps toward the City or licensure board.
Argument structure (Toulmin):
Claim Provided informal correction is attempted first, unless the report's reliance and harm risk make immediate escalation necessary.

Engineer M should first confer with Firm DBA to correct the discrepancies, then if unresolved confer with the City, and finally consider reporting to the state licensure board if the City takes no action.

Grounds

Firm DBA dismissed Engineer M's expressed concerns and proceeded to submit the report, which may already be relied upon by the City in decisions affecting Community P's displacement.

Warrant

Engineers must escalate known Code violations first internally, then to the client, and ultimately to appropriate licensing authorities once informal correction fails; collegial loyalty does not override the duty to protect the public and the profession's integrity once a violation persists uncorrected.

Backing

NSPE Code II.1.f, III.3.a

Rebuttal

Would not apply if the omissions are judged not material to the City's decision-making, if internal correction remains plausible, or if escalation would cause disproportionate harm relative to the benefit gained.

Engineer M Conditional Licensure Reporting Duty

Should Engineer M withdraw from continued association with Firm DBA, or remain involved to pursue correction and escalation?

Options considered:
O1 End continued professional association with Firm DBA immediately given its dismissal of ethical concerns and submission of a misleading report.
O2 Continue association with Firm DBA while escalating the unresolved concerns to the City, preserving a chance to correct the record before withdrawing. Board's choice
O3 Remain associated with Firm DBA without pursuing further escalation or reconsideration of the relationship.
Argument structure (Toulmin):
Claim Unless Firm DBA demonstrates continued unwillingness to correct the report, in which case withdrawal becomes warranted.

Engineer M should remain engaged with Firm DBA long enough to pursue correction and escalation, withdrawing only if Firm DBA shows no willingness to change and continued association would attach his name to a dishonest report.

Grounds

Engineer M expressed objections which Firm DBA dismissed, and Firm DBA proceeded to submit the misleading report despite Engineer M's stated concerns.

Warrant

Engineers must not permit their name to be associated with a person or firm they believe is engaged in dishonest enterprise, but escalation duties presuppose continued engagement to attempt correction before withdrawal is warranted.

Backing

NSPE Code II.1.f

Rebuttal

Would not apply, favoring continued engagement, if Engineer M's continued presence created a realistic chance of correcting the report or protecting the public; but if Firm DBA showed no willingness to change and proceeded regardless, withdrawal would be the warranted course.

Firm DBA Principals Ethical Practice Duty Engineer M Dishonest Association Prohibition

Should Firm DBA's licensed engineer principals treat the communications and public relations department's outreach work as governed by the NSPE Code, or as exempt because it is not labeled engineering services?

Options considered:
O1 Hold the communications and public relations department to the same NSPE Code standards as engineering departments because licensed engineers supervise and own it. Board's choice
O2 Treat the communications and public relations department as a separate non-engineering business line outside the scope of the NSPE Code.
O3 Restrict Code compliance requirements to deliverables formally designated as engineering work product, excluding outreach and communications reports.
Argument structure (Toulmin):
Claim Even though the firm's services on this project were confined to communication and public relations rather than design or calculation engineering.

Firm DBA's principals must treat the outreach and public relations work as governed by the NSPE Code because licensed engineers supervise and own the department, and the paramount duty to public welfare applies regardless of internal labeling.

Grounds

Firm DBA's communications and public relations department, staffed under the ownership and supervision of licensed professional engineers, conducted the outreach sessions and produced the report used to justify the highway route decision.

Warrant

The Code applies to all work performed under the supervision and ownership of licensed engineers regardless of whether that work is internally labeled engineering services, because the paramount canon of public welfare governs the firm's conduct as a whole.

Backing

NSPE Code I.1, II.3.a

Rebuttal

Would not apply if the communications and public relations functions were staffed entirely by non-engineers with no supervisory or ownership control by licensed engineers, in which case Code applicability to that department would be less clear.

Firm DBA Code Adherence Duty

Should Engineer M treat the City's directive to schedule outreach sessions disadvantaging Community P as a separate ethical issue requiring direct engagement with the City, or address it only through correcting Firm DBA's report?

Options considered:
O1 Raise the City's scheduling directive as an independent ethical concern to the City, documented separately from the report's deficiencies. Board's choice
O2 Limit corrective action to fixing Firm DBA's report and refrain from separately raising the City's scheduling directive as its own ethical issue.
O3 Mention the City's directive only as background context during discussions with Firm DBA, without separately documenting or escalating it to the City.
Argument structure (Toulmin):
Claim Even though Community P is not Engineer M's direct contractual client.

Engineer M should raise the City's directive as an independent ethical concern with the City, documenting it separately from Firm DBA's report deficiencies, because the directive itself disadvantaged Community P for economic and political reasons.

Grounds

The City explicitly instructed that outreach sessions be scheduled in a manner disadvantaging Community P, resulting in low participation from Community P and unaddressed displacement concerns.

Warrant

Engineers must hold paramount the safety, health, and welfare of the public, which requires confronting a client's own role in directing an inequitable process rather than treating it solely as an internal firm reporting problem.

Backing

NSPE Code I.1, II.3.a

Rebuttal

Would not apply if the City's directive is understood as a legitimate business or political policy choice entirely outside Engineer M's contractual or professional purview, or if no direct causal link to public harm can be established.

Engineer M Escalation to City Duty
Event Timeline (12)
12 sequenced 8 actions 4 events
Case timeline
Engineer M is retained by the City as the lead engineer on the major public infrastructure project to upgrade the highway through Community P.
City leaders, citing economic, political, and social considerations, specifically instruct Firm DBA to perform the public engagement sessions in the manner Firm DBA carried out.
Causal-normative reasoning(confidence 0.70)
The Outreach Method Directive itself is neutral with no fulfill or violate tag, but its normative weight comes from being the causal origin that compels the Firm to enact the scheduling choices that then violate the public safety obligation, showing how an upstream directive can seed a downstream ethical failure.
Firm DBA organizes public engagement sessions at times and locations difficult for Community P residents to attend, in Community Q, with no written comment mechanism and no virtual meetings.
Violates (1)
  • Hold Paramount Public Safety, Health, and Welfare
Causal-normative reasoning(confidence 0.85)
Public Engagement Scheduling violates the paramount safety obligation because its design choices directly produce both Low Community Participation, which silences Displacement Concerns, and Supportive Comments Reception, which together feed the Misleading Report Submission that misrepresents public sentiment on a safety-relevant project.
Few residents of Community P attend the public engagement sessions because the sessions are scheduled at inaccessible times and held in Community Q, far from the affected area.
The few Community P attendees who do participate express concerns that the project could displace residents and disrupt local businesses.
Because the sessions are held in Community Q, an alternate route area, many comments are received favoring routing the upgrade through Community P rather than Community Q, producing a skewed public input record.
Engineer M expresses concern to Firm DBA about the public outreach and the session locations after observing the flawed engagement process.
Fulfills (1)
  • Hold Paramount Public Safety, Health, and Welfare
Causal-normative reasoning(confidence 0.80)
Engineer M's Concern Expression fulfills the paramount safety obligation by surfacing a legitimate risk, but because it triggers the Firm's Concern Dismissal rather than corrective action, the ethical act is immediately undermined by the downstream chain toward a Misleading Report Submission.
Firm DBA rejects Engineer M's concerns, stating the practices are consistent with prior projects for the City and were performed under specific City instruction.
Violates (1)
  • Hold Paramount Public Safety, Health, and Welfare
Causal-normative reasoning(confidence 0.85)
Concern Dismissal violates the paramount public safety obligation precisely because it converts a properly raised safety concern into suppressed information, directly causing the Misleading Report Submission that misinforms decision makers relying on the report's accuracy.
Firm DBA prepares and submits a carefully-framed report that omits where and when sessions were held and that written comments were not accepted, and claims Community P supports the project.
Violates (3)
  • Issue Statements in an Objective and Truthful Manner
  • Avoid Deceptive Acts
  • Not Omit a Material Fact
Causal-normative reasoning(confidence 0.80)
By omitting the community's displacement concerns while highlighting only supportive comments, the Misleading Report Submission violates truthfulness and non-omission duties, and this deception is precisely what later compels Engineer M to raise the matter in an Ethics Conference With Firm, showing how the upstream dismissal of concerns culminated in a report whose dishonesty had direct downstream consequences for professional accountability.
Recommended prospective action in which Engineer M confers immediately with Firm DBA, states objections, and expresses all ethical obligations under the Code, with Firm DBA's supervising licensed engineers involved.
Fulfills (2)
  • Not Associate With Fraudulent or Dishonest Enterprise
  • Advise Clients or Employers When a Project Will Not Be Successful
Causal-normative reasoning(confidence 0.78)
Engineer M's decision to confront the firm rather than silently participate in or ignore the misleading report fulfills the duty to avoid association with dishonest enterprises and to advise when a project will fail, and this action, guided by paramount concern for public welfare and ethical conduct, is what forces the escalation to the client when the firm refuses to correct course.
Prospective action in which Engineer M, if Firm DBA does not correct the discrepancies, confers with the City with the knowledge and potential presence of Firm DBA to discuss the ethical obligations of all involved.
At stake (2)
  • Advise Clients or Employers When a Project Will Not Be Successful
  • Hold Paramount Public Safety, Health, and Welfare
Causal-normative reasoning(confidence 0.75)
Escalation to Client carries no direct fulfill or violate tag yet is guided by the public welfare obligation, and it matters because it is the necessary corrective step after the Firm's refusal at the Ethics Conference, ultimately forcing the Licensure Board Reporting Decision that restores accountability the Firm avoided.
Prospective decision in which Engineer M, if the City decides to do nothing, must decide whether to report Firm DBA's actions to the state's engineering licensure board.
At stake (1)
  • Hold Paramount Public Safety, Health, and Welfare
Causal-normative reasoning(confidence 0.75)
Because the client (City) failed to act after escalation, Engineer M's subsequent decision about whether to report to the licensure board is guided by the paramount duty to protect public safety and welfare, making this action the final safeguard against the harms that began with skewed engagement scheduling and a deceptive report.
Narrative (4 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 M, the lead engineer retained by the City on a major infrastructure project to upgrade a highway system running through Community P, a historically underserved and overburdened neighborhood. Your firm partnered with Firm DBA, whose communications and public relations department, staffed under licensed professional engineers who hold supervisory and ownership roles throughout the firm, was tasked with organizing the required public engagement sessions. Those sessions were scheduled during work hours at venues far from Community P and difficult to reach by public transit, with no virtual option and no method for submitting written comments. Instead, most sessions were held in Community Q, an area that serves as an alternate route for the project. Turnout from Community P was minimal, and the few residents who attended raised concerns about the project's impact on their neighborhood. You are aware of these outreach deficiencies and now face a series of decisions about how to respond to Firm DBA's reporting, its accountability under professional codes, and your own continued role on the project.

Main characters (4)

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 DBA Roles in this case: Consultant EngineerPrincipal Engineers

If Engineer M's conditional licensure status is not disclosed in the firm's report to the city, the report becomes materially incomplete and effectively deceptive about who is qualified to certify the work. Fulfilling the reporting duty could expose M and the firm to licensure board scrutiny, creating pressure to omit the disclosure and thereby violate the deceptive report prohibition.

Attaches to role: Consultant Engineer

Tension between Firm DBA Complete Report Duty and Firm DBA Deceptive Report Prohibition

Attaches to role: Consultant Engineer

Engineer M's duty to advise the city or firm about the likely failure of the project can conflict with the firm principals' institutional duty to practice ethically, if the principals prefer to delay or soften disclosure of the failure to protect the firm's reputation or client relationship. This creates pressure on M to either soften his advisory role or confront the principals directly.

Attaches to role: Principal Engineers

The firm's duty to genuinely incorporate community input, particularly from both Community P and Community Q who may prefer different routes, can conflict with the duty to honestly represent the level of community support in official reports. If input from one community is minimized to present a unified support narrative, the firm risks misrepresenting the actual balance of public opinion.

Attaches to role: Consultant Engineer

Tension between Firm DBA Principals Ethical Practice Duty and Engineer M Dishonest Association Prohibition

Attaches to role: Consultant Engineer
Community P Roles in this case: Affected Public

The firm's duty to genuinely incorporate community input, particularly from both Community P and Community Q who may prefer different routes, can conflict with the duty to honestly represent the level of community support in official reports. If input from one community is minimized to present a unified support narrative, the firm risks misrepresenting the actual balance of public opinion.

Community Q Roles in this case: Alternate Route Public

The firm's duty to genuinely incorporate community input, particularly from both Community P and Community Q who may prefer different routes, can conflict with the duty to honestly represent the level of community support in official reports. If input from one community is minimized to present a unified support narrative, the firm risks misrepresenting the actual balance of public opinion.

Engineer M Roles in this case: Lead EngineerFirm Partner

Tension between Engineer M Escalation to City Duty and Engineer M Dishonest Association Prohibition

Attaches to role: Lead Engineer

If Engineer M's conditional licensure status is not disclosed in the firm's report to the city, the report becomes materially incomplete and effectively deceptive about who is qualified to certify the work. Fulfilling the reporting duty could expose M and the firm to licensure board scrutiny, creating pressure to omit the disclosure and thereby violate the deceptive report prohibition.

Attaches to role: Lead Engineer

Engineer M's duty to advise the city or firm about the likely failure of the project can conflict with the firm principals' institutional duty to practice ethically, if the principals prefer to delay or soften disclosure of the failure to protect the firm's reputation or client relationship. This creates pressure on M to either soften his advisory role or confront the principals directly.

Attaches to role: Lead Engineer

Tension between Firm DBA Principals Ethical Practice Duty and Engineer M Dishonest Association Prohibition

Attaches to role: Lead Engineer

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

Guided by: Honesty in Support Claim, Professional Dignity in Community P Outreach, Complete Reporting in Engagement Report

If Engineer M's conditional licensure status is not disclosed in the firm's report to the city, the report becomes materially incomplete and effectively deceptive about who is qualified to certify the work. Fulfilling the reporting duty could expose M and the firm to licensure board scrutiny, creating pressure to omit the disclosure and thereby violate the deceptive report prohibition.

Engineer M's duty to advise the city or firm about the likely failure of the project can conflict with the firm principals' institutional duty to practice ethically, if the principals prefer to delay or soften disclosure of the failure to protect the firm's reputation or client relationship. This creates pressure on M to either soften his advisory role or confront the principals directly.

The firm's duty to genuinely incorporate community input, particularly from both Community P and Community Q who may prefer different routes, can conflict with the duty to honestly represent the level of community support in official reports. If input from one community is minimized to present a unified support narrative, the firm risks misrepresenting the actual balance of public opinion.

If Engineer M's conditional licensure status is not disclosed in the firm's report to the city, the report becomes materially incomplete and effectively deceptive about who is qualified to certify the work. Fulfilling the reporting duty could expose M and the firm to licensure board scrutiny, creating pressure to omit the disclosure and thereby violate the deceptive report prohibition.

The Board’s deliberation

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

Engineer M should challenge the validity of Firm DBA’s report as Firm DBA did not abide by the Code in a number of instances.
Engineer M should first confer with Firm DBA to correct all discrepancies in the report. If no agreement can be made going forward, Engineer M should confer with the City to outline the ethical obligations. Engineer M should also consider any obligations they may have to report to the state licensure board.
The actions of Firm DBA are not ethical under the Code as the services provided were under the supervision and ownership of licensed professional engineers.
Opening States (8)
Carefully Framed Engagement Report Omissions Code Applicability To Firm DBA Engineer M Awareness Of Outreach Deficiencies Highway Project Failure Risk Engineer M Association With Firm DBA City Directive On Engagement Sessions Community P Displacement Exposure Firm DBA Report Code Violation
Summary
  • An engineer must refuse to lend professional credibility to a report from their own firm if that report is incomplete or deceptive, regardless of internal loyalty pressures.
  • When a firm's collective output conflicts with the honesty and completeness requirements of the Code, individual engineers are still personally accountable for challenging that output.
  • Escalating concerns to an external authority like a city can be ethically required even when it creates tension with maintaining a cooperative relationship within one's own firm.

© Licensed under the GNU GPL v3