Step 4: Review

Hold paramount the safety, health, and welfare of the public.

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.

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.

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

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.

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.

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.

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.

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.

It was unethical for Engineer A not to report the safety violations to the appropriate public authorities.

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.

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

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

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.

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

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.

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.

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.

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.

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

Was it ethical 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?

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?

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?

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?

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?

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?

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?

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?

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

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?

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?

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?

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?

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?

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?

Accepting the confidentiality agreement fulfills Engineer A's Section III.4 client-transmitted confidentiality obligation but simultaneously creates the foundational tension that leads to downstream violations of the paramount safety hierarchy and cross-provision code integration obligations, because the agreement is accepted without recognizing its non-absolute character under Section II.1.c.

Conducting structural integrity tests fulfills Engineer A's contracted scope of work and is guided by competence boundary recognition, but the constraint that scope-of-work limitations cannot shield the engineer from out-of-discipline safety disclosure obligations means this action alone is ethically insufficient when electrical and mechanical violations are subsequently disclosed.

Verbally warning the client partially discharges the client notification obligation but is constrained to insufficiency because it does not escalate to appropriate public authorities, does not directly notify occupants, and does not constitute the insistence on remedial action or project withdrawal that the paramount safety obligation requires after the client refuses to act.

Documenting the conversation in the confidential report superficially records the safety concern but simultaneously violates multiple obligations because the report is confined to the client under the confidentiality agreement, making it an act of passive acquiescence rather than genuine escalation, and the constraint that a brief report mention is insufficient for public authority safety notification means this action does not discharge Engineer A's paramount safety duties.

Declining to report violations externally is the central ethical failure of the case, violating the full spectrum of paramount safety obligations, appropriate authority notification duties, and the Section II.1.c. exception clause that releases Engineer A from confidentiality when public safety is at risk, while being guided only by a misapplied and absolutist reading of the confidentiality principle that the NSPE Code and BER precedents explicitly prohibit.

This question arose because Engineer A's inaction sits at the intersection of two legitimate but competing professional duties - contractual confidentiality and paramount public safety - neither of which is absolute on its face. The question crystallizes when the data (known code violations in an occupied building, deliberate non-reporting) is evaluated against the NSPE Code's internal hierarchy, which the BER ultimately resolved in favor of public safety but which Engineer A's conduct treated as resolved in favor of confidentiality.

This question emerged because the mechanism by which Engineer A learned of the violations - voluntary client disclosure - introduces a legally and ethically significant variable that the base question (Q1) does not resolve: whether the trust relationship created by client-initiated disclosure creates a stronger confidentiality shield or is simply irrelevant to the paramount safety obligation. The tension between Section III.4's client-transmitted-information engagement and Section II.1.c's safety exception clause makes the source of information a genuine warrant-level dispute rather than a mere factual detail.

This question emerged because Engineer A's report mention creates an ambiguous factual record: he did not remain entirely silent, yet the structural confidentiality of the report ensured the information was functionally suppressed from those who needed it. The question forces analysis of whether ethical obligations are discharged by the act of documentation or by the functional outcome of information reaching those who can act on it - a warrant-level dispute about what 'notification' means in the context of public safety.

This question emerged because Engineer A's structural-only licensure creates a genuine professional boundary that could plausibly rebut the reporting obligation - he was not retained to evaluate electrical or mechanical systems and lacks the competence to do so. The question forces resolution of whether the public-safety duty is competence-gated (requiring technical authority to assess the hazard) or hazard-recognition-gated (requiring only awareness that occupants face injury risk), a distinction with significant implications for how broadly the paramount safety obligation extends across disciplinary lines.

This question emerged because the standard framing of the reporting obligation focuses on public authorities and regulatory bodies, but the occupants of the building are a distinct class of affected parties who are immediately exposed, identifiable, and unable to protect themselves - a factual configuration that raises the question of whether the public-safety duty has a direct-notification dimension that is separate from, and potentially more urgent than, the regulatory-reporting dimension. The tension between the client's confidentiality interest and the occupants' proximate safety interest generates a warrant dispute that the base question (Q1) does not resolve.

This question emerged because Engineer A's situation instantiated two legitimate NSPE Code provisions pointing in opposite directions: the duty of loyalty to the client (faithful agent) and the paramount duty to public safety with an explicit confidentiality exception. The question crystallizes the structural conflict between these provisions and demands a priority rule specifying which controls and under what triggering conditions.

