Step 4: Full View

Entities, provisions, decisions, and narrative

Public Health, Safety and Welfare-Former Employee's Participation in a Public Safety Standards Hearing
Step 4 of 5

313

Entities

6

Provisions

2

Precedents

17

Questions

24

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's internal safety obligation — initially owed to the public through the employer relationship — transfers outward to the governmental hearing authority upon Engineer A's testimony. Company X's rejection of additional testing and Engineer A's subsequent resignation severed the internal agency relationship, and the public safety standards hearing provides the institutional mechanism through which the obligation migrates from the private professional domain to the public regulatory domain. The Board's three conditions (technical competence, objectivity, confidentiality compliance) function as the transfer protocol: they define the terms under which the handoff is ethically valid and the original party is relieved of further unilateral duty.
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
I.1. Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 73)
Obligation
Engineer A Standard Testing Non-Preclusion of Additional Safety Reporting
Holding public safety paramount means standard testing compliance does not preclude additional safety reporting when concerns exist.
Action
Recommend Additional Safety Testing
Recommending additional safety testing directly serves the paramount duty to protect public safety and welfare.
State
Engineer A Residual Safety Concern Post-Testing
Engineer A's professional safety assessment directly implicates the paramount duty to protect public health and welfare.
Obligation (9)
  • Engineer A Standard Testing Non-Preclusion of Additional Safety Reporting
    Holding public safety paramount means standard testing compliance does not preclude additional safety reporting when concerns exist.
  • Engineer A Public Interest Testimony Obligation at Government Hearing
    Participating in a government safety hearing to share safety concerns directly serves the obligation to hold public welfare paramount.
  • Engineer A Current Case Standard Safety Testing Non-Preclusion Additional Concern Reporting
    The obligation to report additional safety concerns beyond standard testing is grounded in the paramount duty to protect public safety.
  • Engineer A Non-Acquiescence After Company X Rejection
    After employer rejection, the duty to hold public safety paramount requires Engineer A to assess whether further action is needed.
  • Engineer A Post-Employment Hearing Participation Consideration
    Participating as a witness at a public safety hearing one year after resignation upholds the paramount duty to public safety.
  • Engineer A Regulatory Gap Escalation Recognition
    The absence of applicable standards heightens the paramount duty to protect the public by escalating safety concerns.
  • Company X Safety Testing Rejection Ethical Violation
    Rejecting additional safety testing solely on cost grounds violates the paramount obligation to protect public safety.
  • Engineer A Current Case Regulatory Gap Heightened Safety Escalation
    The regulatory gap heightens the paramount public safety duty, requiring escalation of safety concerns to appropriate authorities.
  • Engineer A Current Case Employer Cost Rejection Non-Acquiescence Assessment
    The paramount duty to public safety requires Engineer A to assess whether acquiescing to the employer's cost-based rejection is acceptable.
Action (6)
  • Recommend Additional Safety Testing
    Recommending additional safety testing directly serves the paramount duty to protect public safety and welfare.
  • Reject Additional Testing Recommendation
    Rejecting safety testing recommendations potentially endangers the public, conflicting with the duty to hold public safety paramount.
  • Resign From Company X
    Resigning is a response to the company overriding safety concerns, reflecting the engineer's commitment to public safety above employer interests.
  • Consider Testifying at Public Hearing
    Testifying at a public hearing on safety standards is a means of upholding the paramount duty to protect public health and welfare.
  • Report Findings to Regulatory Authority
    Reporting safety findings to a regulatory authority is a direct action to protect public health and welfare.
  • Escalate with External Reporting Threat
    Threatening external reporting is motivated by the duty to ensure public safety is not compromised by the employer's decision.
State (7)
  • Engineer A Residual Safety Concern Post-Testing
    Engineer A's professional safety assessment directly implicates the paramount duty to protect public health and welfare.
  • Public Safety at Risk from Unresolved Consumer Product Concern
    Consumers exposed to unresolved product safety risks are the direct subject of the obligation to hold public safety paramount.
  • Company X Cost-Driven Rejection of Additional Safety Testing
    Company X's rejection of safety testing creates a condition that conflicts with the paramount duty to protect public welfare.
  • BER 76-4 Public Safety at Risk from Environmental Discharge
    Environmental discharge threatening water quality directly implicates the duty to hold public health and welfare paramount.
  • BER 08-10 Infant Respirator Confirmed Safety Concern Without Imminent Incident
    A confirmed safety concern with an infant respirator directly engages the paramount duty to protect public safety.
  • Present Case Company X Good Faith Safety Concern Without Demonstrable Violation
    Engineer A's good faith safety concerns about the product relate to the overarching duty to prioritize public welfare.
  • Present Case Competing Duties Between Confidentiality and Public Safety Reporting
    The tension between confidentiality and reporting is anchored by the paramount obligation to protect public safety.
Constraint (7)
  • Engineer A Citizen Advocacy Whistleblower Non-Suppression at Hearing
    The paramount public safety obligation underpins why Engineer A's advocacy at the hearing cannot be suppressed by other professional duties.
  • Engineer A Public Safety Paramount Over Confidentiality at Hearing
    I.1 directly establishes the paramount public safety obligation that overrides post-employment confidentiality constraints.
  • Engineer A Non-Acquiescence After Company X Rejection Escalation Constraint
    I.1 creates the duty that prevents Engineer A from simply acquiescing to Company X's rejection of safety testing when public safety is at risk.
  • Engineer A Completed Testing Non-Preclusion of Hearing Participation Constraint
    I.1 establishes that even completed compliant testing does not extinguish Engineer A's paramount obligation to raise residual public safety concerns.
  • Engineer A Good Faith Belief Public Safety Reporting Permissibility Constraint
    I.1 is the foundational provision that permits Engineer A to bring good faith public safety concerns forward.
  • Engineer Doe Post-Termination Public Hearing Reporting Constraint
    I.1 creates the paramount obligation that required Engineer Doe to report findings to the State Pollution Control Authority.
  • Engineer A No Black and White Standard Contextual Calibration Constraint
    I.1 is the paramount provision whose application must be contextually calibrated rather than applied uniformly.
Principle (12)
  • Public Welfare Paramount Invoked By Engineer A Safety Concern Identification
    I.1 directly embodies the paramount public welfare obligation that Engineer A invoked when identifying safety concerns.
  • Public Welfare Paramount Invoked By Engineer A Post-Employment Testimony Consideration
    I.1 grounds Engineer A's post-employment consideration to testify in the public interest.
  • Post-Employment Public Safety Testimony Obligation Invoked By Engineer A
    I.1 is the foundational provision establishing that the public welfare obligation survives resignation.
  • Regulatory Gap Safety Escalation Obligation Invoked In New Product Context
    I.1 supports heightened escalation obligations when no standards exist to protect the public.
  • Non-Acquiescence to Employer Safety Testing Rejection Invoked By Engineer A Resignation
    I.1 underlies Engineer A's refusal to acquiesce when employer rejection endangered public safety.
  • Public Interest Engineering Testimony Obligation Invoked By Engineer A Hearing Participation
    I.1 directly supports Engineer A's obligation to participate in a hearing to protect public welfare.
  • Post-Client-Refusal Escalation Assessment Obligation Invoked By Engineer A After Company X Rejection
    I.1 requires Engineer A to assess further action after employer refusal to protect public safety.
  • Public Welfare Paramount Invoked in Engineer A Current Case Testimony Decision
    I.1 is the direct provision grounding Engineer A's decision to participate in the standards hearing.
  • Regulatory Gap Safety Escalation Obligation Invoked In Current Case
    I.1 supports the principle that regulatory gaps heighten rather than diminish the public welfare obligation.
  • Public Welfare Paramount Invoked BER 76-4 Engineer Doe Pollution Reporting
    I.1 is the provision Engineer Doe invoked when reporting pollution findings to protect public welfare.
  • Good Faith Safety Concern Threshold for External Reporting Invoked Current Case
    I.1 supports the principle that a good-faith safety belief is sufficient to trigger the public welfare reporting obligation.
  • Proactive Risk Disclosure Invoked By Engineer A Safety Recommendation
    I.1 underlies Engineer A's proactive communication of safety concerns to fulfill the paramount public welfare duty.
Role (6)
  • Engineer A Consumer Product Safety Design Engineer
    Engineer A is obligated to hold public safety paramount when identifying and reporting inconsistent product performance safety concerns to their employer.
  • Engineer A Current Case Consumer Product Safety Design Engineer
    Engineer A must prioritize public welfare when raising unique safety concerns about the new consumer product during employment at Company X.
  • Engineer A Post-Employment Public Safety Standards Witness
    Engineer A's consideration of participating in the public safety hearing is directly motivated by the obligation to hold public safety paramount.
  • Engineer A Current Case Post-Employment Public Safety Standards Witness
    Engineer A's participation as a witness at the government safety hearing reflects the duty to hold public health and welfare paramount.
  • Engineer A BER 08-10 MedTech Respirator Safety Engineer
    Engineer A is governed by the obligation to hold public safety paramount when identifying and reporting the dangerous relief valve placement on infant respirators.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    Engineer Doe must hold public welfare paramount when evaluating whether plant discharge meets environmental standards affecting public health.
Event (3)
  • Safety Inconsistency Detected
    The detection of a safety inconsistency directly triggers the paramount duty to protect public safety, health, and welfare.
  • Additional Testing Rejected
    Rejecting additional testing that could address safety concerns conflicts with the duty to hold public safety paramount.
  • Engineer A Faces Testimony Decision
    Deciding whether to testify at a public safety hearing is directly tied to the obligation to protect public safety and welfare.
Resource (7)
  • NSPE_Code_of_Ethics_Primary
    I.1 is the foundational provision of the NSPE Code establishing the paramount duty to public safety that this resource directly cites.
  • NSPE Code of Ethics for Engineers
    I.1 is the core provision of this primary normative authority governing Engineer A's paramount obligation to public health, safety, and welfare.
  • Client Confidentiality vs. Public Safety Balancing Framework
    I.1 establishes the paramount public safety duty that must be weighed against confidentiality obligations in this balancing framework.
  • Client_Confidentiality_vs_Public_Safety_Balancing_Framework_Individual
    I.1 provides the paramount safety obligation that anchors the conditions under which Engineer A may participate in the hearing despite confidentiality concerns.
  • National Product Safety Standards (General)
    I.1 requires holding public safety paramount, directly motivating concern about the regulatory gap this resource identifies.
  • Government Agency Public Safety Standard Hearing
    I.1 grounds Engineer A's potential duty to participate in this formal proceeding to protect public safety.
  • Whistleblower Protection Framework
    I.1 provides the paramount safety duty that normatively justifies Engineer A's public interest disclosure referenced in this framework.
Capability (16)
  • Engineer A BER 08-10 MedTech Employer Rejection Non-Acquiescence
    Holding public safety paramount requires not acquiescing when an employer ignores safety concerns for over a year.
  • Engineer A Regulatory Gap Safety Escalation Recognition
    Recognizing that absent standards do not eliminate the duty to protect public safety directly reflects the paramount safety obligation.
  • Engineer A Standard Testing Non-Preclusion Recognition
    Recognizing that passing standard tests does not preclude further safety obligations upholds the paramount duty to public safety.
  • Engineer A Post-Employment Hearing Participation Capability
    Participating in a public safety standards hearing to address known safety concerns is a direct expression of holding public safety paramount.
  • Engineer A Consumer Product Inconsistent Performance Safety Recognition
    Recognizing inconsistent product performance as a safety concern reflects the obligation to hold public safety paramount.
  • Engineer A Employer Rejection Non-Acquiescence Escalation
    Not acquiescing when an employer rejects safety testing on cost grounds upholds the paramount duty to public safety.
  • Engineer A Public Interest Testimony Obligation Recognition
    Recognizing the obligation to testify about safety concerns at a public hearing directly serves the paramount duty to public safety.
  • Engineer A BER 08-10 Standard Testing Non-Preclusion Recognition
    Recognizing that compliance with existing standards does not preclude further safety action upholds the paramount public safety obligation.
  • Company X Safety Rejection Ethical Violation Recognition
    Company X's failure to recognize the ethical violation of rejecting safety testing on cost grounds conflicts with the paramount duty to public safety.
  • Engineer Doe BER 76-4 Post-Contract Reporting Persistence
    Persisting in reporting safety concerns despite contract termination reflects the paramount obligation to public safety.
  • Engineer A Current Case Regulatory Gap Heightened Escalation Recognition
    Recognizing that a regulatory gap heightens the escalation obligation directly serves the paramount duty to public safety.
  • Engineer A Current Case Standard Testing Non-Preclusion Recognition
    Recognizing that standard testing completion does not end safety obligations upholds the paramount duty to public safety.
  • Engineer A Current Case Consumer Product Inconsistent Performance Safety Recognition
    Recognizing inconsistent performance as a safety issue even after passing tests reflects the paramount obligation to protect the public.
  • Engineer A Current Case Employer Cost Rejection Non-Acquiescence Assessment
    Assessing whether cost-based rejection of safety testing is acceptable directly implicates the paramount duty to public safety.
  • Engineer Doe BER 76-4 Post-Termination Reporting Persistence
    Persisting in safety reporting after termination reflects the paramount obligation to hold public safety above employer interests.
  • BER Multi-Case Synthesis Consumer Product Safety Calibration
    Synthesizing precedent to determine consumer product safety obligations is grounded in the paramount duty to public safety.
