Step 4: Review

Engineers shall perform services only in the areas of their competence.

Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.

Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.

Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment.

Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project.

Cited to establish the propriety of retaining experts and specialists for projects, and that engineers have an ethical obligation to seek work only in areas where they possess educational background and experience or retain those who do.

Cited to reinforce the principle from BER Case 71-2 that engineers must only seek work in areas where they possess the necessary educational background and experience, affirming the ethical obligation regarding competence.

Cited as the primary analogous precedent where a chemical engineer accepting a county surveyor position was deemed unethical due to lack of relevant background, establishing that engineers must have substantive background and experience to accept positions requiring specialized expertise.

It would be unethical for Engineer B to perform the design of the structural footings as part of the facility.

Engineer A has an ethical responsibility to question Engineer B's competency and report his concerns to the contractor.

Beyond the Board's finding that Engineer B's acceptance of the structural footing assignment is unethical, Engineer B bore an independent and antecedent ethical obligation to conduct a candid self-assessment of his own competence before accepting the engagement - not merely to decline if challenged by a peer. The chemical engineering background that defines Engineer B's training is substantively remote from the soil mechanics, load-path analysis, and foundation design principles required for structural footing work. Because Engineer B's sole-purpose retention was specifically and exclusively for structural footing design, there was no broader project role within which a competence gap could be absorbed, delegated, or remediated through collaboration with a qualified structural engineer. The circularity is decisive: Engineer B could not ethically seal work he lacked the competence to perform, and he could not ethically oversee a qualified structural engineer performing that work without himself possessing the substantive background necessary to evaluate it. Holding a general PE license does not dissolve this constraint; the ethics code imposes a higher standard than the legal minimum of licensure, and that higher standard required Engineer B to proactively disclose his disciplinary background to the contractor and decline the assignment before any peer raised concerns.

The Board's conclusion that Engineer B's assignment is unethical carries an important but unaddressed implication for the construction contractor: the contractor's failure to verify Engineer B's disciplinary background and domain-specific qualifications before retention constitutes an independent ethical failure that neither diminishes nor displaces Engineer A's reporting obligation but does amplify the systemic risk to public safety. The contractor, operating in a design-build context, assumed a coordination and oversight role that included a duty to confirm that each retained engineer possessed qualifications aligned to the specific technical task assigned. Retaining a chemical engineer for structural footing design without investigating whether that engineer had subsequent training in foundation design represents a degree-to-task alignment verification failure. However, assigning primary responsibility for this failure to the contractor must not be permitted to dilute the engineering profession's internal self-policing norms: the contractor's negligence does not reduce Engineer A's obligation to report, nor does it excuse Engineer B's obligation to decline. Rather, the contractor's verification failure and the engineers' individual competence obligations operate in parallel, each independently required by the ethical framework governing their respective roles.

The Board's treatment of Engineer B's situation is further illuminated by the BER Case 85-3 analogy: just as the county surveyor's appointment to a public role did not expand the technical scope of that engineer's competence, Engineer B's retention by the contractor for a specific structural task did not confer structural engineering competence that Engineer B did not independently possess. The institutional or contractual framing of an assignment - whether a public appointment or a private consulting engagement - is ethically inert with respect to the competence boundary. This principle forecloses any argument that Engineer B's status as a retained PE, or the contractor's apparent confidence in retaining him, could serve as a substitute for substantive domain-specific qualification. From a deontological standpoint, Engineer B's categorical duty to practice only within competence was violated at the moment of acceptance, entirely independent of whether the resulting footing design might have proven structurally adequate. The outcome of the design is irrelevant to the ethical violation; the violation was complete upon acceptance of an assignment for which Engineer B lacked the requisite education or experience in the specific technical domain.

While the Board left unresolved whether Engineer A had an ethical responsibility to report concerns to the contractor, the analytical framework strongly supports the conclusion that Engineer A's reporting was not merely permissible but obligatory - subject to an important sequencing condition the Board did not explicitly address. The ethics code's peer competence challenge obligation activates upon reasonable doubt about a colleague's competence, and Engineer A's inability to establish any subsequent training in foundation design for a chemical engineer assigned to structural footing work constitutes a sufficient objective basis for that reasonable doubt. However, the principle of peer confrontation before authority escalation suggests that Engineer A's ethical obligation was sequenced: first, directly confront Engineer B and recommend withdrawal from the assignment; second, if Engineer B refused or the concern remained unresolved, escalate to the contractor. The fact that Engineer A reported to the contractor does not itself establish whether Engineer A first confronted Engineer B - and the Board's silence on this sequencing question leaves open whether Engineer A fully discharged the collegial dimension of the obligation or appropriately compressed the sequence given the structural safety stakes involved.

The Board's unresolved question about Engineer A's reporting obligation has a further dimension that the Board did not reach: if the contractor receives Engineer A's concerns and takes no corrective action, Engineer A's ethical obligation does not terminate at the contractor level. The structural footing context is particularly significant here because footing failures are catastrophic, irreversible, and capable of causing loss of life to building occupants who have no knowledge of and no ability to protect themselves from the competence deficiency. This asymmetry between the severity and irreversibility of potential harm and the relative ease of remediation - replacing Engineer B with a qualified structural engineer - means that the public welfare paramount principle accelerates the escalation threshold. Engineer A's obligation would progress from contractor notification to state licensing board notification if the contractor failed to act, and continued participation in the project alongside an unqualified Engineer B performing structural footing design could, under sufficiently unresponsive circumstances, constitute complicity requiring Engineer A's withdrawal from the project entirely.

