Step 4: Review

Engineers shall 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 approve only those engineering documents that are in conformity with applicable standards.

Engineers shall advise their clients or employers when they believe a project will not be successful.

Engineers are encouraged to adhere to the principles of sustainable development1in order to protect the environment for future generations.Footnote 1"Sustainable development" is the challenge of meeting human needs for natural resources, industrial products, energy, food, transportation, shelter, and effective waste management while conserving and protecting environmental quality and the natural resource base essential for future development.

The Board cited this case to establish the appropriate course of action when an engineer discovers a client has violated environmental laws, including the obligation to notify authorities if the client fails to remedy the violation.

The Board cited this case to reinforce that engineers have an obligation to be objective and truthful in professional reports and must include all relevant information, even when it may be unfavorable to the client's development interests.

Engineer A should continue to pursue discussions with Client A to convince Client A of the danger in which future residents, as well as the general public, could be placed, and the potential for significant property and environmental damage.

If Client A refuses to agree with Engineer A's design standard, Engineer A should withdraw from the project.

Beyond the Board's recommendation that Engineer A continue to pursue discussions with Client A, Engineer A bears an affirmative obligation to document in writing the 100-year storm surge recommendation, the technical basis for that recommendation including the newly released algorithm and historic weather data, and Client A's explicit refusal on cost grounds. This written record serves two distinct functions: first, it fulfills Engineer A's faithful agent duty by formally notifying Client A that the project as currently scoped carries foreseeable risk to future residents and the general public; and second, it creates a contemporaneous professional record that may be essential if Engineer A is later called upon to demonstrate that the safety-critical recommendation was made and rejected. The absence of a local building code in the jurisdiction makes this documentation obligation more urgent, not less, because there is no regulatory paper trail that would otherwise capture the identified deficiency. Engineer A should provide this written notification to Client A before withdrawing from the project, and should retain copies as part of the professional record.

The Board's recommendation that Engineer A pursue persistent discussions with Client A before withdrawing does not require Engineer A to engage in indefinite or open-ended negotiation. The proportional escalation obligation is bounded by the point at which continued engagement becomes functional acquiescence to a design standard that Engineer A has already determined endangers life and property. Once Client A has explicitly and unambiguously refused the 100-year storm surge elevation standard on cost grounds, and once Engineer A has made a good-faith written effort to explain the public safety consequences of that refusal, the escalation obligation is satisfied. Continued discussion beyond that point risks creating the appearance that the safety standard is negotiable, which would itself undermine Engineer A's professional integrity and the clarity of the public safety message. The Board's two-step framework - persuade, then withdraw - should therefore be understood as a sequential and time-bounded process, not a license for indefinite deferral of withdrawal.

The Board's conclusion that Engineer A should withdraw if Client A refuses to accept the 100-year storm surge standard does not exhaust Engineer A's ethical obligations. Withdrawal removes Engineer A from complicity in an unsafe design but does not eliminate the foreseeable risk to future residents and the general public, who remain exposed to storm surge danger regardless of which engineer ultimately executes the project. In a jurisdiction with no building code, there is no regulatory mechanism that will independently capture or correct the identified deficiency after Engineer A's departure. Accordingly, Engineer A's post-withdrawal obligations extend to notifying appropriate local government officials or public authorities of the identified storm surge risk and the absence of any regulatory standard adequate to address it. This obligation is grounded in the public welfare paramount principle and is reinforced by the building code advocacy engineer principle, which encourages engineers to engage with public authorities to establish protective standards. Engineer A's duty to the public does not terminate at the boundary of the client relationship, and the residual risk to future residents constitutes a continuing professional responsibility that survives withdrawal from the project.

The absence of a local building code in the project jurisdiction does not merely create a regulatory gap - it affirmatively expands Engineer A's independent professional duty to self-impose a technically defensible safety standard. Where a building code exists, an engineer's minimum obligation is compliance with that code, even if the engineer believes a higher standard is warranted. Where no code exists, the engineer's professional judgment is the only operative safety standard, and that judgment must be exercised with full application of available technical knowledge, including newly released algorithms and historic weather data. Client A's cost objection cannot function as a substitute for the absent regulatory floor. The Board's framework implicitly recognizes this dynamic by treating Engineer A's 100-year storm surge recommendation not as a discretionary preference but as a professional obligation grounded in public safety. This obligation persists regardless of cost constraints and is not diminished by the fact that a lower standard might have been acceptable in a jurisdiction with a more permissive building code.

From a consequentialist perspective, the Board's recommendation that Engineer A withdraw if Client A refuses the 100-year storm surge standard requires supplementary analysis to avoid a potentially counterproductive outcome. If Engineer A withdraws and a replacement engineer with fewer safety commitments accepts the engagement and designs to a lower storm surge elevation, the net effect on future residents may be worse than if Engineer A had remained engaged and continued to advocate for the higher standard from within the project. This replacement engineer risk does not, however, override the deontological obligation to withdraw - Engineer A cannot ethically lend professional credentials to a design that Engineer A has determined endangers life and property. But it does reinforce the importance of the post-withdrawal obligations identified above: Engineer A's notification to public authorities and advocacy for a protective building code are not merely optional extensions of professional responsibility but are the consequentialist mechanism by which withdrawal produces better rather than worse outcomes for the public. Withdrawal without post-withdrawal public disclosure may protect Engineer A's professional integrity while leaving the underlying public safety risk entirely unaddressed.

The Board's conclusions do not address the epistemic dimension of Engineer A's recommendation, specifically the tension between the professional obligation to render a definitive and defensible safety standard and the inherent uncertainty in climate projections derived from newly released algorithms and recently identified historic weather data. Engineer A's reliance on newly released tools is itself an expression of the professional competence obligation - engineers must apply the best available technical knowledge, not merely established consensus methods. However, professional integrity also requires that Engineer A qualify the recommendation appropriately: the 100-year storm surge standard should be presented as the technically defensible minimum given current best-available data, with explicit acknowledgment that evolving climate baselines may require future reassessment. This qualification does not weaken the recommendation or provide Client A with grounds to reject it on grounds of uncertainty; rather, it demonstrates the epistemic honesty that distinguishes a professionally credible safety recommendation from an overconfident assertion. The qualification also reinforces the case for building to the higher standard, since uncertainty in climate projections generally argues for greater rather than lesser conservatism in safety-critical infrastructure design.