II.1.a. If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
How this applies in the case (showing 3 of 49)
Obligation
Engineer A Non-Acquiescence After Company X Rejection
After Company X overruled the recommendation for additional testing, Engineer A was obligated to notify appropriate authorities as this provision requires.
Action
Reject Additional Testing Recommendation
When the employer overrules the safety recommendation, this provision requires the engineer to notify appropriate authorities.
State
Company X Cost-Driven Rejection of Additional Safety Testing
Company X overruling Engineer A's safety recommendation triggers the duty to notify appropriate authorities when life or property may be endangered.
Obligation (7)
  • Engineer A Non-Acquiescence After Company X Rejection
    After Company X overruled the recommendation for additional testing, Engineer A was obligated to notify appropriate authorities as this provision requires.
  • Engineer A Internal Safety Recommendation to Supervisor B
    This provision requires notifying the employer of safety concerns, which aligns with Engineer A's obligation to communicate concerns to Supervisor B.
  • Engineer A Current Case Employer Cost Rejection Non-Acquiescence Assessment
    When the employer rejected additional testing on cost grounds, this provision obligates Engineer A to consider notifying appropriate authorities.
  • Engineer A Regulatory Gap Escalation Recognition
    The absence of standards and potential danger triggers the obligation to notify appropriate authorities beyond the employer.
  • Engineer A Current Case Regulatory Gap Heightened Safety Escalation
    The regulatory gap heightens the obligation under this provision to escalate safety concerns to authorities beyond the employer.
  • Company X Safety Testing Rejection Ethical Violation
    Company X's rejection of additional testing on cost grounds creates the endangerment circumstance triggering Engineer A's notification obligation under this provision.
  • Engineer A MedTech BER 08-10 Premature External Reporting Threat
    This provision requires exhausting internal notification before escalating externally, directly relating to the obligation to avoid premature external reporting threats.
Action (4)
  • Reject Additional Testing Recommendation
    When the employer overrules the safety recommendation, this provision requires the engineer to notify appropriate authorities.
  • Report Findings to Regulatory Authority
    Reporting to a regulatory authority is precisely the action this provision mandates when an engineer's safety judgment is overruled.
  • Escalate with External Reporting Threat
    Threatening to escalate to external authorities aligns with the provision requiring notification of appropriate authorities when safety judgment is overruled.
  • Verbally Report Findings to Client
    Verbally notifying the employer of safety concerns is the initial step required by this provision when judgment is at risk of being overruled.
State (7)
  • Company X Cost-Driven Rejection of Additional Safety Testing
    Company X overruling Engineer A's safety recommendation triggers the duty to notify appropriate authorities when life or property may be endangered.
  • Engineer A Post-Employment Witness Participation Consideration
    Engineer A's consideration of testifying at a public hearing is a form of notifying an appropriate authority after judgment was overruled.
  • BER 76-4 Client-Suppressed Environmental Findings at Public Hearing
    Engineer Doe's situation of suppressed findings at a public hearing parallels the duty to notify appropriate authorities when overruled.
  • BER 08-10 Internal Escalation Pathway Assessment for MedTech Respirator
    Engineer A's escalation options within MedTech after manager non-response reflect the duty to notify appropriate authority when judgment is overruled.
  • Present Case Client Safety Recommendation Rejection by Company X
    Company X's rejection of the safety recommendation triggers the obligation to notify the employer or appropriate authority of the endangerment.
  • Present Case Post-Employment Expert Witness Participation Consideration
    Participating as a witness at a government safety hearing is a means of notifying an appropriate authority after Engineer A's judgment was overruled.
  • Present Case Competing Duties Between Confidentiality and Public Safety Reporting
    The duty to notify appropriate authorities when overruled is central to the tension between confidentiality and public safety reporting.
Constraint (4)
  • Engineer A Non-Acquiescence After Company X Rejection Escalation Constraint
    II.1.a directly establishes that when an engineer's judgment is overruled in ways that endanger safety, they must notify appropriate authorities rather than acquiesce.
  • Engineer A Good Faith Belief Public Safety Reporting Permissibility Constraint
    II.1.a creates the duty to notify appropriate authorities when safety judgments are overruled, grounding the permissibility of Engineer A's reporting.
  • Engineer Doe Post-Termination Public Hearing Reporting Constraint
    II.1.a directly supports Engineer Doe's obligation to report findings to the appropriate authority after his safety concerns were overruled.
  • Engineer A MedTech Premature External Reporting Threat Prohibition
    II.1.a requires exhausting internal escalation before notifying outside authorities, constraining premature external reporting threats.
Principle (6)
  • Non-Acquiescence to Employer Safety Testing Rejection Invoked By Engineer A Resignation
    II.1.a directly applies as Engineer A's resignation was a form of notifying appropriate authority after judgment was overruled on safety grounds.
  • Post-Client-Refusal Escalation Assessment Obligation Invoked By Engineer A After Company X Rejection
    II.1.a requires Engineer A to assess escalation to appropriate authorities after Company X rejected the safety recommendation.
  • Non-Acquiescence to Employer Safety Testing Rejection Invoked BER 08-10 MedTech
    II.1.a directly applies to the MedTech scenario where the engineer escalated after the manager failed to act on a safety defect.
  • Public Welfare Paramount Invoked BER 76-4 Engineer Doe Pollution Reporting
    II.1.a applies as Engineer Doe notified appropriate authority after his professional judgment was overruled by XYZ Corporation.
  • Regulatory Gap Safety Escalation Obligation Invoked In Current Case
    II.1.a supports escalation to appropriate authorities when no standards exist and employer has rejected safety recommendations.
  • Proactive Risk Disclosure Invoked By Engineer A Safety Recommendation
    II.1.a underlies the obligation to notify appropriate parties when safety concerns are identified and judgment may be overruled.
Role (4)
  • Engineer A Consumer Product Safety Design Engineer
    When Company X overruled Engineer A's safety recommendations, Engineer A was obligated to notify appropriate authorities beyond the employer.
  • Engineer A Current Case Consumer Product Safety Design Engineer
    Engineer A's safety judgment being overruled by Company X triggers the duty to notify the employer and other appropriate authorities of the endangerment.
  • Engineer A BER 08-10 MedTech Respirator Safety Engineer
    When MedTech failed to act on the safety concern, Engineer A was obligated to notify appropriate authorities about the dangerous respirator design.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    When XYZ Corporation suppressed Engineer Doe's adverse findings, Engineer Doe was obligated to notify appropriate authorities about the public safety risk.
Event (2)
  • Additional Testing Rejected
    When the engineer's judgment for additional testing was overruled, the provision requires notifying appropriate authorities about the endangerment.
  • Safety Inconsistency Detected
    Upon detecting a safety inconsistency that was not addressed, the engineer is obligated to notify relevant authorities as appropriate.
Resource (6)
  • Engineer_Public_Safety_Escalation_Standard_Individual
    II.1.a directly requires the internal-then-external escalation process this resource governs when safety concerns are overruled.
  • Engineer Public Safety Escalation Standard
    II.1.a mandates escalation to appropriate authorities when safety judgment is overruled, which is the core duty this resource governs.
  • Engineer Safety Recommendation Rejection Standard
    II.1.a governs Engineer A's obligations after Company X rejects the safety recommendation, requiring notification of appropriate authorities.
  • BER_Case_08-10
    II.1.a is the provision underlying the graduated internal escalation framework established as precedent in this case.
  • BER_Case_76-4
    II.1.a supports the obligation to report findings to a public authority when a client suppresses adverse engineering findings, as established in this precedent.
  • Government Agency Public Safety Standard Hearing
    II.1.a identifies the government agency hearing as an appropriate authority to notify when safety judgment is overruled by an employer.
Capability (9)
  • Engineer A BER 08-10 MedTech Employer Rejection Non-Acquiescence
    When MedTech overruled Engineer A's safety judgment, the obligation to notify appropriate authorities was triggered.
  • Engineer A Regulatory Gap Safety Escalation Recognition
    Recognizing that a regulatory gap requires escalation aligns with the duty to notify appropriate authorities when safety judgments are overruled.
  • Engineer A Employer Rejection Non-Acquiescence Escalation
    When Company X rejected additional safety testing, Engineer A's obligation to escalate to appropriate authorities was directly triggered.
  • Engineer A BER 08-10 Internal Escalation Exhaustion Assessment
    Assessing whether internal escalation pathways were exhausted before notifying outside authorities is central to this provision.
  • Engineer A Current Case Regulatory Gap Heightened Escalation Recognition
    Recognizing that absent standards heighten the escalation obligation reflects the duty to notify appropriate authorities when safety is endangered.
  • Engineer A Current Case Employer Cost Rejection Non-Acquiescence Assessment
    Assessing whether to escalate beyond Company X after cost-based rejection of safety testing directly implicates the duty to notify appropriate authorities.
  • Engineer Doe BER 76-4 Post-Contract Reporting Persistence
    Persisting in reporting safety concerns to appropriate authorities despite employer instruction not to reflects this provision's escalation duty.
  • Engineer Doe BER 76-4 Post-Termination Reporting Persistence
    Continuing to report safety concerns after contract termination reflects the obligation to notify appropriate authorities when safety judgments are overruled.
  • Engineer A Faithful Agent Internal Recommendation
    Working within company channels first before escalating reflects the sequential obligation to notify the employer before other authorities.
II.1.b. Engineers shall approve only those engineering documents that are in conformity with applicable standards.
How this applies in the case (showing 3 of 28)
Obligation
Engineer A Standard Testing Non-Preclusion of Additional Safety Reporting
This provision requires approving only conforming documents, implying Engineer A cannot simply approve products meeting only standard testing when additional concerns exist.
Action
Recommend Additional Safety Testing
Recommending additional safety testing reflects the duty to ensure engineering decisions conform to applicable safety standards.
State
Novel Consumer Product Regulatory Standards Vacuum
The absence of applicable safety standards for the new product directly relates to the duty to approve only documents conforming to applicable standards.
Obligation (4)
  • Engineer A Standard Testing Non-Preclusion of Additional Safety Reporting
    This provision requires approving only conforming documents, implying Engineer A cannot simply approve products meeting only standard testing when additional concerns exist.
  • Engineer A Current Case Standard Safety Testing Non-Preclusion Additional Concern Reporting
    Compliance with applicable standards does not preclude additional reporting, consistent with the requirement to approve only conforming engineering documents.
  • Company X Employer Reasonableness Recognition Absent Standards Context
    The absence of applicable national or industry standards is directly relevant to the obligation to approve only documents conforming to applicable standards.
  • Engineer A Regulatory Gap Escalation Recognition
    The lack of national or industry standards for the product is directly relevant to the obligation to approve only documents conforming to applicable standards.
Action (2)
  • Recommend Additional Safety Testing
    Recommending additional safety testing reflects the duty to ensure engineering decisions conform to applicable safety standards.
  • Reject Additional Testing Recommendation
    Rejecting safety testing may result in approving engineering work that does not conform to applicable standards, violating this provision.
State (3)
  • Novel Consumer Product Regulatory Standards Vacuum
    The absence of applicable safety standards for the new product directly relates to the duty to approve only documents conforming to applicable standards.
  • Present Case Regulatory Standards Vacuum for Company X Novel Product
    The lack of governmental or industry safety standards for the product is the core context in which conformity to applicable standards must be assessed.
  • BER 76-4 Confidentiality Instruction Suppressing Safety Report
    Suppressing a safety report conflicts with the duty to ensure engineering documents conform to applicable standards and reporting obligations.
Constraint (2)
  • Company X Absent Standards Employer Reasonableness Non-Violation Constraint
    II.1.b requires conformity with applicable standards, and its absence means Company X cannot be found in violation when no such standards exist.
  • Engineer A Regulatory Standards Vacuum Testimony Framing Constraint
    II.1.b establishes that engineering documents must conform to applicable standards, directly informing why Engineer A cannot frame testimony as violations where no standards exist.
Principle (4)
  • Public Welfare Paramount Invoked By Engineer A Safety Concern Identification
    II.1.b applies because Engineer A's concern that standard safety testing was insufficient relates to conformity with applicable standards.
  • Regulatory Gap Safety Escalation Obligation Invoked In New Product Context
    II.1.b is directly relevant as the absence of applicable standards for the new product creates the regulatory gap at issue.
  • Regulatory Gap Safety Escalation Obligation Invoked In Current Case
    II.1.b applies because the lack of governmental or industry standards for Company X's product is central to the escalation obligation.
  • Employer Reasonableness in Absent-Standards Context Invoked Company X Current Case
    II.1.b is relevant because Company X's decision is evaluated against the backdrop of no applicable standards existing for the product.
Role (4)
  • Engineer A Consumer Product Safety Design Engineer
    Engineer A is governed by the duty to approve only engineering documents conforming to applicable standards when working on the consumer product design.
  • Engineer A Current Case Consumer Product Safety Design Engineer
    Engineer A must ensure that engineering documents related to the new consumer product conform to applicable safety standards during employment.
  • Engineer A BER 08-10 MedTech Respirator Safety Engineer
    Engineer A is obligated to approve only engineering documents for the infant respirator that conform to applicable safety standards.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    Engineer Doe must only approve engineering reports and documents that conform to applicable environmental discharge standards.
Event (1)
  • Safety Inconsistency Detected
    The detected safety inconsistency raises the question of whether engineering documents and standards were in conformity with applicable standards.
Resource (4)
  • Company X Standard Safety Testing Policies and Procedures
    II.1.b requires engineers to approve only documents conforming to applicable standards, directly relevant to whether Engineer A can endorse Company X's completed testing process.
  • National Product Safety Standards (General)
    II.1.b requires conformity with applicable standards, and this resource defines the existing regulatory baseline against which engineering documents must be evaluated.
  • Consumer_Product_Safety_Testing_Standard_Individual
    II.1.b requires conformity with applicable standards, and the absence of developed standards for this product is directly relevant to what Engineer A can approve.
  • Professional Competence Standard
    II.1.b requires engineers to assess conformity with standards, which depends on the professional competence this resource grounds.
