Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (9)
View Extraction-
Engineer M Safety Obligation Public Welfare Highway Upgrade Community P
This provision directly mandates holding paramount public safety and welfare, which is the core of Engineer M's obligation to protect Community P.
-
Scheduling Sessions Inaccessibly
Inaccessible scheduling undermines public welfare by excluding community members from infrastructure decisions affecting them.
-
Excluding Written and Virtual Participation
Excluding participation modes harms public welfare by denying community members meaningful input on infrastructure projects.
-
Engineer M Raises Concerns
Engineer M acts to hold public welfare paramount by flagging exclusionary engagement practices.
-
Engineer M Escalates to City
Escalating to the city is a direct action to protect public welfare by ensuring proper community engagement.
-
Public Safety and Welfare at Risk from Misrepresented Community Input
Engineer M must hold paramount the welfare of Community P residents whose safety is jeopardized by project decisions based on misrepresented input.
-
Engineer M Competing Duties Between Client Authority and Public Welfare
This provision directly frames Engineer M's obligation to prioritize public welfare over client directives.
-
Public Safety at Risk. Project Proceeding on Fraudulent Basis
Proceeding with the project on a fraudulent engagement basis directly threatens public safety and welfare, which engineers must hold paramount.
-
Historically Underserved Community Impact. Community P Project
Community P as the primary affected community represents the public whose safety and welfare Engineer M is obligated to protect.
-
Engineer M Ethical Dilemma Regarding Report Endorsement
Engineer M's decision on whether to endorse the report is governed by the paramount duty to protect public welfare.
-
Public Safety Paramount. Community P Project Proceeding on Fraudulent Basis
I.1 directly creates the obligation to hold public safety paramount that constrains Engineer M from allowing the project to proceed on a fraudulent basis.
-
Engineer M Public Safety Paramount. Community P Highway Upgrade
I.1 is the foundational provision requiring Engineer M to hold public safety, health, and welfare paramount throughout the project.
-
Environmental Justice Community Protection. Community P Highway Project
I.1 underpins the obligation to protect Community P as a vulnerable population whose safety and welfare must be held paramount.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M as lead engineer must hold paramount the safety, health, and welfare of the public, including ensuring Community P is not excluded from the engagement process.
-
Firm DBA Public Outreach Engineering Consultant
Firm DBA's conduct in holding inaccessible sessions that excluded an overburdened community directly undermines the welfare of the public.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PEs at Firm DBA bear responsibility for ensuring their firm's work upholds public welfare, including equitable community engagement.
-
Community P Participation Failure
Failing to engage the community undermines public welfare by excluding those affected by the infrastructure project.
-
Displacement Concerns Raised
Displacement directly threatens the safety, health, and welfare of the public, which engineers must hold paramount.
-
Concerns Formally Dismissed
Dismissing legitimate public welfare concerns without proper consideration violates the duty to hold public welfare paramount.
-
NSPE-Code-of-Ethics
This provision is the foundational public welfare obligation within the NSPE Code that governs Engineer M's conduct.
-
NSPE Code of Ethics - Primary Authority
This provision is directly applied as primary authority to assess whether Engineer M upheld the paramount duty to public safety and welfare.
-
Environmental-Justice-Executive-Order-12898
This provision requires protecting public welfare, and the Executive Order grounds the obligation to protect the historically underserved Community P from infrastructure harm.
-
Public-Engagement-Standard-Infrastructure
Holding public welfare paramount requires meeting minimum inclusive engagement standards so affected communities can participate in infrastructure decisions.
-
Qualitative-Risk-Assessment-Community-Impact
Assessing likelihood and magnitude of harm to residents directly supports the obligation to hold public safety and welfare paramount.
-
NSPE-Position-Statement-Public-Welfare
NSPE position statements on the primacy of public welfare provide authoritative interpretive guidance for applying this provision.
-
BER Case 88-6
This precedent establishes that an engineer who fails to act after being silenced on a public safety risk violates the duty to hold public welfare paramount.
-
BER-Community-Engagement-Precedents
Prior BER cases addressing conflicts between client instructions and public welfare directly inform application of this paramount duty provision.
-
Engineer M Public Welfare Paramountcy Recognition
This provision directly requires holding public welfare paramount, which is the core capability Engineer M demonstrated in identifying the exclusionary process.
-
Engineer M Public Welfare Paramountcy Highway Upgrade Community P
This provision requires paramountcy of public welfare, directly matching Engineer M's capability to recognize this obligation for Community P.
-
Engineer M Environmental Justice Awareness
Holding paramount the welfare of the public includes recognizing environmental justice concerns for historically underserved communities.
-
Firm DBA Equitable Public Engagement Design Failure
Failing to design equitable engagement directly undermines the public welfare of Community P residents affected by the infrastructure project.
-
Firm DBA Licensed PE Supervisors Equitable Engagement Oversight
Licensed PE supervisors bear responsibility under this provision to ensure public welfare is held paramount through equitable engagement oversight.
-
Engineer M Equitable Public Engagement Design
Recognizing inaccessible session logistics as harmful to Community P connects directly to the obligation to hold public welfare paramount.
-
Engineer M Stakeholder Interest Balancing
Balancing stakeholder interests while prioritizing public welfare is a direct application of this provision.
-
Firm DBA Public Engagement Report Completeness Accuracy Highway Upgrade
This provision requires objective and truthful public statements, directly applying to Firm DBA's duty to issue an accurate public engagement report.
-
Engineer M Subcontractor Ethical Compliance Oversight Firm DBA
This provision requires truthful public statements, supporting Engineer M's obligation to object to the materially false report issued by Firm DBA.
-
Producing Misleading Outreach Report
Issuing a misleading report violates the requirement to make public statements only in an objective and truthful manner.
-
Firm DBA Misrepresentative Public Engagement Report
Firm DBA's report contains misrepresentations, violating the requirement to issue public statements only in an objective and truthful manner.
-
Misrepresentative Public Record. Firm DBA Report
The official public engagement report is a public statement that fails the standard of objectivity and truthfulness.
-
Engineer M Ethical Dilemma Regarding Report Endorsement
Engineer M endorsing or allowing the misrepresentative report to stand would violate the duty to ensure public statements are truthful.
-
Inequitable Public Engagement. Community P Sessions
The inequitable sessions produced a misleading public record, violating the obligation for truthful public statements.
-
Firm DBA Non-Deception Constraint. Public Engagement Report
I.3 requires objective and truthful public statements, directly creating the constraint against Firm DBA issuing non-objective or untruthful engagement reports.
-
Fact-Grounded Opinion. Firm DBA Community P Support Claim
I.3 requires truthfulness in public statements, constraining Firm DBA from claiming community support without a truthful factual basis.
-
Firm DBA Written Report Completeness. Public Engagement Sessions Material Facts
I.3 requires objective and truthful public statements, which constrains Firm DBA to include all material facts in its public engagement report.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must ensure that public statements and reports related to the project are objective and truthful.
-
Firm DBA Public Outreach Engineering Consultant
Firm DBA issued public engagement reports that were not objective or truthful, violating this provision.
-
Firm DBA Public Relations Subcontractor
Firm DBA in its public relations role issued statements falsely claiming community support, violating the requirement for truthful public statements.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors and owners at Firm DBA are responsible for ensuring all public statements issued by the firm are objective and truthful.
-
Misleading Report Enters Record
Issuing a misleading report violates the requirement to make public statements only in an objective and truthful manner.
-
Project Record Integrity Compromised
A compromised project record reflects a failure to issue objective and truthful public documentation.
-
NSPE-Code-of-Ethics
This provision requiring objective and truthful public statements is a core obligation within the NSPE Code governing Engineer M.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to evaluate whether public statements made by Firm DBA and Engineer M were truthful and objective.
-
BER Case 98-2
This precedent establishes universal application of the NSPE Code including truthful public statement obligations regardless of context.
-
BER Case 21-7
This precedent establishes the obligation to include all relevant information in reports, directly supporting the requirement for objective and truthful public statements.
-
Certified Public Relations Professional Code of Ethics
This parallel code binding Firm DBA's PR professionals to honest conduct reinforces the truthful public statement obligation.
-
Firm DBA Public Engagement Report Accuracy Failure
This provision requires truthful public statements, which Firm DBA violated by producing a report with material omissions and false implications.
-
Firm DBA Public Engagement Report Completeness Accuracy Obligation Individual
This provision directly requires objective and truthful public statements, matching the completeness and accuracy obligation for the engagement report.
-
Firm DBA Licensed PE Supervisors Report Accuracy Oversight
Licensed PE supervisors are responsible under this provision for ensuring public statements issued by their firm are objective and truthful.
-
Engineer M Material Omission Recognition Public Engagement Report
Recognizing material omissions in a public report directly relates to the requirement that public statements be objective and truthful.
-
Engineer M False Community Consent Recognition
Identifying that the report falsely implied community support connects to the requirement to issue public statements only in a truthful manner.
-
Firm DBA Public Engagement Report Completeness Accuracy Highway Upgrade
This provision prohibits deceptive acts, directly applying to Firm DBA's obligation to avoid producing a false or misleading public engagement report.
-
City Municipal Infrastructure Client Non-Direction Fraudulent Report
This provision prohibits deceptive acts, applying to the City's obligation to refrain from directing or accepting a fraudulent engagement report.
-
Scheduling Sessions Inaccessibly
Deliberately scheduling sessions inaccessibly constitutes a deceptive act by creating the appearance of engagement without genuine access.
-
Excluding Written and Virtual Participation
Excluding participation modes deceptively limits engagement while maintaining a facade of public outreach.
-
Producing Misleading Outreach Report
Producing a misleading report is a direct deceptive act misrepresenting the extent and quality of community engagement.
-
Firm DBA Dismisses Concerns
Dismissing legitimate concerns to continue deceptive practices constitutes avoidance of correcting a deceptive act.
-
Firm DBA Misrepresentative Public Engagement Report
Submitting a report that misrepresents the public engagement process constitutes a deceptive act.
-
City Client-Directed Procedural Manipulation of Engagement
The City's instruction to manipulate the engagement process is a deceptive act that engineers must avoid facilitating.
-
Firm DBA Inequitable Public Engagement Sessions
Conducting inequitable sessions designed to suppress community input is a deceptive act.
-
Engineer M Ethical Dilemma Regarding Report Endorsement
Engineer M endorsing the misrepresentative report would make them complicit in a deceptive act.
-
Client-Directed Procedural Manipulation. City Direction to Firm DBA
The City's direction to manipulate engagement procedures is itself a deceptive act that engineers must not participate in.
-
Misrepresentative Public Record. Firm DBA Report
The falsified public record constitutes a deceptive act that engineers are obligated to avoid.
-
Non-Deception. Firm DBA Public Engagement Report Submission
I.5 directly creates the non-deception obligation that constrains Firm DBA from submitting a report that creates a false impression of community support.
-
Firm DBA Non-Deception Constraint. Public Engagement Report
I.5 is the direct source of the non-deception constraint prohibiting Firm DBA from engaging in deceptive acts in its public engagement reporting.
-
Incomplete Risk Disclosure. Firm DBA Omission of Engagement Conditions
I.5 prohibits deceptive acts, which includes omitting material facts about engagement conditions that would create a false impression.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must avoid deceptive acts, including allowing a flawed engagement process to proceed without correction.
-
Firm DBA Public Outreach Engineering Consultant
Firm DBA engaged in deceptive acts by organizing sessions in inaccessible locations and misrepresenting community participation.
-
Firm DBA Public Relations Subcontractor
Firm DBA as public relations subcontractor engaged in deceptive acts by falsely claiming community support in its report.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors and owners at Firm DBA are responsible for preventing deceptive acts carried out under their supervision.
-
City Municipal Infrastructure Client
City leaders allegedly directed Firm DBA in ways that contributed to deceptive engagement practices, implicating this provision.
-
Misleading Report Enters Record
Allowing a misleading report to enter the record constitutes a deceptive act that engineers must avoid.
-
Concerns Formally Dismissed
Formally dismissing concerns through deceptive or bad-faith processes constitutes a deceptive act.
-
Project Record Integrity Compromised
Compromising the integrity of the project record through omission or misrepresentation is a deceptive act.
-
NSPE-Code-of-Ethics
The prohibition on deceptive acts is a core provision of the NSPE Code directly governing Engineer M's conduct.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to determine whether Firm DBA's engagement practices constituted deceptive acts.
-
Public-Engagement-Standard-Infrastructure
Deceptive engagement practices such as inaccessible meeting times violate minimum inclusive engagement standards and constitute deceptive acts under this provision.
-
Certified Public Relations Professional Code of Ethics
This parallel professional code reinforces the prohibition on deception by binding PR professionals at Firm DBA to honest conduct.
-
BER-Community-Engagement-Precedents
Prior BER cases on honest reporting and public welfare provide precedent for identifying deceptive community engagement practices.
-
Firm DBA Public Engagement Report Accuracy Failure
Producing a carefully-framed report that omits material facts constitutes a deceptive act that this provision requires engineers to avoid.
-
Firm DBA Equitable Public Engagement Design Failure
Organizing inaccessible sessions and then reporting implied community support is a deceptive act prohibited by this provision.
-
Engineer M False Community Consent Recognition
Recognizing false implied community consent is directly tied to identifying and avoiding the deceptive act prohibited by this provision.
-
Firm DBA Procurement Rationalization Resistance Failure
Accepting insufficient justifications to rationalize a flawed process that produces deceptive outputs violates the requirement to avoid deceptive acts.
-
Firm DBA Institutional Pressure Resistance Failure
Acquiescing to directives that result in a deceptive engagement report constitutes a failure to avoid deceptive acts as required by this provision.
-
Engineer M Non-Association Fraudulent Enterprise Recognition
Recognizing that Firm DBA's report constitutes a deceptive act is directly linked to the obligation to avoid such acts under this provision.
-
Engineer M Non-Association Fraudulent Enterprise Firm DBA
This provision directly prohibits permitting use of one's name or associating with a fraudulent enterprise, which is exactly the obligation described for Engineer M regarding Firm DBA.
-
City Engages Firm DBA
If Firm DBA is engaged in fraudulent outreach practices, the city associating with them implicates this provision.
-
Engineer M Confronts Firm DBA Formally
Engineer M formally confronting Firm DBA reflects concern about being associated with a potentially dishonest enterprise.
-
Engineer M Professional Disassociation Decision
Engineer M must consider disassociating from the project if Firm DBA is engaged in fraudulent or dishonest enterprise.
-
Firm DBA Fraudulent Public Engagement Report
Firm DBA's fraudulent report represents the dishonest enterprise from which Engineer M must not permit association with their name.
-
Subconsultant Ethical Non-Compliance. Firm DBA
Firm DBA's conduct in producing a deficient and dishonest report triggers Engineer M's obligation to disassociate.
-
Engineer M Subconsultant Ethical Non-Compliance with Firm DBA
Engineer M's professional relationship with Firm DBA must be severed if Firm DBA is engaged in fraudulent enterprise.
-
Firm DBA Code Applicability Contested
Regardless of whether Firm DBA is directly bound by the Code, Engineer M cannot permit their name to be associated with Firm DBA's fraudulent conduct.
-
Engineer M Non-Association Fraudulent Enterprise. Firm DBA Project
II.1.d directly creates the constraint prohibiting Engineer M from permitting use of their name or continuing association with a project they believe involves fraudulent conduct.
-
Professional Disassociation. Engineer M Continued Association with Fraudulent Project
II.1.d is the provision that constrains Engineer M from continuing to associate with the project if Firm DBA is engaged in fraudulent or dishonest enterprise.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must not permit association with Firm DBA if Engineer M believes Firm DBA is engaged in fraudulent or dishonest enterprise.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PEs at Firm DBA must not associate with or permit dishonest enterprise within their own firm.
-
Misleading Report Enters Record
Permitting ones name on a fraudulent or dishonest report associates the engineer with a dishonest enterprise.
-
Project Record Integrity Compromised
Allowing association with a project whose record has been dishonestly compromised violates this provision.
-
NSPE-Code-of-Ethics
This provision prohibiting association with fraudulent enterprises is part of the NSPE Code directly governing Engineer M's professional associations.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to assess whether Engineer M's continued association with Firm DBA constitutes permitted conduct.
-
BER Case 60-3
This precedent regarding whether firms providing sub-professional services must abide by the Canons is directly relevant to determining Engineer M's association obligations.
-
BER Case 98-2
This precedent establishing universal NSPE Code applicability supports applying this provision to Engineer M regardless of Firm DBA's own professional status.
-
Engineer M Non-Association Fraudulent Enterprise Recognition
This provision directly requires engineers not to associate with firms engaged in fraudulent enterprise, matching Engineer M's capability to recognize Firm DBA's conduct as such.
-
Engineer M Subcontractor Ethical Oversight
Exercising oversight over a subcontractor engaged in potentially fraudulent reporting is directly required by this provision.
-
Engineer M Code Universality Application Highway Upgrade
Recognizing that the NSPE Code applies to Firm DBA's conduct is necessary to assess whether association with a fraudulent enterprise is occurring.
-
Engineer M Licensure Board Reporting Firm DBA After City Inaction
This provision requires reporting alleged code violations to professional bodies and authorities, directly grounding Engineer M's obligation to report to the licensure board after City inaction.
-
Engineer M Graduated Escalation City After Firm DBA Non-Compliance
This provision requires cooperating with proper authorities, supporting Engineer M's obligation to escalate the matter to the City if Firm DBA refuses to correct discrepancies.
-
Engineer M Escalates to City
Escalating to the city is the act of reporting an alleged code violation to the appropriate authority as required.
-
Engineer M Confronts Firm DBA Formally
Formally confronting Firm DBA is a step toward reporting and addressing the alleged unethical conduct.
-
Internal Escalation Exhausted. Engineer M Post-City Meeting
Once internal escalation fails, Engineer M is obligated to report the violations to appropriate professional bodies and public authorities.
-
Engineer M Competing Duties Between Client Authority and Public Welfare
Engineer M's duty to report violations to proper authorities is a direct professional obligation that competes with client loyalty.
-
Subconsultant Ethical Non-Compliance. Firm DBA
Engineer M having knowledge of Firm DBA's ethical violations must report them to appropriate professional bodies.
-
Firm DBA Fraudulent Public Engagement Report
Knowledge of the fraudulent report obligates Engineer M to report the alleged violation to proper authorities.
-
Engineer M Professional Disassociation Decision
Engineer M's reporting obligation to authorities is a key consideration in deciding how to proceed after disassociation.
-
Engineer M Unlicensed Practice Reporting. Firm DBA Licensure Board
II.1.f requires engineers with knowledge of code violations to report to appropriate professional bodies, directly creating the constraint for Engineer M to report to the licensure board.
-
Engineer M Graduated Escalation Sequence. Firm DBA to City to Licensure Board
II.1.f creates the obligation to report violations to appropriate professional bodies and cooperate with authorities, underpinning the graduated escalation sequence.
-
Internal Compliance Reporting Escalation. Engineer M Post-Firm DBA Non-Response
II.1.f requires reporting known violations to appropriate bodies, constraining Engineer M to escalate after Firm DBA fails to respond.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M, having knowledge of Firm DBA's alleged violations, is obligated to report them to appropriate professional bodies and public authorities.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors at Firm DBA who become aware of ethical violations within the firm are obligated to report them to proper authorities.
-
State Engineering Licensure Board
The state engineering licensure board is identified as the appropriate authority to receive reports of ethical violations from Engineer M regarding Firm DBA.
-
Misleading Report Enters Record
Engineers aware of a misleading report entering the record are obligated to report this violation to appropriate bodies.
-
Project Record Integrity Compromised
Knowledge of a compromised project record requires engineers to report the violation to proper authorities.
-
NSPE-Code-of-Ethics
This provision requiring reporting of Code violations to appropriate bodies is a core obligation within the NSPE Code governing Engineer M.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to determine Engineer M's obligation to report Firm DBA's alleged violations.
-
BER Case 88-6
This precedent establishes that an engineer silenced by a supervisor must take further action, directly supporting the reporting obligation under this provision.
-
BER Case 09-10
This precedent establishes that discovering potential ethical violations by another firm creates an obligation to report, directly applying this provision.
-
BER-Community-Engagement-Precedents
Prior BER cases on engineer obligations when client instructions conflict with public welfare inform when and how the reporting obligation is triggered.
-
Engineer M Internal Compliance Reporting
This provision requires reporting alleged violations to appropriate bodies, directly matching the capability to formally document and report Firm DBA's conduct to the City.
-
Engineer M Licensure Board Self-Reporting Assessment
This provision requires reporting to professional bodies and public authorities, directly matching the capability to assess whether licensure board reporting is required.
-
Engineer M Licensure Board Reporting Assessment Firm DBA
This provision requires engineers to report alleged violations to proper authorities, directly matching the capability to assess reporting obligations after City inaction.
-
Engineer M Graduated Escalation Navigation
Navigating escalation after Firm DBA dismissed concerns is required by this provision's mandate to report violations to appropriate authorities.
-
Engineer M Graduated Escalation City After Firm DBA Non-Compliance
This provision requires cooperation with proper authorities, directly matching the capability to escalate to the City after Firm DBA refused to correct discrepancies.
-
Firm DBA Public Engagement Report Completeness Accuracy Highway Upgrade
This provision requires objective, truthful, and complete professional reports, directly applying to Firm DBA's obligation to ensure the public engagement report includes all material facts.
-
Engineer M Subcontractor Ethical Compliance Oversight Firm DBA
This provision requires complete and truthful reporting, supporting Engineer M's obligation to object to the materially false and incomplete report produced by Firm DBA.
-
Producing Misleading Outreach Report
The misleading report directly violates the requirement for objective, truthful professional reports that include all relevant information.
-
Engineer M Raises Concerns
Engineer M raising concerns reflects the obligation to ensure professional reports and statements are truthful and complete.
-
Firm DBA Misrepresentative Public Engagement Report
The report fails the standard of objectivity and truthfulness and omits material facts about the inequitable engagement process.
-
Misrepresentative Public Record. Firm DBA Report
The official report omits material facts about the deficient engagement sessions, violating the requirement for complete and truthful professional reports.
-
Engineer M Ethical Dilemma Regarding Report Endorsement
Engineer M endorsing the report would violate the obligation to ensure professional reports are objective, truthful, and include all relevant information.
-
Inequitable Public Engagement. Community P Sessions
The sessions produced a report that omits material facts about the inequitable process, violating standards for professional reporting.
-
Written Report Completeness. Firm DBA Public Engagement Report
II.3.a directly requires inclusion of all relevant and pertinent information in reports, creating the constraint on Firm DBA to produce a complete public engagement report.
-
Firm DBA Written Report Completeness. Public Engagement Sessions Material Facts
II.3.a is the direct source of the requirement to include all relevant and pertinent factual information in professional reports such as the public engagement report.
-
Firm DBA Non-Deception Constraint. Public Engagement Report
II.3.a requires objective and truthful professional reports with all pertinent information, directly constraining Firm DBA's reporting conduct.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must ensure that professional reports associated with the project are objective, truthful, and include all relevant information.
-
Firm DBA Public Outreach Engineering Consultant
Firm DBA produced a professional report that omitted material facts and misrepresented community engagement outcomes, violating this provision.
-
Firm DBA Public Relations Subcontractor
Firm DBA in its subcontractor role submitted a report omitting material facts about session accessibility and falsely claiming community support.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors and owners at Firm DBA are ultimately responsible for ensuring the firm's professional reports are objective and complete.
-
Misleading Report Enters Record
A misleading report directly violates the requirement for objective, truthful, and complete professional reports.
-
Concerns Formally Dismissed
Formally dismissing concerns without including all relevant information in the record violates the duty of complete and truthful reporting.
-
Project Record Integrity Compromised
A compromised project record fails the standard of objective and complete professional documentation.
-
NSPE-Code-of-Ethics
This provision requiring objective and truthful professional reports with all relevant information is a core NSPE Code obligation governing Engineer M.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to evaluate whether Engineer M's professional reports and statements met the standard of objectivity and completeness.
-
BER Case 21-7
This precedent directly establishes that a registered professional engineer must include all relevant and pertinent information in a report, mirroring this provision's requirements.
-
Qualitative-Risk-Assessment-Community-Impact
A structured risk assessment methodology provides the relevant and pertinent information that must be included in professional reports under this provision.
-
Environmental-Justice-Executive-Order-12898
Information grounded in this Executive Order regarding impacts on underserved communities constitutes relevant and pertinent information that must appear in professional reports.
-
Firm DBA Public Engagement Report Accuracy Failure
This provision requires objective and complete professional reports, which Firm DBA violated by omitting material facts from the engagement report.
-
Firm DBA Public Engagement Report Completeness Accuracy Obligation Individual
This provision directly mandates complete and accurate professional reports, matching the completeness and accuracy obligation for Firm DBA's engagement report.
-
Firm DBA Licensed PE Supervisors Report Accuracy Oversight
This provision places responsibility on engineers for report accuracy, matching the oversight obligation of Firm DBA's licensed PE supervisors.
-
Engineer M Material Omission Recognition Public Engagement Report
Identifying material omissions in the report directly relates to this provision's requirement to include all relevant and pertinent information.
-
Engineer M False Community Consent Recognition
Recognizing that the report falsely implied community consent connects to this provision's requirement for objective and truthful professional reports.
-
Engineer M Project Success Notification City Highway Upgrade
This provision directly requires engineers to advise clients when a project will not be successful, which is exactly Engineer M's obligation to notify the City about the project's likely failure.
-
Engineer M Raises Concerns
Engineer M advises that the flawed engagement approach will not achieve a successful or legitimate community outreach outcome.
-
Firm DBA Dismisses Concerns
Firm DBA dismissing concerns violates the obligation to heed advice that the project approach will not be successful.
-
Engineer M Competing Duties Between Client Authority and Public Welfare
Engineer M is obligated to advise the City client that the project will not be successful if based on a fraudulent engagement process.
-
Engineer M Ethical Dilemma Regarding Report Endorsement
Before deciding on report endorsement, Engineer M should advise the client that proceeding on this basis will not lead to a successful project.
-
City Client-Directed Procedural Manipulation of Engagement
Engineer M must advise the City that its direction to manipulate engagement will undermine the project's legitimacy and success.
-
Public Safety at Risk. Project Proceeding on Fraudulent Basis
Engineer M must warn the client that proceeding on a fraudulent basis risks project failure and public harm.
-
Engineer M Project Success Adverse Notification. City Highway Upgrade
III.1.b directly creates the obligation for Engineer M to advise the City that the project will not be successful if it proceeds on the basis of false public engagement.
-
Client-Directed Ethical Violation Non-Compliance. City Instructions to Firm DBA
III.1.b requires advising clients when a project will not be successful, constraining Engineer M and Firm DBA from simply complying with City instructions that undermine project integrity.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M expressed concern to Firm DBA about inaccessible sessions and must advise the client if the engagement process will not be successful or valid.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors at Firm DBA should advise their client Engineer M when the engagement process as directed is unlikely to be successful or legitimate.
-
Displacement Concerns Raised
Engineers should advise clients when displacement concerns indicate the project may not succeed or may cause serious harm.
-
Concerns Formally Dismissed
Engineers are obligated to advise clients of project risks rather than allowing legitimate concerns to be dismissed without action.
-
NSPE-Code-of-Ethics
This provision requiring engineers to advise clients when a project will not be successful is part of the NSPE Code governing Engineer M's advisory obligations.
-
NSPE Code of Ethics - Primary Authority
This provision is applied as primary authority to assess whether Engineer M fulfilled the duty to advise Firm DBA about the inadequacy of the engagement process.
-
Public-Engagement-Standard-Infrastructure
Minimum engagement standards provide the benchmark against which Engineer M should advise Firm DBA that the project engagement process will not be successful.
-
BER-Community-Engagement-Precedents
Prior BER cases on conflicts between client instructions and public welfare inform the scope of the advisory obligation under this provision.
-
Engineer M Project Non-Success Advisory City Highway Upgrade
This provision directly requires advising clients when a project will not be successful, matching Engineer M's capability to recognize and advise the City accordingly.
-
Engineer M Internal Compliance Reporting
Formally communicating to the City that the project cannot succeed on the basis of a false engagement report is required by this provision.
-
Engineer M Stakeholder Interest Balancing
Advising the City of project non-success requires balancing client interests against the obligation to provide honest professional advice under this provision.
-
Firm DBA Public Engagement Report Completeness Accuracy Highway Upgrade
This provision prohibits statements with material misrepresentations or omissions, directly applying to Firm DBA's obligation to produce an accurate and complete public engagement report.
-
Engineer M Subcontractor Ethical Compliance Oversight Firm DBA
This provision prohibits material misrepresentations, supporting Engineer M's obligation to object to the false and incomplete report and demand corrections from Firm DBA.
-
Producing Misleading Outreach Report
The misleading report contains material misrepresentations and omits material facts about the actual scope of community engagement.
-
Scheduling Sessions Inaccessibly
Scheduling sessions inaccessibly while reporting broad engagement omits the material fact of limited public access.
-
Excluding Written and Virtual Participation
Excluding participation modes while claiming comprehensive outreach omits a material fact about engagement limitations.
-
Incomplete Risk Disclosure. Firm DBA Omission of Engagement Conditions
III.3.a prohibits omitting material facts, directly creating the constraint against Firm DBA omitting conditions under which engagement was conducted.
-
Fact-Grounded Opinion. Firm DBA Community P Support Claim
III.3.a prohibits material misrepresentation of fact, constraining Firm DBA from claiming community support without factual grounding.
-
Non-Deception. Firm DBA Public Engagement Report Submission
III.3.a prohibits statements omitting material facts, directly constraining Firm DBA from submitting a report that omits material engagement conditions.
-
Firm DBA Non-Deception Constraint. Public Engagement Report
III.3.a is a direct source of the constraint prohibiting Firm DBA from misrepresenting or omitting material facts in its public engagement report.
-
Written Report Completeness. Firm DBA Public Engagement Report
III.3.a prohibits omitting material facts in statements, reinforcing the constraint that Firm DBA must include all relevant information in its report.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must avoid statements that misrepresent or omit material facts related to the public engagement process and project outcomes.
-
Firm DBA Public Outreach Engineering Consultant
Firm DBA's report contained material misrepresentations and omitted material facts about session locations, times, and comment restrictions.
-
Firm DBA Public Relations Subcontractor
Firm DBA as public relations subcontractor issued statements omitting material facts and falsely claiming community support, directly violating this provision.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors and owners at Firm DBA are responsible for ensuring the firm's statements do not contain material misrepresentations or omissions.
-
Misleading Report Enters Record
A misleading report contains material misrepresentations or omits material facts in violation of this provision.
-
Concerns Formally Dismissed
Formally dismissing concerns while omitting material facts from the record constitutes a material omission.
-
Project Record Integrity Compromised
A compromised project record reflects the use of statements with material misrepresentations or omissions.
-
Engineer M Licensure Board Reporting Firm DBA After City Inaction
This provision requires presenting information about unethical practice to proper authorities, directly supporting Engineer M's obligation to report Firm DBA to the licensure board.
-
Engineer M Graduated Escalation City After Firm DBA Non-Compliance
This provision directs engineers to present evidence of unethical practice to proper authorities, supporting Engineer M's escalation obligation to the City after Firm DBA's non-compliance.
-
Engineer M Escalates to City
Escalating to the city aligns with presenting information about unethical practice to the proper authority rather than making false personal attacks.
-
Engineer M Confronts Firm DBA Formally
Formally confronting Firm DBA follows the proper channel of addressing unethical conduct directly before escalating to authorities.
-
Engineer M Lead Infrastructure Project Engineer
Engineer M must not act to injure Firm DBA's reputation falsely, but must present evidence of unethical practice to the proper authority if warranted.
-
Firm DBA Licensed PE Supervisors and Owners
Licensed PE supervisors at Firm DBA must not act to injure other engineers and must report unethical conduct within their firm to proper authorities.
-
State Engineering Licensure Board
The state engineering licensure board is the proper authority to which information about unethical practice by Firm DBA should be presented for action.
Cross-Case Connections
View ExtractionExplicit 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:
When an engineering firm provides sub-professional services, the Canons of Ethics and Rules of Professional Conduct do not necessarily apply to those services.
Citation Context:
The Board cited this case to show a prior ruling where the Canons and Rules did not apply to an engineering firm providing sub-professional services, then distinguished it by noting the Code has since been revised and that Firm DBA has licensed PEs in supervisory and ownership roles.
Principle Established:
A registered professional engineer is obliged to include relevant and pertinent information in reports; a report lacking such information fails to help stakeholders make informed decisions and does not protect public safety, health, and welfare.
Citation Context:
The Board cited this case to support the principle that a registered professional engineer is obligated to include all relevant and pertinent information in a report, and that omitting such information prevents stakeholders from making informed decisions and fails to protect public safety, health, and welfare.
Principle Established:
When an engineer learns of a potential ethical or licensure violation by another engineer or firm, the engineer should first seek clarification from the party in question and, if not satisfied, may be required to report the matter to the state engineering licensure board.
Citation Context:
The Board cited this case to support the principle that when an engineer becomes aware of potential ethical or licensure violations by another firm, the engineer has an obligation to communicate with that firm and, if unsatisfied, may need to report the matter to the state engineering licensure board.
Principle Established:
The NSPE Code of Ethics applies universally to all 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.
Citation Context:
The Board cited this case to support the principle that the NSPE Code applies universally to all members regardless of circumstance, analogizing that just as geography does not exempt members from the Code, the type of services provided should not either.
Principle Established:
An engineer who is aware of a safety or public welfare concern and takes no further action after being directed to stay silent fails to fulfill the ethical obligation to hold paramount the safety, health, and welfare of the public.
Citation Context:
The Board cited this case to establish that engineers have a duty to hold paramount the safety, health, and welfare of the public, and that failing to act when aware of a problem violates that duty, analogizing Engineer M's obligations to those of Engineer A.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (4 board)
View ExtractionShould Engineer M challenge the validity of Firm DBA’s report?
Implicit (4)
Does the City's explicit instruction to Firm DBA to conduct public engagement sessions in an inequitable manner implicate the City itself in an ethical violation, and does Engineer M have an obligation to refuse City directives that foreseeably harm a historically underserved community?
At what point does Engineer M's continued association with the project - after raising concerns that were dismissed by both Firm DBA and potentially the City - constitute complicity in the fraudulent public engagement record, and should Engineer M consider disassociation before exhausting all escalation pathways?
Does the routing of a major public infrastructure project through Community P - a historically underserved, underrepresented, and overburdened neighborhood - based on a fraudulent public engagement report constitute a public safety and welfare harm that triggers Engineer M's paramount obligation to the public independent of client or subconsultant relationships?
Is the Firm DBA communications and public relations department operating within an appropriate scope of engineering practice when it designs and executes public engagement processes for infrastructure projects affecting community welfare, and does the licensed PE supervisory structure within Firm DBA fully satisfy the ethical obligations that attach to that work?
Should Engineer M raise any concerns with the City, as the client, and, if so, how?
Principle tension (4)
How should Engineer M balance the obligation to hold paramount the safety, health, and welfare of the public - including Community P - against the duty to serve the client faithfully when the City itself has directed the conduct that produced the fraudulent engagement record?
Does the principle requiring engineers to report known Code violations to appropriate authorities conflict with the principle of resolving disputes at the lowest possible level first, and how should Engineer M sequence these obligations when both Firm DBA and the City may be implicated in the same ethical violation?
Does the obligation to avoid injuring the professional reputation of another engineer conflict with the obligation to issue truthful public statements and challenge a materially misrepresentative report, and how should Engineer M navigate this tension when formally contesting Firm DBA's public engagement report?
When the City cites economic, political, and social considerations to justify directing inequitable public engagement, how should Engineer M weigh the principle of serving the legitimate interests of clients against the principle of protecting the welfare of a historically underserved community whose input was systematically suppressed?
Are Firm DBA’s actions ethical?
Theoretical (6)
From a deontological perspective, did Engineer M fulfill their categorical duty to hold paramount the safety, health, and welfare of the public by raising concerns only to Firm DBA rather than immediately escalating to the City when the misleading report was submitted?
From a deontological perspective, does the City's explicit instruction to Firm DBA to conduct inequitable public engagement sessions relieve Firm DBA's licensed professional engineers of their independent duty not to deceive, or does the Code impose an unconditional obligation that cannot be delegated away by client direction?
From a consequentialist perspective, does the harm imposed on Community P - a historically underserved, underrepresented, and overburdened neighborhood - by routing a major highway upgrade based on fraudulent public engagement data outweigh any economic, political, or social benefits the City cited as justification for directing the inequitable engagement process?
From a virtue ethics perspective, did Firm DBA's licensed professional engineers demonstrate the professional integrity and moral courage expected of engineers when they rationalized the inequitable engagement sessions as consistent with prior City projects rather than independently evaluating whether those practices met the standard of honest and objective professional conduct?
From a virtue ethics perspective, did Engineer M demonstrate sufficient professional courage and integrity by expressing concern to Firm DBA but continuing to associate with the project after Firm DBA dismissed those concerns and submitted a misleading report, or did continued association compromise Engineer M's character as a trustworthy steward of the public welfare?
From a consequentialist perspective, would Engineer M's reporting of Firm DBA's violations to the state licensure board produce better long-term outcomes for public welfare and professional integrity - including deterrence of future inequitable engagement practices - than limiting escalation to the City alone, even if such reporting risks disrupting the infrastructure project timeline?
Even though Firm DBA is not providing engineering services, are they required to abide by NSPE's Code of Ethics?
Counterfactual (4)
If Engineer M had formally documented their concerns about the inequitable session locations and lack of written comment mechanisms in writing to Firm DBA before the sessions were held - rather than raising concerns informally after the fact - would Firm DBA have had sufficient notice to correct the process, and would the misleading report have been prevented from entering the public record?
If Engineer M had refused to continue as lead engineer on the project upon learning that Firm DBA submitted the misleading public engagement report without correction, would that act of professional disassociation have been sufficient to satisfy Engineer M's ethical obligations, or would it have left Community P without any advocate capable of challenging the fraudulent record?
If the City had not explicitly instructed Firm DBA to conduct the public engagement sessions in an inequitable manner, would Firm DBA's licensed professional engineers have independently designed an accessible and representative outreach process for Community P, and does the City's direction fundamentally alter the ethical culpability analysis for Firm DBA?
If virtual meetings and written comment mechanisms had been provided alongside the in-person sessions held in Community Q, would the participation gap between Community P and Community Q have been sufficiently narrowed to produce a legitimately representative public engagement record, or were the session locations themselves so fundamentally exclusionary that no supplemental access measures could have remedied the structural inequity?
Decisions & Arguments (6)
View ExtractionShould Engineer M formally confront Firm DBA about the materially false and incomplete public engagement report, state all applicable ethical objections in writing, and require correction before the report is used to advance the project?
Engineer M, as lead engineer of record, bears a duty to monitor and require correction of ethical violations in subconsultant deliverables before they are submitted to the client or used to advance the project. The NSPE Code requires engineers to issue only truthful and objective professional statements and to avoid deceptive acts. The public engagement report is a professional deliverable whose integrity is an engineering ethics matter because its outputs directly inform a consequential routing decision. Pre-session written documentation of deficiencies would have created a contemporaneous record and given the City an earlier opportunity to intervene.
Uncertainty arises if Engineer M lacks direct contractual authority over Firm DBA's report content, or if Firm DBA was acting under explicit City direction that superseded Engineer M's oversight role. The failure to document concerns in writing before the sessions were held reduced Engineer M's practical ability to challenge the report effectively after the fact.
Firm DBA submitted a public engagement report omitting session locations, times, and the prohibition on written comments, while affirmatively claiming Community P supported the project. Community P residents were systematically excluded from meaningful participation due to inaccessible session locations and scheduling. Engineer M raised concerns informally; Firm DBA dismissed them citing City direction and consistency with prior projects. The misleading report entered the public record.
After Firm DBA refuses to correct the misleading public engagement report, should Engineer M escalate formally to the City, advise the City in writing that the report is materially false and that the project cannot proceed ethically on its current basis, and present the ethical obligations of all parties before considering external regulatory reporting?
The graduated escalation obligation requires Engineer M to escalate to the City after Firm DBA's non-compliance, with Firm DBA's knowledge and potential presence, and to present the ethical obligations of all parties. Engineer M bears an independent obligation to advise the City that the project will not succeed if it proceeds on the basis of the false report. The Code's hierarchy places public welfare as paramount, making client service legitimate only insofar as it does not require action against that paramount obligation. The City's direction does not constitute a legitimate client directive because client authority extends only to lawful and professionally appropriate direction.
Uncertainty is created if the City itself directed the fraudulent conduct, because escalating to the City as the corrective authority is undermined when the City is also a party to the violation. There is also ambiguity about whether Engineer M can refuse a client directive without triggering contract breach.
Firm DBA dismissed Engineer M's concerns about the misleading public engagement report and cited City direction as justification. The misleading report entered the public record. The City itself had directed the inequitable engagement process, citing economic, political, and social considerations. Engineer M had not yet formally escalated to the City with documented objections. The project was at risk of proceeding on a fraudulent evidentiary basis with Engineer M's implicit professional endorsement as lead engineer.
After exhausting escalation to both Firm DBA and the City without obtaining correction of the fraudulent public engagement report, should Engineer M refuse to continue as lead engineer and formally document the basis for disassociation, including the specific deficiencies in the report and the corrective action required, rather than remaining associated with a project proceeding on a fraudulent evidentiary record?
The Code prohibits engineers from permitting the use of their name or continuing association in business ventures with persons or firms engaged in fraudulent or dishonest enterprise. Continued association after recognizing the report as fraudulent constitutes implicit professional endorsement beyond the point of recognized misrepresentation. However, disassociation alone is ethically insufficient, the paramount public welfare obligation does not terminate upon disassociation and requires active steps to prevent the harm from persisting. Ethical sufficiency requires both disassociation and formal documented disclosure to the City identifying the report's deficiencies and required corrective action.
Uncertainty is created by the absence of a defined threshold at which continued association crosses into complicity, and by the possibility that premature disassociation could harm Community P by eliminating the only professional advocate capable of challenging the fraudulent record from within the project. Disassociation would be sufficient only if external escalation pathways, such as licensure board reporting or direct community notification, could substitute for Engineer M's internal advocacy role.
Engineer M recognized Firm DBA's public engagement report as materially misrepresentative. Firm DBA dismissed concerns citing City direction. The City, itself implicated in directing the inequitable process, declined to take corrective action. The project was proceeding on a fraudulent evidentiary basis with Engineer M's implicit professional endorsement as lead engineer. Community P remained without a professional advocate capable of challenging the fraudulent record in the public process.
Should Firm DBA's licensed PE supervisors reject the materially misrepresentative public engagement report and require corrective action, or allow the report to stand on the grounds that the communications department's execution insulates them from supervisory responsibility?
The NSPE Code applies universally to firms with licensed professional engineers in supervisory or ownership roles, regardless of whether the specific services constitute traditional engineering design work. The public engagement process here is a data-collection mechanism whose outputs directly inform a consequential engineering and planning decision, making its integrity an engineering ethics matter. Responsible charge over a department that produces a fraudulent report means responsible charge over the fraud itself. The City's direction explains the genesis of the violation but does not excuse it. Code obligations regarding deception and misrepresentation are unconditional and non-delegable. The rationalization that sessions were consistent with prior City projects substitutes institutional habit for independent ethical judgment and fails the virtue ethics standard.
The Code universality warrant is rebutted if the PE supervisory structure was nominal rather than substantive: i.e., if licensed PEs did not actually exercise responsible charge over the engagement design. Uncertainty also arises about whether the communications department's work constitutes engineering practice subject to the Code, and whether City direction constitutes a mitigating factor reducing Firm DBA's culpability.
Firm DBA's communications and public relations department designed and executed a public engagement process that held sessions during work hours at venues inaccessible to Community P residents, excluded written and virtual participation, and produced a report omitting these conditions while affirmatively claiming Community P's support. Firm DBA's licensed PE supervisors and owners retained responsible charge over all departments including the communications department. Firm DBA dismissed Engineer M's concerns citing City direction and consistency with prior City projects.
If the City declines to correct the fraudulent public engagement record after Engineer M's formal escalation, should Engineer M report Firm DBA's ethical violations to the state engineering licensure board to prevent similar situations from occurring in the future, even if such reporting risks disrupting the infrastructure project timeline?
The obligation to report known Code violations to appropriate authorities becomes mandatory, not optional, once lower-level resolution pathways are genuinely exhausted. The City is not a neutral corrective authority because it is itself implicated in directing the inequitable process, making independent licensure board reporting necessary for effective accountability. Licensure board reporting creates a formal record of the violation independent of the project's political and economic dynamics, providing deterrence that a private City-level resolution does not. The normalization of fraudulent public engagement practices for infrastructure projects affecting underserved communities produces systemic harms to democratic legitimacy, environmental justice, and professional integrity that are best addressed through formal accountability mechanisms.
Uncertainty is created by the possibility that licensure board reporting would not apply if the marginal deterrence benefit is outweighed by concrete harm to Community P from project delay. Graduated escalation also requires that internal escalation be genuinely attempted and failed, not merely initiated, before the licensure board reporting obligation becomes operative.
Engineer M escalated formally to the City after Firm DBA's non-compliance. The City, itself implicated in directing the inequitable engagement process, declined to take corrective action. The misleading public engagement report remained in the public record as the evidentiary basis for routing a major highway through Community P. Both the subconsultant and the client had demonstrated that internal resolution was unavailable. Community P remained without meaningful participation in a decision materially affecting their neighborhood.
Should Engineer M refuse to allow the project to proceed on the basis of the City-directed fraudulent engagement record, or defer to the City's directives and continue supporting the project?
The Code's explicit hierarchy places public welfare as paramount, making client service legitimate only insofar as it does not require action against that paramount obligation. Client authority extends only to lawful and professionally appropriate direction, not to directing deceptive acts or suppressing community input in a way that misrepresents the basis for a major infrastructure decision. When a client directive foreseeably channels harm toward a historically underserved community by suppressing meaningful participation, compliance with that directive is a facilitation of public harm, not legitimate client service. The harm here flows through a procedural mechanism, a fraudulent engagement report, but is equivalent in severity to a structural defect because it directly corrupts the evidentiary basis of a consequential public decision.
Uncertainty is created by the absence of a clear procedural mechanism for Engineer M to refuse a client directive without triggering contract breach, and by ambiguity about whether environmental justice considerations constitute a recognized basis for overriding client authority under the Code. The paramount obligation warrant also loses force if the harm to Community P is characterized as procedural rather than safety-critical, or if the fraudulent report is deemed correctable through normal project processes.
The City explicitly instructed Firm DBA to conduct public engagement sessions in a manner that foreseeably excluded Community P residents, citing economic, political, and social considerations. Community P is a historically underserved, underrepresented, and overburdened neighborhood whose residents raised concrete concerns about displacement and business disruption during the limited participation that did occur. The resulting fraudulent public engagement report directly corrupted the evidentiary basis on which a consequential routing decision would be made. Engineer M, as lead engineer retained directly by the City, held a paramount duty to the public welfare not subordinate to client authority.
Event Timeline (13)
Case timeline
- Duty to ensure equitable access to public participation for historically underserved communities
- Obligation to exercise adequate oversight of contracted outreach activities affecting public welfare
- Procedural requirement to conduct public engagement before infrastructure decisions
- Nominal procedural compliance with holding sessions (form only)
- NSPE Code obligation to hold paramount the safety, health, and welfare of the public (Code I.1)
- Duty to conduct objective and truthful professional services
- Obligation to serve the public interest, not merely client political preferences
- Duty of equitable treatment of all affected community stakeholders
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- Duty to provide objective professional services not distorted by client political preferences
- Obligation to ensure meaningful public participation in infrastructure decisions affecting underserved communities
- Duty of truthfulness in professional practice
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- Duty to notify appropriate parties of potential project failures or ethical violations (Code III.1.b)
- Obligation not to remain passive when aware of practices that misrepresent public input
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- Duty to issue truthful and objective reports (Code II.3.b)
- Obligation to respond in good faith to substantive ethical concerns raised by a peer engineer
- Duty not to engage in deceptive professional practices
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- NSPE Code prohibition on issuing false, misleading, or deceptive statements (Code II.3.b)
- NSPE Code prohibition on associating with fraudulent or dishonest enterprises (Code II.1.d)
- Duty of objectivity and truthfulness in professional reports
- Obligation to accurately represent the scope and limitations of professional work
- Duty not to misrepresent community input in public infrastructure planning
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- Duty not to associate with fraudulent or dishonest enterprises (Code II.1.d)
- Obligation to take action when aware of Code violations by other engineers
- Duty to advise when project integrity is compromised (Code III.1.b)
- NSPE Code obligation to hold paramount public safety, health, and welfare (Code I.1)
- Duty to advise clients when a project may not be successful or when integrity is compromised (Code III.1.b)
- Obligation not to associate with fraudulent or dishonest enterprises (Code II.1.d)
- Duty to take escalating action when peer-level correction has failed
Narrative (2 main characters)
View ExtractionOpening 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, a licensed professional engineer serving as the lead engineer on a highway upgrade project under a municipal infrastructure client. The project carries a legal mandate for meaningful public engagement with affected communities. During the engagement process, you have become aware that Firm DBA, the subconsultant responsible for public outreach, has produced a public engagement report that omits material community objections and misrepresents the scope of consultation conducted. The City directed the engagement approach, and Firm DBA's licensed PE supervisors approved the report for submission. You now face a series of decisions about whether to confront the inaccuracies, escalate within and beyond the project, and determine how far your professional obligations extend when both your subconsultant and your client resist correction.
Main characters (2)
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.
Tension between Engineer M Non-Association Fraudulent Enterprise Firm DBA and Non-Association with Fraudulent Enterprise Constraint
Engineer M is obligated to disassociate from Firm DBA's fraudulent public engagement report, yet simultaneously bears a professional duty to deliver a successful highway upgrade project to the City. Disassociation — potentially including refusal to submit or endorse the fraudulent report — may halt or severely delay the project, creating a direct conflict between ethical integrity and project delivery obligations. Fulfilling the non-association duty risks project failure; prioritizing project success risks complicity in fraud.
Tension between Engineer M Graduated Escalation City After Firm DBA Non-Compliance and Graduated Subconsultant Escalation Procedural Constraint
Engineer M is obligated to escalate Firm DBA's non-compliance to the City client as the next step in the graduated escalation process. However, the constraint against complying with client-directed ethical violations becomes acutely relevant if the City itself is implicated in — or indifferent to — the fraudulent engagement practices. Escalating to the City may be procedurally required, yet if the City directed or condoned the misconduct, that same escalation step becomes ethically hollow or even counterproductive, forcing Engineer M to choose between following the prescribed escalation ladder and taking more immediate independent action to prevent ongoing harm.
Tension between Engineer M Safety Obligation Public Welfare Highway Upgrade Community P and Client-Directed Ethical Violation Non-Compliance Constraint
Engineer M's paramount obligation to protect public safety and welfare supports moving the highway project forward to deliver infrastructure benefits, yet the environmental justice protection constraint demands that Community P — a historically underserved population — not bear disproportionate burdens from a project process tainted by fraudulent engagement. Proceeding with the project on the basis of a fraudulent public engagement report may expose Community P to unmitigated harms that were never legitimately surfaced or addressed, meaning the safety obligation and the environmental justice constraint pull in opposite directions regarding whether project continuation is ethically permissible.
Tension between Engineer M Licensure Board Reporting Firm DBA After City Inaction and Graduated Subconsultant Escalation Procedural Constraint
Tension between Engineer M Subcontractor Ethical Compliance Oversight Firm DBA and Graduated Subconsultant Escalation Procedural Constraint
Tension between Engineer M Non-Association Fraudulent Enterprise Firm DBA and Non-Association with Fraudulent Enterprise Constraint
Tension between Engineer M Graduated Escalation City After Firm DBA Non-Compliance and Graduated Subconsultant Escalation Procedural Constraint
Engineer M is obligated to escalate Firm DBA's non-compliance to the City client as the next step in the graduated escalation process. However, the constraint against complying with client-directed ethical violations becomes acutely relevant if the City itself is implicated in — or indifferent to — the fraudulent engagement practices. Escalating to the City may be procedurally required, yet if the City directed or condoned the misconduct, that same escalation step becomes ethically hollow or even counterproductive, forcing Engineer M to choose between following the prescribed escalation ladder and taking more immediate independent action to prevent ongoing harm.
Tension between Engineer M Licensure Board Reporting Firm DBA After City Inaction and Graduated Subconsultant Escalation Procedural Constraint
Tension between Firm DBA Public Engagement Report Completeness Accuracy Highway Upgrade and Code of Ethics Universal Applicability Constraint
Tension between Engineer M Subcontractor Ethical Compliance Oversight Firm DBA and Graduated Subconsultant Escalation Procedural Constraint
Other people involved in the case but not central to the opening narrative.
Engineer M is obligated to disassociate from Firm DBA's fraudulent public engagement report, yet simultaneously bears a professional duty to deliver a successful highway upgrade project to the City. Disassociation — potentially including refusal to submit or endorse the fraudulent report — may halt or severely delay the project, creating a direct conflict between ethical integrity and project delivery obligations. Fulfilling the non-association duty risks project failure; prioritizing project success risks complicity in fraud.
Engineer M's paramount obligation to protect public safety and welfare supports moving the highway project forward to deliver infrastructure benefits, yet the environmental justice protection constraint demands that Community P — a historically underserved population — not bear disproportionate burdens from a project process tainted by fraudulent engagement. Proceeding with the project on the basis of a fraudulent public engagement report may expose Community P to unmitigated harms that were never legitimately surfaced or addressed, meaning the safety obligation and the environmental justice constraint pull in opposite directions regarding whether project continuation is ethically permissible.
Engineer M is obligated to escalate Firm DBA's non-compliance to the City client as the next step in the graduated escalation process. However, the constraint against complying with client-directed ethical violations becomes acutely relevant if the City itself is implicated in — or indifferent to — the fraudulent engagement practices. Escalating to the City may be procedurally required, yet if the City directed or condoned the misconduct, that same escalation step becomes ethically hollow or even counterproductive, forcing Engineer M to choose between following the prescribed escalation ladder and taking more immediate independent action to prevent ongoing harm.
Engineer M is obligated to disassociate from Firm DBA's fraudulent public engagement report, yet simultaneously bears a professional duty to deliver a successful highway upgrade project to the City. Disassociation — potentially including refusal to submit or endorse the fraudulent report — may halt or severely delay the project, creating a direct conflict between ethical integrity and project delivery obligations. Fulfilling the non-association duty risks project failure; prioritizing project success risks complicity in fraud.
Tension between Engineer M Safety Obligation Public Welfare Highway Upgrade Community P and Client-Directed Ethical Violation Non-Compliance Constraint
Engineer M's paramount obligation to protect public safety and welfare supports moving the highway project forward to deliver infrastructure benefits, yet the environmental justice protection constraint demands that Community P — a historically underserved population — not bear disproportionate burdens from a project process tainted by fraudulent engagement. Proceeding with the project on the basis of a fraudulent public engagement report may expose Community P to unmitigated harms that were never legitimately surfaced or addressed, meaning the safety obligation and the environmental justice constraint pull in opposite directions regarding whether project continuation is ethically permissible.
Engineer M is obligated to escalate Firm DBA's non-compliance to the City client as the next step in the graduated escalation process. However, the constraint against complying with client-directed ethical violations becomes acutely relevant if the City itself is implicated in — or indifferent to — the fraudulent engagement practices. Escalating to the City may be procedurally required, yet if the City directed or condoned the misconduct, that same escalation step becomes ethically hollow or even counterproductive, forcing Engineer M to choose between following the prescribed escalation ladder and taking more immediate independent action to prevent ongoing harm.
Engineer M is obligated to disassociate from Firm DBA's fraudulent public engagement report, yet simultaneously bears a professional duty to deliver a successful highway upgrade project to the City. Disassociation — potentially including refusal to submit or endorse the fraudulent report — may halt or severely delay the project, creating a direct conflict between ethical integrity and project delivery obligations. Fulfilling the non-association duty risks project failure; prioritizing project success risks complicity in fraud.
Opening States (10)
Summary
- Engineers have an affirmative duty to escalate ethical concerns through graduated channels — first to the offending firm, then to the client, and finally to regulatory authorities — when subcontractors engage in non-compliant practices.
- Association with a firm operating fraudulently, even in a subcontractor capacity, implicates the supervising engineer's ethical standing regardless of organizational distance from the misconduct.
- The provision of engineering services under licensed PE supervision does not legitimize an unlicensed or improperly structured firm's business operations, as licensure requirements attach to the entity's legal and professional structure, not merely its output quality.