In response to Q101: Engineer B bears an independent and primary ethical obligation to proactively disclose his chemical engineering background and lack of structural training to the contractor before accepting the structural footing assignment. This obligation flows directly from Section II.2.a, which requires engineers to undertake assignments only when qualified by education or experience in the specific technical field involved. The duty to disclose is not contingent on a peer raising concerns; it is self-executing and arises at the moment Engineer B evaluates whether to accept the engagement. Waiting for Engineer A or another party to surface the competence gap inverts the ethical architecture of the code, which places primary gatekeeping responsibility on the individual engineer. A fully ethical Engineer B would have declined the assignment outright or, at minimum, disclosed his background limitations to the contractor before any design work commenced, allowing the contractor to make an informed retention decision. The fact that Engineer B accepted the assignment without apparent disclosure compounds the ethical violation beyond mere incompetence into a failure of professional candor.

In response to Q102: The construction contractor bears an independent ethical and practical responsibility to verify Engineer B's qualifications before retaining him for structural footing design, as implied by the degree-to-task alignment verification obligation. However, the contractor's failure to perform adequate pre-retention screening does not diminish Engineer A's reporting obligations - it amplifies them. The contractor's negligence creates a gap in the competence gatekeeping system that Engineer A's reporting obligation is specifically designed to fill. The engineering profession's self-policing norms, reflected in Section II.2 and the broader code structure, exist precisely because clients and contractors often lack the technical sophistication to independently assess cross-discipline competence deficiencies. Assigning primary responsibility to the contractor would dangerously dilute the profession's internal accountability norms and undermine the public trust that professional licensure is meant to guarantee. The contractor's failure is a contributing factor to the ethical problem, but it does not transfer or reduce Engineer A's independent duty to act upon reasonable knowledge of a competence violation that threatens public safety.

In response to Q103: If Engineer A reports concerns to the contractor and the contractor takes no corrective action, Engineer A's ethical obligation escalates progressively and does not terminate at the contractor notification step. The structural safety risk inherent in footing design - where failure can cause catastrophic, irreversible harm to building occupants - materially accelerates the escalation threshold. Under the public welfare paramount principle and the engineer's duty to hold public safety above client interests, Engineer A's next obligation would be to directly confront Engineer B and recommend withdrawal. If Engineer B also refuses to withdraw and the contractor continues to permit the incompetent design work, Engineer A's obligation escalates further to notification of the state licensing board or other relevant public authorities. The severity and irreversibility of potential structural footing failure means that the threshold for escalation beyond the contractor is lower in this context than it would be for a less safety-critical assignment. Continued silence after contractor inaction would risk making Engineer A complicit in a foreseeable public safety harm, which the code does not permit. At that stage, project withdrawal by Engineer A may also become ethically necessary.

In response to Q104: Engineer B could theoretically cure the competence deficiency by engaging a qualified structural engineer to perform the actual footing design under proper supervision, as contemplated by Section II.2.c, which permits accepting coordination responsibility for an entire project while retaining specialists for components outside one's competence. However, the sole-purpose nature of Engineer B's engagement with the contractor makes this remedy structurally circular and ethically unavailable. Engineer B was retained specifically and exclusively to design the structural footings - that task is not a subsidiary component of a broader coordination role but the entirety of his engagement. If Engineer B sub-delegated the actual design to a qualified structural engineer, he would be providing no independent value to the engagement while retaining the ethical and legal responsibility of sealing work he cannot competently review. Furthermore, Engineer B's inability to competently oversee, evaluate, or seal the delegated structural work means the sub-delegation would not satisfy Section II.2.b's prohibition on affixing signatures to plans dealing with subject matter in which the engineer is not competent. The II.2.c remedy is designed for prime professionals with genuine coordination competence, not as a mechanism for incompetent engineers to launder out-of-discipline assignments through nominal delegation.

In response to Q201: The principle requiring Engineer A to confront Engineer B directly before escalating to the contractor or authorities does create a sequencing tension with the public welfare paramount principle, but this tension is resolvable rather than irreconcilable. The graduated escalation sequence - direct confrontation of Engineer B, then contractor notification, then authority escalation - is not merely a procedural courtesy; it reflects the profession's commitment to collegial self-regulation and gives Engineer B the opportunity to self-correct before external intervention. However, the structural footing context materially compresses the acceptable timeline for each escalation step. Because structural footing failures can cause catastrophic and irreversible harm, Engineer A cannot afford extended deliberation at any stage. The public welfare paramount principle does not eliminate the direct confrontation step but it does mean that Engineer A's tolerance for delay or non-response at each stage must be significantly shorter than it would be for a less safety-critical assignment. If direct confrontation of Engineer B produces no corrective action within a reasonable and compressed timeframe, the public welfare obligation overrides any residual collegial deference and compels immediate escalation.

In response to Q202: The tension between incomplete situational knowledge restraint and the peer competence challenge obligation resolves at the point where Engineer A has made a reasonable, good-faith investigation of Engineer B's credentials and background and has been unable to establish any qualifying education or experience in foundation design. The standard is not certainty of incompetence but reasonable doubt grounded in objective evidence - or the absence of evidence - following diligent inquiry. In this case, Engineer A investigated Engineer B's qualifications, found that his degree is in chemical engineering, and could not establish any subsequent training in foundation design. That combination of positive evidence of a non-structural background and absence of evidence of remedial qualification is sufficient to activate the peer competence challenge obligation. Engineer A is not required to prove Engineer B incompetent beyond doubt; the code's protective purpose for public safety means that reasonable, evidence-based doubt about competence in a safety-critical domain is sufficient to trigger the reporting obligation. Epistemic caution is appropriate before investigation but cannot serve as a perpetual shield against action once investigation has produced a reasonable basis for concern.