Capability (4)
  • Engineer A Standard Testing Non-Preclusion Recognition
    Recognizing that standard testing compliance does not preclude further obligations relates to approving only documents conforming to applicable standards.
  • Engineer A BER 08-10 Standard Testing Non-Preclusion Recognition
    Recognizing that compliance with existing standards does not preclude further safety action relates to the duty to approve only conforming engineering documents.
  • Engineer A Current Case Standard Testing Non-Preclusion Recognition
    Recognizing that standard testing completion does not end safety obligations reflects the duty to ensure engineering documents conform to applicable standards.
  • Company X Employer Reasonableness in Absent Standards Context
    The reasonableness of Company X's testing decisions is evaluated against the requirement to conform to applicable standards.
II.3.a. Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.
How this applies in the case (showing 3 of 38)
Obligation
Engineer A Public Interest Testimony Obligation at Government Hearing
Testifying at a government hearing requires Engineer A to be objective and truthful and include all relevant safety information as this provision mandates.
Action
Consider Testifying at Public Hearing
Testifying at a public hearing requires the engineer to be objective and truthful and include all relevant information in their testimony.
State
Engineer A Post-Employment Witness Participation Consideration
Testifying at a public safety hearing requires Engineer A to be objective and truthful and include all relevant pertinent information.
Obligation (4)
  • Engineer A Public Interest Testimony Obligation at Government Hearing
    Testifying at a government hearing requires Engineer A to be objective and truthful and include all relevant safety information as this provision mandates.
  • Engineer A Proprietary Information Boundary in Hearing Testimony
    Calibrating testimony to share safety concerns truthfully while respecting confidentiality boundaries aligns with the objectivity and completeness requirements of this provision.
  • Engineer Doe BER 76-4 Post-Termination Public Hearing Reporting
    Engineer Doe's obligation to report contradicting data at a public hearing reflects the requirement to be objective and include all relevant information in testimony.
  • Engineer A Current Case Post-Employment Confidentiality Agreement Compliance Public Testimony
    Providing truthful and complete testimony while respecting confidentiality constraints directly implicates the objectivity and completeness requirements of this provision.
Action (3)
  • Consider Testifying at Public Hearing
    Testifying at a public hearing requires the engineer to be objective and truthful and include all relevant information in their testimony.
  • Verbally Report Findings to Client
    Verbally reporting findings to the client requires the engineer to be objective and truthful in conveying professional information.
  • Report Findings to Regulatory Authority
    Reporting findings to a regulatory authority must be done objectively and truthfully with all pertinent information included.
State (5)
  • Engineer A Post-Employment Witness Participation Consideration
    Testifying at a public safety hearing requires Engineer A to be objective and truthful and include all relevant pertinent information.
  • BER 76-4 Client-Suppressed Environmental Findings at Public Hearing
    Engineer Doe's obligation to present complete findings at the public hearing directly implicates the duty to be objective and include all relevant information.
  • BER 76-4 Confidentiality Instruction Suppressing Safety Report
    The instruction to suppress the safety report conflicts with the duty to be truthful and include all relevant information in professional reports.
  • Present Case Post-Employment Expert Witness Participation Consideration
    Engineer A's witness participation at the government hearing requires objective and truthful testimony including all pertinent safety information.
  • Present Case Competing Duties Between Confidentiality and Public Safety Reporting
    The duty to be objective and include all relevant information in testimony is in direct tension with confidentiality obligations to Company X.
Constraint (3)
  • Engineer A Objective Truthful Testimony Constraint
    II.3.a directly mandates objective and truthful testimony including all relevant information, which is the basis of this constraint.
  • Engineer A Good Faith Concern Epistemic Qualification Constraint at Hearing
    II.3.a requires truthful and objective reporting, constraining Engineer A from presenting unconfirmed concerns as established safety failures.
  • Engineer A Regulatory Standards Vacuum Testimony Framing Constraint
    II.3.a requires truthful testimony, prohibiting Engineer A from framing testimony as violations of standards that do not exist.
Principle (5)
  • Objectivity Invoked Engineer A Current Case Standards Hearing Testimony
    II.3.a directly requires that Engineer A's testimony at the standards hearing be objective and truthful.
  • Professional Competence In Risk Assessment Invoked By Engineer A Safety Observation
    II.3.a requires that Engineer A's statements about safety observations be grounded in truthful and objective professional assessment.
  • Public Interest Engineering Testimony Obligation Invoked By Engineer A Hearing Participation
    II.3.a conditions permissible hearing participation on Engineer A providing objective and truthful testimony.
  • Client Report Suppression Prohibition Invoked BER 76-4
    II.3.a applies as suppressing Engineer Doe's written report violated the obligation to provide objective and truthful professional statements.
  • Professional Competence Invoked Engineer A Current Case Testimony Prerequisite
    II.3.a links objectivity and truthfulness to the competence prerequisite for Engineer A's permissible testimony.
Role (4)
  • Engineer A Post-Employment Public Safety Standards Witness
    Engineer A must be objective and truthful and include all relevant information when providing testimony at the government public safety standards hearing.
  • Engineer A Current Case Post-Employment Public Safety Standards Witness
    Engineer A is obligated to provide objective, truthful, and complete testimony at the government safety hearing regarding the consumer product.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    Engineer Doe must be objective and truthful in professional reports and testimony regarding the plant discharge evaluation, including adverse findings.
  • Engineer A BER 08-10 MedTech Respirator Safety Engineer
    Engineer A must be objective and truthful in the safety concern report submitted regarding the dangerous relief valve placement on the infant respirator.
Event (2)
  • Engineer A Faces Testimony Decision
    If Engineer A testifies at the hearing, the provision requires that testimony be objective, truthful, and include all relevant and pertinent information.
  • Public Safety Hearing Announced
    The announcement of a public safety hearing creates a context where any statements or testimony provided must meet the standard of objectivity and completeness.
Resource (4)
  • Government Agency Public Safety Standard Hearing
    II.3.a directly governs the objectivity and truthfulness required of Engineer A if providing testimony at this formal regulatory proceeding.
  • Professional_Competence_Standard_Hearing_Context
    II.3.a requires that testimony include all relevant and pertinent information, which depends on the technical competence this resource identifies as a condition for participation.
  • Professional Competence Standard
    II.3.a requires objective and truthful statements grounded in knowledge of facts, which this resource establishes as a prerequisite for Engineer A's testimony.
  • BER_Case_76-4
    II.3.a supports the obligation to report complete and truthful findings to public authorities, consistent with the precedent this case establishes.
Capability (8)
  • Engineer A Post-Employment Hearing Participation Capability
    Participating as a witness at a public safety hearing requires objective and truthful testimony with all relevant information included.
  • Engineer A Proprietary Information Boundary Calibration in Testimony
    Calibrating testimony to share safety-relevant information while remaining truthful and objective directly reflects this provision.
  • Engineer A Public Interest Testimony Obligation Recognition
    Recognizing the obligation to share specialized safety knowledge at a public hearing requires objective and truthful reporting of all relevant information.
  • Engineer A Current Case Post-Employment Proprietary Information Boundary
    Calibrating post-employment testimony to be truthful and include all safety-relevant information directly reflects this provision.
  • Engineer A Forensic Expert Objectivity at Government Safety Hearing
    Testifying in an objective and truthful manner independent of former employer interests is the direct expression of this provision.
  • Engineer Doe BER 76-4 Post-Contract Reporting Persistence
    Persisting in providing a truthful and complete safety report despite employer instruction not to reflects the duty to be objective and include all relevant information.
  • Engineer Doe BER 76-4 Post-Termination Reporting Persistence
    Continuing to provide complete and truthful safety reporting after termination directly reflects the obligation to include all relevant information in professional statements.
  • BER Multi-Case Synthesis Consumer Product Safety Calibration
    Synthesizing cases to determine what safety information must be disclosed in testimony reflects the requirement for objective and complete professional statements.
II.3.b. Engineers may express publicly technical opinions that are founded upon knowledge of the facts and competence in the subject matter.
How this applies in the case (showing 3 of 34)
Obligation
Engineer A Public Interest Testimony Obligation at Government Hearing
Engineer A's specialized knowledge and competence in the subject matter grounds the right and obligation to express technical opinions publicly at the hearing.
Action
Consider Testifying at Public Hearing
Testifying publicly at a safety standards hearing is an expression of technical opinion that must be founded on knowledge and competence.
State
Engineer A Post-Employment Witness Participation Consideration
Engineer A expressing technical opinions at the public hearing must be founded on knowledge of the facts and competence in the subject matter.
Obligation (4)
  • Engineer A Public Interest Testimony Obligation at Government Hearing
    Engineer A's specialized knowledge and competence in the subject matter grounds the right and obligation to express technical opinions publicly at the hearing.
  • Engineer A Current Case Contextual Calibration General vs Specific Safety Concern
    This provision permits public technical opinions founded on knowledge and competence, which informs how Engineer A should calibrate the scope of testimony.
  • Engineer Doe BER 76-4 Post-Termination Public Hearing Reporting
    Engineer Doe's participation in a public hearing to express technical findings is grounded in the right to express publicly technical opinions based on competence and knowledge.
  • Engineer A Post-Employment Hearing Participation Consideration
    Engineer A's post-employment participation as a witness is supported by this provision permitting public expression of technically founded opinions.
Action (2)
  • Consider Testifying at Public Hearing
    Testifying publicly at a safety standards hearing is an expression of technical opinion that must be founded on knowledge and competence.
  • Report Findings to Regulatory Authority
    Publicly expressing technical findings to a regulatory authority must be grounded in factual knowledge and subject matter competence.
State (4)
  • Engineer A Post-Employment Witness Participation Consideration
    Engineer A expressing technical opinions at the public hearing must be founded on knowledge of the facts and competence in the subject matter.
  • Engineer A Residual Safety Concern Post-Testing
    Engineer A's professional safety assessment constitutes a technical opinion that must be grounded in factual knowledge and subject matter competence.
  • Present Case Post-Employment Expert Witness Participation Consideration
    Engineer A's public witness participation involves expressing technical opinions that must be based on facts and competence per this provision.
  • BER 76-4 Client-Suppressed Environmental Findings at Public Hearing
    Engineer Doe expressing technical findings at a public hearing must be based on knowledge of facts and competence in the subject matter.
Constraint (3)
  • Engineer A Fact-Grounded Opinion Constraint at Government Hearing
    II.3.b directly requires that publicly expressed technical opinions be founded upon knowledge of facts and competence, which is the basis of this constraint.
  • Engineer A Technical Competence Prerequisite for Hearing Participation
    II.3.b establishes that technical competence in the subject matter is a prerequisite for expressing public technical opinions at the hearing.
  • Engineer A Good Faith Concern Epistemic Qualification Constraint at Hearing
    II.3.b requires fact-based competent opinions, constraining Engineer A from overstating unconfirmed safety concerns as established facts.
Principle (6)
  • Public Interest Engineering Testimony Obligation Invoked By Engineer A Hearing Participation
    II.3.b directly permits Engineer A to express technical opinions at the hearing when founded on knowledge and competence.
  • Professional Competence In Risk Assessment Invoked By Engineer A Safety Observation
    II.3.b requires that Engineer A's public technical opinions be grounded in the competence applied during safety observations.
  • Professional Competence Invoked Engineer A Current Case Testimony Prerequisite
    II.3.b directly conditions permissible public testimony on Engineer A possessing competence in the subject matter.
  • Objectivity Invoked Engineer A Current Case Standards Hearing Testimony
    II.3.b supports the objectivity requirement by grounding permissible testimony in knowledge of facts and subject matter competence.
  • Good Faith Safety Concern Threshold for External Reporting Invoked Current Case
    II.3.b applies as Engineer A's public testimony must be founded on knowledge of facts, consistent with the good-faith concern threshold.
  • Public Welfare Paramount Invoked BER 76-4 Engineer Doe Pollution Reporting
    II.3.b applies as Engineer Doe expressed technical opinions at the public hearing founded on his competent environmental findings.
Role (3)
  • Engineer A Post-Employment Public Safety Standards Witness
    Engineer A may publicly express technical opinions at the safety hearing only if founded on knowledge of the facts and competence in the subject matter.
  • Engineer A Current Case Post-Employment Public Safety Standards Witness
    Engineer A's witness testimony at the government hearing must be grounded in factual knowledge and subject matter competence to be permissible.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    Engineer Doe may publicly express technical opinions about plant discharge at the public hearing only if based on factual knowledge and competence.
Event (2)
  • Engineer A Faces Testimony Decision
    Engineer A's decision to express technical opinions publicly at the hearing must be grounded in factual knowledge and subject matter competence.
  • Public Safety Hearing Announced
    The public hearing provides the forum where Engineer A may express technical opinions, which must be founded on knowledge and competence.
Resource (4)
  • Government Agency Public Safety Standard Hearing
    II.3.b explicitly permits Engineer A to express public technical opinions at this hearing provided they are founded on knowledge and competence.
  • Professional Competence Standard
    II.3.b conditions public technical opinion on competence in the subject matter, which this resource directly establishes for Engineer A.
  • Professional_Competence_Standard_Hearing_Context
    II.3.b requires technical competence as a condition for expressing public opinions, which this resource applies as one of the three conditions for ethical participation.
  • National Product Safety Standards (General)
    II.3.b allows Engineer A to publicly express technical opinions about the regulatory gap this resource identifies, based on knowledge and competence.
