Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Duty To Report Violation—Anonymous Complaint
Step 4 of 5
Entity Review

235

Entities

6

Provisions

1

Precedents

17

Questions

22

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's personal ethical obligation under Code Section II.1.f — to act upon knowledge of a serious professional conduct violation — transfers to the state licensure board upon submission of the anonymous complaint. The board then assumes responsibility for investigation, credibility assessment, procedural fairness protections for Engineer B, and any disciplinary action. Engineer A exits the obligation set; the board enters it. The transfer is conditioned on the board having an established anonymous complaint procedure, which is the mechanism that makes the handoff institutionally valid.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

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

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (6)
View Extraction
II.1. Engineers shall hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 28)
Obligation
Engineer A BER 89-7 Out-of-Discipline Safety Code Violation Reporting
The duty to hold public safety paramount directly grounds the obligation to report safety-related code violations even outside one's discipline.
Action
Observe and Assess Violation
Engineers must hold public safety paramount, which requires recognizing and evaluating safety violations when encountered.
State
BER 89-7 Public Safety at Risk from Building Code Violations
This provision directly requires engineers to hold public safety paramount, which applies to the risk posed to occupants by building code deficiencies.
Obligation (4)
  • Engineer A BER 89-7 Out-of-Discipline Safety Code Violation Reporting
    The duty to hold public safety paramount directly grounds the obligation to report safety-related code violations even outside one's discipline.
  • Engineer A BER 89-7 Confidentiality Agreement Non-Excuse for Safety Reporting
    Paramount public safety overrides confidentiality agreements when known code violations pose a safety risk.
  • Engineer A BER 89-7 Brief Report Mention Insufficiency
    Holding public safety paramount requires more than a brief mention in a confidential report when serious violations are known.
  • Engineer A Current Case Self-Policing Foundational Reporting Duty
    The foundational duty to protect public welfare underlies the self-policing reporting obligation for serious professional violations.
Action (2)
  • Observe and Assess Violation
    Engineers must hold public safety paramount, which requires recognizing and evaluating safety violations when encountered.
  • Withhold Safety Violation Report (BER 89-7)
    Withholding a safety violation report directly conflicts with the duty to hold public safety paramount.
State (3)
  • BER 89-7 Public Safety at Risk from Building Code Violations
    This provision directly requires engineers to hold public safety paramount, which applies to the risk posed to occupants by building code deficiencies.
  • BER 89-7 Client Confidentiality vs. Public Safety Conflict
    This provision establishes that public safety must be held paramount, directly framing the conflict between client confidentiality and safety obligations.
  • BER 89-7 Confidentiality Agreement Suppressing Safety Report
    The provision requires engineers to prioritize public safety over contractual confidentiality obligations that suppress safety-related information.
Constraint (4)
  • Present Case Engineer A Self-Policing Profession Foundational Reporting Duty Constraint Instance
    The paramount duty to protect public safety grounds the foundational reporting obligation that constrains Engineer A as a licensed professional.
  • BER 89-7 Confidentiality Agreement Non-Bar to Safety Reporting Constraint Instance
    Public safety paramount duty overrides confidentiality agreements when code violations posing safety risks are known.
  • BER 89-7 Brief Report Mention Insufficiency Constraint Instance
    The duty to hold public safety paramount requires more than a brief mention in a confidential report to adequately address known safety violations.
  • Engineer A Anonymous Reporting Adequacy Serious Violation BER Case
    The paramount safety duty sets the standard against which the adequacy of Engineer A's anonymous complaint is measured.
Principle (3)
  • Engineering Self-Policing Obligation Invoked in BER Case Context
    Holding public safety paramount underpins the profession's self-policing obligation to report violations.
  • Public Welfare Paramount Applied in BER 89-7 Confidentiality Override
    This provision directly supports the ruling that public safety overrides confidentiality agreements.
  • Confidentiality Non-Applicability to Public Danger Invoked in BER 89-7
    The paramount duty to public welfare is the basis for overriding confidentiality when public danger exists.
Role (2)
  • Engineer A BER 89-7 Confidentiality-Bound Building Sale Engineer
    Engineer A must hold public safety paramount when deciding whether to report known building code violations despite a confidentiality agreement.
  • Engineer A Anonymous Professional Conduct Complaint Filer
    Engineer A's decision to file a complaint about Engineer B reflects the duty to protect public welfare by reporting unethical conduct.
Event (2)
  • BER 89-7 Safety Harm Materializes
    This provision directly addresses the paramount duty to protect public safety which is at stake when safety harm occurs.
  • Professional Violation Occurs
    A professional violation that endangers public safety triggers the paramount duty engineers hold under this provision.
Resource (4)
  • NSPE Code of Ethics - Section I.1
    This provision establishes the paramount obligation to protect public safety that Section I.1 is cited as the primary normative authority for.
  • BER Case 89-7
    BER 89-7 is cited as precedent applying the public health and safety paramount obligation that II.1 establishes.
  • Client Confidentiality vs. Public Safety Balancing Framework (BER 89-7 Application)
    This framework directly applies the II.1 paramount safety obligation when weighing it against confidentiality duties.
  • NSPE_Code_of_Ethics
    II.1 is a core provision of the NSPE Code of Ethics which provides the overarching professional ethics framework governing engineer conduct.
Capability (4)
  • Engineer A Current Case Public Welfare Paramountcy Recognition
    This provision directly requires engineers to hold public safety paramount, which is the core capability Engineer A demonstrated.
  • Engineer A Current Case Confidentiality Pre-emption by Public Safety Recognition
    This provision establishes that public safety overrides other considerations including confidentiality, which is what Engineer A recognized.
  • Engineer A Current Case Self-Policing Profession Reporting Duty Recognition
    The duty to hold public welfare paramount grounds the self-policing reporting obligation Engineer A recognized.
  • Engineer A BER 89-7 Out-of-Discipline Reporting Duty Activation
    Holding public welfare paramount requires reporting violations even outside one's engineering discipline.
II.1.e. Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
How this applies in the case (showing 3 of 20)
Obligation
Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
Reporting Engineer B's serious violation directly prevents Engineer A from aiding or abetting unlawful engineering practice through silence.
Action
Withhold Safety Violation Report (BER 89-7)
Failing to report unlawful engineering practice can constitute aiding or abetting that unlawful practice.
State
Engineer A Peer Violation Observation State
This provision prohibits aiding or abetting unlawful engineering practice, which is directly relevant when Engineer A observes Engineer B's alleged serious rules violation.
Obligation (3)
  • Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
    Reporting Engineer B's serious violation directly prevents Engineer A from aiding or abetting unlawful engineering practice through silence.
  • Engineer B Licensure Board Accountability Process BER Case
    Engineer B's accountability to the state board relates to ensuring licensed engineers do not engage in unlawful practice.
  • Engineer A Current Case Self-Policing Foundational Reporting Duty
    The obligation not to abet unlawful practice reinforces the duty to report apparent violations of state board rules.
Action (1)
  • Withhold Safety Violation Report (BER 89-7)
    Failing to report unlawful engineering practice can constitute aiding or abetting that unlawful practice.
State (2)
  • Engineer A Peer Violation Observation State
    This provision prohibits aiding or abetting unlawful engineering practice, which is directly relevant when Engineer A observes Engineer B's alleged serious rules violation.
  • Present Case Self-Policing Profession Peer Reporting Duty
    By prohibiting aiding unlawful practice, this provision reinforces Engineer A's duty not to remain silent about Engineer B's misconduct.
Constraint (2)
  • Present Case Engineer A Self-Policing Profession Foundational Reporting Duty Constraint Instance
    The prohibition on aiding unlawful engineering practice reinforces the foundational duty to report Engineer B's apparent violation.
  • Engineer A Non-Competitor No-Personal-Relationship Reporting Duty BER Case
    The duty not to abet unlawful practice applies regardless of competitive or personal relationship status between engineers.
Principle (3)
  • Mandatory Competitor Misconduct Reporting Obligation Applied to Engineer A
    Not aiding unlawful practice directly supports the obligation to report Engineer B's serious violation.
  • Mandatory Misconduct Reporting Invoked By Engineer A Against Engineer B
    This provision prohibits abetting unlawful engineering practice, reinforcing Engineer A's duty to report.
  • Professional Accountability Applied to Engineer B's Obligation to Respond
    The prohibition on aiding unlawful practice establishes Engineer B's accountability for the alleged violation.
Role (2)
  • Engineer A BER 89-7 Confidentiality-Bound Building Sale Engineer
    Engineer A must not aid the client in concealing code violations that could constitute unlawful engineering practice.
  • Building Sale Client BER 89-7
    The client's concealment of known code violations could constitute unlawful practice that Engineer A must not abet.
Event (2)
  • Professional Violation Occurs
    This provision prohibits aiding or abetting unlawful engineering practice, which is directly implicated when a professional violation occurs.
  • Violation Becomes Observed
    Once a violation is observed, this provision becomes relevant as the observing engineer must not aid or abet the unlawful practice.