In response to Q203: The principle that the ethics code sets a higher standard than mere PE licensure and the principle that consulting contexts afford engineers greater competence flexibility than employment contexts do create a genuine tension, but that tension does not benefit Engineer B in this case. The consulting context flexibility principle, as illustrated in BER cases 71-2 and 78-5, applies to situations where a consulting firm or prime professional can restructure its workforce, retain specialists, or otherwise adapt its organizational capacity to address competence gaps. That flexibility is organizational and structural in nature - it permits a consulting firm to cure a competence gap through legitimate subconsultant arrangements. It does not permit an individual engineer to accept an assignment for which he personally lacks competence on the theory that consulting contexts are more permissive. Engineer B's sole-purpose engagement means there is no organizational flexibility to invoke; the consulting context flexibility principle simply has no application to his situation. Meanwhile, the ethics code higher standard principle directly forecloses any argument that Engineer B's general PE licensure authorizes structural footing design. The two principles are not in genuine conflict as applied to Engineer B - the consulting flexibility principle is inapplicable, and the higher standard principle is directly operative.

In response to Q204: The degree-to-task alignment verification obligation applicable to the contractor and the engineering self-policing obligation applicable to Engineer A and Engineer B are not fundamentally in conflict, but assigning meaningful responsibility to the contractor does carry a risk of diluting the profession's internal accountability norms if not carefully bounded. The contractor's verification duty is real but it is a secondary safeguard - it exists because contractors sometimes retain engineers without adequate credential scrutiny, and the profession's ethical framework anticipates this gap. The primary burden of competence gatekeeping remains on Engineer B himself, who must self-assess and decline out-of-competence assignments, and on Engineer A, who must challenge apparent competence violations when discovered. Treating the contractor's verification failure as a primary or co-equal responsibility risks creating a moral hazard where engineers assume that contractor screening will catch competence problems they themselves should have prevented. The correct framing is that the contractor's verification obligation and the engineers' self-policing obligations operate in parallel and are mutually reinforcing, but the engineers' obligations are primary and non-delegable, while the contractor's obligation is a secondary institutional check that does not substitute for professional self-regulation.

In response to Q301: From a deontological perspective, Engineer B violated a categorical duty to practice only within competence by accepting the structural footing assignment, regardless of whether the resulting design might have turned out to be structurally sound. The deontological analysis under Section II.2.a is outcome-independent: the duty is to undertake assignments only when qualified by education or experience in the specific technical field, and that duty is violated at the moment of acceptance, not at the moment of failure. A fortuitously adequate design produced by an incompetent engineer does not retroactively cure the ethical violation, just as a lucky outcome does not transform a reckless act into a prudent one. The categorical nature of this duty reflects the code's recognition that competence cannot be reliably assessed after the fact by non-expert clients or the public, and that the profession's trustworthiness depends on engineers self-enforcing competence boundaries unconditionally. Engineer B's chemical engineering background and absence of established foundation design training place him categorically outside the competence boundary for structural footing design, making the acceptance of the assignment an unconditional ethical violation.

In response to Q302: From a consequentialist perspective, the potential harm to public safety from an incompetently designed structural footing vastly outweighs any project efficiency or cost benefits gained by retaining Engineer B rather than a qualified structural engineer. Structural footing failures can cause building collapse, loss of life, and severe injury to occupants and workers - harms that are catastrophic in magnitude, irreversible in nature, and potentially affect many people beyond the immediate parties to the contract. The cost savings or scheduling convenience of retaining an already-engaged chemical engineer for a structural task are marginal and speculative benefits by comparison. A rigorous consequentialist calculus, properly accounting for the probability of harm, the severity and irreversibility of potential outcomes, and the breadth of persons affected, would unambiguously favor retaining a qualified structural engineer. This analysis should directly inform the contractor's retention decision: the contractor's duty to verify Engineer B's qualifications before retention is not merely a procedural nicety but a consequentially critical safeguard against a foreseeable and preventable catastrophic outcome.

In response to Q303: From a virtue ethics perspective, Engineer A demonstrated the professional virtues of courage and integrity by reporting concerns about Engineer B's competence to the contractor, particularly given the professional and social pressures that typically discourage engineers from challenging colleagues on a shared project. However, a fully virtuous engineer would also have directly confronted Engineer B before or alongside escalating to the contractor. Direct confrontation reflects the virtues of honesty, respect for professional peers, and commitment to collegial self-regulation - it gives Engineer B the opportunity to self-correct and preserves the dignity of the professional relationship. Bypassing direct confrontation in favor of immediate contractor notification, while not necessarily unethical, reflects a less complete expression of professional virtue. The virtuous sequence would be: investigate Engineer B's credentials thoroughly, confront Engineer B directly with the concern and recommend withdrawal, and then escalate to the contractor and authorities if Engineer B refuses to act. This sequence embodies both the courage to challenge a peer and the integrity to follow through with escalation when self-correction fails.

In response to Q304: From a deontological perspective, Engineer A's duty to protect public safety creates a strong but not unconditional obligation to escalate concerns beyond the contractor to the state licensing board if the contractor fails to act. The duty is strong because structural footing design implicates irreversible public safety risks that cannot be adequately addressed by private contractual arrangements alone. However, the duty remains sensitive to the severity and imminence of the risk in determining the appropriate escalation pathway and timing. Where the risk is severe and imminent - as it is in structural footing design for an industrial facility under active construction - the threshold for escalating to the licensing board is materially lower than it would be for a speculative or remote risk. The structural safety context means that Engineer A cannot indefinitely defer licensing board notification while waiting for the contractor to act. If the contractor fails to take corrective action within a reasonable and compressed timeframe, the deontological duty to protect public safety becomes an unconditional obligation to escalate to the licensing board, because at that point Engineer A possesses knowledge of an ongoing competence violation that poses a direct threat to public welfare and no private remedy has been effective.