Capability (6)
  • Engineer A Post-Employment Hearing Participation Capability
    Participating as a witness at a public safety hearing to express technical opinions requires that those opinions be founded on knowledge and competence.
  • Engineer A Public Interest Testimony Obligation Recognition
    Recognizing the obligation to share specialized safety knowledge publicly requires that the expressed opinions be founded on competence in the subject matter.
  • Engineer A Post-Employment Hearing Participation Technical Competence Self-Assessment
    Self-assessing technical competence before serving as an expert witness directly reflects the requirement that public technical opinions be founded on competence.
  • Engineer A Forensic Expert Objectivity at Government Safety Hearing
    Testifying objectively based on factual knowledge and technical competence at a government hearing is the direct application of this provision.
  • Engineer A Consumer Product Inconsistent Performance Safety Recognition
    Expressing a technical opinion about inconsistent product performance requires that it be founded on observed facts and subject matter competence.
  • Engineer A Current Case Consumer Product Inconsistent Performance Safety Recognition
    Recognizing and publicly expressing that inconsistent performance raises safety concerns must be grounded in factual knowledge and technical competence.
III.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
How this applies in the case (showing 3 of 40)
Obligation
Engineer A Proprietary Information Boundary in Hearing Testimony
This provision directly governs Engineer A's obligation to avoid disclosing confidential business or technical information from former employer Company X during testimony.
Action
Consider Testifying at Public Hearing
Testifying as a former employee raises the concern of potentially disclosing confidential business or technical information without employer consent.
State
Engineer A Confidential Information from Company X Employment
Engineer A's possession of confidential product safety information and internal deliberations from Company X directly triggers the prohibition on disclosing confidential employer information.
Obligation (4)
  • Engineer A Proprietary Information Boundary in Hearing Testimony
    This provision directly governs Engineer A's obligation to avoid disclosing confidential business or technical information from former employer Company X during testimony.
  • Engineer A Current Case Post-Employment Confidentiality Agreement Compliance Public Testimony
    This provision is the direct basis for Engineer A's obligation to refrain from disclosing confidential information from Company X even while testifying at the hearing.
  • Engineer Doe BER 76-4 Post-Termination Public Hearing Reporting
    Engineer Doe's post-termination hearing participation implicates the obligation not to disclose confidential information from a former employer without consent.
  • Engineer A Post-Employment Hearing Participation Consideration
    Post-employment hearing participation must be conducted in compliance with the prohibition on disclosing confidential former employer information under this provision.
Action (2)
  • Consider Testifying at Public Hearing
    Testifying as a former employee raises the concern of potentially disclosing confidential business or technical information without employer consent.
  • Report Findings to Regulatory Authority
    Reporting findings to a regulatory authority as a former employee risks disclosing confidential technical or business information without consent.
State (6)
  • Engineer A Confidential Information from Company X Employment
    Engineer A's possession of confidential product safety information and internal deliberations from Company X directly triggers the prohibition on disclosing confidential employer information.
  • Engineer A Post-Employment Status
    Engineer A's former employment relationship with Company X establishes the confidentiality obligation that persists post-employment under this provision.
  • Engineer A Post-Employment Witness Participation Consideration
    Participating as a witness risks disclosing confidential information acquired during employment, directly implicating this confidentiality provision.
  • BER 76-4 Client-Suppressed Environmental Findings at Public Hearing
    Engineer Doe's disclosure of findings at a public hearing raises the question of whether confidential client information is being disclosed without consent.
  • Present Case Post-Employment Expert Witness Participation Consideration
    Engineer A's witness participation after leaving Company X risks unauthorized disclosure of confidential business or technical information.
  • Present Case Competing Duties Between Confidentiality and Public Safety Reporting
    This provision is the source of the confidentiality obligation that creates the central ethical tension with public safety reporting duties.
Constraint (7)
  • Engineer A Post-Employment Confidentiality Boundary at Government Hearing
    III.4 directly establishes the confidentiality obligation to former employers that creates this boundary constraint at the hearing.
  • Engineer A Confidentiality Agreement Non-Disclosure Constraint at Hearing
    III.4 is the code provision that prohibits disclosure of confidential information concerning a former employer without consent.
  • Engineer A Confidential Information Non-Deployment Against Former Employer at Hearing
    III.4 directly prohibits using confidential insider knowledge of a former employer's internal deliberations and proprietary processes against them.
  • Engineer A One-Year Temporal Attenuation Confidentiality Assessment
    III.4 applies to present or former employers without explicit time limitation, making the one-year attenuation assessment necessary.
  • Engineer A One Year Post-Employment Temporal Attenuation Confidentiality Constraint
    III.4 extends confidentiality obligations to former employers, directly creating the constraint whose attenuation over one year must be assessed.
  • Engineer A Public Safety Paramount Over Confidentiality at Hearing
    III.4 establishes the confidentiality obligation that is constrained by and must be weighed against the paramount public safety duty.
  • Engineer A Citizen Advocacy Whistleblower Non-Suppression at Hearing
    III.4 is the confidentiality provision whose scope must be assessed to determine whether it can suppress Engineer A's citizen advocacy at the hearing.
Principle (5)
  • Confidentiality Invoked In Post-Employment Testimony Context
    III.4 directly establishes the confidentiality obligation that constrains Engineer A's post-employment testimony about Company X.
  • Confidentiality Principle Invoked Engineer A Current Case Post-Employment Testimony Constraint
    III.4 is the direct provision conditioning Engineer A's hearing participation on not disclosing Company X's proprietary information.
  • Confidentiality Non-Applicability to Public Danger Disclosure Invoked BER 76-4
    III.4 is the provision whose limits were tested in BER 76-4, where confidentiality did not bar disclosure of public danger findings.
  • Loyalty Invoked By Company X Employer Relationship
    III.4 embodies the duty of loyalty to a former employer through the confidentiality obligation that must be weighed against public welfare.
  • Faithful Agent Obligation Within Ethical Limits Invoked By Engineer A Internal Recommendation
    III.4 reflects the faithful agent duty to protect employer confidential information within ethical limits.
Role (4)
  • Engineer A Post-Employment Public Safety Standards Witness
    Engineer A must not disclose confidential business or technical information about former employer Company X without consent when testifying at the hearing.
  • Engineer A Current Case Post-Employment Public Safety Standards Witness
    Engineer A is governed by the duty not to disclose confidential information concerning Company X's business affairs or technical processes at the public hearing.
  • Engineer Doe BER 76-4 Pollution Consulting Engineer
    Engineer Doe must not disclose confidential technical or business information about XYZ Corporation without consent when participating in the public hearing.
  • Engineer A BER 08-10 MedTech Respirator Safety Engineer
    Engineer A must not disclose confidential information about MedTech's technical processes or business affairs without consent when raising safety concerns externally.
Event (3)
  • Engineer A Departs Company
    Upon departing the company, Engineer A becomes a former employee subject to confidentiality obligations regarding the employer's business affairs and technical processes.
  • Engineer A Faces Testimony Decision
    When deciding whether to testify, Engineer A must consider whether doing so would disclose confidential information from the former employer without consent.
  • BER 76-4 Client Conflict Arises
    This conflict directly involves the tension between confidentiality obligations to a former employer and the duty to participate in a public safety proceeding.
Resource (5)
  • Client Confidentiality vs. Public Safety Balancing Framework
    III.4 establishes the confidentiality obligation to former employer Company X that this framework must balance against public safety duties.
  • Client_Confidentiality_vs_Public_Safety_Balancing_Framework_Individual
    III.4 is the specific provision governing confidentiality of former employer information that this resource applies to determine conditions for ethical hearing participation.
  • Company X Standard Safety Testing Policies and Procedures
    III.4 prohibits disclosure of Company X's confidential technical processes and business affairs, which this resource represents.
  • Whistleblower Protection Framework
    III.4 creates the confidentiality constraint that Engineer A's potential disclosure must navigate, making this framework normatively relevant.
  • Government Agency Public Safety Standard Hearing
    III.4 directly constrains what confidential information Engineer A may disclose when testifying at this proceeding without Company X's consent.
Capability (4)
  • Engineer A Proprietary Information Boundary Calibration in Testimony
    Calibrating testimony to share safety-relevant information without disclosing confidential business or technical information directly reflects this provision.
  • Engineer A Current Case Post-Employment Proprietary Information Boundary
    Calibrating post-employment testimony to avoid disclosing confidential employer information while sharing safety concerns directly applies this provision.
  • Engineer A Post-Employment Hearing Participation Capability
    Participating in a post-employment public hearing requires recognizing the boundary between shareable safety information and confidential employer information.
  • BER Multi-Case Synthesis Consumer Product Safety Calibration
    Synthesizing precedent to calibrate what safety information can be disclosed without violating confidentiality obligations reflects this provision.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 2 Lineage Graph

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

Principle Established:

An engineer who identifies a potential safety issue should first seek to understand what internal steps are being taken, then explore internal mechanisms for recourse, and only if those efforts fail should the engineer consider external avenues such as reporting to a federal regulatory agency.

Citation Context:

The Board cited this case to illustrate the proper sequence of steps an engineer should take when raising safety concerns internally before resorting to external reporting, establishing that engineers must exhaust internal remedies first.

Relevant Excerpts
discussion: "More recently in BER Case 08-10 , Engineer A, an experienced professional engineer, was employed by MedTech, a company that manufactured medical equipment."
discussion: "The Board concluded that it was not ethical for Engineer A to indicate that he would be compelled to report the matter to an appropriate federal regulatory agency if prompt measures were not taken to correct the problem."

Principle Established:

When an engineer discovers that a client's actions may be detrimental to public health and safety, and a public hearing is called, the engineer has an ethical obligation to report findings to the relevant authority, as the duty to the public is paramount.

Citation Context:

The Board cited this case to illustrate a prior situation where an engineer had an ethical obligation to report findings to a public authority upon learning of a hearing, establishing that public safety duties are paramount over client loyalty.

Relevant Excerpts
discussion: "For example, in BER Case No. 76-4 , the XYZ Corporation was advised by a State Pollution Control Authority that it had 60 days to apply for a permit to discharge manufacturing wastes"
discussion: "In concluding that Engineer Doe had an ethical obligation to report his findings to the authority upon learning of the hearing, the Board concluded that upon learning of the hearing, Engineer Doe was squarely confronted with his obligations to the public"
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 50% Facts Similarity 27% Discussion Similarity 42% Provision Overlap 60% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, I.3, II.1, II.1.a, II.3, II.3.a, III.1.b, III.2, III.3.a Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 40% Discussion Similarity 62% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 27%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 50% Discussion Similarity 56% Provision Overlap 35% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.1, II.1, II.1.a, II.1.c, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 40% Discussion Similarity 57% Provision Overlap 32% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.1, II.1, II.1.a, II.3, II.3.a, III.2 Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 44% Discussion Similarity 59% Provision Overlap 41% Outcome Alignment 100% Tag Overlap 21%
Shared provisions: I.1, I.2, II.1, II.1.a, II.2, III.1.b, III.2 Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 26% Discussion Similarity 72% Provision Overlap 40% Outcome Alignment 100% Tag Overlap 27%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.2, III.4 Same outcome True View Synthesis
Component Similarity 38% Facts Similarity 23% Discussion Similarity 52% Provision Overlap 56% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, I.3, II.1, II.3, II.3.a, II.3.b, III.1.b, III.2, III.3.a Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 32% Discussion Similarity 64% Provision Overlap 47% Outcome Alignment 100% Tag Overlap 23%
Shared provisions: I.1, II.1, II.1.a, II.3, II.3.a, III.1.b, III.2, III.3.a Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 26% Discussion Similarity 64% Provision Overlap 31% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.1, II.1, II.1.a, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 55% Discussion Similarity 57% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 23%
Shared provisions: I.1, II.1, II.1.a, III.1.b Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Would it be ethical for Engineer A to participate as a witness at the public safety standard hearings?

Board conclusion The NSPE Board of Ethical Review does not believe there is any clear ethical prohibition on Engineer A from participating in the public safety standards hearing as long as (1) Engineer A possesses the technical competence to serve as an engineering expert in the area in which Engineer A is testifying; (2) Engineer A testifies in an objective and truthful manner; and (3) Engineer A does not disclose any information regarding Company X’s product that will violate any confidentiality agreements with Company X.
Implicit (4)

Did Engineer A have an ethical obligation to report safety concerns to a governmental authority or the public immediately after Company X rejected the recommendation for additional testing, rather than waiting until a public hearing was announced one year later?

AnalyticalThe Board's analysis treats Engineer A's participation as a binary ethical question - permissible or not - but does not address the prior and arguably more pressing question of whether Engineer A had an affirmative obligation to escalate safety concerns to the government agency immediately after Company X rejected the additional testing recommendation, rather than waiting one year until a public hearing was announced. Code Section II.1.a imposes a duty to notify appropriate authorities when engineering judgment is overruled under circumstances that endanger life or property. The absence of applicable governmental or industry standards does not extinguish this duty; if anything, the regulatory vacuum heightens it, because the public safety hearing is not the only institutional mechanism available and may not be the most timely one. The one-year delay, while not rendering Engineer A's eventual testimony unethical, does suggest that Engineer A may have underweighted the proactive risk disclosure obligation in the period immediately following Company X's rejection. The Board's silence on this point leaves open a significant gap in the ethical analysis: the permissibility of eventual testimony does not retroactively satisfy any obligation that may have existed to report earlier. Engineers facing analogous situations should understand that the ethical clock on escalation begins at the moment of employer rejection, not at the moment a convenient institutional forum appears.
AnalyticalIn response to Q101, Engineer A did not have a clear ethical obligation to report safety concerns to a governmental authority immediately after Company X rejected the additional testing recommendation. At that moment, no applicable governmental or industry standards existed for the product, no confirmed safety failure had occurred, and Engineer A's concerns were grounded in observed performance inconsistencies rather than a documented violation of an established standard. Code Section II.1.a requires notification to authorities when engineering judgment is overruled under circumstances that endanger life or property, but the threshold of 'endangerment' requires more than a good-faith professional concern in a regulatory vacuum. The absence of any governing standard meant there was no objective benchmark against which Company X's product could be declared non-compliant or dangerous. Immediate external disclosure at that stage would have risked premature harm to Company X's commercial interests without a sufficiently firm epistemic foundation. The one-year gap, while not ideal, does not itself constitute an ethical failure, because the triggering institutional mechanism - the public safety standards hearing - did not exist until the government agency announced it. Engineer A's ethical obligation to escalate externally crystallized when that hearing was announced, not when the internal recommendation was rejected.