Resource (3)
  • State_Board_Rules_of_Professional_Conduct
    Aiding unlawful practice relates directly to the rules whose violation by Engineer B forms the basis of the complaint.
  • State Licensing Board Rules of Professional Conduct (Referenced in Case)
    This provision prohibits aiding unlawful engineering practice, which is governed by the state licensing board rules referenced in the case.
  • NSPE_Code_of_Ethics
    II.1.e is a provision within the NSPE Code of Ethics framework governing Engineer A's obligations regarding Engineer B's conduct.
Capability (2)
  • Engineer A BER 89-7 Confidential Report Brief Mention Insufficiency Recognition
    Failing to adequately report known violations risks aiding unlawful engineering practice, which this provision prohibits.
  • Engineer A BER 89-7 Out-of-Discipline Reporting Duty Activation
    This provision prohibits aiding unlawful practice, requiring Engineer A to report violations even outside his structural discipline.
II.1.f. 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 69)
Obligation
Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
This provision directly mandates reporting known violations to appropriate professional bodies, which is the core obligation Engineer A fulfills.
Action
Decision to File Complaint
This provision directly requires engineers with knowledge of a Code violation to report it to appropriate bodies.
State
Present Case Anonymous Reporting Adequacy
This provision requires engineers to report violations to appropriate bodies, directly raising the question of whether an anonymous complaint satisfies that reporting obligation.
Obligation (13)
  • Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
    This provision directly mandates reporting known violations to appropriate professional bodies, which is the core obligation Engineer A fulfills.
  • Engineer A Anonymous Filing Permissibility Assessment BER Case
    The provision requires reporting to appropriate bodies and speaks to the manner of reporting, making anonymous filing relevant to its satisfaction.
  • Engineer A Collegial Pre-Reporting Engagement Non-Requirement Serious Violation BER Case
    The provision imposes a duty to report without conditioning it on prior direct engagement with the accused engineer.
  • Engineer A No-Personal-Relationship Non-Excuse for Non-Reporting BER Case
    The reporting duty under this provision arises from knowledge of a violation, not from any personal relationship with the violator.
  • Engineer A Motivation Purity Disinterested Reporting BER Case
    The provision frames reporting as a professional duty, consistent with disinterested motivation rather than personal animus.
  • Engineer B Licensure Board Accountability Process BER Case
    Reporting to the state board triggers the accountability process that this provision requires engineers to support.
  • Engineer A BER 89-7 Out-of-Discipline Safety Code Violation Reporting
    The provision requires reporting violations to appropriate public authorities, directly grounding the obligation to report code violations outside one's discipline.
  • Engineer A BER 89-7 Confidentiality Agreement Non-Excuse for Safety Reporting
    The mandatory reporting duty under this provision overrides confidentiality agreements when violations must be disclosed to authorities.
  • Engineer A BER 89-7 Brief Report Mention Insufficiency
    The provision requires reporting to appropriate authorities, not merely noting violations in a confidential internal report.
  • Engineer A Current Case Self-Policing Foundational Reporting Duty
    This provision is the direct textual basis for the self-policing reporting obligation described in this entity.
  • Engineer A Current Case Signed Complaint Policy Preference
    The provision's requirement to cooperate with authorities supports the policy preference for a signed complaint that enables full cooperation.
  • Engineer A Current Case Anonymous Complaint Case-Weakening Acknowledgment
    The duty to cooperate with authorities implies that anonymous filing may undermine the effectiveness of the required reporting.
  • Engineer B Procedural Fairness Interest in Knowing Accuser Identity
    The provision's emphasis on cooperation with proper authorities connects to procedural integrity, including the accused's interest in knowing the complainant.
Action (3)
  • Decision to File Complaint
    This provision directly requires engineers with knowledge of a Code violation to report it to appropriate bodies.
  • Submit Complaint Anonymously
    This provision governs how complaints must be reported, implying cooperation with authorities which may conflict with anonymous submission.
  • Withhold Safety Violation Report (BER 89-7)
    Withholding a known violation report directly violates the duty to report to appropriate professional bodies.
State (5)
  • Present Case Anonymous Reporting Adequacy
    This provision requires engineers to report violations to appropriate bodies, directly raising the question of whether an anonymous complaint satisfies that reporting obligation.
  • Engineer A Peer Violation Observation State
    This provision explicitly obligates engineers with knowledge of alleged violations to report them to appropriate professional bodies.
  • Engineer A Anonymous Complaint Filing State
    This provision requires reporting and cooperation with authorities, which bears directly on whether filing anonymously fulfills the duty to report and cooperate.
  • Present Case Self-Policing Profession Peer Reporting Duty
    This provision is the primary code basis for Engineer A's foundational professional obligation to report Engineer B's misconduct to the appropriate authority.
  • Present Case Non-Competitor Peer Reporting Obligation
    This provision establishes the reporting duty regardless of competitive or personal motivations, supporting the evaluation of Engineer A's obligation as a neutral peer.
Constraint (11)
  • Engineer A Anonymous Reporting Adequacy Serious Violation BER Case
    This provision directly creates the reporting obligation whose adequacy is evaluated when Engineer A files anonymously.
  • Engineer A Serious Violation Collegial Pre-Reporting Non-Requirement BER Case
    The duty to report to appropriate bodies does not condition reporting on first approaching the offending engineer collegially.
  • Engineer A Competitive Interest Neutrality Disinterested Reporting BER Case
    This provision requires reporting based on professional duty, implying the motivation must be genuine rather than competitive.
  • Engineer A Friendship Non-Reporting Prohibition Non-Applicability BER Case
    The reporting duty applies universally and is not excused by friendship or lack thereof with the engineer being reported.
  • Present Case Engineer A Anonymous vs. Signed Complaint Policy Preference Constraint Instance
    This provision creates the reporting duty and its policy preference for identified complaints that anonymous filing does not fully satisfy.
  • Present Case Engineer A Anonymous Complaint Permissibility Constraint Instance
    This provision establishes the reporting obligation within which anonymous filing is evaluated as permissible but not ideal.
  • Present Case Engineer A Self-Policing Profession Foundational Reporting Duty Constraint Instance
    This provision is the direct source of the foundational reporting duty constraining Engineer A as a licensed professional.
  • Engineer A Non-Competitor No-Personal-Relationship Reporting Duty BER Case
    This provision establishes that the reporting duty is not diminished by the absence of competitive or personal relationships.
  • BER 89-7 Confidentiality Agreement Non-Bar to Safety Reporting Constraint Instance
    This provision requires reporting to appropriate authorities and is not negated by a confidentiality agreement with a client.
  • BER 89-7 Brief Report Mention Insufficiency Constraint Instance
    This provision requires reporting to appropriate bodies, which a brief mention in a confidential internal report does not fulfill.
  • Present Case Engineer A Client Confidentiality Reliance Modulation Constraint Instance
    This provision creates the reporting duty that is modulated but not eliminated by the client confidentiality agreement context.
Principle (10)
  • Engineering Self-Policing Obligation Invoked in BER Case Context
    This provision is the direct codification of the profession's self-policing obligation to report violations to proper authorities.
  • Disinterested Professional Duty to Report Invoked by Engineer A
    This provision mandates reporting known violations regardless of personal or competitive interest.
  • Anonymous Reporting as Ethical Minimum Applied to Engineer A's Complaint
    This provision requires reporting to appropriate bodies, and the Board links anonymous reporting as satisfying this minimum requirement.
  • Signed Complaint Preference Applied to Engineer A's Reporting Decision
    This provision's reporting mandate supports the policy preference for signed complaints as a fuller expression of the duty.
  • Mandatory Competitor Misconduct Reporting Obligation Applied to Engineer A
    This provision directly obligates Engineer A to report the known serious violation to the appropriate professional body.
  • Mandatory Misconduct Reporting Invoked By Engineer A Against Engineer B
    This provision is the explicit code basis for Engineer A's obligation to report Engineer B's misconduct.
  • Anonymous Reporting Permissibility Invoked By Engineer A
    This provision's reporting requirement is the standard against which the permissibility of anonymous reporting is evaluated.
  • Collegial Pre-Reporting Engagement Question Raised By Engineer A Situation
    This provision's direct reporting mandate informs whether prior collegial engagement is required before filing a complaint.
  • Disinterested Professional Duty Demonstrated By Engineer A
    This provision establishes the duty that Engineer A fulfills by reporting without competitive or personal motivation.
  • Professional Accountability of Engineer B Through Licensing Board Process
    This provision establishes the reporting mechanism that subjects Engineer B to the licensing board accountability process.
Role (3)
  • Engineer A BER 89-7 Confidentiality-Bound Building Sale Engineer
    Engineer A has knowledge of alleged code violations and is obligated to report them to appropriate authorities despite the confidentiality agreement.
  • Engineer A Anonymous Professional Conduct Complaint Filer
    Engineer A is required to report Engineer B's alleged violation of professional conduct rules to the appropriate professional body.
  • State Licensing Board Complaint Recipient
    The state licensing board is the appropriate professional body to which violations must be reported under this provision.
Event (4)
  • Violation Becomes Observed
    Observing a violation directly triggers the duty under this provision to report to appropriate bodies.
  • Reporting Obligation Activated
    This provision is the explicit basis for the reporting obligation that becomes activated upon knowledge of a violation.
  • Anonymous Complaint Received
    This provision governs the act of reporting, which is what the anonymous complaint represents in practice.
  • Ethical Permissibility Established
    This provision establishes that reporting is not only permitted but required, forming the basis for ethical permissibility of the complaint.