In response to Q401: Substantial post-degree self-study and informal mentorship in foundation design, without formal credentials or documented training, would not be sufficient to satisfy the competence standard for structural footing design under the code's requirements. Section II.2.a requires qualification by education or experience in the specific technical field, and the word 'experience' in this context implies documented, verifiable, and professionally supervised practice - not self-directed study or informal mentorship that cannot be independently assessed. The structural footing context is particularly demanding because the consequences of incompetence are catastrophic and irreversible, which means the competence threshold must be reliably verifiable rather than self-reported. Engineer A and the contractor evaluating such informal experience should apply a high degree of skepticism and require objective evidence: documented project history, references from supervising engineers, and ideally formal continuing education records. Absent such documentation, informal self-study claims should not override the reasonable doubt that Engineer B's chemical engineering background and absence of formal structural training creates. The burden of demonstrating competence rests on Engineer B, and unverifiable informal experience does not discharge that burden.

In response to Q402: If Engineer B had accepted the structural footing assignment but immediately sub-delegated the actual design work to a qualified structural engineer while retaining overall coordination responsibility, that arrangement would not have resolved the ethical problem. The core issue is not merely who performs the physical design calculations but who bears the professional responsibility for reviewing, evaluating, and sealing the work. Engineer B's inability to competently oversee and seal the structural footing design means that any sub-delegation would be nominal rather than substantive - Engineer B would be affixing his seal to plans dealing with subject matter in which he is not competent, which is directly prohibited by Section II.2.b. Furthermore, the sole-purpose nature of Engineer B's engagement means that his coordination role has no independent content beyond the structural footing design itself; there is no broader project coordination function that would justify invoking the Section II.2.c exception. The sub-delegation arrangement would create a false appearance of professional oversight while providing none of its substance, which is arguably more ethically problematic than straightforward incompetent practice because it actively misleads the contractor and the public about the quality of professional review.

In response to Q403: If Engineer A had not reported concerns to the contractor and the structural footings subsequently failed causing injury, Engineer A would bear significant ethical responsibility for the harm. Engineer A possessed knowledge - grounded in objective credential investigation - that Engineer B lacked apparent competence for the structural footing assignment. The engineering profession's self-policing obligation and the public welfare paramount principle together create an affirmative duty to act upon such knowledge. Silence in the face of a known, foreseeable public safety risk is not ethically neutral; it constitutes a failure of the professional duty to protect public welfare. The fact that Engineer A did not design the footings himself does not insulate him from ethical responsibility, because his knowledge of Engineer B's apparent incompetence created an independent obligation to intervene. This analysis reinforces the Board's implicit conclusion that Engineer A's reporting to the contractor was not merely permissible but ethically required. Failure to report would have transformed Engineer A from a bystander into a passive participant in the competence violation, with corresponding ethical culpability for foreseeable harms that his intervention could have prevented.

In response to Q404: If the contractor ignored Engineer A's reported concerns and directed Engineer A to continue working on the project alongside Engineer B, Engineer A's ethical obligation would require serious consideration of withdrawal from the project, and continued participation would risk becoming complicity in the competence violation. The threshold for required withdrawal is reached when Engineer A has exhausted available internal remedies - reporting to the contractor - and the contractor has not only failed to act but has affirmatively directed continuation of the problematic arrangement. At that point, Engineer A's continued participation lends professional credibility and implicit endorsement to a project in which a known competence violation is ongoing. The project withdrawal obligation is not triggered by mere disagreement with a client decision; it is triggered when continued participation would require Engineer A to act contrary to the code's requirements or to remain silent about an ongoing public safety threat. Before withdrawing, Engineer A should also escalate to the state licensing board, because withdrawal alone does not protect the public from the ongoing risk - it only removes Engineer A from personal complicity. The combination of licensing board notification and project withdrawal represents the full discharge of Engineer A's ethical obligations when contractor-level remedies have failed.

The most fundamental tension in this case - between the principle that public welfare is paramount and the principle of incomplete situational knowledge restraint - was resolved by the Board in favor of a graduated, sequenced response rather than immediate escalation. The Board did not treat public safety as a trump card that collapses all procedural steps into an immediate duty to report to authorities. Instead, it preserved the collegial-first sequencing: Engineer A should confront Engineer B directly before escalating to the contractor or beyond. This resolution implicitly teaches that 'public welfare is paramount' functions as a ceiling constraint on inaction, not as a lever that bypasses professional process. The principle only overrides procedural sequence when the risk is imminent and the process has already failed - not at the moment reasonable doubt first arises. In the structural footing context, where failures can be catastrophic, this sequencing remains intact precisely because early-stage intervention (direct confrontation, then contractor notification) is itself a public-safety-protective act, not a delay of it.

The case reveals a decisive resolution of the tension between the ethics code as a higher standard than mere PE licensure and the principle that consulting contexts afford engineers greater competence flexibility than employment contexts. The Board's analysis makes clear that these two principles operate on different axes and do not cancel each other out: consulting flexibility is a real and recognized principle, but it applies to how competence gaps are remediated organizationally - through subconsultant retention, team structuring, or specialist delegation - not to whether a given engineer may personally seal work outside their domain. Because Engineer B was retained on a sole-purpose basis specifically to design structural footings, the consulting-context flexibility principle had no operative purchase: there was no organizational structure through which Engineer B could legitimately route the work to a qualified structural engineer while retaining meaningful oversight. The ethics code's higher standard therefore prevailed unconditionally in Engineer B's situation, and the consulting flexibility principle was effectively neutralized by the sole-purpose engagement constraint. This teaches that consulting flexibility is an organizational remedy, not a personal competence waiver.