Does the one-year gap between Engineer A's resignation and the public safety hearing affect the reliability or ethical weight of Engineer A's testimony, given that product designs, testing data, and safety conditions may have changed in the interim?

AnalyticalBeyond the Board's three stated conditions for ethical participation, the temporal gap of one year between Engineer A's resignation and the public safety standards hearing introduces a distinct epistemic obligation that the Board did not address: Engineer A must affirmatively assess whether the safety concerns observed during employment remain materially accurate at the time of testimony. If Company X has modified the product design, conducted additional testing, or otherwise addressed the performance inconsistencies in the intervening year, Engineer A's testimony based on stale observations could mislead the hearing authority rather than inform it. Objectivity under Code Section II.3.a requires not merely that Engineer A believe what is said, but that the factual basis for the testimony be current enough to support the conclusions offered. Engineer A therefore bears a pre-testimony duty of epistemic diligence - to the extent possible without breaching confidentiality - to determine whether the conditions that gave rise to the safety concern still obtain, and to qualify testimony accordingly if they cannot be verified.
AnalyticalIn response to Q102, the one-year temporal gap between Engineer A's resignation and the public safety hearing does introduce a meaningful epistemic constraint on the reliability of Engineer A's testimony, though it does not render participation unethical. Product designs, manufacturing processes, and safety testing data may have evolved during that interval, and Engineer A's knowledge is necessarily frozen at the point of departure from Company X. This temporal attenuation has two ethical implications. First, Engineer A has an obligation under Code Section II.3.a to be objective and truthful, which requires explicitly framing testimony as reflecting conditions observed during employment rather than asserting current product status. Second, Engineer A must exercise professional competence in acknowledging the limits of that knowledge, particularly if competitors' products or updated versions of Company X's product are also under review at the hearing. The temporal gap does not diminish the ethical weight of Engineer A's testimony about the systemic regulatory gap - the absence of standards applicable to this product category - because that structural observation remains valid regardless of product-specific changes. However, product-specific safety claims must be qualified accordingly. The Board's condition requiring objective and truthful testimony implicitly encompasses this epistemic honesty obligation.

Was Company X's rejection of additional safety testing itself an ethical violation, given that the product operates in a regulatory standards vacuum and the safety concerns were raised by a qualified engineer based on observed performance inconsistencies?

AnalyticalIn response to Q103, Company X's rejection of Engineer A's additional safety testing recommendation occupies an ethically ambiguous rather than clearly violative position. On one hand, the product had passed standard safety testing within accepted parameters, no applicable governmental or industry standards mandated further testing, and the rejection was driven by cost and delay considerations that are commercially legitimate in the absence of a regulatory requirement. On the other hand, when a qualified engineer raises specific, professionally grounded safety concerns based on observed performance inconsistencies - concerns that the completed standard testing did not address - an employer's refusal to investigate those concerns solely on cost grounds represents a failure to give adequate weight to the public safety paramount principle. The ethical violation, if any, is not that Company X declined optional testing, but that it declined without engaging substantively with the engineering basis for Engineer A's concern. A commercially reasonable decision in an absent-standards context is not automatically an ethically reasonable one when a credentialed engineer has identified a specific, articulable safety gap. The Board's framework implicitly acknowledges this by treating Engineer A's concern as legitimate enough to support public testimony, which would be incoherent if Company X's rejection were entirely beyond ethical reproach.

To what extent does Engineer A's status as a private citizen rather than a retained expert witness change the ethical analysis of participation in the public safety standards hearing, particularly regarding objectivity and the appearance of personal grievance against a former employer?

AnalyticalThe Board's conclusion implicitly treats Engineer A's status as a private citizen and former employee as ethically neutral relative to a retained expert witness, but this equivalence deserves scrutiny. A retained expert witness operates under formal procedural constraints - disclosure obligations, cross-examination, daubert-type competence standards - that provide institutional checks on bias and epistemic overreach. Engineer A, appearing as a private citizen witness, operates without these structural safeguards. This asymmetry does not render Engineer A's participation unethical, but it does place a heightened self-imposed obligation on Engineer A to police the appearance of personal grievance, to distinguish between professional safety judgment and residual resentment toward a former employer that rejected a recommendation and contributed to a resignation, and to present testimony in a manner that a neutral professional would recognize as objective. The virtue ethics framework is particularly apt here: the professional virtues of courage, integrity, and practical wisdom require Engineer A not merely to testify, but to testify in a manner that would withstand scrutiny from a reasonable peer who knew both the safety concern and the employment history. The Board's condition of objectivity, while necessary, is insufficient without this additional self-critical dimension.
AnalyticalIn response to Q104, Engineer A's status as a private citizen rather than a retained expert witness materially changes the ethical texture of the analysis in two respects, though not the ultimate permissibility of participation. As a private citizen acting on personal professional judgment rather than as a hired advocate, Engineer A faces a reduced risk of the structural bias that retained expert witnesses carry - namely, the financial incentive to shade testimony toward the retaining party's position. This actually strengthens the objectivity dimension of the Board's three conditions. However, Engineer A's status as a former employee who resigned after a conflict with Company X introduces a different appearance problem: the testimony may be perceived as motivated by personal grievance rather than disinterested professional concern. This appearance risk does not make participation unethical, but it does impose a heightened obligation on Engineer A to ensure that testimony is scrupulously confined to technically grounded observations, explicitly qualified as reflecting conditions at the time of employment, and free of any advocacy framing that could suggest retaliatory intent. Code Section II.3.b permits engineers to express public technical opinions founded on knowledge and competence, and this provision applies with equal force to private citizens as to retained experts. The ethical burden is on Engineer A to demonstrate through the substance and tone of testimony that the public safety motivation is genuine and primary.
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 Confidentiality in the post-employment testimony context conflict with the principle of Public Welfare Paramount when Engineer A possesses non-public safety information about Company X's product that could be material to the government hearing but is potentially covered by a confidentiality agreement?

AnalyticalThe Board's conclusion that Engineer A may participate provided confidentiality agreements are not violated implicitly assumes that the boundary between general professional knowledge and employer-specific confidential information is clear and stable. In practice, this boundary is highly porous in the context of a novel consumer product operating in a regulatory standards vacuum. Because no external standards exist against which to benchmark the product's safety performance, virtually any technically meaningful testimony Engineer A could offer about performance inconsistencies would necessarily draw on observations made exclusively within Company X's proprietary testing environment. The Board's third condition - non-disclosure of confidential information - may therefore be structurally difficult to satisfy without reducing Engineer A's testimony to generalities so abstract as to be of limited value to the hearing authority. The Board should have acknowledged this structural tension and provided guidance on how Engineer A can calibrate testimony to remain within the confidentiality boundary while still fulfilling the public interest testimony obligation. One workable approach consistent with Code Section III.4 is for Engineer A to testify about the category of safety concern - the nature of the performance inconsistency and the type of additional testing that would be warranted - without identifying Company X's specific product data, internal deliberations, or proprietary design details.
AnalyticalThe Board's three conditions for ethical participation - technical competence, objectivity, and confidentiality compliance - are framed as independent requirements, but they interact in ways that create a compound constraint the Board did not analyze. Specifically, the confidentiality constraint may limit the scope of testimony that Engineer A can offer, and that limitation in turn affects whether Engineer A can satisfy the technical competence condition in a meaningful sense. If the most technically significant safety observations Engineer A possesses are inseparable from confidential product-specific data, then complying with the confidentiality constraint may reduce Engineer A's testimony to a level of generality at which Engineer A no longer qualifies as a competent expert on the specific safety question before the hearing. In that scenario, Engineer A would face a trilemma: breach confidentiality to testify competently, testify incompetently to preserve confidentiality, or decline to testify. The Board's framework does not resolve this trilemma. The most ethically defensible resolution, consistent with Code Sections II.3.b and III.4, is that Engineer A should testify only to the extent that technically meaningful and accurate testimony can be offered without breaching confidentiality, and should explicitly disclose to the hearing authority the existence and nature of the limitation - without revealing the confidential content - so that the hearing authority can assess the weight and completeness of the testimony accordingly.
AnalyticalIn response to Q201, the tension between the Confidentiality principle under Code Section III.4 and the Public Welfare Paramount principle under Code Section I.1 is real but resolvable in this case without requiring either principle to be entirely displaced. The confidentiality obligation survives post-employment and prohibits Engineer A from disclosing, without consent, confidential information concerning Company X's business affairs or technical processes. However, the public welfare paramount principle does not require Engineer A to disclose confidential specifics in order to serve the hearing's purpose. The hearing is a standard-setting proceeding, not a product liability adjudication. Engineer A can provide substantial value to the hearing by testifying about the general category of safety concerns observed, the nature of the performance inconsistencies at a level of abstraction that does not reveal proprietary design details, and the structural inadequacy of existing testing frameworks for this product category - all without breaching confidentiality. The ethical resolution is not a hierarchy in which one principle defeats the other, but a calibration in which Engineer A contributes the maximum safety-relevant information that can be shared without crossing the confidentiality boundary. Only if Engineer A possessed knowledge of an imminent, specific, and serious danger to the public - analogous to the confirmed violation in BER 76-4 - would the confidentiality obligation be fully displaced by the public danger exception.
AnalyticalThe tension between Confidentiality and Public Welfare Paramount was resolved not by displacing confidentiality entirely, but by drawing a precise boundary: Engineer A may testify about professional observations, engineering judgment, and safety concerns without disclosing the proprietary business details, internal deliberations, or product design specifics that confidentiality agreements protect. This resolution treats the two principles as operating on different domains of information rather than as direct competitors. Public welfare paramount governs what Engineer A is permitted - and arguably obligated - to say about safety concerns observed through professional competence; confidentiality governs the channel and content of disclosure, not the decision to participate at all. The case therefore teaches that confidentiality is a constraint on the manner of public safety disclosure, not a veto over it, particularly in a post-employment context where the engineer participates as a private citizen rather than as a company representative.

Does the principle of Loyal and Faithful Agent Obligation within ethical limits conflict with the principle of Proactive Risk Disclosure when Company X has completed standard safety testing that passed, yet Engineer A's professional judgment identifies residual safety concerns that the completed testing did not resolve?

AnalyticalThe tension between the Faithful Agent Obligation Within Ethical Limits and Proactive Risk Disclosure was resolved at the moment Company X rejected Engineer A's recommendation for additional testing, not at the moment Engineer A chose to testify. The case reveals a sequential principle structure: the faithful agent obligation is primary and requires internal escalation first, but it is exhausted - not merely weakened - once the employer has made a final cost-driven rejection of a safety recommendation in a regulatory vacuum. After that rejection, the proactive risk disclosure principle becomes operative and is no longer constrained by the faithful agent duty. Engineer A's resignation further confirms this transition: by departing, Engineer A formally exited the agency relationship, removing any residual argument that testifying at a public hearing would constitute a breach of ongoing employer loyalty. The case teaches that faithful agent obligations are temporally bounded by both the employer's final decision and the termination of the employment relationship itself.

Does the Good Faith Safety Concern Threshold for External Reporting conflict with the principle of Professional Competence in Risk Assessment when Engineer A's safety concerns are based on observed performance inconsistencies rather than a confirmed safety failure, raising the question of whether a good faith belief alone is a sufficient epistemic basis for public testimony that could harm Company X's commercial interests?

AnalyticalIn response to Q203, a good-faith professional belief based on observed performance inconsistencies is a sufficient epistemic basis for participation in a public safety standards hearing, but it is not a sufficient basis for asserting confirmed danger as a matter of fact. The distinction is critical. Code Section II.3.b permits engineers to express publicly technical opinions founded on knowledge of the facts and competence in the subject matter. A good-faith concern grounded in direct professional observation during product development satisfies the 'knowledge of the facts' requirement - Engineer A witnessed the inconsistencies firsthand. Professional competence in risk assessment then converts those observations into a reasoned safety concern. What good faith alone cannot support is testimony that characterizes the product as definitively unsafe or that overstates the certainty of harm. Engineer A's epistemic obligation is to present the concern as what it is: a professionally grounded inference from observed data that warrants further investigation, not a confirmed finding of danger. This framing is not merely a rhetorical nicety - it is the ethical boundary between legitimate expert opinion and misleading testimony. The potential commercial harm to Company X from overstated testimony makes this epistemic precision an ethical imperative, not just a professional courtesy.
AnalyticalThe tension between the Good Faith Safety Concern Threshold for External Reporting and Professional Competence in Risk Assessment was resolved by the Board in a manner that treats good faith professional judgment as a sufficient - though not unlimited - epistemic basis for public testimony, provided that testimony is framed as expert opinion grounded in observed facts rather than as a confirmed finding of defect. This resolution carries an important prioritization lesson: the absence of a documented safety failure or an applicable standard does not raise the evidentiary bar for testimony to the level of certainty; it instead shifts the framing obligation onto the engineer. Engineer A must testify as a competent professional offering a reasoned opinion about observed performance inconsistencies, not as a whistleblower asserting a proven violation. The Regulatory Gap Safety Escalation Obligation actually heightens rather than diminishes the value of this testimony precisely because the public hearing is the institutional mechanism through which good-faith professional judgment is converted into protective standards. The case therefore teaches that in a regulatory vacuum, the epistemic threshold for testimony is calibrated to the standard of professional competence - what a qualified engineer in good faith believes based on observed evidence - rather than to the higher standard of confirmed harm or existing regulatory violation.