Resource (6)
  • Engineer_Reporting_Obligation_to_Licensing_Board
    This provision directly governs whether and how Engineer A must report the observed violation to the state engineering licensure board.
  • Engineer_Reporting_Obligation_to_State_Board
    II.1.f establishes the professional duty to report violations to relevant state regulatory authorities that this entity describes.
  • Engineer Reporting Obligation to State Board Standard (Self-Policing Duty)
    II.1.f is the foundational code provision requiring engineers to report unprofessional conduct to appropriate professional bodies and public authorities.
  • Anonymous Ethics Complaint Policy (NSPE BER Guidance)
    II.1.f requires reporting to appropriate bodies, making the permissibility of anonymous complaint filing directly relevant to fulfilling this provision.
  • State Licensing Board Rules of Professional Conduct (Referenced in Case)
    II.1.f directs engineers to report violations to appropriate public authorities, which includes the state licensing board referenced in the case.
  • NSPE_Code_of_Ethics
    II.1.f is a provision within the NSPE Code of Ethics that governs Engineer A's reporting obligation.
Capability (14)
  • Engineer A Disinterested Reporting Duty Recognition BER Case
    This provision mandates reporting known violations to proper authorities, which is the duty Engineer A recognized regardless of personal interest.
  • Engineer A Anonymous Complaint Permissibility Assessment BER Case
    This provision requires reporting to appropriate bodies, and Engineer A assessed whether an anonymous complaint satisfied that requirement.
  • Engineer A Serious Violation Collegial Pre-Engagement Non-Requirement BER Case
    This provision requires reporting to proper authorities without conditioning that obligation on first approaching the offending engineer.
  • Engineer A Reporting Motivation Purity Self-Assessment BER Case
    This provision imposes a duty-based reporting obligation, which Engineer A confirmed was his sole motivation.
  • Engineer A Jurisdiction Misconduct Reporting Threshold Compliance BER Case
    This provision requires reporting violations to appropriate bodies, and Engineer A assessed whether the conduct met the threshold triggering that obligation.
  • Engineer A BER 89-7 Confidential Report Brief Mention Insufficiency Recognition
    This provision requires adequate reporting to proper authorities, and a brief mention in a confidential report failed to meet that standard.
  • Engineer A BER 89-7 Out-of-Discipline Reporting Duty Activation
    This provision requires reporting any known violation regardless of whether it falls within the engineer's own discipline.
  • Engineer A Current Case Anonymous Complaint Permissibility Assessment
    This provision requires reporting to appropriate authorities, and Engineer A assessed whether anonymous filing satisfied that obligation.
  • Engineer A Current Case Accused Engineer Procedural Fairness Interest Recognition
    This provision requires cooperation with proper authorities, which implicates the quality and completeness of the complaint including identity disclosure.
  • Engineer A Current Case Anonymous Complaint Case-Weakening Weighing
    This provision requires effective reporting and cooperation with authorities, making the practical weakening effect of anonymity directly relevant.
  • Engineer A Current Case Signed Complaint Policy Preference Self-Application
    This provision's reporting and cooperation requirement supports the policy preference for signed complaints that better assist authorities.
  • Engineer A Current Case Self-Policing Profession Reporting Duty Recognition
    This provision directly establishes the reporting duty to appropriate professional bodies that Engineer A recognized as foundational.
  • Engineer A Current Case Serious Violation Collegial Pre-Engagement Non-Requirement Recognition
    This provision requires reporting to proper authorities without imposing a prior collegial engagement condition.
  • Engineer A Current Case Reporting Motivation Purity Self-Assessment
    This provision imposes a duty to report that Engineer A confirmed was his sole motivation, free of improper purposes.
II.3. Engineers shall issue public statements only in an objective and truthful manner.
How this applies in the case (showing 3 of 16)
Obligation
Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
Reporting must be objective and truthful, consistent with the disinterested and factual nature of Engineer A's complaint.
Action
Submit Complaint Anonymously
Filing anonymously raises questions about whether the complaint is issued in an objective and truthful manner with full accountability.
State
Engineer A Anonymous Complaint Filing State
This provision requires objective and truthful public statements, which relates to the integrity and accuracy of the complaint Engineer A files with the board.
Obligation (3)
  • Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
    Reporting must be objective and truthful, consistent with the disinterested and factual nature of Engineer A's complaint.
  • Engineer A Motivation Purity Disinterested Reporting BER Case
    The requirement for objective and truthful statements aligns with the obligation that reporting be free from competitive or personal bias.
  • Engineer A Current Case Anonymous Complaint Case-Weakening Acknowledgment
    Objective and truthful reporting is best served by a signed complaint that can be fully verified and tested by authorities.
Action (1)
  • Submit Complaint Anonymously
    Filing anonymously raises questions about whether the complaint is issued in an objective and truthful manner with full accountability.
State (2)
  • Engineer A Anonymous Complaint Filing State
    This provision requires objective and truthful public statements, which relates to the integrity and accuracy of the complaint Engineer A files with the board.
  • Present Case Anonymous Complainant Identity Concealment Fairness
    The requirement for truthful and objective statements is relevant to the fairness implications of concealing the complainant's identity in a board proceeding.
Constraint (2)
  • Engineer A Competitive Interest Neutrality Disinterested Reporting BER Case
    The requirement for objective and truthful statements supports the constraint that reporting must be grounded in genuine duty rather than competitive self-interest.
  • Present Case Engineer A Anonymous vs. Signed Complaint Policy Preference Constraint Instance
    Objective and truthful reporting is better served by identified complaints that allow verification of the complainant's basis for the claim.
Principle (2)
  • Signed Complaint Preference Applied to Engineer A's Reporting Decision
    Issuing statements in an objective and truthful manner supports the preference for a signed, accountable complaint over an anonymous one.
  • Accused Engineer Procedural Fairness Right Acknowledged for Engineer B
    The requirement for objective and truthful statements relates to Engineer B's interest in knowing the context and basis of the complaint.
Role (1)
  • Engineer A Anonymous Professional Conduct Complaint Filer
    Engineer A must ensure that the complaint filed against Engineer B is objective and truthful rather than malicious or misleading.
Event (1)
  • Anonymous Complaint Received
    The complaint as a public statement or report must be objective and truthful as required by this provision.
Resource (2)
  • Anonymous Ethics Complaint Policy (NSPE BER Guidance)
    The requirement to issue statements objectively and truthfully is relevant to the Board's deliberation on whether anonymous complaints meet standards of fairness and accuracy.
  • NSPE_Code_of_Ethics
    II.3 is a provision of the NSPE Code of Ethics framework that governs how engineers must present information about other engineers' conduct.
Capability (2)
  • Engineer A Current Case Reporting Motivation Purity Self-Assessment
    This provision requires truthful and objective statements, which aligns with Engineer A confirming his report was grounded in honest professional duty rather than personal animus.
  • Engineer A Reporting Motivation Purity Self-Assessment BER Case
    This provision requires objectivity and truthfulness in public statements, consistent with Engineer A ensuring his report was free of improper motivation.
III.7. 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 36)
Obligation
Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
This provision permits presenting information about unethical practice to proper authority, which is exactly what Engineer A's disinterested report does.
Action
Decision to File Complaint
This provision requires that complaints about unethical practice be presented to proper authority rather than used to maliciously harm another engineer.
State
Present Case Anonymous Reporting Adequacy
This provision states that engineers believing others are guilty of unethical practice shall present information to proper authority, directly addressing the adequacy of how Engineer A reports.
Obligation (4)
  • Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
    This provision permits presenting information about unethical practice to proper authority, which is exactly what Engineer A's disinterested report does.
  • Engineer A Motivation Purity Disinterested Reporting BER Case
    The prohibition on malicious or false injury requires that reporting be motivated by professional duty rather than personal animus, as confirmed here.
  • Engineer A Current Case Self-Policing Foundational Reporting Duty
    The provision explicitly directs engineers who believe others are guilty of unethical practice to present information to proper authority.
  • Engineer B Licensure Board Accountability Process BER Case
    Presenting information to the proper authority for action is the mechanism by which Engineer B's board accountability process is initiated.
Action (2)
  • Decision to File Complaint
    This provision requires that complaints about unethical practice be presented to proper authority rather than used to maliciously harm another engineer.
  • Submit Complaint Anonymously
    Anonymous complaints must not be motivated by malicious intent to injure another engineers reputation, as prohibited by this provision.
State (4)
  • Present Case Anonymous Reporting Adequacy
    This provision states that engineers believing others are guilty of unethical practice shall present information to proper authority, directly addressing the adequacy of how Engineer A reports.
  • Engineer A Anonymous Complaint Filing State
    This provision prohibits malicious or false injury to another engineer's reputation while requiring proper reporting, framing the ethical boundaries of Engineer A's anonymous complaint.
  • Present Case Anonymous Complainant Identity Concealment Fairness
    This provision's concern with protecting engineers from malicious or false complaints is directly relevant to the fairness implications of anonymous accusations against Engineer B.
  • Present Case Non-Competitor Peer Reporting Obligation
    This provision requires presenting evidence of unethical practice to proper authority, reinforcing Engineer A's obligation to report regardless of competitive considerations.