A subtler but important principle tension exists between the degree-to-task alignment verification obligation - which implies the contractor bore a duty to screen Engineer B before retention - and the engineering self-policing obligation that places primary competence gatekeeping on engineers themselves. The Board's analysis does not explicitly resolve this tension, but its structure implicitly prioritizes the internal professional obligation: the ethical conclusions are directed at Engineer B's acceptance decision and Engineer A's reporting duty, not at the contractor's screening failure. This prioritization carries a normative lesson: assigning primary responsibility to the contractor risks diluting the profession's internal accountability norms by suggesting that engineers may accept assignments unless externally screened out. The profession's ethical framework instead demands that Engineer B self-screen before acceptance and that Engineer A police the boundary when Engineer B fails to do so. The contractor's verification duty is real but secondary - a backstop, not the primary line of defense. Allowing contractor negligence to diminish Engineer A's reporting obligation would invert this hierarchy and undermine the self-regulating character of professional engineering ethics.

Would it be ethical for Engineer B to perform the design of the structural footings as part of the facility?

Did Engineer A have an ethical responsibility to question Engineer B's competency and report his concerns to the contractor?

Does Engineer B bear an independent ethical obligation to proactively disclose his chemical engineering background and lack of structural training to the contractor before accepting the structural footing assignment, rather than waiting for a peer to raise concerns?

What ethical responsibility, if any, does the construction contractor bear for failing to verify Engineer B's qualifications before retaining him for structural footing design, and does the contractor's negligence in this regard diminish or amplify Engineer A's reporting obligations?

If Engineer A's concerns are reported to the contractor but the contractor takes no corrective action, at what point does Engineer A's ethical obligation escalate from internal reporting to notification of the state licensing board or other public authorities, and does the structural safety risk inherent in footing design accelerate that threshold?

Could Engineer B ethically cure the competence deficiency by collaborating with or directly supervising a qualified structural engineer, and if so, would that arrangement satisfy the ethical requirements of Section II.2.c, or does the sole-purpose nature of his engagement make such delegation structurally impossible?

Does the principle requiring Engineer A to confront Engineer B directly before escalating to the contractor or authorities conflict with the principle that public welfare is paramount, particularly when structural footing failures could cause catastrophic and irreversible harm to building occupants?

How should the principle of incomplete situational knowledge restraint - which cautions Engineer A against acting on unverified assumptions about Engineer B's competence - be reconciled with the peer competence challenge obligation that activates upon reasonable doubt, and where precisely does reasonable doubt become sufficient to override epistemic caution?

Does the principle that the ethics code sets a higher standard than mere PE licensure conflict with the principle that consulting contexts afford engineers greater competence flexibility than employment contexts, and if so, does that flexibility have any legitimate application to Engineer B's situation or is it entirely foreclosed by the sole-purpose nature of his engagement?

Does the degree-to-task alignment verification obligation - which implies the contractor should have screened Engineer B before retention - conflict with the engineering self-policing obligation that places the primary burden of competence gatekeeping on Engineer A and Engineer B themselves, and does assigning responsibility to the contractor risk diluting the profession's internal accountability norms?

From a deontological perspective, did Engineer B violate a categorical duty to practice only within competence by accepting the structural footing assignment, regardless of whether the resulting design might have turned out to be structurally sound?

From a consequentialist perspective, does the potential harm to public safety from an incompetently designed structural footing outweigh any project efficiency or cost benefits gained by retaining Engineer B rather than a qualified structural engineer, and how should that calculus inform the contractor's retention decision?

From a virtue ethics perspective, did Engineer A demonstrate the professional virtues of courage and integrity by reporting concerns about Engineer B's competence to the contractor, and would a fully virtuous engineer have gone further by directly confronting Engineer B before escalating to the contractor?

From a deontological perspective, does Engineer A's duty to protect public safety create an unconditional obligation to escalate concerns beyond the contractor to the state licensing board if the contractor fails to act, or does the duty remain conditional on the severity and imminence of the risk?

If Engineer B had substantial post-degree self-study and informal mentorship in foundation design but no formal credentials or documented training, would that be sufficient to satisfy the competence standard for structural footing design, and how should Engineer A or the contractor evaluate such informal experience?

If Engineer B had accepted the structural footing assignment but immediately sub-delegated the actual design work to a qualified structural engineer while retaining overall coordination responsibility, would that arrangement have resolved the ethical problem, or would Engineer B's inability to competently oversee and seal the work still constitute an ethical violation?

If Engineer A had not reported concerns to the contractor and the structural footings subsequently failed causing injury, would Engineer A bear any ethical or professional responsibility for the harm, given that Engineer A possessed knowledge of Engineer B's apparent incompetence?

If the contractor had ignored Engineer A's reported concerns and directed Engineer A to continue working on the project alongside Engineer B, would Engineer A's ethical obligation require withdrawal from the project entirely, and at what point does continued participation become complicity in the competence violation?

The contractor retains Engineer B for structural footing design without verifying domain-specific competence, violating the obligation to confirm degree-to-task alignment before specialist retention and ignoring the constraint that a general PE license does not authorize cross-discipline structural practice.

Engineer B's acceptance of the structural footing assignment violates multiple obligations because a chemical engineering background does not confer structural competence, a general PE license does not satisfy the ethics code's higher standard, and the sole-purpose nature of the engagement forecloses sub-delegation as a remediation path.

Engineer A's investigation of Engineer B's qualifications fulfills the obligation to establish an objective credential basis before initiating a peer competence challenge, and is guided by the principle that reasonable doubt about a peer's competence triggers a verification duty before escalation.

Reporting concerns to the contractor fulfills the client-escalation obligation but potentially violates the sequencing obligation requiring direct peer confrontation first, as the graduated escalation framework constrains Engineer A to attempt collegial resolution with Engineer B before involving the client.

Direct confrontation of Engineer B fulfills the sequencing obligation requiring collegial peer engagement before authority escalation, and is constrained by the requirement that Engineer A have an objective credential basis and awareness of consulting-versus-employment flexibility distinctions before recommending withdrawal.

