Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Whistleblowing
Step 4 of 5

153

Entities

2

Provisions

2

Precedents

14

Questions

14

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A is locked in an unresolved standoff with his employer: he retains a permissive right to keep raising concerns, but no mandatory duty compels him to escalate, while the employer retains authority to reject his recommendations and even retaliate (memorandum, probation) without the Board condemning this. Neither obligation is transferred to a new party (no external authority takes over), no phase alternation occurs, and no hidden fact later resolves the conflict—the parties remain fixed in their original, incompatible positions.
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 (2)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

II.1.a board + analysis 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 22)
Obligation
Engineer A Deficiency Reporting Duty
This provision requires notifying employer and appropriate authority when judgment is overruled endangering life or property matching the reporting duty
Action
Deficiency Reporting
Notifying authority of deficiencies aligns with duty to report when judgment is overruled on safety matters
State
Engineer A Management Disagreement
This provision requires notifying employer and authorities when judgment is overruled which relates to the disagreement with management
Obligation (2)
  • Engineer A Deficiency Reporting Duty
    This provision requires notifying employer and appropriate authority when judgment is overruled endangering life or property matching the reporting duty
  • Engineer A Conditional Withdrawal Duty
    This provision requires notification to other authority when overruled judgment endangers public safety consistent with the conditional duty
Action (5)
  • Deficiency Reporting
    Notifying authority of deficiencies aligns with duty to report when judgment is overruled on safety matters
  • Continued Internal Advocacy
    Persisting internally reflects the duty to notify employer when judgment is overruled
  • Critical Memorandum Filing
    Filing a memorandum documents notification to employer of overruled safety judgment
  • Ethical Review Request
    Requesting review is a form of notifying appropriate authority as required
  • Continued Insistence
    Continuing to insist reflects fulfilling the duty to notify employer of overruled judgment
State (3)
  • Engineer A Management Disagreement
    This provision requires notifying employer and authorities when judgment is overruled which relates to the disagreement with management
  • Absent Public Safety Danger Finding
    This provision only applies when circumstances endanger life or property so its relevance depends on this safety finding
  • Subcontractor Submission Deficiency Finding
    The deficiency finding may represent the overruled judgment situation requiring notification to appropriate authority
Constraint (2)
  • Engineer A Withdrawal Duty Scope
    This provision defines the notification duty that the constraint clarifies does not create a blanket withdrawal obligation
  • Engineer A Rejected Recommendation Boundary
    This provision governs notifying authority when judgment is overruled, bounding how far Engineer A must press rejected recommendations
Principle (2)
  • Public Welfare in Defense Spending
    Engineer A notified superiors of subcontractor deficiencies affecting proper performance.
  • Public Welfare Defense Expenditures
    The provision requires notifying appropriate authority even when issue involves waste rather than direct safety.
Role (1)
  • Engineer A Review Engineer
    He must notify employer or other authority if his engineering judgment is overruled in circumstances endangering life or property
Event (2)
  • Disagreement Persistence
    This provision requires notification when engineering judgment is overruled and disagreement continues
  • Employment Jeopardy Onset
    The provision mandates notifying appropriate authority even if it risks employment consequences
Resource (2)
  • BER Case 65-12
    Both address engineers refusing to participate in unsafe or improper practices and notifying appropriate authority
  • BER Case 61-10
    Both consider when overruled engineering judgment is an ethical duty versus a business decision
Capability (3)
  • Engineer A Deficiency Disclosure
    This provision requires notifying employer and other authorities when judgment is overruled which matches Engineer A's memoranda disclosures
  • Engineer A Endangerment Threshold Distinction
    The provision's duty to notify is conditioned on endangerment which requires the capability to discern such endangerment
  • Board Precedent Distinction Reasoning
    The Board's precedent reasoning interprets when the duty to notify under this provision is triggered by endangerment
III.2.b board + analysis Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project.
How this applies in the case (showing 3 of 19)
Obligation
Engineer A Conditional Withdrawal Duty
This provision mandates withdrawal and reporting to proper authorities if employer insists on nonconforming plans matching the withdrawal duty
Action
Recommendation Rejection
Rejection of recommendation relates to employer insisting on unprofessional conduct
State
Subcontractor Submission Deficiency Finding
This provision prohibits certifying plans not conforming to standards which relates directly to the deficiency finding
Obligation (1)
  • Engineer A Conditional Withdrawal Duty
    This provision mandates withdrawal and reporting to proper authorities if employer insists on nonconforming plans matching the withdrawal duty
