Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section I. Fundamental Canons 1 79 entities
Hold paramount the safety, health, and welfare of the public.
Section II. Rules of Practice 4 169 entities
Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
Engineers shall act for each employer or client as faithful agents or trustees.
Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.
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.
Section III. Professional Obligations 1 46 entities
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.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 3 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
Section III.4 relates to confidential information given by the client to the engineer in the course of providing services; where no such transmission occurs, the confidentiality obligation under that section is not triggered.
Citation Context:
Cited to illustrate the principle of client confidentiality in private practice, and to distinguish it from the present case because in Case 82-2 there was no transmission of confidential information by the client to the engineer, whereas in the present case there was.
Principle Established:
When a client refuses to adopt safety measures the engineer believes are necessary to prevent danger, the engineer must either insist on those measures or refuse to continue work on the project rather than acquiescing.
Citation Context:
Cited by analogy to illustrate that an engineer who 'goes along' with a client's decision that endangers public safety, rather than insisting on safety measures or withdrawing, acts unethically.
Principle Established:
Section II.1.c has been interpreted by the Board in the context of an engineer's obligation regarding disclosure of information acquired during professional services.
Citation Context:
Cited as one of three cases in which the Board interpreted Section II.1.c, though the Board notes none of these cases fully outlined the scope of that section.
Principle Established:
Engineers have an ethical obligation to maintain the confidentiality of information made available to them during the course of employment.
Citation Context:
Cited as an early example of the Board interpreting confidentiality obligations under Sections II.4 and III.4 in the context of employed engineers maintaining confidences of their employer.
Principle Established:
Section II.1.c has been interpreted by the Board in the context of an engineer's obligation regarding disclosure of information acquired during professional services.
Citation Context:
Cited as one of three cases in which the Board interpreted Section II.1.c, though the Board notes none of these cases fully outlined the scope of that section.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionWas it ethical for Engineer A not to report the safety violations to the appropriate public authorities?
It was unethical for Engineer A not to report the safety violations to the appropriate public authorities.
Does the fact that the safety-critical information was voluntarily disclosed by the client - rather than independently discovered by Engineer A - reduce, eliminate, or actually strengthen Engineer A's obligation to report it to public authorities?
The Board's conclusion that reporting was ethically required is strengthened - not weakened - by the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection. Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. A client's voluntary disclosure does not transform dangerous information into protected business intelligence; it simply means the engineer received confirmed, first-hand knowledge of a life-safety hazard directly from the party responsible for it. If anything, client-transmitted disclosure eliminates the epistemic uncertainty that might otherwise justify caution before reporting, because the engineer need not rely on inference or indirect evidence - the client has affirmatively confirmed the violations exist. The source of the information therefore strengthens rather than modulates the reporting obligation.
The fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A does not reduce - and may actually strengthen - Engineer A's reporting obligation. The NSPE Code's paramount safety duty in Section I.1 is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. Once Engineer A possessed actual knowledge that occupants of an occupied building faced injury from known code violations, the ethical trigger was complete regardless of how that knowledge was acquired. If anything, the client's voluntary disclosure eliminated any ambiguity about whether the violations existed, removing the epistemic uncertainty that might otherwise counsel caution before reporting. The argument that client-confided information deserves heightened confidentiality protection under Section III.4 is not without force, but it cannot override the explicit exception in Section II.1.c, which releases engineers from confidentiality obligations precisely when public danger is present. The source of the information is therefore ethically irrelevant to the reporting threshold; it is relevant only to the weight of the confidentiality interest being overridden, and even that interest is expressly subordinated by the Code when safety is at stake.
Was Engineer A's brief mention of the electrical and mechanical deficiencies in his confidential structural report a meaningful discharge of any ethical obligation, or did it create a false appearance of compliance while ensuring the information would never reach those who needed it - the occupants or public authorities?
Engineer A's brief mention of the electrical and mechanical deficiencies within a confidential structural report constitutes a procedural gesture that affirmatively failed to discharge any meaningful ethical obligation. By embedding safety-critical information in a document contractually shielded from third-party disclosure, Engineer A created a record of awareness while simultaneously ensuring that the parties most exposed to the hazard - the building's current occupants - and the regulatory authorities empowered to act on it would never receive the information. This is not a partial discharge of the notification duty; it is a form of ethical concealment dressed as disclosure. The NSPE Code's public safety obligation under Section I.1 and the notification duty under Section II.1.a are directed at outcomes - specifically, that endangered parties receive actionable information - not at the mere creation of internal documentation. A confidential mention satisfies neither the letter nor the spirit of those provisions.
Engineer A's brief mention of the electrical and mechanical deficiencies in his confidential structural report did not constitute a meaningful discharge of any ethical obligation to protect public safety. On the contrary, it created a false appearance of compliance - a record that Engineer A had 'noted' the violations - while structurally ensuring that the information would never reach the parties who needed it most: the building's current occupants and the public authorities responsible for enforcing safety codes. A disclosure that is deliberately confined to a document the client controls, that no regulator will ever see, and that no occupant will ever read is functionally equivalent to no disclosure at all from a public safety standpoint. The NSPE Code's obligation under Section II.1.a requires notification to appropriate authorities when professional judgment is overruled under circumstances that endanger life or property. A notation in a confidential report addressed to the party who has already refused remediation satisfies none of the elements of that obligation: it reaches no authority, it triggers no regulatory response, and it protects no occupant. The brief mention therefore represents a procedural gesture that obscures rather than discharges the substantive ethical duty.
Given that Engineer A is a structural engineer without competence in electrical or mechanical systems, does his professional incompetence in those domains diminish his reporting obligation, or does the threshold for triggering a public safety duty require only that he recognize a risk of injury - not that he be able to evaluate it technically?
Engineer A's lack of competence in electrical and mechanical engineering does not diminish the reporting obligation and may not be invoked as a scope-of-work defense. The threshold for triggering the public safety duty under Section I.1 requires only that the engineer recognize a risk of injury - not that the engineer be technically qualified to evaluate, quantify, or remediate it. Engineer A explicitly acknowledged recognizing that the disclosed deficiencies could cause injury to occupants. That recognition alone activated the reporting duty. The competence boundary argument, if accepted, would produce an absurd result: engineers would be ethically insulated from reporting known dangers simply because those dangers fall outside their primary discipline. The Code contains no such carve-out, and the Board's precedents in analogous cases confirm that out-of-scope safety findings carry independent disclosure obligations. Engineer A's disciplinary limitations were relevant to the scope of his remediation authority - they were irrelevant to his obligation to notify public authorities of a known hazard.
Engineer A's lack of competence in electrical and mechanical engineering does not diminish his obligation to report the known code violations to public authorities. The threshold for triggering a public safety reporting duty under the NSPE Code requires only that the engineer recognize a risk of injury to the public - not that he be technically qualified to evaluate, diagnose, or remediate the hazard. Engineer A himself acknowledged that the disclosed deficiencies 'could cause injury to the occupants,' which means the recognition threshold was met by his own assessment. The scope-of-work and domain-competence arguments function as incomplete defenses at best: they might limit Engineer A's authority to demand specific corrective measures or to certify the severity of the violations, but they do not limit his capacity to convey to a public authority that a client has disclosed the existence of code violations in an occupied building. Reporting what one knows to those with the competence and authority to investigate is precisely the appropriate response when an engineer encounters a hazard outside his discipline. Domain incompetence is therefore a reason to escalate to qualified authorities, not a reason to remain silent.
Engineer A's domain incompetence in electrical and mechanical engineering does not diminish his reporting obligation, and this case establishes an important principle about the threshold for triggering a public safety duty: recognition of injury risk, not technical competence to evaluate it, is the operative standard. Engineer A himself acknowledged that the disclosed deficiencies could cause injury to occupants - that acknowledgment is precisely the threshold event. The duty to hold public safety paramount does not require the engineer to be able to diagnose, quantify, or remediate the hazard; it requires only that the engineer recognize that a hazard exists and that persons are exposed to it. Requiring technical competence as a precondition for reporting would perversely insulate engineers from safety obligations in exactly those situations where they are most dependent on others' expertise - and would allow scope-of-work boundaries to function as shields against accountability. This case teaches that the faithful agent role under Section II.4 is bounded by ethical limits, and that those limits include the obligation not to allow disciplinary boundaries to suppress safety-critical information from reaching appropriate authorities.
Did Engineer A have an independent ethical obligation to notify the building's current occupants directly of the known code violations, separate from any duty to report to regulatory or public authorities, given that the occupants are the parties most immediately exposed to the hazard?
Engineer A had an independent ethical obligation to consider notifying the building's current occupants directly of the known code violations, separate from any duty to report to regulatory or public authorities. The occupants of the 60-year-old apartment building are the parties most immediately and continuously exposed to the hazard: they live within it, they cannot protect themselves from dangers they do not know exist, and they have no contractual relationship with Engineer A that would generate any competing confidentiality interest. While the NSPE Code's explicit reporting pathway runs through 'appropriate public authorities' under Section II.1.a, the paramount safety obligation in Section I.1 is not exhausted by that single channel. When regulatory reporting is the most effective route, it should be pursued; but when occupants are immediately at risk and regulatory response may be delayed, direct notification to those at risk is consistent with - and may be required by - the spirit of the paramount safety obligation. Engineer A's failure to consider this pathway represents an additional dimension of ethical shortcoming beyond the failure to notify authorities.
Does the principle that an engineer must act as a faithful agent or trustee of the client conflict with the principle that public safety is paramount and that confidentiality agreements cannot supersede the duty to prevent imminent danger - and if so, which principle controls and under what conditions?
The Board's conclusion that reporting was ethically required is strengthened - not weakened - by the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection. Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. A client's voluntary disclosure does not transform dangerous information into protected business intelligence; it simply means the engineer received confirmed, first-hand knowledge of a life-safety hazard directly from the party responsible for it. If anything, client-transmitted disclosure eliminates the epistemic uncertainty that might otherwise justify caution before reporting, because the engineer need not rely on inference or indirect evidence - the client has affirmatively confirmed the violations exist. The source of the information therefore strengthens rather than modulates the reporting obligation.
The conflict between the faithful agent principle under Section II.4 and the paramount safety obligation under Section I.1 is resolved unambiguously by the NSPE Code's own internal hierarchy: public safety is explicitly designated as paramount, meaning it takes precedence over all other duties including client loyalty and confidentiality. The faithful agent role is not absolute - it is expressly conditioned on the engineer acting 'within ethical limits,' and those limits are defined in part by the safety obligations in Sections I.1 and II.1.a. The condition that triggers the override is not merely theoretical danger but actual knowledge of a hazard that could cause injury to occupants, which Engineer A possessed. Engineer A's misapplication of the faithful agent principle as a basis for confidentiality absolutism therefore represents a category error: he treated a conditional, subordinate duty as though it were unconditional and supreme. The principle that controls is public safety, and the condition under which it controls is precisely the one present in this case - known, code-violating hazards in an occupied building.
The tension between client confidentiality and public safety was not genuinely unresolvable in this case - it was falsely treated as such by Engineer A. The NSPE Code does not present these principles as equals requiring ad hoc balancing; it establishes a normative hierarchy in which public safety is explicitly paramount. Section I.1 places the safety, health, and welfare of the public at the apex of engineering obligation, and Section II.1.c contains an explicit exception clause that releases engineers from confidentiality duties precisely when public danger is present. Engineer A's error was not a failure of judgment in a genuinely ambiguous situation but a failure to recognize that the Code had already resolved the tension in advance. By treating confidentiality as an absolute constraint capable of overriding a known life-safety hazard in an occupied building, Engineer A inverted the Code's own priority structure. This case teaches that when the Code itself contains an exception clause addressing the exact conflict an engineer faces, invoking the general confidentiality rule while ignoring the exception is not a defensible ethical position - it is a misreading of the Code's architecture.
Does the principle that confidentiality does not apply when public danger is present conflict with the principle that client-transmitted confidential information carries its own distinct confidentiality weight under Section III.4 - and does the source of the information (client disclosure versus independent discovery) legitimately modulate the engineer's reporting threshold?
Beyond the Board's finding that Engineer A's failure to report was unethical, the confidentiality agreement itself cannot bear the interpretive weight Engineer A assigned to it. Section II.1.c expressly releases engineers from confidentiality obligations when public danger is present, meaning the contractual arrangement never legally or ethically foreclosed disclosure to public authorities. Engineer A's reliance on the confidentiality agreement as a complete bar to external reporting therefore reflects a fundamental misreading of the NSPE Code's internal hierarchy: the agreement was a valid constraint on routine business disclosures, but it was categorically inapplicable to life-safety code violations in an occupied residential building. The ethical failure was not merely that Engineer A chose confidentiality over safety - it was that Engineer A treated a conditional obligation as an absolute one, never activating the exception clause the Code explicitly provides.
Engineer A's brief mention of the electrical and mechanical deficiencies within a confidential structural report constitutes a procedural gesture that affirmatively failed to discharge any meaningful ethical obligation. By embedding safety-critical information in a document contractually shielded from third-party disclosure, Engineer A created a record of awareness while simultaneously ensuring that the parties most exposed to the hazard - the building's current occupants - and the regulatory authorities empowered to act on it would never receive the information. This is not a partial discharge of the notification duty; it is a form of ethical concealment dressed as disclosure. The NSPE Code's public safety obligation under Section I.1 and the notification duty under Section II.1.a are directed at outcomes - specifically, that endangered parties receive actionable information - not at the mere creation of internal documentation. A confidential mention satisfies neither the letter nor the spirit of those provisions.
The fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A does not reduce - and may actually strengthen - Engineer A's reporting obligation. The NSPE Code's paramount safety duty in Section I.1 is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. Once Engineer A possessed actual knowledge that occupants of an occupied building faced injury from known code violations, the ethical trigger was complete regardless of how that knowledge was acquired. If anything, the client's voluntary disclosure eliminated any ambiguity about whether the violations existed, removing the epistemic uncertainty that might otherwise counsel caution before reporting. The argument that client-confided information deserves heightened confidentiality protection under Section III.4 is not without force, but it cannot override the explicit exception in Section II.1.c, which releases engineers from confidentiality obligations precisely when public danger is present. The source of the information is therefore ethically irrelevant to the reporting threshold; it is relevant only to the weight of the confidentiality interest being overridden, and even that interest is expressly subordinated by the Code when safety is at stake.
The tension between Section III.4's protection of client-transmitted confidential information and Section II.1.c's explicit exception releasing engineers from confidentiality when public danger is present is resolved by reading the Code as an integrated normative system rather than a collection of isolated provisions. Section III.4 establishes a genuine confidentiality obligation that applies to business affairs and technical processes disclosed by clients, and the fact that the client voluntarily confided the violations to Engineer A does carry some weight in calibrating the confidentiality interest at stake. However, Section II.1.c is not a general provision - it is a specific exception clause that was drafted precisely to address the situation where confidentiality and public danger collide. Specific exception clauses override general rules in any coherent normative system. Moreover, the source of the information (client disclosure versus independent discovery) may modulate the weight of the confidentiality interest, but it cannot eliminate the operation of an explicit exception clause. Engineer A's failure to activate Section II.1.c therefore cannot be justified by appeal to Section III.4, because the Code itself resolves that conflict in favor of disclosure when danger to the public is present.
The source of the hazardous information - client voluntary disclosure rather than independent discovery - introduced a genuine complication that the Board did not fully resolve, but that complication does not ultimately alter the outcome. Section III.4 does create a distinct confidentiality weight for information transmitted by a client in confidence, and this distinguishes the case from one where an engineer independently discovers a defect during inspection. However, Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the origin of that knowledge. Once Engineer A possessed knowledge that occupants of an occupied building faced injury from known code violations, the triggering condition for the paramount safety duty was satisfied regardless of how that knowledge was acquired. The source-of-information distinction is therefore relevant to calibrating the confidentiality weight on one side of the balance, but it cannot extinguish the safety obligation on the other side when the hazard is concrete, known, and affecting identifiable persons. This case teaches that Section III.4 and Section II.1.c must be read together, not in isolation: the former establishes that client-transmitted information carries confidentiality expectations, while the latter establishes that those expectations yield when public danger is present.
Does the principle requiring an engineer to insist on remedial action or withdraw from a project when safety is at stake conflict with the principle that an engineer's scope-of-work limitations and out-of-discipline boundaries constrain his authority to demand corrective action on electrical and mechanical systems - and how should these competing obligations be reconciled?
Engineer A's lack of competence in electrical and mechanical engineering does not diminish the reporting obligation and may not be invoked as a scope-of-work defense. The threshold for triggering the public safety duty under Section I.1 requires only that the engineer recognize a risk of injury - not that the engineer be technically qualified to evaluate, quantify, or remediate it. Engineer A explicitly acknowledged recognizing that the disclosed deficiencies could cause injury to occupants. That recognition alone activated the reporting duty. The competence boundary argument, if accepted, would produce an absurd result: engineers would be ethically insulated from reporting known dangers simply because those dangers fall outside their primary discipline. The Code contains no such carve-out, and the Board's precedents in analogous cases confirm that out-of-scope safety findings carry independent disclosure obligations. Engineer A's disciplinary limitations were relevant to the scope of his remediation authority - they were irrelevant to his obligation to notify public authorities of a known hazard.
Engineer A's lack of competence in electrical and mechanical engineering does not diminish his obligation to report the known code violations to public authorities. The threshold for triggering a public safety reporting duty under the NSPE Code requires only that the engineer recognize a risk of injury to the public - not that he be technically qualified to evaluate, diagnose, or remediate the hazard. Engineer A himself acknowledged that the disclosed deficiencies 'could cause injury to the occupants,' which means the recognition threshold was met by his own assessment. The scope-of-work and domain-competence arguments function as incomplete defenses at best: they might limit Engineer A's authority to demand specific corrective measures or to certify the severity of the violations, but they do not limit his capacity to convey to a public authority that a client has disclosed the existence of code violations in an occupied building. Reporting what one knows to those with the competence and authority to investigate is precisely the appropriate response when an engineer encounters a hazard outside his discipline. Domain incompetence is therefore a reason to escalate to qualified authorities, not a reason to remain silent.
Engineer A's domain incompetence in electrical and mechanical engineering does not diminish his reporting obligation, and this case establishes an important principle about the threshold for triggering a public safety duty: recognition of injury risk, not technical competence to evaluate it, is the operative standard. Engineer A himself acknowledged that the disclosed deficiencies could cause injury to occupants - that acknowledgment is precisely the threshold event. The duty to hold public safety paramount does not require the engineer to be able to diagnose, quantify, or remediate the hazard; it requires only that the engineer recognize that a hazard exists and that persons are exposed to it. Requiring technical competence as a precondition for reporting would perversely insulate engineers from safety obligations in exactly those situations where they are most dependent on others' expertise - and would allow scope-of-work boundaries to function as shields against accountability. This case teaches that the faithful agent role under Section II.4 is bounded by ethical limits, and that those limits include the obligation not to allow disciplinary boundaries to suppress safety-critical information from reaching appropriate authorities.
Does the principle that an engineer must notify appropriate authorities when professional judgment is overruled conflict with the principle that the engineer's duty to report is triggered only by dangers within his professional competence - and does passive acquiescence after verbally warning the client constitute an independent ethical violation even if the engineer genuinely believed the reporting duty was blocked by confidentiality?
Engineer A's passive acquiescence after verbally warning the client constitutes an independent ethical violation separate from and in addition to the failure to report to public authorities. The Board's precedent in BER Case 84-5 establishes that an engineer who goes along with a client's safety-compromising decision without formal dissent or escalation commits an ethical violation even if the engineer privately disagreed. Engineer A's single verbal warning, followed by silent compliance with the client's 'as is' sale directive, mirrors precisely the going-along-without-dissent pattern condemned in that precedent. The ethical obligation required Engineer A to either insist on remedial action, formally document objection and withdraw from the project, or escalate to public authorities - not to treat a verbal protest as a terminal act of compliance. Passive acquiescence after a client overrules safety concerns is not a neutral act; it is an affirmative ethical failure under Section II.1.a, which requires engineers whose judgment is overruled under life-endangering circumstances to notify appropriate authorities.
Engineer A's passive acquiescence after verbally warning the client constitutes an independent ethical failure distinct from the failure to report to public authorities, and this case teaches that the duty of non-acquiescence has both a procedural and a substantive dimension. Procedurally, as established in BER Case 84-5, an engineer who disagrees with a client's safety-compromising decision must formally document that objection - a single verbal warning does not satisfy the requirement. Substantively, even formal objection and documented dissent do not discharge the engineer's obligation when the hazard remains active and occupants remain exposed: the engineer must either insist on remedial action, withdraw from the project, or escalate to public authorities. The brief mention in a confidential report satisfies neither the procedural nor the substantive dimension - it is a record that ensures the information will never reach those who need it, while creating a superficial appearance of disclosure. This case therefore teaches that the principle requiring insistence on remedial action or withdrawal under Section II.1.a and the principle requiring appropriate authority notification when professional judgment is overruled are sequential obligations, not alternatives: exhausting one does not eliminate the other.
From a consequentialist perspective, did Engineer A's decision to limit disclosure to a brief mention in a confidential report - rather than notifying public authorities - produce the best reasonably achievable outcome for all affected parties, including building occupants who remained exposed to known electrical and mechanical code violations?
Beyond the Board's finding that Engineer A's failure to report was unethical, the confidentiality agreement itself cannot bear the interpretive weight Engineer A assigned to it. Section II.1.c expressly releases engineers from confidentiality obligations when public danger is present, meaning the contractual arrangement never legally or ethically foreclosed disclosure to public authorities. Engineer A's reliance on the confidentiality agreement as a complete bar to external reporting therefore reflects a fundamental misreading of the NSPE Code's internal hierarchy: the agreement was a valid constraint on routine business disclosures, but it was categorically inapplicable to life-safety code violations in an occupied residential building. The ethical failure was not merely that Engineer A chose confidentiality over safety - it was that Engineer A treated a conditional obligation as an absolute one, never activating the exception clause the Code explicitly provides.
The Board's conclusion that reporting was ethically required is strengthened - not weakened - by the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection. Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. A client's voluntary disclosure does not transform dangerous information into protected business intelligence; it simply means the engineer received confirmed, first-hand knowledge of a life-safety hazard directly from the party responsible for it. If anything, client-transmitted disclosure eliminates the epistemic uncertainty that might otherwise justify caution before reporting, because the engineer need not rely on inference or indirect evidence - the client has affirmatively confirmed the violations exist. The source of the information therefore strengthens rather than modulates the reporting obligation.
The fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A does not reduce - and may actually strengthen - Engineer A's reporting obligation. The NSPE Code's paramount safety duty in Section I.1 is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. Once Engineer A possessed actual knowledge that occupants of an occupied building faced injury from known code violations, the ethical trigger was complete regardless of how that knowledge was acquired. If anything, the client's voluntary disclosure eliminated any ambiguity about whether the violations existed, removing the epistemic uncertainty that might otherwise counsel caution before reporting. The argument that client-confided information deserves heightened confidentiality protection under Section III.4 is not without force, but it cannot override the explicit exception in Section II.1.c, which releases engineers from confidentiality obligations precisely when public danger is present. The source of the information is therefore ethically irrelevant to the reporting threshold; it is relevant only to the weight of the confidentiality interest being overridden, and even that interest is expressly subordinated by the Code when safety is at stake.
From a consequentialist perspective, Engineer A's decision to limit disclosure to a brief mention in a confidential report produced the worst reasonably foreseeable outcome for the most vulnerable affected parties. The building's current occupants - who had no knowledge of the violations, no ability to protect themselves, and no contractual relationship with Engineer A - remained continuously exposed to electrical and mechanical hazards that the client had already acknowledged violated applicable codes. The client's interests were served in the short term by the suppression of the violations, but even those interests are not clearly advanced by a strategy that exposes the client to future liability for selling a building with known, undisclosed safety defects. Engineer A's professional standing was not protected by his silence - it was ultimately condemned. The only outcome that would have produced the best reasonably achievable result for all affected parties was notification of public authorities, which would have triggered regulatory inspection, potentially required remediation before sale, and protected occupants from ongoing exposure. The consequentialist calculus therefore aligns with the deontological conclusion: reporting was the ethically required action.
From a deontological perspective, does the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection meaningfully alter Engineer A's duty to report, given that the NSPE Code's public safety obligation in Section I.1 is framed in terms of the engineer's knowledge of danger rather than the source of that knowledge?
The Board's conclusion that reporting was ethically required is strengthened - not weakened - by the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection. Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. A client's voluntary disclosure does not transform dangerous information into protected business intelligence; it simply means the engineer received confirmed, first-hand knowledge of a life-safety hazard directly from the party responsible for it. If anything, client-transmitted disclosure eliminates the epistemic uncertainty that might otherwise justify caution before reporting, because the engineer need not rely on inference or indirect evidence - the client has affirmatively confirmed the violations exist. The source of the information therefore strengthens rather than modulates the reporting obligation.
Engineer A's passive acquiescence after verbally warning the client constitutes an independent ethical violation separate from and in addition to the failure to report to public authorities. The Board's precedent in BER Case 84-5 establishes that an engineer who goes along with a client's safety-compromising decision without formal dissent or escalation commits an ethical violation even if the engineer privately disagreed. Engineer A's single verbal warning, followed by silent compliance with the client's 'as is' sale directive, mirrors precisely the going-along-without-dissent pattern condemned in that precedent. The ethical obligation required Engineer A to either insist on remedial action, formally document objection and withdraw from the project, or escalate to public authorities - not to treat a verbal protest as a terminal act of compliance. Passive acquiescence after a client overrules safety concerns is not a neutral act; it is an affirmative ethical failure under Section II.1.a, which requires engineers whose judgment is overruled under life-endangering circumstances to notify appropriate authorities.
The fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A does not reduce - and may actually strengthen - Engineer A's reporting obligation. The NSPE Code's paramount safety duty in Section I.1 is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. Once Engineer A possessed actual knowledge that occupants of an occupied building faced injury from known code violations, the ethical trigger was complete regardless of how that knowledge was acquired. If anything, the client's voluntary disclosure eliminated any ambiguity about whether the violations existed, removing the epistemic uncertainty that might otherwise counsel caution before reporting. The argument that client-confided information deserves heightened confidentiality protection under Section III.4 is not without force, but it cannot override the explicit exception in Section II.1.c, which releases engineers from confidentiality obligations precisely when public danger is present. The source of the information is therefore ethically irrelevant to the reporting threshold; it is relevant only to the weight of the confidentiality interest being overridden, and even that interest is expressly subordinated by the Code when safety is at stake.
The source of the hazardous information - client voluntary disclosure rather than independent discovery - introduced a genuine complication that the Board did not fully resolve, but that complication does not ultimately alter the outcome. Section III.4 does create a distinct confidentiality weight for information transmitted by a client in confidence, and this distinguishes the case from one where an engineer independently discovers a defect during inspection. However, Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the origin of that knowledge. Once Engineer A possessed knowledge that occupants of an occupied building faced injury from known code violations, the triggering condition for the paramount safety duty was satisfied regardless of how that knowledge was acquired. The source-of-information distinction is therefore relevant to calibrating the confidentiality weight on one side of the balance, but it cannot extinguish the safety obligation on the other side when the hazard is concrete, known, and affecting identifiable persons. This case teaches that Section III.4 and Section II.1.c must be read together, not in isolation: the former establishes that client-transmitted information carries confidentiality expectations, while the latter establishes that those expectations yield when public danger is present.
From a deontological perspective, did Engineer A fulfill their categorical duty to protect public safety when they allowed a contractual confidentiality obligation to override the paramount duty established in NSPE Code Section I.1, given that the code itself contains an explicit exception clause in Section II.1.c that releases engineers from confidentiality when public danger is involved?
From a deontological perspective, Engineer A failed to fulfill his categorical duty to protect public safety. The NSPE Code's structure is explicitly hierarchical: Section I.1 designates public safety as paramount, and Section II.1.c contains an express exception clause that releases engineers from confidentiality obligations when public danger is involved. A deontological analysis does not require Engineer A to calculate consequences - it requires him to follow the duty that the Code itself identifies as supreme. The confidentiality obligation under Sections II.1.c and III.4 is not a categorical duty in the Kantian sense; it is a conditional duty that yields when the paramount duty is triggered. Engineer A's reliance on the confidentiality agreement as a categorical bar to disclosure therefore inverts the Code's own normative hierarchy. He treated a subordinate, conditional obligation as though it were absolute, while treating the paramount, unconditional obligation as though it were merely one consideration among many. This inversion is not a defensible interpretation of the Code - it is a failure to apply the Code's own explicit priority rules.
The tension between client confidentiality and public safety was not genuinely unresolvable in this case - it was falsely treated as such by Engineer A. The NSPE Code does not present these principles as equals requiring ad hoc balancing; it establishes a normative hierarchy in which public safety is explicitly paramount. Section I.1 places the safety, health, and welfare of the public at the apex of engineering obligation, and Section II.1.c contains an explicit exception clause that releases engineers from confidentiality duties precisely when public danger is present. Engineer A's error was not a failure of judgment in a genuinely ambiguous situation but a failure to recognize that the Code had already resolved the tension in advance. By treating confidentiality as an absolute constraint capable of overriding a known life-safety hazard in an occupied building, Engineer A inverted the Code's own priority structure. This case teaches that when the Code itself contains an exception clause addressing the exact conflict an engineer faces, invoking the general confidentiality rule while ignoring the exception is not a defensible ethical position - it is a misreading of the Code's architecture.
From a virtue ethics perspective, did Engineer A demonstrate the professional integrity and moral courage expected of a licensed engineer when, after verbally warning the client of the danger, they passively acquiesced to the client's 'as is' sale directive rather than insisting on remedial action, withdrawing from the project, or escalating to public authorities?
Engineer A's lack of competence in electrical and mechanical engineering does not diminish the reporting obligation and may not be invoked as a scope-of-work defense. The threshold for triggering the public safety duty under Section I.1 requires only that the engineer recognize a risk of injury - not that the engineer be technically qualified to evaluate, quantify, or remediate it. Engineer A explicitly acknowledged recognizing that the disclosed deficiencies could cause injury to occupants. That recognition alone activated the reporting duty. The competence boundary argument, if accepted, would produce an absurd result: engineers would be ethically insulated from reporting known dangers simply because those dangers fall outside their primary discipline. The Code contains no such carve-out, and the Board's precedents in analogous cases confirm that out-of-scope safety findings carry independent disclosure obligations. Engineer A's disciplinary limitations were relevant to the scope of his remediation authority - they were irrelevant to his obligation to notify public authorities of a known hazard.
Engineer A's lack of competence in electrical and mechanical engineering does not diminish his obligation to report the known code violations to public authorities. The threshold for triggering a public safety reporting duty under the NSPE Code requires only that the engineer recognize a risk of injury to the public - not that he be technically qualified to evaluate, diagnose, or remediate the hazard. Engineer A himself acknowledged that the disclosed deficiencies 'could cause injury to the occupants,' which means the recognition threshold was met by his own assessment. The scope-of-work and domain-competence arguments function as incomplete defenses at best: they might limit Engineer A's authority to demand specific corrective measures or to certify the severity of the violations, but they do not limit his capacity to convey to a public authority that a client has disclosed the existence of code violations in an occupied building. Reporting what one knows to those with the competence and authority to investigate is precisely the appropriate response when an engineer encounters a hazard outside his discipline. Domain incompetence is therefore a reason to escalate to qualified authorities, not a reason to remain silent.
From a virtue ethics perspective, Engineer A failed to demonstrate the professional integrity and moral courage expected of a licensed engineer. Virtue ethics asks not merely whether an agent followed rules but whether the agent acted as a person of good character would act in the circumstances. A virtuous engineer, upon learning that occupants of an occupied building faced injury from known code violations, would not have passively acquiesced to the client's 'as is' sale directive after a single verbal warning. Moral courage - a core professional virtue - requires the willingness to act on one's convictions even when doing so is costly, inconvenient, or contrary to a client's economic interests. Engineer A's conduct reflects the opposite disposition: he identified the danger, warned the client privately, documented the warning in a document no one outside the transaction would ever see, and then did nothing further. This pattern of behavior - identifying a problem, performing a minimal gesture, and then acquiescing - is precisely what the BER condemned in Case 84-5 as 'going along' without meaningful dissent. A virtuous engineer would have insisted on remedial action, withdrawn from the project if refused, or escalated to public authorities - not performed a procedural gesture designed to create a record of awareness while ensuring no protective action was taken.
Drawing on the precedent established in BER Case 84-5, if Engineer A had explicitly objected to the client's 'as is' sale decision and formally documented that objection - rather than passively acquiescing after a single verbal warning - would that act of dissent alone have been sufficient to discharge the ethical obligation, or would subsequent escalation to public authorities still have been required?
Engineer A's passive acquiescence after verbally warning the client constitutes an independent ethical violation separate from and in addition to the failure to report to public authorities. The Board's precedent in BER Case 84-5 establishes that an engineer who goes along with a client's safety-compromising decision without formal dissent or escalation commits an ethical violation even if the engineer privately disagreed. Engineer A's single verbal warning, followed by silent compliance with the client's 'as is' sale directive, mirrors precisely the going-along-without-dissent pattern condemned in that precedent. The ethical obligation required Engineer A to either insist on remedial action, formally document objection and withdraw from the project, or escalate to public authorities - not to treat a verbal protest as a terminal act of compliance. Passive acquiescence after a client overrules safety concerns is not a neutral act; it is an affirmative ethical failure under Section II.1.a, which requires engineers whose judgment is overruled under life-endangering circumstances to notify appropriate authorities.
Drawing on the precedent established in BER Case 84-5, formal documentation of Engineer A's objection to the client's 'as is' sale decision - even if it had been explicit and emphatic rather than merely a brief mention in a confidential report - would not alone have been sufficient to discharge the ethical obligation. Case 84-5 established that an engineer who 'goes along' with a client's safety-overriding decision without meaningful dissent commits an independent ethical violation, but the lesson of that case is not that dissent alone is sufficient - it is that dissent is a necessary but not sufficient condition for ethical compliance when public safety is at stake. The NSPE Code's obligation under Section II.1.a requires notification to appropriate authorities when professional judgment is overruled under circumstances that endanger life or property. This is an affirmative duty to act, not merely a duty to object. An engineer who formally objects, documents the objection, and then does nothing further has satisfied the dissent requirement of Case 84-5 but has not satisfied the notification requirement of Section II.1.a. Subsequent escalation to public authorities would therefore still have been required, because the Code's safety obligation is not discharged by internal protest - it is discharged by ensuring that those with authority to protect the public are informed.
Engineer A's passive acquiescence after verbally warning the client constitutes an independent ethical failure distinct from the failure to report to public authorities, and this case teaches that the duty of non-acquiescence has both a procedural and a substantive dimension. Procedurally, as established in BER Case 84-5, an engineer who disagrees with a client's safety-compromising decision must formally document that objection - a single verbal warning does not satisfy the requirement. Substantively, even formal objection and documented dissent do not discharge the engineer's obligation when the hazard remains active and occupants remain exposed: the engineer must either insist on remedial action, withdraw from the project, or escalate to public authorities. The brief mention in a confidential report satisfies neither the procedural nor the substantive dimension - it is a record that ensures the information will never reach those who need it, while creating a superficial appearance of disclosure. This case therefore teaches that the principle requiring insistence on remedial action or withdrawal under Section II.1.a and the principle requiring appropriate authority notification when professional judgment is overruled are sequential obligations, not alternatives: exhausting one does not eliminate the other.
If Engineer A had refused to accept the confidentiality agreement as a condition of engagement - or had negotiated an explicit carve-out permitting disclosure of life-safety code violations to public authorities - would the ethical conflict between client confidentiality and occupant safety have arisen at all, and does the failure to negotiate such terms itself constitute an ethical lapse?
The ethical analysis reveals a structural problem that preceded Engineer A's conduct during the engagement: the failure to negotiate a life-safety carve-out from the confidentiality agreement at the outset. An engineer who accepts a blanket confidentiality agreement without reserving the right to disclose safety-critical information to public authorities has, at the moment of contracting, already compromised the ability to fulfill the paramount duty under Section I.1. While the Board did not address this antecedent failure, it represents a distinct ethical lapse - not merely a procedural oversight. Engineers are not passive recipients of contract terms; they are professionals with independent ethical obligations that cannot be contracted away. Accepting confidentiality terms that purport to suppress life-safety disclosures, without negotiating explicit exceptions, creates the very conflict that Engineer A later used as a justification for inaction. The ethical obligation to protect public safety begins before the engagement commences and includes the duty to structure contractual arrangements in ways that preserve - rather than foreclose - the ability to fulfill that obligation.
Engineer A's failure to negotiate a carve-out from the confidentiality agreement for life-safety code violations before accepting the engagement represents a preliminary ethical lapse that created the conditions for all subsequent failures. A prudent engineer, aware that he was being retained to inspect an occupied building and that confidentiality would be required, should have anticipated that the inspection might uncover - or that the client might disclose - safety-critical information. Negotiating an explicit exception permitting disclosure of life-safety violations to public authorities would have been consistent with the NSPE Code's paramount safety obligation and would have placed the client on notice from the outset that safety disclosures were non-negotiable. The failure to do so does not excuse Engineer A's subsequent inaction - the Code's safety obligations exist independently of contractual terms and cannot be waived by agreement - but it does represent a missed opportunity to prevent the ethical conflict from arising at all. Engineers who accept confidentiality agreements without safety carve-outs in contexts where safety-critical discoveries are foreseeable are not merely passive victims of an unforeseen conflict; they are partially responsible for creating the conditions that made the conflict inevitable.
If Engineer A had immediately notified the appropriate public authorities upon learning of the electrical and mechanical code violations - rather than merely mentioning them in a confidential report - what would the likely consequences have been for the building occupants, the client's sale transaction, and Engineer A's professional standing, and would those consequences have been ethically preferable to the outcome that actually occurred?
Had Engineer A immediately notified the appropriate public authorities upon learning of the electrical and mechanical code violations, the most likely consequences would have been: regulatory inspection of the building, potential enforcement action requiring remediation before occupancy could continue or the sale could proceed, protection of current occupants from ongoing exposure to the hazard, and possible delay or restructuring of the client's 'as is' sale. These consequences would have been ethically preferable to the outcome that actually occurred - in which occupants remained exposed, the client proceeded with a sale concealing known violations, and Engineer A's conduct was ultimately condemned. The client's short-term economic interests would have been disrupted, but the client had no legitimate interest in selling a building with known, code-violating safety defects to an uninformed buyer while current occupants remained at risk. Engineer A's professional standing would have been protected, not harmed, by compliance with the Code's paramount safety obligation. The counterfactual therefore confirms that the ethically correct action was available, feasible, and would have produced better outcomes for every party except the client's immediate economic interest - which the Code does not recognize as a legitimate basis for suppressing safety disclosures.
If Engineer A had been a licensed electrical or mechanical engineer rather than solely a structural engineer, would the scope-of-work and domain-competence arguments invoked as partial defenses have carried any weight, or would the ethical obligation to report known life-safety code violations to public authorities have been even more clearly triggered regardless of disciplinary boundaries?
If Engineer A had been a licensed electrical or mechanical engineer rather than solely a structural engineer, the scope-of-work and domain-competence arguments would have carried no weight whatsoever, and the ethical obligation to report the known life-safety code violations to public authorities would have been even more clearly and unambiguously triggered. The domain-competence argument, as applied in the actual case, is already an incomplete defense - it limits Engineer A's authority to evaluate or certify the violations but does not limit his duty to report what he knows. In the counterfactual where Engineer A possessed full competence in the relevant domains, he would have had both the knowledge and the technical authority to assess the severity of the violations, making the case for reporting even stronger. This counterfactual confirms that domain incompetence functions as a marginal modulator of the reporting obligation at most - it might affect the specificity of what the engineer reports, but it cannot eliminate the duty to report the existence of known hazards to those with authority to investigate and enforce. The reporting obligation is triggered by knowledge of danger, not by technical mastery of the domain in which the danger exists.
Decisions & Arguments
View ExtractionCausal-Normative Links 5
- Engineer A Brief Report Mention Insufficiency Public Authority Safety Notification
- Engineer A Competing Confidentiality Safety Code Provision Contextual Balancing
- Engineer A Brief Report Mention Insufficiency Public Authority Safety Notification
- Engineer A Tenant Occupant Direct Notification Electrical Mechanical Violations
- Engineer A Post-Client-Override Public Safety Escalation Assessment
- Engineer A Appropriate Authority Notification After Client Safety Override Failure
- Engineer A Going-Along After Client Safety Refusal Independent Ethical Violation
- Client-Disclosed Safety Hazard Out-of-Scope Reporting Obligation
- Engineer A Client-Disclosed Safety Hazard Out-of-Scope Reporting
- Engineer A Brief Report Mention Insufficiency Public Authority Safety Notification
- Engineer A Tenant Occupant Direct Notification Electrical Mechanical Violations
- Engineer A Post-Client-Override Public Safety Escalation Assessment
- Engineer A Occupied Building Electrical Mechanical Violation Occupant Escalation
- Engineer A Client Safety Violation Insistence or Project Withdrawal
- Engineer A Out-of-Discipline Electrical Mechanical Code Violation Public Authority Reporting
- Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting
- Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
- Engineer A Tenant Occupant Direct Notification Electrical Mechanical Violations
- Engineer A Post-Client-Override Public Safety Escalation Assessment
- Engineer A Appropriate Authority Notification After Client Safety Override Failure
- Engineer A Going-Along After Client Safety Refusal Independent Ethical Violation
- Engineer A Client Safety Violation Insistence or Project Withdrawal
- Occupied Building Electrical-Mechanical Code Violation Occupant Injury Risk Escalation Obligation
- As-Is Sale Client Directive Safety Reporting Non-Override Obligation
- Section II.1.c. Law-or-Code-Authorized Confidentiality Release Obligation
- Appropriate Authority Notification After Professional Judgment Safety Override Obligation
- Going-Along Prohibition After Client Safety Refusal Obligation
- Paramount Safety Obligation Hierarchy Supremacy Principle
- Section III.4 Confidentiality Client-Transmitted Information Engagement Obligation
- Engineer A Section III.4 Client-Transmitted Confidentiality Engagement Recognition
- Engineer A Paramount Safety Word Supremacy Hierarchy Non-Recognition
- Engineer A Ethics Code Cross-Provision Non-Vacuum Reading Failure
- Engineer A Scope of Work Non-Shield Electrical Mechanical Safety Disclosure
- Client-Disclosed Safety Hazard Out-of-Scope Reporting Obligation
Decision Points 5
Should Engineer A report the client-disclosed electrical and mechanical code violations to appropriate public authorities, or treat the confidentiality agreement as a complete bar to external disclosure?
The paramount safety obligation in Section I.1 places public safety above all competing duties, and Section II.1.c explicitly releases engineers from confidentiality when public danger is present, together these provisions required Engineer A to report to public authorities. Competing: Section III.4 creates a genuine and distinct confidentiality weight for information voluntarily transmitted by a client in confidence, and the faithful agent role under Section II.4 supports honoring the contractual arrangement Engineer A accepted.
Uncertainty arises because the client-transmitted nature of the information engages Section III.4 in a way that independently discovered violations would not, potentially modulating the confidentiality weight upward. Additionally, the violations fell outside Engineer A's structural engineering scope, creating a plausible argument that his reporting authority was constrained by domain incompetence. The confidentiality agreement was a voluntarily accepted contractual obligation, not merely an informal expectation.
The client voluntarily disclosed to Engineer A that the 60-year-old occupied apartment building contains electrical and mechanical code violations that could injure occupants. Engineer A verbally warned the client of the danger. The client declared the building would be sold 'as is' with no remedial action. Engineer A had signed a confidentiality agreement. Engineer A made only a brief mention of the violations in his confidential structural report and declined to notify any public authority.
After the client refused remediation, should Engineer A have escalated to public authorities or formally withdrawn from the project, or was a brief mention of the violations in the confidential structural report a sufficient discharge of his ethical obligation?
Section II.1.a requires engineers whose professional judgment is overruled under circumstances endangering life or property to notify appropriate authorities, a single verbal warning followed by silent compliance does not satisfy this affirmative duty. BER Case 84-5 establishes that going along with a client's safety-compromising decision without meaningful dissent or escalation constitutes an independent ethical violation. Competing: Engineer A did warn the client, did document the conversation, and the violations fell outside his structural engineering scope, providing a plausible basis for treating client notification as the limit of his authority to act.
Uncertainty is created by the question of whether a verbal warning followed by written documentation, even in a confidential report, satisfies the procedural dissent requirement of BER Case 84-5, and whether the scope-of-work limitation on Engineer A's authority to demand corrective action on electrical and mechanical systems reduces the substantive escalation obligation. The competence-boundary argument is strongest if Engineer A genuinely could not assess the severity of the violations and therefore could not represent their urgency to public authorities with professional confidence.
Engineer A verbally warned the client that the electrical and mechanical deficiencies could injure building occupants. The client responded by declaring the building would be sold 'as is' with no remedial action. Engineer A then completed his structural report, including only a brief mention of the conversation about the deficiencies, and took no further action, neither escalating to public authorities nor withdrawing from the project. The building's occupants remained continuously exposed to the known hazards.
Should Engineer A report the client-disclosed electrical and mechanical violations to public authorities despite lacking competence in those domains, or does his structural-only scope of work and domain incompetence limit his reporting obligation to client notification alone?
The NSPE Code's public safety duty under Section I.1 is triggered by recognition of injury risk, not by technical competence to evaluate or remediate the hazard. Engineer A's own acknowledgment that the deficiencies could injure occupants satisfied the recognition threshold, making domain incompetence a reason to escalate to qualified authorities rather than a reason to remain silent. Competing: The faithful agent role under Section II.4 and the scope-of-work limitation provide a plausible basis for treating Engineer A's authority to demand corrective action, and therefore his reporting obligation, as bounded by his structural engineering discipline, particularly where the violations were client-disclosed rather than independently assessed.
Uncertainty is created by the absence of explicit NSPE Code language specifying whether out-of-discipline safety observations trigger the same reporting obligation as in-discipline findings. The competence-boundary argument carries its greatest force when the engineer cannot independently verify the existence or severity of the hazard, but here the client's own admission eliminated that epistemic gap, potentially collapsing the distinction between in-discipline and out-of-discipline observations for reporting purposes.
Engineer A is a structural engineer retained to assess the structural integrity of a 60-year-old occupied apartment building. The client disclosed that the building contains electrical and mechanical code violations. Engineer A is not an electrical or mechanical engineer and the violations fell outside his structural scope of work. Nevertheless, Engineer A himself recognized that the deficiencies could cause injury to the building's occupants. Engineer A informed the client of this risk but did not report the violations to any public authority.
Should Engineer A report the known electrical and mechanical code violations to appropriate public authorities, or confine disclosure to a brief mention in the confidential structural report delivered only to the client?
Warrant for reporting: Section I.1 designates public safety as paramount; Section II.1.a requires notification of appropriate authorities when professional judgment on life-endangering matters is overruled; Section II.1.c explicitly releases engineers from confidentiality obligations when public danger is present; Engineer A's own acknowledgment that the violations could injure occupants satisfied the recognition threshold regardless of his domain incompetence in electrical and mechanical systems; client-voluntary disclosure eliminates epistemic uncertainty and strengthens rather than weakens the reporting obligation; passive acquiescence after a single verbal warning constitutes an independent ethical failure under BER Case 84-5. Warrant for limiting disclosure to confidential report: Section III.4 creates a distinct confidentiality weight for information transmitted by a client in confidence; the faithful agent obligation under Section II.4 supports deference to client direction within ethical limits; Engineer A's scope of work was structural, not electrical or mechanical, arguably limiting his authority to assess or certify the severity of the violations; the client's voluntary disclosure may be argued to carry heightened confidentiality expectations distinct from independently discovered defects.
Uncertainty arises from several sources: (1) Section III.4's protection of client-transmitted confidential information creates a genuine competing weight that the Code does not explicitly subordinate in the same explicit language as Section II.1.c's exception clause, leaving open whether the source-of-information distinction modulates the reporting threshold; (2) Engineer A's lack of competence in electrical and mechanical engineering could be argued to limit his capacity to assess whether the hazard rises to the level of 'imminent danger' required to trigger the exception clause; (3) the Code does not specify the minimum form or channel that safety notification must take, leaving open whether a written record in a professional report, even a confidential one, constitutes partial compliance; (4) the faithful agent role is itself bounded by ethical limits, but the precise boundary between legitimate client loyalty and impermissible safety suppression is not always self-evident from the Code's text alone.
Engineer A was retained by a client to conduct a structural integrity assessment of a 60-year-old occupied apartment building under a confidentiality agreement. During the engagement, the client voluntarily disclosed the existence of electrical and mechanical code violations. Engineer A verbally warned the client that the deficiencies could cause injury to occupants, noted the violations briefly in the confidential structural report, and then declined to report them to any public authority or to notify the building's occupants. The client proceeded with an 'as is' sale. Occupants remained continuously exposed to the known hazards. Engineer A's conduct was subsequently condemned.
After the client refuses remediation, should Engineer A escalate by formally documenting objection and notifying occupants or public authorities, withdraw from the project, or treat the verbal warning as sufficient discharge of the safety obligation and proceed with delivering the confidential report?
Warrant for escalation beyond verbal warning: BER Case 84-5 establishes that passive acquiescence after a client overrules safety concerns constitutes an independent affirmative ethical violation; Section II.1.a requires notification of appropriate authorities when professional judgment on life-endangering matters is overruled, a verbal warning to the client does not satisfy this obligation; the paramount safety obligation under Section I.1 is not exhausted by the single channel of regulatory notification and may independently require direct notification to occupants who are the parties most immediately and continuously exposed to the hazard and who have no other means of learning of the danger; moral courage as a core professional virtue requires sustained action, not a minimal procedural gesture followed by acquiescence. Warrant for treating verbal warning as sufficient: The faithful agent obligation under Section II.4 supports deference to client direction after the engineer has discharged a warning duty; Engineer A's scope of work was structural, and the violations fell outside his discipline, arguably limiting his authority to demand corrective action on electrical and mechanical systems; a single verbal warning, if genuine, may satisfy the spirit of the dissent requirement under a narrow reading of BER Case 84-5; the confidentiality agreement may be argued to constrain the channels through which Engineer A could escalate.
Uncertainty is created by several factors: (1) BER Case 84-5 may be read narrowly to require only that the engineer not 'go along without dissent,' leaving open whether formal documentation and escalation are required or whether a genuine verbal warning satisfies the dissent standard; (2) the NSPE Code does not explicitly specify occupant direct notification as a required channel distinct from regulatory reporting, leaving open whether 'appropriate public authorities' encompasses or exhausts the notification obligation; (3) the competence-boundary argument creates genuine uncertainty about whether Engineer A had the authority to insist on remediation of electrical and mechanical systems outside his structural scope; (4) the question of whether passive acquiescence after a verbal warning constitutes an independent ethical violation separate from the failure to report to authorities depends on whether the two obligations are sequential or alternative, a question the Code does not resolve with complete clarity.
After completing the structural assessment and learning of the electrical and mechanical violations through client disclosure, Engineer A verbally warned the client that the deficiencies could cause injury to occupants. The client directed Engineer A to proceed on an 'as is' basis. Engineer A noted the violations briefly in the confidential structural report, delivered the report to the client, and took no further action: neither formally documenting objection, withdrawing from the project, notifying public authorities, nor contacting the building's occupants. The occupants remained continuously exposed to the hazard. Engineer A's conduct was subsequently condemned. BER Case 84-5 had previously established that an engineer who 'goes along' with a client's safety-compromising decision without meaningful dissent commits an independent ethical violation.
Event Timeline
Causal Flow
- Accepting Confidentiality Agreement Conducting Structural Integrity Tests
- Conducting Structural Integrity Tests Verbally Warning Client of Danger
- Verbally Warning Client of Danger Documenting Conversation in Report
- Documenting Conversation in Report Declining to Report Violations Externally
- Declining to Report Violations Externally Occupants Remain Exposed to Hazard
Opening Context
View ExtractionYou are a licensed structural engineer retained by a client to assess the structural integrity of a 60-year-old occupied apartment building prior to its sale. Your agreement specifies that your report is confidential, and the client has stated the building will be sold as-is with no repairs or renovations planned. Your structural testing is complete, and the building is sound. During the engagement, however, the client disclosed that the building contains electrical and mechanical deficiencies that violate applicable codes, conditions outside your area of licensure but ones you recognize as potential hazards to the current occupants. You have noted the conversation briefly in your structural report, but have not contacted any public authority or third party about the violations. The decisions you face now concern your obligations to the occupants, your client, and the limits of your professional and ethical duties.
Characters (7)
Vulnerable residents of an aging occupied apartment building who remain unknowingly exposed to injury risk from undisclosed electrical and mechanical code violations throughout the sale process.
- Motivated by the basic expectation of safe habitation and the reasonable assumption that their living environment meets legal safety standards, with no awareness that known violations are being concealed during a confidential transaction.
A property owner strategically leveraging a confidentiality agreement and an as-is sale structure to transfer a non-compliant building while minimizing disclosure obligations and remediation costs.
- Motivated primarily by financial self-interest — maximizing sale proceeds by avoiding costly code compliance remediation while using contractual confidentiality as a shield against liability and public disclosure.
A cost-driven client who, when advised by their retained engineer that full-time on-site safety oversight was necessary during a dangerous construction phase, refused to authorize the measure on purely financial grounds.
- Motivated by short-term budget preservation, prioritizing immediate cost savings over worker and public safety, and applying financial pressure on the engineer to proceed without the professionally required safeguard.
A professionally retained structural engineer who fulfills the narrow technical scope of his engagement by confirming structural soundness but responds inadequately to collateral safety violations by limiting his action to a verbal notice and a brief report notation.
- Motivated by a desire to honor his contractual confidentiality obligation and maintain the client relationship, while making a minimal good-faith gesture toward safety disclosure that ultimately falls short of his paramount ethical duty to the public.
Engineer A received confidential information from the client during professional service delivery that implicated public safety. Rather than notifying appropriate authorities or refusing to proceed, Engineer A 'went along' and continued work, subordinating the paramount public safety obligation to client confidentiality. The Board found this conduct ethically impermissible under the Code.
The client transmitted confidential business information to Engineer A during the course of professional service delivery. This information implicated public safety. The client's interest in maintaining confidentiality conflicted with Engineer A's paramount obligation to notify appropriate authorities.
Referenced analogously from Case 84-5: an engineer who recommended a full-time on-site project representative for a dangerous construction phase, then abandoned that recommendation when the client objected on cost grounds and proceeded with the work. The Board found this conduct unethical and used it as the precedent framework for evaluating Engineer A's conduct in the present case.
Tension between Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting and Confidentiality Principle Invoked By Engineer A Under Contractual Agreement
Tension between Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure and Scope-of-Work Limitation Invoked As Incomplete Defense By Engineer A
Tension between Engineer A Out-of-Discipline Electrical Mechanical Code Violation Public Authority Reporting and Engineer A Scope of Work Non-Shield Electrical Mechanical Safety Disclosure
Tension between Paramount Safety Obligation Hierarchy Supremacy — Public Authority Notification Duty and Confidentiality Agreement Accepted Under Client Engagement
Tension between Non-Acquiescence to Unsafe Client Directives — Post-Refusal Escalation Obligation and Client Refusal of Remediation Under As-Is Sale Directive
Engineer A is bound by a confidentiality agreement with the client, who disclosed electrical and mechanical code violations in confidence. The obligation demands that confidentiality cannot legally or ethically excuse non-reporting of safety violations, yet the constraint recognizes that the client's reasonable expectation of confidentiality — especially for information disclosed voluntarily and outside the engineer's formal scope — carries genuine moral weight. Fulfilling the reporting obligation requires breaching a contractual and relational trust; honoring the confidentiality constraint risks leaving occupants exposed to known hazards. This is a genuine dilemma because both duties are grounded in recognized ethical principles (NSPE Code II.1.c vs. II.1.b), not merely competing preferences.
The engineer has a clear obligation to escalate known electrical and mechanical code violations that pose injury risk to current building occupants. However, the client has invoked a legitimate business decision — selling the property as-is — which constrains the engineer from unilaterally overriding client authority over property disposition. The tension is genuine because the as-is sale directive is not inherently fraudulent or illegal as a business choice, yet the occupants currently residing in the building face ongoing, unmitigated risk during the sale process. Escalating to public authorities may protect occupants but effectively overrides a client business decision the engineer was not retained to adjudicate.
Engineer A may have attempted to discharge safety duties by briefly mentioning the violations in the written report to the client, but the obligation establishes that such a mention is ethically insufficient — direct notification to public authorities is required when client remediation is refused. The constraint, however, marks a boundary on how far the engineer may go in disclosing confidential client information externally. This creates a dilemma of degree and method: the engineer must do more than mention the hazard internally, yet doing more means crossing the confidentiality boundary the constraint protects. The tension is not merely procedural — it determines whether Engineer A's ethical duty is satisfied or violated.
Opening States (10)
Key Takeaways
- Confidentiality agreements cannot override an engineer's fundamental obligation to report known safety violations to public authorities, regardless of contractual provisions.
- An engineer's lack of technical competence in a specific discipline does not eliminate the duty to report observed code violations that pose public safety risks — awareness, not expertise, triggers the reporting obligation.
- Passive acquiescence to known safety violations constitutes an independent ethical failure, meaning silence itself is a breach of professional duty even when the engineer argues limited scope of work.