Constraint (5)
  • Engineer A Competitive Interest Neutrality Disinterested Reporting BER Case
    This provision prohibits malicious or false injury to other engineers, directly constraining Engineer A to report from duty rather than competitive motivation.
  • Engineer A Friendship Non-Reporting Prohibition Non-Applicability BER Case
    This provision directs engineers who believe others are guilty of unethical practice to present information to proper authority, framing the reporting duty regardless of personal relationships.
  • Present Case Engineer B Accuser Identity Fairness Constraint Instance
    This provision protects engineers from malicious or false complaints, supporting Engineer B's legitimate interest in knowing the complainant's identity.
  • Present Case Engineer A Anonymous vs. Signed Complaint Policy Preference Constraint Instance
    The requirement to present information to proper authority for action rather than act maliciously supports the policy preference for identified over anonymous complaints.
  • Engineer A Non-Competitor No-Personal-Relationship Reporting Duty BER Case
    This provision requires presenting evidence of unethical practice to proper authority, reinforcing the reporting duty independent of competitive or personal relationships.
Principle (5)
  • Disinterested Professional Duty to Report Invoked by Engineer A
    This provision distinguishes legitimate reporting of unethical practice from malicious injury to another engineer's reputation, directly relevant to Engineer A's disinterested motivation.
  • Anonymous Reporting as Ethical Minimum Applied to Engineer A's Complaint
    This provision requires presenting evidence of unethical practice to proper authority, which the Board links to the legitimacy of anonymous complaints.
  • Mandatory Misconduct Reporting Invoked By Engineer A Against Engineer B
    This provision explicitly directs engineers who believe others are guilty of unethical practice to present information to proper authority.
  • Disinterested Professional Duty Demonstrated By Engineer A
    This provision's distinction between malicious injury and legitimate reporting affirms that Engineer A's disinterested report is ethically proper.
  • Professional Accountability of Engineer B Through Licensing Board Process
    This provision channels complaints about unethical practice through proper authority, establishing the accountability process Engineer B faces.
Role (2)
  • Engineer A Anonymous Professional Conduct Complaint Filer
    Engineer A must ensure the complaint against Engineer B is not malicious or false and is directed to the proper authority for legitimate action.
  • Engineer B Licensee Subject to Professional Conduct Complaint
    Engineer B is the subject of the complaint and this provision protects his professional reputation from malicious or false allegations.
Event (3)
  • Anonymous Complaint Received
    This provision ensures the complaint is directed to proper authority and not used to maliciously injure another engineers reputation.
  • Ethical Permissibility Established
    This provision clarifies that reporting unethical practice to proper authority is ethically permissible and not malicious injury.
  • Professional Violation Occurs
    When a professional violation occurs, this provision directs that information be presented to proper authority rather than used harmfully.
Resource (5)
  • Anonymous Ethics Complaint Policy (NSPE BER Guidance)
    III.7 prohibits malicious or false injury to other engineers' reputations, directly relevant to whether anonymous complaints risk unfair harm to the accused engineer.
  • Engineer_Reporting_Obligation_to_Licensing_Board
    III.7 requires presenting information about unethical practice to proper authority, which aligns with the obligation to report to the licensing board.
  • Engineer Reporting Obligation to State Board Standard (Self-Policing Duty)
    III.7 explicitly requires engineers who believe others are guilty of unethical practice to present such information to proper authority, embodying the self-policing duty.
  • State Licensing Board Rules of Professional Conduct (Referenced in Case)
    III.7 directs engineers to present information about unethical practice to proper authority, which is the state licensing board in this case.
  • NSPE_Code_of_Ethics
    III.7 is a provision of the NSPE Code of Ethics governing how Engineer A must handle knowledge of Engineer B's alleged violations.
Capability (6)
  • Engineer A Disinterested Reporting Duty Recognition BER Case
    This provision prohibits malicious injury to other engineers while requiring proper reporting, making disinterested motivation directly relevant.
  • Engineer A Reporting Motivation Purity Self-Assessment BER Case
    This provision prohibits malicious or false injury to other engineers, requiring Engineer A to confirm his reporting was not motivated by personal animus.
  • Engineer A Current Case Reporting Motivation Purity Self-Assessment
    This provision prohibits malicious injury to other engineers, making Engineer A's confirmation of pure professional motivation directly required.
  • Engineer A Current Case Accused Engineer Procedural Fairness Interest Recognition
    This provision protects engineers from malicious or false injury, which connects to Engineer B's interest in knowing his accuser.
  • Engineer A Current Case Anonymous Complaint Case-Weakening Weighing
    This provision requires presenting information to proper authority for action, making the practical effectiveness of the complaint a relevant consideration.
  • Engineer A Current Case Signed Complaint Policy Preference Self-Application
    This provision directs engineers to present information to proper authority for action, supporting the preference for a signed complaint that strengthens that action.
III.8.a. Engineers shall conform with state registration laws in the practice of engineering.
How this applies in the case (showing 3 of 22)
Obligation
Engineer B Licensure Board Accountability Process BER Case
Conforming with state registration laws is the standard Engineer B is held to, making the board accountability process directly applicable.
Action
Observe and Assess Violation
Assessing whether a violation occurred involves determining if state registration laws are being breached in the practice of engineering.
State
Engineer A Peer Violation Observation State
This provision requires conformance with state registration laws, making it directly relevant when Engineer A observes Engineer B allegedly violating such laws.
Obligation (3)
  • Engineer B Licensure Board Accountability Process BER Case
    Conforming with state registration laws is the standard Engineer B is held to, making the board accountability process directly applicable.
  • Engineer A Disinterested Reporting of Engineer B Serious Violation BER Case
    The alleged violation of state board rules of professional conduct is a failure to conform with state registration law requirements.
  • Engineer A Current Case Self-Policing Foundational Reporting Duty
    The apparent violation of state board rules that triggers the reporting duty is a violation of the state registration law conformance requirement.
Action (1)
  • Observe and Assess Violation
    Assessing whether a violation occurred involves determining if state registration laws are being breached in the practice of engineering.
State (2)
  • Engineer A Peer Violation Observation State
    This provision requires conformance with state registration laws, making it directly relevant when Engineer A observes Engineer B allegedly violating such laws.
  • Present Case Self-Policing Profession Peer Reporting Duty
    This provision establishes the state registration law framework that Engineer B allegedly violated, underpinning the basis for Engineer A's reporting duty.
Constraint (3)
  • Present Case Engineer A Self-Policing Profession Foundational Reporting Duty Constraint Instance
    Conformance with state registration laws is part of the self-policing professional framework that grounds Engineer A's foundational reporting duty.
  • Engineer A Non-Competitor No-Personal-Relationship Reporting Duty BER Case
    The obligation to conform with registration laws applies to all engineers and supports the reporting duty when violations of those laws are observed.
  • BER 89-7 Confidentiality Agreement Non-Bar to Safety Reporting Constraint Instance
    Conformance with registration laws includes reporting violations thereof, which a confidentiality agreement cannot lawfully bar.
Principle (3)
  • Professional Accountability Applied to Engineer B's Obligation to Respond
    Conforming with state registration laws is the standard Engineer B is accountable for under the licensing board complaint process.
  • Professional Accountability of Engineer B Through Licensing Board Process
    This provision establishes the state registration law compliance requirement that forms the basis of the licensing board's jurisdiction over Engineer B.
  • Mandatory Competitor Misconduct Reporting Obligation Applied to Engineer A
    Engineer B's alleged serious violation of state board rules is a violation of this provision, triggering Engineer A's reporting obligation.
Role (2)
  • Engineer A BER 89-7 Confidentiality-Bound Building Sale Engineer
    Engineer A must conform with state registration laws when conducting the building inspection and handling discovered violations.
  • Engineer B Licensee Subject to Professional Conduct Complaint
    Engineer B is alleged to have violated state board rules of professional conduct, directly implicating the duty to conform with state registration laws.
Event (2)
  • Professional Violation Occurs
    This provision requires conformance with state registration laws, making its breach the basis of the professional violation.
  • Violation Becomes Observed
    The violation observed is one of state registration law conformance, which this provision directly mandates.
Resource (3)
  • State Licensing Board Rules of Professional Conduct (Referenced in Case)
    III.8.a requires conforming with state registration laws, directly referencing the regulatory framework administered by the state licensing board.
  • State_Board_Rules_of_Professional_Conduct
    III.8.a mandates conformance with state registration laws, and Engineer B's alleged violation of these rules is the subject of the complaint.
  • NSPE_Code_of_Ethics
    III.8.a is a provision within the NSPE Code of Ethics requiring compliance with state registration laws as part of professional conduct.
Capability (3)
  • Engineer A Jurisdiction Misconduct Reporting Threshold Compliance BER Case
    This provision requires conformance with state registration laws, and Engineer A applied the state board threshold to determine whether a reportable violation occurred.
  • Engineer A Current Case Serious Violation Collegial Pre-Engagement Non-Requirement Recognition
    This provision requires conformance with state registration laws, which Engineer B violated and which triggered Engineer A's reporting obligation.
  • Engineer A BER 89-7 Out-of-Discipline Reporting Duty Activation
    This provision requires conformance with state registration laws, making violations of those laws reportable regardless of the reporting engineer's discipline.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