In response to Q101: Engineer A bears an affirmative obligation to notify local government officials or other relevant public authorities about the identified storm surge risk even after withdrawing from the project. The absence of a building code in the jurisdiction does not eliminate the foreseeable danger to future residents; it amplifies it. Code provision II.1.a makes clear that when an engineer's judgment is overruled under circumstances that endanger life or property, the engineer shall notify the proper authority. Withdrawal alone satisfies the negative duty not to participate in an unsafe design, but it does not discharge the positive duty to protect public welfare. Because no regulatory floor exists in this jurisdiction, Engineer A's notification to local government officials is the only remaining mechanism by which the identified risk can be surfaced to a body capable of acting on it. Silence after withdrawal, in a no-code jurisdiction where the developer may simply retain a less scrupulous engineer, leaves the public safety risk entirely unaddressed and is ethically insufficient.

In response to Q102: Engineer A is obligated to document in writing the 100-year storm surge recommendation and Client A's explicit refusal. This obligation flows from multiple converging sources. First, code provision II.1.a requires that when an engineer's judgment is overruled under circumstances endangering life or property, the engineer shall notify the proper authority - a notification that is only credible and actionable if supported by a written record. Second, code provision III.1.b requires Engineer A to advise the client when a project will not be successful, and written documentation of that advice protects the integrity of that communication. Third, the Written Documentation Requirement for Safety Notification principle establishes that oral advocacy alone is insufficient when safety-critical recommendations are rejected. The documentation must be retained by Engineer A as a professional record, provided to Client A as formal notice of the safety concern and its rejection, and made available to any public authority to whom Engineer A subsequently discloses the risk. It should not be treated merely as a liability shield for Engineer A's professional standing; its primary ethical function is to create a durable, verifiable record of the safety risk that can inform regulatory or legal action.

In response to Q103: The absence of a local building code materially expands Engineer A's independent professional duty to self-impose a safety standard. Where a regulatory floor exists, an engineer can at minimum point to codified requirements as a baseline, even if personally recommending a higher standard. In a no-code jurisdiction, the engineer's professional judgment is the only operative safety standard in the design process. This places the full weight of public safety determination on Engineer A's expertise, making the self-imposed standard not merely aspirational but ethically mandatory. Client A's cost objections do not diminish this duty; the Public Welfare Paramount principle and the constraint that public safety is not subordinate to client cost preference together establish that economic considerations cannot override a safety-critical technical determination. Furthermore, this duty persists regardless of cost objections because the harm at stake - storm surge danger to future residents and the general public - is foreseeable, serious, and irreversible in the event of a major storm event. The no-code context therefore heightens rather than relaxes Engineer A's obligation to hold the 100-year storm surge standard as a non-negotiable professional floor.

In response to Q104: Engineer A does bear residual ethical responsibility for harm to future residents if Engineer A withdraws from the project but takes no further action to alert public authorities or advocate for protective building codes. Withdrawal is a necessary but not sufficient ethical response once Client A refuses the safety-critical recommendation. The Board's conclusion that Engineer A should withdraw if Client A refuses is correct as far as it goes, but it does not exhaust Engineer A's obligations. Code provision II.1.a explicitly contemplates post-overruling notification to proper authorities, and the Building Code Advocacy Engineer Principle and Post-Client-Refusal Escalation Assessment Obligation together establish that Engineer A's professional duty extends beyond the client relationship into the broader public sphere. In a no-code jurisdiction, where no regulatory body will independently discover the risk, Engineer A's silence after withdrawal is functionally equivalent to acquiescence in the unsafe outcome. The residual responsibility is not unlimited - Engineer A cannot compel the developer or the jurisdiction to act - but it does require Engineer A to take affirmative steps to surface the risk to those with authority to address it.

In response to Q201: The Faithful Agent Notification Obligation and the Public Welfare Paramount principle do not fundamentally conflict in this case - they operate in sequence rather than in opposition, but Public Welfare Paramount takes lexical priority when they diverge. Engineer A's duty as a faithful agent requires notifying Client A of the storm surge risk and the likelihood that a lower design standard will expose the project and its future residents to foreseeable danger. This notification duty is fully compatible with public welfare protection so long as Client A accepts the recommendation. The conflict arises only when Client A refuses: at that point, continuing to serve the client's cost preference would require Engineer A to subordinate public safety to client interest, which the NSPE Code does not permit. Code provision II.1. establishes that public safety is paramount, and the Client Loyalty Obligation of Engineer A is explicitly bounded by public safety. The faithful agent role therefore terminates at the boundary of ethical permissibility - Engineer A cannot be a faithful agent to a client directive that endangers the public.

In response to Q202: The Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle are in genuine tension, but that tension does not license indefinite hedging. Engineer A is correct to acknowledge that climate projections carry inherent uncertainty and that the baseline for storm surge risk may shift over time. However, professional competence requires that Engineer A render a definitive and defensible recommendation based on the best available data at the time of the assessment - in this case, the newly released algorithm and historic weather data. Epistemic humility does not mean refusing to commit to a standard; it means selecting the most protective standard that the current evidence supports and disclosing the uncertainty range transparently. The 100-year storm surge elevation standard represents Engineer A's best professional judgment given available tools, and that judgment must be stated clearly enough to be actionable. Qualifying the recommendation to the point of ambiguity would undermine its protective function and would itself constitute a failure of professional competence. Engineer A should state the recommendation definitively while noting that the standard may need to be revisited as climate data evolves.

In response to Q203: The Proportional Escalation Obligation and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle are in tension, but the resolution depends on the nature and clarity of Client A's refusal. Proportional escalation - attempting to persuade, documenting the disagreement, and escalating through available channels before withdrawing - is the appropriate framework when a client's position is ambiguous, negotiable, or based on incomplete information. However, when Client A has made an explicit, cost-driven refusal of a safety-critical standard, continued engagement that delays withdrawal risks becoming a form of tacit acquiescence. The Board's recommendation that Engineer A continue to pursue discussions is appropriate only if those discussions are genuinely aimed at changing Client A's position, not at finding a compromise that falls below the safety threshold. If Client A's refusal is unequivocal and no further persuasion is plausible, the Non-Acquiescence principle demands that Engineer A not continue to participate in a design process that will produce an unsafe outcome. The escalation obligation does not require Engineer A to exhaust every conceivable avenue before withdrawing; it requires that withdrawal be preceded by a good-faith effort to resolve the disagreement through professional persuasion.