Action (3)
  • Recommendation Rejection
    Rejection of recommendation relates to employer insisting on unprofessional conduct
  • Deficiency Reporting
    Reporting deficiencies aligns with notifying proper authorities of nonconforming plans
  • Ethical Review Request
    Seeking review corresponds to notifying proper authorities as required by this provision
State (2)
  • Subcontractor Submission Deficiency Finding
    This provision prohibits certifying plans not conforming to standards which relates directly to the deficiency finding
  • Engineer A Management Disagreement
    This provision requires withdrawal from service if employer insists on unprofessional conduct relating to the management conflict
Constraint (2)
  • Engineer A Withdrawal Duty Scope
    This provision mandates withdrawal only when unprofessional conduct is insisted upon, which the constraint says does not apply here
  • Engineer A Rejected Recommendation Boundary
    This provision limits the duty to withdraw and report to cases of nonconforming plans, bounding Engineer A's further insistence
Principle (1)
  • Public Welfare in Defense Spending
    Engineer A urged rejection of deficient work that did not conform to applicable standards.
Role (1)
  • Engineer A Review Engineer
    He must refuse to approve deficient plans and notify proper authorities if the employer insists on unprofessional conduct
Event (2)
  • Deficiency Discovery
    This provision addresses discovery of nonconforming plans or specifications
  • Disagreement Persistence
    The provision requires withdrawal and notification if the employer insists on unprofessional conduct despite disagreement
Resource (3)
  • Subcontract Equipment Specifications
    The provision requires conformity with applicable specifications for equipment on the project
  • BER Case 65-12
    Both address refusal to sign off or participate in production not meeting proper standards
  • NSPE Code of Ethics
    This provision is itself part of the duty regarding plans not safe to public health and welfare
Capability (4)
  • Engineer A Submission Adequacy Review
    This provision requires engineers not to approve nonconforming plans which relates directly to Engineer A's review of subcontractor submissions
  • Engineer A Deficiency Disclosure
    The provision requires notifying proper authorities of nonconforming plans which matches Engineer A's disclosure actions
  • Engineer A Endangerment Threshold Distinction
    The provision's withdrawal and reporting duty depends on assessing whether nonconformity constitutes unprofessional or unsafe conduct
  • Board Precedent Distinction Reasoning
    The Board distinguishes precedent cases to determine when the duty to withdraw under this provision applies
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

Engineers who hold a genuine belief that a product is unsafe are ethically justified in refusing to participate in its processing or production, even though this may lead to loss of employment.

Citation Context:

Cited to establish that engineers who believe a product is unsafe are ethically justified in refusing to participate in its production, even at risk of job loss, but the current case is distinguished because it does not involve public safety.

Relevant Excerpts
discussion: "In Case 65-12 we dealt with a situation in which a group of engineers believed that a product was unsafe, and we determined that so long as the engineers held to that view they were ethically justified in refusing to participate in the processing or production of the product in question."

Principle Established:

When engineers object to a business/design decision that does not entail any question of public health or safety, this is a business decision for management and does not entitle engineers to challenge it on ethical grounds.

Citation Context:

Cited as a directly analogous precedent where engineers objected to a redesign decision not involving public health or safety, supporting the conclusion that such matters are business decisions for management.

Relevant Excerpts
discussion: "In Case 61-10 we distinguished a situation in which engineers had objected to the redesign of a commercial product, but which did not entail any question of public health or safety. On that basis we concluded that this was a business decision for management and did not entitle the engineers to question the decision on ethical grounds."
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 54% Facts Similarity 46% Discussion Similarity 57% Outcome Alignment 100% Tag Overlap 100%
Same outcome unclear View Synthesis
Component Similarity 59% Facts Similarity 45% Discussion Similarity 73% Outcome Alignment 100% Tag Overlap 50%
Same outcome unclear View Synthesis
Component Similarity 57% Facts Similarity 48% Discussion Similarity 70% Outcome Alignment 100% Tag Overlap 50%
Same outcome unclear View Synthesis
Component Similarity 68% Facts Similarity 64% Discussion Similarity 82% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 57% Facts Similarity 46% Discussion Similarity 56% Outcome Alignment 100% Tag Overlap 20%
Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 29% Discussion Similarity 62% Outcome Alignment 100% Tag Overlap 25%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 56% Discussion Similarity 68% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 57% Facts Similarity 37% Discussion Similarity 31% Outcome Alignment 100% Tag Overlap 12%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 46% Discussion Similarity 28% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 47% Discussion Similarity 60% Outcome Alignment 100% Tag Overlap 11%
Same outcome unclear View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Does Engineer A have an ethical obligation, or an ethical right, to continue his efforts to secure change in the policy of his employer under these circumstances, or to report his concerns to proper authority?