Engineer B's withdrawal decision is the pivotal ethical moment where fulfilling the refusal obligation and competence verification obligation converges with the constraints of PE license non-authorization and sole-purpose sub-delegation infeasibility, meaning withdrawal is the only path that avoids violating the acceptance refusal obligation while satisfying the ethics code's higher standard over mere legal licensure.

Engineer A's escalation to the client and authorities fulfills the conditional escalation obligation triggered by Engineer B's refusal to withdraw, but is constrained by the graduated sequencing requirement that direct collegial confrontation must precede authority escalation, meaning this action is only ethically justified as a last resort after the prior confrontation step has failed to resolve the competence concern.

This question arose because Engineer B's chemical engineering background placed his structural footing assignment at the intersection of two contested warrants: the legal sufficiency of a PE license versus the ethics code's higher domain-specific competence standard. The sole-purpose engagement structure eliminated the consulting-context remediation flexibility that might otherwise have resolved the tension, forcing a direct confrontation between licensure adequacy and ethical competence obligation.

This question arose because Engineer A's position as a co-project engineer - rather than a supervisor or client - placed him in a role where two sequencing warrants competed: the collegial confrontation-first norm protecting professional relationships and the self-policing reporting obligation protecting public welfare. The structural footing context amplified the tension because the safety stakes potentially accelerated the point at which collegial deference must yield to authority notification.

This question arose because the standard BER analysis focused on whether Engineer B should accept the assignment, leaving unresolved whether the ethics code imposes a temporally prior, independent obligation to disclose before acceptance rather than merely to decline. The sole-purpose engagement structure and the absence of any contractor verification mechanism made Engineer B's pre-acceptance silence the only point at which the competence gap could have been surfaced, generating a novel question about the proactive versus reactive character of the disclosure duty.

This question arose because the standard BER analysis treated the contractor as a passive recipient of Engineer A's report rather than as an independent duty-bearer, leaving unresolved how the contractor's own verification failure interacts with Engineer A's reporting obligation. The design-build structure, in which the contractor directly retained both engineers without an intermediary prime professional, created a novel multi-party responsibility allocation problem that the original BER question did not address.

This question arose because the BER analysis established a graduated escalation sequence - confront Engineer B, report to contractor, withdraw if unresolved - without specifying whether contractor inaction triggers an additional mandatory step of state board notification or whether withdrawal alone discharges Engineer A's ethical obligation. The structural footing context, with its direct life-safety implications for future occupants, created pressure to treat the escalation threshold as lower than it would be for non-safety-critical engineering work, generating a question the original BER framework left structurally open.

This question arose because Engineer B's sole-purpose structural footing engagement creates a structural paradox: the general consulting-practice flexibility that allows competence remediation through collaboration was designed for multi-scope firms, not for a retained engineer whose entire engagement purpose is the very task he cannot competently perform. The question crystallizes when the data of sole-purpose retention collides with two irreconcilable warrants - one permitting delegation and one prohibiting it - leaving the ethical sufficiency of collaboration genuinely contested.

This question arose because the data of confirmed structural incompetence with life-safety consequences places Engineer A at the intersection of two temporally incompatible obligations: the profession's collegial norm of direct confrontation before external escalation, and the overriding public-welfare norm that cannot tolerate procedural delay when catastrophic harm is foreseeable. The question is not merely about sequence but about whether the irreversibility of structural failure collapses the ethical space between the two steps entirely.

This question arose because the data of a credential investigation that reveals cross-discipline background without direct proof of incompetence places Engineer A between two epistemically competing warrants: one that protects Engineer B from premature professional challenge and one that protects the public from delayed intervention. The question crystallizes at the precise evidentiary gap where credential evidence is sufficient to raise concern but insufficient to constitute certainty, making the activation point of the challenge obligation genuinely contested.

This question arose because two BER-derived principles that normally operate in different domains - the ethics-over-licensure principle and the consulting-flexibility principle - are placed in direct collision by Engineer B's situation, where consulting status might seem to afford flexibility but the sole-purpose nature of the engagement may strip that flexibility entirely. The question is whether the consulting-flexibility principle has any residual application after the sole-purpose constraint and the higher-standard principle jointly operate, or whether those two constraints together foreclose it completely.

This question arose because the data of a contractor retaining an unqualified engineer without apparent screening places two accountability-allocation warrants in tension: one that distributes competence verification responsibility to the client who controls retention decisions, and one that insists the engineering profession's self-policing norm cannot be diluted by assigning gatekeeping to non-engineer clients. The question is not merely about who failed but about whether recognizing the contractor's obligation structurally undermines the profession's internal accountability architecture.

This question emerged because Engineer B's acceptance of a structural footing assignment despite a chemical engineering background directly activates the categorical deontological warrant against practicing outside competence, yet the existence of a general PE license creates a competing legal-minimum rebuttal that forces the question of whether the duty is truly unconditional. The deontological framing sharpens the issue by demanding an answer independent of whether harm actually materialized.

This question arose because the contractor's retention decision is the precise moment where consequentialist logic must assign weights to public safety risk versus project continuity, and the confirmed incompetence of Engineer B makes the safety cost non-trivial and potentially catastrophic given the structural nature of the assignment. The absence of a clear probability estimate for harm and the availability of partial mitigation strategies prevent the calculus from resolving cleanly, generating the ethical question.

This question emerged because virtue ethics evaluates not just what Engineer A did but the sequence and completeness of virtuous action, and the Peer Competence Confrontation Before Authority Escalation Sequencing Obligation introduces a procedural virtue dimension that the simple act of reporting to the contractor does not satisfy. The gap between reporting to the contractor and directly confronting Engineer B becomes the site of ethical contestation about what full professional virtue requires.

This question arose because the deontological framework demands clarity on whether the duty to protect public safety is lexically prior to all other considerations or whether it is a conditional duty whose activation depends on empirical facts about risk level, and the contractor's inaction creates the precise scenario where that distinction becomes practically consequential. The BER precedent structure, which distinguishes employment from consulting contexts and graduated escalation steps, further complicates whether board reporting is the next obligatory step or merely a permissible one.