In response to Q204: The Building Code Advocacy Engineer Principle and the Regulatory Gap Awareness and Proactive Risk Disclosure principle are not fundamentally in conflict regarding timing, but they operate on different tracks. Proactive risk disclosure to public authorities is triggered by the identification of a foreseeable public safety risk that cannot be adequately addressed through the client relationship - a trigger that may be reached before withdrawal if Client A's refusal is clear and the risk is serious. Building code advocacy, by contrast, is a longer-horizon obligation that involves engaging local government to establish systemic protective standards and is appropriately pursued both during and after the client engagement. The disclosure duty is narrower and more urgent: it requires Engineer A to surface the specific identified risk to authorities capable of acting on it. The advocacy duty is broader and more structural: it requires Engineer A to work toward closing the regulatory gap that allowed the risk to go unaddressed in the first place. These duties are complementary rather than conflicting, and both are activated by the combination of a no-code jurisdiction, a foreseeable public safety risk, and a client's refusal to adopt the recommended protective standard.

In response to Q301: From a deontological perspective, Engineer A's duty to hold public safety paramount does create a near-absolute obligation to withdraw once Client A explicitly refuses the 100-year storm surge elevation standard, but the deontological analysis does not end there. Withdrawal is obligatory because continuing to participate in the design of a structure that Engineer A knows to be unsafe would make Engineer A complicit in a foreseeable harm to future residents - a violation of the categorical duty not to use persons merely as means. However, the deontological framework also imposes a positive duty of beneficence toward those future residents, which withdrawal alone does not satisfy. The duty to withdraw is therefore necessary but not sufficient: it must be accompanied by the affirmative duty to notify proper authorities, as specified in code provision II.1.a. The fact that withdrawal may not actually prevent harm - because another engineer may replace Engineer A - does not diminish the deontological obligation to withdraw; acting from duty is not contingent on producing the desired outcome. But it does reinforce the importance of the notification duty as the mechanism through which Engineer A's moral agency extends beyond the client relationship.

In response to Q302: From a consequentialist perspective, the question of whether withdrawal produces better outcomes than remaining engaged is genuinely difficult, but the analysis ultimately supports withdrawal as the ethically superior choice under the specific conditions of this case. The argument for remaining engaged - that Engineer A might influence the design from within - is plausible only if Client A's refusal is soft and subject to ongoing persuasion. If Client A's refusal is firm, remaining engaged produces no safety benefit and instead lends Engineer A's professional credibility to an unsafe design. The replacement engineer scenario - where a less scrupulous engineer simply adopts the lower standard - is a real consequentialist concern, but it does not justify Engineer A's continued participation in an unsafe project. The better consequentialist response to the replacement risk is not to remain on the project but to pursue the post-withdrawal notification and advocacy obligations that can alert public authorities to the risk regardless of who ultimately designs the structure. Withdrawal combined with proactive disclosure to local government officials produces better expected outcomes than continued engagement without client agreement on the safety standard.

In response to Q303: From a virtue ethics perspective, Engineer A demonstrates genuine professional integrity by applying the newly released algorithm and historic weather data to recommend the 100-year storm surge standard, but epistemic humility requires that the recommendation be accompanied by a transparent disclosure of the uncertainty inherent in climate projections - not as a qualification that weakens the recommendation, but as a demonstration of intellectual honesty that strengthens it. A virtuous engineer does not suppress uncertainty to make a recommendation appear more authoritative than the evidence warrants; nor does the virtuous engineer use uncertainty as a reason to avoid making a definitive professional judgment. The virtue of practical wisdom - phronesis - requires Engineer A to calibrate the recommendation to the best available evidence, state it clearly and confidently, and acknowledge the evolving nature of the climate baseline in a way that informs rather than undermines the client's decision-making. Recommending the 100-year standard on the basis of the best current tools, while noting that the standard may need to be revisited as data improves, reflects the kind of honest, competent, and courageous professional conduct that virtue ethics demands.

In response to Q304: From a deontological perspective, Engineer A's duty as a faithful agent to Client A and the duty to hold public safety paramount do conflict when Client A's cost-driven refusal creates foreseeable risk to future residents, and public safety takes unambiguous lexical priority. The faithful agent duty - including the obligation under code provision III.1.b to notify the client when a project will not be successful - is a genuine professional obligation, but it is explicitly bounded by the public safety paramount principle established in code provision II.1. The NSPE Code does not treat these duties as equally weighted and subject to balancing; it establishes a clear hierarchy in which public safety is paramount. This means that when the two duties conflict, Engineer A cannot satisfy the faithful agent obligation by continuing to serve Client A's cost preference at the expense of public safety. The faithful agent duty is fully discharged when Engineer A provides Client A with a clear, written notification of the safety risk and the consequences of refusing the recommended standard - after which the public safety duty takes over and requires Engineer A to withdraw and notify appropriate authorities.

In response to Q401: If the jurisdiction had an existing building code mandating a lower storm surge elevation standard, Engineer A would still be ethically obligated to recommend the 100-year projection if professional judgment - supported by the best available data - indicated that the code-mandated standard was technically insufficient to protect public safety. Code provision II.1.b requires engineers to approve only those engineering documents in conformity with applicable standards, but it does not limit Engineer A's professional duty to recommend a higher standard when the applicable code is inadequate. Legal compliance provides a legal safe harbor but not an ethical one: an engineer who knows that a code-compliant design will expose future residents to foreseeable danger cannot discharge the public safety obligation merely by pointing to the code. However, the ethical calculus for withdrawal would change in a coded jurisdiction: Engineer A could not refuse to certify a code-compliant design on safety grounds alone without a stronger evidentiary basis that the code itself was deficient, and the appropriate response might shift toward formal advocacy for code revision rather than project withdrawal. The no-code jurisdiction in the present case removes this complication and places the full weight of the safety determination on Engineer A's professional judgment.

