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 principle that a prime professional should retain or recommend experts and specialists when performing substantial services on a project, and that engineers have an ethical obligation to work only in areas of their competence or retain those who do.

Cited to reaffirm the principle from BER Case 71-2 that engineers must seek work only within their competence or retain qualified individuals, in the context of a firm altering its qualifications to secure a contract.

Cited as the most closely analogous precedent, where an engineer with only chemical engineering background was deemed unqualified to serve as county surveyor because he lacked substantive background in surveying; the Board applies the same reasoning to conclude Engineer B lacks competence to design structural footings.

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.

The Board's finding that Engineer B's performance of the footing design would be unethical rests on a per se competence mismatch: a chemical engineering background does not, absent demonstrated subsequent training, establish qualification under II.2.a for structural foundation work. This suggests the Board's standard is not merely subjective doubt (as held by Engineer A) but an objective evidentiary gap—the absence of any established credential in foundation design is itself sufficient to trigger the ethical violation, independent of whether the resulting footing design would actually be deficient in practice.

The Board's conclusion implicitly places the primary duty of self-restraint on Engineer B himself, independent of Engineer A's intervention. Even if Engineer A had never raised concerns or reported them to the contractor, Engineer B would still bear an unmet obligation under II.2.a to decline an assignment outside his demonstrated competence. This means the ethical violation in Conclusion 1 exists prior to and independent of the reporting behavior addressed in Conclusion 2, making Engineer B's culpability the primary and freestanding issue, while Engineer A's conduct is a secondary, contingent question.

The Board's treatment of Engineer A's duty to question and report suggests a bounded obligation: Engineer A's ethical responsibility is satisfied by raising the concern to the party with authority to act (the contractor), and does not necessarily extend to policing the contractor's subsequent decision, verifying Engineer B's credentials independently, or refusing further cooperation on the project if the contractor disregards the warning. This reading leaves open whether Engineer A's duty is discharged entirely upon reporting, or whether continued participation in a project using an unqualified footing design would itself implicate Engineer A in a downstream ethical or public-safety failure under III.2.b if Engineer A is asked to coordinate or rely upon that design.

Regarding Q101, once Engineer A has fulfilled the Engineer A Competence Concern Report by notifying the contractor, if the contractor disregards the concern and proceeds with Engineer B's design, Engineer A's obligations escalate under the Engineer A Client and Authority Reporting Duty. Because public safety is implicated by potentially inadequate structural footings, Engineer A cannot treat the initial report as discharging all ethical responsibility; further action may include escalating concerns to a state licensing board or other authority, consistent with the profession's paramount duty to protect public safety.

In response to Q102, Engineer B bears an independent, non-delegable ethical obligation under the Engineer B Footing Competence Duty to self-assess his own qualifications before accepting the footing design assignment. This obligation exists irrespective of whether Engineer A or anyone else raises concerns; the Code's competence provisions (II.2. and II.2.a.) place the primary duty of self-restraint on the engineer performing the work, not solely on third parties who might detect the deficiency.

Addressing Q103, the construction contractor, as the party controlling the design/build process and the Specialist Retention Decision, bears a practical if not strictly codified ethical responsibility to exercise due diligence when retaining specialists such as Engineer B for safety-critical work like structural footing design. The contractor's failure to verify Engineer B's qualifications contributed to the Qualification Verification Failure and created the conditions for the competence gap identified in the case.

In response to Q301, from a deontological perspective Engineer B violated a clear duty of competence by accepting the footing design assignment without demonstrated qualifications in foundation engineering. NSPE Code provisions II.2. and II.2.a. establish a categorical duty—not a consequence-dependent one—that engineers undertake assignments only within their area of competence; Engineer B's chemical engineering background and lack of subsequent training in foundation design place this assignment outside that duty's bounds regardless of whether harm ultimately resulted.

Regarding Q302, from a consequentialist standpoint, Engineer A's decision to report concerns to the contractor was justified by the magnitude of potential harm from a structurally deficient footing design, even without certainty that Engineer B's work would in fact fail. Given that structural footings are safety-critical elements whose failure could endanger the public, the expected disutility of remaining silent outweighed the social costs of raising a peer's competence concerns, supporting Engineer A's intervention as ethically warranted.

In response to Q303, viewed through a virtue-ethics lens, Engineer B failed to exhibit professional integrity by accepting the footing design assignment without first disclosing the limits of his chemical engineering background to the contractor. A virtuous engineer, oriented toward honesty and prudence, would have proactively disclosed the mismatch between his training and the assignment rather than allowing the contractor to assume competence that was never established.