Does the Regulatory Gap Safety Escalation Obligation conflict with the principle of Employer Reasonableness in an Absent-Standards Context, given that Company X's rejection of additional testing may have been commercially reasonable precisely because no applicable standards existed to define what additional testing was required?

Theoretical (4)

From a deontological perspective, does Engineer A have a categorical duty to testify at the public safety standards hearing regardless of personal risk or inconvenience, given that the NSPE Code imposes an affirmative obligation to hold public safety paramount and to notify authorities when engineering judgment is overruled in ways that may endanger the public?

AnalyticalIn response to Q301, from a deontological perspective, Engineer A does not face a categorical, unconditional duty to testify at the public safety standards hearing in the Kantian sense, but does face a strong prima facie duty that is difficult to override. The NSPE Code imposes an affirmative obligation to hold public safety paramount and, under Code Section II.1.a, to notify appropriate authorities when engineering judgment is overruled in ways that may endanger life or property. The public safety hearing is precisely the institutional mechanism through which that notification can be made. A strict deontological reading would hold that Engineer A's duty to testify is not contingent on personal convenience, reputational risk, or the uncertainty of outcome - the duty flows from the role of engineer and the nature of the safety concern, not from a calculation of consequences. However, the deontological framework also recognizes that duties can conflict: the duty of confidentiality is itself a genuine obligation, not merely a preference. The resolution is not that public safety always defeats confidentiality categorically, but that Engineer A has a duty to testify to the maximum extent that confidentiality permits. Silence in the face of a government-convened safety hearing, when Engineer A possesses relevant professional knowledge, would be difficult to justify on deontological grounds as anything other than a failure of professional duty.

From a consequentialist perspective, does the aggregate public safety benefit of Engineer A's testimony at the hearing - potentially shaping new safety standards for an entire product category - outweigh the harms of possible confidentiality breaches, reputational damage to Company X, and the epistemic uncertainty inherent in Engineer A's unverified safety concerns?

AnalyticalIn response to Q302, from a consequentialist perspective, the aggregate public safety benefit of Engineer A's testimony at the hearing plausibly outweighs the identified harms, but the analysis is more nuanced than a simple benefit-harm comparison. On the benefit side, Engineer A's testimony could contribute to the establishment of safety standards for an entire product category affecting all consumers of this class of products - a systemic benefit that extends far beyond the specific Company X product. The hearing is precisely the institutional mechanism designed to aggregate such professional knowledge into protective regulation. On the harm side, the risks include: inadvertent confidentiality breach harming Company X's competitive position, reputational damage to Company X based on unverified concerns, and the epistemic uncertainty inherent in testimony grounded in performance inconsistencies rather than confirmed failures. The consequentialist calculus favors testimony because: (1) the Board's three conditions - technical competence, objectivity, and confidentiality compliance - substantially mitigate the identified harms; (2) the systemic benefit of sound safety standards is large and durable; and (3) the cost of Engineer A's silence - a missed opportunity to inform a once-in-a-generation standard-setting process for a new product category - is itself a significant harm to the public interest. The epistemic uncertainty in Engineer A's concerns is a reason for careful framing of testimony, not for silence.

From a virtue ethics perspective, does Engineer A demonstrate the professional virtues of courage, integrity, and practical wisdom by choosing to testify within the Board's three stated conditions - technical competence, objectivity, and confidentiality compliance - rather than either remaining silent out of loyalty to a former employer or disclosing confidential details out of zeal for public safety?

AnalyticalIn response to Q303, from a virtue ethics perspective, Engineer A's decision to testify within the Board's three stated conditions - technical competence, objectivity, and confidentiality compliance - represents a paradigmatic exercise of the professional virtues of courage, integrity, and practical wisdom. Courage is demonstrated by willingness to participate in a public proceeding that carries reputational risk and potential legal exposure from a former employer, motivated by professional duty rather than personal gain. Integrity is demonstrated by the commitment to testify truthfully and objectively even when a more self-protective course - silence - is available and arguably defensible. Practical wisdom, the Aristotelian virtue of phronesis, is demonstrated precisely by the calibrated approach the Board's conditions embody: neither the excess of reckless disclosure that ignores confidentiality obligations, nor the deficiency of cowardly silence that abandons public safety obligations, but the mean of principled, bounded, competent testimony. The virtue ethics analysis also highlights that the manner of testimony matters as much as the decision to testify: an engineer who testifies with epistemic humility, acknowledges the limits of personal knowledge, and refrains from advocacy framing demonstrates greater professional virtue than one who testifies with certainty or apparent animus toward a former employer.

From a deontological perspective, does the absence of applicable governmental or industry safety standards for Company X's new product heighten rather than diminish Engineer A's duty to testify, because the regulatory vacuum means the public safety hearing is the primary institutional mechanism through which Engineer A's professional judgment can be converted into protective standards?

AnalyticalIn response to Q304, from a deontological perspective, the absence of applicable governmental or industry safety standards for Company X's new product heightens rather than diminishes Engineer A's duty to testify. The deontological reasoning proceeds as follows: the NSPE Code's public safety paramount obligation is not contingent on the existence of a regulatory framework - it is a foundational professional duty that exists independently of whether standards have been codified. In a regulatory vacuum, the public safety hearing is not merely one of several available mechanisms for Engineer A to fulfill the notification obligation under Code Section II.1.a - it is the primary and perhaps only institutional mechanism through which Engineer A's professional judgment can be converted into protective standards applicable to the entire product category. The absence of standards means that Engineer A's testimony carries greater marginal value than it would in a mature regulatory environment where other engineers, inspectors, and compliance mechanisms already exist to surface safety concerns. A deontological framework that grounds duty in the nature of the professional role and the vulnerability of the public would therefore conclude that the regulatory vacuum creates a heightened, not diminished, obligation to participate - because the hearing is the mechanism through which the vacuum itself is addressed.
Counterfactual (4)

If Engineer A had not resigned from Company X but were still employed there at the time of the public safety standards hearing, would the ethical calculus for participation as a witness change materially - particularly regarding the tension between the faithful agent obligation to an active employer and the public safety testimony obligation - and would the Board's three conditions be sufficient to resolve that tension?

AnalyticalIn response to Q401, if Engineer A were still employed by Company X at the time of the public safety standards hearing, the ethical calculus would change materially and the Board's three conditions would be insufficient on their own to resolve the resulting tension. An active employment relationship creates a faithful agent obligation under the NSPE Code that does not exist post-employment. Testifying at a public hearing about safety concerns that Company X has already rejected - while still employed there - would place Engineer A in direct conflict with the employer's interests in a way that resignation has already resolved in the current case. The active employment context would require Engineer A to first exhaust all internal escalation pathways, including escalation above Supervisor B to senior management or a board-level safety committee, before considering external testimony. If internal escalation were exhausted and the safety concern remained unaddressed, the Code's public safety paramount obligation would still permit - and potentially require - external disclosure, but the faithful agent obligation would demand that Engineer A provide Company X with notice and an opportunity to respond before testifying publicly. The Board's three conditions address the content and manner of testimony but do not address the procedural obligations that active employment would impose. A fourth condition - exhaustion of internal remedies - would be necessary to resolve the tension in the active employment scenario.

If Engineer A had escalated safety concerns directly to the relevant government agency immediately after Company X rejected the additional testing recommendation - rather than waiting until the public hearing one year later - would that earlier disclosure have been ethically required, ethically permissible, or premature given that no imminent harm had yet materialized and no regulatory standards existed at that time?

AnalyticalIn response to Q402, if Engineer A had escalated safety concerns directly to the relevant government agency immediately after Company X rejected the additional testing recommendation, that earlier disclosure would have been ethically permissible but not ethically required, and potentially premature given the epistemic and regulatory context at that time. It would have been permissible because Code Section II.1.a does not specify a waiting period before notifying appropriate authorities when engineering judgment is overruled in ways that may endanger life or property. However, it would not have been required because: (1) no imminent harm had materialized; (2) no applicable regulatory standards existed against which the product could be declared non-compliant; (3) the relevant government agency had not yet established a forum for receiving such concerns; and (4) Engineer A's concerns were grounded in performance inconsistencies rather than a confirmed safety failure. Premature disclosure to a government agency without an established regulatory framework or hearing process risks being ineffective - the agency may have no mechanism to act on the concern - and could expose Engineer A to confidentiality liability without producing any public safety benefit. The ethical calculus favors waiting for the institutional mechanism - the public hearing - to exist before escalating externally, provided Engineer A did not observe any escalation in the safety risk during the intervening period that would have triggered an immediate reporting obligation.

Drawing on the BER 76-4 precedent involving Engineer Doe, if Engineer A's safety concerns had been based on a confirmed, documented violation of an existing standard rather than a good-faith belief about inconsistent performance in a regulatory vacuum, would the confidentiality constraint under Code Section III.4 have been entirely displaced by the public danger exception, and would Engineer A have faced an unambiguous obligation - not merely a permission - to testify?

AnalyticalDrawing on the BER 76-4 precedent involving Engineer Doe, a critical distinction emerges that the Board in the present case did not fully develop: in BER 76-4, Engineer Doe's safety concern was grounded in a confirmed violation of an existing environmental standard, which meant the confidentiality constraint under Code Section III.4 was clearly displaced by the public danger exception. In the present case, Engineer A's concern is grounded in observed performance inconsistencies in a regulatory standards vacuum - a materially weaker epistemic foundation. This distinction has two analytical consequences the Board should have addressed. First, the good faith belief standard that suffices to permit testimony in the present case would not have been sufficient to compel testimony in the BER 76-4 scenario; the presence of a confirmed violation in BER 76-4 converted permission into obligation. Second, because Engineer A's concern lacks the anchor of a violated standard, the epistemic qualification constraint is more demanding: Engineer A must be especially careful to frame testimony as professional judgment about observed inconsistencies and the need for further investigation, rather than as a finding of demonstrated danger. The absence of applicable standards cuts both ways - it heightens the importance of the hearing as a standard-setting mechanism, but it also means Engineer A cannot claim the authority of a violated benchmark to support the testimony.
AnalyticalIn response to Q403, drawing on the BER 76-4 precedent, if Engineer A's safety concerns had been based on a confirmed, documented violation of an existing standard rather than a good-faith belief about inconsistent performance in a regulatory vacuum, the confidentiality constraint under Code Section III.4 would not have been entirely displaced, but the public danger exception would have operated with far greater force, and Engineer A would have faced an obligation - not merely a permission - to testify. In BER 76-4, Engineer Doe's situation involved a confirmed violation of an established environmental standard, which the Board treated as triggering a clear duty to report despite confidentiality instructions. The key distinction is that a confirmed violation of an existing standard provides the objective, verifiable basis that transforms a professional concern into a public danger - the epistemic threshold that justifies overriding confidentiality. In the current case, the absence of applicable standards means there is no benchmark against which a 'violation' can be confirmed, which is precisely why the Board treats Engineer A's participation as ethically permissible rather than obligatory. A confirmed violation in an existing-standards context would shift the analysis from permissibility to obligation, and would require Engineer A to disclose the specific safety information necessary to protect the public even if that disclosure incidentally revealed confidential details - subject to the constraint that disclosure be limited to what is necessary to address the danger.

If Engineer A's testimony at the public safety standards hearing were to inadvertently reveal proprietary details about Company X's product design - even without intent to breach confidentiality - would the resulting harm to Company X's competitive position retroactively render Engineer A's participation unethical, or does the public safety imperative insulate Engineer A from that ethical liability provided the Board's three conditions were met in good faith?

AnalyticalIn response to Q404, if Engineer A's testimony were to inadvertently reveal proprietary details about Company X's product design - even without intent to breach confidentiality - the resulting harm to Company X's competitive position would not retroactively render Engineer A's participation unethical, provided the Board's three conditions were met in good faith. The ethical evaluation of conduct is assessed at the time of the decision and action, not retroactively by reference to unintended consequences that a reasonable person could not have foreseen. If Engineer A exercised genuine professional judgment in calibrating testimony to avoid confidential specifics, testified truthfully and objectively, and possessed the requisite technical competence, then an inadvertent disclosure that resulted from the inherent difficulty of separating general safety knowledge from proprietary knowledge does not constitute an ethical violation - it constitutes an unfortunate but non-culpable outcome. However, this insulation from retroactive ethical liability is conditional: it applies only if Engineer A made a genuine, documented effort to identify and avoid confidential information before testifying, and did not take undue risks with information that a reasonable engineer would have recognized as proprietary. If Engineer A was reckless or insufficiently careful in that pre-testimony assessment, the inadvertent disclosure would reflect a failure to meet the Board's third condition in good faith, and the ethical insulation would not apply. The public safety imperative justifies the risk of participation but does not excuse negligence in managing that risk.
Decisions & Arguments (4)
View Extraction

Should Engineer A participate as a witness at the public safety standards hearing, and if so, under what epistemic and confidentiality constraints must that testimony be calibrated?

