Source: Amended Ethics Essay, Introduction to Computer Science Concepts and Programming (Texas A&M University)
Tags: engineering ethics, NSPE, Case 16-12, confidential information, professional responsibility, whistleblowing, public safety, ethical obligations, BER, Board of Ethical Review
Difficulty: Beginner Prerequisites: Basic familiarity with engineering codes of ethics (e.g. NSPE Code of Ethics). No prior case law knowledge needed.
Big picture: Engineering ethics cases teach you how professional codes translate into real decisions under pressure. NSPE Case 16-12 sits within a broader unit on confidentiality, loyalty to employers, and the overriding duty to public safety. If you have covered the NSPE Code of Ethics and understand the hierarchy of obligations (public safety first, then employer, then profession), you have the background you need. This case is a useful one because it forces you to weigh competing loyalties when potentially confidential information lands in your lap.
Engineer A's firm obtains what appears to be a competitor's confidential presentation. The ethical question is what Engineer A should do with it. The approved resolution says the right move is to go directly to the affected firm (Firm Y), because protecting public welfare and professional integrity outweighs loyalty to your own team. The twist: the suspected breach turned out to be unfounded, but the obligation to report still applies if the engineer believes otherwise.
NSPE
National Society of Professional Engineers. The professional body that publishes the Code of Ethics for Engineers and adjudicates ethics cases through its Board of Ethical Review (BER).
In simple terms, NSPE is the organisation that sets the ethical rules engineers are expected to follow in the US.
Board of Ethical Review (BER)
The NSPE committee that examines real and hypothetical ethics cases and publishes "approved resolutions" explaining what the code requires. These resolutions serve as precedent-like guidance for engineers.
Think of it as the ethics case-law library for the engineering profession.
Case No. 16-12
An NSPE ethics case involving an engineer (Engineer A) whose firm comes into possession of what appears to be a competitor's (Firm Z's) confidential presentation, intended for a client (Firm Y). The central question is the engineer's duty regarding that information.
In simple terms, this is the scenario you need to know for this assignment: someone on your team may have seen the other side's playbook, and you have to decide what to do about it.
Confidential information
Proprietary data, strategies, or documents belonging to another party that were not intended to be shared. In engineering ethics, using or failing to report the misuse of confidential information can itself be an ethical violation.
Think of it as someone else's private work product that you were never supposed to see.
Public safety and wellbeing (paramount duty)
The principle, embedded in virtually every engineering code of ethics, that an engineer's first obligation is to protect the health, safety, and welfare of the public. This duty overrides obligations to employers, clients, or colleagues.
In simple terms, if doing the right thing for the public conflicts with doing the right thing for your boss, the public wins.
Approved resolution
The BER's published conclusion on how the Code of Ethics applies to a given case. It functions as the "correct answer" for study and exam purposes.
Think of it as the model answer you are measured against.
Whistleblowing (in engineering context)
Reporting unethical or unsafe conduct to a higher authority when internal channels fail or are compromised. In the NSPE framework, engineers have a duty to report violations, escalating as necessary.
In simple terms, if your firm will not do the right thing, you go over their heads.
Engineer A works at a firm that is preparing a presentation for Firm Y (the client).
The firm appears to have obtained Firm Z's (a competitor's) confidential presentation, also intended for Firm Y.
The ethical dilemma: should Engineer A use the information, ignore it, or report it?
Engineer A should either not use the information at all, or verify its legitimacy and inform both parties before the presentation.
This position missed a key fact: Engineer A is part of a team and cannot unilaterally make decisions for the firm.
Advise Engineer A to inform his own firm about the unethical possession of the information.
If the firm tries to hide the information or exploit it, escalate to a higher authority.
This aligns with the general principle of internal reporting first, then escalation.
Engineer A should go directly to Firm Y (the client for whom the presentation is intended) and disclose the situation.
Rationale: public safety and professional integrity are the engineer's top priority.
Any delay, including routing the issue through your own firm first, introduces risk that the information gets buried or misused.
Going straight to the affected party is the most protective course of action.
It turned out Firm Y never actually reviewed Firm Z's presentation, so the suspected ethical breach was unfounded.
If the facts show no breach occurred, no corrective action is needed on that specific point.
However, if Engineer A personally believes a breach did occur, the duty to report still stands regardless of what the facts later reveal. The obligation is triggered by the engineer's reasonable belief, not by the outcome.
This pattern appears whenever professionals handle competitors' proprietary information, whether in engineering bids, consulting proposals, or technology tenders. The same logic applies in industries beyond engineering: if you receive information you should not have, sitting on it or using it quietly is itself the ethical failure. The duty runs to disclosure, not to advantage.
"I can just ignore the information and do nothing." Passivity is not neutral here. If you know confidential information has been improperly obtained, silence can itself be an ethical violation under the NSPE Code.
"Telling my own firm first is always the right first step." The approved resolution in this case says otherwise. When public safety or a third party's rights are at stake, going to the affected party directly may be the required action.
"If the breach turns out to be false, I was wrong to raise it." No. The duty to report is based on reasonable belief at the time, not on hindsight. You are not penalised for reporting in good faith.
"Because I'm part of a team, ethics decisions are the team's problem, not mine." Individual engineers retain personal ethical obligations. Being on a team does not dilute your duty.
⚠️ Know the hierarchy of duties: public safety > employer loyalty > personal convenience. This is tested constantly.
⚠️ Understand why the approved resolution favours going to Firm Y directly rather than routing through Engineer A's own firm. Be ready to explain the reasoning, not just state the conclusion.
⚠️ Be prepared for a question that changes the facts (e.g. "What if Firm Y had reviewed the presentation?") and asks how the ethical obligation shifts.
⚠️ The difference between the student's original position and the approved resolution is a common exam setup: "Identify what this analysis missed and why the approved resolution differs."
True or False: An engineer's duty to public safety can be overridden by loyalty to their employer.
Fill in the blank: The approved resolution for Case 16-12 advises Engineer A to go directly to ________, the firm the presentation was intended for.
True or False: If an engineer reports a suspected ethical breach in good faith and the breach turns out not to have occurred, the engineer acted improperly.
Fill in the blank: The body that publishes approved resolutions on NSPE ethics cases is the ________.
True or False: Being part of a team removes an individual engineer's personal ethical obligations.
(Answers: 1. False; 2. Firm Y; 3. False; 4. Board of Ethical Review (BER); 5. False)
Q: In NSPE Case 16-12, what is the approved resolution's recommended course of action for Engineer A?
A: Engineer A should go directly to Firm Y (the client) and disclose that the firm appears to have obtained Firm Z's confidential presentation. The rationale is that public safety and professional integrity take precedence over internal firm loyalty.
Q: Why does the approved resolution differ from the approach of reporting internally to Engineer A's own firm first?
A: Routing the disclosure through Engineer A's own firm introduces the risk that the firm suppresses or exploits the information. Since the engineer's paramount duty is to the public and to the affected party, going directly to Firm Y removes that risk and fulfils the obligation most cleanly.
Q: How do the facts of the case (Firm Y never reviewed Firm Z's presentation) affect the ethical analysis?
A: The facts mean that the suspected breach was unfounded, so no corrective action on that specific point is necessary. However, this does not retroactively make the duty to report disappear. If Engineer A had reasonable grounds to believe a breach occurred, reporting was still the correct action at the time.
Q: What ethical principle does this case primarily illustrate?
A: The principle that an engineer's duty to public safety and welfare overrides competing obligations, including loyalty to their employer or team. It also illustrates the duty to report known or suspected ethical violations.
Q: Can an engineer defer ethical responsibility to their team or firm?
A: No. Individual engineers retain personal ethical obligations under the NSPE Code of Ethics. Being part of a team does not transfer or dilute those obligations.
This case connects directly to broader units on professional codes of ethics (NSPE, IEEE, ACM), where the hierarchy of duties is a recurring theme. It also links to whistleblower protections in employment law, since the escalation path described here (internal report, then external authority) mirrors the legal framework for protected disclosures. If your course covers intellectual property, the confidential-information element of this case is a natural bridge.
NSPE Code of Ethics, Case 16-12, BER, Board of Ethical Review, engineering ethics case study, confidential information ethics, whistleblowing engineering, public safety duty, paramount obligation, professional responsibility, ethical obligations engineer, Texas A&M CSCE ethics, employer loyalty vs public safety, approved resolution NSPE, ethics case analysis, engineering ethics exam review