Board conclusion Engineer A does not have an ethical obligation to continue his effort to secure a change in the policy of his employer under these circumstances, or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience.
Resolved by: The Board weighed Engineer A's personal conscience interest in continued advocacy against the absence of a codified duty, resolving the tension by demoting the matter from obligation to right because the triggering condition (safety endangerment) of the mandatory reporting provision was not met. (confidence 0.85)
II.1.a. 3 principles 3 facts Conditions Narrative
Implicit (2)

Does the absence of a finding that public safety is endangered fundamentally change Engineer A's ethical obligations compared to a case involving safety risk, even though substantial public (defense) funds are at stake?

AnalyticalThe Board's conclusion rests on a threshold distinction embedded in Code provision II.1.a: the mandatory duty to report overruled judgment applies only when life or property is endangered. Because Engineer A's concern was economic waste and schedule delay rather than a safety hazard, his situation falls outside the triggering condition of that provision, which explains why the Board characterizes his continued advocacy as a right of conscience rather than a codified obligation. This suggests the Code's reporting duty is calibrated specifically to physical risk, not to fiscal stewardship, even where the funds involved are substantial public defense expenditures.
Resolved by: The Board privileged the textual endangerment threshold of II.1.a over the magnitude of the public funds at stake, treating fiscal stewardship as insufficient by itself to trigger the mandatory duty even though it otherwise engages public welfare concerns. (confidence 0.85)
II.1.a. 2 principles 3 facts Conditions Narrative
AnalyticalQ101: The absence of a finding that public safety is endangered is the pivotal fact that shifts this case from the domain of mandatory reporting under Code II.1.a to the domain of discretionary conscience. Even though substantial defense funds are implicated, the Code's reporting obligation is textually and structurally tied to endangerment of life or property, not to economic waste. Thus the case is fundamentally different from safety cases, and Engineer A's obligations are correspondingly diminished from a duty to a right.
Resolved by: The Board treated the endangerment finding as the pivotal fact that reallocates the case from the mandatory-reporting domain to the discretionary-conscience domain, subordinating the economic significance of defense spending to the textual scope of II.1.a. (confidence 0.85)
II.1.a. 2 principles 3 facts Conditions Narrative

Is Engineer A's continued insistence on redesign, after management has rejected his recommendation, an overreach into a business/management decision rather than a legitimate technical or ethical objection, similar to the distinction drawn in Case 61-10?

AnalyticalOnce management formally rejected Engineer A's redesign recommendation, the matter arguably shifted from a technical/ethical determination within Engineer A's professional purview to a business decision reserved to management, paralleling the reasoning in Case 61-10. This reframing does not negate Engineer A's right to keep raising the issue, but it clarifies why the Board declines to elevate his continued insistence into an ethical obligation: engineers do not have an unlimited mandate to override management's final allocation-of-resources decisions once those decisions have been made through the proper corporate channels, absent a safety endangerment finding.
Resolved by: The Board balanced Engineer A's continuing technical conviction against management's prerogative to make final resource-allocation decisions, favoring managerial finality absent a safety trigger while preserving the engineer's residual right to keep raising the issue. (confidence 0.75)
II.1.a. 2 principles 3 facts Conditions Narrative
Principle tension (3)

How should Public Welfare in Defense Spending be balanced against Personal Conscience in Whistleblowing when the concern raised is economic waste rather than a direct threat to life or property?

AnalyticalQ201/Q301: Analyzed deontologically, Code II.1.a creates a conditional duty whose triggering condition (endangerment of life or property) is not met here; therefore Engineer A cannot be said to have failed a deontological duty of reporting. His continued advocacy is instead better understood as an exercise of a moral permission grounded in professional conscience rather than a categorical imperative arising from the Code itself.
Resolved by: Because the deontological trigger condition for a reporting duty is absent, the competing pull of public welfare concerns is reclassified as a permissible conscience-based action rather than a binding obligation. (confidence 0.82)
II.1.a. 3 principles 3 facts Conditions Narrative
AnalyticalThe Code's explicit trigger for a mandatory reporting obligation under II.1.a is endangerment to life or property. Because the Board found no such danger present—only economic waste in the form of excessive cost and time delays on defense contracts—Public Welfare in Defense Spending was not treated as invoking the same mandatory force as public safety would. This effectively subordinates economic public welfare concerns to a lower tier of ethical urgency than physical safety concerns, even though both involve the public interest and substantial public funds. The tension is resolved not by balancing the two principles against each other, but by threshold-gating: only safety-endangerment crosses into obligation, while cost/efficiency concerns remain in the domain of discretionary conscience.
Resolved by: Rather than balancing economic public welfare against safety concerns on a continuum, the board applied a threshold gate so that only safety-endangerment crosses into mandatory obligation while cost concerns remain discretionary. (confidence 0.85)
II.1.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C303