This question arose because the competence standard in NSPE Code Section II.2 is defined functionally rather than credentially, leaving open the possibility that informal pathways could satisfy it, yet the sole-purpose retention context and the structural safety stakes create strong pressure toward requiring verifiable, documented competence that informal experience cannot provide. The inability of Engineer A or the contractor to reliably evaluate undocumented informal expertise compounds the uncertainty, making the question practically urgent as well as philosophically contested.

This question arose because the data of Engineer B's sole-purpose structural engagement collides with two structurally opposed warrants: the general consulting-practice flexibility that permits subconsultant remediation and the sole-purpose engagement constraint that renders delegation a circular nullification. The question could not be resolved without determining whether Engineer B's oversight role itself demands structural competence, making the sub-delegation arrangement ethically insufficient on its own terms.

This question arose because the data of Engineer A possessing confirmed competence concerns but limiting action to contractor notification, followed by a hypothetical failure causing injury, places two warrants in direct conflict: the engineering self-policing and public welfare obligations that extend responsibility beyond initial reporting, and the graduated escalation principle that may have discharged Engineer A's duty at the contractor-notification stage. The question could not be resolved without determining whether Engineer A's partial action constituted ethical sufficiency or culpable omission.

This question arose because the contractor's dismissal of Engineer A's concerns creates a data state in which two warrants-withdrawal as ethical recourse and escalation as primary obligation-point toward different and potentially incompatible actions, while the concept of complicity introduces a temporal threshold that neither warrant precisely defines. The question could not be resolved without determining both the sequencing of Engineer A's remaining obligations and the moment at which passive continuation crosses into active ethical violation.

The board concluded that Engineer A's ethical responsibility to report was activated by the observable mismatch between Engineer B's disciplinary background and the structural footing assignment, and that the public safety stakes of foundation design made inaction ethically impermissible regardless of uncertainty about Engineer B's actual competence level.

The board concluded that Engineer B's ethical violation was complete at the moment of acceptance because the antecedent duty of self-assessment - not merely a reactive duty to decline when challenged - required proactive disclosure and refusal, and because the sole-purpose nature of the engagement made delegation or collaboration structurally impossible as a cure given Engineer B's inability to competently oversee or seal the resulting work.

The board concluded that it would be unethical for Engineer B to perform the structural footing design because his chemical engineering background does not provide the domain-specific education or experience required by the ethics code, and because the public safety implications of foundation design make the competence standard non-negotiable regardless of his general PE licensure.

The board concluded that the contractor bears an independent ethical failure for degree-to-task alignment verification but carefully cabined that finding to prevent it from diluting Engineer A's reporting obligation or Engineer B's duty to decline, treating the contractor's negligence as an amplifying systemic risk factor rather than a responsibility-shifting one.

The board concluded, by analogy to BER Case 85-3, that Engineer B's retention by the contractor for structural footing design conferred no structural engineering competence that Engineer B did not independently possess, and that the categorical duty to practice only within competence was violated at the moment of acceptance entirely independent of whether the footing design might have proven structurally sound.

The board concluded that Engineer A's reporting to the contractor was not merely permissible but ethically obligatory, grounded in the peer competence challenge obligation triggered by Engineer B's lack of documented structural training; however, the board left open whether Engineer A satisfied the collegial sequencing norm of direct peer confrontation before escalation, treating that sequencing question as unresolved rather than definitively answered.

The board concluded that Engineer A's ethical obligation escalates beyond the contractor level if the contractor takes no corrective action, driven by the catastrophic and irreversible nature of structural footing failure and the public welfare paramount principle, such that continued silence after contractor inaction risks making Engineer A complicit in foreseeable public harm - a posture the code does not permit.

The board concluded that Engineer B bore an independent, primary, and self-executing ethical obligation to proactively disclose his chemical engineering background and absence of structural training before accepting the footing assignment, and that his failure to do so - compounded by proceeding with the work - constituted a failure of professional candor that elevated the violation beyond mere technical incompetence.

The board concluded that while the contractor bears an independent ethical and practical responsibility to verify Engineer B's qualifications before retention, the contractor's failure to do so amplifies rather than diminishes Engineer A's reporting obligations, because the profession's self-policing architecture exists specifically to compensate for clients' and contractors' inability to independently assess cross-discipline competence deficiencies.

The board concluded that Engineer A's ethical obligation escalates progressively - from contractor notification to direct confrontation of Engineer B, then to state licensing board notification, and potentially to project withdrawal - if each prior step fails to produce corrective action, with the structural footing context specifically accelerating that escalation threshold because the severity and irreversibility of potential harm make continued silence after contractor inaction a form of complicity the code does not permit.

The board concluded that Engineer B cannot ethically cure his competence deficiency through sub-delegation because the II.2.c remedy presupposes a prime professional with genuine coordination competence overseeing specialists, whereas Engineer B's sole-purpose engagement means delegation would be circular - he would retain sealing responsibility for work he cannot competently review, directly violating II.2.b's prohibition on sealing work outside one's competence.

The board concluded that the direct confrontation requirement and the public welfare paramount principle are not irreconcilable - public welfare does not skip the confrontation step but instead accelerates it, meaning Engineer A must move through each escalation stage with urgency proportionate to the catastrophic and irreversible harm potential of structural footing failure, and must escalate immediately if Engineer B fails to self-correct within a compressed but reasonable timeframe.

The board concluded that the threshold for activating Engineer A's peer competence challenge obligation is reached when diligent, good-faith investigation produces reasonable, evidence-based doubt about competence in a safety-critical domain, and that Engineer A crossed that threshold upon discovering Engineer B's chemical engineering degree combined with no identifiable foundation design training - the standard being reasonable doubt, not proof beyond doubt, given the public safety stakes.