An engineer's obligation to protect public health and safety is paramount and takes precedence over confidentiality obligations to clients; engineers must report safety violations to appropriate public authorities.

Citation Context:

The Board cited this case to establish the precedent that engineers have a primary obligation to report safety violations to appropriate public authorities, even when confidentiality agreements exist with clients.

Relevant Excerpts
discussion: "In BER Case 89-7 , Engineer A was retained to investigate the structural integrity of a 60-year old occupied apartment building which his client was planning to sell."
discussion: "In ruling that it was unethical for Engineer A not to report the safety violations to the appropriate public authorities, the Board highlighted the engineer's primary obligation to protect the safety, health, property, and welfare of the public."
discussion: "the obligation of the engineer to refrain from revealing confidential information, data, and facts concerning the business affairs of the client without consent of the client is a significant ethical obligation. (However) matters of public health and safety must take precedence."
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 66% Facts Similarity 65% Discussion Similarity 67% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.1, II.1.a, II.1.f, III.1.a Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 32% Discussion Similarity 73% Provision Overlap 57% Outcome Alignment 100% Tag Overlap 60%
Shared provisions: I.1, II.1.a, II.1.f, III.2 Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 53% Discussion Similarity 64% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, II.1.f, III.1.a Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 41% Discussion Similarity 69% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.2 Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 35% Discussion Similarity 61% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.1, II.1.a, II.1.f Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 51% Discussion Similarity 55% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1.a, II.1.f Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 46% Discussion Similarity 73% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1.a, II.1.f, III.2 Same outcome True View Synthesis
Component Similarity 61% Facts Similarity 67% Discussion Similarity 67% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, III.2 Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 52% Discussion Similarity 44% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.1.a Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 51% Discussion Similarity 58% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1.a Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Was it ethical for Engineer A to submit an anonymous letter to the state engineering licensure board?

Board conclusion It was ethical for Engineer A to submit an anonymous letter to the state engineering licensure board as long as the state engineering licensure board has a procedure for accepting anonymous complaints.
Implicit (4)

Should Engineer A have attempted to contact Engineer B directly before filing a complaint with the state licensure board, and does the seriousness of the alleged violation affect that obligation?

AnalyticalEngineer A was not ethically required to contact Engineer B directly before filing a complaint with the state licensure board. When an engineer observes what he believes is a serious violation of the state board's rules of professional conduct, the gravity of that violation activates the reporting obligation under Code Section II.1.f immediately and independently. Requiring collegial pre-reporting engagement as a precondition to formal complaint would undermine the independence and integrity of the licensure board's disciplinary process, potentially allow the violating engineer to conceal or correct evidence, and place an undue burden on the reporting engineer that the Code does not impose. The seriousness of the alleged violation reinforces rather than relaxes this conclusion: the more serious the violation, the stronger the case for proceeding directly to the appropriate authority rather than attempting informal resolution first.
AnalyticalThe Board's conclusion leaves unaddressed whether Engineer A was obligated to attempt collegial pre-reporting engagement with Engineer B before filing the complaint. Given that the alleged violation is described as serious, the better-reasoned position is that no such prior direct engagement was ethically required. Requiring an engineer to confront the alleged violator before reporting would risk alerting the subject, potentially enabling concealment of evidence, and would inappropriately shift the burden of professional discipline from the licensure board - the institution designed to adjudicate such matters - to the individual reporter. Furthermore, the seriousness of the violation is a material factor: minor or ambiguous infractions might warrant collegial inquiry first, but a serious violation of the state board's rules of professional conduct triggers the reporting obligation directly and without a prerequisite of peer confrontation. The Board should have stated explicitly that the collegial pre-reporting engagement principle does not apply as a precondition when the alleged violation is serious, thereby clarifying the scope of the self-policing duty for future cases.

Does the anonymous nature of the complaint expose Engineer A to any risk of violating the prohibition against maliciously or falsely injuring another engineer's professional reputation, given that Engineer B cannot identify or confront the accuser?

AnalyticalThe anonymous nature of Engineer A's complaint creates a meaningful tension with Code Section III.7, which prohibits maliciously or falsely injuring another engineer's professional reputation. However, this tension does not render anonymous filing per se unethical. The prohibition in III.7 targets malicious or false injury, not the mere concealment of identity. Because Engineer A is a disinterested party with no competitive or personal stake in Engineer B's professional standing, the risk that the complaint is motivated by malice or fabrication is materially reduced. Engineer B's inability to identify or confront the accuser is a procedural fairness concern that the licensure board must manage through its own investigative procedures, but it does not transform a good-faith anonymous report into a violation of III.7. The ethical risk under III.7 would be substantially elevated if Engineer A were a competitor or had a personal grievance, because in those circumstances the anonymous format would shield a potentially malicious actor from accountability.

What threshold of certainty must Engineer A have about the alleged violation before filing a complaint, and does filing based on mere belief rather than confirmed knowledge satisfy the ethical reporting obligation under the Code?

AnalyticalEngineer A's reporting obligation under Code Section II.1.f is triggered by 'knowledge of any alleged violation,' which the Code's own language frames in terms of belief and allegation rather than confirmed or adjudicated fact. Filing a complaint based on a sincere, good-faith belief that a serious violation occurred therefore satisfies the ethical threshold for reporting. Engineer A is not required to conduct an independent investigation sufficient to prove the violation before submitting a complaint; that investigative function belongs to the licensure board. The ethical obligation is to report credible, sincerely held observations to the appropriate authority, not to serve as a pre-adjudicator. However, Engineer A must be able to represent that the complaint is grounded in genuine observation rather than speculation, rumor, or inference unsupported by direct knowledge, because a complaint lacking any factual foundation would risk crossing into the territory prohibited by Section III.7.

Does the fact that Engineer A is neither a competitor nor a personal acquaintance of Engineer B strengthen the ethical legitimacy of the complaint, and should the Board treat disinterested reporters differently from those with a potential personal or competitive stake?

AnalyticalBeyond the Board's finding that anonymous filing is permissible when the board has an established procedure for it, the ethical legitimacy of Engineer A's complaint is further reinforced by the disinterested nature of the reporting. Because Engineer A is neither a competitor nor a personal acquaintance of Engineer B, the complaint cannot plausibly be attributed to competitive self-interest, personal animus, or professional rivalry. This disinterested posture substantially reduces the risk that the anonymous filing constitutes a malicious or false attempt to injure Engineer B's professional reputation in violation of the Code's prohibition on such conduct. The absence of a personal or competitive stake functions as an implicit safeguard against the abuse of anonymous reporting mechanisms, and the Board's analysis would have been more complete had it explicitly recognized that the reporter's motivation is a relevant factor in assessing whether anonymity crosses from permissible reporting into ethically impermissible reputational harm.
AnalyticalEngineer A's status as a disinterested party - neither a competitor nor a personal acquaintance of Engineer B - strengthens the ethical legitimacy of the complaint by eliminating the most common sources of improper motivation. The Board should recognize that disinterested reporters occupy a particularly credible position in the profession's self-policing framework: their reports are more likely to reflect genuine concern for professional standards and public welfare rather than competitive advantage or personal animus. This does not mean that interested parties are categorically barred from reporting - the Code's reporting obligation applies to all engineers with knowledge of violations - but the Board may reasonably give greater initial credibility to complaints from disinterested sources and should scrutinize complaints from competitors or personal adversaries more carefully for signs of improper motivation before proceeding to formal investigation.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the principle of accused engineer procedural fairness conflict with the principle of anonymous reporting permissibility, and if so, how should a licensing board weigh Engineer B's right to confront an accuser against Engineer A's interest in reporting without fear of retaliation?

AnalyticalThe Board's conclusion implicitly resolves, without explicitly addressing, the tension between Engineer B's procedural fairness interest in knowing the identity of the accuser and Engineer A's interest in reporting without fear of retaliation. The resolution embedded in the Board's reasoning is that Engineer B's procedural fairness interest is adequately protected by the licensure board's own investigative procedures - including its obligation to assess the credibility and sufficiency of the complaint before taking adverse action - rather than by requiring the complainant to identify themselves. This is a defensible resolution because the licensure board, not the complainant, is the adjudicative institution, and it is the board's procedural safeguards that protect Engineer B from unfounded accusations. However, the Board should have made explicit that the ethical permissibility of anonymous filing is contingent not only on the existence of a board procedure for accepting such complaints, but also on the board having adequate investigative safeguards to protect the accused from action based solely on an unverifiable anonymous allegation. Without such safeguards, anonymous filing could become an instrument of professional harm rather than a mechanism of legitimate self-policing.
AnalyticalThe tension between Engineer B's procedural fairness interest in knowing the identity of the accuser and Engineer A's interest in reporting without fear of retaliation is real but resolvable. Engineer B's procedural fairness interest is a legitimate concern that the licensure board must address through its own investigative framework - for example, by requiring corroborating evidence before proceeding to formal charges, or by declining to act on anonymous complaints that lack sufficient factual specificity. However, this interest does not override Engineer A's ethical permission to file anonymously where the board has established procedures for accepting such complaints. The licensing board, not Engineer A, bears the institutional responsibility for ensuring that Engineer B receives due process. Engineer A's ethical obligation is to report; the board's obligation is to adjudicate fairly. Conflating these two responsibilities would effectively nullify the anonymous reporting mechanism that the board itself has chosen to make available.
AnalyticalThe tension between Engineer B's procedural fairness interest in knowing the identity of their accuser and Engineer A's interest in reporting without fear of retaliation was not fully resolved by the Board - it was instead deferred to the institutional design of the state licensure board. By conditioning ethical permissibility on whether the board has an established procedure for anonymous complaints, the Board implicitly delegated the fairness balancing function to the regulatory body: if the board accepts anonymous complaints, it has presumably built procedural safeguards - such as independent investigation - that protect Engineer B's due process interests without requiring accuser identification. This teaches that principle tensions between reporter protection and accused fairness need not be resolved at the individual engineer's level when a competent institutional framework absorbs and mediates that conflict.