Does Public Welfare Defense Expenditures create an obligation that competes with the Engineer A Rejected Recommendation Boundary, which limits an engineer's authority once management has made a final decision on a subcontractor's work?

AnalyticalThe Engineer A Rejected Recommendation Boundary and Public Welfare Defense Expenditures principle are placed in tension once management makes a final decision on a subcontractor's work, but the Board resolves this by analogy to Case 61-10, treating the matter as a business/management decision after Engineer A's technical concerns were heard and considered. This shows that Public Welfare Defense Expenditures does not override managerial authority once due process (memoranda exchange, internal review) has occurred internally; the principle competes with, but does not defeat, the employer's decision-making boundary. However, this resolution stops short of extending to Case 65-12's treatment of unsafe production refusal, since that precedent involved life/property endangerment rather than cost/schedule disagreement, marking a clear prioritization: safety-related principles displace managerial boundaries, but economic-welfare principles do not.
Resolved by: The board weighed the engineer's continuing technical objection against management's final authority and favored managerial deference once due process had occurred internally, but distinguished this from safety cases where such deference would not apply. (confidence 0.75)
2 principles 3 facts Conditions Narrative

How is the tension resolved between treating whistleblowing as a matter of Personal Conscience in Whistleblowing (a right) versus the precedent in Case 65-12 where refusal to participate in unsafe production was treated as ethically justified conduct approaching an obligation?

AnalyticalQ203: Case 65-12 is distinguishable rather than controlling: there, refusal to participate in producing an unsafe product was treated as ethically justified because participation risked direct physical harm to end users. Here, Engineer A's objection concerns cost and schedule inefficiency, not safety, so the heightened ethical weight given to refusal-based conduct in 65-12 does not transfer with equal force. The tension is resolved by recognizing a sliding scale: as the stakes shift from safety to economics, the ethical status of persistence shifts correspondingly from near-obligation toward discretionary right.
Resolved by: The board weighs the type of stake at issue, safety versus economics, and lets that determine whether persistence sits closer to obligation or to discretionary right. (confidence 0.78)
2 principles 3 facts Conditions Narrative
AnalyticalPersonal Conscience in Whistleblowing emerges as the dominant organizing principle once the safety threshold is not met: it absorbs the residual ethical space left after Public Welfare Defense Expenditures fails to generate an obligation. Rather than being weighed against competing obligations, conscience functions as a permissive fallback right, allowing Engineer A to continue advocacy without being ethically compelled to do so. This suggests a hierarchy in the Board's reasoning: mandatory Code duties (tied to safety) sit at the top, business/managerial authority (post-decision) sits next, and personal conscience operates as a permissive residual category that fills the space where neither mandatory duty nor managerial deference fully resolves the engineer's dilemma.
Resolved by: Personal conscience was not weighed as a competing obligation against mandatory duty or managerial authority but installed as a permissive residual right occupying the space left open once neither of those resolved the dilemma. (confidence 0.75)
II.1.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C302
Theoretical (3)

From a deontological perspective, did Engineer A fulfill the duty of reporting under Code provision II.1.a, given that this duty is explicitly triggered only when overruled judgment endangers life or property?

Also discussed in: C203

From a consequentialist perspective, did the potential outcome of saving substantial defense expenditures justify Engineer A's continued insistence and internal advocacy despite the risk of losing his job?

From a virtue-ethics perspective, did Engineer A act with professional integrity by persisting in his objections through repeated memoranda even after management rejected his recommendations and placed him on probation?

Counterfactual (3)

If the subcontractor's deficient submissions had posed a danger to public safety rather than merely representing excessive cost and time delays, would the Board still have concluded that Engineer A had no ethical obligation to report his concerns to proper authority?

AnalyticalQ401: If the subcontractor's deficiencies had posed a genuine danger to public safety, the Board's analysis would very likely have shifted from framing Engineer A's conduct as an optional exercise of conscience to recognizing an affirmative obligation under II.1.a to report to proper authority, since that provision is explicitly triggered by endangerment to life or property. The presence of a safety threat would also strengthen the case for treating continued advocacy as ethically compulsory rather than merely permissible, aligning the case more closely with the reasoning in Case 65-12.
Resolved by: The board treats the presence or absence of safety endangerment as the deciding factor that shifts the balance from a permissive conscience right to an affirmative reporting obligation. (confidence 0.75)
II.1.a. 2 principles 3 facts Conditions Narrative