This question arose because the case introduced a factual wrinkle - the violations were disclosed by the client, not discovered independently - that maps onto a genuine tension between two NSPE Code provisions (II.1.c and III.4) that have never been explicitly reconciled when the source of safety-critical information is the client itself. The question forces analysis of whether information provenance is ethically relevant to the reporting duty.

This question emerged because Engineer A occupied a structurally defined scope of work while receiving safety-critical information about systems entirely outside that scope, placing two legitimate professional norms in direct conflict: the duty to act on known safety hazards and the duty to respect the boundaries of one's professional competence and engagement. The question asks whether scope limitations can ever justify inaction on disclosed dangers.

This question arose because Engineer A's conduct after the client refused remediation involved multiple distinct acts (verbal warning, documentation, continued engagement, non-escalation) each of which maps onto a different ethical norm, and the question forces analysis of whether any single defense (competence limits, confidentiality) can simultaneously defeat all applicable warrants or whether passive acquiescence constitutes an independent violation that survives even successful rebuttal of the reporting duty.

This question emerged because the case presents a situation where the engineer's own professional code contains an internal resolution mechanism (Section II.1.c) that should have dissolved the apparent conflict between confidentiality and safety, yet Engineer A acted as though the conflict were irresolvable - making the ethical failure not merely a matter of choosing the wrong value but of failing to read the code's own normative hierarchy correctly. From a deontological perspective, this raises the question of whether the categorical duty was violated by the substantive choice or by the prior failure to integrate the code's provisions.

This question emerged because the data - known code violations in an occupied building, a confidential report as the sole disclosure vehicle, and continued occupant exposure - creates a direct tension between the consequentialist warrant to maximize welfare for all affected parties and the confidentiality warrant that Engineer A invoked. The question crystallizes because the chosen action (brief confidential mention) sits between two cleaner consequentialist poles, making it impossible to assess optimality without specifying counterfactual outcomes.

This question arose because the data reveals a two-stage pattern - Engineer A warned the client but then acquiesced - that sits in the gap between full ethical compliance and clear violation under virtue ethics. The passive acquiescence state, combined with the client's 'as is' directive and continued occupant exposure, forces the question of whether warning alone satisfies the virtue of professional integrity or whether moral courage demands more active resistance, a question the NSPE Code does not resolve with precision.

This question emerged because the data introduces a factual distinction - voluntary client disclosure versus independent discovery - that maps onto competing code provisions with different confidentiality weights, creating genuine ambiguity about whether the source of safety-critical information alters the engineer's reporting duty. The question crystallizes because NSPE Section I.1's knowledge-based framing appears source-neutral, yet Section III.4's client-transmission confidentiality principle appears to create a stronger obligation, and no code provision explicitly resolves the conflict.

This question arose because the data shows that the ethical conflict between confidentiality and public safety was structurally embedded in the engagement terms from the outset, raising the counterfactual question of whether the conflict was preventable through better contract negotiation. The question crystallizes because it contests whether ethical responsibility is purely reactive (resolve conflicts as they arise) or also proactive (structure engagements to prevent foreseeable conflicts), a distinction the NSPE Code does not explicitly address in the context of pre-engagement confidentiality agreements.

This question arose because the data - inaction in the face of known hazards, continued occupant exposure, and retrospective condemnation - creates pressure to evaluate the road not taken, forcing a comparison between the actual outcome and the counterfactual outcome of immediate notification. The question crystallizes because the competing warrants (paramount safety versus confidentiality and proportionality) generate different predictions about what immediate notification would have produced, and the ethical preferability of the counterfactual depends entirely on empirical assumptions about regulatory response, client reaction, and professional consequences that the record does not resolve.

This question arose because Engineer A's structural-only licensure created a plausible but contested jurisdictional defense: the argument that an engineer cannot be obligated to report violations outside their licensed domain appeared facially reasonable, yet the data showed the violations were client-disclosed facts rather than Engineer A's independent findings, stripping the competence argument of its epistemic justification. The question therefore probes whether disciplinary licensure boundaries can modulate - or are entirely irrelevant to - the paramount safety reporting obligation when the engineer's knowledge derives from client disclosure rather than technical assessment.

