Step 4: Full View

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.

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.

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.

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.

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.

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.

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 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.

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.

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 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.

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.

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.

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.

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.

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.

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.

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.