If management had not placed a critical memorandum in Engineer A's file or put him on probation, would the Board's characterization of his continued advocacy as merely a 'personal conscience' right rather than an obligation still hold?

Also discussed in: C207

If Engineer A's dispute concerned a commercial redesign decision analogous to Case 61-10 rather than a defense subcontractor's specification compliance, would the Board still frame his course of action as an ethical matter rather than purely a business decision for management?

AnalyticalQ403: Because Engineer A's dispute concerns compliance with defense subcontract specifications rather than a purely commercial redesign preference, it retains an ethical dimension that Case 61-10 did not require the Board to recognize. Unlike 61-10, where the disagreement was framed as a business judgment call belonging to management, Engineer A's objections implicate specification conformity and stewardship of public defense funds, which keeps his conduct within the ethical review's proper scope even though management's final business decision remains authoritative once made.
Resolved by: The board balances management's authority over final business decisions against the ethical stake in specification conformity and public fund stewardship, preserving ethical review scope without displacing management's ultimate authority. (confidence 0.77)
3 principles 3 facts Conditions Narrative
Analytical questions (2)

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

Implicit (2)

Does Engineer A's role in reviewing and certifying the adequacy of subcontractor submissions impose a professional duty under the Code not to approve or acquiesce in specifications he believes are deficient, independent of whether he has a right to whistleblow?

AnalyticalQ102: Engineer A's professional duty under III.2.b not to approve or certify specifications he believes are deficient is independent of, and logically prior to, any question of whistleblowing. As the reviewing engineer, he satisfied this duty simply by refusing to certify the subcontractor's submission as adequate and by documenting his objections in memoranda. This technical/certification duty is fully discharged once he declines to sign off; it does not itself generate a further obligation to escalate the matter externally or to continue pressing management once his professional judgment has been formally overruled.
Resolved by: The certification duty and any external reporting duty are treated as separate obligations, so satisfying the former does not require satisfying the latter. (confidence 0.80)
III.2.b. 2 principles 3 facts Conditions Narrative

What ethical responsibility, if any, does the employer bear for placing a critical memorandum in Engineer A's file and imposing probation in response to his good-faith technical objections, and does this retaliatory environment affect the scope of Engineer A's ethical obligations?

AnalyticalThe Board's silence on the propriety of the employer's retaliatory measures—placing a critical memorandum in Engineer A's file and imposing probation—implies that such employer conduct, even if arguably harsh given Engineer A's good-faith technical objections, does not itself convert Engineer A's right of conscience into an ethical obligation to persist or to escalate externally. However, this gap leaves open a distinct question of employer ethics: whether retaliating against an engineer who raises good-faith, code-consistent concerns about subcontractor compliance is itself ethically problematic, independent of whether Engineer A had a duty to continue his advocacy.
Resolved by: The Board implicitly separated the question of Engineer A's obligations from the question of employer retaliation, declining to let the harshness of the employer's response either strengthen Engineer A's duty or resolve the separate issue of employer ethics. (confidence 0.60)
II.1.a. 2 principles 3 facts Conditions Narrative
AnalyticalQ104/Q402: The employer's act of placing a critical memorandum in Engineer A's file and imposing probation in response to good-faith technical objections raises separate concerns about retaliatory treatment of engineers who exercise their professional judgment, but it does not by itself convert Engineer A's continued advocacy into an ethical obligation. Even absent this adverse employment action, the underlying triggering condition for a reporting duty under II.1.a (danger to life or property) would still be missing, so the Board's characterization of his course of action as a matter of personal conscience would likely remain unchanged.
Resolved by: The board treated retaliation as a separate wrong worth flagging but did not let it substitute for the missing safety trigger that would otherwise convert conscience into obligation. (confidence 0.80)
II.1.a. 2 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A continue his campaign for change and reporting to proper authority as a matter of personal conscience, or is he ethically obligated to do so under the circumstances?

Options considered:
O1 Keep pressing management internally about the subcontractor deficiencies as an exercise of personal conscience, understanding this is a right rather than a duty. Board's choice
O2 Escalate the deficiency concerns outside the company to a proper external authority given the substantial defense expenditures at stake.
O3 Stop raising the issue and accept management's final decision on the subcontractor submissions to preserve employment.
Argument structure (Toulmin):
Grounds

Engineer A discovered deficiencies in subcontractor submissions, filed memoranda, faced persistent disagreement with management, had his recommendations rejected, received a critical memorandum, was placed on probation, and continued his internal advocacy despite these actions.

Warrant

Engineers must withdraw from a project and report to proper authorities when circumstances endanger public health, safety, and welfare; absent such endangerment, whether to continue advocacy or make the issue public is a matter of personal conscience rather than codified duty.