In response to Q402: Proactive contact with local government officials before presenting findings to Client A would likely have produced better outcomes for future residents than treating advocacy as a post-withdrawal obligation. If Engineer A had engaged local government at the outset - alerting officials to the identified storm surge risk and the absence of a protective building code - the jurisdiction might have initiated a code development process that would have established a regulatory floor independent of Client A's cost preferences. This would have changed the negotiating dynamic: Client A would have faced not only Engineer A's professional recommendation but also the prospect of an emerging regulatory requirement. However, this sequencing raises its own ethical complexity: Engineer A's primary engagement is with Client A, and disclosing project-specific findings to public authorities before informing the client could be seen as a breach of the faithful agent obligation. The more defensible approach is for Engineer A to raise the regulatory gap issue with local government in general terms - advocating for a building code that addresses storm surge risk in the jurisdiction - without disclosing Client A's project-specific information before the client relationship has broken down. Post-withdrawal, the disclosure obligation becomes more direct and project-specific.

In response to Q403: Written documentation of the safety recommendation and Client A's refusal, provided at the outset of the disagreement rather than only during ongoing discussions, would likely have served a dual function: it would have created a formal record that could influence Client A's decision-making by making the professional stakes of the refusal explicit, and it would have protected Engineer A's professional standing. However, the evidence suggests that Client A's refusal is cost-driven and firm, which means the written record's primary practical effect would be protective of Engineer A rather than persuasive to Client A. This does not diminish the obligation to document: the Written Documentation Requirement for Safety Notification principle establishes that documentation is required regardless of its persuasive effect, because its function extends beyond the client relationship to the broader public safety record. The written record is the instrument through which Engineer A's professional judgment becomes available to public authorities, future investigators, and regulatory bodies. Its value is not exhausted by its effect on Client A's decision, and the underlying public safety risk remains unresolved regardless of whether Client A is persuaded - which is precisely why the post-withdrawal notification obligation to public authorities is independently required.

In response to Q404: The availability of the newly released algorithm and historic weather data does create a heightened professional duty that did not previously exist to the same degree, and the ethical obligation to recommend the 100-year storm surge standard is correspondingly stronger than it would have been under previously established climate models alone. Professional competence requires engineers to apply the best available tools and data to their assessments; when superior technical tools become available, the standard of care rises accordingly. If Engineer A had relied only on older climate models that did not support the 100-year projection, the obligation to recommend that specific standard would have been weaker - though the obligation to recommend the most protective standard supported by available evidence would have remained. The newly released algorithm does not create the ethical obligation from scratch; it provides the technical basis for a more specific and more demanding recommendation. This also means that Engineer A's obligation to stay current with technical literature and newly released tools is itself an ethical obligation, not merely a professional development aspiration: failing to apply available superior tools when assessing a safety-critical design would itself constitute a failure of professional competence under the circumstances of this case.

The tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle was resolved in this case through a clear lexical ordering: Engineer A's duty to serve Client A's interests is bounded by, and ultimately subordinate to, the obligation to hold public safety paramount. The Board's conclusions confirm that Engineer A must first attempt persuasion - satisfying the faithful agent duty by fully informing Client A of the risk and its consequences - but when Client A's cost-driven refusal persists, the public welfare obligation overrides client loyalty and compels withdrawal. This resolution teaches that client service is not an independent ethical value in engineering; it is a conditional obligation that operates only within the space permitted by public safety. The moment client direction would require Engineer A to acquiesce to a design standard that exposes future residents to foreseeable storm surge danger, the faithful agent role collapses into the public welfare role, and the latter governs. Notably, the absence of a local building code does not relax this hierarchy - it intensifies it, because Engineer A's independent professional judgment becomes the only operative safety standard in the jurisdiction.

The tension between the Proportional Escalation Obligation - which calls for graduated steps before withdrawal - and the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle was resolved in this case by treating them as sequentially compatible rather than genuinely conflicting. The Board's recommendation that Engineer A continue to pursue discussions before withdrawing reflects the proportional escalation logic: withdrawal is the terminal step in a graduated response, not the first. However, this sequential compatibility has a critical limit. Once Client A has explicitly and finally refused the 100-year storm surge standard on cost grounds, continued discussion that merely delays withdrawal without any realistic prospect of changing the client's position would itself become ethically problematic - it would allow Engineer A to remain nominally engaged with a project whose safety standard Engineer A has already determined to be inadequate. The non-acquiescence principle therefore functions as a ceiling on how long proportional escalation may continue: Engineer A may pursue persuasion, but may not use the escalation framework as a pretext for indefinite engagement with a project that endangers the public. This case teaches that proportional escalation is a procedural obligation, not a substantive one - it governs the sequence of Engineer A's response but does not alter the ultimate outcome once client refusal is confirmed.

The interaction between the Climate Change as Moving Target principle and the Professional Competence in Risk Assessment principle reveals an important synthesis: epistemic uncertainty about future climate baselines does not diminish Engineer A's obligation to render a definitive and defensible safety recommendation - it actually strengthens the case for adopting the more protective standard. When the technical baseline is inherently uncertain and evolving, a competent professional does not hedge toward the lower bound of risk; rather, professional competence in a no-code jurisdiction requires Engineer A to apply the best available tools - here, the newly released algorithm and historic weather data - and recommend the standard that accounts for the upper plausible range of foreseeable harm. The availability of superior technical tools creates a heightened professional duty, because Engineer A can no longer claim ignorance of the more protective standard. At the same time, the moving-target nature of climate data requires Engineer A to qualify the recommendation transparently - not to weaken it, but to explain its basis and acknowledge that future data may require design revision. This synthesis teaches that professional competence and epistemic humility are not in conflict: a competent engineer discloses uncertainty while still committing to the most defensible protective standard available at the time of the assessment. The Building Code Advocacy Engineer Principle further extends this synthesis: because the climate baseline will continue to evolve, Engineer A's obligation to advocate for a local building code incorporating the 100-year standard is not merely a post-withdrawal courtesy but a forward-looking professional responsibility to ensure that the jurisdiction's regulatory framework keeps pace with improving climate science.

What are Engineer A’s obligations under the circumstances?

Does Engineer A have an obligation to notify local government officials or other public authorities about the identified storm surge risk even after withdrawing from the project, given that no building code exists in the jurisdiction and future residents remain exposed to foreseeable danger?

Is Engineer A obligated to document in writing the 100-year storm surge recommendation and Client A's refusal, and if so, to whom must that documentation be provided and retained?

To what extent does the absence of a local building code expand Engineer A's independent professional duty to self-impose a safety standard, and does that duty persist regardless of client cost objections?