Does the mandatory misconduct reporting obligation conflict with the signed complaint policy preference when Engineer A fears professional retaliation, and can the ethical duty to report ever be fully satisfied by an anonymous submission that may weaken the evidentiary value of the complaint?

AnalyticalThe mandatory reporting obligation under Code Section II.1.f can be ethically satisfied by an anonymous submission where the board has procedures for accepting such complaints, even though a signed complaint would be preferable and would strengthen the board's investigative capacity. The ethical duty to report is a floor, not a ceiling: it requires that the engineer bring the alleged violation to the attention of the appropriate authority, but it does not specify the form that report must take. An anonymous complaint that reaches the appropriate authority and provides sufficient factual detail to enable investigation fulfills the minimum ethical requirement. The preference for signed complaints is a policy preference grounded in evidentiary and procedural considerations, not an independent ethical mandate. However, Engineer A should understand that choosing anonymity may reduce the likelihood of a successful disciplinary outcome, and that a signed complaint would more fully honor the spirit of the self-policing obligation even if anonymity satisfies its letter.
AnalyticalThe Board's conclusion that anonymous filing is ethically permissible when board procedure allows it does not fully resolve the tension between that permissibility and the policy preference for signed complaints. The Board implicitly acknowledged that a signed complaint is preferable because it strengthens the evidentiary value of the complaint and supports the licensure board's investigative capacity. This means that while Engineer A satisfied the minimum ethical threshold by filing anonymously, Engineer A did not necessarily fulfill the most ethically robust version of the reporting obligation. The ethical duty to report under the Code is best understood as existing on a spectrum: silence constitutes a clear violation, anonymous filing satisfies the minimum obligation, and a signed complaint represents the fullest discharge of the duty. Engineer A's choice of anonymity is therefore ethically adequate but not ethically optimal, and the Board should have made this gradation explicit rather than treating permissibility as equivalent to full compliance with the spirit of the reporting obligation.
AnalyticalThe tension between the mandatory misconduct reporting obligation and the signed complaint policy preference was resolved in favor of permitting anonymous filing, but only conditionally: the Board treated anonymity as an ethically adequate minimum rather than an ethically ideal choice. The reporting duty is non-negotiable - engineers with knowledge of violations must report - but the form of that report may be shaped by legitimate concerns such as fear of retaliation, provided the receiving board has a procedure that can act on anonymous submissions. This resolution teaches that the profession distinguishes between the threshold duty to report (absolute) and the manner of reporting (contextually flexible), and that procedural permissibility at the board level is the operative constraint that converts an otherwise suboptimal choice into an ethically sufficient one.

Does the engineering self-policing obligation conflict with the collegial pre-reporting engagement principle, and does requiring engineers to first confront a peer before reporting undermine the integrity and independence of the licensure board's disciplinary process?

AnalyticalThe interaction between the disinterested professional duty to report and the collegial pre-reporting engagement principle reveals a hierarchy in which the seriousness of the alleged violation determines whether peer-to-peer engagement is ethically required before escalating to a licensure board. The Board's analysis - consistent with the BER 89-7 precedent - treats a serious rules-of-professional-conduct violation as sufficient to activate the reporting obligation directly, bypassing any collegial confrontation requirement. This prioritization reflects a deeper principle: the integrity and independence of the licensure board's disciplinary process would be undermined if engineers were routinely expected to negotiate or warn peers before reporting, since doing so could compromise evidence, allow remediation that obscures the violation, or create social pressure that suppresses legitimate complaints. The disinterested nature of Engineer A's motivation further reinforces this hierarchy, as it eliminates the concern that bypassing collegial engagement serves competitive or personal ends rather than professional self-policing.

Does the disinterested professional duty to report conflict with the public welfare paramount principle when the alleged violation does not directly implicate public safety, raising the question of whether Engineer A's reporting obligation is equally strong for procedural or administrative violations as it is for violations that endanger the public?

AnalyticalThe Board's analysis, read in light of the BER 89-7 precedent, implies that the strength of the reporting obligation scales with the severity of the harm implicated by the alleged violation. In BER 89-7, the public safety dimension elevated the reporting duty to the point where confidentiality agreements could not suppress it. In the present case, the alleged violation involves the state board's rules of professional conduct rather than an immediate public safety threat, yet the Board still found reporting ethically appropriate. This suggests that the Code's reporting obligation under Section II.1.f is not limited to safety-critical violations but extends to any serious breach of professional conduct rules, reflecting the engineering profession's foundational interest in self-policing and maintaining public trust in licensure. However, the absence of a direct public safety nexus in the present case means that the urgency and mandatory character of the reporting duty, while still present, is somewhat less absolute than it would be in a BER 89-7-type scenario. Anonymous filing, which might be insufficient in an acute public safety emergency requiring immediate and credible action, is more defensible in the present context where the harm is professional and institutional rather than physical and immediate.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill a categorical duty to report Engineer B's alleged violation, independent of whether the complaint was signed or anonymous, given that the NSPE Code of Ethics imposes an affirmative obligation on engineers with knowledge of violations to report them to appropriate authorities?

AnalyticalFrom a deontological perspective, Engineer A fulfilled a categorical duty under the NSPE Code of Ethics by reporting the alleged violation to the appropriate authority, regardless of whether the complaint was signed or anonymous. Code Section II.1.f imposes an affirmative obligation on engineers with knowledge of alleged violations to report them, and this obligation is not conditioned on the form of the report. The duty is categorical in the sense that it applies independently of consequences: Engineer A was obligated to report whether or not the complaint would lead to disciplinary action, and whether or not Engineer A's identity was disclosed. The choice of anonymity does not negate the fulfillment of this duty, though a competing deontological consideration - Engineer B's right to procedural fairness - creates a secondary tension. On balance, the duty to report to the appropriate authority takes precedence, and the procedural fairness obligation is discharged by the board's institutional processes rather than by Engineer A's personal disclosure of identity.

From a deontological perspective, does Engineer B's right to know the identity of their accuser - as a matter of procedural fairness - create a competing duty that constrains Engineer A's otherwise permissible choice to file anonymously, and if so, how should those duties be ranked?

From a consequentialist perspective, does the weakening effect of an anonymous complaint on the licensure board's investigative capacity - reducing the likelihood of a successful disciplinary outcome - outweigh the benefit of encouraging reluctant reporters to come forward, such that anonymous reporting produces worse aggregate outcomes for the profession and the public than a signed complaint would?

AnalyticalFrom a consequentialist perspective, the aggregate outcome of permitting anonymous complaints is likely superior to a regime that requires signed complaints as a condition of ethical compliance. A signed-only requirement would deter a significant number of good-faith reporters who fear professional retaliation, resulting in fewer complaints reaching the licensure board and a weaker self-policing mechanism overall. The reduction in investigative strength caused by any individual anonymous complaint is a real but bounded cost, whereas the chilling effect of a signed-only requirement would systematically suppress reporting across the entire profession. The net effect of anonymous reporting permissibility is therefore likely positive for both the profession and the public, even accounting for the evidentiary limitations of anonymous submissions. This consequentialist analysis supports the Board's conclusion that anonymous filing is ethically permissible where the board has established procedures for it.

From a virtue ethics perspective, does choosing to file anonymously rather than signing the complaint reflect a deficit in professional courage - a virtue central to engineering integrity - even when anonymity is procedurally permissible, and does Engineer A's disinterested motivation partially redeem or fully offset that deficit?