Rebuttal

Would not apply if the subcontractor's deficiencies posed an actual danger to public safety, since Code II.1.a mandates withdrawal and reporting in that circumstance rather than leaving the matter to discretion.

Engineer A Conditional Withdrawal Duty Engineer A Withdrawal Duty Scope

Should Engineer A discharge his review duty by refusing to certify and documenting objections in memoranda, or does he need to escalate the matter externally to fully meet his professional obligation?

Options considered:
O1 Refuse to certify the subcontractor's submissions as adequate and record objections in memoranda to superiors. Board's choice
O2 Take the deficiency findings outside the company once management rejects the recommendation, treating internal documentation as insufficient.
O3 Certify the submission as directed by management while privately recording reservations, treating the certification decision as management's prerogative.
Argument structure (Toulmin):
Grounds

Engineer A was assigned to review the adequacy of subcontractor plans, found deficiencies in the submissions, and advised his superiors of the problems through memoranda recommending rejection and correction.

Warrant

Engineers must advise superiors of problems found in reviewed work and must not approve or certify work they believe fails to conform to applicable specifications.

Rebuttal

Would not apply if the deficiency endangered public safety, in which case a further duty to withdraw and report to proper authorities would attach beyond mere non-certification.

Engineer A Deficiency Reporting Duty

Should Engineer A continue to insist on rejection and redesign after management's rejection, or accept that the matter has become a business decision reserved to management?

Options considered:
O1 Voice objections through memoranda, then accept management's final rejection of the recommendation as a legitimate business decision. Board's choice
O2 Keep pressing for rejection and redesign of the subcontractor's work even after management's decision and disciplinary action.
O3 Comply with management's operational decision while requesting a formal ethics review of the underlying specification compliance issue.
Argument structure (Toulmin):
Grounds

Management rejected Engineer A's recommendation to reject and redesign the subcontractor's submissions; Engineer A continued to insist on redesign; he subsequently received a critical memorandum and was placed on probation.

Warrant

Management retains authority over final resource-allocation and business decisions once an engineer's technical concerns have been heard through proper channels, and this authority prevails over further insistence absent a safety endangerment finding.

Rebuttal

Would not apply if the rejected recommendation involved endangerment to public safety, in which case Engineer A's continued persistence would be ethically justified rather than an overreach into management's domain.

Engineer A Deficiency Reporting Duty Engineer A Rejected Recommendation Boundary

Should Engineer A treat his continued advocacy about wasted defense expenditures as a discretionary matter of personal conscience, or as equivalent in urgency to a mandatory safety-based reporting duty?

Options considered:
O1 Continue or discontinue advocacy about the defense expenditure waste as a personal choice, recognizing no mandatory duty applies absent a safety finding. Board's choice
O2 Treat the wasted defense expenditures as carrying the same mandatory reporting force as a safety endangerment, requiring escalation.
O3 Stop advocating altogether once management has rejected the recommendation, since no safety issue has been found to justify further action.
Argument structure (Toulmin):
Grounds

Substantial defense expenditures were implicated by the subcontractor deficiencies, no finding of danger to life or property was made, and Engineer A continued his internal advocacy despite a critical memorandum and probation.

Warrant

The Code's mandatory reporting duty under II.1.a is triggered specifically by endangerment of life or property; ethical concern for substantial public or defense expenditures exists but does not carry the same mandatory force as a safety-based duty.

Rebuttal

Would not apply if the excessive cost and time delays were shown to result in equipment defects endangering public safety, which would elevate the matter to the mandatory reporting threshold.

Engineer A Conditional Withdrawal Duty Engineer A Withdrawal Duty Scope

Should the employer impose disciplinary measures such as a critical memorandum and probation on Engineer A for his continued insistence, or address his concerns without disciplinary action?

Options considered:
O1 Place a critical memorandum in the employee's file and impose probation in response to continued insistence after a rejected recommendation. Board's choice
O2 Address the engineer's technical objections through further internal dialogue rather than disciplinary action.
O3 Conduct a formal internal investigation into the specification compliance concerns before deciding whether discipline is warranted.
Argument structure (Toulmin):
Grounds

A critical memorandum was filed in Engineer A's employment record and probation was imposed after he continued to insist on his rejected recommendation regarding subcontractor submissions.

Warrant

Management may exercise disciplinary authority over employees who continue to press decisions already made through proper channels, but retaliating against good-faith, Code-consistent technical objections raises separate ethical concerns not fully resolved by the Board.

Rebuttal

Would not apply if the disciplinary action were shown to be retaliation for good-faith reporting protected under the Code, in which case the employer's conduct would itself be ethically improper.