Does Engineer A bear any residual ethical responsibility for harm to future residents if Engineer A withdraws from the project but takes no further action to alert public authorities or advocate for protective building codes in the jurisdiction?

Does the Faithful Agent Notification Obligation - which requires Engineer A to serve Client A's interests and notify the client of project risks - conflict with the Public Welfare Paramount principle when serving the client's cost preference would expose future residents to foreseeable storm surge danger?

Does the Climate Change as Moving Target principle - which acknowledges inherent uncertainty in projecting future storm surge baselines - conflict with the Professional Competence in Risk Assessment principle, which demands that Engineer A render a definitive and defensible safety recommendation rather than hedging on the basis of evolving data?

Does the Proportional Escalation Obligation - which calls for graduated steps before withdrawal - conflict with the Non-Acquiescence to Client Directive Suppressing Safety Analysis principle, which may demand immediate refusal to proceed once Client A explicitly rejects the safety-critical 100-year storm surge standard?

Does the Building Code Advocacy Engineer Principle - which encourages Engineer A to engage local government to establish protective standards - conflict with the Regulatory Gap Awareness and Proactive Risk Disclosure principle in terms of timing and scope, specifically whether Engineer A's disclosure duty to public authorities is triggered before or only after withdrawal from the project?

From a deontological perspective, does Engineer A's duty to hold public safety paramount create an absolute obligation to withdraw from the project once Client A refuses the 100-year storm surge elevation standard, regardless of whether withdrawal actually prevents harm to future residents?

From a consequentialist perspective, does Engineer A's withdrawal from the project after Client A's refusal actually produce better outcomes for future residents and the public than remaining engaged and attempting to influence the project design from within, given that another engineer with fewer safety scruples might simply replace Engineer A?

From a virtue ethics perspective, does Engineer A demonstrate genuine professional integrity by relying on newly released climate data and a recently developed algorithm to recommend the 100-year storm surge standard, or does epistemic humility require Engineer A to qualify that recommendation more explicitly given the inherent uncertainty in climate projections?

From a deontological perspective, does Engineer A's duty as a faithful agent to Client A - which includes notifying the client when a project is unlikely to succeed - conflict with the duty to hold public safety paramount, and if so, which duty takes lexical priority when Client A's cost-driven refusal creates foreseeable risk to future residents?

If the geographic area had an existing building code that mandated only a lower storm surge elevation standard, would Engineer A still be obligated to recommend the 100-year projection, and would the ethical calculus for withdrawal change given that compliance with the code would provide a legal safe harbor even if Engineer A believed it was technically insufficient?

Would the outcome for future residents have been materially different if Engineer A had proactively contacted local government officials to advocate for a building code incorporating the 100-year storm surge standard before presenting findings to Client A, rather than treating that advocacy as a post-withdrawal obligation?

If Engineer A had provided written documentation of the safety recommendation and Client A's refusal at the outset of the disagreement rather than only during ongoing discussions, would that written record have changed Client A's willingness to accept the 100-year storm surge standard, or would it have served primarily to protect Engineer A's professional standing while leaving the underlying public safety risk unresolved?

If the newly released algorithm and historic weather data had not been available and Engineer A had relied only on previously established climate models, would the ethical obligation to recommend the 100-year storm surge standard have been weaker, and does the availability of superior technical tools create a heightened professional duty that did not previously exist?

Accepting the engagement initiates Engineer A's professional duty to apply current competence and proactively disclose climate-informed coastal risks in a jurisdiction lacking building codes, constrained by the requirement to maintain algorithm currency and self-impose appropriate safety standards where no regulatory floor exists.

Applying the newly released algorithm and data directly fulfills Engineer A's competence obligation to use current technical tools and reflects the principle that climate change creates a moving target requiring updated design baselines, constrained by the need to qualify findings appropriately given the preliminary nature of newly released data.

Determining the 100-year surge standard is the core technical-ethical act that fulfills Engineer A's obligation to recommend a climate-informed safety standard in the absence of a regulatory code, constrained by the requirement that public safety primacy cannot be subordinated to client cost preferences and that the standard must reflect the moving target of climate-adjusted baselines.

Presenting findings to the client fulfills Engineer A's faithful agent notification and written documentation obligations by formally communicating the 100-year storm surge recommendation and its public safety rationale, constrained by the requirement to qualify preliminary judgments, acknowledge budget limitations, and document the communication in writing before any escalation or withdrawal is considered.

Continuing to advocate for the higher safety standard after client refusal fulfills Engineer A's non-acquiescence and post-refusal escalation obligations by pursuing graduated escalation - including potential building code advocacy with local government officials - constrained by the requirement to exhaust persuasion before withdrawal and to operate within permissible post-refusal advocacy channels rather than unilaterally overriding the client.

Withdrawal is ethically permissible only after graduated escalation and persistent persuasion have failed to move the client from a cost-driven rejection of the 100-year storm surge standard, and it fulfills the non-acquiescence obligation while simultaneously triggering the residual post-withdrawal code advocacy obligation to protect public safety.

Contacting government officials to advocate for a coastal storm surge building code directly fulfills the post-client-refusal escalation and code advocacy obligations by addressing the regulatory gap in the no-code jurisdiction, thereby protecting future residents and the public from foreseeable storm surge risk that the client refused to mitigate voluntarily.

Q1 emerges because Engineer A sits at the intersection of multiple unresolved warrant chains - client loyalty, public safety paramountcy, and regulatory gap - each triggered simultaneously by the same data set. The question is irreducibly broad because no single established norm resolves all competing obligations when a client refuses a safety recommendation in an unregulated jurisdiction.

Q2 emerges because withdrawal resolves the client-loyalty tension but leaves the public-safety warrant fully active, and the absence of a building code means no regulatory mechanism will independently capture Engineer A's risk finding after departure. The question arises precisely because the rebuttal condition for the escalation warrant - an existing regulatory backstop - is absent.

Q3 emerges because the faithful-agent documentation warrant and the public-safety disclosure warrant point to different recipients and different retention purposes, and the absence of a building code removes the standard regulatory channel that would normally resolve which documentation pathway governs. The question is forced by the gap between what the client relationship requires and what public safety may independently demand.

Q4 emerges because the code-free jurisdiction creates a normative vacuum in which the source and persistence of Engineer A's safety standard obligation are genuinely contested - the same data that triggers the public-welfare warrant also removes the external authority that would normally define its scope and limits. The question is structurally forced by the interaction between regulatory absence and client cost refusal.