The board concluded that consulting context flexibility affords no benefit to Engineer B because that principle operates at the organizational level - permitting firms to retain specialists to cure competence gaps - and Engineer B's sole-purpose individual engagement provides no organizational structure within which such flexibility could be exercised, while the ethics code higher standard principle independently and directly forecloses any argument that his general PE licensure authorizes structural footing design.

The board concluded that the contractor's degree-to-task alignment verification obligation and the engineers' self-policing obligations are mutually reinforcing but hierarchically ordered: Engineer B's duty to self-assess and decline, and Engineer A's duty to challenge, are primary obligations that exist independently of and prior to any contractor screening, while the contractor's verification duty functions as a secondary institutional safeguard that catches gaps in professional self-regulation rather than substituting for it.

The board concluded that Engineer B committed an unconditional ethical violation by accepting the structural footing assignment because the deontological duty under II.2.a attaches at the moment of acceptance and is entirely indifferent to whether the resulting design happened to be sound - the absence of structural training made the acceptance categorically impermissible regardless of outcome.

The board concluded that the consequentialist analysis unambiguously disfavors retaining Engineer B because the potential harms - building collapse, death, and serious injury - are catastrophic in magnitude, irreversible in nature, and affect many people, while the countervailing benefits of retaining an already-engaged chemical engineer are trivially small by comparison, making the contractor's pre-retention qualification verification a consequentially essential safeguard.

The board concluded that Engineer A demonstrated genuine professional virtue by escalating to the contractor but fell short of the fully virtuous ideal by bypassing direct confrontation with Engineer B first, because a complete expression of professional virtue requires both the courage to challenge a peer directly and the integrity to escalate when that challenge fails - the two obligations are sequential rather than alternative.

The board concluded that Engineer A's duty to escalate to the licensing board is not unconditional in the abstract but becomes unconditional in this specific context because the combination of severe and imminent structural safety risk, the irreversibility of potential harm, and the contractor's failure to act eliminates any legitimate basis for further deferral - at that point Engineer A holds knowledge of an ongoing public threat that no private remedy has addressed.

The board concluded that substantial post-degree self-study and informal mentorship are insufficient to satisfy the II.2.a competence standard for structural footing design because the code's 'experience' requirement implies verifiable, supervised professional practice rather than self-reported learning, and the catastrophic-harm context demands that competence be objectively demonstrable - Engineer A and the contractor should require documented project history, supervising engineer references, and formal continuing education records, and should treat their absence as unrebutted reasonable doubt.

The board concluded that sub-delegation would not resolve the ethical problem because Engineer B's inability to competently oversee and seal the work means the arrangement would be nominal rather than substantive - the Section II.2.c exception requires meaningful oversight capacity that Engineer B does not possess, and the sole-purpose engagement eliminates any independent coordination role that might otherwise justify invoking it.

The board concluded that Engineer A would bear significant ethical responsibility for harm resulting from unreported concerns because the combination of the public welfare paramount principle and the profession's self-policing obligation converts knowledge of foreseeable risk into an affirmative duty to intervene - failure to report would make Engineer A a passive participant in the competence violation rather than a neutral bystander.

The board concluded that contractor rejection of Engineer A's concerns triggers a two-part obligation - project withdrawal to avoid personal complicity and licensing board notification to protect the public - because withdrawal alone removes Engineer A from the ethical violation but does nothing to address the ongoing public safety threat that Engineer A's reporting obligation was designed to prevent.

The board concluded that the public welfare paramount principle does not override collegial-first sequencing because the sequenced process is itself a form of public safety protection - the principle only collapses procedural steps when the risk is imminent and the process has already failed, not at the moment reasonable doubt first arises about a peer's competence.

The board concluded that consulting flexibility was entirely foreclosed in Engineer B's situation because the sole-purpose engagement eliminated the organizational infrastructure through which flexibility operates, leaving the ethics code's higher standard to prevail unconditionally - consulting flexibility is an organizational remedy that requires an organization to work through, not a personal exemption from competence requirements.

The Board resolved the tension between contractor screening responsibility and professional self-policing by implicitly prioritizing the latter: ethical conclusions were directed at Engineer B's acceptance decision and Engineer A's reporting duty rather than at the contractor's screening failure, on the normative ground that engineers must self-screen and peer-police first, with contractor verification serving only as a secondary backstop. This structure preserves the internal accountability norms of the profession and prevents contractor negligence from becoming a shield that diminishes individual engineer responsibility.

Should Engineer B accept the structural footing design assignment based on holding a valid PE license, or decline the assignment and disclose his chemical engineering background to the contractor before any design work commences?

Should Engineer A first directly confront Engineer B and recommend withdrawal from the structural footing assignment before reporting concerns to the contractor, or should Engineer A report concerns directly to the contractor given the structural safety risk without first confronting Engineer B?

If the contractor takes no corrective action after Engineer A reports concerns about Engineer B's competence, should Engineer A escalate to the state licensing board and withdraw from the project, or continue participation while deferring to the contractor's authority over the retention decision?

Should Engineer B attempt to cure the structural footing competence deficiency by sub-delegating the actual design to a qualified structural engineer while retaining coordination responsibility, or must Engineer B recognize that the sole-purpose nature of his engagement makes sub-delegation an ethically unavailable remedy and decline the assignment entirely?

Should the construction contractor independently verify Engineer B's structural engineering qualifications before retention, or rely on Engineer B's PE license as sufficient evidence of competence for the structural footing assignment?

Has Engineer A's credential investigation produced a sufficient objective basis to activate the peer competence challenge obligation and proceed with confronting Engineer B, or must Engineer A conduct further investigation before concluding that reasonable doubt about Engineer B's structural competence is warranted?