Engineer A Deficiency Reporting Duty Engineer A Rejected Recommendation Boundary
Event Timeline (10)
10 sequenced 7 actions 3 events
Case timeline
During his assigned review of subcontractor plans, Engineer A found problems with certain submissions of one of the subcontractors, including deficiencies he judged to involve excessive cost and time delays.
State changes (1)
  • began: Subcontractor Submission Deficiency Finding
Engineer A advised his superiors by memoranda of problems he found with a subcontractor's submissions and urged management to reject the work and require correction of the deficiencies.
Fulfills (1)
  • Obligation to Ensure Subcontractor Compliance with Specifications
Causal-normative reasoning(confidence 0.80)
A2's Deficiency Reporting fulfills the Obligation to Ensure Subcontractor Compliance with Specifications and is guided by the Public Welfare Principle, which matters because this single act of professional diligence triggers the entire downstream causal chain, from Recommendation Rejection through Probation Imposition to Employment Jeopardy Onset, making it the ethically justified origin point of a conflict that Management's later actions do not similarly justify.
State changes (1)
  • began: Engineer A Management Disagreement
Management rejected Engineer A's comments, particularly his proposal that the work of a particular subcontractor be redesigned based on his claims of excessive cost and time delays.
Causal-normative reasoning(confidence 0.60)
A3's Recommendation Rejection carries no fulfillment, violation, or guiding principle, indicating that Management's dismissal of the safety concern is normatively unanchored, yet it is causally pivotal because it directly provokes Engineer A's Continued Internal Advocacy and sets in motion the disagreement that ultimately jeopardizes his employment.
State changes (1)
  • began: Engineer A Management Disagreement
Engineer A continued pressing his objections through further exchanges of memoranda with his management superiors despite management's rejection of his position.
Causal-normative reasoning(confidence 0.60)
A4's Continued Internal Advocacy, guided by the Public Welfare Principle and Personal Conscience without fulfilling or violating any specific obligation, represents Engineer A's ethically motivated persistence that causes Disagreement Persistence and thus indirectly leads to the punitive Critical Memorandum and Probation, underscoring the cost of principled advocacy in the face of institutional resistance.
State changes (1)
  • began: Engineer A Management Disagreement
After the exchange of further memoranda, the disagreement between Engineer A and his management superiors on the issues he raised persisted rather than resolving, setting the conditions for management's escalating personnel measures.
Management placed a critical memorandum in Engineer A's personnel file after continued disagreement over the issues he raised.
Causal-normative reasoning(confidence 0.60)
A5's Critical Memorandum Filing, lacking any fulfillment, violation, or guiding principle, marks Management's retaliatory response to unresolved disagreement and is normatively significant mainly for its consequences, since it directly causes Probation Imposition and subsequent Employment Jeopardy Onset, revealing an asymmetry where Engineer A's principled actions are met with unjustified institutional punishment.
State changes (1)
  • began: Memoranda Disclosure to Superiors
Management placed Engineer A on three months' probation with the notation that if his job performance did not improve he would be terminated.
Causal-normative reasoning(confidence 0.60)
Probation Imposition, though not itself tagged as fulfilling or violating a duty, functions as Management's retaliatory response to Engineer A's persistent safety advocacy, and it directly precipitates Employment Jeopardy Onset, making it the pivotal causal link that transforms a technical disagreement into a threat to the engineer's livelihood.
State changes (1)
  • began: Engineer A Probation Jeopardy
As a consequence of the probation imposed with a notation warning of termination, Engineer A's continued employment became at risk, a condition the Discussion connects to the price whistleblowing engineers may pay.
State changes (1)
  • began: Engineer A Probation Jeopardy
Despite the disciplinary consequences, Engineer A continued to insist that his employer had an obligation to ensure that subcontractors deliver equipment according to the specifications as he interprets them, and thereby save substantial defense expenditures.
Causal-normative reasoning(confidence 0.60)
A1's Continued Insistence, though not tied to any explicit obligation, is guided by Public Welfare Principle and Personal Conscience, showing that Engineer A's persistence stems from a moral commitment to safety rather than a formal duty, which sets the ethical tone for the escalating conflict with Management even though no violation is recorded.
State changes (1)
  • began: Engineer A Management Disagreement
Engineer A requested an ethical review and determination of the propriety of his course of action and the degree of ethical responsibility of engineers in such circumstances.
Causal-normative reasoning(confidence 0.65)
Ethical Review Request fulfills no explicit external duty but is guided by Personal Conscience, showing that once Employment Jeopardy Onset threatened Engineer A's career, the engineer turned to an internal moral compass rather than institutional obligation to seek vindication of the original safety concerns, underscoring the limits of formal duties when institutional channels have failed.
Narrative (2 main characters)
View Extraction
Opening Context

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