This question arose because BER Case 84-5 established a going-along-without-dissent prohibition that Engineer A partially satisfied through verbal warning and report documentation, creating genuine ambiguity about whether the precedent sets a floor (dissent is the minimum) or a ceiling (dissent is sufficient) for ethical compliance. The persistence of occupant exposure after the client's 'as is' decision introduced a third-party harm dimension that the original Case 84-5 context - a bilateral engineer-client safety staffing dispute - did not squarely address, making it contestable whether the dissent-discharge rule extends to situations where identifiable non-consenting third parties remain at risk.

The board concluded that Engineer A's lack of electrical and mechanical competence was irrelevant to his reporting obligation because the NSPE Code's public safety duty is triggered by recognition of risk, not by technical mastery of the hazard - and Engineer A's own words confirmed he had crossed that recognition threshold, making domain incompetence a reason to escalate rather than a defense for silence.

The board concluded that Engineer A had an independent ethical obligation to consider notifying the building's occupants directly because they are the parties most immediately harmed by the hazard, they lack the information needed to protect themselves, and no confidentiality interest runs in their direction - making Engineer A's failure to even consider this pathway an additional ethical shortcoming beyond the failure to notify authorities.

The board reached the core ethical determination that Engineer A's failure to report was unethical because the NSPE Code's paramount safety obligation required external disclosure once Engineer A recognized a risk of injury to occupants, and none of the defenses Engineer A implicitly relied upon - confidentiality, scope of work, or disciplinary boundaries - were sufficient to override that obligation.

The board concluded that Engineer A's reliance on the confidentiality agreement as an absolute bar to reporting reflected a fundamental misreading of the NSPE Code, because Section II.1.c explicitly provides an exception for public danger situations - meaning the ethical failure was not merely choosing confidentiality over safety, but treating a conditional obligation as unconditional and never activating the exception the Code itself supplies.

The board concluded that the voluntary nature of the client's disclosure strengthened rather than weakened Engineer A's reporting obligation because the Code's safety duty turns on what the engineer knows, not how he came to know it - and a direct client admission eliminates the epistemic uncertainty that might otherwise counsel caution, providing the engineer with the most reliable possible confirmation that the hazard exists.

The board concluded that embedding safety-critical findings in a contractually shielded document is not a partial discharge of the notification duty but an affirmative ethical failure, because the Code's public safety provisions are directed at ensuring endangered parties receive actionable information - an outcome the confidential mention structurally prevented from occurring.

The board concluded that Engineer A's lack of electrical and mechanical competence was irrelevant to the reporting obligation because the Code's safety duty is activated by the engineer's recognition of a risk of injury - a threshold Engineer A explicitly met - and that permitting a competence defense would create an uncodified and ethically indefensible loophole.

The board concluded that Engineer A's passive acquiescence constitutes an independent ethical violation separate from the failure to notify public authorities, because BER Case 84-5 establishes that going along with a client's safety-compromising decision without formal dissent or escalation is itself a breach of Section II.1.a, and a single verbal protest does not satisfy that standard.

The board concluded that Engineer A's failure to negotiate a life-safety carve-out from the confidentiality agreement at the outset constitutes a distinct antecedent ethical lapse, because accepting blanket confidentiality terms that purport to suppress safety disclosures is itself a violation of the paramount duty under Section I.1 - one that created the very conflict Engineer A subsequently used as a justification for inaction.

The board concluded that the voluntary nature of the client's disclosure does not reduce Engineer A's reporting obligation and may actually strengthen it, because the Code's safety duty attaches to the engineer's knowledge of danger regardless of its source, and the client's disclosure eliminated the epistemic uncertainty that might otherwise counsel caution - while Section II.1.c expressly overrides confidentiality when public danger is present.

The board concluded that Engineer A's brief mention in the confidential report was not a meaningful discharge of his ethical obligation because disclosure confined to a document the client controls and regulators never see is functionally equivalent to no disclosure at all; the notation created a false paper trail of compliance while structurally guaranteeing the information would never reach those with the power or need to act on it.

The board concluded that Engineer A committed a category error by treating the faithful agent principle as unconditional and supreme when the Code itself designates it as subordinate to public safety; because the precise triggering condition - known, code-violating hazards in an occupied building - was present, the paramount safety obligation controlled and the confidentiality-based reading of faithful agency was not a defensible interpretation of the Code's normative structure.