Options considered:
O1 Participate as a witness at the public safety standards hearing, testifying about the category of safety concern and the nature of observed performance inconsistencies at a level of abstraction that avoids Company X's proprietary design details, explicitly framing testimony as professional judgment based on conditions observed during employment rather than as confirmed findings of current product danger Board's choice
O2 Decline to participate as a witness at the public safety standards hearing on the grounds that the one-year temporal gap, the absence of confirmed safety incidents, and the structural difficulty of separating safety observations from confidential product-specific knowledge make it impossible to testify in a manner that is simultaneously technically meaningful, objectively framed, and confidentiality-compliant
O3 Participate as a witness at the public safety standards hearing and testify fully about all observed performance inconsistencies and internal testing data, treating the public safety paramount principle as displacing post-employment confidentiality obligations given the regulatory vacuum and the absence of any other institutional mechanism through which the safety concern can be surfaced
Argument structure:
Warrants

The Post-Employment Public Safety Testimony Participation Obligation (II.1.a, I.1) establishes that the public welfare duty survives the employment relationship and that Engineer A's unique technical knowledge is directly relevant to the regulatory body's mission. The Good Faith General Safety Concern Public Hearing Participation Obligation permits participation based on good-faith professional belief without requiring confirmed incidents, provided Engineer A testifies objectively, possesses technical competence, and does not disclose confidential information. Competing against these is the Post-Employment Confidentiality Agreement Compliance Obligation (III.4), which prohibits disclosure of Company X's proprietary product information, processes, or business affairs. The One-Year Post-Employment Temporal Attenuation of Confidentiality Constraint further establishes that temporal distance may attenuate but does not eliminate residual confidentiality duties. The Good Faith Safety Concern Objective Testimony Constraint prohibits advocacy, overstatement of certainty, or presenting unconfirmed concerns as established findings.

Rebuttals

Uncertainty arises on multiple axes: (1) the confidentiality boundary is structurally porous in a regulatory vacuum: because no external standards exist, virtually any technically meaningful testimony about performance inconsistencies necessarily draws on observations made exclusively within Company X's proprietary testing environment, potentially reducing compliant testimony to generalities of limited value; (2) the one-year temporal gap means Engineer A's knowledge is frozen at the point of departure, and product designs or testing data may have changed, creating an epistemic currency problem that objectivity requires Engineer A to acknowledge; (3) Engineer A's status as a former employee who resigned after a conflict creates an appearance-of-grievance problem that, while not rendering participation unethical, imposes a heightened self-imposed objectivity obligation beyond the Board's stated conditions; (4) the good-faith belief standard is sufficient to permit testimony but not to assert confirmed danger, the epistemic threshold for participation is professional competence, not certainty.

Grounds

Engineer A observed inconsistent product performance issues raising unique safety concerns not captured by standard testing. Company X rejected the recommendation for additional testing on cost and schedule grounds. Engineer A resigned. Approximately one year later, the relevant government agency announced a public safety standards hearing covering Company X's product and competitors' products. No applicable governmental or industry standards exist for this product category. Engineer A possesses specialized technical knowledge directly relevant to the hearing's standard-setting mission.

Post-Employment Public Safety Testimony Participation Obligation Post-Employment Confidentiality Agreement Compliance in Public Testimony Obligation

After Company X rejected the additional safety testing recommendation on cost and schedule grounds, was Engineer A obligated to escalate the safety concern to a governmental authority immediately upon rejection, or was it ethically permissible to wait until the public safety standards hearing was announced approximately one year later?

Options considered:
O1 After Company X's rejection, assess the safety concern as not yet meeting the urgency threshold for immediate external reporting given the absence of confirmed incidents, applicable standards, or an established regulatory forum, and wait for an appropriate institutional mechanism, such as the announced public safety standards hearing, before escalating externally, while remaining alert to any escalation in safety risk during the intervening period that would trigger an earlier reporting obligation Board's choice
O2 After Company X's rejection, escalate the safety concern directly to the relevant government agency without waiting for a formal hearing to be announced, treating the cost-driven rejection of a credentialed engineer's safety recommendation in a regulatory vacuum as itself sufficient to trigger the notification obligation under Code Section II.1.a regardless of whether an established regulatory forum yet exists
O3 After Company X's rejection, exhaust remaining internal escalation channels above Supervisor B, including senior management or a board-level safety committee, before treating the rejection as final, and only upon confirmed exhaustion of all internal mechanisms assess whether the safety concern meets the threshold for external reporting to a governmental authority
Argument structure:
Warrants

The Non-Acquiescence to Employer Safety Testing Rejection principle establishes that Engineer A was obligated to assess whether the identified safety concerns required escalation beyond the employer relationship after Company X's cost-driven rejection, and to refrain from treating that rejection as a final resolution of the safety concern. Code Section II.1.a imposes a duty to notify appropriate authorities when engineering judgment is overruled under circumstances that may endanger life or property. The Regulatory Gap Safety Escalation Obligation establishes that the absence of applicable standards heightens rather than diminishes the duty to escalate, because the public safety hearing is the primary institutional mechanism through which professional judgment can be converted into protective standards. Competing against these is the Graduated Internal Escalation Before External Reporting Obligation, which requires exhaustion of internal channels before external escalation. The Employer Reasonableness in Absent-Standards Context principle establishes that Company X's rejection was not unreasonable given the absence of governing standards, which affects the urgency threshold for mandatory immediate reporting. The Contextual Calibration principle establishes that general concerns without confirmed incidents in an absent-standards context generate a different, though still real, reporting obligation than specific, demonstrable concerns with confirmed incidents.

Rebuttals

Uncertainty arises from three compounding conditions: (1) the endangerment threshold under II.1.a may require more than a good-faith professional concern in a regulatory vacuum: without a governing standard, there is no objective benchmark against which Company X's product can be declared non-compliant or dangerous, which means the urgency threshold for mandatory immediate reporting may not have been met at the time of rejection; (2) the relevant government agency had not yet established a forum for receiving such concerns, meaning immediate disclosure risked being institutionally ineffective and could expose Engineer A to confidentiality liability without producing any public safety benefit; (3) the Graduated Internal Escalation principle creates uncertainty about whether Engineer A had genuinely exhausted all internal channels, including escalation above Supervisor B, before the rejection was treated as final. The rebuttal to waiting is that the ethical clock on escalation arguably begins at the moment of employer rejection, not at the moment a convenient institutional forum appears, and the one-year delay may represent an underweighting of the proactive risk disclosure obligation even if it does not constitute a clear ethical violation.

Grounds

Engineer A identified inconsistent product performance issues raising unique safety concerns not captured by standard testing. Company X completed standard safety testing within acceptable parameters. Company X rejected Engineer A's recommendation for additional testing solely on cost and schedule grounds. No applicable governmental or industry standards existed for this product category at the time of rejection. No confirmed safety incidents had occurred. Engineer A resigned. Approximately one year elapsed before the government agency announced the public safety standards hearing. The relevant government agency had not established a formal mechanism for receiving safety concerns about this product category prior to announcing the hearing.

Good Faith General Safety Concern Public Hearing Participation Obligation Contextual Calibration of Public Safety Reporting Obligation

Should Engineer A formally recommend additional safety testing to Supervisor B based on the observed performance inconsistencies, document the concern while deferring to standard testing, or raise the issue informally as a monitoring observation?

Options considered:
O1 Proactively recommend to Supervisor B that Company X conduct additional safety testing specifically designed to address the observed performance inconsistencies, explicitly identifying the unique safety concerns not captured by the standard testing already completed. Board's choice
O2 Document the observed performance inconsistencies in internal engineering records as a professional notation of residual concern, but defer to Company X's completion of standard safety testing as a sufficient basis for proceeding without a formal new testing recommendation.
O3 Raise the observed performance inconsistencies informally with Supervisor B as a professional observation warranting attention during post-market surveillance, without formally recommending a new series of pre-market safety tests.
Argument structure:
Warrants

The Faithful Agent Obligation Within Ethical Limits (III.2.a) requires Engineer A to act as a faithful agent to Company X, which includes working within the company's standard safety testing process and making recommendations through proper internal channels. The Proactive Risk Disclosure principle requires Engineer A to proactively communicate identified safety concerns to Supervisor B without waiting for formal requests or for harm to materialize. The Engineer A Current Case Standard Safety Testing Non-Preclusion Additional Concern Reporting principle establishes that completion of standard testing does not extinguish the obligation to report additional unique safety concerns that the standard testing did not capture. Competing against proactive disclosure is the Employer Reasonableness in Absent-Standards Context principle, which establishes that Company X's reliance on standard testing in the absence of governing standards was not unreasonable, creating tension about whether Engineer A's additional concern rises to the level that demands internal escalation or merely represents a professional preference for more conservative testing.

Rebuttals

Uncertainty arises because the boundary between a professional safety concern that obligates internal escalation and a professional preference for more conservative testing that does not is indeterminate when no applicable standards exist to define what additional testing is required. The completion of standard safety testing within acceptable parameters provides Company X with a reasonable basis for concluding the product is safe, which means Engineer A's residual concern, grounded in observed performance inconsistencies rather than a confirmed failure, may not clearly meet the threshold that triggers the proactive disclosure obligation as a matter of ethical duty rather than professional prudence. However, the rebuttal to this uncertainty is that the Faithful Agent Obligation Within Ethical Limits explicitly preserves the engineer's obligation to raise safety concerns even when the employer has completed standard testing, and that the absence of applicable standards heightens rather than diminishes the importance of Engineer A's specialized professional judgment as the primary available mechanism for identifying safety gaps.

Grounds

Engineer A observed what Engineer A believed were inconsistent product performance issues raising unique safety concerns not captured by standard testing. Company X had completed standard safety testing and the product demonstrated compliance with acceptable safety parameters. No applicable governmental or industry standards existed for this product category. Engineer A possessed specialized engineering competence in the relevant area. The safety concerns were identified through direct professional observation during product development.

Engineer A Faithful Agent Internal Recommendation Fulfillment

Did Engineer A have an ethical obligation to escalate safety concerns to a governmental authority immediately after Company X rejected the additional testing recommendation, or was waiting for the public hearing one year later ethically defensible given the epistemic and regulatory context?

Options considered:
O1 Wait for an established institutional forum, such as the announced public safety standards hearing, before escalating safety concerns externally, on the grounds that the endangerment threshold for mandatory immediate reporting was not clearly met and premature disclosure without an effective regulatory mechanism risks confidentiality liability without producing public safety benefit Board's choice
O2 Escalate safety concerns directly to the relevant government agency immediately after Company X's rejection, submitting a formal written safety concern report that frames the concern as professional judgment about observed performance inconsistencies warranting regulatory attention, without disclosing proprietary Company X product data
O3 After resigning from Company X, monitor publicly available information about the product category and escalate to a government agency only if evidence of actual harm or a confirmed safety incident emerges during the intervening period, treating the absence of imminent harm and the absence of applicable standards as jointly sufficient to defer external reporting until a concrete triggering event occurs
Argument structure:
Warrants

The regulatory gap safety escalation obligation and proactive risk disclosure warrant support immediate external reporting: Code Section II.1.a does not specify a waiting period before notifying appropriate authorities when engineering judgment is overruled in ways that may endanger life or property, and the regulatory vacuum arguably heightens rather than diminishes the urgency of escalation because no internal regulatory mechanism exists to surface the concern. The contextual calibration and graduated internal escalation warrants support waiting: the endangerment threshold under II.1.a requires more than a good-faith professional concern in a regulatory vacuum, no objective benchmark exists against which the product can be declared non-compliant, no imminent harm had materialized, and premature disclosure to a government agency without an established regulatory framework risks being ineffective while exposing Engineer A to confidentiality liability without producing public safety benefit. The institutional effectiveness principle holds that the ethical obligation to escalate externally crystallizes upon the existence of an institutional mechanism capable of receiving and acting on the concern.

Rebuttals

Three rebuttal conditions create uncertainty: (1) the absence of imminent harm at the time of rejection means the urgency threshold for mandatory immediate reporting may not have been met, but the threshold between 'good-faith concern' and 'endangerment' is indeterminate in a regulatory vacuum; (2) the absence of applicable standards means there is no objective benchmark for non-compliance, but the absence of standards does not mean the absence of danger; (3) the BER 08-10 MedTech precedent suggests that premature external reporting threats without exhausting internal remedies may themselves be ethically problematic, but Engineer A did exhaust internal remedies by making the recommendation formally before resigning. The one-year gap, while not ideal, does not itself constitute an ethical failure if no escalation in safety risk occurred during the intervening period.

Grounds

Immediately after Company X rejected the additional safety testing recommendation, no applicable governmental or industry standards existed for the product, no confirmed safety failure had occurred, Engineer A's concerns were grounded in observed performance inconsistencies rather than a documented violation, and no established government forum existed for receiving such concerns. Engineer A resigned and one year later a public safety standards hearing was announced. The question is whether the ethical clock on external escalation began at the moment of employer rejection or at the moment the institutional forum appeared.

Engineer A MedTech BER 08-10 Premature External Reporting Threat Contextual Calibration of Public Safety Reporting Obligation
13 sequenced 7 actions 6 events
Case timeline
Inconsistent safety performance is identified in a new consumer product during or after standard safety testing at Company X. This discovery reveals a potential hazard that standard testing protocols did not fully resolve.
Engineer A observed inconsistent product performance following completed standard safety testing and formally recommended to Supervisor B that Company X conduct a new series of tests to assess consumer safety. This decision was made despite the product having passed existing safety parameters and in the absence of any governing standards specific to the new product.
Fulfills (4)
  • Duty to hold public safety, health, and welfare paramount (NSPE Code)
  • Obligation to notify employer of safety concerns observed in the course of professional work
  • Duty to act within area of professional competence by flagging concerns rather than unilaterally deciding product is unsafe
  • Obligation to use internal channels before pursuing external remedies