Q5 emerges because the ethical architecture of engineering codes does not clearly specify whether the public-welfare obligation is discharged by withdrawal or whether it generates an independent post-withdrawal duty when the risk remains unmitigated and unregulated. The prior BER cases contextualize but do not resolve this question, because neither involved a situation where the engineer withdrew and the only remaining protective action was governmental advocacy in a code-free jurisdiction.

This question arose because the absence of a local building code removed the external regulatory backstop that would normally resolve the tension between client service and public protection, forcing Engineer A to choose between two internally valid professional obligations with no neutral arbiter. The client's explicit refusal transformed a routine cost negotiation into a direct collision between fiduciary loyalty and the paramount public safety duty, making the conflict unavoidable rather than merely theoretical.

This question arose because the very novelty of the climate algorithm that grounded Engineer A's recommendation also introduced legitimate scientific uncertainty about future baselines, creating a structural tension between intellectual honesty about data limitations and the professional obligation to provide actionable safety guidance. The client's refusal sharpened this tension by making the degree of Engineer A's epistemic hedging consequential to whether any protective standard would be adopted at all.

This question arose because the NSPE Code's graduated response framework assumes that escalation steps can meaningfully alter client behavior, but Client A's explicit cost-based refusal called that assumption into question by signaling that no amount of persuasion would change the outcome. The collision between a procedurally cautious escalation norm and an immediate non-acquiescence norm reflects genuine uncertainty about whether the ethical weight of the safety risk is sufficient to compress or eliminate the graduated response sequence.

This question arose because the no-code jurisdiction created a structural vacuum in which Engineer A's public-protective obligations had no pre-existing regulatory channel, forcing a choice between treating government engagement as a systemic, long-term advocacy role and treating it as an urgent, project-specific disclosure duty. The timing ambiguity is ethically significant because disclosure before withdrawal could protect the public sooner but might also be perceived as circumventing the client relationship, while disclosure only after withdrawal may come too late to prevent construction at the lower standard.

This question arose because the deontological framing of the public safety duty - as expressed in NSPE Code primacy language - does not explicitly condition the withdrawal obligation on its causal efficacy in preventing harm, yet the practical ethics of professional withdrawal are deeply entangled with consequentialist reasoning about whether leaving the project serves or undermines the public interest. The no-code jurisdiction amplified this tension by eliminating the regulatory backstop that would otherwise ensure minimum safety standards regardless of which engineer served the client.

This question arose because the consequentialist frame forces a comparison of real-world outcome trajectories - withdrawal versus continued engagement - rather than simply evaluating the deontological propriety of Engineer A's act, and the no-code jurisdiction state removes any regulatory backstop that might otherwise make the replacement-engineer rebuttal moot. The absence of a building code means Engineer A's withdrawal does not trigger a mandatory compliance review, so the question of whether disengagement actually protects the public becomes genuinely open.

This question arose because virtue ethics evaluates not just what Engineer A recommended but the character disposition - intellectual honesty versus overconfidence - expressed in how the recommendation was framed, and the novelty of both the data and the algorithm creates a genuine tension between the duty to apply best available science and the duty to communicate its limits faithfully. The no-code jurisdiction amplifies the question because Engineer A's recommendation carries greater practical weight when no regulatory floor exists to independently validate or constrain it.

This question arose because deontological analysis requires identifying which duty holds lexical priority when two genuine professional obligations - loyalty to client and protection of the public - point in different directions, and Client A's explicit cost-driven refusal creates the precise conflict scenario that the NSPE Code's hierarchy of duties is designed to resolve but does not resolve with complete clarity at the level of specific required actions. The absence of a building code removes the possibility of resolving the conflict by deferring to regulatory authority, forcing the lexical priority question into sharp relief.

This question arose because the no-code jurisdiction is a load-bearing factual premise of the original scenario, and testing whether the ethical analysis changes under a lower-code jurisdiction reveals whether Engineer A's obligations derive from the absence of regulation or from an independent professional duty that exists regardless of regulatory context. The legal safe harbor rebuttal condition is particularly significant because it introduces the possibility that regulatory compliance could dissolve the withdrawal trigger, fundamentally altering the ethical structure of the case.

This question arose because the Post-Client-Refusal Regional Code Advocacy Obligation state frames government advocacy as reactive, but the Regulatory Gap Awareness and Proactive Risk Disclosure principle implies a forward-looking duty that is not contingent on client behavior, creating a genuine sequencing question about when the advocacy obligation was triggered. The consequentialist framing sharpens the question by asking whether the timing difference would have produced materially different outcomes for future residents, making the abstract sequencing dispute practically significant.

This question arose because the data - Client A's refusal and the persistence of public safety risk in an unregulated jurisdiction - activates two structurally distinct warrants simultaneously: the faithful agent written notification obligation and the post-client-refusal escalation obligation. The question emerges precisely because early written documentation satisfies the first warrant but leaves the second warrant entirely unaddressed, creating genuine uncertainty about whether procedural compliance with documentation norms constitutes ethical sufficiency or merely professional self-protection.

This question arose because the data - the existence of a newly released algorithm that informed the 100-year storm surge determination - creates ambiguity about whether the ethical duty is epistemically contingent on the quality of available technical tools or categorically grounded in the public welfare paramount principle. The rebuttal condition that the climate change as moving target principle and public welfare paramountcy operate independently of any specific algorithm's availability destabilizes the claim that superior tools generate a heightened duty, leaving unresolved whether Engineer A's obligation was stronger in this case than it would have been under older models.

The board concluded that Engineer A must continue pursuing discussions with Client A because the proportional escalation framework demands good-faith persuasion before withdrawal, but this obligation is grounded in the recognition that informing the client of foreseeable danger to life, property, and the environment is itself a component of the public safety duty - not merely a courtesy to the client.

The board concluded that withdrawal is ethically mandatory if Client A refuses the 100-year standard because remaining on the project after an explicit, cost-driven rejection of a safety-critical recommendation would transform Engineer A from a professional advocate for public safety into a participant in a foreseeably dangerous design, which the paramount public welfare obligation categorically prohibits.

The board concluded that Engineer A bears an affirmative obligation to document the recommendation and Client A's refusal in writing because the absence of a building code eliminates any regulatory substitute for that record, and because the dual function of the documentation - client notification and professional accountability - makes it a necessary precondition to ethically defensible withdrawal rather than an optional protective measure.