You are Engineer A, employed by a large industrial company that performs substantial work on defense contracts. Your assigned duties involve reviewing plans and materials submitted by subcontractors to determine whether their work meets contract specifications. During this review process, you identified problems with submissions from one particular subcontractor and sent memoranda to your superiors recommending rejection of the work and redesign to correct the deficiencies, citing concerns about excessive cost and time delays to the government. Management reviewed your objections and declined to follow your recommendations, choosing instead to accept the subcontractor's submissions as delivered. Further memoranda passed between you and management without resolving the disagreement, after which management placed a critical memorandum in your personnel file and put you on three months' probation, warning that continued performance issues could lead to termination. You continue to maintain that your employer has an obligation to ensure subcontractor compliance with specifications as you interpret them, in order to protect defense expenditures. You must now consider how to proceed given your professional obligations, the position your employer has taken, and the consequences you may face.

Main characters (2)

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

Industrial Company Roles in this case: Employer

Guided by: Public Welfare in Defense Spending, Public Welfare Defense Expenditures, Personal Conscience in Whistleblowing

Engineer A may feel obligated to withdraw once a safety-relevant recommendation is rejected, but the rejected recommendation boundary limits the engineer's further responsibility once the client or employer has made its decision, creating ambiguity about when withdrawal becomes mandatory versus optional overreach.

Engineer A's duty to report the deficiency in the subcontractor's submission may require disclosure beyond what the narrowly scoped withdrawal duty contemplates, creating uncertainty about whether reporting obligations persist or expand once the engineer's formal involvement in the project is limited by the withdrawal scope constraint.

Continuing to fulfill the duty to report deficiencies may require Engineer A to remain engaged with the project, while the conditional duty to withdraw once conditions are unmet pushes toward disengagement, forcing a choice between staying involved to ensure the deficiency is addressed and withdrawing to avoid complicity in an unresolved safety issue.

Engineer A Roles in this case: Review Engineer

Engineer A may feel obligated to withdraw once a safety-relevant recommendation is rejected, but the rejected recommendation boundary limits the engineer's further responsibility once the client or employer has made its decision, creating ambiguity about when withdrawal becomes mandatory versus optional overreach.

Tension between Engineer A Conditional Withdrawal Duty and Engineer A Withdrawal Duty Scope

Engineer A's duty to report the deficiency in the subcontractor's submission may require disclosure beyond what the narrowly scoped withdrawal duty contemplates, creating uncertainty about whether reporting obligations persist or expand once the engineer's formal involvement in the project is limited by the withdrawal scope constraint.

Continuing to fulfill the duty to report deficiencies may require Engineer A to remain engaged with the project, while the conditional duty to withdraw once conditions are unmet pushes toward disengagement, forcing a choice between staying involved to ensure the deficiency is addressed and withdrawing to avoid complicity in an unresolved safety issue.

Tension between Engineer A Deficiency Reporting Duty and Engineer A Rejected Recommendation Boundary

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

Engineer A's duty to report the deficiency in the subcontractor's submission may require disclosure beyond what the narrowly scoped withdrawal duty contemplates, creating uncertainty about whether reporting obligations persist or expand once the engineer's formal involvement in the project is limited by the withdrawal scope constraint.

Continuing to fulfill the duty to report deficiencies may require Engineer A to remain engaged with the project, while the conditional duty to withdraw once conditions are unmet pushes toward disengagement, forcing a choice between staying involved to ensure the deficiency is addressed and withdrawing to avoid complicity in an unresolved safety issue.

The Board’s deliberation

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

Engineer A does not have an ethical obligation to continue his effort to secure a change in the policy of his employer under these circumstances, or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience.
Opening States (7)
Memoranda Disclosure to Superiors Engineer A Management Disagreement Engineer A Probation Jeopardy Absent Public Safety Danger Finding Unjustified Public Expenditure Claim Whistleblowing Personal Conscience Condition Subcontractor Submission Deficiency Finding
Summary
  • An engineer's duty to press further after a recommendation is rejected depends on whether the underlying issue rises to a genuine public health or safety threat, not merely a difference of professional judgment.
  • Once a good faith recommendation has been made and rejected through legitimate channels, the affirmative obligation to continue advocacy, escalate to authorities, or withdraw from the project generally ends, even though the engineer may choose to do more.
  • Duties to withdraw or report are conditional and narrowly scoped, so they do not automatically expand into an open ended obligation to keep fighting an employer's decision.

© Licensed under the GNU GPL v3