Company X's management, through the decision-making process involving Supervisor B and organizational leadership, rejected Engineer A's recommendation to conduct additional safety testing. The rejection was explicitly based on the projected cost of additional testing and the anticipated delay to product launch.
Fulfills (2)
  • Compliance with existing applicable safety standards and testing procedures
  • Exercise of business judgment within legal and regulatory boundaries
Violates (2)
  • Arguably, a broader ethical obligation to proactively investigate credible safety concerns raised by a qualified engineer, even absent regulatory mandate
  • Duty of responsible care toward consumers when a professional engineer has flagged potential unique safety risks
Company X formally rejects Engineer A's recommendation for additional safety testing, citing cost and schedule delay concerns. This institutional decision leaves the safety inconsistency unresolved and Engineer A's professional concern unaddressed.
At an unspecified point after Company X rejected the additional testing recommendation, Engineer A made the volitional decision to resign from employment at Company X. The case does not specify the explicit reasons for resignation, but it occurs in the context of the unresolved safety concern and the rejection of Engineer A's professional recommendation.
Fulfills (2)
  • Protection of personal professional integrity by not continuing association with a product believed to have unresolved safety concerns
  • Implicit recognition that internal remedies had been exhausted at the recommendation level
Violates (2)
  • Arguably, ongoing internal advocacy obligation, resignation ends Engineer A's ability to continue pressing for safety improvements from within the organization
  • Some interpretations of engineering ethics suggest engineers should exhaust all internal escalation paths before disengaging
Engineer A's resignation from Company X takes effect, formally ending the employment relationship and altering Engineer A's legal and ethical standing with respect to company confidential information and safety concerns. This transition changes but does not eliminate Engineer A's professional obligations.
One year after Engineer A's resignation, a government agency publicly announces a safety standards hearing covering the specific product category in question. This exogenous governmental action creates a formal, legitimate public channel through which Engineer A's safety concerns can be officially addressed.
One year after resigning from Company X, upon learning that the relevant government agency announced a public safety standards hearing covering the new product category, Engineer A faces and actively considers the decision of whether to participate as a witness at the hearing. This is the central volitional decision analyzed in the case.
At stake (1)
  • Duty to assess competence boundaries before agreeing to serve as expert witness
Fulfills (2)
  • Duty to consider public safety obligations as a professional engineer when presented with a relevant public forum
  • Obligation to bring safety concerns to appropriate governmental authorities when internal remedies have been exhausted (consistent with BER 76-4)
Engineer A finds themselves in a state of active ethical deliberation about whether to testify at the government safety hearing, a condition triggered by the hearing announcement and their possession of relevant safety knowledge. This is not a decision itself but the resulting state of ethical obligation and deliberation that the hearing announcement produces.
In precedent case BER 76-4, Engineer Doe chose to verbally advise XYZ Corporation of his findings, that the plant's discharge would lower water quality below established standards, before completing a written report, representing a deliberate choice about the form and timing of disclosure to the client.
Fulfills (2)
  • Duty to inform client of material findings relevant to the engagement
  • Honesty and transparency with client about professional conclusions
Violates (1)
  • Arguably, the decision to report only verbally without completing the written report left the findings undocumented and susceptible to suppression
In the precedent case BER 76-4, Engineer Doe's verbal report of findings to the client results in a conflict situation where the client's interests diverge from public safety, setting the stage for Engineer Doe's subsequent external reporting. This outcome establishes the precedent that internal reporting followed by client non-action can justify external disclosure.
In precedent case BER 76-4, upon learning that XYZ Corporation had called a public hearing and presented data supporting its position that discharge met minimum standards, Engineer Doe faced the decision of whether to report his contrary findings to the regulatory authority. The Board concluded this reporting was an ethical obligation.
Fulfills (3)
  • Paramount duty to public safety, health, and welfare (NSPE Code)
  • Obligation to provide truthful information to governmental authorities
  • Duty to correct misleading information before a regulatory body when engineer possesses contrary evidence
Violates (2)
  • Implicit client confidentiality, though the Board determined public safety obligation superseded this
  • Possible contractual constraints from the terminated engagement
In precedent case BER 08-10, after learning one month later that nothing had been done to correct the potentially dangerous respirator valve placement, Engineer A escalated by indicating to the manager that if prompt measures were not taken to correct the problem, Engineer A would be compelled to report the matter to an appropriate federal regulatory agency. The Board found this action premature and unethical.
Fulfills (2)
  • Re-escalation of unresolved safety concern demonstrating persistence in public safety advocacy
  • Urgency of response proportionate to the increasing market exposure of potentially dangerous devices
Violates (3)
  • Obligation to exhaust internal remedies before threatening external action (per Board's analysis)
  • Duty to inquire about and understand internal processes before bypassing them
  • Professional obligation to use measured escalation rather than coercive threats
Narrative (4 main characters)
View Extraction
Opening Context

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

You are Engineer A, a professional engineer who recently resigned from Company X after working on the design and manufacturing of a new consumer product. During and after the company's standard safety testing process, you observed inconsistent product performance issues that you believe raise unique safety concerns not addressed by any current national, governmental, or industry standards. You brought these concerns to Supervisor B and recommended additional testing, but Company X rejected that recommendation citing cost and schedule impacts. One year after your resignation, the relevant government agency has announced a public safety standards hearing covering this product category, including the product developed by Company X. You are now considering whether and how to participate as a witness in that proceeding. The decisions ahead involve your obligations to public safety, the boundaries of post-employment disclosure, and the conditions under which your technical knowledge may appropriately inform a regulatory process.

Main characters (4)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Company X Roles in this case: Safety-Rejecting Manufacturing Employer Current CaseSafety-Rejecting Manufacturing Employer

Guided by: Regulatory Gap Safety Escalation Obligation, Graduated Internal Escalation Before External Reporting Obligation, Public Welfare Paramount

Tension between Company X Safety Testing Rejection Ethical Violation and Company X Employer Reasonableness Recognition Absent Standards Context

Attaches to role: Safety-Rejecting Manufacturing Employer Current Case

Engineer A is obligated not to simply acquiesce when Company X rejects safety recommendations on cost grounds, implying a duty to escalate or resist. However, the constraint recognizes that where no binding regulatory standards exist, an employer's cost-based rejection of additional safety testing may not constitute a clear ethical violation, limiting the moral and professional basis for escalation. This creates a genuine dilemma: the engineer feels compelled to push back against what appears to be a safety compromise, yet the absence of codified standards weakens the ethical footing for treating the employer's decision as wrongful, potentially making escalation appear insubordinate rather than principled.

Attaches to role: Safety-Rejecting Manufacturing Employer

Engineer A has a genuine duty to participate in government safety hearings to protect the public, yet simultaneously bears a continuing obligation not to disclose proprietary or confidential information acquired during employment at Company X. Meaningful testimony about product safety concerns may be impossible to deliver without drawing on specific technical knowledge that is proprietary, creating a direct conflict where fulfilling one duty substantively undermines the other. The engineer cannot fully serve the public interest without risking breach of confidentiality, and cannot fully honor confidentiality without withholding safety-relevant information from a government authority.

Attaches to role: Safety-Rejecting Manufacturing Employer

When regulatory standards are absent, Engineer A faces a heightened obligation to escalate safety concerns precisely because no external authority is enforcing minimum thresholds. Yet the constraint holds that a good-faith safety concern, absent a demonstrable regulatory or ethical violation, has a bounded permissible escalation path — the engineer cannot treat subjective concern alone as sufficient justification for aggressive external reporting or whistleblowing. The regulatory vacuum simultaneously amplifies the moral urgency to act and removes the objective benchmark that would legitimize strong escalatory action, trapping the engineer between under-reacting and overstepping.

Attaches to role: Safety-Rejecting Manufacturing Employer
Engineer A Roles in this case: Current Case Post-Employment Public Safety Standards WitnessConsumer Product Safety Design EngineerPost-Employment Public Safety Standards WitnessBER 08-10 MedTech Respirator Safety EngineerCurrent Case Consumer Product Safety Design Engineer

Tension between Engineer A MedTech BER 08-10 Premature External Reporting Threat and Contextual Calibration of Public Safety Reporting Obligation

Attaches to role: Current Case Post-Employment Public Safety Standards Witness

Engineer A is obligated not to simply acquiesce when Company X rejects safety recommendations on cost grounds, implying a duty to escalate or resist. However, the constraint recognizes that where no binding regulatory standards exist, an employer's cost-based rejection of additional safety testing may not constitute a clear ethical violation, limiting the moral and professional basis for escalation. This creates a genuine dilemma: the engineer feels compelled to push back against what appears to be a safety compromise, yet the absence of codified standards weakens the ethical footing for treating the employer's decision as wrongful, potentially making escalation appear insubordinate rather than principled.

Attaches to role: Consumer Product Safety Design Engineer

Engineer A has a genuine duty to participate in government safety hearings to protect the public, yet simultaneously bears a continuing obligation not to disclose proprietary or confidential information acquired during employment at Company X. Meaningful testimony about product safety concerns may be impossible to deliver without drawing on specific technical knowledge that is proprietary, creating a direct conflict where fulfilling one duty substantively undermines the other. The engineer cannot fully serve the public interest without risking breach of confidentiality, and cannot fully honor confidentiality without withholding safety-relevant information from a government authority.

Attaches to role: Post-Employment Public Safety Standards Witness

When regulatory standards are absent, Engineer A faces a heightened obligation to escalate safety concerns precisely because no external authority is enforcing minimum thresholds. Yet the constraint holds that a good-faith safety concern, absent a demonstrable regulatory or ethical violation, has a bounded permissible escalation path — the engineer cannot treat subjective concern alone as sufficient justification for aggressive external reporting or whistleblowing. The regulatory vacuum simultaneously amplifies the moral urgency to act and removes the objective benchmark that would legitimize strong escalatory action, trapping the engineer between under-reacting and overstepping.

Attaches to role: Consumer Product Safety Design Engineer
Supervisor B Roles in this case: Engineering Employer Representative

Engineer A is obligated not to simply acquiesce when Company X rejects safety recommendations on cost grounds, implying a duty to escalate or resist. However, the constraint recognizes that where no binding regulatory standards exist, an employer's cost-based rejection of additional safety testing may not constitute a clear ethical violation, limiting the moral and professional basis for escalation. This creates a genuine dilemma: the engineer feels compelled to push back against what appears to be a safety compromise, yet the absence of codified standards weakens the ethical footing for treating the employer's decision as wrongful, potentially making escalation appear insubordinate rather than principled.

When regulatory standards are absent, Engineer A faces a heightened obligation to escalate safety concerns precisely because no external authority is enforcing minimum thresholds. Yet the constraint holds that a good-faith safety concern, absent a demonstrable regulatory or ethical violation, has a bounded permissible escalation path — the engineer cannot treat subjective concern alone as sufficient justification for aggressive external reporting or whistleblowing. The regulatory vacuum simultaneously amplifies the moral urgency to act and removes the objective benchmark that would legitimize strong escalatory action, trapping the engineer between under-reacting and overstepping.

Engineer Doe Roles in this case: BER 76-4 Pollution Consulting Engineer

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

Engineer A has a genuine duty to participate in government safety hearings to protect the public, yet simultaneously bears a continuing obligation not to disclose proprietary or confidential information acquired during employment at Company X. Meaningful testimony about product safety concerns may be impossible to deliver without drawing on specific technical knowledge that is proprietary, creating a direct conflict where fulfilling one duty substantively undermines the other. The engineer cannot fully serve the public interest without risking breach of confidentiality, and cannot fully honor confidentiality without withholding safety-relevant information from a government authority.

When regulatory standards are absent, Engineer A faces a heightened obligation to escalate safety concerns precisely because no external authority is enforcing minimum thresholds. Yet the constraint holds that a good-faith safety concern, absent a demonstrable regulatory or ethical violation, has a bounded permissible escalation path — the engineer cannot treat subjective concern alone as sufficient justification for aggressive external reporting or whistleblowing. The regulatory vacuum simultaneously amplifies the moral urgency to act and removes the objective benchmark that would legitimize strong escalatory action, trapping the engineer between under-reacting and overstepping.


These tensions did not map cleanly to a single character.

Tension between Post-Employment Public Safety Testimony Participation Obligation and Post-Employment Confidentiality Agreement Compliance in Public Testimony Obligation

Tension between Post-Employment Public Safety Testimony Participation Obligation and Post-Employment Confidentiality Agreement Compliance in Public Testimony

Tension between Good Faith General Safety Concern Public Hearing Participation Obligation and Contextual Calibration of Public Safety Reporting Obligation

Opening States (10)
Engineer A Post-Employment Witness Participation Consideration Internal Escalation Pathway Exhaustion Assessment State Good Faith Safety Concern Without Demonstrable Violation State Completed Safety Testing with Residual Concern State Regulatory Standards Vacuum for Novel Product State Post-Employment Safety Concern Witness Participation State Client Safety Recommendation Rejection Without Standards Basis State Engineer A Residual Safety Concern Post-Testing Novel Consumer Product Regulatory Standards Vacuum Company X Cost-Driven Rejection of Additional Safety Testing
Summary
  • Post-employment confidentiality agreements do not categorically override an engineer's ethical obligation to participate in public safety proceedings when they possess relevant expertise.
  • The ethical permissibility of post-employment public testimony hinges on the quality and independence of the engineer's knowledge — specifically whether it derives from general professional expertise rather than exclusively from proprietary employer information.
  • Engineers must calibrate their public safety disclosures contextually, distinguishing between good-faith general safety concerns and disclosures that would constitute a breach of legitimate confidentiality obligations.