The board concluded that the persuade-then-withdraw framework is time-bounded and sequential, not a license for indefinite deferral, because once Client A has explicitly refused and Engineer A has provided written notification of the public safety consequences, the escalation obligation is fully satisfied and further delay would itself constitute a professional integrity failure by implying the safety standard remains open to negotiation.

The board concluded that Engineer A's post-withdrawal obligations extend to notifying local government officials or public authorities of the identified storm surge risk because withdrawal removes Engineer A from complicity but does not eliminate the foreseeable danger to future residents, and in a jurisdiction with no building code, Engineer A's notification is the only available mechanism by which the identified deficiency might be captured and addressed through regulatory or governmental action.

The board concluded that the regulatory vacuum created by the absence of a building code expands rather than contracts Engineer A's independent duty, because without a code the engineer's judgment is the only operative safety standard; accordingly, Client A's cost objection carries no ethical weight as a substitute for the missing regulatory floor, and the 100-year storm surge recommendation is a professional obligation, not a preference.

The board concluded that while the deontological duty to withdraw is absolute and not overridden by the replacement engineer risk, that risk reinforces the non-optional character of post-withdrawal obligations - specifically notification to public authorities and advocacy for a protective building code - because without those steps, withdrawal protects Engineer A's integrity while leaving the public safety hazard entirely unaddressed.

The board concluded that Engineer A's reliance on newly released tools satisfies the professional competence obligation, but that epistemic honesty requires presenting the 100-year standard as the defensible minimum given current data with explicit acknowledgment that evolving baselines may require reassessment - a qualification that reinforces rather than undermines the recommendation because uncertainty in safety-critical infrastructure design argues for conservatism.

The board concluded that Engineer A bears an affirmative post-withdrawal obligation to notify local government officials because the absence of a building code means Engineer A's notification is the only remaining mechanism by which the identified storm surge risk can reach a body capable of acting on it, and silence after withdrawal in that regulatory vacuum is ethically insufficient under code provision II.1.a.

The board concluded that Engineer A is obligated to document in writing both the 100-year storm surge recommendation and Client A's explicit refusal, with that record to be retained by Engineer A, provided to Client A as formal notice, and made available to public authorities, because multiple converging code obligations - II.1.a and III.1.b - require a durable, verifiable record that can support the post-withdrawal notification and any subsequent regulatory or legal response to the identified risk.

The board concluded that the absence of a building code heightens rather than relaxes Engineer A's duty because Engineer A's professional judgment becomes the sole operative safety standard; since the Public Welfare Paramount principle renders client cost objections legally and ethically subordinate to foreseeable, irreversible public harm, the 100-year storm surge standard is a non-negotiable professional floor.

The board concluded that Engineer A bears residual ethical responsibility after withdrawal because Code provision II.1.a explicitly requires notification to proper authorities when professional judgment is overruled under dangerous circumstances, and in a jurisdiction with no regulatory backstop, Engineer A's inaction after withdrawal leaves the public with no mechanism to discover or address the risk.

The board concluded that the two principles do not fundamentally conflict because they operate in sequence: Engineer A fulfills the faithful agent duty by notifying Client A of the risk, but once Client A refuses, the faithful agent role cannot extend to executing a design that endangers the public, because Code provision II.1. establishes an absolute ceiling on client loyalty.

The board concluded that the genuine tension between climate uncertainty and the duty to render a definitive recommendation is resolved by requiring Engineer A to state the 100-year standard clearly and actionably while noting it may need revisiting as data evolves, because a recommendation qualified into ambiguity fails the professional competence standard and leaves the public unprotected.

The board concluded that proportional escalation and non-acquiescence are reconcilable because escalation is appropriate when a client's position is ambiguous or negotiable, but when Client A's refusal is explicit and cost-driven, the Non-Acquiescence principle takes precedence and Engineer A must withdraw after a good-faith but not indefinitely prolonged persuasion effort.

The board concluded that the two principles are not in conflict but operate on different temporal and functional planes: proactive disclosure to public authorities is triggered immediately upon identification of a foreseeable risk that the client refuses to address, while building code advocacy is a broader, longer-term structural obligation that runs concurrently and continues after the engagement ends. By separating urgency from scope, the board avoided a false either/or framing and affirmed that both duties are activated together by the combination of a no-code jurisdiction, a foreseeable risk, and client refusal.

The board concluded that deontological analysis imposes a two-part obligation: withdrawal is mandatory because continued participation makes Engineer A complicit in foreseeable harm to future residents, violating the categorical duty not to treat persons merely as means; but withdrawal alone is insufficient because the positive duty of beneficence toward those same residents requires Engineer A to notify proper authorities under code provision II.1.a. The board explicitly rejected the argument that the futility of withdrawal (due to replacement risk) diminishes the withdrawal obligation, while simultaneously using that futility to underscore why notification is indispensable.

The board concluded that consequentialist analysis supports withdrawal as the ethically superior choice under the specific conditions of this case - namely, a firm client refusal - because remaining engaged produces no safety benefit while actively lending professional legitimacy to an unsafe design. The board addressed the replacement engineer concern not by endorsing continued participation but by redirecting the consequentialist response toward post-withdrawal notification and advocacy, which can protect future residents regardless of who ultimately designs the structure, thereby producing better expected outcomes than either passive withdrawal or continued complicit engagement.

The board concluded that virtue ethics demands that Engineer A make a clear, confident recommendation based on the best available evidence while transparently acknowledging the inherent uncertainty in climate projections - not as a hedge that weakens the recommendation but as an act of intellectual honesty that strengthens it. The board applied the virtue of phronesis to resolve the apparent tension: a virtuous engineer neither suppresses uncertainty to appear more authoritative nor hides behind uncertainty to avoid professional commitment, but instead calibrates the recommendation to current evidence and notes that the standard may need revisiting as data evolves.

The board concluded that the faithful agent duty and the public safety paramount duty do genuinely conflict when Client A's cost preference creates foreseeable risk to future residents, but the NSPE Code resolves this conflict through an explicit hierarchy rather than a balancing test: public safety is paramount and takes unambiguous lexical priority under code provision II.1. The faithful agent obligation under III.1.b is not discarded but is fully satisfied when Engineer A provides Client A with clear written notification of the safety risk and the consequences of refusal, after which the public safety duty takes over and requires withdrawal and notification of appropriate authorities.