Addressing Q304, from a deontological standpoint Engineer A fulfilled a duty that prioritizes public protection over collegial deference. The obligation to question a peer's competence, captured in the Engineer A Peer Confrontation Duty, reflects the Code's hierarchy of duties in which safeguarding public safety and welfare takes precedence over professional courtesy or reluctance to criticize a fellow engineer.

In response to the counterfactual Q401, if Engineer B had possessed documented subsequent formal training or certification specifically in foundation design, the Board's conclusion would likely differ, since the Code's competence standard (II.2.a.) turns on demonstrated qualification by education or experience rather than on the engineer's original degree discipline alone. The unethical nature of the assignment in the actual case stems specifically from the Qualification Verification Failure and absence of any evidence of relevant training, not from the chemical engineering degree per se.

Regarding the counterfactual Q402, even if Engineer A had harbored no personal doubts about Engineer B's competence, the Board would likely still find an ethical responsibility to investigate given the objective absence of verifiable qualifications (Qualification Verification Failure) and the safety-critical nature of structural footing design. The duty to question competence in such circumstances arises from the objective competence gap and role-based responsibility for project integrity, not merely from Engineer A's subjective reservations.

In response to the counterfactual Q403, if the contractor had instead asked Engineer A to coordinate and approve Engineer B's footing design as part of an integrated design/build responsibility, the analysis would shift toward Code provision II.2.c., which permits an engineer to coordinate an entire project provided that each component is designed by a qualified specialist under appropriate signature and seal. In that scenario, Engineer A's approval role would create a more direct oversight duty, potentially making Engineer A more clearly accountable for verifying Engineer B's competence before allowing the design to proceed.

The tension between respecting Engineer B's professional autonomy as an independently retained peer and the Competence Concern in Footing Design is resolved in favor of competence: an engineer's freedom to accept work from a client is not absolute but is bounded by the Code's competence requirements, so Engineer A's peer status did not excuse silence in the face of a credible competence gap. This shows that competence verification duties can override normal professional deference between engineers who are not in a supervisory relationship.

The contractor's practical interest in efficiently retaining a specialist for a discrete task (reflected in Specialist Retention Infeasible for Footings) does not diminish or dilute the Competence Concern in Footing Design; the Board's reasoning implies that convenience-based staffing decisions in design/build arrangements cannot substitute for verified qualification matching when structural safety is at stake. Practical project-management considerations are subordinate to the core competence principle whenever public safety is implicated.

Taken together, the case illustrates a general prioritization rule within the NSPE Code: competence-related obligations (II.2 and II.2.a) function as threshold constraints that take precedence over relational or operational principles such as collegial non-interference or contractor efficiency. Once a competence gap is identified, it activates downstream reporting duties (Engineer A Competence Concern Report) regardless of countervailing interests, indicating that public safety concerns embedded in competence provisions are treated as near-absolute rather than balanced case-by-case against convenience or autonomy interests.

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?

Once Engineer A reported concerns to the contractor, what further obligations, if any, does Engineer A have if the contractor ignores those concerns and proceeds to have Engineer B design the footings anyway?

Does Engineer B bear an independent ethical obligation to self-assess and decline the footing design assignment regardless of whether Engineer A ever raises concerns?

What responsibility does the construction contractor bear for retaining Engineer B without verifying his qualifications in foundation design, given that the contractor controls the design/build process?

Should Engineer A have gone beyond reporting concerns to actively investigate or verify Engineer B's credentials before forming a conclusion about his competence?

How should the principle of respecting professional autonomy and inter-firm boundaries be balanced against the Competence Concern in Footing Design when Engineer A, who is not Engineer B's supervisor, raises concerns about a peer's qualifications?

Does the contractor's practical interest in efficiently retaining specialists for discrete tasks (Specialist Retention Infeasible for Footings) conflict with the Competence Concern in Footing Design that demands rigorous qualification matching for structural safety work?

From a deontological perspective, did Engineer B violate a duty of competence by accepting an assignment to design structural footings despite lacking demonstrated training in foundation engineering?

From a consequentialist standpoint, did the potential public safety risk from an unqualified footing design justify Engineer A's decision to intervene by reporting concerns to the contractor, even absent certainty of actual harm?

Did Engineer B act with professional integrity, in the virtue-ethical sense, by accepting a structural footing design assignment outside a chemical engineering background without first disclosing the limits of his qualifications to the contractor?

From a deontological perspective, did Engineer A fulfill an obligation of professional solidarity and public protection by questioning a peer's competence rather than remaining silent out of collegial deference?