AnalyticalFrom a virtue ethics perspective, the Board's conclusion that anonymous filing is ethically permissible does not fully reckon with the question of whether it reflects the highest expression of professional character. Professional courage - the willingness to stand behind one's convictions and accept accountability for one's accusations - is a virtue central to engineering integrity. An engineer who files anonymously avoids the personal risk of retaliation but also avoids the reciprocal accountability that a signed complaint would impose: namely, the obligation to substantiate the claim and to be answerable if the complaint proves unfounded or malicious. Engineer A's disinterested motivation partially offsets this deficit in professional courage, because the absence of competitive or personal animus suggests the complaint is genuine rather than strategic. Nevertheless, the Board's conclusion should be understood as establishing a floor of ethical permissibility, not a ceiling of ethical excellence. Engineers who can sign their complaints without genuine risk of disproportionate retaliation should be understood to have a stronger ethical reason to do so, even when anonymity is procedurally available.
AnalyticalFrom a virtue ethics perspective, Engineer A's choice to file anonymously rather than sign the complaint reflects a partial deficit in professional courage, which is a virtue central to engineering integrity. A fully courageous engineer would stand behind a good-faith complaint with their professional identity, accepting the risk of retaliation as a cost of upholding professional standards. However, Engineer A's disinterested motivation - filing without competitive or personal advantage - substantially mitigates this deficit. The virtue of integrity is expressed not only through the form of the complaint but through the decision to report at all, particularly when Engineer A had no obligation arising from personal relationship or competitive interest. The anonymous filing is therefore ethically permissible but not fully virtuous; it represents the minimum expression of professional courage rather than its fullest realization. Engineer A's disinterested motivation partially redeems but does not fully offset the courage deficit inherent in anonymous filing.
Counterfactual (4)

If Engineer A had first approached Engineer B directly to discuss the alleged violation before filing any complaint, would that collegial pre-reporting engagement have been ethically required, ethically preferable, or ethically neutral - and would it have changed the Board's conclusion about the permissibility of the anonymous filing?

If Engineer A had been a direct competitor of Engineer B, would the Board's analysis of the reporting obligation have changed materially - specifically, would competitive motivation have rendered the anonymous complaint ethically impermissible even if the underlying violation was genuine?

AnalyticalIf Engineer A had been a direct competitor of Engineer B, the Board's analysis of the reporting obligation would not change in its conclusion that a genuine violation must be reported, but it would require substantially greater scrutiny of Engineer A's motivation and the factual basis of the complaint. Competitive motivation does not categorically render a complaint impermissible - a competitor who genuinely observes a violation is still subject to the reporting obligation under Code Section II.1.f - but it raises the risk that the complaint is motivated by competitive advantage rather than professional integrity, which would implicate Code Section III.7's prohibition on maliciously injuring another engineer's professional reputation. In a competitive context, the anonymous format would be particularly problematic because it would shield a potentially self-interested actor from accountability while exposing Engineer B to reputational harm. The Board should therefore treat complaints from competitors with heightened scrutiny and may reasonably require additional corroboration before proceeding to formal investigation.

If the state licensure board had no established procedure for accepting anonymous complaints, would Engineer A have been ethically obligated to file a signed complaint rather than simply declining to report - and would silence in that scenario itself constitute an ethical violation?

AnalyticalIf the state licensure board had no established procedure for accepting anonymous complaints, Engineer A would face a more demanding ethical situation but would not be ethically permitted to remain silent. Code Section II.1.f imposes an affirmative reporting obligation that does not contain an exception for personal discomfort or fear of retaliation. In the absence of an anonymous complaint procedure, Engineer A would be ethically obligated to file a signed complaint, because the alternative - silence - would constitute a failure to fulfill the mandatory reporting duty. Silence in that scenario would itself be an ethical violation, not a neutral choice. The availability of anonymous procedures is what makes anonymous filing ethically permissible; the absence of such procedures does not eliminate the reporting obligation but rather removes the anonymous option, leaving signed filing as the only ethically compliant path.

Drawing on the BER 89-7 precedent, if Engineer A's observation of Engineer B's violation had also implicated an immediate public safety risk - rather than a rules-of-professional-conduct violation alone - would the ethical calculus have shifted to require a signed, urgent report, making anonymous filing insufficient regardless of board procedure?

AnalyticalDrawing on the BER 89-7 precedent, if Engineer A's observation had also implicated an immediate public safety risk rather than a rules-of-professional-conduct violation alone, the ethical calculus would shift significantly toward requiring a more urgent and substantive report. BER 89-7 established that public safety obligations can override confidentiality commitments and that a brief or passing mention of a safety concern is insufficient - the engineer must take affirmative, effective action to protect the public. By analogy, where an immediate public safety risk is present, anonymous filing may be insufficient not because anonymity is categorically impermissible but because the urgency and gravity of the situation demand a report that enables the board to act quickly and effectively. An anonymous complaint that delays or weakens the board's response to an imminent safety threat would fail to satisfy the paramount obligation under Code Section II.1, even if it technically satisfies the minimum reporting requirement under II.1.f. In such circumstances, a signed, urgent, and detailed report would be ethically required.
Decisions & Arguments (5)
View Extraction

Is Engineer A ethically obligated to report Engineer B's apparent serious violation to the state licensing board, and does the absence of a personal or competitive relationship with Engineer B affect that obligation?

Options considered:
File a complaint with the state engineering licensure board regarding Engineer B's apparent serious violation of professional conduct rules, acting on the foundational self-policing duty that applies to every licensed engineer regardless of personal or competitive relationship with the alleged violator.
Decline to report the violation on the grounds that Engineer A has no personal acquaintance with Engineer B and therefore no standing or sufficient basis to initiate a formal complaint, treating the reporting duty as contingent on personal relationship.
Attempt to contact Engineer B directly to discuss the apparent violation before filing any formal complaint with the licensing board, applying the collegial pre-reporting engagement norm regardless of the seriousness of the alleged violation.
Self-Policing Profession Peer Misconduct Reporting Foundational Duty Obligation

Should Engineer A file the complaint against Engineer B as a signed, identified complaint or as an anonymous complaint, and does the choice between these forms affect the ethical adequacy of the reporting act?

Options considered:
Submit the complaint to the state licensing board with Engineer A's full name and contact information, enabling the board to call upon Engineer A for testimony and follow-up, satisfying fundamental fairness norms regarding Engineer B's right to know the accuser's identity, and demonstrating the professional courage that the self-policing character of engineering demands.
Submit the complaint without identifying information, relying on the board's established procedure for accepting anonymous complaints, satisfying the minimum ethical reporting obligation while accepting the practical limitation that the absence of an identified complainant may weaken the board's investigative and prosecutorial capacity.
Decline to file any complaint, signed or anonymous, because Engineer A's concerns about retaliation make identified filing feel too risky and anonymous filing feels professionally inadequate, effectively allowing the apparent serious violation to go unreported.
Anonymous Complaint Permissibility With Signed Complaint Preference Obligation

In choosing to file anonymously, is Engineer A obligated to recognize and weigh the case-weakening limitation of anonymous complaints, and does that limitation create a residual duty to reconsider signing the complaint?

Options considered:
Recognize that the anonymous complaint may limit the board's investigative capacity, weigh that limitation against the concerns about retaliation and competitive perception, and proceed with anonymous filing as the ethically permissible minimum, accepting the tradeoff as a conscious professional judgment rather than an oversight.
Upon fully reckoning with the case-weakening limitation of anonymous filing and its impact on Engineer B's procedural fairness interests and the board's enforcement capacity, decide to step forward publicly with a signed complaint, acting on the policy preference for identified reporting and demonstrating the professional courage that the self-policing profession demands.
Submit the anonymous complaint without consciously considering how the absence of an identified complainant affects the board's ability to investigate and prosecute, treating anonymous filing as fully equivalent to signed filing in terms of professional responsibility discharge.
Anonymous Complaint Case-Weakening Limitation Acknowledgment Obligation

Is Engineer A obligated to report out-of-discipline safety code violations to public authorities notwithstanding a client confidentiality agreement, and does a brief mention of those violations in a confidential client report satisfy the public safety reporting duty?

Options considered:
Notify the appropriate regulatory or enforcement authority, not merely the client, of the electrical and mechanical code violations that could cause injury to building occupants, recognizing that the paramount obligation to protect public health and safety supersedes the contractual confidentiality agreement and is not limited to Engineer A's structural engineering specialty.
Include a brief reference to the electrical and mechanical code violations in the confidential structural report delivered to the client, treating this mention as sufficient discharge of the safety reporting obligation without separately notifying public authorities who have enforcement jurisdiction over the hazards.
Decline to report the out-of-discipline code violations to any party beyond the client, on the grounds that the confidentiality agreement bars disclosure and that the violations fall outside Engineer A's structural engineering specialty, treating the contractual obligation as superseding the public safety reporting duty.
Out-of-Discipline Safety Code Violation Public Authority Reporting Obligation

What threshold of certainty must Engineer A have before filing a complaint, and does filing based on good-faith belief rather than confirmed knowledge satisfy the ethical reporting obligation while avoiding the prohibition against malicious or false injury to another engineer's reputation?

Options considered:
Submit the complaint to the licensing board on the basis of Engineer A's sincere, good-faith belief that a serious violation has occurred, without waiting for independent verification of every element of the alleged misconduct, recognizing that the board's investigative process, not the complainant, is the appropriate mechanism for determining whether a violation actually occurred.
Withhold the complaint until Engineer A has independently confirmed, through additional investigation or evidence gathering, that Engineer B's conduct actually constitutes a violation of the state board's rules of professional conduct, treating verified knowledge rather than good-faith belief as the minimum threshold for ethical reporting.
Refrain from filing any complaint because Engineer A cannot be certain the conduct constitutes a violation, and because filing a complaint that turns out to be unfounded could constitute the kind of malicious or false injury to Engineer B's professional reputation that the NSPE Code prohibits, treating the risk of being wrong as a bar to reporting.
Disinterested Non-Competitive Peer Misconduct Reporting Obligation
Event Timeline (10)
10 sequenced 4 actions 6 events
Case timeline
In the referenced precedent case (BER Case 89-7), Engineer A chose not to report known electrical and mechanical safety deficiencies to any third-party public authority, instead honoring client confidentiality by limiting disclosure to a brief mention in his structural report. This action was ruled unethical by the Board.
Fulfills (2)
  • Contractual and professional duty of client confidentiality (honored in the short term)
  • Duty to inform the client of the safety concern (Engineer A did notify the client)