The board concluded that even in a coded jurisdiction mandating a lower standard, Engineer A would remain ethically obligated to recommend the 100-year projection because the public safety obligation under II.1 is not discharged by pointing to a code that Engineer A's professional judgment identifies as inadequate - though the appropriate response in that context would shift toward formal code revision advocacy rather than project withdrawal, a complication absent in the no-code jurisdiction of the present case.

The board concluded that proactive pre-withdrawal contact with local government in general terms - advocating for storm surge building codes without disclosing Client A's project specifics - would have been both ethically permissible and likely more beneficial for future residents than treating advocacy as a purely post-withdrawal obligation, because it could have created an independent regulatory requirement that changed the negotiating dynamic with Client A.

The board concluded that written documentation of the safety recommendation and Client A's refusal was required from the outset of the disagreement regardless of its persuasive effect, because the documentation's function extends beyond influencing Client A to creating a formal record available to public authorities and future investigators - and because the persistence of the unresolved public safety risk independently triggers the post-withdrawal notification obligation to those authorities.

The board concluded that the newly released algorithm and historic weather data created a heightened professional duty by providing the technical basis for a more specific and more demanding recommendation, and that Engineer A's obligation to stay current with such tools is itself an ethical requirement - meaning that reliance on inferior older models when superior tools are available would itself constitute a failure of professional competence in a safety-critical context.

The board concluded that the tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle is resolved by a strict hierarchical ordering in which client service is not an independent ethical value but a conditional one - Engineer A must first fully inform Client A of the risk (satisfying the faithful agent duty), but when that persuasion fails and the client's direction would expose future residents to foreseeable danger, the public welfare obligation governs absolutely and compels withdrawal, with the absence of a local building code intensifying this hierarchy by making Engineer A's judgment the sole operative safety standard.

The board concluded that the Proportional Escalation Obligation and the Non-Acquiescence principle do not genuinely conflict because they operate at different stages: escalation is a procedural framework requiring graduated steps before withdrawal, while non-acquiescence sets the substantive limit beyond which continued engagement becomes ethically impermissible. Once Client A's refusal is confirmed and final, the escalation framework cannot be used as a pretext for indefinite involvement in a project Engineer A has already judged to endanger the public.

The board concluded that professional competence and epistemic humility are complementary rather than conflicting obligations: a competent engineer discloses the uncertainty inherent in evolving climate data while still committing to the most defensible protective standard available at the time of assessment. The availability of the new algorithm and historic weather data created a heightened professional duty that did not previously exist, because Engineer A could no longer claim ignorance of the more protective standard, and the absence of a local building code further required Engineer A to apply that standard independently and advocate for its codification as a continuing forward-looking responsibility.

After Client A explicitly refuses to fund construction to the 100-year storm surge elevation, what sequence of professional actions must Engineer A take to satisfy the public welfare paramount obligation while respecting the proportional escalation framework?

After withdrawing from the project, does Engineer A bear an affirmative obligation to notify local government officials or public authorities of the identified storm surge risk and advocate for adoption of a protective building code, or does withdrawal alone discharge Engineer A's professional duty to the public?

In a jurisdiction with no applicable building code, does Engineer A's professional judgment - informed by newly released climate data and a recently developed storm surge modeling algorithm - establish the 100-year storm surge elevation as an ethically mandatory design standard that cannot be reduced in response to Client A's cost-driven objections, and does the availability of superior technical tools create a heightened duty that did not previously exist?

When a newly released climate algorithm supports a 100-year storm surge standard that Client A refuses on cost grounds, and no local building code exists to establish a regulatory floor, should Engineer A treat that standard as a non-negotiable professional floor and continue advocating it, or calibrate the recommendation to account for algorithmic uncertainty and client budget constraints?

Once Client A explicitly refuses the 100-year storm surge standard on cost grounds, should Engineer A continue pursuing discussions and provide formal written documentation of the recommendation and refusal before withdrawing, or does the categorical nature of Client A's refusal trigger an obligation to withdraw without further engagement that risks signaling the standard is negotiable?

After withdrawing from the project because Client A refuses the 100-year storm surge standard, does Engineer A bear an affirmative obligation to notify local government officials of the identified risk and advocate for a protective building code - obligations that survive the termination of the client relationship - or does withdrawal discharge Engineer A's professional responsibilities, leaving further action to Engineer A's discretion?

When Engineer A has identified a 100-year storm surge standard as the technically defensible safety floor using newly released tools, and Client A refuses on cost grounds in a jurisdiction with no building code, how should Engineer A respond to that refusal?

Once Client A has explicitly refused the 100-year storm surge standard on cost grounds, what combination of written documentation, continued persuasion, and withdrawal timing satisfies Engineer A's proportional escalation obligation without crossing into tacit acquiescence to an unsafe design?

After withdrawing from the project, what affirmative steps must Engineer A take to discharge the continuing public welfare obligation to future residents who remain exposed to storm surge danger in a jurisdiction with no building code?

Once Client A explicitly refuses the 100-year storm surge elevation standard on cost grounds, what is Engineer A's ethically required course of action - continue pursuing discussions with the client, withdraw from the project, or accept a modified standard that partially addresses the risk?

Should Engineer A apply the newly released climate algorithm and historic weather data to determine the 100-year storm surge standard as a definitive professional recommendation, qualify that recommendation to reflect epistemic uncertainty, or defer to previously established climate models pending broader peer validation of the new algorithm?

After withdrawing from the project, is Engineer A obligated to notify local government officials of the identified storm surge risk and advocate for a protective building code, or does withdrawal alone discharge Engineer A's professional ethical obligations?

Should Engineer A apply the newly released algorithm and historic weather data to render a definitive 100-year storm surge recommendation, and how should the epistemic uncertainty inherent in evolving climate projections be handled in that recommendation?

When Client A explicitly refuses the 100-year storm surge elevation standard on cost grounds, should Engineer A document the recommendation and refusal in writing, continue pursuing discussions to persuade Client A, or withdraw from the project - and in what sequence must these obligations be discharged?

After withdrawing from the project, does Engineer A bear an affirmative obligation to notify local government officials or public authorities of the identified storm surge risk and to advocate for a protective building code, or is withdrawal a sufficient discharge of Engineer A's professional duty to the public?