The board concluded that Engineer A could not justify his failure to disclose by appealing to Section III.4's confidentiality protection for client-transmitted information, because Section II.1.c is a specific exception clause that overrides the general confidentiality rule when public danger is present - and the Code, read as an integrated system, resolves that conflict unambiguously in favor of disclosure regardless of whether the engineer discovered the violations independently or learned of them from the client.

The board concluded that from a deontological perspective Engineer A failed his categorical duty because the Code's own hierarchy - not a consequentialist weighing - required him to treat public safety as supreme and confidentiality as conditional; his inversion of that hierarchy, treating a subordinate conditional obligation as absolute while demoting the paramount obligation to merely one factor among many, was not a defensible interpretation of the Code but a failure to apply its explicit priority rules.

The board concluded that Engineer A's decision to limit disclosure to a confidential report produced the worst reasonably foreseeable outcome for all parties: occupants remained continuously exposed to known hazards, the client incurred future liability risk from undisclosed defects, and Engineer A's professional standing was condemned - whereas notifying public authorities would have triggered regulatory inspection, potentially required remediation before sale, and protected occupants, aligning the consequentialist conclusion with the deontological one reached in Conclusion 4.

The board concluded that Engineer A failed the virtue ethics standard not merely because he violated a rule but because his conduct - identifying danger, performing a minimal gesture, and then acquiescing - revealed a disposition of professional cowardice rather than integrity; a virtuous engineer would have insisted on remediation, withdrawn, or escalated, and the board used BER Case 84-5 to confirm that this pattern of behavior had already been recognized as ethically condemned.

The board concluded that Engineer A's failure to negotiate a life-safety carve-out before accepting the engagement was itself an ethical lapse because a prudent engineer foreseeing safety-critical discoveries in an occupied building should have placed the client on notice from the outset that safety disclosures were non-negotiable, and the failure to do so made Engineer A partially responsible for creating the very conflict he later used as a justification for inaction.

The board concluded that the consequentialist analysis confirmed the ethical correctness of reporting because every affected party - occupants, the prospective buyer, Engineer A's professional standing, and the integrity of the regulatory system - would have been better served by immediate notification to public authorities, and the only outcome that would have been worse was the client's ability to complete an economically advantageous but ethically illegitimate concealed-defect sale.

The board concluded that the domain-competence argument was at most a marginal modulator of the reporting obligation rather than a defense against it, because the counterfactual analysis - in which a fully competent engineer would have had an even clearer duty to report - confirmed that the reporting threshold is set by knowledge of danger rather than technical mastery, and that Engineer A's structural-only licensure affected only the specificity of his report, not his obligation to make one.

The board concluded that even explicit, formally documented objection to the client's 'as is' sale decision would not alone have discharged Engineer A's ethical obligation, because BER Case 84-5 establishes dissent as a floor rather than a ceiling, and Section II.1.a's affirmative notification duty requires escalation to public authorities as a separate and subsequent obligation that internal protest cannot satisfy.

The board concluded that Engineer A's failure was not a judgment error in a genuinely ambiguous situation but a misreading of the Code's architecture - by ignoring the exception clause in II.1.c and treating confidentiality as absolute, Engineer A inverted the Code's own priority ordering, which places public safety unambiguously above client confidentiality when danger to occupants is known and concrete.

The board concluded that while the voluntary-disclosure origin of the information is a genuine complication that modulates the confidentiality weight on one side of the balance, it does not alter the outcome because I.1's triggering condition is framed in terms of the engineer's knowledge of danger - not the source of that knowledge - meaning Engineer A's reporting obligation was fully activated the moment he possessed the information, regardless of how it came to him.

The board concluded that Engineer A's domain incompetence in electrical and mechanical systems is irrelevant to his reporting obligation because his own acknowledgment that the deficiencies could cause injury to occupants constituted the precise threshold event - and allowing disciplinary boundaries to suppress that safety-critical information would perversely convert scope-of-work limitations into ethical shields, which the Code's paramount safety obligation under I.1 does not permit.

The board concluded that Engineer A committed an independent ethical failure through passive acquiescence because neither the verbal warning nor the confidential report notation satisfied the procedural requirement of formal documented objection established in BER Case 84-5, and even if they had, the substantive dimension of the non-acquiescence duty still required escalation to public authorities since the hazard remained active and the confidential report ensured the information would never reach those who needed it - creating only a superficial appearance of disclosure.

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?

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?

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?

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?

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?