If Engineer B had in fact possessed subsequent formal training or certification in foundation design beyond his chemical engineering degree, would the Board still have concluded it was unethical for him to perform the footing design?

If Engineer A had not been able to confirm his own reservations about Engineer B's competence and instead had no doubts at all, would the Board still have found Engineer A ethically obligated to question Engineer B's competency and report concerns to the contractor?

If the construction contractor, rather than separately retaining Engineer B, had asked Engineer A to coordinate and approve the footing design as part of the overall design/build project, would the Board's conclusion about the unethical nature of Engineer B's independent retention still apply?

The Construction Contractor's decision to retain a specialist sets the causal chain in motion, leading directly to Engineer B's acceptance of the assignment, so although it carries no normative commitments itself, its significance lies in creating the conditions under which competence obligations become relevant.

Engineer B's acceptance of the assignment violates the duty to undertake work only when qualified and to perform services only within one's area of competence, and because this acceptance causally triggers the subsequent qualification investigation, the violation matters as the root failure that necessitates later scrutiny of B's credentials.

The qualification investigation fulfills the obligation to objectively determine whether Engineer B has sufficient education, experience and training, and is guided by the competence standard, yet because it causally leads to a verification failure, its normative value is undermined by the outcome it produces, showing that even a proper process can expose an underlying competence gap.

Engineer A's concern reporting fulfills the obligation to bring competence concerns to the client's attention and is guided by the competence-based standard, and because it causally follows from the qualification verification failure and the resulting competence concern, it represents the corrective mechanism that addresses the earlier violation in the causal chain.

The question arose because Engineer A's reservations about Engineer B's qualifications, combined with the impracticality of retaining a specialist solely for footing design, created a direct conflict between the ethical principle of competence-bounded practice and the operational necessity that drove Engineer B's retention.

The question arises because the code of ethics does not specify a required sequence or threshold for escalating competence doubts about a peer, leaving open whether internal resolution or external reporting is the primary obligation.

The question emerges because the contractor's inaction after being informed leaves unresolved whether Engineer A's ethical duty is satisfied by disclosure alone or whether the continuing competence gap in Engineer B's footing design obligates further intervention.

The question arises because the Code's individual competence obligation and the situational dependence on a colleague's disclosure create two plausible loci of responsibility, leaving unclear whether ethical duty attaches to self-knowledge or to external notification.

The question arises because the Qualification Verification Failure occurred within a design/build arrangement where the contractor, not a licensed engineer, made the Specialist Retention Decision, creating ambiguity about whether competence-verification obligations attach to engineers alone or extend to the controlling business entity.

The question arises because the data only shows Engineer A forming and reporting a concern, without evidence of direct verification, creating uncertainty about whether reporting alone was sufficient or whether professional fairness demanded deeper inquiry first.

The question arises because the same facts, an out-of-scope engineer being retained for structural footing work, support both a competence-protection duty and a peer-respect norm, and no clear supervisory relationship exists to resolve which obligation takes precedence.

The question arises because the contractor's practical need to retain one consultant for multiple discrete tasks collides with the structural safety expectation that footing design requires specifically verified competence, leaving open whether efficiency concerns can override rigorous qualification standards.

The question arises because the facts show a documented competence gap and an accepted assignment, creating an unresolved tension between a strict competence-boundary principle and the practical constraint that specialist retention was not feasible under the circumstances.

The question arises because Engineer A acted on suspected rather than confirmed incompetence, forcing a comparison between a rule based duty to report competence concerns and a consequentialist calculus balancing uncertain public risk against the costs of unwarranted intervention.

The question arises because Engineer B's assignment acceptance created a visible mismatch between his credentialed expertise and the task, and the absence of an explicit disclosure act leaves it contested whether his conduct meets the virtue-based standard of integrity or merely the technical competence requirement.

The question arises because the same facts, an engineer raising doubts about a peer's competence, can be read either as a deontological duty to protect the public or as a breach of professional solidarity, making the correct warrant contested.

The question arises because the case record ties Engineer B's competence gap specifically to his chemical engineering education, and altering that single fact forces reconsideration of whether the Board's ethical conclusion depended on formal qualifications, practical experience, or both.

The question arises because the case facts pair Engineer A's actual reservations with his reporting obligation, leaving unclear whether the obligation is contingent on those reservations existing or would hold even if he had none.

The question arises because the Board's reasoning was built on the specific fact pattern of separate, contractor-driven retention of Engineer B, and altering that structural detail, by inserting Engineer A as coordinator and approver, tests whether the ethical violation stemmed from the retention mechanism itself or from the underlying failure to verify competence.