Violates (3)
  • Paramount duty to protect public health, safety, and welfare (NSPE Code Section I.1)
  • Obligation to report safety violations to appropriate public authorities when public health and safety are at risk
  • Duty to hold public safety as superseding confidentiality obligations in cases of imminent risk to third parties
In the referenced prior case (BER Case 89-7), the engineer's failure to report safety violations results in the continuation of unsafe conditions, allowing potential or actual harm to occur that proper reporting might have prevented. This outcome illustrates the real-world consequences of non-reporting.
Engineer B commits what appears to be a serious professional conduct violation, creating an observable breach of engineering ethical or practice standards. This occurrence is independent of Engineer A's awareness and precedes any reporting obligation.
Engineer A observes Engineer B's professional conduct violation, transforming a latent ethical situation into an active one that directly implicates Engineer A's own professional obligations. This observation is the triggering event for the entire ethical dilemma.
Engineer A witnesses what he believes is a serious violation of the state board's rules of professional conduct by Engineer B and makes a conscious judgment that the conduct warrants action. This assessment initiates the chain of volitional decisions that follow.
Fulfills (2)
  • Duty of vigilance over professional standards in the engineering community
  • NSPE Code obligation to be aware of and respond to unprofessional conduct
As an automatic consequence of Engineer A's observation and assessment of a serious violation, Engineer A's professional reporting obligation under engineering ethics codes becomes fully active and enforceable. This is not a decision but a status change triggered by the combination of knowledge and professional licensure.
Engineer A makes the volitional decision to submit a formal complaint to the state engineering licensure board against Engineer B rather than remaining silent or pursuing informal channels. This decision reflects the exercise of the engineer's self-policing obligation.
Fulfills (4)
  • NSPE Code of Ethics obligation to report violations of professional conduct rules to appropriate authorities
  • Duty to cooperate with the state licensure board
  • Paramount duty to protect public health, safety, and welfare
  • Self-policing obligation of the licensed engineering profession
Engineer A chooses to submit the complaint to the state engineering licensure board without identifying himself, opting for anonymity rather than attaching his name as the complainant. This is a distinct volitional decision layered on top of the decision to file.
Fulfills (2)
  • Partial fulfillment of the duty to report (complaint is filed, bringing the matter to the board's attention)
  • Duty to act rather than remain silent, even if imperfectly
Violates (3)
  • Policy-level obligation to stand publicly behind ethical concerns and cooperate fully with the board
  • Implicit obligation of fairness to Engineer B, the accused's interest in knowing his accuser
  • Obligation to provide the strongest possible basis for the board's investigation and enforcement action
The state engineering licensure board receives Engineer A's complaint against Engineer B without identifying information, creating a procedural and investigative situation where the board must evaluate an allegation without a named complainant. This is an outcome of Engineer A's submission action.
The Board of Ethical Review's analysis concludes that anonymous reporting, while not ideal, is ethically permissible, establishing a normative outcome that defines the ethical status of Engineer A's conduct and creates guidance for future cases. This is an outcome of the BER's deliberative process.
Narrative (2 main characters)
View Extraction
Opening Context

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

You are Engineer A, a licensed professional engineer who has observed what you believe is a serious violation of the state board's rules of professional conduct by Engineer B. You have no personal relationship with Engineer B and no competitive interest in the outcome of any complaint. Your state's licensure board maintains a process for receiving complaints about engineer misconduct, and its rules of professional conduct address the obligations of engineers who witness such violations. You must now determine how to respond to what you have observed, including whether to report, in what form to report, and what standard of certainty your observations must meet before you act.

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.

Engineer A Roles in this case: BER 89-7 Confidentiality-Bound Building Sale EngineerAnonymous Professional Conduct Complaint Filer

Guided by: Professional Accountability, Engineering Self-Policing Obligation, Signed Complaint Preference Over Anonymous Reporting Principle

Engineer A is bound by a confidentiality agreement with the building sale client, yet discovers a safety code violation committed by Engineer B. The obligation asserts that confidentiality cannot excuse non-reporting of known safety violations to public authorities, while the constraint acknowledges that the client's reasonable reliance on confidentiality modulates how and to what degree Engineer A can act on that information. This creates a genuine dilemma: honoring the client relationship and contractual trust conflicts directly with the duty to protect public safety, and Engineer A cannot fully satisfy both simultaneously. The tension is especially acute because the client's interests (a smooth building sale) are directly harmed by disclosure.

Attaches to role: BER 89-7 Confidentiality-Bound Building Sale Engineer

Engineer A may be tempted to satisfy reporting duties by briefly mentioning the safety code violation within a professional report rather than making a direct, explicit notification to public authorities. The obligation establishes that such a brief mention is insufficient to discharge the duty to notify public authorities of a safety violation. However, the confidentiality constraint limits how far Engineer A can go in disclosing client-related information. This tension forces Engineer A to choose between a minimalist disclosure that respects confidentiality but fails the public safety standard, and a robust disclosure that meets the safety notification standard but potentially breaches client trust and contractual obligations.

Attaches to role: BER 89-7 Confidentiality-Bound Building Sale Engineer

Engineer A is permitted to file an anonymous complaint against Engineer B, yet Engineer B's due process interest in knowing the identity of their accuser creates a fairness constraint on that anonymity. The obligation acknowledges anonymous filing as ethically permissible while preferring signed complaints; the constraint recognizes that Engineer B, as the licensee subject to complaint, has a legitimate fairness interest in confronting their accuser. Filing anonymously satisfies Engineer A's self-protective interest and still triggers accountability, but it weakens the case and may deny Engineer B a fair hearing. These two pull in opposite directions: maximizing Engineer A's willingness to report versus maximizing procedural fairness for Engineer B.

Attaches to role: Anonymous Professional Conduct Complaint Filer
Engineer B Roles in this case: Licensee Subject to Professional Conduct Complaint

Engineer A is permitted to file an anonymous complaint against Engineer B, yet Engineer B's due process interest in knowing the identity of their accuser creates a fairness constraint on that anonymity. The obligation acknowledges anonymous filing as ethically permissible while preferring signed complaints; the constraint recognizes that Engineer B, as the licensee subject to complaint, has a legitimate fairness interest in confronting their accuser. Filing anonymously satisfies Engineer A's self-protective interest and still triggers accountability, but it weakens the case and may deny Engineer B a fair hearing. These two pull in opposite directions: maximizing Engineer A's willingness to report versus maximizing procedural fairness for Engineer B.

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

Engineer A is bound by a confidentiality agreement with the building sale client, yet discovers a safety code violation committed by Engineer B. The obligation asserts that confidentiality cannot excuse non-reporting of known safety violations to public authorities, while the constraint acknowledges that the client's reasonable reliance on confidentiality modulates how and to what degree Engineer A can act on that information. This creates a genuine dilemma: honoring the client relationship and contractual trust conflicts directly with the duty to protect public safety, and Engineer A cannot fully satisfy both simultaneously. The tension is especially acute because the client's interests (a smooth building sale) are directly harmed by disclosure.

Engineer A may be tempted to satisfy reporting duties by briefly mentioning the safety code violation within a professional report rather than making a direct, explicit notification to public authorities. The obligation establishes that such a brief mention is insufficient to discharge the duty to notify public authorities of a safety violation. However, the confidentiality constraint limits how far Engineer A can go in disclosing client-related information. This tension forces Engineer A to choose between a minimalist disclosure that respects confidentiality but fails the public safety standard, and a robust disclosure that meets the safety notification standard but potentially breaches client trust and contractual obligations.

Opening States (10)
Non-Competitor Peer Conduct Reporting Obligation State Anonymous Complainant Identity Concealment Fairness State Self-Policing Profession Peer Reporting Duty Activation State BER 89-7 Confidentiality Agreement Suppressing Safety Report BER 89-7 Public Safety at Risk from Building Code Violations BER 89-7 Client Confidentiality vs. Public Safety Conflict Present Case Anonymous Reporting Adequacy Engineer A Peer Violation Observation State Engineer A Anonymous Complaint Filing State Present Case Anonymous Complainant Identity Concealment Fairness
Summary
  • Confidentiality agreements with clients cannot ethically override an engineer's affirmative duty to report known safety code violations to public authorities, as public safety constitutes a non-negotiable threshold obligation.
  • Anonymous complaint mechanisms serve a legitimate ethical function by lowering the barrier to reporting, but they introduce procedural fairness costs for the accused that engineers must weigh when deciding how to file.
  • A cursory or embedded mention of a safety violation within a professional report does not satisfy the duty to notify public authorities, which requires direct, explicit, and unambiguous communication to the relevant regulatory body.

© Licensed under the GNU GPL v3 | Report Issue