Given that Engineer B was retained solely to design footings despite a chemical engineering background with no shown structural training, the Board concluded that performing that design would violate the duty to work only within one's area of competence.

Because Engineer A knew Engineer B's background was in chemical rather than structural engineering, the Board concluded Engineer A was obligated to raise and report that concern to the contractor rather than remain silent.

Since the record showed only a chemical engineering background with no evidence of added structural training, the Board reasoned that the objective absence of credentials, not mere suspicion, was sufficient to establish the violation.

Because the ethical violation in Conclusion 1 could be identified without reference to Engineer A's actions, the Board implicitly reasoned that Engineer B bore a primary duty to decline the assignment on his own, making Engineer A's reporting a secondary matter.

Since Engineer A's only established action was reporting concerns to the contractor, the Board reasoned that this reporting could satisfy Engineer A's duty, while noting that a later request to coordinate or rely on the footing design could reopen the ethical question under III.2.b.

Given that the contractor ignored Engineer A's competence report and allowed Engineer B to proceed on safety-critical footing design, the board concluded that Engineer A's ethical duty escalates beyond the initial report because public safety concerns override the presumption that reporting once discharges all responsibility.

Given that Engineer B lacked foundation engineering training and nonetheless accepted the assignment, the board concluded that his obligation under II.2 and II.2.a to self-assess and decline unqualified work is independent and non-delegable, existing whether or not Engineer A or anyone else ever raised a concern.

Given that the contractor controlled the hiring of Engineer B and failed to verify his qualifications before assigning safety-critical footing design, the board concluded that this failure contributed to the competence gap and constitutes a practical ethical lapse even though the Code does not impose a formal duty on contractors.

Given that Engineer B's only demonstrated background was chemical engineering with no subsequent foundation design training, the board concluded that accepting the footing design assignment violated the categorical, non-consequentialist duty of competence under II.2 and II.2.a regardless of whether the design ultimately failed.

Given that structural footings are safety-critical and their failure could endanger the public, the board concluded that Engineer A's decision to report concerns to the contractor was consequentially justified even without certainty of actual failure, because the expected harm of silence exceeded the social cost of raising the concern.

Given that Engineer B's degree was in chemical engineering and no disclosure of this limitation was made to the contractor before accepting the footing design, the board concluded through a virtue-ethics lens that B failed to act with the honesty and prudence expected of a professional engineer.

Because Engineer A held credible reservations about Engineer B's qualifications for safety-critical footing design, the board reasoned deontologically that reporting those concerns fulfilled a duty ranked above collegial deference in the Code's hierarchy of obligations.

Since the original unethical finding rested on the absence of any verified foundation-related training rather than the chemical engineering degree itself, the board reasoned that documented subsequent qualification would likely change the outcome under the Code's competence standard.

Even if Engineer A had no personal doubts, the board reasoned that the objective absence of verified qualifications for safety-critical footing design would still impose a duty to question competence, since the obligation flows from the role and the risk, not merely from subjective suspicion.

Had the contractor instead assigned Engineer A to coordinate and approve Engineer B's footing design, the board reasoned that this formal oversight role under II.2.c. would create a direct duty to verify B's competence, unlike the actual case where A had only a peer relationship without approval authority.

Given that Engineer B was working outside his chemical engineering background on structural footings and Engineer A had genuine reservations, the Board concluded that peer autonomy could not excuse silence because competence obligations under the Code are not waived merely by the absence of a supervisory relationship.

Because the contractor's justification rested on staffing convenience rather than any verification of Engineer B's structural qualifications, the Board concluded that such practical considerations cannot substitute for actual competence matching when public safety is at stake.

Since a concrete competence gap in footing design was identified and Engineer A was positioned to recognize it, the Board reasoned that this triggered an near-automatic reporting obligation, treating competence and public safety as controlling over collegial or contractual convenience considerations in this specific fact pattern.

Should Engineer B accept the assignment to design the structural footings given his lack of demonstrated qualification in foundation engineering?

Should Engineer A report his concerns about Engineer B's competency to the contractor?

Must Engineer A take further action, such as escalating to a licensing authority, if the contractor ignores his reported concerns and proceeds with Engineer B's design?

Should the construction contractor verify Engineer B's qualifications before retaining him to design the structural footings?

Should Engineer A independently investigate or verify Engineer B's credentials before forming a conclusion about his competence, or is reporting the concern to the contractor sufficient?